Scribd
Upload
78 views4 pages

01 Introduction To OOAD

This document provides an overview of software development approaches and artifacts. It discusses the software lifecycle process and common artifacts like requirements, design documentation, source code, and test cases. It then contrasts the structured and object-oriented development approaches. The structured approach uses top-down design but has weaknesses around reuse and changing requirements. The object-oriented approach models the system as collaborating objects, which allows for reusable components and easier maintenance. The document concludes by mentioning object-oriented analysis and design, which involve analyzing requirements and designing the system architecture respectively.

Uploaded by

Nichupan Pratheeprat
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
78 views4 pages

01 Introduction To OOAD

This document provides an overview of software development approaches and artifacts. It discusses the software lifecycle process and common artifacts like requirements, design documentation, source code, and test cases. It then contrasts the structured and object-oriented development approaches. The structured approach uses top-down design but has weaknesses around reuse and changing requirements. The object-oriented approach models the system as collaborating objects, which allows for reusable components and easier maintenance. The document concludes by mentioning object-oriented analysis and design, which involve analyzing requirements and designing the system architecture respectively.

Uploaded by

Nichupan Pratheeprat
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Agenda

• Software Lifecycle Process
• Software Artifact
Software Artifact
Introduction to OOAD • Software Development Approaches
• What’s Next

Software Lifecycle Process


Software Lifecycle Process Software Artifacts
Software Artifacts
• The standard that defines all the tasks  • What is an artifact?
Wh t i tif t?
– “Something created by humans usually for a practical purpose”
q p g
required for developing and maintaining  g – “Something characteristic of or resulting from a human 
g g
institution or activity”
software • A software system is a collection of diverse software 
• What are those tasks?
What are those tasks? artifacts
– Requirements documentation
Requirement  – Design documentation
– Source code
Design – Source code documentation
– Executable (binary) code
Executable (binary) code
Implement – Installation/run‐time/usage documentation
– etc.
Testing
Maintenance
Software Artifacts
Software Artifacts Software Development Approaches
Software Development Approaches
Requirement  • There are two general approaches to 
h l h
Analysis model
‐ Domain Model
Domain Model
software development
Design
‐ Requirement Model • Structured approach 
• Ex. ALGOL, Pascal, PL/I , Ada, C
Design Model • Object‐oriented approach
Implement
‐ Software Architecture Documentation  • Ex. Java, .Net
‐ Detail Design Specification 
Detail Design Specification
Testing

Maintenance

structured approach
structured approach Structured Approach
• Very fashionable since the 1970s
f hi bl i h • There are two major weaknesses with the structured 
Th j k ih h d
approach:
• Adequately supported by conventional 
q y pp y • Data structures is likely out scope of work in top
Data structures is likely out scope of work in top‐down
down design
design
procedural languages.  • Difficult to reuse work done for other projects
ƒ Tend to produce the design that is unique to the initial problem
• Top‐down
Top down program design 
program design – break the 
break the ƒ when functions of the system change 
when functions of the system change =>> the analysis, the design models and the 
the analysis the design models and the
implementation of the system will have to be changed substantially. 
problem into several pieces and work on  • The above weaknesses of the structured approach have 
each piece separately
each piece separately made it less cost effective when compared with the object
made it less cost‐effective when compared with the object‐
oriented approach. 
• Centered on the system’s functional views 
and uses different models at various stages 
d diff t d l t i t
of the development process.  
Object-oriented Approach Object-oriented Approach
• Base on bottom up design and modular 
b d i d d l • M d l
Models a software system as a collection of 
ft t ll ti f
approach collaborating objects.  
• Reusable software component might be exist • Th b h i
The behaviour of the system results from the 
f h l f h
collaboration of those objects
• Easy to write code since information hiding
Easy to write code since information hiding 
• An object and its data interact with other 
b d d h h
used objects through messages being sent and 
• No effort or time is wasted by transforming
No effort or time is wasted by transforming  received by the object and which manipulate
received by the object and which manipulate 
and updating models in different stages.  the object’s data in the process and object 
itself decides what function to carry out to
itself decides what function to carry out to 
service that message.

Object‐Oriented Analysis (OOA)


Object‐Oriented Analysis (OOA) Object‐Oriented Design (OOD)
Object‐Oriented Design (OOD)
• An investigation of the problem to analyse the  • Transform the analysis models to produce 
q y
functional requirements for a system p p
implementation specifications
• focuses on what the system does • Focus on how the system does it
• Aim is to develop a model that describes 
Ai i d l d l h d ib • Concern on the constraints imposed by the 
C h i i db h
computer software as it works to satisfy a set  chosen architecture and any non‐functional –
of customer defined requirements. technological or environmental 
• The result of OOA is Analysis Model
The result of OOA is Analysis Model • The result of OOD is Design model which is a 
The result of OOD is Design model which is a
detailed description of how the system is to be 
b ilt
built
What’ss Next
What Next
• UML

You might also like