PROJECT DESCRIPTION
it will include UML diagram, tables, group task, individual task,
1. The name of the sub-system you 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
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
In group task
The main part of the group report document is expected to contain the following information:
1. The name of the organisation you are modelling;
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;