|
|
[ SA-Depot] > [category - 'UML 2 - Diagrams']
Problem description
Draw a state diagram to show the state transitions for a flight reservation.
On opening the flight, the initial state leads to the NoReservation state. When this state is entered, the reset operation is executed. If a reservation is made (i.e., reserve operation is executed), the object changes to the PartiallyReserved state. To book [...]
What are they?
A Use Case represents a single interaction between a primary actor (who initiates the interaction) and other (secondary) actors, and the system itself. The interaction is presented as a sequence of simple steps. A Use Case provides one or more scenarios that convey how an Actor interacts with the system to achieve [...]
A Class
An individual class is shown on the diagram as a box with up to four sections:
The first section shows the name of the class. Names should be nouns. Typically the first letter of every word in a name is capitalized.
Attributes represent the state of the object or what the object knows.
Operators represent the behavior [...]
This class diagram shows examples of associations, aggregations, and generalizations.
In general, associations describe the relationships between classes or objects. They start as simple connectors, to show that some relationship exists. As design progress (and often during development), the natures of the relationships become clearer, and the associations are modified to reflect the new knowledge. For [...]
What is a Class Diagram?
A class diagram describes the types of objects in the system and the various kinds of static relationships that exist among them. It is a graphical representation of a static view on declarative static elements and a central modeling technique that runs through nearly all object-oriented methods. The richest notation in [...]
Suppose we have such a lower level detailed design related to a member registration process:
register new member
fill in information
create a member
update personal information member
insert new member object to the database
We can used different behavior diagrams to represent the above scenario. Now let’s use a MVC architectural pattern to represent the scenario using interaction diagrams and [...]
Responsibility and Collaboration
We could put the implementation of a single Use Case inside a single method in a single class, but it would be an object oriented design which means that the single class is the whole system itself. To make a Use Case happen, we need to realize the Use Case with a group [...]
An Example: Capturing Requirements by using Business Workflow Modeling
Problem Statement
ABC Software Helpdesk received customers’ query related to the software products they supported. If the helpdesk staff can resolve the queries, they do so and give the customer a solution; otherwise they identify a problem and refer this to Second-line Support. Second-line Support reproduces and investigates [...]
The deployment model describes how an application is deployed across an infrastructure. It is used to show the distribution of components, typically across a multi-tier system or the deployment of components around a heterogeneous environment. In other words, The Deployment diagram shows the physical configuration of run-time processing components of a distributed system. The intention [...]
The behavior of an entity is not only a direct consequence of its inputs, but it also depends on its preceding state. The past history of an entity can best be modeled by a finite state diagram traditionally named automata. State diagrams (or sometimes referred to as statechart diagrams or state machine) show the different [...]
An object is an instance of a class and it is the instantiation of a class, i.e. it is the object created from the class at runtime. An object diagram shows specific instances of classes in a class diagram and links between the instances at some point in time. It can be thus viewed as [...]
The primary purpose of the timing diagram is to show the change in state or condition of a lifeline (representing a Classifier Instance or Classifier Role) over linear time. Timing diagrams are another type of interaction diagram focusing on conditions changing within and among Lifelines along a linear time axis. Timing diagrams describe behavior of [...]
Use Cases as a Communication Tool
It is important to make sure that each use case emphasizes on the functions of the system as seen by the user and that they are understandable by both the user and the system analyst. The use cases can then truly become an effective communication tool for the domain experts [...]
Both component and deployment diagram is a kind of implementation diagrams; it shows the aspects of model implementation, including source structure and run-time implementation structure. Component diagram shows the organizations and dependencies among software components. Typical examples of software components include source code, binary code or executable components. In contrast, Deployment diagram shows the configuration [...]
It is possible to organize sequence diagrams into control flow to indicate how they fit together. Interaction diagram combining the power of sequence diagrams and activity diagram together. It can be used to describe an overview of a complex system by embedding of Object Notes of Activity Diagram, inline interaction or InteractionOcurrences inside a control [...]
This entry is part of, Sequence Diagram Introduction» Example:
A sequence diagram has two dimensions: the vertical dimension and the horizontal dimension, respectively representing the passage of time and the objects involved in the interaction. Object icons are placed horizontally at the top of the sequence diagram, and messages are passed between them. Figure 1 shows [...]
This entry is part of, Sequence Diagram Introduction»
A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the life of the object instances that it represents, each having a vertical life span. On the vertical axis, it shows the sequence of the creation or invocation of these objects which are drawn [...]
An Introduction
Communication diagrams provide another way to model a scenario. In a communication diagram, each object is represented by an object icon, and links are used to indicate communication paths on which messages are transmitted. Messages are presented in the same way as those in a sequence diagram, and in fact, sequence diagrams and communication [...]
The use case description is a narrative document that describes, in general terms, the required functionality of the use case. Typically it describes the use case goal and gives a general description of what usually happens, the normal course of events, adding a brief description of any minor variations. In other words the description is [...]
Domain analysis is a tedious development process and it is quite difficult to be documented. We often jot it in a piece of paper and lack of center documentation repository for storing them, so that we know what is customer’s original intents of the project in terms of goals and scope.
Now, we use VP-UML to [...]
|
|