Assessment topic: Analysing and Modelling System requirements
Submission requirements details: Submit in Moodle through Turnitin by Sunday of Week 11, 11.59pm.
Task Details: Case Study
Case Study: Courier ASAP
Courier ASAP (CASAP) is a new courier company whose aim is to provide fast delivery with a secure
alternative compared to other available services. To meet its goal, CASAP is looking forward to an automated
system with an efficient and effective interface that can help the company do an online booking system for
customers to access the application from computers and mobile devices for necessary booking and monitoring.
This system will allow the customer to log in with their account for required booking and services, including
selecting pick-up and drop off based on their choice.
Through this system, courier agents should be able to allocate the job delivery agent for fast processing. In
addition, customers will be informed about the overall calculated cost and the approximate delivery date and
time.
This system must have the following features for a variety of users.
1. Customer Management operations (Creating, deleting, updating, searching for the customer)
2. Shipment Management operations (Checking for available delivery agents, Tracking detailed
information of shipment deliveries)
3. Payment processing functions (Processing customer payments, Issuing online receipts)
4. Login Management functions (Creating or removing system users)
5. Report Generation functions (Generating reports on shipments, delivery agent's details, customers etc.
You can also assume any possible functions necessary to function in this business case.
You may also add other possible functions and make necessary assumptions.
All assumptions need to be documented.
The report must contain at least the following sections
1. Introduction: Introduce the important aspects of the case study. (2 marks)
2. Methodologies: Briefly describe the System development Life Cycle (SDLC) and discuss different
approaches to SDLC. 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)
3. Information gathering techniques: Choose a suitable information gathering technique to gather specific
requirements and design at least 4 questions that can be asked from relevant stakeholders to capture
the system requirements. Also list all functional and non-functional requirements gathered from
different stakeholders and discussed in the case study (2 marks)
4. Use Case Diagram: Provide the name and complete description of a use case for the proposed system
and draw a use case diagram. (2 marks)
5. Activity Diagram: Provide an activity diagram for the use case identified above. (2 marks)
6. Sequence Diagram: Provide a sequence diagram related to the case study. (2 marks)
7. Domain Model Class Diagram: Provide the domain model class diagram for the proposed system. (2
marks)
8. User Interface: Provide a final user interface design using dialog and screen prototypes for any of the
use cases listed above. (2 marks)
9. Conclusion: Write a brief conclusion by clearly defining and describing the findings in your own words
related to the given case study (2 marks)
10. Structure and Formatting Guidelines (2 marks)