Dynamic Modelling, Screen Design and
1. TIMELINES AND EXPECTATIONS
Due date: Monday, Week 11, 11:55pm Weighting: 30%, maximum mark: 30.
Minimum time expectation: 40 hours.
You will be working with your team member(s) from assignment 1.
Your assignment will be assessed by your tutor or lecturer if your lecturer is also your tutor. You will receive your mark and written feedback via Moodle two weeks after the due date or submission, whichever is later.
In this assignment you will model the behaviour of systems or subsystems for two of your most complex use cases using two UML diagrams (activity diagram and system sequence diagram) and write the extended use case description. You must also submit test plans and screens developed using InVision.
Section 3 describes the motivation behind the design of this assignment. Section 4 provides information on how and what to submit (note that Moodle has been setup so there is only one submission from each group). Section 5 explains the tasks for individual and group work. You will find the criteria for marking your submission in Section 6.
The purpose of the assignment is to ensure that you know:
1. How to write extended use case texts.
2. How to model the dynamic aspect of a system using UML (activity diagram and system sequence diagram).
3. How to develop screen prototypes to assist analysis.
4. How to develop quality test plans. The assignment addresses the following learning outcomes:
K1. Explain how models are used to assist in analysing and modifying existing business systems;
K2. Define various roles involved in the processes of system analysis;
K3. Describe techniques used to gather required information for system analysis;
K4. Explain the various stages of the system development life cycle;
S1. Identify appropriate models for given scenarios;
S2. Develop various models using a professional CASE tool;
S4. Perform Object Oriented Analysis and Design to construct various object models used to communicate the scope and requirements of the project.
A1. Write integrated reports, using appropriate models, providing detailed analysis of given textual scenarios.
4. HOW AND WHAT TO SUBMIT
1. Create a document in OneDrive and share it with your team members.
2. This assignment has eight tasks (see Section 6), and there are two types of submissions:
a. Group submission. Submit tasks 1 to 6 and 8 as a single report.
Submit your document via Moodle Shell. Moodle has been set up so each group submits only one document. You need to submit the group report in .docx or .odt or .pdf.
Please nominate a team member to submit. You need to submit only one document for the whole group. If you submit only your own work, you will lose all the group marks.
b. Individual submission. Submit constructive reflection (task 7) individually.
3. Plagiarism. Your submission will be checked by Turnitin, a plagiarism detection system. Students suspected of plagiarism will face disciplinary actions. Copying or allowing your work to be copied (including uploading your assessment to StuDoc or something similar) constitute plagiarism.
4. Working in groups can be challenging but being able to work in groups is a highly valuable skill. Please see the tips on Moodle Shell – “Groupwork Online” on top of the shell for successful group work.
As a general guide to how the document should look, think about your target audience, which in this case is another system analyst and a quality assurance (QA) team who will work with the system. Remember that everyone is busy and overloaded with information, so please include only the most essential information: be brief but clear. The QA team will use the test plans to develop automated system tests.
5. ASSESSMENT DETAIL
This assignment has group work and individual work components. The following sections describe the tasks for the individual and group work.
Task A - Individual work [29 marks]
No Description Reference
1 Plain English description of two processes
Find two of the most complex use cases you have submitted in
assignment one. For each use case, describe the process for each use case in plain English as in Tutorial Six.
Week 6 tutorial
2 Two extended use case descriptions.
Develop extended use case descriptions of the two use cases from task 1 above. Week 6 tutorial
3 Activity diagrams for the two use cases from task 2 above.
Each activity diagram must have at least one decision making, parallelism or loop. If the diagram has no such features your extended use case might be incomplete: you must revisit your use case to ensure that it is complete. Week 6 slides and tutorial
4 System sequence diagrams (SSD) for the two use cases from task 2 above.
Each SSD must have at least one of the following: a loop, optional or alternate frames. If the diagram has no such frame or loop, then you must revisit your use case to ensure that it is complete. Week 6 slides and tutorial
5 Test Plan.
Develop a test plan for one of the use cases selected for task 4 above. Week 7 slides
6 Screen prototype using Invision.
Use Invision to develop the screen prototype for the use case selected for task 5 above. Week 8 lab
7 Constructive reflection (TO BE SUBMITTED INDIVIDUALLY) Week 5 slides
Use Gibbs’ Reflective Cycle, as taught in Week 5, to reflect on your experience in working on this assignment. Please review if your action plan developed in assignment 1 has helped you in the second assignment.
Task B - Group work [1 mark]
8 Consolidated Group Report.
Consolidate all three subsystems into one report: the plain English description of the use cases, extended use case descriptions, activity diagrams, SSDs, the filenames of the Invision screens and test plans. The report must have a title, all three subsystems and the student responsible for the subsystem.
6. MARKING RUBRIC
End of Assignment Two Specification