MIS605 Assignment Help

	ASSESSMENT 1 BRIEF
Subject Code and Title	MIS605 Systems Analysis and Design
Assessment	Requirement Analysis
Individual/Group	Individual
Length	2000 words +/- 10%
Learning Outcomes	The Subject Learning Outcomes demonstrated by the successful completion of the task below include: a) Identify, critically evaluate and recommend information systems solutions for inefficiencies in business processes, procedures, and work practices using data and process modeling techniques. b) Formulate, validate, and document business requirements for a medium-scale information system development project and effectively communicate these requirements to the stakeholders. c) Demonstrate the ability to effectively analyze, design, and develop information systems using Unified Modelling Language (UML) models.
Submission	For 12-week Duration: Due by 11:55 pm AEST Sunday end of Module 3.1 (Week 5) For 6-week Duration: Due by 11:55 pm AEST Sunday end of Module 3.1 (Week 3)
Weighting	30%
Total Marks	100 marks

Task Summary

In response to the case study provided to you by your facilitator, identify the functional and the non-functional requirements for the required information system and then decide on the project and the software development life cycle. Also, identify actors, build a use case diagram, and document a set of use cases.

Context

System analysis methods and skills are of fundamental importance for a Business Analyst. This assessment allows you to enhance your system analysis skills by capturing the business and then functional and non-functional requirements of a system. It helps you in identifying “what” the proposed system will do and “how”?

Instructions

Please read the case study provided to you by your facilitator. Note that every piece of information provided in the case has a purpose.
Once you have completed reading the case study. Please answer the following questions:

Question 1 (10 mark).

For the given case study, propose a suitable software development life cycle and project life cycle. Provide diagrams with justification.

Question 2 (10 mark).

Identify all the human and non-human actors within the system. Provide a brief description of every actor, clearly describing if the actor is a primary, secondary, or abstract actor.

Question 3 (30 marks).

Using the information provided in the case study, build and provide a Use Case Diagram (UCD) using any diagramming software.

Word Count and Layout

∙ The total word count for this assessment should be no more than 2200 words. ∙ Please provide all your answers in an MS Word document.

∙ Please note that you are NOT required to copy the questions over to the MS Word document. Use the question number to indicate which question your answer relates to. ∙ The recommended font size is 12 with 1.5 line spacing.

Referencing

It is essential that you use the appropriate APA style for citing and referencing research. Please see more information on referencing on the Academic Skills webpage.

Submission Instructions

Please submit the written assessment via the Assessment link within Assessment 1. The Learning Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedback can be viewed in My Grades.

Academic Integrity

When submitting their assessment task, students will be asked to declare the academic integrity of their assessment by completing and signing an assignment cover sheet. You can find the assignment cover sheet here

All students are responsible for ensuring that all work submitted is their own and is appropriately referenced and academically written according to the Academic Writing Guide. Students also need to have read and be aware of Torrens University Australia Academic Integrity Policy and Procedure and subsequent penalties for academic misconduct.

Students also must keep a copy of all submitted material and any assessment drafts.

Special Consideration

To apply for special consideration for a modification to an assessment or exam due to unexpected or extenuating circumstances, please consult the Assessment Policy for Higher Education Coursework and ELICOS and, if applicable to your circumstance, submit a completed Application for Assessment Special Consideration Form to your Learning Facilitator.

Assessment Attributes	Fail (Yet to achieve minimum standard) 0-49%	Pass(Functional)50-64%	Credit(Proficient)65-74%	Distinction(Advanced)75-84%	High Distinction (Exceptional) 85-100%
Question 1: For the given case study, propose a suitable software development life cycle and project life cycle. Provide diagrams with justification. 10%	The proposed project life cycle and the software development life cycle are not appropriate for this case study.	The proposed project life cycle and the software development life cycle are appropriate for this case study.	The proposed project life cycle and the software development life cycle are appropriate for this case study. The solution is provided with strong reasoning but diagrams need improvements.	The proposed project life cycle and the software development life cycle are appropriate for this case study. The solution is provided with strong reasoning and the diagrams are clear and reflect the case requirement.	The proposed project life cycle and the software development life cycle are appropriate for this case study. Solution is provided with strong reasoning and the diagrams are clear and reflect the case requirement. The student clearly explains the advantages of the proposed solution for the given case.
Question 2: Identify all the human and the non-human actors within the system. Provide a brief description against every actor, clearly describing if the actor is primary, secondary or an abstract actor. 10%	The actors identified are largely incorrect.	The actors identified are partially incorrect.	The actors identified are correct but sufficient detail is not provided.	The actors identified are correct and sufficient detail is provided.	The actors identified are correct and sufficient detail is provided. The student has a clear understanding of human, non-human, primary, secondary, and abstract actors.
Question 3: Using the information provided in the case study, build and provide a Use Case Diagram (UCD) using any diagramming software. 30%	UCD does not include major use cases, many actors in the UCD are missing, associations of actors are not given with the use cases, extends and includes are not identified where required and not linked to the base use case. The use case diagram does not sync well with the requirements laid down in the case study.	UCD misses some important use cases, some actors in the UCD are missing, and some associations of actors are not given with the use cases, extends, and includes are partially identified (where required). Extends and includes are not appropriately linked to the base use cases. The use case diagram does not fully sync with the requirements laid down in the case study.	UCD has all the use cases and actors, some associations of actors are not given with the use cases, extends and includes are partially identified (where required). Extends and includes are not appropriately linked to the base use cases. The use case diagram largely syncs with the requirements laid down in the case study.	UCD has all the use cases and actors, associations of actors are given with the use cases, extends and includes are identified (where required). Extends and includes are not appropriately linked to the base use cases. The use case diagram syncs in completely with the requirements laid down in the case study.	UCD has all the use cases and actors, associations of actors are given with the use cases, extends and includes are identified (where required). Extends and includes are appropriately linked to the base use cases. The use case diagram syncs in completely with the requirements laid down in the case study.
Question 4: Document all use cases (use case methods). All use cases identified in the Use Case Diagram in Question 3 must be elaborated in detail. 50%	Use case descriptions are incomplete and do not sync in with the given case study.	Use case descriptions are partially complete and do not fully sync in with the given case study.	Use case descriptions are complete but do not fully sync in with the given case study.	Use case descriptions are complete and are in sync with the given case study.	Use case descriptions are complete, detailed, and in sync with the given case study.