Uml 1st Part

7/30/2019 Uml 1st Part

1/27

INDEX

S. No ContentsPage No

4 Lab Objective2

4 Introduction About Lab2

6 Guidelines to Students3

8

List of Lab Exercises

4.1 Syllabus Programs (JNTU)

4.2 Additional and Advanced Programs

4

9 Description about UML6

12 Diagrams9

55 References49

www.jntuworld.com-1-


2/27

LAB OBJECTIVE

Overview of UML

Basic & Advanced Models

Class , Object, Collaboration & Sequence

Use Cases Advanced Modeling

Component Diagram & Deployment Diagrams

INTRODUCTION ABOUT LAB

There are 66 systems (Compaq Presario) installed in this Lab. Theirconfigurations are as follows:

Processor : AMD Athelon 1.67 GHz

RAM : 256 MB

Hard Disk : 40 GB

Mouse : Optical Mouse

Network Interface card : Present

Software

All systems are configured in DUAL BOOT mode i.e., Students can boot fromWindows XP or Linux as per their lab requirement.

This is very useful for students because they are familiar with different

Operating Systems so that they can execute their programs in different

programming environments.

Each student has a separate login for database access

Oracle 9i client version is installed in all systems. On the server, account for each

student has been created.



3/27

This is very useful because students can save their work ( scenarios, pl/sqlprograms, data related projects ,etc) in their own accounts. Each student work is safe

and secure from other students.

Latest Technologies like DOT NET and J2EE are installed in some systems. Beforesubmitting their final project, they can start doing mini project from 2nd year onwards.

MASM ( Macro Assembler ) is installed in all the systems

Students can execute their assembly language programs using MASM. MASMis very useful students because when they execute their programs they can see

contents of ProcessorRegisters and how each instruction is being executed in

the CPU.

Rational Rose Software is installed in some systems

Using this software, students can depict UML diagrams of their

projects.

Softwares installed: C, C++, JDK1.5, MASM, OFFICE-XP, J2EE and DOT NET,

Rational Rose.

Systems are provided for students in the 1:1 ratio.

Systems are assigned numbers and same system is allotted for students when

they do the lab.



4/27

Guidelines to Students

1. Learn what the UML is, what it is not and why it is relevant to the process of

developing software-intensive systems

2. Master the vocabulary rules and idioms of the UML and in general how to speak the

language efficiently

3. Under stand how to apply UML to solve a number of common problems

The user guide provides a reference to the use of specific UML features,However it is not intended to be a comprehensive reference manual for UML. That isfocus on other book, The Unified Modeling Language Reference Manual

For the developer approaching the UML for the first time, the user guide is

best-read linearly. All chapters are constructed so that each builds upon the contentsof previous one, thus lending it as linear progression.



5/27

UML Syllabus Programs (JNTU)

www.jntuworld.com

S. No Programs

1. Class diagram of school without attributes2. Class diagram of school with attributes

3. Class diagram of Hospital without attributes

4. Class diagram of Hospital with attributes

5. Class diagram for ATM.

6. Use case diagram for ATM.

7. Activity diagram for ATM

8. Sequence diagram ATM

9. Collaboration diagram for ATM

10. Component diagram for ATM

11. Deployment diagram for ATM

12. State Transition diagram for ATM13. Use case Diagram for Librarian Scenario

14. Use case diagram for mechanic

15. Use case diagram for Point of sale


17. Activity diagram for Point of sale

18. Sequence diagram for Point of sale

19. Collaboration diagram for Point of sale

20. Deployment diagram for Point of sale

21. Sequence diagram for Hospital

22. Collaboration diagram for Hospital23. Activity diagram for Patient visiting doctor using Swim lines

24. Activity diagram of patient checked by Treatment Provider for Diabetes

25. Activity diagram for Cellular Company

26. Online Book shop of class diagram without attributes

27. On line book shop of Use case diagram

28. Online book shop of Activity diagram

29. Sequence diagram using Timing Constraints & Locations

30. State transition diagram representing a history state H

31. Diagram representing Concurrent sub states

33. State transition diagram fora Computer being identified withstates

34. Diagram for the relation between a component & interface35. Diagram for the relation between a component & class

36. Deployment diagram for Physical connection system

37. Deployment diagram for Client server system

38. Development Diagram that shows the Embedded System.

-5-


6/27


7/27

Constructing

Documenting

The UML is a Language

A modeling language is a language whose vocabulary and

rules focus on the conceptual and physical representation of a

system

The UML is a Language for Visualizing

Some programmers think of an implementation and then code

it. Some programmers think mentally i.e. they even sketch outa few ideas on a paper. That means some things are best

modeled textually, others are best modeled graphically. TheUML is such a graphical language.

The UML is a Language for Specifying

Specifying means building models. It specifies of all the

important analysis, design, and implementation decisions that

must be made in developing a software project.

The UML is a Language for constructing

The UML is not a visual programming language, but its

models can be directly connected to a variety of a

programming language. This means that it is possible to mapfrom a model in the UML to a programming language such as

Java, C++.

The UML is a Language for Documenting



8/27

A Healthy software organization produces all sorts of artifacts

in addition to raw executable code. These artifacts include

1. Requirements

2. Architecture

3. Design

4. Source code

5. Project plans

6. Tests

7. Releases

The UML addresses the documentation of a systems

architecture and all of its detail

4. Architectural views of UML

The user model view

- Use Case Diagram - The functionality of a system

The structural model view

- Class Diagram - The static structure of a system

- Object Diagram - The static structure of a system at a particular time

The behavioral model view

- Sequence Diagram - Interaction among elements of a system in a timesequence

- Collaboration diagram - Interaction among elements and their relations

organized in time and space

- State Diagram - The status condition and responses of the elements of a

system

- Activity Diagram - The activities of the system



9/27

The implementation model view

- Component Diagram - The organization of the elements realizing the system

The Environment model view

- Deployment diagram - Configuration of environment elements and the mapping of

elements realizing the system into them



10/27

1. School model without Attributes



11/27

2. School Model with Attributes



12/27

3. Hospital Model without Attributes



13/27

4. Hospital Model with Attributes



14/27

5. ATM Scenario Class Diagram



15/27



16/27

6. ATM Scenario Use Case Diagram

Transfer fund

View balance

Transfer funds

Deposi t fundsCustomer

Withdraw money

Bank officer

Change pin

Make paymentClient



17/27

7. ATM Scenario Activity Diagram

Insert

card

EnterPIN

Entertransition

Connect Not connected

Any more transaction

Removecard

No more transaction



18/27

8. ATM Scenario Sequence Diagram

A : Atmmachine

ac :account

B : Bankclient

1: Insert card

Insert PIN

3 : Enter PIN

4 : Verification

5 : PIN ok

6 : Request for transaction

7 : Process transaction

8 : Enter amount

9 : Amount entered

10 : Withdrawal

11 : Withdrawal success

12 : Dispense cash

13 : take cash

14 : Terminate

15 : Print slip

16 : Eject card



19/27

9. ATM Scenario Collaboration Diagram



20/27

10. ATM Scenario Deployment Diagram



21/27

11. ATM Scenario Component Diagram

Card Reader

ATM Screen

Cash Dispenser

Card ReaderCard dispenser

ATM Screen

ATM.exe



22/27

12. ATM Scenario State Transition Diagram



23/27

13. Use case Diagram for Librarian Scenario



24/27

14. Use case diagram for mechanic



25/27

15. Class diagram for Point of sale



26/27




27/27

Uml 1st Part

Documents

Transcript of Uml 1st Part