Anda di halaman 1dari 18

Object-Oriented Development

Life Cycle
(OODLC)
John Wiley & Sons, ISBN 0471371378
Topic 2 Week 2 Object-Oriented Application Development
1. The Life Cycle
2. The Object-Oriented Analysis Phase
3. The Object-Oriented Design Phase
4. The Construction Phase
5. The Object-Oriented Testing Phase
6. The Maintenance Phase
The Object-Oriented Development Life
Cycle
(OODLC)
The OODLC is
an update of
the older SDLC
The Life Cycle
Phase
Analysis
Design
Construction
Testing
Maintenance
Activity
OOA
OOD
OOP
O-O Testing
All of the above
Models
Produced

Requirements
Model
Design versions of
the 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
In Analysis we model the users requirements
For what the eventual system must DO.
Output of this process is a conceptual model
Consisting of 2 deliverables:
Requirements Model
Object Model
The Object-Oriented Analysis Phase
The Object-Oriented Analysis Phase
Requirements Model
The Requirements model has 5 components:
Project Scope
Context Diagram
Use Case Model
Interface Descriptions
Feasibility study
The Project Scope is a statement of what our project is
to produce.
States in general terms what the system will do for the users.
May be a paragraph or many pages, depending on the size of the
project.
There is much variation in size and format among
companies and methodologies.
The Object-Oriented Analysis Phase
Requirements Model
It is also important that the Scope says what the
system will not do,
Otherwise the users will try to push the
scope
Which causes Scope Creep
(uncontrolled changes or continuous
growth in a projects scope).
The Object-Oriented Analysis Phase
Requirements Model
The Context Diagram:
Shows our system as a large box,
Surrounded by smaller boxes,
Representing External Entities:
ie., People, organizations, systems and other things outside our
system that either provide data to it or draw data from it.
The Object-Oriented Analysis Phase
Requirements Model
The Object-Oriented Analysis Phase
Requirements Model
Context Diagram
Radio CHQT
Advertisers Database
System
Advertisers
Regulatory
Authorities
Revenue
Canada
Shareholders
Listeners
Business
Bureau
Requests
Billing
Statistics &
Reports
Program
Info
Credit
Ratings
Quarterl
y
Reports
Financial
Reports
A Use Case is a script,
A step-by-step description of how a user might make use of the
system
To do a task.
It is a case of the usage of the system.
The Object-Oriented Analysis Phase
Use Case Model
GUI (Abbreviated GUI (pronounced GOO-ee).
A program interface that takes advantage of
the computer's graphics capabilities to make the program
easier to use.)
Other software interface Systems
Real-World systems that we control
Communications interfaces
etc.
The Object-Oriented Analysis Phase
Interface Descriptions
Can we do this project?
Should we?
Can we make it work?
Is the cost worth it?
etc.
The Object-Oriented Analysis Phase
Feasibility Analysis
Modify Analysis model to reflect design decisions,
Mostly by adding information to the existing model.
Add some new classes that do not directly model things in the real
world.
Result is a plan of how the system will do what the
Requirements Analysis asks for
Object-Oriented Design Phase
Analysis is what the system
must do,

Design is how the system will
do it.
Analysis VS Design
Coding and testing
Should be done with an O-O language or database.
Deployment and user training.
The Construction Phase
First: unit testing of individual classes and programs
Second: system testing.
Testing must be thorough and complete,
And automated.
Object-Oriented Testing Phase
Bug fixes
Enhancements
Viruses
End-user computing
Backups and restores
Disaster preparedness and recovery
The World Trade Center bombing.
Murphys Law: Anything that can go wrong will go wrong.
The Maintenance Phase
References


Brown D.W, 2002, An Introduction to Object-Oriented Analysis;
Objects and UML in Plain English, Wiley, USA.

Anda mungkin juga menyukai