Date post: | 17-Nov-2015 |
Category: |
Documents |
Upload: | aiyas-aboobakar |
View: | 8 times |
Download: | 4 times |
CT015-3.5-2 Design Methods
Object Oriented Life Cycle
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Module objectives
After completing this module, you will be able to: Explain Object-Oriented Life Cycle Understand Analysis and Design, Construction,
Testing and Maintenance phases
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Outline
The Life Cycle The Object-Oriented Analysis Phase The Object-Oriented Design Phase The Construction Phase The Object-Oriented Testing Phase The Maintenance Phase
CT015-3.5-2 Design Methods Object Oriented Life Cycle
The Life Cycle
The OODLC is an update of the older SDLC
CT015-3.5-2 Design Methods Object Oriented Life Cycle
The Life CyclePhase
Analysis
Design
Construction
Testing
Maintenance
Activity
OOA
OOD
OOP
O-O Testing
All of the above
ModelsProduced
RequirementsModel
Design versions ofthe OO models
Actual system
Working system
All of the above
Components
Project scope
Feasibility study
Context diagram
Class diagram:
Entity classes
Interface classes
Control classes
Behavior diagrams:
Statechart diagrams
Collaborations and CRC cards
Sequence diagrams
Activity diagrams
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Object Oriented Analysis Phase
model the users requirements
what the final system must PERFORM. Output: Conceptual Model. Consisting of 2 deliverables:
Requirements Model Object Model
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Requirement Model
The Requirements model has 5 components:1. Project Scope2. Context Diagram 3. Use Case Model 4. Interface Descriptions 5. Feasibility study
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Requirement Model
Project Scope is a statement of what our project is to produce.
States in general terms what the system will do for the users.
Also say what the system will not do
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Requirement Model
Context diagram defines the boundarybetween the system, or part of a system, and its environment, showing the entitiesthat interact with it.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Use Case Model
It is a case of the usage of the system.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Interface Description
GUI Other I.S. Systems Real-World systems that we control Communications interfaces etc.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
OOA: Feasibility Study
Can we do this project? Should we? Can we make it work? Is the cost worth it? etc.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Object Oriented Design Phase
Modify Analysis model to reflect design decisions by mostly adding information to the existing model.
plan of how the system will do what the Requirements Analysis asks for.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Object Oriented Design Phase
Analysis is what the system must do,
Design is how the system will do it.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Construction Phase
Coding and testing. Should be done with an O-O language or
database.
Deployment and user training.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Object Oriented Testing Phase
Complete the unit testing of individual classes and programs
Then system testing. Testing must be thorough and
complete.
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Maintenance Phase
Bug fixes Enhancements Viruses End-user computing Backups and restores Disaster preparedness and recovery
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Review
Object-Oriented Life Cycle Analysis and Design, Construction,
Testing and Maintenance phases
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Further information
COMET: A UML-Based Software Design Method for Single Systems
http://www.informit.com/articles/article.aspx?p=349038&seqNum=7
CT015-3.5-2 Design Methods Object Oriented Life Cycle
Q & A