2021 Term-3 COIT11226 Assignment -2 (30%)
Due Date : Week-10 Tuesday (25th January 2022) 11am AEST
Weighting : 30%
Length : 1000 to 1500 words (word count includes all contents except the cover title
page, tables, diagrams, and references)
Objectives
This assessment is an individual assignment. In this assessment, you need to complete your assigned tasks and produce a professionally written, business report for submission. Your submission for this assessment should be in essay format, and it should follow the predetermined layout and required contents as stated in the Section -Layout of Your Report- (on following pages).
Your submitted report (in an MS Word document) will be checked by a computerized copy detection system (Turnitin) for copied and plagiarized work.
• Copying (plagiarism) can incur penalties ranging from deduction of marks to failing the unit or even exclusion from the University.
• Please ensure that you are familiar with the University's Plagiarism Policy (https://www.cqu.edu.au/student-life/ services-and-facilities/referencing/ what-is- plagiarism).
Requirements
Assessment 2 is based on the Project Case - UniSports Club - used in Assessment 1. In Assessment 1, you have presented your systems development project and the management has approved it. Now, you are required to: (a) Identify Functional and Non-Functional requirements, and (b) document the analysis results using various types of modeling diagrams.
Required Tasks in This Assignment
Complete the following tasks and document your work in your submission:
1. Identify Functional and Non-Functional requirements with brief justification for the new
Unisports Club’s automated information system (thereafter simply referred to as the
“new system”). Note that this new system to be developed should support all the business
operations at new system as described in the business case document.
2. After analyzing your collected information, produce the following UML diagrams for the new system:
(a) A Use Case Diagram: It should show all the “critical” use cases in the entire new system.
(b) A Domain Model Class Diagram: It should include all important classes needed in the entire new system.
(c) An Activity Diagram: You only need to draw an activity diagram for those tasks related to process “Submitting articles by the club members”. (One only)
(d) A System Sequence Diagram: You only need to draw one system sequence diagram for those tasks related to process “Submitting articles by the club members”. (One only)
Note that when developing each diagram, you may make some assumptions (e.g., related to the detailed operational workflow) to support your analysis of the new system. If this is the case, state your assumptions.
Layout of Report
Your report should be organized using the following headings and guidelines:
A “Separate” Cover Title Page
Should include your name, student ID, campus, tutor, and the word count of your report. If the word count of your report falls outside the range “1000 to 1500 words”, marks will be deducted from your submission.
An Introduction
Should clearly define the objectives of this report. Additionally, outline your major
findings in the Introduction.
Task 1 (Determining Requirements)
Identify Functional and Non-Functional requirements with brief justification for the new System.
Task 2
(UML Modeling Diagrams)
Assume that you have chosen the object-oriented (O-O) analysis approach for systems development. Draw the following four UML diagrams to capture users' requirements. Note that these diagrams should be drawn for the -new- system to be developed, not for the existing manual system.
A Use Case Diagram for the entire system.
A Domain Model Class Diagram for the entire system.
An Activity Diagram (Submitting articles by the club members)
A System Sequence Diagram (Submitting articles by the club members).
Each of the above diagrams should be accompanied with clear explanations and
assumption(s).
• You are -encouraged- to use Microsoft Visio to produce the above diagrams. However, this is not a mandatory requirement. You are allowed to use any other software tools to produce these diagrams. Note that hand-drawn diagrams are not acceptable.
Summary and Conclusion
• A summary of your findings. Also, your recommendation as to whether or not the project should continue, and if yes, how to continue.
References
• This section should include at least five references with their related in-text citations. The Harvard Referencing Style should be used.
Submission Requirements
You should submit only one file for your business report. All diagrams and tables should be included in your report. These diagrams and tables should not be submitted as separate files.
The file name of your submission should include your student ID for easy reference.
Marks for Assessment 2 will be allocated as follows:
Items Mark Result
Introduction
- Define the objectives of the report
- Outline all major findings of the report
5
5
Task 1: Functional & Non Functional requirements
- Functional requirements for UniSports Club System.
- Non Functional requirements UniSports Club System.
10
10
Task 2: A Use Case Diagram (for the entire new system)
• Well explained & well justified 10
4
A Domain Model Class Diagram (for the entire new system)
• Well explained & well justified 10
4
An Activity Diagram
• Well explained & well justified 10
4
A System Sequence Diagram
• Well explained & well justified 10
4
Summary and Conclusion
A summary of your findings
Recommend whether or not the project should continue/how to
continue
5
5
References (at least five references with related in-text citations; follows Harvard Citation Style) 4
Total 100
Assessment mark will be weighted to 30%.