Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 1 of 8 Purpose and submission details The purpose of this assignment is to extend the work done in Assignment 1 to analyse and design the proposed library management system. In this assignment, students will work in groups of TWO students. Each group is to work together, distribute work equally and submit ONE group submission. The submission is to include an individual statement of contribution signed by each student that identifies who contributed to each part of the solution and which parts were completed together. Due date: Refer to the course description Submit the individual work via Moodle before the due date. Cutoff date: One week after the due date. Any submission after the due date will receive a deduction of 10% per day, this includes weekends. Marks: This assignment is worth 30% of the total assessment. Extensions: An extension will only be considered with supporting documentation from a health professional and if the problem/illness occurred within the week prior to the due date. If an extension is granted, the extension will then equal the number of days specified on the doctor's certificate, with the maximum limit of one week. Authorship: This assignment is a group assignment and it shall be completed by a group of TWO students only. The final submission must be identifiably the work of the group. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in the offending students being required to present before the Disciplinary Committee. Submission: Via Moodle.Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 2 of 8 Overview In assignment 1 students individually documented the requirements for the proposed library management system for a public library. Now students will work in a group of TWO students to extend the work from assignment 1 to perform system analysis and design tasks. Examine your assignment 1 submissions and, as a group, combine ideas from each member's case study completed in Assignment 1 to form a new case study. For your new case study, focus on all the components of your new system and perform the following structured and object-oriented analysis and design tasks in TWO analysis cycles toward the development of the proposed system. Cycle I: Events and Structured Analysis with Data Flow Diagrams A. Extract useful and relevant information about the scope of the system to be addressed from the case study and list all possible events to which the system must respond. Create event table entries listing the event, event type, trigger, source, activity/use case, response(s), and destination(s). An example of the layout for your answer is: Event Event Type Source Trigger Activity/Use case Response Destination B. Use all the understanding of the system you have so far from the case background (refer assignment 1), the events list and the draft scope document you prepared in Assignment 1 to construct the Context Diagram for the proposed library management system. C. In order to develop an appropriate Level 0 Data Flow Diagram, the list of business events should be examined for possible logical groupings (e.g., which events are closely related?). Logical groupings or associations of events can suggest subsystems or major processes that make up the system. Create the Level 0 Data Flow Diagram with 5-9 major processes for the proposed library management system. D. Draw Level 1 Data Flow Diagrams (child diagrams) by exploding major processes from your Level 0 DFD. Choose TWO different processes from the level 0 DFD and produce a detailed Data Flow analysis on each process. Cycle I Additional tasks for ITECH6101 Students E. Document the Data Structure for all data flows related to the TWO major processes chosen in Part D. Cycle II: Object Oriented Analysis and Design A. Create a Use Case Model for the complete overall system. B. Flow of events essentially documents the functionality of a use case, i.e., what the use case can do from an end-user's perspective. A scenario is an instance of a use case and it emphasizes howAssignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 3 of 8 a use case incorporates user activities as well as interactions of related objects. Hence it provides a basis for drawing Activity diagrams and Sequence diagrams. Choose ONE of the major use cases in your Use Case Model developed in Part A and develop the followings: i. A fully developed Use Case Scenario (description) with exception conditions for the chosen major use case. ii. An Activity Diagram for the chosen use case. C. Develop a System Sequence Diagram (SSD) for the complete overall system. D. Develop a Sequence Diagram (SD) for the major use case chosen in Part B. E. Create a Domain Model Class Diagram for the complete overall system. F. State chart diagrams are drawn to design and describe internal activity, or method logic, of system objects and to develop a further understanding of such processes and behaviour. Create a State chart Diagram for any ONE of the major objects in the proposed system. G. Design any TWO major reports required as output to the relevant personnel in the organization. Refer to the Event-Response table from part 1 as part of this task. Cycle II Additional tasks for ITECH6101 Students H. From your Use Case Model developed in Part A, chose another major use case (NOT chosen in Part B) and developed the following: i. A fully developed Use Case Scenario (description) with exception conditions. ii. An Activity Diagram for the chosen use case. iii. A Sequence Diagram (SD) Evidence of teamwork Note that this is a group assignment and good teamwork is ESSENTIAL. All tasks must be evenly distributed and assigned among group members. All completed tasks must be reviewed by all members. Marks to individual group members may vary if reported "lack of participation or involvement" by other members and the quality of individually assigned tasks varies in standard. Each group member's name must be shown with the diagrams/charts the group member has completed individually. Submission You are required to submit a pdf document in a formal report format (with school cover page attached) containing brief walkthrough/discussions of the diagrams/charts along with those diagrams/charts on or before the due date. You should use a CASE tool such as Enterprise Architect as appropriate. Note that all diagrams are to be drawn using appropriate conventions, preferably those used by Kendall and Kendall. All files, including the completed statement provided on the next page, should be ZIPPED and uploaded to Moodle. Your lecturer/tutor may have further instructions. Students are reminded to consult, prior to preparing their report, the General Guide for the Presentation of Academic Work available from the University website:Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 4 of 8 https://federation.edu.au/current-students/learning-and-study/online-help-with/study-skills-andwriting-guides Refer to the Course Description again for information concerning lateness, extension, special consideration, plagiarism and student support.Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 5 of 8 Statement of Contribution Student Name: _________________________________ Student Number: ____________________ I have individually prepared the solution for the following questions in the Assignment 2: - - - - - I have been involved in group collaboration, discussion and review of the following questions in the Assignment 2: - - - - - I feel that overall, my contribution to Assignment 2 would equal ____% of the total work submitted. The other member in my group was: Student Name: Student Number: Signature: _________________________________ Date: ___________________________Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 6 of 8 Marking Guide ITECH2101 ⃝ ITECH6101 ⃝ Student Name: _________________________________ Student ID: ______________________ Student Name: _________________________________ Student ID: ______________________ Marker: _______________________________________ Assessable tasks Max. Mark Mark Cycle I - Part A: Events Table for all possible events  Correct identification of maximum possible number of core events  All other associated information (Type of Events, Triggers, Activity/Use Case, Responses and Destinations)  Correct naming/language conventions. 10 Cycle I – Part B: Context Diagram for the overall system  Appropriate number of External Entities/Agents and Data Flows  Appropriate naming, numbering and drawing conventions 10 Cycle I – Part C: Level 0 DFD for the overall system  Appropriate number of Processes, Data Flows and Data Stores  Correct naming, numbering and drawing conventions  Level 0 appropriately balanced and made consistent 20 Cycle I – Part D: Level 1 DFD (For TWO selected processes)  More detailed with appropriate number of exploded Processes, relevant Data Flows, associated External Agents and Data Stores  Correct naming, numbering and drawing conventions 10 (2*5) Cycle I – Part E: Data structure (ITECH 6101 Students only) for all Data Flows related to the TWO DFDs created in Part D.  Complete and matches the DFD  Appropriately and clearly described  Use appropriate conventions 10 (2*5) Cycle II – Part A: Use Case Model for the overall system  Complete with correct Use Cases and Actors  Appropriate interactions  Correct use of naming and drawing conventions 10 Cycle II – Part B (i): Use Case Scenario for the selected Use Case  Fully developed including exception conditions  Correct use of conventions 5 Cycle II – Part B (ii): Activity Diagram for the selected Use Case  Appropriate identification and flow of activities, and consistent to the Use Case selected  Correct use of naming and drawing conventions 5 Cycle II – Part C: System Sequence Diagram (SSD) for the overall system  Correct SSD for the overall system 10Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 7 of 8  Appropriate actor(s) and messages identified in correct sequence  Correct use of naming and drawing conventions Cycle II – Part D: Sequence Diagram (SD) for the Use Case chosen in Part B  Correct SD for the selected Use Case  Appropriate objects, actors and messages identified in correct sequence  Correct use of naming and drawing conventions 5 Cycle II – Part E: Domain Model Class Diagram for the overall system  Appropriate number of Classes with attributes and some major methods  Appropriate multiplicities, associations including generalization/specialization  Correct naming/drawing conventions 10 Cycle II – Part F: State Chart Diagram for the selected object  Appropriate number of States, State Transitions, and paths – Independent/concurrent  Correct use of naming/drawing conventions 5 Cycle II – Part G: Report Design (for TWO selected reports)  Contains all appropriate information as required  Use of appropriate Printed Report design considerations including clear layout and formatting including appropriate headings 10 (2*5) Additional tasks for ITECH 6101 students only For another Use Case other than the one chosen in Part B: Cycle II – Part H (i): Use Case Scenario  Fully developed including exception conditions  Correct use of conventions Cycle II – Part H (ii): Activity Diagram  Appropriate identification and flow of activities, and consistent to the Use Case selected  Correct use of naming and drawing conventions Cycle II – Part H (iii): Sequence Diagram (SD)  Correct SD for the selected Use Case  Appropriate objects, actors and messages identified in correct sequence  Correct use of naming and drawing conventions 5 5 5 Overall Presentation Presentation of the document along with assumptions, and walkthroughs or discussions. 15 Total marks out of 125 (ITECH 2101) 125 Total marks out of 150 (ITECH 6101) 150 Total marks out of 30 30Assignment 2 School Engineering and Information Technology ITECH2101-6101 Software Engineering – Processes and Methods Page 8 of 8 Comments: