GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

OVERVIEW: A critical step of the project is to design a modeling and simulation infrastructure to experiment and validate the proposed solutions. 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 project if focused on the user to take lend, purchase a machine and over a series of monthly and yearly production runs follows the concept of the company. The company has to see all the takings and the losses. They have to see all dealings of the company and see the additional features of the machine for better development. The company accounts are updated for a given month. The accounts take into the gross profits from the sales. General expenses such as salary and rent are taken into account to calculate the net profit for the company. In addition details such as inventory and sales are updated. As part of the case study, following analysis diagrams will be updated. o o o o o Usecase for the system Class diagram for initially identified classes. Activity diagram to show flow for each use case. Sequence and collaboration diagrams. Statechart diagram shows states before and after each action.

Conceptualization: Assumptions: The company has to take the loan and repay the loan. It has to purchase machinery and start the production. The sales person has to sell the foods and update the details in the record. The sales has to submit the record and stock details required. 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.

Inputs: UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

_ _ _ _

The amount of time required for sanctioning the loan. The amount of time needed for the production. The probability for estimating the machinery cost and raw materials. The probability of estimating profit and loss.

Outputs: _ _ _ _ _ Total time required in completing a project. The number of goods manufactured in a simulated time. Number of sales done in a project. Getting profit and loss for every month. Case study of the project.

Key Terms: Pay loan/repay loan Purchase machinery and start production. Sell the products and updated the records. The performance department has to update the statistics and to the company.

Modeling steps for Use case Diagram 1. Draw the lines around the system and actors lie outside the system. 2. Identify the actors which are interacting with the system. 3. Separate the generalized and specialized actors. 4. Identify the functionality the way of interacting actors with system and specify the behavior of actor. 5. Functionality or behavior of actors is considered as use cases. 6. Specify the generalized and specialized use cases. 7. Se the relationship among the use cases and in between actor and use cases. 8. Adorn with constraints and notes. 9. If necessary, use collaborations to realize use cases.

Modeling steps for Sequence Diagrams UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

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

Modeling steps for Activity Diagrams

UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

1. Select the object that has high level responsibilities. 2. These objects may be real or abstract. In either case, create a swim lane for each important object. 3. Identify the precondition of initial state and post conditions of final state. 4. Beginning at initial state, specify the activities and actions and render them as activity states or action states. 5. For complicated actions, or for a set of actions that appear multiple times, collapse these states and provide separate activity diagram. 6. Render the transitions that connect these activities and action states. 7. Start with sequential flows, consider branching, fork and joining. 8. Adorn with notes tagged values and so on.

Modeling steps for State chart Diagram

1. Choose the context for state machine, whether it is a class, a use case, or the system as a whole. 2. Choose the initial & final states of the objects. 3. Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time. Start with the high-level states of the objects & only then consider its possible substrates. 4. Decide on the meaningful partial ordering of stable states over the lifetime of the object. 5. 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. 6. Attach actions to these transitions and/or to these states. 7. Consider ways to simplify your machine by using sub states, branches, forks, joins and history states. 8. Check that all states are reachable under some combination of events. 9. Check that no state is a dead from which no combination of events will transition the object out of that state. 10.Trace through the state machine, either manually or by using tools, to check it against expected sequence of events & their responses.

UNIFIED MODELING LANGUAGE

Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

Modeling steps for Class Diagrams

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

Modeling steps for Object Diagrams

1. Identify the mechanisms which you would like to model. 2. Identify the classes, use cases, interface, subsystem which are collaborated with mechanisms. 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 this executables and libraries as 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. 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. UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

15.Adorn with nodes, constraints and tag values.

Modeling steps for Deployment Diagram

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

UNIFIED MODELING LANGUAGE

Page no:

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:

UNIFIED MODELING LANGUAGE

Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

Sequence Diagram:

Collabor ation Diagram: UNIFIED MODELING LANGUAGE Page no:

GITAM INSTITUTE OF TECHNOLOGY

NAME: T. JAHNAVI ROLL NO: 1220609110

Activity D iagram: 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. JAHNAVI ROLL NO: 1220609110

UNIFIED MODELING LANGUAGE

Page no:

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: