| Unit Name/Code | ISY3002/ISY302 IS Project 1 | |
| Assessment Number | 3 | |
| Assessment Name | Software Design Document | |
| Report and Presentation | ||
| Unit Learning Outcomes | ULO 1: Work effectively in a team to liaise with clients to determine systems requirements and elicit information necessary to create a software solution. ULO 2: Demonstrate an understanding of the roles and responsibilities of software developers, clients and users of a system software developers, clients and users of a system. |
Graduate Attributes Assessed |
| Communications Collaborations Research |
||
| Critical thinking & problem solving | ||
| Communications Critical Thinking & problem solving Ethical Behavior |
||
| Flexibility | ||
| ULO 3: Conduct a feasibility study that outlines costs, timeframes, a development schedule, and the features and benefits of a prospective software solution. ULO 4: Demonstrate skills in project planning and management, problem solving, analysis, and evaluation. ULO 5: Demonstrate skills in software design, development, implementation, testing and documentation of an authentic industry type project, that is, a less well-structured or messy problem, requiring demonstration of high-level skills. |
Communication Collaboration Research Critical Thinking & problem solving Ethical Behavior |
|
| Communication Collaboration Research |
||
| Critical thinking & problem solving | ||
| Ethical behaviour Communication Research Critical Thinking & problem solving Ethical Behavior Flexibility |
||
| Due Date and Time | ||
| Weighting | ||
| Assessment Description | ||
| Detailed Submission | ||
| Requirements | Report submission deadline is 12.06.2020 by 5 PM AEST. 40% (30% Report and 10% Presentation) A 4000 word Report on Software Design based on your Client’s project details. 15-minute Presentation in week 11 (08-02-2020) during class time by whole group. Report: This report is to be submitted in MS Word format. Upload the report via Moodle/Turnitin. Follow the instructions as required by this assessment brief. Presentation: All group members must give the presentation to get the marks. Zero marks will be given to the group member who does not give the presentation or who is absent on the presentation day. |
INSTRUCTIONS
Report: The word limit of the report is 4000. It should be written in size 12 Arial Font. You must submit your own work and
use appropriate references in Harvard style where needed. The similarity index of your report should not be more than 20%.
Draft report must be discussed with the instructor in the class on 06-02-2020 and 13-02-2020. All groups must bring a hard
copy of the Draft report for discussion.
Presentation: Maximum time allowed for presentation is 15 min. All group members must present the work to obtain marks.
Zero marks for being absent on the presentation day.
NATURE OF THE TASK
This is a group assessment. Please make groups of three students for this assessment.
HOW TO PRESENT YOUR ASSIGNMENT / SUBMISSION INSTRUCTIONS
Your report must follow the structure given below;
1. Executive Summary
• It should summarize the key points of the Software Design Document.
• 250-300 words
2. Introduction
Introduction has the following sections;
• Background of Project: Explain the aims, objectives and importance of the project.
• Purpose: Explain the purpose of the Software Design Document.
• Structure: Explain the structure of the Software Design Document.
3. Conceptual Model
This section has the following three components;
• Technologies used: Explain the various technologies that will be used by you in this project.
• System overview: Provide an overview of main functionalities of the system.
• Architectural Pattern: Explain the architectural design pattern (s) that will be used by you in
this project. Draw a block diagram of the software architecture.
4. Design Viewpoints
• Logical Viewpoint: Explain the logical viewpoint related to your project. Draw class diagrams to
explain the logical viewpoint.
• Information Viewpoint: Explain the information viewpoint related to your project. Draw Entity
Relationship (ER) diagrams to explain the Information viewpoint.
• Interface Viewpoint: Explain the various interfaces of the project. Provide screenshots of various
aspects of Front End of the software.
• Interaction Viewpoint: Explain the interaction viewpoint related to your project. Draw Sequence
Diagrams to explain the Interaction viewpoint.
5. Traceability Matrix
• Draw and explain the traceability matrix related to your project.
6. References
• In Harvard referencing style
7. Appendix (if needed)
• Programming code, screenshots, tables etc.
• Must be referred in the main body of the report.
RETENTION OF RECORDS
Students are required to keep a copy of all items submitted or completed for assessment or evaluation until the end of the grade
appeal period.
GROUP CONTRIBUTION FORM
You must submit the Group Contribution Form with the report. Group Contribution Form is given at the last page of this
assessment brief.
MARKING CRITERIA
See the rubric given at the next few pages.
| Assessment Rubric of Report | |||||
| Executive Summary and Introduction (6 marks) | |||||
| Executive Summary (3 marks) |
Clearly summarizes the key point of the Software Design Document (3 marks) |
Lacks in summarizing some key points of the Software Design Document (2 – 2.75 marks) |
Not clearly summarizes key points of the Software Design Document (1 – 1.75 marks) |
Poorly summarizes the key points of the Software Design Document (0.25 – 0.75 mark) |
Executive Summary is missing and not part of the report (0 marks) |
| Introduction (3 marks) |
Clearly describes the background of project, purpose and structure of Software Design Document (3 marks) |
Lacks some description of background of project, purpose and structure of Software Design Document (2 – 2.75 marks) |
Not clearly describes the background of project, purpose and structure of Software Design Document (1 – 1.75 marks) |
Poorly describes the background of project, purpose and structure of Software Design Document (0.25-0.75 marks) |
Introduction is missing and not part of the report (0 marks) |
| Conceptual Model (9 marks) | |||||
| Technologies Used (2 marks) |
Clearly explains the technologies that will be used in the Project (2 marks) |
Lacks some description of the technologies that will be used in the Project (1.5 -1.75 marks) |
Not clearly describes the technologies that will be used in the Project (1-1.25 marks) |
Poorly describes the technologies that will be used in the Project (0.25-0.75 marks) |
Technologies that will be used in the project are not written (0 marks) |
| System Overview (2 marks) |
Clearly explains the main functionalities of the system (2 marks) |
Lacks some description of the main functionalities of the system (1.5 -1.75 marks) |
Not clearly describes the main functionalities of the system (1-1.25 marks) |
Poorly describes the main functionalities of the system (0.25-0.75 marks) |
System Overview section is missing (0 marks) |
| Architecture Pattern (3 marks) |
Architectural Pattern is clearly explained (3 marks) |
Few aspects of Architectural Pattern are not clearly explained (2.25 – 2.75 marks) |
Many aspects of Architectural Pattern are not clearly explained (1.25 – 02 marks) |
Many aspects of Architectural Pattern are missing and are poorly explained (0.25 – 1 marks) |
Architectural pattern used is missing and not part of the report. (0 marks) |
| Block Diagram (2 marks) |
Block Diagram is clearly drawn (2 marks) |
Some aspects of Block Diagram are not clearly drawn (1.5-1.75 marks) |
Many aspects of Block Diagram are not clearly drawn (1-1.25 marks) |
Block Diagram is poorly drawn (0.25 – 0.75 marks) |
Block Diagram is missing (0 marks) |
| Design View Points (12 marks) | |||||
| Logical Viewpoint (3 marks) |
Class Diagrams are clearly drawn and explained (3 marks) |
Few class diagrams are not clearly drawn and/or not clearly explained (2 – 2.75 marks) |
Many class diagrams are missing and/or not clearly explained (1-1.75 marks) |
Many class diagrams are missing and poorly explained (0.25-0.75 marks) |
Logical Viewpoint section is missing and not part of the report (0 marks) |
| Information Viewpoint (3 marks) |
Entity Relationship (ER) diagrams are clearly drawn and explained (3 marks) |
Entity Relationship (ER) diagrams are not clearly drawn and/or not clearly explained (2 -2.75 marks) |
Many Entity Relationship (ER) diagrams are missing and/or not clearly explained (1-1.75 marks) |
Many Entity Relationship (ER) diagrams are missing and poorly explained (0.25 – 0.75 marks) |
Information Viewpoint section is missing and not part of the report (0 marks) |
| Interface Viewpoint (3 marks) |
All Interfaces are clearly explained and appropriate screenshots are provided (3 marks) |
Few interfaces are not clearly explained and/or appropriate screenshots are not provided (2-2.75 marks) |
Many interfaces are not clearly explained and/or appropriate screenshots are not provided (1-1.75 marks) |
Many interfaces are not clearly explained and appropriate screenshots are not provided (0.25 – 0.75 marks) |
Interface Viewpoint section is missing and not part of the report (0 marks) |
| Interaction Viewpoint (3 marks) |
Sequence diagrams are clearly drawn and explained (3 marks) |
Few Sequence diagrams are not clearly drawn and/or not clearly explained (2-2.75 marks) |
Many Sequence diagrams are missing and/or not clearly explained (1-1.75 marks) |
Many Sequence diagrams are missing and poorly explained (0.25-0.75 marks) |
Interaction Viewpoint section is missing and not part of the report (0 marks) |
| Traceability Matrix (3 marks) | |||||
| Traceability Matrix (3 marks) |
Traceability Matrix is clearly drawn and explained (3 marks) |
Few aspects of Traceability Matrix are not clearly drawn and/or not clearly explained (2-2.75 marks) |
Many aspects of Traceability Matrix are missing and/or not clearly explained (1-1.75 marks) |
Many aspects of Traceability Matrix are missing and poorly explained (0.25-0.75 marks) |
Traceability Matrix is missing and not part of the report (0 marks) |
Marking Criteria for the Oral Presentation
Assignment 3
| Task | Description | Maximum Marks |
Marks Obtained |
| 1 | Comprehensive introduction: – Introduced self – Introduced the project and its importance |
01 | |
| 2 | – Content – Delivery – Timing |
03 | |
| 3 | – Well-designed Slides – Readable/ Spellings/Grammar – Slides are numbered – References in Harvard Style |
03 | |
| 4 | Answers to Questions | 03 | |
| Total | 10 |
Group Contribution Form
| Unit Name/Code | ISY3002/ISY302 IS Project 1 |
| Assessment Number | 3 |
| Assessment Name | Software Design Document |
| Due Date and Time | Report submission deadline is 12.06.2020 by 5 PM AEST. |
| Instructions | • Report will not be marked without the submission of this form with the report. • This form should be completely filled. • This form should be signed by all group members. • Attach this form at the end of the report. • Do not upload it separately on the moodle. |
| Names of Student | Tasks Worked on | Percentage Contribution to Assessment e.g. If you have contributed equally then mention 33.33% contribution by each |
Signature |
| <insert student name> | <Insert tasks> | <Insert % > | <Insert signature here> |
| <insert student name> | <Insert tasks> | <Insert % > | <Insert signature here> |
| <insert student name> | <Insert tasks> | <Insert % > | <Insert signature here> |
| <insert student name> | <Insert tasks> | <Insert % > | <Insert signature here> |
The post Software Design Document appeared first on My Assignment Online.
