Object Oriented Analysis and Design Lab - Study of UML - Unified Modeling Language
Click here to download the complete document with Diagrams...
1. What is Object-Oriented Analysis and Design?
During object-oriented design (or simply, object design) there is an emphasis on defining
software objects and how they collaborate to fulfill the requirements. For example, a Plane
software object may have a tailNumber attribute and a getFlightHistory method.
2. What is UML?
The UML defines various UML profiles that specialize subsets of the notation for common
subject areas, such as diagramming Enterprise JavaBeans (with the UML EJB profile).
Three Ways to Apply UML:
· UML as sketch Informal and incomplete diagrams (often hand sketched on whiteboards)
created to explore difficult parts of the problem or solution space, exploiting the power of
visual languages.
· UML as blueprint Relatively detailed design diagrams used either for 1) reverse
engineering to visualize and better understanding existing code in UML diagrams, or for
2) code generation (forward engineering).
· UML as programming language Complete executable specification of a software
system in UML. Executable code will be automatically generated, but is not normally
seen or modified by developers; one works only in the UML "programming language."
This use of UML requires a practical way to diagram all behavior or logic (probably
using interaction or state diagrams), and is still under development in terms of theory,
tool robustness and usability.
Agile modeling emphasizes UML as sketch; this is a common way to apply the UML, often
with a high return on the investment of time (which is typically short). UML tools can be
useful, but I encourage people to also consider an agile modeling approach to applying UML.
Three Perspectives to Apply UML:
1. Conceptual perspective the diagrams are interpreted as describing things in a situation of
the real world or domain of interest.
2. Specification (software) perspective the diagrams (using the same notation as in the
conceptual perspective) describe software abstractions or components with specifications
and interfaces, but no commitment to a particular implementation (for example, not
specifically a class in C# or Java).
3. Implementation (software) perspective the diagrams describe software implementations
in a particular technology (such as Java).
3. UML Use Cases
Actors:
Actor is something with behavior, such as a person (identified by role), computer system, or
organization; for example, a cashier.
Scenario:
A scenario is a specific sequence of actions and interactions between actors and the system; it is
also called a use case instance the use case; for example, the scenario of successfully purchasing items with cash, or the scenario of failing to purchase items because of a credit payment denial.
Use Case:
A use case is a collection of rel
system to support a goal.
4. UML Use Cases and the Use
The UP defines the Use-Case Model
of all written use cases; it is a model of the system's functionality and environment.
The Use-Case Model is not the only requirement artifact in the UP. There are also the
Supplementary Specification, Glossary, Vision, and Business Rules. These are all useful for
requirements analysis, but secondary at this point.
1. What is Object-Oriented Analysis and Design?
During object-oriented design (or simply, object design) there is an emphasis on defining
software objects and how they collaborate to fulfill the requirements. For example, a Plane
software object may have a tailNumber attribute and a getFlightHistory method.
2. What is UML?
The UML defines various UML profiles that specialize subsets of the notation for common
subject areas, such as diagramming Enterprise JavaBeans (with the UML EJB profile).
Three Ways to Apply UML:
· UML as sketch Informal and incomplete diagrams (often hand sketched on whiteboards)
created to explore difficult parts of the problem or solution space, exploiting the power of
visual languages.
· UML as blueprint Relatively detailed design diagrams used either for 1) reverse
engineering to visualize and better understanding existing code in UML diagrams, or for
2) code generation (forward engineering).
· UML as programming language Complete executable specification of a software
system in UML. Executable code will be automatically generated, but is not normally
seen or modified by developers; one works only in the UML "programming language."
This use of UML requires a practical way to diagram all behavior or logic (probably
using interaction or state diagrams), and is still under development in terms of theory,
tool robustness and usability.
Agile modeling emphasizes UML as sketch; this is a common way to apply the UML, often
with a high return on the investment of time (which is typically short). UML tools can be
useful, but I encourage people to also consider an agile modeling approach to applying UML.
Three Perspectives to Apply UML:
1. Conceptual perspective the diagrams are interpreted as describing things in a situation of
the real world or domain of interest.
2. Specification (software) perspective the diagrams (using the same notation as in the
conceptual perspective) describe software abstractions or components with specifications
and interfaces, but no commitment to a particular implementation (for example, not
specifically a class in C# or Java).
3. Implementation (software) perspective the diagrams describe software implementations
in a particular technology (such as Java).
3. UML Use Cases
Actors:
Actor is something with behavior, such as a person (identified by role), computer system, or
organization; for example, a cashier.
Scenario:
A scenario is a specific sequence of actions and interactions between actors and the system; it is
also called a use case instance the use case; for example, the scenario of successfully purchasing items with cash, or the scenario of failing to purchase items because of a credit payment denial.
Use Case:
A use case is a collection of rel
system to support a goal.
4. UML Use Cases and the Use
The UP defines the Use-Case Model
of all written use cases; it is a model of the system's functionality and environment.
The Use-Case Model is not the only requirement artifact in the UP. There are also the
Supplementary Specification, Glossary, Vision, and Business Rules. These are all useful for
requirements analysis, but secondary at this point.
0 comments:
Post a Comment