Paper, Order, or Assignment Requirements
Module Intended Learning Outcomes
On successful completion of this module you will be able to:
Knowledge and understanding 1. Understand theories and concepts of object oriented analysis and design methodology
2. Appreciate the strengths of OOAD methodology
Intellectual, practical, affectiveand transferable skills 3. Apply object oriented techniques, tools and methods to analyse and design a solution to a given problem.
4. Use correct UML notations to produce models and designs
5. Evaluate UML designs
l Microsoft Visio or equivalent CASE tools should be used for drawing all models and diagrams.
l Diagrams will be marked for consistency throughout the models. Each of the models should be accompanied by textual descriptions which may include the purpose of the model, analysis and design notes, assumptions and considerations for the model.
l This assignment should be completed individually. Plagiarism will be penalized according to university regulations.
l Hand-in Dates are stipulated in the Module Guides. Both reports should be submitted to TurnitinGradeMarkSystem before 2pm of the submission date. Please refer to the Module Guide for detailed regulations regarding late submissions and how feedback will be distributed after marking.
l Note that this is Assignment 1 with two parts: Analysis Report and Design Report. Assignment 2 will be published in a separate document.Proper documentation of your assignment will also be rewarded extra points (see the Marking Schemes). Therefore, make sure that your documentation skills are up to the standard required.
Based on the following Problem Statement you are required to produce:
Part I. Analysis Report (40%)
For this part you should focus on the analysis of the business needs, the structure of the system and the functionalities that should be built into the system in order to meet the business requirements.
1. A set of use case diagrams for the system with
a. An overview use case model (both description and diagram); 4%
b. Detailed use case models (both description and diagram) for major business processes. 8%
2. Two activity diagrams to model two major business processes in the system. 10%
3. A class model for the whole system showing important / major classes in the system with their basic attributes and methods. 10%
4. A deployment model to show how components of the system are to be installed on completion of the product. 8%
Part II. Design Report (60%)
For this part you are required to designthe implementation details of the functionalities andthe structure of the system, based on the analysis report in Part One. Also, you are expected to produce behavioural models for the classes involved in the system.
1. A detailed design of the class model for the system with implementation details. 12%
2. An object model describing capturing how classes (minimum of 3) collaborate with each other in completing a chosen business process (possibly one of the major processes in Task 1b), with a diagram (part of the class diagram from Task 3). 8%
3. Two communication diagrams to show the detailed collaboration and the interaction between classes in performing a chosen use case (different from Task 2, with a minimum of two classes involved. 12%
4. Two sequence diagrams for modellingtwo differentuse cases from any tasks above. 12%
5. Twobehaviour state machine diagrams for capturing all possible states of two major classes in the system. 8%
6. Evaluate your designs against object-oriented system analysis and design principles in the context of business requirements of the case study. 8%
A Web-based Car Sharing System
Car sharing is becoming increasingly popular in the UK and other European countries. It not only reduces the cost of travelling but also lowers your carbon footprint. There are already many interactive websites on the Internet for people to use. More information about benefits of car sharing is available on
The following describes the business processes involved inatypical web-based Car Sharing System although you may find variations. Your designs should be strictly based on the information provided in the Case Study. You can make your some assumptions for the missing information as long as they are within reason, appropriately explained and justified. The following websites are indicated below for your reference so you will understand how the system works.