UML
Transcript: In the field of genetics have made enormous progress in America was born 1990 in genetic medicine, which is to use one of the 100,000 genes in human DNA to repair or alter the body's cells. 1b). Essay "Cases Diagram" Definition and uses The Unified Modeling Language prescribes a set of standard notations and diagrams to model object-oriented systems, and describes the essential semantics of these diagrams and symbols mean. A cases diagram describes what a system from the viewpoint of an outside observer, because of this, a diagram of this type is usually the easiest to interpret UML as its reason for being is concentrated on a that makes the system, unlike other UML diagrams that attempt to answer a How does the system behavior. The case diagrams describe the relationships and dependencies among a group of use cases and actors involved in the process. UML HISTORICAL ASPECTS The cases diagrams are used to facilitate communication with the future users of the system, and the customer, and are especially useful in determining the characteristics necessary to be the system. The cases diagrams describe what the system should do but not how. When working with use cases, it is important to remember some simple rules: • Each use case is related to at least one actor • Each use case is an initiator (ie an actor) • Each Use Case leads to a relevant result (a result with "intrinsic value"). The draft specification of UML 1.0 UML Partners was proposed to the OMG in January 1997. During the same month the UML Partners formed a Semantics Task Force, led by Cris Kobryn and administered by Ed Eykholt to finalize the semantics of the specification and to integrate with other standardization efforts. The result of this work, the UML 1.1 was submitted to the OMG in August 1997 and adopted by the OMG in November 1997. As a modeling notation, the dominating influence of OMT UML (eg using rectangles for classes and objects). Although it took the notation of "clouds" of Booch, if adopted Booch capability to specify design details at lower levels. The notation Objectory Use Cases and notation of Booch components were integrated into the rest of the notation, but the semantic integration was relatively weak in UML 1.1, and not really settled until the major revision of UML 2.0. 1c). HISTORICAL CONTEXT. With the collapse of communism in Eastern Europe, whose symbol was the fall of the Berlin Wall, and added to the economic and political crisis that would lead to its disintegration Soviet Union in late 1991, the "cold war" came to an end. This became the origin of a new world order, with few exceptions, the world was unified under one language: English, an economic trend: the globalization of markets, a multi-media: the Internet, one faith: democracy and capitalism, and an emperor: the United States of America. . In 1994 he created the World Trade Organization, in association with the International Monetary Fund and World Bank. The birth of the European Union (EU) in 1993, gave the world a new political bloc strong economic gradually positioned itself as a dominant force in Europe. Middle East increased its internal divisions and the Arab countries no longer pose a threat to the existence of Israel. The Gulf War divided the Arab countries, some of whom were allied with Western powers to attack Iraq, which, under the rule of Saddam Hussein, had invaded Kuwait. In 1996 Rational concluded that the abundance of modeling languages was encouraging the adoption of object technology, and to move towards a unified approach, charged the Three Amigos to develop a Unified Modeling Language opened. We consulted with representatives of competing companies in the area of object technology for the OOPSLA '96, chose boxes for representing classes instead of the Booch notation that used cloud symbols. Under the technical direction of the Three Friends was organized an international consortium called the UML Partners in 1996 to complete the specifications of the Unified Modeling Language (UML), and to propose it as a response to the OMG RFP. Use cases may have relationships with other use cases. The three most common types of relationships between use cases are: • << include>> specifying a situation in which a case of use takes place in another case of use. • << extends >> which specifies that in certain situations, or at some point (called the extension point) a use case will be extended by another. • Generalization specifies that a Use Case inherits the characteristics of "super" use case, and can override some or all of them in a way very similar to the inheritance between classes. Actor An actor is an external entity (outside the system) that interacts with the system by participating (and often initiating) a Use Case. Actors can be people (eg. users), other computers or external events. CONCLUSIONS: • The use case diagrams are a tool in the requirements phase. • Intuitive, easy is to be used in discussion with customers. • Use cases are hardly
Prezi Present
Prezi Video
Prezi Design
