Object Orientated Analysis Major Group Project

3 Found helpful • 195 Pages • Essays / Projects • Year: Pre-2021

This document serves as a full documentation for the Fast Pizza Management System. Based on this Fast Pizza scenario given and also included in this document, a full analysis and report was made. A HD mark was awarded to my group for this report. The content of this document is divided into major chapters. Chapter2 Introduction describes the purpose of the document and also introduces some terms that would help us reading of the actual document. Chapter 3 is simply the actual narrative that we analyse for the creation of FPMS. From this document, we manage to extract what is the current system, the requirements and demands of the company for the development of the new system. Chapter 4 Vision and Scope chapter describes the conditions that drive the analysis and development of FPMS. It is broken into few points namely; the Background, Possible Solution and Recommended Solution, Feasibility Assessment and Scope and Limitation. The background is the narrative of what we have extracted from the case study which gives us a brief problem statement, what will the new system they need do, the benefits they wanted to realise and also states the deliverables they are expecting in doing the project. The Possible Solution and Recommendation; as the heading suggests provides an overview of the alternative solutions for the problem and the recommended solution that the team pursued. The Feasibility Assessment point; simply describes few factors that actually supported the given recommendation. The final point in this chapter is the Scope and Limitation; which sets out the boundary of the project, states the scope (current and future), constraints and limitation, and also specifies the assumptions made that helped the team in analysing the project and leading into a solution. Chapter 5 System Overview and Description chapter gives us an idea about the recommended solution or the new system that the team will develop. This chapter is broken into two main areas namely; Solution Overview and Functional Requirements. The Solution Overview area states the vision statement of the project, the high level requirement of the new system and the overall description of the recommended system. The Overall Description part of this chapter is divided into System Perspective and User Characteristics. The System Perspective gives us a better understanding of what considerations are necessary and what are addressed for the new system; like interfaces, memory, operations and adaptation requirement for the system. Furthermore, the User Characteristics describes what kind of users will be using the new system. The Functional Requirement on the other hand, clearly defines the detailed requirements of the new system based on the high level requirement set out in the project. Chapter 6 to Chapter 16 covers how the requirement of the system are handled using UML. These chapters show us the package diagram, actors list and its documentation, Fast-Pizza Management System 2010: OOA Project Report <> Page:
9 of 195 use cases, use case diagrams, activity diagrams, class descriptions, class diagrams, interaction overview diagrams, sequence diagrams, state machine diagrams and prototypes. By going through these chapters; we will deeply understand the solution to the project. Chapter 17 Operational (Non-Functional) Requirement; gives us a detailed operational requirement which includes performance, scalability, security, volume, bandwidth, os and maintenance factors. Chapter 18 Environment Considerations will just describe what kind of system environment will be used for the new system. Chapter 19 and Chapter 20 mainly describe Testing Plan and Testing Design conducted for the project. Chapter 21 Project Management is the chapter that simply collates the all the supporting document that help us in the conducting the project. The Project Plan, Project Time Management and the minutes of the meetings

This document is 10 Exchange Credits