The purpose of this assignment is to provide students with experience in structured and object-oriented analysis and design. This assignment is to be completed by groups of two students. Each group is to work together, distribute work equally and submit one group submission. The submission is to include an individual statement of contribution signed by each student that identifies who contributed to each part of the solution and which parts were completed together. The two students in the group need to examine their Individual Assignment submissions and, as a group, combine ideas from each member's case study completed in Assignment 1 to form a new case study. They will then need to perform further analysis and design based on the new case study.

Timelines and Expectations - Marks: Assignment will be assessed based on a mark out of 100. Percentage Value of Task: 30% of the course marks, Due: Week 11, Friday 5:00pm. Minimum time expectation: 30 hours. This is a group (2 students only) assignment. Both students are expected to contribute equally to the assignment submitted. Submission - An electronic copy of the Group Assignment should be submitted via Moodle. Partner students should refer to their course lecturer for submission instructions.

The assignment should be submitted in a pdf document in a formal report format (with school cover page attached) containing brief walkthrough/discussions of the diagrams/charts along with those diagrams/charts/drawings on or before the due date. Students should use a CASE tool such as Enterprise Architect as appropriate. Note that all diagrams are to be drawn using appropriate conventions, preferably those used by your textbook (Kendall, K.E. & Kendall, J.E. (2014). Systems Analysis and Design 9/E. Pearson Education Limited, Harlow, England) l. All files, including the completed statement provided on the next page, should be zipped and uploaded to Moodle. Your lecturer/tutor may have further instructions. Marking Criteria/Rubric - A student’s work will be assessed based on answers to all parts of the Assessable Tasks/Requirements and a student’s overall mark may be adjusted based on their contribution to the group.

Cycle 1, Item A (1A) - Events Table - Correct identification of maximum possible number of core events, All other associated information (Type of Events, Triggers, Activity/Use Case, Responses and Destinations) Correct naming/language conventions. 1B - Context Diagram - Appropriate number of External Entities/Agents and Data Flows, Appropriate naming, numbering and drawing conventions. 1C - Level 0 DFD - Appropriate number of Processes, Data Flows and Data Stores, Correct naming, numbering and drawing conventions, Level 0 appropriately balanced, levelled and made consistent. 1D - Level 1 DFD for 2 selected Processes - More detailed with appropriate number of exploded Processes, relevant Data Flows, associated External Agents and Data Stores, Correct naming, numbering and drawing conventions.

2A - USE Case Model - Complete with correct Use Cases and Actors, Appropriate interactions, Correct use of naming and drawing conventions. 2A - Use Case Scenario for the selected Use Case - Fully developed including exception conditions, Correct use of conventions. 2Ba - Activity Diagram for the selected Use Case - Appropriate identification and flow of activities, and consistent to the Use Case selected, Correct use of naming and drawing conventions. 2Bb - System Sequence Diagrams (SSD) - Correct SSD for the overall system, Appropriate actor(s) and messages identified in correct sequence, Correct use of naming and drawing conventions.

2Bb - Sequence Diagrams (SD) for the selected Use Case - Correct SD for the selected Use Case, Appropriate objects, actors and messages identified in correct sequence, Correct use of naming and drawing conventions. 2C - Domain Model Class Diagram for the overall system - Appropriate number of Classes with attributes and some major methods, Appropriate multiplicities, associations including generalization/specialization, Correct naming/drawing conventions. 2D - Statechart Diagram for the selected object - Appropriate number of States, State Transitions, and pathsindependent/concurrent, Correct use of naming/drawing conventions. 2E - Design of one of the major Reports as Output - Contains all appropriate information as required, Use of appropriate Printed Report design considerations including clear layout and formatting including appropriate headings. Based on contribution statements, these totals may be adjusted if there is inequity in student contributions. Final marks to be adjusted to equivalent percentage and scaled to a Total Mark out of 30.