tyhyhrtggeggr

7/27/2019 tyhyhrtggeggr

http://slidepdf.com/reader/full/tyhyhrtggeggr 1/10

Diagrams

1.Activity Diagrams:Activity diagram is basically a flow chart to represent the flow form one activity to

another activity.

So before drawing an activity diagram we should identify the following elements:

• Activities

• Association

• Conditions

• Constraints

2.Data Flow diagram:a data flow diagram looks at how data flows through a system. It concerns things like wherethe data will come from and go to as well as where it will be stored.

External Entity

An external entity can represent a human, system or subsystem. It is where certain data

comes from or goes to. It is external to the system we study, in terms of the business

process. For this reason, people use to draw external entities on the edge of a diagram.



Process

A process is a business activity or function where the manipulation and transformation of

data takes place. A process can be decomposed to finer level of details, for representing

how data is being processed within the process.

Data Store

A data store represents the storage of persistent data required and/or produced by the

process. Here are some examples of data stores: membership forms, database table, etc.

Data Flow

A data flow represents the flow of information, with its direction represented by an arrow

head that shows at the end(s) of flow connector.



3. Control flow diagram A control flow diagram (CFD) is a diagram to describe the control flow of a businessprocess, process or program. A control flow diagram can consist of a subdivision to show sequential steps, with if-then-elseconditions, repetition, and/or case conditions. Suitably annotated geometrical figures are used torepresent operations, data, or equipment, and arrows are used to indicate the sequential flowfrom one to another.

CRC Diagram:



4. CRC Cards:

A CRC (Class, Responsibilities, and Collaborators) cards is an index card that is use to representthe responsibilities of classes and interaction between classes. CRC cards are an informalapproach to object oriented modeling. The cards are created through scenarios, based on thesystem requirements, that model the behavior of the system.

By definition, a class diagram is a diagram showing a collection of classes and interfaces, alongwith the collaborations and relationships among classes and interfaces.Why use CRC Cards

• They are portable. No computers are required so they can be used anywhere. • They allow participants to experience first hand how the system will work. No computer

tool can replace the interaction that happens by physically picking up the cards andplaying role of that object.

• They ar • e useful tool for teaching people the object-oriented paradigm. • They can be used as a methodology themselves or as a front end to more formal

methodology such as Booch, Jacobson, etc.

The Cards

Class Name :

Superclass :

Subclass :

Responsibilities Collaborators

The exact format of the card can be customized to the preferences of the group, but minimalrequired information if the name of the class, it's responsibilities and the collaborators.

5. State Diagram:

The state diagram in the Unified Modeling Language is essentially a Harel statechart with

standardized notation[1]

,[2]

which can describe many systems, from computer programs to

business processes. In UML 2 the name has been changed to State Machine Diagram. The

following are the basic notational elements that can be used to make up a diagram:

• Filled circle, pointing to the initial state

• Hollow circle containing a smaller filled circle, indicating the final state (if any)

• Rounded rectangle, denoting a state. Top of the rectangle contains a name of the state.

Can contain a horizontal line in the middle, below which the activities that are done in that

state are indicated

• Arrow, denoting transition. The name of the event (if any) causing this transition labels

the arrow body. A guard expression may be added before a "/" and enclosed in square-

brackets ( eventName[guardExpression] ), denoting that this expression must be true for

the transition to take place. If an action is performed during this transition, it is added to the

label following a "/" (eventName[guardExpression]/action ).



• Thick horizontal line with either x>1 lines entering and 1 line leaving or 1 line entering and

x>1 lines leaving. These denote join/fork, respectively.

6. Sequence Diagram:

A sequence diagram is a kind of interaction diagram that shows how processes operate withone another and in what order. It is a construct of a Message Sequence Chart. A sequencediagram shows object interactions arranged in time sequence. It depicts the objects and classesinvolved in the scenario and the sequence of messages exchanged between the objects neededto carry out the functionality of the scenario. Sequence diagrams are typically associated with usecase realizations in the Logical View of the system under development. Sequence diagrams aresometimes called event diagrams, event scenarios, and timing diagrams.



7. Use case Diagram:

UML Use Case Diagrams can be used to describe the functionality of a system

in a horizontal way. That is, rather than merely representing the details of

individual features of your system, UCDs can be used to show all of its

available functionality. It is important to note, though, that UCDs arefundamentally different from sequence diagrams or flow charts because they do

not make any attempt to represent the order or number of times that the systems

actions and sub-actions should be executed.



8. Deployment Diagram:

A deployment diagram in the Unified Modeling Language models the physical deployment

of artifacts on nodes.[1]

To describe a web site, for example, a deployment diagram would show

what hardware components ("nodes") exist (e.g., a web server, an application server, and adatabase server), what software components ("artifacts") run on each node (e.g., web application,database), and how the different pieces are connected (e.g. JDBC, REST, RMI).



9. Architecture Diagram:The system architecture diagram enables you to graphically model the applications of a system,

and the externals that they interface with and data stores that they use or provide information to.

The following information describes the symbols used on the diagram:

Application

You use the Application symbol to represent an entire application and graphically show on this

diagram how it is related to externals and data stores. Within the application definition, you can

specify overall information about the application -- the process threads in the organization that it

enables, the type of team effort being used to build it, etc. To specify more details on the

implementation of the application, you can create child Data Flow diagrams or UML diagrams,

depending on the nature of the application (for example, structured or object-oriented or

component-based).

Data Flow



You can model the flow of data as it moves from one point in the system to another with the Data

Flow line. The flow might be between externals and applications, or applications and data stores.

Within the data flow you can model the data elements and data structures used. Data flows can

split into two or more flows, or they can join to one from two or more flows.

Material Flow

You can model the direction of the flow of physical items and materials in the system with the

Material Flow line. The flow might be between externals and applications, or applications and

data stores.

Data Store

A Data Store symbol is where data "rests" when it is neither flowing nor being operated on. A

data store can be a database, hard disk, floppy disk, or a file on a disk.

Multi-Data Store

A Multi-Data Store symbol is used to denote that multiple instances of the data store exists. This

convention is used to avoid drawing a copy of a schema for each equivalent data store when you

build a data model.

External

An External symbol represents an object that sends information or data to the system, or takes

information from the system, but is not itself part of the system.

Multi-External

A Multi-External symbol is used to denote that multiple instances of the external exists.



Documents

tyhyhrtggeggr