You are on page 1of 108

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

SNO 1

NAME OF THE EXPERIMENT UML INTRODUCTION A POINT-OF-SALES SYSTEM

PAGE NO

REMARKS

2

3

ONLINE BOOKSHOP AN AUCTION APPLICATION A MULTI THREADED AIRPORT SIMULATION A SIMULATED COMPANY

4
5 6

UNIFIED MODELING LANGUAGE

Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

UML INTRODUCTION

UNIFIED MODELING LANGUAGE

Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

STUDY OF UML
AIM: General study of UML DESCRIPTION: The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential details of the underlying problem from its usually complicated real world. Several modeling tools are wrapped under the heading of the UML, which stands for Unified Modeling Language. The purpose of this course is to present important highlights of the UML. CLASS A class is a blueprint or prototype from which objects are created. This section defines a class that models the state and behavior of a real-world object. It intentionally focuses on the basics, showing how even simple classes can cleanly model state and behavior. For example, the class Dog would consist of traits shared by all dogs, such as breed and fur color (characteristics), and the ability to bark and sit (behaviors). OBJECT An object is a software bundle of related state and behavior. Software objects are often used to model the real-world objects that you find in everyday life. This lesson explains how state and behavior are represented within an object, introduces the concept of data

UNIFIED MODELING LANGUAGE

Page no:

For example. the object Lassie is one particular dog. and as an Animal (perhaps the parent class of Dog) when counting Timmy's pets. OBJECT ORIENTATION CONCEPTS: Object-Orientation goes beyond just modeling attributes and behavior. and working at the most appropriate level of inheritance for a given aspect of the problem. encapsulation. and explains the benefits of designing your software in this manner. with particular versions of the characteristics. Lassie has brown-and-white fur. The class Dog defines all possible dogs by listing the characteristics and behaviors they can have. These aspects modularity.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Abstraction is also achieved through Composition. polymorphism and encapsulation. For example. inheritance. JAHNAVI ROLL NO: 1220609110 encapsulation. and abstraction. Programming techniques may include features such as data abstraction. A Dog has fur. a class UNIFIED MODELING LANGUAGE Page no: . A pattern(exemplar) of a class. It considers the other aspects of objects as well. Objectoriented programming (OOP) is a programming paradigm that uses "objects" – data structures consisting of data fields and methods together with their interactions – to design applications and computer programs. a Collie when necessary to access Collie-specific attributes or behaviors. are called polymorphism. Lassie the Dog may be treated as a Dog much of the time. ABSTRACTION Abstraction is simplifying complex reality by modeling classes appropriate to the problem. Inheritance.

Encapsulation is achieved by specifying which classes may use the members of an object.NET reserve some members to classes in the same assembly using keywords internal (C#) or Friend (VB. protected or private. at a particular pitch and volume). Timmy. an interface can ensure that puppies can only be added to an object of the class Dog by code in that class. sub-classes or only the defining class. Members are often specified as public. and Eiffel and C++ allow one to specify which classes may access any member. Some languages go further: Java uses the default access modifier to restrict access also to classes in the same package. the Dog class has a bark () method. Lassie's friend. determining whether they are available to all classes.g. The code for the bark() method defines exactly how a bark happens (e. however. For example. without changes to clients.GITAM INSTITUTE OF TECHNOLOGY NAME: T.. that is. by inhale() and then exhale(). thereby allowing those changes to be made more easily. JAHNAVI ROLL NO: 1220609110 ENCAPSULATION: Encapsulation conceals the functional details of a class from objects that send messages to it.NET). UNIFIED MODELING LANGUAGE Page no: . does not need to know exactly how she barks. The result is that each object exposes to any class a certain interface — those members accessible to that class. For example. C# and VB. The reason for encapsulation is to prevent clients of an interface from depending on those parts of the implementation that are likely to change in the future.

can be abstractly applied in many different situations.GITAM INSTITUTE OF TECHNOLOGY NAME: T. this may elicit a bark(). One method. JAHNAVI ROLL NO: 1220609110 POLYMORPHISM: Polymorphism allows the programmer to treat derived class members just like their parent class's members. -. Lassie would be an instance of the Collie subclass. Chihuahua. In this case. which inherit attributes and behaviors from their parent classes. meaning that the programmer only needs to write the code for them once. this may elicit an oink(). or *. More precisely. if a Pig is commanded to speak(). and Golden Retriever) will inherit these members. However. and can introduce their own. UNIFIED MODELING LANGUAGE Page no: . Chihuahua. For example. the class Dog might have sub-classes called Collie. each one according to an appropriate type-specific behavior. INHERITANCE: Subclasses are more specialized versions of a class. and Golden Retriever. Each subclass overrides the speak() method inherited from the parent class Animal. Polymorphism in object-oriented programming is the ability of objects belonging to different data types to respond to calls of methods of the same name. Each of its subclasses (Collie. Suppose the Dog class defines a method called bark() and a property called fur Color. If a Dog is commanded to speak(). or an operator such as +.

JAHNAVI ROLL NO: 1220609110 Each subclass can alter its inherited traits. but Lassie would not.GITAM INSTITUTE OF TECHNOLOGY NAME: T. is a" relationship between classes. not a Chihuahua.. In fact. The Chihuahua object would also have the tremble () method.. For example. The Chihuahua subclass could add a method called tremble (). the object named Lassie has the methods from both classes Collie and Dog. independent classes could define Dogs and Cats. Multiple inheritances are inheritance from more than one ancestor class. while instantiation is an "is a" relationship between an object and a class: a Collie is a Dog ("a. which in turn inherited the usual bark () from Dog. The Chihuahua subclass might specify that the bark () method produces a high pitch by default. So an individual Chihuahua instance would use a highpitched bark () from the Chihuahua subclass. but Lassie is a Collie ("is a").      Use case diagrams Class diagrams Object diagrams Sequence diagrams Collaboration diagrams Page no: UNIFIED MODELING LANGUAGE . inheritance is an "a.. Subclasses can also add new members. and a Chimera object could be created from these two which inherits all the (multiple) behavior of cats and dogs. neither of these ancestors being an ancestor of the other. Thus.. which we describe here. as it can be hard to implement At the center of the UML are its nine kinds of modeling diagrams. This is not always supported. is a"). because she is a Collie. For example. the Collie subclass might specify that the default four-Color for a collie is brown-and-white.

and programmers alike. The more complicated the underlying system. The UML is applicable to object-oriented problem solving. The more complicated the building.GITAM INSTITUTE OF TECHNOLOGY     NAME: T. the more critical the communication between architect and builder. The UML gives everyone from business analyst to designer to programmer a common vocabulary to talk about software design. It is now part of the software trade. Architects design buildings. Builders use the designs to create buildings. JAHNAVI ROLL NO: 1220609110 State chart diagrams Activity diagrams Component diagrams Deployment diagrams Why is UML important? Let's look at this question from the point of view of the construction trade. the more critical the communication among everyone involved in creating and deploying the software. In the past decade. A model is an abstraction of the underlying problem. Writing software is not unlike constructing a building. the UML has emerged as the software blueprint language for analysts. designers. The domain is the actual world from which the problem UNIFIED MODELING LANGUAGE Page no: . Blueprints are the standard graphical language that both architects and builders must learn as part of their trade.it all begins with the construction of a model. Anyone interested in learning UML must be familiar with the underlying tenet of object-oriented problem solving -.

JAHNAVI ROLL NO: 1220609110 comes. Here is a scenario for a medical clinic. Use case diagrams are closely connected to scenarios. Classes are the "blueprints" for objects. The emphasis is on what a system does rather than how. The actor is a UNIFIED MODELING LANGUAGE Page no: . Objects are instances of classes. A scenario is an example of what happens when someone interacts with the system. Models consist of objects that interact by sending each other messages. The values of an object's attributes determine its state. The picture below is a Make Appointment use case for the medical clinic. "A patient calls the clinic to make an appointment for a yearly checkup. Use case diagrams: Use case diagrams describe what a system does from the standpoint of an external observer. The receptionist finds the nearest empty time slot in the appointment book and schedules the appointment for that time slot." Objects have things they know (attributes) and things they can do (behaviors or operations). Think of an object as "alive. An actor is who or what initiates the events involved in that task.GITAM INSTITUTE OF TECHNOLOGY NAME: T. " A use case is a summary of scenarios for a single task or goal. Actors are simply roles that people or objects play. A class wraps attributes (data) and behaviors (methods or functions) into a single distinct entity.

use cases. JAHNAVI ROLL NO: 1220609110 and use case is a communication association (or communication for short). UNIFIED MODELING LANGUAGE Page no: . Communications are lines that link actors to use cases. The connection between actor NAME: T. A use case diagram is a collection of actors. Notice that a single use case can have multiple actors. We've put Make Appointment as part of a diagram with four actors and four use cases. Actors are stick figures. Use cases are ovals. and their communications.GITAM INSTITUTE OF TECHNOLOGY Patient.

 Determining features (requirements). The central class is the Order. Communicating with clients. Class diagrams are static -they display what interacts but not what happens when they do interact. New use cases often generate new requirements as the system is analyzed and the design takes shape. Generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.   Class diagrams: A Class diagram gives an overview of a system by showing its classes and the relationships among them. Associated with it is the UNIFIED MODELING LANGUAGE Page no: . Their notational simplicity makes use case diagrams a good way for developers to communicate with clients. JAHNAVI ROLL NO: 1220609110 Use case diagrams are helpful in three areas. The class diagrams below models a customer order from a retail catalog.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

UNIFIED MODELING LANGUAGE Page no: . UML class notation is a rectangle divided into three parts: class name. each with its associated Item. The order contains Order Details (line items).a relationship between instances of the two classes.GITAM INSTITUTE OF TECHNOLOGY NAME: T. are in italics. or Credit. There is an association between two classes if an instance of one class must know about the other in order to  Perform its work. attributes.  Association -. Relationships between classes are the connecting links. Our class diagram has three kinds of relationships. and operations. JAHNAVI ROLL NO: 1220609110 Customer making the purchase and the Payment? A Payment is one of three kinds: Cash. Check. such as Payment. an association is a link connecting two classes. In a diagram. Names of abstract classes.

Multiplicities are single numbers or ranges of numbers. m indicates n to m instances. Check. an Order Detail is a line item of each Order. A navigability arrow on an association shows which direction the association can be traversed or queried. Order has a collection of Order Details. This table gives the most common multiplicities. but not the other way around. in this case. Order Detail has an Item.1 0. A generalization has a triangle pointing to the super class.. Associations with no navigability arrows are bi-directional. Multiplicities Meaning 0. Generalization -. An Order Detail can be queried about its Item.an inheritance link indicating one class is a super class of the other.GITAM INSTITUTE OF TECHNOLOGY  NAME: T.* or * zero or one instance. The multiplicity of an association end is the number of possible instances of the class associated with a single instance of the other end. In our example.  An association has two ends. there can be only one Customer for each Order. Payment is a super class of Cash.. The arrow also lets you know who "owns" the association's implementation. no limit on the number of instances (including UNIFIED MODELING LANGUAGE Page no: . but a Customer can have any number of Orders. JAHNAVI ROLL NO: 1220609110 Aggregation -.an association in which one class belongs to a collection. In our diagram. An aggregation has a diamond end pointing to the part containing the whole. For example. . An end may have a role name to clarify the nature of the association. and Credit. The notation n .

you can group classes into packages. UNIFIED MODELING LANGUAGE Page no: .* exactly one instance at least one instance NAME: T. JAHNAVI ROLL NO: 1220609110 Every class diagram has classes. 1 1. The diagram below is a business model in which the classes are grouped into packages. Packages and object diagrams To simplify complex class diagrams.. and multiplicities. associations. Navigability and roles are optional items placed in a diagram to provide clarity. A package is a collection of logically related UML elements.GITAM INSTITUTE OF TECHNOLOGY none).

GITAM INSTITUTE OF TECHNOLOGY NAME: T. The object diagram below instantiates the class diagram. UNIFIED MODELING LANGUAGE Page no: . The dotted arrows are dependencies. They are useful for explaining small pieces with complicated relationships. replacing it by a concrete example. especially recursive relationships. This small class diagram shows that a university Department can contain lots of other Departments. Object diagrams show instances instead of classes. JAHNAVI ROLL NO: 1220609110 Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the rectangle. One package depends on another if changes in the other could possibly force changes in the first.

A sequence diagram is an interaction diagram that details how operations are carried out -.what messages are sent and when. Sequence diagrams are organized according to time. The objects involved in the operation are listed from left to right according to when they take part in the message sequence. Below is a sequence diagram for making a hotel reservation. Sequence diagrams Class and object diagrams are static model views. The time progresses as you go down the page. UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T. Instance names are underlined in UML diagrams. Class or instance names may be omitted from object diagrams as long as the diagram meaning is still clear. They describe how objects collaborate. The object initiating the sequence of messages is a Reservation window. Interaction diagrams are dynamic. JAHNAVI ROLL NO: 1220609110 Each rectangle in the object diagram corresponds to a single instance.

The asterisk on the self call means iteration (to make sure there is available room for each day of the stay in the hotel). Each vertical dotted line is a lifeline. The expression in square brackets. Each arrow is a message call. UNIFIED MODELING LANGUAGE Page no: . the Hotel issues a self call to determine if a room is available. An arrow goes from the sender to the top of the activation bar of the message on the receiver's lifeline. [ ]. The activation bar represents the duration of execution of the message. In our diagram. then the Hotel creates a Reservation and a Confirmation. then it makes a Reservation and a Confirmation. If so. The Hotel Chain then sends a make Reservation () message to a Hotel.GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 The Reservation window sends a make Reservation () message to a Hotel Chain. If the Hotel has available rooms. is a condition. representing the time that an object exists.

They Convey the same information as sequence diagrams. object roles are the vertices and messages are the connecting links. UNIFIED MODELING LANGUAGE Page no: . Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1. according to when they occur.GITAM INSTITUTE OF TECHNOLOGY NAME: T. 2. The top-level message is numbered 1. etc. but they focus on object roles instead of the times that messages are sent. Class names are preceded by colons (: ). JAHNAVI ROLL NO: 1220609110 Collaboration diagrams: Collaboration diagrams are also interaction diagrams. Each message in a collaboration diagram has a sequence number. In a sequence diagram. The object-role rectangles are labeled with either class or object names (or both).

A state chart diagram shows the possible states of the object and the transitions that cause a change in state. JAHNAVI ROLL NO: 1220609110 State chart diagrams: Objects have behaviors and state. UNIFIED MODELING LANGUAGE Page no: . Our example diagram models the login part of an online banking system. The state of an object depends on its current activity or condition. Logging in can be factored into four non-overlapping states: Getting SSN. Getting PIN. then submitting the information for validation. and Rejecting. Logging in consists of entering a valid social security number and personal id number.GITAM INSTITUTE OF TECHNOLOGY NAME: T. From each state comes a complete set of transitions that determine the subsequent state. Validating.

one on Getting SSN and another on Getting PIN. etc. The action that occurs as a result of an event or condition is expressed in the form /action. Transitions are arrows from one state to another. While in its Validating state. ATM. While a state chart diagram focuses attention on an object undergoing a process (or on a process as an object). Activity diagrams: An activity diagram is essentially a fancy flowchart. "Withdraw money from a bank account through an ATM.GITAM INSTITUTE OF TECHNOLOGY NAME: T." The three involved classes (people. Instead. and Bank. JAHNAVI ROLL NO: 1220609110 States are rounded rectangles. it performs an activity.) of the activity are Customer. an activity diagram focuses on the flow of activities involved in a single process. The result of that activity determines its subsequent state. Final states are also dummy states that terminate the action. The process begins at the black start UNIFIED MODELING LANGUAGE Page no: . we used the following process. The initial state (black circle) is a dummy to start the action. the object does not wait for an outside event to trigger a transition. Events or conditions that trigger transitions are written beside the arrows. Our diagram has two self-transition. The activity diagram shows the how those activities depend on one another. Activity diagrams and state chart diagrams are related. For our example.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. The activities are rounded rectangles. JAHNAVI ROLL NO: 1220609110 Circle at the top and ends at the concentric white/black stop circles at the bottom. Activity diagrams can be divided into object swimlanes that determine which object is responsible for which activity. UNIFIED MODELING LANGUAGE Page no: . A single transition comes out of each activity. connecting it to the next activity.

UNIFIED MODELING LANGUAGE Page no: . A transition may fork into two or more parallel activities. The following deployment diagram shows the relationships among software and hardware components involved in real estate transactions. JAHNAVI ROLL NO: 1220609110 A transition may branch into two or more mutually exclusive transitions.GITAM INSTITUTE OF TECHNOLOGY NAME: T. The fork and the subsequent join of the threads coming out of the fork appear in the diagram as solid bars. Component diagrams are physical analogs of class diagram. Guard expressions (inside [ ]) label the transitions coming out of a branch. A branch and its subsequent merge marking the end of the branch appear in the diagram as hollow diamonds. Component and deployment diagrams: A component is a code module. Deployment diagrams show the physical configurations of software and hardware.

UNIFIED MODELING LANGUAGE Page no: . 4. Identify the functionality the way of interacting actors with system and specify the behavior of actor. STEPS FOR MODELING UML DIAGRAMS Modeling steps for Use case Diagram 1.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Identify the actors which are interacting with the system. Components are shown as rectangles with two tabs at the upper left. Draw the lines around the system and actors lie outside the system. Each component belongs on a node. 3. Separate the generalized and specialized actors. 2. JAHNAVI ROLL NO: 1220609110 The physical hardware is made up of nodes.

Set the lifelines for each and every object by sending create and destroy messages. 7. Modeling steps for Sequence Diagrams 1. Functionality or behavior of actors is considered as use cases. subsystem. Set the pre and post conditioned. 9. 2. Set the context for the interactions. Specify the time and space constraints. 5. Modeling steps for Collaboration Diagrams UNIFIED MODELING LANGUAGE Page no: . Se the relationship among the use cases and in between actor and use cases. Adorn with constraints and notes. Lay them out along the X-axis by placing the important object at the left side and others in the next subsequent. Specify the generalized and specialized use cases. Set the stages for the interactions by identifying objects which are placed as actions in interaction diagrams. 3. JAHNAVI ROLL NO: 1220609110 5. classes. 8. Start the message which is initiating interactions and place all other messages in the increasing order of items. 7. 6. 6. object or use cases. system. use collaborations to realize use cases. If necessary.GITAM INSTITUTE OF TECHNOLOGY NAME: T. 4.

whether it is system. attach each subsequent message to appropriate appropriate. Starting with the message setting that initiates number this as interaction. Set the context for interaction. Set the initial properties of each of these objects. update with these new values and connect them by a message stereotyped as become or copy. Identify the objects that play a role in the interaction. placing important objects in centre and neighboring objects to outside. Lay out other links and adorn with stereotypes. 6. place a duplicate object. 2. operation or class or one scenario of use case or collaboration. Modeling steps for Activity Diagrams 1.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Adorn each message with time and space constraints if needed 7. Lay them as vertices in graph. subsystem. Select the object that has high level link. 4. 3. 5. UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 1. Specify the links among these objects. sequence responsibilities. Attach pre & post conditions to specify flow of control formally. If the attributes or tagged values of an object changes in significant ways over the interaction. Lay the association links first represent structural connection.

a use case. 4. 6. Render the transitions that connect these activities and action states. consider branching. or for a set of actions that appear multiple times. For complicated actions. UNIFIED MODELING LANGUAGE Page no: . whether it is a class. 4. The high-level states of the objects & only then consider its possible sub-states. Decide on the meaningful partial ordering of stable states over the lifetime of the object. create a swim-lane for each important object. NAME: T. Choose the initial & final states of the objects.GITAM INSTITUTE OF TECHNOLOGY 2. 5. fork and joining. 3. 5. Start with sequential flows. 2. JAHNAVI ROLL NO: 1220609110 These objects may be real or abstract. Choose the context for state machine. In either case. specify the activities and actions and render them as activity states or action states. 3. Identify the precondition of initial state and post conditions of final state. collapse these states and provide separate activity diagram. 8. 7. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. or the system as a whole. Adorn with notes tagged values and so on. Modeling steps for State chart Diagram 1. Beginning at initial state.

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

6. Decide on the events that may trigger a transition from state to state. Model these events as triggers to transitions that move from one legal ordering of states to another. 7. Attach actions to these transitions and/or to these states. 8. Consider ways to simplify your machine by using substates, branches, forks, joins and history states. 9. Check that all states are reachable under some combination of events. 10.Check that no state is a dead from which no combination of events will transition the object out of that state. 11.Trace through the state machine, either manually or by using tools, to check it against expected sequence of events & their responses.

Modeling steps for Class Diagrams
1. Identity the things that are interacting with class diagram. 2. Set the attributes and operations. 3. Set the responsibilities. 4. Identify classes. 5. Set the relationship among all the things. 6. Adorn with tagged values, constraints and notes. the generalization and specification

Modeling steps for Object Diagrams
1. Identify the mechanisms which you would like to model. UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY 2. Identify the classes, which use

NAME: T. JAHNAVI ROLL NO: 1220609110

cases,

interface, with

subsystem mechanisms.

are

collaborated

3. Identify the relationship among all objects. 4. Walk through the scenario until to reach the certain point and identify the objects at that point. 5. Render all these classes as objects in diagram. 6. Specify the links among all these objects. 7. Set the values of attributes and states of objects.

Modeling steps for Component Diagrams
1. Identify the component libraries and executable files which are interacting with the system. 2. Represent components. 3. Show the relationships among all the components. 4. Identify the files, tables, documents which are interacting with the system. 5. Represent files, tables, documents as components. 6. Show the existing relationships among them generally dependency. 7. Identify the seams in the model. 8. Identify the interfaces which are interacting with the system. 9. Set attributes and operation signatures for interfaces. 10.Use either import or export relationship in b/w interfaces & components. UNIFIED MODELING LANGUAGE Page no: this executables and libraries as

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

11.Identify the source code which is interacting with the system. 12.Set the version of the source code as a constraint to each source code. 13.Represent source code as components. 14.Show the relationships among components. 15.Adorn with nodes, constraints and tag values.

Modeling steps for Deployment Diagram
1. Identify the processors which represent client & server. 2. Provide the visual cue via stereotype classes. 3. Group all the similar clients into one package. 4. Provide the links among clients & servers. 5. Provide the attributes & operations. 6. Specify the components which are living on nodes. 7. Adorn with nodes & constraints & draw the deployment diagram.

APPLICATION OF RATION ROSE TO UML
Rational Rose was developed by IBM Corporation in order to develop a software system based on the concepts of Object Oriented Analysis and Design approach as developed from the models of Grady Booch, Jacobson and Ram Baugh methodologies, resulting into a Unified approach. Rational Rose is an object-oriented Unified Modeling Language (UML) software design tool intended for visual modeling and component construction of enterprise-level software applications. In UNIFIED MODELING LANGUAGE Page no:

as the developer begins to understand how the components interact and makes modifications in the design. Java. Two popular features of Rational Rose are its ability to provide iterative development and round-trip engineering. use case elements (ovals). (This is in contrast to waterfall development where the whole project is completed from start to finish before a user gets to try it out. a software designer uses Rational Rose to visually create (model) the framework for an application by blocking out classes with actors (stick figures). component packages. components. The overall model contains classes.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Rational Rose allows designers to take advantage of iterative development (sometimes called evolutionary development) because the new application can be created in stages with the output of one iteration becoming the input to the next. which provides a means of visualizing and manipulating the model’s elements UNIFIED MODELING LANGUAGE Page no: . objects (rectangles) and messages/relationships (arrows) in a sequence diagram using dragand-drop symbols. Oracle8. operations. objects. devices and the relationship between them. Rational Rose can perform what is called "round-trip engineering" by going back and updating the rest of the model to ensure the code remains consistent. Each of these model elements possess model properties that identify and characterize them. Visual Basic. Rational Rose documents the diagram as it is being constructed and then generates code in the designer's choice of C++. processors. JAHNAVI ROLL NO: 1220609110 much the same way a theatrical director blocks out a play. A model also contains diagrams and specifications. CORBA or Data Definition Language. packages.) Then. use cases.

which element. HISTORY ROSE = Rational Object Oriented Software Engineering Rational Rose is a set of visual modeling tools for development of object-oriented software. UNIFIED MODELING LANGUAGE Page no: . or several of a model’s diagrams. Within its application window. It also enables teams to reuse large. it displays each diagram in a diagram window and each specification in a specification window. called Model Integrator to compare and merge models and their controlled units. icons representing a model element can appear in none. using facilities provided by its application window. Roses uses the UML to provide graphical method for non-programmers wanting to model business process as well as programmers modeling application logic. It provides a separate tool .scale design assets developed in earlier modeling efforts by providing the possibility to add frame works in Rational Rose.GITAM INSTITUTE OF TECHNOLOGY NAME: T. relationship and property icons appear on each diagram. The application therefore enables you to control. JAHNAVI ROLL NO: 1220609110 and their model properties. Since diagram is used to illustrate multiple views of a model.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Point of Sale System Point of Sale System AIM: To create a Point of Sale System UNIFIED MODELING LANGUAGE Page no: .

Pay Bill. JAHNAVI ROLL NO: 1220609110 STEP 1: Start the application STEP 2: Create the require actors and use cases in the browser window STEP 3: Goto new use case view and then click the use case view and open a new package STEP 4: Rename the new package with the package with required names STEP 5: Create two packages actor and use case Class diagram: UNIFIED MODELING LANGUAGE Page no: . 5. Buy product 7. cashier USECASES: 1. Update Inventory ALGORITHMIC PROCEDURE: NAME: T. Bar code scanning 2. Close sale 4. Process sale 3.GITAM INSTITUTE OF TECHNOLOGY ACTORS: 1. Tax calculation 6. customer 2.

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY Use Case Diagram : NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY POS system sequence diagram NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 Process sale collaboration diagram UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY Process sale sequence diagram NAME: T.

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY POS system activity diagram NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 Component Diagram Point of scale RESULT: Thus various UML Diagrams were generated for POINT OF SALE SYSTEM and the corresponding code was generated using Visual Basic.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 ONLINE BOOK SHOP SYSTEM UNIFIED MODELING LANGUAGE Page no: .

Scope: The specification defines the non-functional requirements of the system. References: Amazon. Tigris. 98 . Usability: compliant. such as reliability. BN. This specification lists the requirements that are not readily captured in the use cases of the Use case model.  The system shall provide access to catalog database with no more then ten seconds latency.com Functionality: Multiple users must be able to perform work concurrently.GITAM INSTITUTE OF TECHNOLOGY NAME: T. The functional requirements are defined in the use case specifications.  The system must be able to complete 80% of all transactions within 2 minutes. usability. performance and supportability. JAHNAVI ROLL NO: 1220609110 ONLINE BOOK SHOP SYSTEM ONLINE BOOKSHOP SYSTEM SPECIFICATIONS: Objectives: The purpose of this document is to define requirements of the online bookshop system. Performance:  The system shall support large number of simultaneous users against the central database at any time. The user must be notified about the stock of books in the inventory. UNIFIED MODELING LANGUAGE Page no: The system shall be available 24 hrs a day and 7 days a The desktop user-interface shall be Windows 95.com.com. The supplementary specifications and the use case model together capture a complete set of requirement on the system. Reliability: week.

If the user cannot find a book in current category. An internet customer should have a login to access the book store. The proposed system should allow the customer with activities from logging on to the system. browsing the book store. JAHNAVI ROLL NO: 1220609110 Supportability: None Brief Description of the Project: The current project emphasizes on analysis and design of an online bookshop system. The shipment details are entered by the customer and through those details the delivery is processed. Publishers. author and book category. selecting items and making purchases are described. selecting items and making purchases i. the customer can browse the current book catalogue online and this should detail the book details and stock details for the books. That serves the customers needs. This includes details like Author. The system should be competitive enough by providing the facilities/options that are currently provided by reputed systems like Amazon. PROBLEM STATEMENT FOR ONLINE BOOKSHOP SYSTEM As a young promising student you are tasked with developing an online book shop system. UNIFIED MODELING LANGUAGE Page no: . Title. The payment is done through credit card and also through gift cheques etc. Book Name and Category. the customer is informed about the transaction details through e-mails. they should place an order and request the book. the customer will be able to browse... Registration of the customer with the book shop is primary. The new system should even assist the customer in locating a book in that.com. The user should be able to filter by book title. select and buy books online.e.GITAM INSTITUTE OF TECHNOLOGY NAME: T. A registered customer can browse through the book catalogue and can make selections. The customer’s available activities in the proposed system from logging on the browsing the book store.com and BN.

A use case represents a discrete unit of interaction between a user and the system. Separate the generalized and specialized actors.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Functionality or behavior of actors is considered as use cases. use collaborations to realize use cases. 5. Draw the lines around the system and actors lie outside the system. Each use case has a description which describes the functionality that will be built in a proposed system. Specify the generalized and specialized use cases. A use case is a single unit of meaningful work. 2. JAHNAVI ROLL NO: 1220609110 USE CASE The use case model describes the proposed functionality of the system. 7. ACTORS: Customer and Book shop staff USE        CASES: Registration Login Create order Book catalog Manage cart and payments Order status Inventory RELATIONSHIPS USED:  Association  Dependency  Composition Modeling steps for Use case Diagram 1. 4. A use case may ‘include’ another use case functionality or ‘extend’ another use case with its own behavior. If necessary. UNIFIED MODELING LANGUAGE Page no: . Identify the actors which are interacting with the system. Adorn with constraints and notes. Identify the functionality the way of interacting actors with system and specify the behavior of actor. 6. Se the relatonship among the use cases and in between actor and use cases. 3.

UNIFIED MODELING LANGUAGE Page no: . Lay the association links first represent structural connection. whether it is system. 4. attach each subsequent message to appropriate link. 3. subsystem. Set the pre and post conditioned. 2. Starting with the message that initiates this interaction. Start the message which is initiating interactions and place all other messages in the increasing order of items. Adorn each message with time and space constraints if needed 7. Identify the objects that play a role in the interaction. Attach pre & post conditions to specify flow of control formally. Modeling steps for Collaboration Diagrams 1. Lay out other links and adorn with stereotypes. setting sequence number as appropriate. place a duplicate object. placing important objects in centre and neighboring objects to outside. classes. Specify the links among these objects. Set the stages for the interactions by identifying objects which are placed as actions in interaction diagrams. Set the context for the interactions. object or use cases. subsystem. 6. 2.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Set the initial properties of each of these objects. Set the lifelines for each and every object by sending create and destroy messages. Lay them as vertices in graph. 5. Specify the time and space constraints. update with these new values and connect them by a message stereotyped as become or copy. system. JAHNAVI ROLL NO: 1220609110 Modeling steps for Sequence Diagrams 1. 5. 7. If the attributes or tagged values of an object changes in significant ways over the interaction. Set the context for interaction. operation or class or one scenario of use case or collaboration. 4. Lay them out along the X-axis by placing the important object at the left side and others in the next subsequent. 3. 6.

4. Modeling steps for State chart Diagram 1. In either case. UNIFIED MODELING LANGUAGE Page no: . fork and joining. 2. create a swim lane for each important object. 7. Consider ways to simplify your machine by using substates. Check that no state is a dead from which no combination of events will transition the object out of that state. 9. Decide on the meaningful partial ordering of stable states over the lifetime of the object. Adorn with notes tagged values and so on. consider branching. a use case.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Model these events as triggers to transitions that move from one legal ordering of states to another. These objects may be real or abstract. JAHNAVI ROLL NO: 1220609110 Modeling steps for Activity Diagrams 1. 2. joins and history states. 3. 4. 3. For complicated actions.whether it is a class. Start with the high-level states of the objects & only then consider its possible substrates. 7. 6. 8. Decide on the events that may trigger a transition from state to state. forks. Start with sequential flows. Render the transitions that connect these activities and action states. Beginning at initial state. Check that all states are reachable under some combination of events. specify the activities and actions and render them as activity states or action states. Choose the initial & final states of the objects. collapse these states and provide separate activity diagram. 8. Select the object that has high level responsibilities. 5. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. branches. 5. or the system as a whole. Identify the precondition of initial state and post conditions of final state. Choose the context for state machine. Attach actions to these transitions and/or to these states. 6. or for a set of actions that appear multiple times.

Use either import or export relationship in b/w interfaces & components. constraints and notes. Modeling steps for Class Diagrams 1. Set the relationship among all the things. Show the existing relationships among them generally dependency. 2. 3. documents which are interacting with the system. 2. 7. UNIFIED MODELING LANGUAGE Page no: . 5. 7. 3. Represent this executables and libraries as components. to check it against expected sequence of events & their responses. Set attributes and operation signatures for interfaces. Identify the generalization and specification classes. Identity the things that are interacting with class diagram. 4. Set the responsibilities. subsystem which are collaborated with mechanisms. Modeling steps for Component Diagrams 1. 3. tables.Trace through the state machine. Identify the classes. 2. 9. Modeling steps for Object Diagrams 1. Set the values of attributes and states of objects. 6. Identify the component libraries and executable files which are interacting with the system. 6.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Show the relationships among all the components. Specify the links among all these objects. Identify the mechanisms which you would like to model.documents as components. JAHNAVI ROLL NO: 1220609110 10.tables. Represent files. 5. Identify the relationship among all objects. Render all these classes as objects in diagram. either manually or by using tools. 4. Adorn with tagged values. 5. 8. 10. Identify the files. Identify the seams in the model. interface. Set the attributes and operations. 4. 6. Walk through the scenario until to reach the certain point and identify the objects at that point. Identify the interfaces which are interacting with the system. use cases.

2. The description for each of them is described clearly. 13. Set the version of the source code as a constraint to each source code. Specify the components which are living on nodes. Represent source code as components. Classes may be inherited from other classes. Provide the visual cue via stereotype classes. have other classes as attributes. The class diagram for the proposed system has several classes. JAHNAVI ROLL NO: 1220609110 11. 12. Provide the attributes & operations. Modeling steps for Deployment Diagram 1.GITAM INSTITUTE OF TECHNOLOGY NAME: T. constraints and tag values. Adorn with nodes & constraints & draw the deployment diagram. Identify the processors which represent client & server. The classes include  Book shop staff  Book  Bookshop  Item  Customer  Shopping cart  Order  Item order  Shipping address and billing address. 7. Adorn with nodes. CLASS DIAGRAM: A Class is a standard UML construct used to detail the pattern from which objects will be produced at run time. delegate responsibilities to other classes and implement abstract interfaces. Group all the similar clients into one package. 14. Provide the links among clients & servers. 5. 4. Identify the source code which is interacting with the system. 6. A class is a specification. These classes have attributes and operations. 15. UNIFIED MODELING LANGUAGE Page no: . 3.an object is an instance of a class. Show the relationships among components.

The contents of the packages are as follows: PACKAGE-1: BOOKSHOP This package consists of following classes: 1. JAHNAVI ROLL NO: 1220609110 PACKAGES: The class diagram of the online book shop system is shown to be grouped into three packages. Order 2. Bookshop staff 2. Bookshop 4. Shopping Cart UNIFIED MODELING LANGUAGE Page no: . Book 3. Item PACKAGE-2: CUSTOMER This package consists of following classes: 1. Address 3. Billing Address 4. Shipping Address PACKAGE -3:ONLINE ORDERING This package consists of following classes: 1. Customer 2. Item Order 3.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 CLASS DIAGRAM: UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 USE CASE DIAGRAM FOR ONLINE BOOKSHOP SYSTEM: UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 UML provides a graphical means of depicting object interactions over time in sequence diagrams. These typically show a user or actor and the objects and components they interact with in the execution of a use case. customer registration 1: login request login create order book catalog inventory bookshop staff cart shippment details payment consortinum database 2: manages 3: updates 4: update 5: verify 6: register first 7: registered logon request 8: verify 9: logon successful 10: create order 11: select books 12: verify 13: stock ok 14: confirm selection 15: add to cart 16: shippment details 17: payment 18: delivered successfully UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY SEQUENCE DIAGRAM: NAME: T.

registrat ion login 5: verify create order 11: select books book catalog 10: create order 1: login request 7: registered logon request 6: register first 15: add to cart payme nt 4: update 12: verify consorti cart 8: verify shippment num details 16: shippment details 17: payment bookshop custom staff er 18: delivered successfully 3: updates 9: logon successful 13: stock ok databa se 14: confirm selection 2: manages invent ory UNIFIED MODELING LANGUAGE Page no: . interfaces and other elements that work together to provide some cooperative behavior that is bigger than the sum of all its parts. Collaboration diagram emphasis is based on structural organization of the objects that send and receive messages. JAHNAVI ROLL NO: 1220609110 COLLOBORATION DIAGRAM: Collaboration names a society of classes.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. A state chart diagram shows the possible states of the object and the transitions that cause a change in state. selections valid login mainscreen browse screen select create order choose listed books in catalog add to cancel can't find wait for result cancels wait for view details cart confirm transaction success display thank u screen search by author. JAHNAVI ROLL NO: 1220609110 STATE CHART DIAGRAM: Objects have behaviors and state.title. The state of an object depends on its current activity or condition.isbn return to view shipping details not satisfied invalid transaction wait for transaction details UNIFIED MODELING LANGUAGE Page no: . The initial state (black circle) is a dummy to start the action. Final states are also dummy states that terminate the action.

Activity diagrams can be divided into object swim lanes that determine which object is responsible for which activity. connecting it to the next activity. an activity diagram focuses on the flow of activities involved in a single process. While a state chart diagram focuses attention on an object undergoing a process (or on a process as an object). Activity diagrams and state chart diagrams are related.GITAM INSTITUTE OF TECHNOLOGY NAME: T. The activity diagram shows the how those activities depend on one another. A single transaction comes out of each activity. JAHNAVI ROLL NO: 1220609110 ACTIVITY DIAGRAM: An activity diagram is essentially a fancy flowchart. display welcome msg get login rejected get pwd and validate accepted display item info accept selection more selections completed display order acceptance ship to customer create order for cart rejected UNIFIED MODELING LANGUAGE Page no: .

address.java central server.c lass books.cl ass central server. JAHNAVI ROLL NO: 1220609110 COMPONENT DIAGRAM: A component is a code module.dll item. Components are shown as rectangles with two tabs at the upper left. Component diagrams are physical analogs of class diagram. class bookstaff.db bookshop.java order. Each component belongs on a node.java item.class bookstaff.ja va order.java bokshop.class central database address.class/.class book.db items.db UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.java address.db order.java book.

JAHNAVI ROLL NO: 1220609110 Deployment diagram shows the physical configurations of software and hardware.GITAM INSTITUTE OF TECHNOLOGY DEPLOYMENT DIAGRAM: NAME: T. UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 RESULT: Thus various UML Diagrams were generated for ONLINE BOOK SHOP and the corresponding code was generated using Visual Basic. UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

JAHNAVI ROLL NO: 1220609110 AN ONLINE AUCTION SALE UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

5. The auctioneer requesting the product for the cut-off price is given priority. Page no: UNIFIED MODELING LANGUAGE . State chart diagram shows states before and after each action. To accomplish this purpose the user has to access the site. After the transaction by going back to the main menu where he can view other items. 1. Class diagram for initially identified classes. The users are allowed to bid for any price according to their wish provided it’s more than the minimum price of auction.GITAM INSTITUTE OF TECHNOLOGY NAME: T. As per case study. Sequence and collaboration diagrams. 2. 3. the following analysis diagrams will be created. Incase it’s a new user he has to register. JAHNAVI ROLL NO: 1220609110 AN ONLINE AUCTION SALE Aim: To create a case study on ONLINE AUCTION Overview: The online auction system is a design about a website where sellers collect and prepare a list of items they want to sell and place it on the website for visualizing. Activity diagram to show flow of each use case. The purchaser gets a confirmation of his purchase as an acknowledgement from the website. He can pay the amount directly and own the product. 4. Use cases for the system. Conceptualization: Assumptions:     The users are allowed to register and give user id’s to have identification. Interacting with the purchasers and sellers in the chat room does this. If the auctioneer or the purchaser does not want to bid for the product then there is fixed cutoff price mentioned for every product. The fixed cut-off price is decided and confirmed for every product. Purchaser logs in and selects items they want to buy and keep bidding for it. The purchaser making the highest bid for the item before the close of the auction is declared as the owner of the item.

 Pay final price and bid the product. Fix or bid for the price. JAHNAVI ROLL NO: 1220609110 The auctioneer bidding the maximum price is given the product. Bidding price of the auctioneer. An Auction Simulation:     Bid for the product. Pay the price and log out. Outputs:     The cut-off price for each product. Purchaser 2. Log on to the site. Acknowledgement to whom the product is sold.  Loop  Check any product details. Actors: 1.  Check for cutoff price.GITAM INSTITUTE OF TECHNOLOGY  Inputs:     NAME: T. Updated status of bid price. List of available products on the site. Key Terms:    Get details and bid the product. The login details of the auctioneer. Seller UNIFIED MODELING LANGUAGE Page no: . Details such as specifications and the price of each product. Deliver the product. Function points  Bidder request product details. Status of each product if it is bid or sold for sale.

5. 3.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Record chatting. ALGORITHMIC PROCEDURE: STEP 1: Start the application STEP 2: Create the require actors and use cases in the browser window STEP 3: Got new use case view and then click the use case view and Open a new package STEP 4: Rename the new package with the package with required Names STEP 5: Create two packages actor and use case UNIFIED MODELING LANGUAGE Page no: . 8. Login Seller Purchaser Chatting Select Method of bidding Select Method of Auction Buy Goods Register for goods Select history of database Use Cases In Purchaser’s Diagram: 1. 9. Validate User 2. 7. 2. JAHNAVI ROLL NO: 1220609110 Use Cases in Auction System 1. 4. 6.

Specify the time and space constraints. 4. 8. Draw the lines around the system and actors lie outside the system. subsystem. 6.GITAM INSTITUTE OF TECHNOLOGY NAME: T. 9. Se the relationship among the use cases and in between actor and use cases. JAHNAVI ROLL NO: 1220609110 DIAGRAMS: Modeling steps for Use case Diagram 1. 3. Adorn with constraints and notes. 3. use collaborations to realize use cases. Set the context for the interactions. 7. 2. classes. object or use cases. 6. 5. Set the pre and post conditioned. 5. Set the lifelines for each and every object by sending create and destroy messages. Functionality or behavior of actors is considered as use cases. UNIFIED MODELING LANGUAGE Page no: . Specify the generalized and specialized use cases. system. Identify the functionality the way of interacting actors with system and specify the behavior of actor. 7. Modeling steps for Sequence Diagrams 1. 4. 2. Start the message which is initiating interactions and place all other messages in the increasing order of items. Lay them out along the X-axis by placing the important object at the left side and others in the next subsequent. Separate the generalized and specialized actors. If necessary. Identify the actors which are interacting with the system. Set the stages for the interactions by identifying objects which are placed as actions in interaction diagrams.

7. 3. 2. setting sequence number as appropriate. subsystem. Attach pre & post conditions to specify flow of control formally. If the attributes or tagged values of an object changes in significant ways over the interaction. UNIFIED MODELING LANGUAGE Page no: . Set the context for interaction. 8. Lay out other links and adorn with stereotypes. JAHNAVI ROLL NO: 1220609110 Modeling steps for Collaboration Diagrams 1. Beginning at initial state. Adorn each message with time and space constraints if needed 7. Modeling steps for Activity Diagrams 1. Identify the precondition of initial state and post conditions of final state. Set the initial properties of each of these objects. 6. 5. Lay the association links first represent structural connection. Adorn with notes tagged values and so on. create a swim lane for each important object. 4. collapse these states and provide separate activity diagram. fork and joining. 4. Lay them as vertices in graph. 6. place a duplicate object. consider branching. Render the transitions that connect these activities and action states.GITAM INSTITUTE OF TECHNOLOGY NAME: T. specify the activities and actions and render them as activity states or action states. Identify the objects that play a role in the interaction. operation or class or one scenario of use case or collaboration. 3. For complicated actions. placing important objects in centre and neighboring objects to outside. Start with sequential flows. In either case. 2. 5. Select the object that has high level responsibilities. These objects may be real or abstract. attach each subsequent message to appropriate link. Specify the links among these objects. update with these new values and connect them by a message stereotyped as become or copy. whether it is system. Starting with the message that initiates this interaction. or for a set of actions that appear multiple times.

Set the relationship among all the things. Choose the initial & final states of the objects. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. branches. Identify the generalization and specification classes. 3. Decide on the events that may trigger a transition from state to state. a use case. joins and history states.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Check that all states are reachable under some combination of events. 3. JAHNAVI ROLL NO: 1220609110 Modeling steps for State chart Diagram 1. 4. Attach actions to these transitions and/or to these states. 6. to check it against expected sequence of events & their responses.Trace through the state machine. either manually or by using tools. Adorn with tagged values. 5. 7. 4. UNIFIED MODELING LANGUAGE Page no: . Check that no state is a dead from which no combination of events will transition the object out of that state. 10. Consider ways to simplify your machine by using substates. or the system as a whole. Choose the context for state machine. Identity the things that are interacting with class diagram. 9. 6. 8. 2. constraints and notes. Set the attributes and operations. forks. Set the responsibilities. Decide on the meaningful partial ordering of stable states over the lifetime of the object. Start with the high-level states of the objects & only then consider its possible substrates. 5. 2. Modeling steps for Class Diagrams 1. whether it is a class. Model these events as triggers to transitions that move from one legal ordering of states to another.

5. 10. UNIFIED MODELING LANGUAGE Page no: . 11. Specify the links among all these objects. 4. Set the values of attributes and states of objects. 2. Represent source code as components. 12. 4. subsystem which are collaborated with mechanisms. 7. 6. 2. Identify the source code which is interacting with the system. Use either import or export relationship in b/w interfaces & components. 8. Show the existing relationships among them generally dependency. Show the relationships among all the components. Adorn with nodes. Represent this executables and libraries as components. 6. Identify the classes. 5. Set attributes and operation signatures for interfaces. Walk through the scenario until to reach the certain point and identify the objects at that point. Modeling steps for Component Diagrams 1. Identify the mechanisms which you would like to model. Show the relationships among components. JAHNAVI ROLL NO: 1220609110 Modeling steps for Object Diagrams 1. Identify the interfaces which are interacting with the system. 3. interface. 15.GITAM INSTITUTE OF TECHNOLOGY NAME: T.documents as components. 3. 14. constraints and tag values. 7. Represent files. Identify the component libraries and executable files which are interacting with the system. Set the version of the source code as a constraint to each source code. Render all these classes as objects in diagram. Identify the relationship among all objects. documents which are interacting with the system. 13. use cases. 9. Identify the files.tables. Identify the seams in the model. tables.

6. Identify the processors which represent client & server. JAHNAVI ROLL NO: 1220609110 Modeling steps for Deployment Diagram 1. 5. 2. Group all the similar clients into one package. Specify the components which are living on nodes.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Adorn with nodes & constraints & draw the deployment diagram. 7. 3. UNIFIED MODELING LANGUAGE Page no: . Provide the links among clients & servers. Provide the visual cue via stereotype classes. 4. Provide the attributes & operations.

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY Class Diagram: NAME: T.

GITAM INSTITUTE OF TECHNOLOGY Use case Diagram: NAME: T. JAHNAVI ROLL NO: 1220609110 login search for product request/send details BIdder Auctioner bid the product buy/sell the product pay the price deliver the product UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY Sequence diagram: NAME: T. JAHNAVI ROLL NO: 1220609110 s:site : BIdder a:auctioner p:product login search request product details get details display details pay final price or bid for product update bid price check for product give ackn if suitable for selling buy the product pay price logout UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY Collaboration Diagram: s:site NAME: T. JAHNAVI ROLL NO: 1220609110 1: login 12: logout 2: search 8: check for product p:product 5: display details 9: give ackn if suitable for selling 4: get details 3: request product details 6: pay final price or bid for product 7: update bid price 10: buy the product 11: pay price : BIdder a:auctione r UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 log on to the site search for the product request details bid the final price and buy the product yes if final fixed price suitable no bid for the product check for the cutoff price if suitable for selling wait for the next bid no sell/buy the product pay the price UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY ActivityDiagram: NAME: T.

GITAM INSTITUTE OF TECHNOLOGY State chart diagram: NAME: T. JAHNAVI ROLL NO: 1220609110 wait for request requested product details wait for the desicion Bid the price wait to update bid price bid for a higher price wait for bid price to meet cut off compare the bidding price with cutoff wait until next bid comes sell / but the product wait for payment UNIFIED MODELING LANGUAGE Page no: .

db UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 COMPONENT DIAGRAM: name list of prices central server java web host central server class site customer Central database product.

JAHNAVI ROLL NO: 1220609110 AN AIRPORT SIMULATION UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

ATC Controller 2.Threaded Airport Simulation Actors: ATC Controller Use Cases 1. Terminal 9. Decision Support System 3.Threaded Airport Simulation Aim: to create a Multi. Available 10. Planning 4. Runway 8. Emergency 5.GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 A Multi. Sensor 6. Gateway 7.Waiting Queue Algorithmic Procedure: STEP 1: Start the application STEP 2: Create the require actors and use cases in the browser window STEP 3: Go to new use case view and then click the use case view and Open a new package STEP 4: Rename the new package with the package with required Names STEP 5: Create two packages actor and use case UNIFIED MODELING LANGUAGE Page no: .

time delays. The critical step of the project was to design an airport modeling and simulation infrastructure to improve the safety and efficiency of ground movements in all whether conditions. Activity diagram to show flow for each use case. assign planes to runways. they may take off. It simulates the arrivals and departures at an airport in a time sequence.  Planes arrive for landing at random times. they may land. State chart diagram shows states before and after each action. UNIFIED MODELING LANGUAGE Page no: . 5. or they may crash.GITAM INSTITUTE OF TECHNOLOGY Overview NAME: T. Class diagram for initially identified classes. planes may enter the systems. runway and terminal. but with a specified probability of a plane arriving during any given minute. As part of case study. literally from the airspace to the curb. So the finally made computer software should model various aspects of the total airports operation-connecting airside and landside. 4.  All take offs take the same amount of time and all landings take the same amount of time (through these two times may be different). During every minute.particularly in poor whether conditions. following analysis diagrams will be created 1. The project must keep track of planes. Sequence and Collaboration diagram. execute the take offs and landings.  Planes arrive for take off at random times. 3. etc. and keep track of status of each plan. Use cases for the system. 2. Conceptualization Assumptions. The project is focused on controller and pilot assistance systems for approach and ground movements. JAHNAVI ROLL NO: 1220609110 A critical step of the project is to design a modeling and simulation infrastructure to experiment and validate the proposed solutions The ever growing demand of air transport shows the vulnerability of the current air traffic management system: Congestion. but with a specified probability of a plane arriving during any given minute  Landings have priorities over takeoffs.

 The statues of each runway.Check the status of each terminal.  Airport: runways. Get the plane landed safely. Update status of runway and terminal. Transmit/receive signals. The average time a plane spent in the landing queue.  The maximum minutes until a plane waiting to land will crash. pilots.  Function points: 1.  The probability of a plane entering the landing queue in any given minute. plane and terminal. and terminal.Validate if terminal suitable for particular aircraft. terminals. The       Output of the program will be: Total simulation time. Pilot sends signals for takeoff/landing. JAHNAVI ROLL NO: 1220609110  Planes arriving for landing have a random amount of fuel and they will crash if they do not land before they run out of fuel.Finalize a free runway.  The amount of time needed for one plane to takeoff.  The probability of a plane entering the takeoff queue in any given minute. Input will be:  The amount of time needed for one plane to land. 3. Loop . model no. . plane. planes. cockpit. control room.Assign terminal to aircraft. 6. .  Aircraft: passengers. Key terms:  Aircraft simulation. 2. Updated status of each runway.GITAM INSTITUTE OF TECHNOLOGY NAME: T. The number of planes that takeoff in the simulated time. Loop . UNIFIED MODELING LANGUAGE Page no: . 5. The number of planes that landed in the simulated time. 7. .Assign the runway to the plan. Check if time left for next departure.Check status of each runway. The average time a plane spent in the takeoff queue. 4. .

 Transmit/receive signals. Update status of terminal.  Update status of runway.  Check for free terminal. Transmit/receive signals: The pilot in the aircraft transmits signals for requesting a free runway to takeoff or land. He is responsible for the safe landing or takeoffs the planes. 2. He transmits or receives signals regarding the free runways. Requirement Analysis: NAME: T. 1. 2. Use cases: The steps involved in the whole process are indicated as use cases. terminal. Get the plane parked in the terminal.  Land the plane. UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 Textual Analysis: This covers the requirements and diagrams of the project. The complete simulation of airport control system as follows Actors: These are who are involved in interaction of the whole process. Pilot: He is the person who controls the aircraft. Land the plane: The plane is landed safely on the airport as per directions given by the control room regarding runway and timings. If this is going to be free then runway number is transmitted to the pilot on aircraft.  Check availability of runways. The control room on the ground receives these signals from the aircrafts. Technical head: He is the person who supervises the controls the ground traffic on runway.GITAM INSTITUTE OF TECHNOLOGY 8. Check availability of runway: The status of each runway in the airport is checked if it’s free and its going to be free until the particular aircraft is landed or takeoff.  Check if time left for next departure. 9. 3. He checks the status of runways and assigns the free runways and terminals for takeoff and landing. 1. and terminal from the control room.

He transmits or receives signals regarding the free runways and terminals from the control room. delegate responsibilities to other classes and implement abstract interfaces. A class is a specification. Classes of airport simulation are: UNIFIED MODELING LANGUAGE Page no: . Then that particular terminal has to be assigned to the plane. Check if time left for next departure: If the plane leaves immediately after landing then assign again a runway for takeoff. 2.an object is an instance of a class. 6. It should be checked whether that particular model of plane fits into that terminal. Takeoff/land: The leaving of planes is called takeoff and coming back to runway is called landing. Diagrams: Class Diagram A Class is a standard UML construct used to detail the pattern from which objects will be produced at run time. If there is still time then the plane has to be parked in a terminal. Check availability of terminals: the status of each terminal is to be checked to find a free terminal. 4. This should be supervised carefully to avoid collisions and crashes of aircrafts. have other classes as attributes. The status has to be immediately changed as soon as the work is complete. 5. Control Room: he is the person who supervises the controls the ground traffic on runway. Plane Cockpit: He is the person who controls the aircraft. Update Status: the status of runway and terminal are to be set to be using while using them. The runway is used for either purpose. JAHNAVI ROLL NO: 1220609110 4. He is responsible for the safe landing or takeoff of the plane. 3. The terminal is to be parked in it. 5. Runway: This is the part the planes use to land or takeoff only one plane can use runway at a time to takeoff or land. Classes: The classes contain the attributes and operations related to them the main classes classified in this solution are: 1.GITAM INSTITUTE OF TECHNOLOGY NAME: T. He checks the status of runways and assigns the free runways and terminals for takeoff and landing. Terminal: This is the place where the planes are parked until the next departure. Classes may be inherited from other classes.

GITAM INSTITUTE OF TECHNOLOGY Class Control Room Attributes -Technical head -No of staff -systems to control NAME: T. JAHNAVI ROLL NO: 1220609110 Takeoff/Landing Plane Cockpit -Runway no -Flight no -Status -Time taken -No of pilots -Flight no -Destination -Timings Operations +Receive signals from planes() +Check for free runway() +Send runway no() +Check for next departure() +Look for free terminal() +Send terminal no to plane() +Get plane parked() +Update status of runway after each take of or landing() +Send signal to ground station() +Receive runway no() +Land on runway() +Request terminal if time left for next departure() +Receive terminal no() +Get the plane parked in the terminal() -----------------------+Update status of runway after each takeoff/landing() Terminal Runway -No of runways -Size of terminal -Flight model which fits in -Status of terminal -No of runways -Length of runway Status of runway -Free timings -Runway no UNIFIED MODELING LANGUAGE Page no: .

He checks the status of runways and assigns free terminals for takeoff and landing.Get the plane into the free UNIFIED MODELING LANGUAGE Page no: .Look for free terminal .Transmit/Receive signals . These typically show a user or actor and the objects and components they interact with in the execution of a use case.Give acknowledgment about the timings to control Terminal Sequence diagram UML provides a graphical means of depicting object interactions over time in sequence diagrams. JAHNAVI ROLL NO: 1220609110 The use case model describes the proposed functionality of the system. A use case may ‘include’ another use case functionality or ‘extend’ another use case with its own behavior. He transmits or Receives signals regarding the free runways and terminal from the control room. .Transmit/Receive signals . A use case represents a discrete unit of interaction between a user and the system. 1. Pilot: He is the person who controls the aircraft. He is responsible for the safe landing or takeoff the planes.GITAM INSTITUTE OF TECHNOLOGY Use Case Diagram NAME: T.Get the plane parked in the free Terminal pilot .Land or takeoff the plane Safely . A use case is a single unit of meaningful work. 2.Give directions to aircraft . Technical head: He is the person who supervises the controls the ground traffic on runway.Look for free runway . Actors Use cases Technical head .Check whether conditions . Each use case has a description which describes the functionality that will be built in a proposed system.

Whether Conditions: The whether department decodes the atmospheric data files from the current whether conditions and sends them to the control room. The terminal differs in size and shape. Terminal: This is the place where the planes are parked until the next departure. 2. The runway is used for either purpose. 3. Runway: This is the path the plane uses to land or takeoff. Activity diagrams can be divided into object swim lanes that determine which object is responsible for which UNIFIED MODELING LANGUAGE Page no: . The activity diagram shows the how those activities depend on one another. He transmits or receives signals regarding the free runways and terminal fro the control room. He is responsible for the safe landing or takeoff of the planes. Collaboration Diagram Collaboration names a society of classes. an activity diagram focuses on the flow of activities involved in a single process. Only one plane can use a runway at a time takeoff or landing. JAHNAVI ROLL NO: 1220609110 Objects 1. Activity diagrams and state chart diagrams are related. Takeoff/Landing: The leaving of plane is called takeoff and coming back to runway is called landing. 4. The systems in the control room checks whether the condition is suitable for landing the planes. 5. interfaces and other elements that work together to provide some cooperative behavior that is bigger than the sum of all its parts. Activity Diagram An activity diagram is essentially a fancy flowchart. Cockpit: He is the person who controls the aircraft.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Collaboration diagram emphasis is based on structural organization of the objects that send and receive messages. The plane suitable for that particular terminal is to be parked in it. While a state chart diagram focuses attention on an object undergoing a process (or on a process as an object).

GITAM INSTITUTE OF TECHNOLOGY NAME: T. Component diagrams are physical analogs of class diagram. Final states are also dummy states that terminate the action. connecting it to the next activity. A single transaction comes out of each activity. A state chart diagram shows the possible states of the object and the transitions that cause a change in state. Component Diagram A component is a code module. State Chart Diagram Objects have behaviors and state. Each component belongs on a node. The state of an object depends on its current activity or condition. Deployment Diagram Deployment diagram shows the physical configurations of software and hardware. JAHNAVI ROLL NO: 1220609110 activity. The initial state (black circle) is a dummy to start the action. UNIFIED MODELING LANGUAGE Page no: . Components are shown as rectangles with two tabs at the upper left.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Class Diagram: UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 Use Case Diagram: send/receive signal check availability of run awy send/receive run way num land / aircraft send / receive terminals numbers Control room Plane cockpit check free terminals send / receive terminal numbers park aircraft update status of runway UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Sequence Diagram: Airport Simulation : control room 1: request signal 2: send signal 3: Check Weather conditions 4: send acknowledgement 5: check avaliable for run way 6: wait signal 7: send signal 8: send ack 9: update runway status 10: if time is for next dep send req 11: if terminal is free send terminal no 12: send terminal 13: land aircraft 14: update status of terminal p:prane Cockpit T:terminal R:runway W:WeatherD ept UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY Collaboration Diagram: NAME: T. JAHNAVI ROLL NO: 1220609110 p:prane Cockpit 1: request signal 6: wait signal 7: send signal 8: send ack 12: send terminal 13: land aircraft : control room 5: check avaliable for run way 9: update runway status 10: if time is for next dep send req 11: if terminal is free send terminal no 14: update status of terminal T:termin al 2: send signal 4: send acknowledgement R:runwa y 3: Check Weather conditions W:Weather Dept UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY Activity Diagram: NAME: T. JAHNAVI ROLL NO: 1220609110 Runway allocation for takeoff Activity Diagram landing give aircraft info to lock s/m lock system checking for ks no acquire landing area lock all locks are locked yes priority acquire runway lock landing on another runway acquire terminal lock aircraft at take off area if the aircraft is at takeoff area then release terminal and taxiing locks while moving from takeoff area release takeoff area lock and acquire runway lock acquire taxiing lock move to the terminal gate and release terminal and taxiing lock UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 takeoff acquire terminal lock give aircraft info to lock s/m checks for locks if locks are available acquire takeoff area lock acquire taxiing lock aircraft at takeoff area acquire runway lock if the aircraft is at the takeoff area then release terminal and taxiing lock while moving from takeoff area release takeoff area lock and acquire runway lock use the runway for takeoff and release runway lock UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY Runway allocation for takeoff Activity Diagram NAME: T.

JAHNAVI ROLL NO: 1220609110 State Chart Diagram: wait for weather conditions req runway status wait for running status req runway no wait for runway no avail not avail wait for terminal status if time left land on runway avail not avail wait for terminal no not avail avail halt UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Component Diagram: terminal lock.class landing.db priority.java central server java landing.cla ss takeofflock . java terminalloc k.jav a takeofflock .class / . class central database airport.db UNIFIED MODELING LANGUAGE Page no: .java central server .dll taxiinglock.class taxiinglock.

JAHNAVI ROLL NO: 1220609110 Deployment Diagram: <<DATA BASE>> central database <<SERVER>> central server <<WIRELESS COMMUNICATION>> <<DEVICE>> <<DEVICE>> <<DEVICE>> <<DEVICE>> control manager aircarft controlor lockmanager taxiing manager UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 Result: The various UML diagrams were drawn for AIRPORT SIMULATION SYSTEM application and the corresponding code was generated.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

JAHNAVI ROLL NO: 1220609110 A SIMULATED COMPANY A SIMULATED COMPANY UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

o o o o o Usecase for the system Class diagram for initially identified classes. Activity diagram to show flow for each use case. The project if focused on the user to take lend. Statechart diagram shows states before and after each action. The sales has to submit the record and stock details required. As part of the case study. The performance department has to prepare record statistics as given by marketing department. The performance department has to get collected details from all the departments and submit to the company. The sales person has to sell the foods and update the details in the record. This application is called simco: Simulated Company. In addition details such as inventory and sales are updated. following analysis diagrams will be updated. The company accounts are updated for a given month. The accounts take into the gross profits from the sales. purchase a machine and over a series of monthly and yearly production runs follows the concept of the company. It has to purchase machinery and start the production. Inputs: UNIFIED MODELING LANGUAGE Page no: . The company has to see all the takings and the losses. Conceptualization: Assumptions: The company has to take the loan and repay the loan. Simulated company is an example that shows the documents produced when undertaking the analysis and design of an application that simulates a small manufacturing company. General expenses such as salary and rent are taken into account to calculate the net profit for the company. Sequence and collaboration diagrams. They have to see all dealings of the company and see the additional features of the machine for better development. JAHNAVI ROLL NO: 1220609110 A critical step of the project is to design a modeling and simulation infrastructure to experiment and validate the proposed solutions.GITAM INSTITUTE OF TECHNOLOGY OVERVIEW: NAME: T.

Case study of the project. Identify the functionality the way of interacting actors with system and specify the behavior of actor. 7. use collaborations to realize use cases. 9. 6. 3. Identify the actors which are interacting with the system.  The probability of estimating profit and loss. Sell the products and updated the records. The number of goods manufactured in a simulated time. JAHNAVI ROLL NO: 1220609110  The amount of time required for sanctioning the loan.  The probability for estimating the machinery cost and raw materials. 8. Number of sales done in a project. Modeling steps for Use case Diagram 1. If necessary. Functionality or behavior of actors is considered as use cases. Getting profit and loss for every month.  The amount of time needed for the production. 2. 4. The performance department has to update the statistics and to the company. 5. Modeling steps for Sequence Diagrams UNIFIED MODELING LANGUAGE Page no: . Adorn with constraints and notes. Specify the generalized and specialized use cases. Outputs:      Total time required in completing a project.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Separate the generalized and specialized actors. Key Terms: Pay loan/repay loan Purchase machinery and start production. Draw the lines around the system and actors lie outside the system. Se the relationship among the use cases and in between actor and use cases.

subsystem. 2. JAHNAVI ROLL NO: 1220609110 1. Specify the links among these objects. 5. 3. Set the context for the interactions. Modeling steps for Collaboration Diagrams 1. If the attributes or tagged values of an object changes in significant ways over the interaction. Modeling steps for Activity Diagrams UNIFIED MODELING LANGUAGE Page no: . Set the lifelines for each and every object by sending create and destroy messages. 5. attach each subsequent message to appropriate link. system. operation or class or one scenario of use case or collaboration. 4. whether it is system. classes. 6. place a duplicate object. Specify the time and space constraints. Lay out other links and adorn with stereotypes. update with these new values and connect them by a message stereotyped as become or copy.GITAM INSTITUTE OF TECHNOLOGY NAME: T. 4. Attach pre & post conditions to specify flow of control formally. placing important objects in centre and neighboring objects to outside. Adorn each message with time and space constraints if needed 7. setting sequence number as appropriate. 2. Set the pre and post conditioned. Set the initial properties of each of these objects. Lay them out along the X-axis by placing the important object at the left side and others in the next subsequent. Starting with the message that initiates this interaction. Set the context for interaction. subsystem. 6. Lay the association links first represent structural connection. object or use cases. Lay them as vertices in graph. Identify the objects that play a role in the interaction. Start the message which is initiating interactions and place all other messages in the increasing order of items. 3. Set the stages for the interactions by identifying objects which are placed as actions in interaction diagrams.

Trace through the state machine. 4. These objects may be real or abstract. Model these events as triggers to transitions that move from one legal ordering of states to another. Start with sequential flows. forks. JAHNAVI ROLL NO: 1220609110 1. joins and history states.GITAM INSTITUTE OF TECHNOLOGY NAME: T. 7. whether it is a class. 8. 6. UNIFIED MODELING LANGUAGE Page no: . to check it against expected sequence of events & their responses. 5. 10. Adorn with notes tagged values and so on. 2. a use case. specify the activities and actions and render them as activity states or action states. create a swim lane for each important object. 2. For complicated actions. consider branching. Check that no state is a dead from which no combination of events will transition the object out of that state. Check that all states are reachable under some combination of events. Consider ways to simplify your machine by using sub states. collapse these states and provide separate activity diagram. Render the transitions that connect these activities and action states. Start with the high-level states of the objects & only then consider its possible substrates. branches. Decide on the meaningful partial ordering of stable states over the lifetime of the object. 3. In either case. 3. or the system as a whole. Choose the initial & final states of the objects. Attach actions to these transitions and/or to these states. either manually or by using tools. 5. Identify the precondition of initial state and post conditions of final state. 8. 4. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. 7. fork and joining. 9. Decide on the events that may trigger a transition from state to state. or for a set of actions that appear multiple times. Modeling steps for State chart Diagram 1. Beginning at initial state. Choose the context for state machine. 6. Select the object that has high level responsibilities.

tables. Set attributes and operation signatures for interfaces. 7. Adorn with tagged values. 10. Render all these classes as objects in diagram. Identify the files. Represent files. 3. interface. Identify the relationship among all objects. 2. Set the attributes and operations. Identify the mechanisms which you would like to model. 6. 5.Identify the source code which is interacting with the system. Identify the classes. 11. constraints and notes. 9. 4. 5. NAME: T.documents as components. 14.GITAM INSTITUTE OF TECHNOLOGY Modeling steps for Class Diagrams 1. 3. Walk through the scenario until to reach the certain point and identify the objects at that point. 2. 4. Show the existing relationships among them generally dependency. Show the relationships among all the components. Set the relationship among all the things. 12.Represent source code as components. Specify the links among all these objects. 4. Identify the seams in the model. Modeling steps for Object Diagrams 1. subsystem which are collaborated with mechanisms.tables. UNIFIED MODELING LANGUAGE Page no: . 6. Modeling steps for Component Diagrams 1. 5. JAHNAVI ROLL NO: 1220609110 Identity the things that are interacting with class diagram. Set the responsibilities. Represent this executables and libraries as components. Set the values of attributes and states of objects. Identify the interfaces which are interacting with the system. 7. 6. 3. 8. 13.Show the relationships among components. Identify the component libraries and executable files which are interacting with the system.Use either import or export relationship in b/w interfaces & components. Identify the generalization and specification classes. use cases.Set the version of the source code as a constraint to each source code. 2. documents which are interacting with the system.

4. 2. JAHNAVI ROLL NO: 1220609110 15. Provide the attributes & operations. UNIFIED MODELING LANGUAGE Page no: . Provide the links among clients & servers. 5. Group all the similar clients into one package. Modeling steps for Deployment Diagram 1. Provide the visual cue via stereotype classes. 7.GITAM INSTITUTE OF TECHNOLOGY NAME: T.Adorn with nodes. constraints and tag values. Adorn with nodes & constraints & draw the deployment diagram. Identify the processors which represent client & server. 3. 6. Specify the components which are living on nodes.

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY Class Diagram: NAME: T.

GITAM INSTITUTE OF TECHNOLOGY Use Case Diagram:

NAME: T. JAHNAVI ROLL NO: 1220609110

UNIFIED MODELING LANGUAGE

Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

Sequence Diagram:

Collaboration Diagram: UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

Activity Diagram: UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 State Chart Diagram: UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Component Diagram <<Application>> Simulated company RESULT: Thus various UML Diagrams were generated for SIMULATED COMPANY and the corresponding code was generated using Visual Basic. UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 la nding give aircraft info to lock s/m lock syste m checking for ks no acquire la nding area lock all locks a re locked yes prio rity acquire runway lock la nding on another runway acquire termina l lock aircraft at take off area if the aircraft is at takeoff area then release termina l a nd taxiing locks while moving from takeoff a rea release takeoff a rea lock and acquire runway lock acquire taxiing lock move to the terminal gate and release term inal and taxiing lo ck Runway allocation for takeoff Activity Diagram UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 takeoff acquire terminal lock give aircraft info to lock s/m checks for locks if locks are available acquire takeoff area lock acquire taxiing lock aircraft at takeoff area acquire runway lock if the aircraft is at the takeoff area then release terminal and taxiing lock while moving from takeoff area release takeoff area lock and acquire runway lock use the runway for takeoff and release runway lock UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 State Chart Diagram: UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 w a it fo r w e a the r re q runw a y s ta tus c o nd itio ns w a it fo r run nin g s ta tu s re q ru nw a y n o w a it fo r ru nw a y n o a va il n o t a va il w a it fo r te rm ina l s ta tus if tim e le ft la nd o n ru n w a y a va il no t a va il w a it fo r te rm ina l n o n o t a va il h a lt a va il UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 Component Diagram: UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

java terminalloc k.GITAM INSTITUTE OF TECHNOLOGY NAME: T.dll taxiinglock.db UNIFIED MODELING LANGUAGE Page no: .java central server java landing.db priority. JAHNAVI ROLL NO: 1220609110 terminal lock. class central database airport.class / .java central server .class taxiinglock.jav a takeofflock .cla ss takeofflock .class landing.

JAHNAVI ROLL NO: 1220609110 Deployment Diagram: <<DATA BASE>> central database <<SERVER>> central server <<WIRELESS COMMUNICATION>> <<DEVICE>> <<DEVICE>> <<DEVICE>> aircarft controlor lockmanager <<DEVICE>> control manager taxiing manager UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 Result: The various UML diagrams were drawn for AIRPORT SIMULATION SYSTEM application and the corresponding code was generated.GITAM INSTITUTE OF TECHNOLOGY NAME: T.

JAHNAVI ROLL NO: 1220609110 A SIMULATED COMPANY UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

purchase a machine and over a series of monthly and yearly production runs follows the concept of the company. following analysis diagrams will be updated. In addition details such as inventory and sales are updated. As part of the case study.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Simulated company is an example that shows the documents produced when undertaking the analysis and design of an application that simulates a small manufacturing company. This application is called simco: Simulated Company. The company has to see all the takings and the losses. The project if focused on the user to take lend. The company accounts are updated for a given month. They have to see all dealings of the company and see the additional features of the machine for better development. UNIFIED MODELING LANGUAGE Page no: . General expenses such as salary and rent are taken into account to calculate the net profit for the company. The accounts take into the gross profits from the sales. JAHNAVI ROLL NO: 1220609110 A SIMULATED COMPANY OVERVIEW: A critical step of the project is to design a modeling and simulation infrastructure to experiment and validate the proposed solutions.

 The probability for estimating the machinery cost and raw materials. Sequence and collaboration diagrams. Number of sales done in a project. The sales has to submit the record and stock details required.  The probability of estimating profit and loss. The performance department has to get collected details from all the departments and submit to the company. JAHNAVI ROLL NO: 1220609110 ○ ○ ○ ○ ○ Usecase for the system Class diagram for initially identified classes. Statechart diagram shows states before and after each action. It has to purchase machinery and start the production. Key Terms: UNIFIED MODELING LANGUAGE Page no: . The performance department has to prepare record statistics as given by marketing department.  The amount of time needed for the production. Activity diagram to show flow for each use case. Outputs:      Total time required in completing a project. Conceptualization: Assumptions: The company has to take the loan and repay the loan. Getting profit and loss for every month. Inputs:  The amount of time required for sanctioning the loan.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Case study of the project. The sales person has to sell the foods and update the details in the record. The number of goods manufactured in a simulated time.

Adorn with constraints and notes. Sell the products and updated the records. 7. Modeling steps for Use case Diagram 1. 4. 2. Identify the functionality the way of interacting actors with system and specify the behavior of actor. Separate the generalized and specialized actors. UNIFIED MODELING LANGUAGE Page no: . use collaborations to realize use cases. Lay them out along the X-axis by placing the important object at the left side and others in the next subsequent. Set the context for the interactions. Start the message which is initiating interactions and place all other messages in the increasing order of items. classes. 2.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Functionality or behavior of actors is considered as use cases. If necessary. object or use cases. 3. 5. Specify the generalized and specialized use cases. 6. 3. 5. Identify the actors which are interacting with the system. Set the stages for the interactions by identifying objects which are placed as actions in interaction diagrams. The performance department has to update the statistics and to the company. 4. Se the relationship among the use cases and in between actor and use cases. subsystem. 8. Draw the lines around the system and actors lie outside the system. system. JAHNAVI ROLL NO: 1220609110 Pay loan/repay loan Purchase machinery and start production. Modeling steps for Sequence Diagrams 1. 9. Set the lifelines for each and every object by sending create and destroy messages.

2. Identify the objects that play a role in the interaction. 2. 5. Specify the time and space constraints. These objects may be real or abstract. Set the initial properties of each of these objects. 6. 4. Lay out other links and adorn with stereotypes. Set the context for interaction. Starting with the message that initiates this interaction. create a swim lane for each important object. Lay the association links first represent structural connection. whether it is system. place a duplicate object. Select the object that has high level responsibilities. Attach pre & post conditions to specify flow of control formally. Specify the links among these objects. UNIFIED MODELING LANGUAGE Page no: . Lay them as vertices in graph. 3. Modeling steps for Collaboration Diagrams 1. Adorn each message with time and space constraints if needed 7. Modeling steps for Activity Diagrams 1. setting sequence number as appropriate. In either case. If the attributes or tagged values of an object changes in significant ways over the interaction. placing important objects in centre and neighboring objects to outside. subsystem.GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 6. update with these new values and connect them by a message stereotyped as become or copy. Set the pre and post conditioned. operation or class or one scenario of use case or collaboration. attach each subsequent message to appropriate link.

or for a set of actions that appear multiple times. Decide on the meaningful partial ordering of stable states over the lifetime of the object. 7. collapse these states and provide separate activity diagram. 8. joins and history states. 6. 7. Choose the initial & final states of the objects. 6. 3. either manually or by using tools. 9. Check that no state is a dead from which no combination of events will transition the object out of that state.Trace through the state machine. Check that all states are reachable under some combination of events. or the system as a whole. Decide on the events that may trigger a transition from state to state. a use case. consider branching. branches. specify the activities and actions and render them as activity states or action states. For complicated actions. forks. 5. Choose the context for state machine. 8. Modeling steps for State chart Diagram 1. 5. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. UNIFIED MODELING LANGUAGE Page no: . Render the transitions that connect these activities and action states. Start with the high-level states of the objects & only then consider its possible substrates. 4. fork and joining. JAHNAVI ROLL NO: 1220609110 3. Model these events as triggers to transitions that move from one legal ordering of states to another. Start with sequential flows. Beginning at initial state. Adorn with notes tagged values and so on. to check it against expected sequence of events & their responses. 2. 10. 4. Consider ways to simplify your machine by using sub states.GITAM INSTITUTE OF TECHNOLOGY NAME: T. whether it is a class. Identify the precondition of initial state and post conditions of final state. Attach actions to these transitions and/or to these states.

Set the attributes and operations. Show the existing relationships among them generally dependency. Set attributes and operation signatures for interfaces.Use either import or export relationship in b/w interfaces & components. 4. 7. Identify the interfaces which are interacting with the system. 2. 4. 4. Show the relationships among all the components. interface. tables. Identify the component libraries and executable files which are interacting with the system. 2. Identity the things that are interacting with class diagram. JAHNAVI ROLL NO: 1220609110 Modeling steps for Class Diagrams 1. 6. documents which are interacting with the system. Set the responsibilities. 3. 5. use cases.documents as components. Represent this executables and libraries as components. subsystem which are collaborated with mechanisms. Modeling steps for Object Diagrams 1.tables. Render all these classes as objects in diagram. 10. 3. Set the relationship among all the things. Identify the generalization and specification classes. constraints and notes. Set the values of attributes and states of objects. Walk through the scenario until to reach the certain point and identify the objects at that point. Adorn with tagged values. Identify the mechanisms which you would like to model. Identify the classes. 8. 6. Modeling steps for Component Diagrams 1. Identify the files. 6. Represent files.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Identify the relationship among all objects. UNIFIED MODELING LANGUAGE Page no: . 3. Identify the seams in the model. 9. Specify the links among all these objects. 7. 5. 2. 5.

4.Represent source code as components. Provide the visual cue via stereotype classes. 15. 13. Modeling steps for Deployment Diagram 1. 2.Set the version of the source code as a constraint to each source code.GITAM INSTITUTE OF TECHNOLOGY NAME: T. Specify the components which are living on nodes.Adorn with nodes. constraints and tag values. Adorn with nodes & constraints & draw the deployment diagram. Identify the processors which represent client & server. 6. 3. UNIFIED MODELING LANGUAGE Page no: .Identify the source code which is interacting with the system. 7. 14. JAHNAVI ROLL NO: 1220609110 11. 5. Provide the links among clients & servers.Show the relationships among components. Group all the similar clients into one package. 12. Provide the attributes & operations.

JAHNAVI ROLL NO: 1220609110 Class Diagram: UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Use Case Diagram: UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Sequence Diagram: UNIFIED MODELING LANGUAGE Page no: .

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Collaboration Diagram: UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 Activity Diagram: UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. JAHNAVI ROLL NO: 1220609110 State Chart Diagram: UNIFIED MODELING LANGUAGE Page no: .

GITAM INSTITUTE OF TECHNOLOGY NAME: T. UNIFIED MODELING LANGUAGE Page no: . JAHNAVI ROLL NO: 1220609110 Component Diagram <<Application>> Simulated company RESULT: Thus various UML Diagrams were generated for SIMULATED COMPANY and the corresponding code was generated using Visual Basic.

JAHNAVI ROLL NO: 1220609110 UNIFIED MODELING LANGUAGE Page no: .GITAM INSTITUTE OF TECHNOLOGY NAME: T.