1 Executive Summary
This document is a proof of concept to designing a system for the case study of the Great Sydney Bike Club. The document contains a complete analysis of the functions of various subsystems which include the Online Subsystem, Onsite Subsystem and the Resource Management Subsystem.
The actor descriptions explain about the various live components that make up the GSBC system. These can include customers and staff, constructs such as Banks and the ATO and devices such as Printers and EFTPOS terminals.
The Use Cases explore how the actors will interact with each other and with the system. This can involve their roles such as making bookings, calculating tax or printing out documents.
The various UML diagrams such as the use case diagram, activity diagram, interaction overview diagram, sequence diagram and state machine diagram, assist with presenting the analysis done in this document. It will show how the various actors, use cases and interfaces will interactively participate in the running of the company.
Conceptual User Interfaces are used to illustrate the kind of design that analysis has found that will be beneficial in allowing the actors to interact with the system in an easy to use, understandable and simplified interface.
Operational Requirements show us a detailed explanation of various non-functional components not typically seen from the diagrams presented. These include performance, scalability of the system, volume of the data, bandwidth of the network, operating system and software and security requirements.
Project Management is a collection of the documentation used to support the working of the group, such as the project plan, time management and meeting minutes.
The purpose of this document is to report on the analysis of the Great Sydney Bike Club's current business and provide a comprehensive solution to the Great Sydney Bike Club.
The analysis of the business is documented using object oriented analysis techniques with Unified Modelling Language. With the use of UML, the team was able to translate the analysis of the system into understandable diagrams and descriptions. With proper modelling, all those that read this report will understand how the system will function and understand the requirements and the needs of the new system. Both functional requirements and non-functional (operational) requirements can be mined from the UML diagrams which will help designers with addressing the design of the system.
The analysis adopted an iterative and incremental process to constantly add and update the project report. This allows the project to have an evolutionary nature of development where elements can be created and recreated and allowed the development to be continually improved upon. The intention of this document the design of the system has the following qualities: consistency, correctness, validity, and adaptability.
The main audience of the document will the design and development teams that will work on implementing the GSBC system. They will need the analysis found in this report to realize the design. Some of the other audiences include the GSBC, who have asked for the analysis report to be taken and any other stakeholders with an interest in the company or with the design and implementation of the system not mentioned.
Case Study for Project Work
Great Sydney Bike Club - Problem Statement
1 Executive Summary
Provide a short section that summarises your project report in such a way that readers can rapidly become acquainted with all the main contents of your report without having to read it all.
2 Case Study for Project Work
• Following is a hypothetical problem statement for FantasticAsia Cuisine - a hypothetical restaurant chain.
• This problem statement is purposely kept incomplete requiring you to conduct detailed analysis and documentation to complete them
• You are welcome to modify this problem statement (with an agreement from your tutor).
• Each student should be allocated a package to work individually such as: online/onside food ordering, party/group-dining booking, stock/menu management, finance management, resources maintenance, and staff management. Package Emerging Technologies and other common sections should be done by all group members.
• If a group has fewer than four members, workload (i.e. number of individual packages) could be reduced correspondingly after consulting your tutor.
• Remove this instruction at the final report.
Attachment:- Project Template.rar