ITSU2004 Systems Analysis & Design ITSU2004 Systems Analysis & Design Case Study Report NOTE: This Document is used in conjunction with Assessment [Research Report and Presentation] Case Study document [ITSU2004-CaseStudy.doc] ITSU2004 Systems Analysis & Design Objective(s) 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 Systems Analysis & Design using a simulated industry case study. INSTRUCTIONS Case Study Assignment - 30% (week 12) Group Assignment In this assignment students will work in small groups (maximum 4 members in a group) to develop components of the Software Specification and Design Documents discussed in lectures. Student groups should be formed by Session four. Carefully read the associated CASE STUDY for this assignment contained in the document ITSU2004- CaseStudy.doc From this Case Study you are to prepare the following: 1. Given the ITSU2004-CaseStudy.doc, what SDLC Model would you use to develop the associated software. You will need to justify your answer. Outline the advantages and disadvantages your SDLC model would have over other SDLC models that could be utilized in developing the software. 2. Discuss the techniques from the case study that you would use to gather the requirements 3. Specification Document a. System Description b. Requirements Specification i. Functional ii. Non-Functional c. Use Cases (from functional requirements) (at least 4 per group) i. Use Case Diagrams ii. Use Case Descriptions 4. Design Document a. Executive Summary b. Detailed Class Diagram c. Interface Design (at least 4 per group) i. Activity Diagrams d. Sequence 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 ITSU2004 Systems Analysis & Design 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 resubmit. 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 re-submissions 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. Assessment criteria Marks for Assessment will be allocated as follows: 1. Presentation (5%) ITSU2004 Systems Analysis & Design 2. Research Report (25%) The detailed description is as below: Topic Marks I. There is group presentation regarding this report, and it is mandatory for each member of the group to present (or viva) 5 II. Marks based upon report 25 1. SDLC 2. Requirements Technique 3. Specification Document a. System Description b. Requirements Specification i. Functional ii. Non-Functional c. Use Cases (from functional requirements) (at least 4 per group) i. Use Case Diagrams ii. Use Case Descriptions 4. Design Document a. Executive Summary b. Detailed Class Diagram c. Interface Design (at least 4 per group) i. Activity Diagrams d. Sequence Diagrams (at least 4 per group) 4 2 1 1 1 4 1 1 2 4 4