This assignment has group work and individual work components. Please note each student must contribute equally to the group work component. The following sections describe the tasks for the group and individual work.
Task 1 - Group work [20 marks]
You should develop a high-level InVision screen design that links to the screen of each member. Share with your lecturer and tutor the link to your team’s InVision screen design. Group marks will be allocated to group report and top-level menu/ initial screen and consistency of look and feel across different functions. The top-level design must provide an opportunity to access all group member screens i.e. you need to make sure that users can go to each screen from the top-level screen. The purpose of having a common top-level screen is to give you the experience of creating screens as a team.
The main part of the group report document is expected to contain the following information:
1. The name of the organisation you are modeling;
2. The name and student ID of each team member and the name of the sub-system they modelled;
3. Snapshot of top-level InVision screen which links to the screen of each team member. To avoid confusion, assume that the system you are designing is available through a web browser. Fundamental principles of user-interface design (see your lecture notes and Satzinger, Jackson and Burd (2016), p. 223) should be followed when you design the screen. Your screen may be of any file type and be created in the software of your choice, but it must be possible to load it into and use it in InVision;
4. Link to the top-level InVision screen; and
5. Links for each team member’s InVision screens;
Task 2 - Individual work [80 marks]
You need to identify the subsystem you are working on, select two complicated use cases and then provide fully developed use case descriptions and activity and system sequence diagrams for both. Choose one of the 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, your fully developed use case might be incomplete: you must revisit your 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, you must revisit your use case to ensure that it is complete.
You have been given an example template - ITECH2002_Assignment2_TestPlan_Template – to help you complete your test plan.
The main part of the individual report document is expected to contain the following information:
1. The name of the sub-system you are modeling;
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 your 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 you. The use case chosen by you must be one of the two use cases selected in the previous step, step 2. Fundamental principles of user-interface design (see your lecture notes and Satzinger et. al. (2016), p. 223) should be followed when you design the screens. Your screens may be of any file type and be created in the software of your choice, but it must be possible to load them into and use them in InVision;
4. Link for your InVision screens;
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 design.
You need to follow best practices as far as modelling, interface design and testing are concerned. Satzinger et. al. (2016) and your lecture slides can help you with this.
Both the group and individual report should be professional in nature and follow the university guidelines specified later in this document in the Marking Criteria section.