This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
UML stands for Unified Modeling Language. It represents a unification of the concepts and notations presented by the three amigos in their respective books. The goal is for UML to become a common language for creating models of object oriented computer software. In its current form, UML is comprised of two main components: a Meta model and details. In the future, some form of method or process may also be added to; or associated with, UML.
UML is unique in that it has a standard data representation. This representation is called the Meta model. The meta-model is a description of UML in UML. It explains the objects, characteristic, and associations essential to symbolize the thoughts of UML inside a software application. This provides CASE manufacturers with a standard and unambiguous way to represent UML models. Hopefully it will allow for easy transport of UML models between tools. It may also make it easier to write ancillary tools for browsing, summarizing, and modifying UML models. A deeper discussion of the Meta model is beyond the scope of this column. Interested readers can learn more about it by downloading the UML documents from the rational web site.
The UML notation is rich and full-bodied. It is comprised of two major subdivisions. There is a notation for modeling the static elements of a design such as classes, attributes, and relationships. There is also a detail for modeling the active elements of a design such as messages, objects, and FSM (finite state machines).
Data Flow Diagram
When it comes to conveying how information data flows through systems (and how that data is transformed in the process), data flow diagrams (DFDs) are the method of choice over technical descriptions for three principal reasons.
1. Data flow diagrams are easier to understand by technical and nontechnical audiences
2. Data flow diagrams can provide a high level system overview, complete with boundaries and connections to other systems
3. Data flow diagrams can provide a detailed representation of system components. Data flow diagrams help system designers and others during initial analysis stages visualize a current system or one that may be necessary to meet new requirements. Systems analysts prefer working with Data flow diagrams, particularly when they require a clear understanding of the boundary between existing systems and postulated systems. Data flow diagrams represent the following:
1. External devices sending and receiving data
2. Processes that change that data
3. Data flows themselves
4. Data storage locations
The hierarchical DFD typically consists of a top-level diagram (Level 0) underlain by cascading lower level diagrams (Level 1, Level 2"Â¦) that represent the different system parts.
Use Case Diagram
Unit of functionality provided by the system was illustrated by use case diagram. Use-case diagram helps to improve teams imagine the useful necessities of a system; consist of the relationship of "actors" (person who will work together with the system) to necessary processes, as well as the relations together with various use cases. Use-case diagrams in general illustrate collections of use cases -- either every use cases for the whole system, or a running away of a specific collection of use cases with linked functionality (e.g., every security administration associated use cases). To illustrate a use-case on a use case chart, you sketch an oval in the mid of the diagram and type use case name in the middle of, or under, the oval. To sketch an actor (representing a user of system) on a use case diagram, then sketch a stick person in the diagram to the left or right (and only in case you are wondering, a few people sketch prettier stick people than others).
Class diagram illustrates how the various units (people, things, and data) connect to each other; in other hand, it illustrates the systems fixed structures. To show logical classes, which are usually the types of things the business persons in an company speak about -- DVDs, TV play; or finance, home credits, car credits, and rate of interest - use a class diagram. Class diagrams can as well utilize to illustrate execution classes, which are the belongings that programmers usually deal with. The execution class diagram will most likely illustrate a few of the similar classes as the class diagram (logical). The execution class diagram will not sketch with the similar aspects, but since it will be most possible have references to things like Vectors and Hash Maps.
Software objects relation and interaction are illustrated using UML Collaboration diagrams (interaction diagrams). They need use cases, system function deals, and domain model to subsist. The sent messages between classes and objects (instances) illustrated using collaboration diagram. Every system function that convey to the present development series is created as diagram. When designing collaboration diagrams, patterns are used to validate relations. Patterns are most excellent ethics for conveying tasks to objects and explained more in the part on patterns. There are two major types of patterns used for conveying tasks, which are evaluative patterns and driving patterns.
The practical flow of control among two or more class objects at the same time as handing out an activity exposed by activity diagrams. To representation higher-level business procedure at the business division level, or to representation low-level internal class actions, Activity diagrams can be used. In my understanding, activity diagrams are excellent used to model processes in higher-level, such as how the business is currently doing in companies.
Match up to sequence diagrams, activity diagrams are "less technological"ÂÂ in appearance and business-minded people being likely to be familiar with them without delay.
An activity diagram's notation set is related to that used in a state chart diagram. Like a state chart diagram, the activity diagram begins with a solid circle linked to the primary activity. The activity is modeled by sketch a rectangle with rounded edges, include the activity's name. Activities can be linked to other activities by way of transition lines or to decision points that link up to various actions secured by surroundings of the result point. Behavior that end the modeled process are linked to an ending point (just as in a state chart diagram).
Flows for a precise use case (or similarly part of a specific use case) shown in Sequence diagram. They are practically easy to understand; they illustrate the calls among the various objects in their series and can illustrate, at a complete level, dissimilar calls to dissimilar objects. There are two dimensions in sequence diagram: the series of messages/calls in the moment order that they occur shown in the vertical dimension; the object case to which the messages are sending shown in the horizontal dimension. It is very simple to draw. Diagonally the upper of the diagram, recognize the class instances (objects) by placing each class instance within a box (see Fig 4). In that, place the class instance name and class name alienated by " : " . If a class instance sends a message to a different class instance, sketch a line pointing towards the receiving class request with an open arrowhead; the name of the message/method has put above the line. Possibly, for main messages, you can sketch a dotted line with an arrowhead facing back to the beginning class instance; put a label on the return value above the dotted line. Individually, I all the time like to add in the return value lines for the reason that I find the more particulars create it easier to understand.