In their 1999 book The Unified Software Development Process , the authors of Uni
ID: 3846304 • Letter: I
Question
In their 1999 book The Unified Software Development Process, the authors of Unified Modeling Language (UML) noted that any modern object-oriented approach to developing information systems must be use-case driven, architecture-centric, and iterative and incremental.
Using your preferred UML drawing tool, draw your responses visually. Use any shapes you think are appropriate for your diagrams. Draw a diagram depicting the three basic properties of the modern software development processes. Draw another diagram depicting the models produced by these processes.
Explanation / Answer
UML (Unified Modeling Language) is a standard notation for the modeling of real-world objects as a first step in developing an object-oriented design methodology. Its notation is derived from and unifies the notations of three object-oriented design and analysis methodologies.
Types of UML diagrams
UML uses elements and associates them in different ways to form diagrams that represent static, or structural aspects of a system, and behavioral diagrams, which capture the dynamic aspects of a systems.
Structural UML diagrams
Behavioral UML diagrams
How to create a UML diagram
Structural Diagram
CLASS DIAGRAMS
Class diagrams represent the static structures of a system, including its classes, attributes, operations, and objects. A class diagram can display computational data or organizational data in the form of implementation classes and logical classes, respectively. There may be overlap between these two groups.
DEPLOYMENT DIAGRAMS
A deployment diagram models the physical deployment and structure of hardware components. Deployment diagrams demonstrate where and how the components of a system will operate in conjunction with each other.
ACTIVITY DIAGRAM
Activity diagrams show the procedural flow of control between class objects, along with organizational processes like business workflows. These diagram are made of specialized shapes, then connected with arrows. The notation set for activity diagrams is similar to those for state diagrams.
USE CASE DIAGRAM
A use case is a list of steps that define interaction between an actor (a human who interacts with the system or an external system) and the system itself. Use case diagrams depict the specifications of a use case and model the functional units of a system. These diagrams help development teams understand the requirements of their system, including the role of human interaction therein and the differences between various use cases. A use case diagram might display all use cases of the system, or just one group of use cases with similar functionality.
SEQUENCE DIAGRAM
Sequence diagrams, also known as event diagrams or event scenarios, illustrate how processes interact with each other by showing calls between different objects in a sequence. These diagrams have two dimensions: vertical and horizontal. The vertical lines show the sequence of messages and calls in chronological order, and the horizontal elements show object instances where the messages are relayed.