Page 117 - DCAP308_OBJECT_ORIENTED_ANALYSIS_AND_DESIGN

Unit 9: Analysis and Design

Functional view: Describes system behavior from the perspective of users of the Notes
system. Use case diagrams used to depict this functional view.

Static view: Describes the structure of the system in terms of classes, methods,
attributes, and relationships of objects in the system. This view is depicted using
CRC (Class Responsibility Collaboration) cards, as well using class and object
diagrams.
Dynamic view: Describes the internal system behavior in terms of object
communications and change of states. UML tools used to depict this view are sequence
diagrams, collaboration diagrams, and object state-charts.

Iterative and Incremental: Iterative and Incremental paradigm means that each iteration
of the system development must bring the system closer to the requirements. As SDLC is
a gradual process, the UML diagrams used in OO-based development moves from a
conceptual and abstract thing in the analysis and design phase to become more and more
detail in the implementation phase.

Task Make distinction between static view and dynamic view.

Self Assessment

Fill in the blanks:
1. ...................... applies object-modeling techniques to analyze the functional requirements
for a system.
2. ...................... elaborates the analysis models to produce implementation specifications.
3. The ...................... document will be the main document for developers, testers and database
administrators.
4. OO methodology decomposes problems into .......................
5. ...................... describe how the users of the system interact with the system to perform
activity.
6. ...................... view describes system behavior from the perspective of users of the system.
7. ......................view describes the structure of the system in terms of classes, methods,
attributes, and relationships of objects in the system.
8. ...................... view describes the internal system behavior in terms of object communications
and change of states.
9.2 Development Life Cycle

It is imperative to get acquainted with the general phases through which software development
passes. Unlike consumer products, software is not manufactured. In this sense, software is not a
passive entity rather it behaves organically. It undergoes a series of evolutionary stages
throughout its lifetime – starting from a problem terminating into a solution. That is why
software is said to ‘develop’ or ‘evolve’ and not manufactured.
In other words, software is born, passes through various developmental phases, gets established,
undergoes maintenance and finally grows old before being commissioned out of service.

LOVELY PROFESSIONAL UNIVERSITY 111