BN209 Software Engineering Group Assignment #2: Submission of the project Extended SRS Analysis and Design Document Submission Due: Week 11, 02 June 2017 @ 05:00 PM, online using the MOODLE system Total Marks: 100 marks, 25% of the total 100 marks Purpose of the assessment: The purpose of this assignment is to produce and submit a consolidated version of Extended SRS Analysis and Design Document for your project (i.e. the same project as you have used for Assignment #1). Description: 1. Students submit 'Extended SRS Analysis and Design Document' which contains the following design elements (using UML notations): • Assignment #1 Progression: SRS document updates according to the changes in your ongoing project • Identify all the actors use cases • Draw the use case diagram ((Entire system) • Fully develop use case description (Any 2 use cases) • Activity diagram (Any 2 scenarios) • Sequence diagram(s) (Any 2 scenarios) • Class diagram (Entire system) • Also, an up to date copy of the ‘Project Activity Journal’ where you show the weekly working of the group Team Submission guidelines: 1. This is a group assignment hence, only one member from a group will upload the ONE ZIP FILE on MOODLE. 2. Your report should include the following: • The cover page must identify team members’s (name and number), teaching staff, and assignment. • The assignment must use 12 point font size minimum and at least single line spacing with appropriate section headings. • The report must include executive summary, table of contents, introduction, Analysis/discussions (with heading/sub-headings to address the given requirements), conclusions and recommendations, references and appendices. • References and appendices  Reference sources (min. 6 references) must be cited in the appropriate section of the document  All cited references in IEEE style 3. The assignment must be submitted in soft (electronic) copy under MOODLE. The pages of the assignment must be clear on each page. Marking guidelines: Marks are allocated as follows: Item Mark 1 Assignment #1 Progression: SRS document updates according to the changes in your ongoing project 15 2 Identify all the actors and use cases 5 + 5 3 Draw the use case diagram ((Entire system) 10 4 Fully develop use case description (Any 2 use cases) 7.5 + 7.5 5 Activity diagram (Any 2 scenarios) 7.5 + 7.5 6 Sequence diagram(s) (Any 2 scenarios) 7.5 + 7.5 7 Design Class Diagram (Entire system) 10 8 An up to date copy of the ‘Project Activity Journal’ where you show the weekly working of the group 10 Total 100 Total (out of 25%) Marking Rubric for SRS document: Grade/Mark HD 80% -100% D 70%-79% C 60%-69% P 50%-59% Fail <50 Excellent Very Good Good Satisfactory Unsatisfactory Assignment #1 Progression: SRS document updates according to the changes in your ongoing project Update all the elements and diagrams according to the change in project Most of the elements and diagrams update according to the change in project Some elements and diagrams update according to the change in project No update of ambiguous changes not relating with project Poor, not acceptable All actors use cases All elements and diagrams are present and well designed Most elements and diagrams are present and well designed Some elements are missing or not properly designed OK, with some ambiguous shortcomings Poor, not acceptable Use Case Diagram (Entire System) All actors and use cases are defined accurately with proper notations All actors and use cases are defined partially with proper notations All actors and use cases are defined partially with wrong notations All actors and use cases are defined partially with wrong notations Poor, not acceptable Fully develop use case description (Any 2 use cases) Both use cases with all relevant elements definitions Both use cases with partial relevant elements definitions Both use cases with few partial relevant elements definitions Both use cases with ambiguous relevant elements definition Poor, not acceptable Activity diagrams (Any 2 scenarios) Both scenarios are relevant with proper defined activities definition Both scenarios are partial relevant with defined activities definition Both scenarios are relevant with few partial defined activities definition Both scenarios are ambiguous relevant with defined activities definition Poor, not acceptable Sequence diagram(s) (Any 2 scenarios) Both scenarios are relevant with proper defined sequence definition Both scenarios are partial relevant with proper defined sequence definition Both scenarios are partial relevant with few partial defined sequence definition Both scenarios are ambiguous defined sequence definition Poor, not acceptable Class diagram (Entire system) All classes are defined accurately with proper relationship notations All classes are defined partially with proper relationship notations All classes are defined partially with wrong relationship notations All classes are defined ambiguously with wrong relationship notations Poor, not acceptable Project Activity Journal Developed accurately with all group members participation Developed partially with all group members participation Developed partially with some group members participation Developed ambiguously Poor, not acceptable Presentation (In general and not graded) Excellent presentation, outstanding Significant effort Good effort made but not outstanding Made some effort, but only acceptable Poor, not acceptable Extensions: Requests for an extension will not normally be granted. A request, accompanied by supporting documentation, must be received in writing before 3 working days from the due date. Special consideration form is available on level 8 reception. An extension will be granted only for the extent of the period covered in the accompanying certificates. That is, if granted, a one-day illness will result in a one-day extension. Penalties may apply for late submissions without an approved extension. Penalties: Academic misconduct such as cheating and plagiarism will incur penalties ranging from a zero result to program exclusion.