INSTITU

INDEX

1. INTRODUCTION TO UML 2. ARCHITECTURE OF UML: 3. SIMULATED COMPANY 4. UNIFIED LIBRARY APPLICATION 5. POINT OF SALE

INTRODUCTION TO UML
2

The unified modeling language(UML) is a standard language for writing software blue prints.The uml will be used to visualize specify ,construct and document the artifacts of a software intensive system. AN OVERVIEW OF UML: An UML is language for 1.visualizing 2.specifiying 3.constructing 4.documenting THE UML IS A LANGUAGE 1.A modeling language is a language whose vocabulary and rules focus on the conceptual and physical representation of a system. 2.A modeling language such as the uml is thus a standard language for software blue prints. 3.Modelling yields an understanding of a system.NO one model is ever sufficient .Rather,you often need multiple models that are connected to one anather in order to understand anything but the most trivial system. For software-intersive systems,this recquires a language that addresses the different views of a systems architecture as it evolves throughout the software development life cycle. THE UML IS A LANGUAGE FOR VISUALIZING: The uml is more than just a bunch of graphical symbols. Rather ,behind each symbol in the uml notation is a well defined semantics. In this manner ,one developer can write a model in the uml, and another developer can write a model in the uml.,and anather developer,or even another tool,can interpret that model unambiguously. THE UML IS LANGUAGE FOR SPECIFYING Specifying means building models that are precise,unambiguous and complete.In particular ,the UML addresses the specification of all the important analysis,design,and implementation decisions that must be made in developing and deploying a software intensive system. THE UML IS A LANGUAGE FOR CONSTRUCTING: The uml is not a visual programming language.but it models can directly connected to a variety of programming languages.this means that is possible to map from a model in uml to a programming language such as java,c++ ,or visual basic,or even to a relational database. Things that are best expressed graphically are done so graphically in uml. The uml is sufficiently expressed under ambiguously to permit the direct executioin of models.

THE UML IS LANGUAGE FOR DOCUMENTING:

3

The artifacts include: 1. Requirements 2. Architecture 3. Design 4. Source code 5. Project plans 6. Tests 7. Prototypes 8. Releases The uml addresses the documentation of a systems architecture and all of its details. The uml also provides a language for expressing requirements and for tests.finally ,the uml provides a language for modeling the activities of project planning and release management. WHERE CAN THE UML BE USED? The uml is intended primarily for software-intensive systems. It has been used effectively for such domains as 1. Enterprise information systems 2. Banking and financial services 3. Telecommunications 4. Transportation 5. Defense/aerospace 6. Retail 7. Medical electronics 8. Scientific 9. Distributed web-based services The uml is not limited to modeling software. In fact,it is expressive enough to model nonosoftware systems. Such as workflow in the legal system,the structure and behaviou of a patient healthcare system,and the design of hardware.

ARCHITECTURE OF UML:
4

Visualizing,specifying,constructing,and documenting a software intensive system demands that the system be viewed from a number of perspectives.Different stakeholders-end users,analysts,developers,system integrators,testers,technical writers,and project managerseach bring different agendas to a project and each looks at that system in different ways at different times over the projects life. Architecture is the set of significant decision about 1. The organization of a software system 2. The selection of the structural elements and their interfaces by which the system is composed 3. Their behavior ,as specified in the collaborations among those elements 4. The composition of these structural and behavioral elements into progressively larger subsystems 5. The architectural style that guides this organization:the static and dynamic elements and their collaborations,and their composition THE USE CASE VIEW: The use case view of a system encompasses the use cases that describe the behavior of the system as seen by its end users,analysts,and testers. This view doesnt really specify the organization of a software system. THE DESIGN VIEW: The design view of a system encompasses the classes,interfaces,and collaborations that form the vocabulary of the problem and its solution. This view primarily supports the functional requirements of the system,meaning the services that the system should provide to its end users.

THE PROCESS VIEW: The process view of a system encompasses the threads and process that form the systems concurrency and synchronization mechanisms.this view primarily addresses the performance ,scalability,and throughput of the system. THE IMPLEMENTATION VIEW: The implementation view of a system encompasses the components and files that are used to assemble and release the physical system.this view primarily addresses the configuration management of the systems releases, made up of somewhat independent components and files that can be assembled in various ways to produce a running system. THE DEPLOYMENT VIEW: The deployment view of a system encompasses the nodes that form the systems hardware topology on which the system executes .this view primarily j addresses the distribution,delivery and installation of the parts that make up the physical system.

SIMULATED COMPANY INTRODUCTION Companies are emerging like mushrooms nowadays. It is necessary for us to examine how a company runs and the basic transactions taking place in a company. This project emphasizes on the working of company with main actors being managing director, marketing manager and catalog Director collects capital and then starts company by installing machinery and appointing labor. He then starts the production activity. After production marketing manager along with managing director decides the price of product which is then marketed by marketing manager. He then submits reports to the director about the sales which are analyzed by the director. All these activities are updated into the catalog from time to time Let us just have an overview of point of sale: Director collects capital from various sources Director installs machinery and employs labor to begin production activity Director along with managing director decides price Marketing manager does marketing and submits reports to the director

TEXTUAL ANALYSIS (a) ACTORS i. Director ii. Marketing Manager iii. Catalog (b) VERBS i. Director: 1. Collects capital 2. Installs machinery 3. Employ labor 4. Begin Production 5. Decide price 6. Analyze reports

ii. Marketing Manager: 1. Decide price 2. Do marketing 3. Submit reports 4. Update catalog iii. Catalog 1. Stores reports USECASE DIAGRAM Use case diagram is created to visualize the interaction of our system with the outside world. The components of use case diagram are: Use Case: Scenarios of the system Actor: Someone or something who is interacting with the system Relationship: Semantic link between use case and actor. The forms of relationship are: a. Association b. Dependency c. Generalization

ACTIVITY DIAGRAM Activity diagram shows the flow of events within our system. The components are: a) Start State b) End State c) Transition d) Decision Box e) Synchronization Bar f) Swim Lane

10

INTERACTION DIAGRAM An interaction diagram models the dynamic aspects of the system by showing the relationship among the objects and messages they may dispatch. There are two types of interaction diagrams: SEQUENCE DIAGRAM Sequence diagram shows the step to step what mush happen to accomplish a piece of functionality provided by the system. The components are: a) b) c) d) e) Actor Object Messages Lifeline Focus of Control

11

COLLABORATION DIAGRAM Collaboration diagram displays object interactions organized around objects and their links to one another. The components are: a) Actor b) Object c) Link

CLASS DIAGRAM Class diagram shows structure of the software system. The class diagram shows a set of classes, interfaces and their relationships. The components are: a) Class b) Relationship: The forms of relationship are: 1. Association 2. Aggregation 3. Generalization 4. Composition 5. Dependency

12

STATE CHART DIAGRAM State chart diagram show a life cycle of a single class. The state is a condition where the object may be in. The components are: a) Start state b) End state c) State d) Transition Catalog

Director

Marketing Manager

13

UNIFIED LIBRARY APPLICATION INTRODUCTION Unified Library Application System emphasizes on the online reservation, issue and return of books. This system globalizes the present library system. Using this application the member can reserve any book from anywhere in the world. Still in nascent stages, this application soon revolutionizes present library system. Let us just have an overview of the unified library application system: Librarian lends books and magazines Librarian maintains the list of all the members of library Borrower makes reservation online Borrower can remove reservation online Librarian issues books to the borrower Librarian calculates dues to be paid by the borrower Borrower issues/returns books and/or magazines Librarian places order about the requirements to the master librarian Librarian updates system Master librarian maintains librarians

TEXTUAL ANALYSIS (a) ACTORS i. Librarian ii. Borrower iii. Catalog iv. Master Librarian

14

(b) VERBS i. Borrower: 1. Logs into the system 2. Browses/searches for books or magazines 3. Makes/removes reservation 4. Views results and reports from the unified library application system ii. Librarian: 1. Manages and validates members 2. View reports from the system 3. Issues books 4. Calculates dues 5. Takes books 6. Places orders to the master librarian 7. Maintains list of books and magazine iii. Master Librarian 1. Maintains other librarians USECASE DIAGRAM Use case diagram is created to visualize the interaction of our system with the outside world. The components of use case diagram are: Use Case: Scenarios of the system Actor: Someone or something who is interacting with the system Relationship: Semantic link between use case and actor. The forms of relationship are: a. Association b. Dependency c. Generalization

15

ACTIVITY DIAGRAM Activity diagram shows the flow of events within our system. The components are: a) Start State b) End State c) Transition d) Decision Box e) Synchronization Bar f) Swim Lane

16

INTERACTION DIAGRAM An interaction diagram models the dynamic aspects of the system by showing the relationship among the objects and messages they may dispatch. There are two types of interaction diagrams: SEQUENCE DIAGRAM Sequence diagram shows the step to step what mush happen to accomplish a piece of functionality provided by the system. The components are: a) Actor b) Object c) Messages d) Lifeline
17

e) Focus of Control

COLLABORATION DIAGRAM Collaboration diagram displays object interactions organized around objects and their links to one another. The components are: a) Actor b) Object c) Link

18

CLASS DIAGRAM Class diagram shows structure of the software system. The class diagram shows a set of classes, interfaces and their relationships. The components are: a) Class b) Relationship: The forms of relationship are: 1. 2. 3. 4. 5. Association Aggregation Generalization Composition Dependency

19

STATE CHART DIAGRAM State chart diagram show a life cycle of a single class. The state is a condition where the object may be in. The components are: a) Start state b) End state c) State d) Transition

20

Member:

Librarian

21

Library Administrator

22

POINT OF SALE INTRODUCTION Shops are the integral part of any civilization. They are present in every culture since ages. This application emphasizes on the transaction going on between the customer and shop keeper during sale of product. The customer approaches the shop keeper/ sales boy and places his order. The shop keeper forwards the order to sales boy who fetches the required goods from inventory. Then the shop keeper calculates bill and issues to the customer. The customer on paying the bill takes goods from the shop keeper. In turn, shop keeper fetches goods from supplier Let us just have an overview of point of sale: Customer places order to the shop keeper/sales boy Sales boy collects goods and forwards them to shop keeper Shop owner calculates bill and forwards to the customer Customer on paying the bill receives goods from shop keeper Shop keeper places order to supplier and receives goods

TEXTUAL ANALYSIS (a) ACTORS i. Customer ii. Shop Owner iii. Sales boy iv. Supplier (b) VERBS i. Customer: 1. Places order to shop owner/sales boy 2. Receives bill from shop owner 3. Pay the bill 4. Receive goods ii. Shop Owner: 1. Receives order from customer 2. Forwards order to sales boy 3. Receive goods from sales boy
23

4. Calculates bill 5. Receives payment 6. Places orders to supplier 7. Maintains inventory iii. Supplier 1. Receives order from shop owner 2. Delivers goods to shop owner USECASE DIAGRAM Use case diagram is created to visualize the interaction of our system with the outside world. The components of use case diagram are: Use Case: Scenarios of the system Actor: Someone or something who is interacting with the system Relationship: Semantic link between use case and actor. The forms of relationship are: a. Association b. Dependency c. Generalization

24

ACTIVITY DIAGRAM Activity diagram shows the flow of events within our system. The components are: a) Start State b) End State c) Transition d) Decision Box e) Synchronization Bar f) Swim Lane

25

26

INTERACTION DIAGRAM An interaction diagram models the dynamic aspects of the system by showing the relationship among the objects and messages they may dispatch. There are two types of interaction diagrams: SEQUENCE DIAGRAM Sequence diagram shows the step to step what mush happen to accomplish a piece of functionality provided by the system. The components are: a) Actor b) Object c) Messages d) Lifeline e) Focus of Control

27

COLLABORATION DIAGRAM Collaboration diagram displays object interactions organized around objects and their links to one another. The components are: a) Actor b) Object c) Link

CLASS DIAGRAM Class diagram shows structure of the software system. The class diagram shows a set of classes, interfaces and their relationships. The components are: a) Class b) Relationship: The forms of relationship are: 1. Association 2. Aggregation 3. Generalization 4. Composition 5. Dependency

28

STATE CHART DIAGRAM State chart diagram show a life cycle of a single class. The state is a condition where the object may be in. The components are: a) Start state b) End state c) State d) Transition Customer

29

Shop Owner

Supplier

30

Sales boy

STIMULUS RESPONSE DIAGRAM Stimulus Response Diagram emphasizes on describing the life cycle of entire system as a whole. The components are: a) Start state b) End state c) State d) Transition

31