Software Design Document Software Design Document Patient Information System Software Requirement Elicitation, Modelling and Design Document. Client: Traffic Accident Reporting System (TARS) Vendor:...

Please find two attached files


Software Design Document Software Design Document Patient Information System Software Requirement Elicitation, Modelling and Design Document. Client: Traffic Accident Reporting System (TARS) Vendor: Due Date: Week6 Friday 2020 11.45pm TABLE OF CONTENTS 1SYSTEM REQUIREMENTS2 1.1Functional requirements2 1.2Non-Functional requirements2 2SYSTEM ARCHITECTURE2 2.1Architectural Design2 2.2Use Case Diagram2 2.3Class Diagram2 2.4Sequence Diagrams2 3DATA DESIGN2 4INTERFACE DESIGN2 5REQUIREMENTS MATRIX2 6TEST PLAN2 SYSTEM REQUIREMENTS Functional requirements Non-Functional requirements SYSTEM ARCHITECTURE Architectural Design Use Case Diagram Class Diagram Sequence Diagrams DATA DESIGN INTERFACE DESIGN REQUIREMENTS MATRIX TEST PLAN 1 1 COIT12200, 2020 Term One - Page 1 of 4 Assessment item 1— Assignment 1 Due date: Friday of Week 6 (24th April 2020) 11.45 pm AEST Weighting: 20% Length: NA 1. Objectives The purpose of this assessment item is to assess your skills attributable to the following learning outcomes.  Apply software design and development principles  Complete appropriate documentation for requirements, system modelling and design, software implementation, testing and evolution  Illustrate a detailed design for a layered information system using appropriate design methods 2. Assessment Task Your task in this assessment is to analyse the given case study, understand the user requirements, and develop the necessary design and documentation for a Traffic Accident Reporting System (TARS) for Queensland Road and Transport Authority who is your client. You have to complete the requirements engineering and design of the system, keeping in view that in the next phase as part of your second Assessment you will be completing the implementation, and testing of the TARS System. 3. Case Study Queensland Road and Transport Authority (QRTA), as part of Queensland Government currently offers the road and transport services to the road users. This service is dedicated to collecting, storing, manipulating, and making available Road Accident Information important to the delivery of services to Queensland road users. Each motor vehicle will have a unique identifier (plate number) assigned by the system when registered for the first time. The QRTA wanted a flexible system with room for change in the future and prefer a layered design and implementation with the data stored in a database. The system is used by the QRTA staff to Create, Edit, Browse, Search on past road accidents in QLD. A View option should also be available to list all the accidents based on the "vehicle plate number" for reporting purposes. The system should also have the ability to update/change the vehicle owner information such as address or the phone number. Response to user actions must be reflected in the interface. The system should be developed as a Java desktop application which runs on a windows operating system with a graphical user interface. The Java application should be developed in a single tier using MVP (model view presenter) pattern. QRTA expects the system to be developed in two parts (Design and Implementation). The user updates the Vehicle information by interacting with the system. A Vehicle record consists of [id(plate number), model, year, owner name, owner address, owner phone number]. A sample record in database exists as ("124-QAY", "TOYOTA", 2018, ”Tom Jones”,"somewhere in Townsville", ”0467567356”). An accident record in database exist as [id(auto-generated), location, comments, vehicle id]. A sample record in database exists as (1, "intersection of Flinders and Ingham roads Townsville", "hitting an other car from behind", "124-QAY"), remember! an accident may involve multiple vehicles. Initial database script files will be provided. Sufficient error handling must be implemented to prevent data entry errors during database update and for the search option. The application when developed should automatically attempt to connect to the database before the user interface screen is displayed and exit with a message for a failed connection. When an accident is reported to the front desk, the system user must be able to check if the vehicle is already in the database and offer to update the information, if not then allow the user to add a new recored as a new vehicle and then add a new accident. The system must also allow user to add other vehicles to one accident. COIT12200, 2020 Term One - Page 3 of 4 4. ASSESSMENT COMPLETION GUIDELINES You should submit a report containing the following sections as listed below. 1. System Requirements Provide functional and non-functional system requirements. 2. System Architecture Provide a package diagram for the MVP design showing all the classes involved. 3. Use Case Diagrams Use UML to develop use case diagrams clearly showing the users (actors) and the main functions of the system 4. UML Class Diagrams Identify the classes based on the descriptions and the functions required. Show clearly public, private access and associations between classes. 5. Sequence Diagrams Provide two sequence diagrams with annotations for update and search operations. Develop the sequence diagrams clearly showing the user interactions and the different layers of the system. 6. Data Design Provide database table design with column names and types 7. GUI design Develop the GUI design based on the use cases and the sequence diagrams. You can be creative and only an indicative GUI is required. Developers are free to use this design as is or to do things differently. Note: You can use the NetBeans Forms to develop a GUI design. 8. Requirements Matrix Provide a table as below to maps requirement to action for each button and inputs required. Table II: Requirement Matrix Requirement Button Inputs Required 9. Test Plan Provide test use cases for update and search operations. COIT12200, 2020 Term One - Page 4 of 4 10. Template File Use the ‘Assignment1Template.dot’ file available from the Unit website under the Assessment folder for creating your report document file. Download the template and save it in your directory. Locate the file in your directory using File explorer and double click on it. This will create a document file named ‘document1’ by default. You can save it assigning the name you prefer and continue writing the report. 11. Report Submission You should submit only the word document using the Assignment 1 submission link available from the Unit website. 5. MARKING GUIDE