Identify all the use cases mentioned in the system description and draw a use case diagram, with all use case relationships. It has an expected workload of 8 hours for each group member. There can be approximately 15-20 use cases selected from this system description.
Marking Criteria:
Suitable Use Cases/Actors/Links: 6
Include/Extend/Generalization relationships: 4
4.2 Week 5, 11/12 April (5 marks)
Use Case Descriptions (Objectives 1 to 6)
Describe 3 use cases using the format described in the lecture notes, showing all details for each use case; describe any included or extended tasks that are required by the stated use cases. It has an expected workload of 3-4 hours for each group member. Each use case should require at most 3 pages of text, and some may take less than one page.
Marking Criteria:
Preamble: 1.5
Mainline:2 Extensions: 1.5
4.3 Week 8, 9/10 May (10 marks)
Class Diagram (Objectives 1 to 6)
Design a design class diagram which shows, for each class in the system, the class name and attributes, plus the class associations, multiplicities and operations. Include any inheritance, composition or aggregation relations. It has an expected workload of 15 hours for each group member.
Marking Criteria:
Suitable Classes: 2.5
Suitable attributes and types: 2.5
Appropriate Associations: 2.5
Suitable Operations: 2.5
4.4 Week 8, 9/10 May (5 marks)
Sequence Diagram (Objectives 1 to 6)
Draw 3 sequence diagram which show all messages (method calls) between classes, including any parameters, and any value returned from a method call. It shows object selection, iteration, and object creation and / or destruction. It has an expected workload of 5 hours for each group member.
Marking Criteria:
Appropriate Control Flow: 3
Correct Notation: 2
4 of 7
4.5 Week 12, 6/7 June (10 marks)
Java Code (Objectives 1 to 6)
Write Java code for 3 methods of any one class or different classes in the class diagram. It has an expected workload of 5 hours for each group member.
Marking Criteria:
Reasonable method logic: 3
Specific correct parameters: 2
Executable code: 5
4.6 Week 12, 6/7 June (5 marks)
User Interface Design (Objectives 1 to 6)
Each group has to design user interface for three methods’ data input and output. The design consists of a set of screen layouts that define the data input to and displayed on each screen. It has an expected workload of 5 hour for each group member.
Marking Criteria:
Appropriate Screen Layout: 2.5
Executable input/output: 2.5
4.7 Week 12, 6/7 June (5 marks)
Connection to Database (Objectives 1 to 6)
Connect one class or entity to MySQL database. Apply or show CRUD operations on one or two objects.
Marking Criteria:
Appropriate Code: 2.5
Executable code: 2.5
5. Group and individual marks
The assignment is done in groups of three. When you hand in the final part of the assignment, you must rate each member of the group on how much that person has contributed to the overall mark; the form is included at the end of this document. The contribution of each team member is written on the form, and each person signs the form. The individual mark is the team mark weighted by the individual contribution. You must fill in and sign the form; if you do not, then your assignment mark will be zero. Any group experiencing problems that cannot be resolved within the group should contact the Subject Coordinator as soon as possible. In extreme cases, the Subject Coordinator may withdraw a problem student from a group. That student must then find another group, or work alone. No complaints will be heard after the submission date.
6. Academic Conduct
The solution should be the original work of the members of your team. No collaboration is allowed with any other person. You are not permitted to discuss your solution with, or show it to, any student outside your team. The Faculty penalty for proven and serial misconduct of this nature is zero marks for the subject, as stated on the Subject Outline.
5 of 7
7. Assignment Submission and Return
You build a system specification by delivering seven documents, where each document builds on the previous one; the timing and deliverables are described in section 4. For each part
• hand in a hard copy of the assignment to the tutor at the start of the Laboratory
• submit a soft copy of the assignment on UTSOnline.
• the marked assignment is returned two week later in the Laboratory
• No late submission is accepted. Failure to submit assignment on time will result in penalty (10% of marks obtained will be deducted per day).
8. Special Consideration
Special cases are to be discussed and considered by the subject coordinator. If any student’s performance in an assessment item or items has been affected by extenuating or special circumstances beyond his/her control (work problems, family problems, or health problems), then he/she may apply for Special Consideration. If you are requesting an extension of time of one week or less to submit an assignment you should contact your subject coordinator, do not formally apply for special consideration.
9. Minimum Requirements
In order to