MITS5002 Assignment 3
Software Engineering Methodology
Case Study Assignment
NOTE: This Document is used in conjunction with MITS5002 Case Study document [MITS5002CaseStudy.doc]
This assessment item relates to the unit learning outcomes as in the unit descriptor. This assessment is designed to improve student collaborative skills in a team environment and to give students experience in constructing a range of documents as deliverables form different stages of the Software Engineering Process using a simulated industry case study
Case Study Assignment - 30% (week 13) Group Assignment
In this assignment students will work in small groups to develop components of the Software
Specification and Design Documents discussed in lectures. Student groups should be formed by Session four. Each group needs to complete the group participation form attached to the end of this document. Assignments will not be grades unless a group participation form is completed.
Carefully read the associated CASE STUDY for this assignment contained in the document MITS5002CaseStudy.doc
From this Case Study you are to prepare the following:
1. Specification Document
a. Executive Summary
b. System Description
d. Feasibility Analysis
e. Requirements Specification
i. Functional ii. Non-Functional
f. Assumptions/ Constraints
g. Use Cases (from functional requirements) (at least 4 per group)
i. Use Case Diagrams ii. Use Case Descriptions
h. Context Model
i. Levelled Set of Functional Models
2. Design Document
a. Executive Summary
b. Architectural Design
c. Hardware Specifications
d. Detailed Class Diagram
e. Interface Design (at least 4 per group)
i. Wireframe Diagrams
f. Business Process Models (utilizing BPMN 2.0) (at least 4 per group)
g. Sequence Diagrams (at least 4 per group)
h. Interaction Diagrams (at least 4 per group)
i. State Diagrams (at least 4 per group)
The above list of documents is not necessarily in any order. The chronological order we cover these topics in lectures is not meant to dictate the order in which you collate these into one coherent document for your assignment.
Your report must include a Title Page with the title of the Assignment and the name and ID numbers of all group members. A contents page showing page numbers and titles of all major sections of the report.
All Figures included must have captions and Figure numbers and be referenced within the document. Captions for figures placed below the figure, captions for tables placed above the table. Include a footer with the page number. Your report should use 1.5 spacing with a 12 point Times New Roman font. Include references where appropriate. Citation of sources is mandatory and must be in the Harvard style.
Only one submission is to be made per group. The group should select a member to submit the assignment by the due date and time. All members of the group will receive the same grade unless special arrangement is made due to group conflicts. Any conflict should be resolved by the group, but failing that, please contact your lecture who will then resolve any issues which may involve specific assignment of work tasks, or removal of group members.
What to Submit
All submissions are to be submitted through turn-it-in. Drop-boxes linked to turn-it-in will be set up in the Unit of Study Moodle account. Assignments not submitted through these drop-boxes will not be considered.
Submissions must be made by the due date and time (which will be in the session detailed above) and determined by your Unit coordinator. Submissions made after the due date and time will be penalized at the rate of 10% per day (including weekend days).
The turn-it-in similarity score will be used in determining the level if any of plagiarism. Turn-it-in will check conference web-sites, Journal articles, the Web and your own class member submissions for plagiarism. You can see your turn-it-in similarity score when you submit your assignment to the appropriate drop-box. If this is a concern you will have a chance to change your assignment and re-submit. However, re-submission is only allowed prior to the submission due date and time. After the due date and time have elapsed you cannot make resubmissions and you will have to live with the similarity score as there will be no chance for changing. Thus, plan early and submit early to take advantage of this feature. You can make multiple submissions, but please remember we only see the last submission, and the date and time you submitted will be taken from that submission
Please Note: All work is due by the due date and time. Late submissions will be penalized at the rate of 10% per day including weekends.
Group Participation Form
This form is to be completed by the group and returned to your tutor/lecturer as soon as possible.
We, the undersigned, agree to contribute individually and as a team to complete the Group Assignment for MITS5002 Software Engineering Methodology in the time specified. (It should be noted that failure to participate in a group may result in a fail for the assignment component of the subject.)
Surname First name Student ID Date Signature
1. ______________________ ___________________ __________ ___/___/___ _______________________
2. ______________________ ___________________ __________ ___/___/___ _______________________
3. ______________________ ___________________ __________ ___/___/____ _______________________
4. ______________________ ___________________ __________ ___/___/____ _______________________
* All members in the team will receive the same mark for an assignment, unless there are extenuating circumstances whereby an
individual’s mark has to be altered by the tutor/lecturer, or if the peer group assessment warrants it.
** Team members should contact their tutor/lecturer immediately if problems arise within the team that may cause completion of an assignment to be severely delayed, or the quality of the submission to be substantially lowered.