The Coad and Yourdon Method

Introduction

The idea in this method is to extend the model with respect to

processes, Human interfaces and DBMS issues.
The 5 steps are:-
1. Finding object and classes
2. Identifying structure
3. Identifying subject
4. Defining attributes
5. Defining services
The design approach addresses not only the application but also
the infrastructure for the application and focuses on 4 components.
Yourdon and Coad Symbols
System Design
Five layers
Subject layer: showing the overall partitions of the system
Class-&-Object layer: showing the abstract and
concrete classes of the system
Structure layer: showing the generalization-specification
and whole part relationships between the classes
Attribute layer: showing the attributes of the classes and
the association relationships between classes.
Service layer: showing the operations of the classes and
the potential message-passing between the objects
1. Problem Domain Component
Initially contains the results of the analysis phase. During
OOD, it is improved and enriched with implementation
details.
Refine design to improve performance.
Develops and interface with the data management
components.
Group all domain specific classes.
Design an appropriate class hierarchy for the
application classes.
2.Human Interaction Component
It includes designing a relevant classes and class
hierarchy.
Handles sending and receiving messages to and from
the user.
Refines the user interaction sequence.
Integrate GUI classes as appropriate.
Graphical user interface libraries are currently not
standardized (at all), so the details concerning them will
vary from system to system. However, the Java user
interface library is currently regarded as being well
designed, and information about it is freely available.
3.Task Management Component
A task can be defined as a process, or a ``stream of
activity.
Coad and Yourdon give a small set of properties or types
of tasks that can be used to identify the services that
their classes must provide, and provide a very simple
``template'' (or pattern) for a task management
subsystem, consisting of a whole-part structure, showing
that a ``Task Coordinator'' object has zero or more
``Task'' objects as components, and can send messages
to them.
4.Data Management Component
The data management component ``provides the
infrastructure for the storage and retrieval of objects
from a data management subsystem.
Coad and Yourdon give a small amount of information
for the design of this component, assuming that a ``flat
file'' system will be used for storage, that a relational
data base package will be used, and, finally, under the
assumption that an object-oriented data base package
will be used
It may be a simple file system, a relational database
management system, or even an object-oriented
database management system.
The End