ITECH2002 Systems Modelling - Assignment 2

Task 2 - Individual work [80 marks]

Students need to identify the sub-system they are working on, select two complicated use cases and then provide fully developed use case descriptions and activity and system sequence diagrams for both. They then must choose one of those two use cases and provide an InVision storyboard and test plan for that use case.

One activity diagram must have at least one decision making, parallelism or loop. If the diagram does not have any of these features, the fully developed use case might be incomplete; a student may then need to revisit the use case to ensure that it is complete.

One system sequence diagram must have at least one of the following: a loop, optional or alternate frames. If the diagram does not have any of these features, the student must revisit their use case to ensure that it is complete.

An example template - ITECH2002_Assignment2_TestPlan_Template – to help you complete your test plan has been provided with this assignment. Students are expected to provide sufficient tests for each part of the mnemonic. It would be unusual for example to only have one Error test.

The individual submissions in the group report are expected to contain (for each student):

1. The name of the sub-system they are modelling;
2. The fully developed use case descriptions, activity diagrams, and system sequence diagrams for two of the most complex use cases of the chosen sub-system. Activity and system sequence diagrams may be created in any package e.g. DrawIO, LucidChart or Enterprise Architect but they must comply with the notation from the text, Systems Analysis and Design in a Changing World (Satzinger et. al., 2016);
3. Snapshots of all individual screens for the use case chosen by the student. The use case chosen must be one of the two use cases selected in the previous step, step 2. Fundamental principles of user-interface design (see lecture notes and Satzinger et. al. (2016), p. 223) should be followed when designing storyboard screens. Screens may be of any file type and be created in the software of the student’s your choice, but it must be possible to load them into and use them in InVision Studio or on the InVision web application;
4. Link for the student’s InVision screens (if applicable);
5. The test plan for the use case chosen in step 3 – in other words, the test plan must be for the same use case as for the screen storyboard.

Students need to follow best practices as far as modelling, interface design and testing are concerned. Satzinger et. al. (2016) and the lecture slides can help students with this.

The group report should be professional in nature and follow the university guidelines specified later in this document in the Marking Criteria section.