creating uml diagrams accrording to the case study
Assignment 2 Case Study: Expert courier company (ECC) is a newly created courier service company whose aim is to serve customers with the courier services that offer a faster and more secure alternative to the usual mail service. To achieve their goal, ECC has considered developing an automated system using an efficient and user-friendly interface with an online booking system that would enable their customers to access the system from their computers as well as mobile devices and to book for their courier services. The system should allow the customers to log into their own account and book the services. They need to be able to enter the pick-up and drop off office location of their choice. The system should be able to allocate the job to the available delivery agent for fast processing and send the relevant information to the customer along with the details of calculated cost as well as the approximate delivery date and time. Overall the system is required to have the following features for a variety of users. • Customer Management operations (Creating, deleting, updating, searching customer) • Shipment Management operations (Checking for available delivery agents, Tracking detailed information of shipment deliveries) • Payment processing functions (Processing customer payments, Issuing online receipts) • Login Management functions (Creating or removing system users) • Report Generation functionalities (Generating reports of shipments, delivery agents, customers etc. You may also add other possible functions that you deem necessary to function in this business case. The report must contain at least the following sections 1. Structure and Formatting Guidelines (2 marks) a. Add a title/cover page of your choice at the beginning of the report. It should include the name of the assessment, subject name, student’s name, and student ID. b. Insert a table of content next to the title page. c. Insert the page number within the footer of every page in your report. d. Provide appropriate referencing(Harvard-Style) for all academic resources used e. Submit your file using the format: YourNameID_ICT103_Assignment2.docx 2. Introduction: Introduce the important aspects of the case study. (2 marks) 3. Methodologies: Briefly describe the System development Life Cycle (SDLC) and discuss the predictive and adaptive approaches to SDLC, evaluate the usefulness and limitation of each approach as well. (2 marks) 4. Chosen methodology: You are then required to choose one model that you find suitable for the system given in the case study and justify your choice. (2 marks) 5. Requirement Gathering: Identify at least two information gathering techniques that can be used to gather specific requirements and design at least 6 questions that can be asked from relevant stakeholders to capture the system requirements and specifications to develop the system successfully. (2 marks) 6. Requirements: List all functional and non-functional requirements as discussed in the case study. (3 marks) 7. Requirement Modelling: Based on the outcome of your requirement analysis carried above, provide an activity diagram for any use case to provide a graphical illustration of the new system and make sure that accurate technical language has been applied. (2 marks) Marking Rubric for Assignment 2 Individual Report: Criteria Fail (0 – 49%) Pass (50 – 64%) Credit (65 – 74%) Distinction (75 – 84%) High Distinction (85 – 100%) Structure and format 2 marks Very difficult to read, unclear structure, and most of the required sections are missing Some difficulty in reading, not very clear, but important sections are included Clear and readable, and all required sections are included Well written and very clear, and all required sections with completed discussion are included Well written and very clear, all required sections with completed discussion are included, and additional sections have been added for clarity Introduction 2 marks No introduction given or most of the introduction is irrelevant Introduction of the business case is provided with some details and limited cohesion Introduction of the business case is provided with most of the required details in a cohesive manner Introduction of the business case is provided with all of the required details in a comprehensive and cohesive manner Introduction of the business case is provided with all details presented systematically in a comprehensive and cohesive manner Methodologies 2 marks Methodologies are not given or most of the discussion is irrelevant Methodologies are provided with some details and limited cohesion Methodologies are provided with most of the required details in a cohesive manner Methodologies are provided with all of the required details in a comprehensive and cohesive manner Methodologies are provided with all details presented systematically in a comprehensive and cohesive manner Chosen methodology 2 marks No methodology chosen or completely irrelevant choice given, no support for the position taken in the justification, or a wrong argument is given A methodology is chosen but not the most effective, biased/irrelevant support for the position taken in the justification Effective methodology is chosen with limited details and ambiguous relevance, basic level of support for the position taken in the justification Effective and relevant methodology is chosen with nearly all required details, good level of support for the position taken in the justification Effective and relevant methodology is chosen with complete required details, exceptional level of support for the position taken in the justification Requirement gathering 2 marks No or mostly irrelevant requirements gathering techniques are identified Requirements gathering techniques are provided with some details and limited cohesion Requirements gathering techniques are provided with most of the required details in a cohesive manner Requirements gathering techniques are provided with all of the required details in a comprehensive and cohesive manner Requirements gathering techniques are provided with all details presented systematically in a comprehensive and cohesive manner Requirements 3 marks No or mostly irrelevant requirements are identified Some of the requirements are identified Most of the requirements are identified Nearly all of the requirements are identified All of the requirements are identified Requirement modelling 2 marks Does not provide any required diagram or irrelevant diagrams are provided Only some of the required diagrams are provided and all diagrams are incomplete Most of the required diagrams are provided and some diagrams are complete Nearly all of the required diagrams are provided and the diagrams are complete All of the required diagrams are provided and all diagrams are complete Total mark out of 15 ICT103 Assessment 2 Digrams This file shows the example of the diagrams you need to prepare for 1. Use Cases: • Use case— an activity that the system performs, usually in response to a request by a user. Use cases define functional requirements. • Use case diagram— a UML model used to graphically show uses cases and their relationships to actors. Use Case Diagrams Symbols Use Case Example 2. Activity Diagram: Activity Diagram– describes user (or system) activities, the person who does each activity, and the sequential flow of these activities a. Useful for showing a graphical model of a workflow b. A UML diagram Activity Diagram Symbols Activity Diagram Example 3. Sequence Diagrams: • A UML sequence diagram • Special case for a sequence diagram • Only shows actor and one object • The one object represents the complete system • Shows input & output messaging requirements for a use case • Actor, System, object lifeline • Messages System Sequence Diagram (SSD) Notation: System Sequence Diagram (SSD) Examples: 4. Domain Model Class Diagram: • Class • A type of classification used to describe a collection of objects • Domain Class • Classes that describe objects in the problem domain • Class Diagram • A UML diagram that shows classes with attributes and associations (plus methods if it models software classes) • Domain Model Class Diagram • A class diagram that only includes classes from the problem domain, not software classes so no methods Domain Model Class Diagram Notation Domain Model Class Diagram Examples 5. State Machine Diagram: • State Machine Diagram – a diagram which shows the life of an object in states and transitions • Origin state – the original state of an object before it begins a transition • Destination state – the state to which an object moves after completing a transition • pseudostate – the starting point in a state machine diagram. Noted by a black circle. • action-expression – some activity that must be completed as part of a transition • guard-condition – a true/false test to see whether a transition can fire 5. User Interface: • User interface design must consider the entire user experience • Good user interfaces are based on good design principles – visibility, affordance, feedback, etc. • Poorly designed user interface can make the information system unusable • Story boards are a powerful tool for UI design • User Interface – inputs and outputs that directly involve a human user/actor • A dialog goes on between actor and system • User interface design must focus on entire User Experience (Human Computer Interaction –HCI) • Called User-Centered Design • Focus early on users and their work • Evaluate designs to ensure usability • Use iterative