0% found this document useful (0 votes)
55 views5 pages

Unified Model Approach - CT

The document discusses the Unified Modeling Language (UML) approach to modeling software systems. It describes the five main views used in UML - user model, structural model, behavioral model, implementation model, and environmental model. Each view is defined using different diagrams. It then provides examples of use case diagrams, class diagrams, sequence diagrams, and collaboration diagrams to illustrate how UML can model different aspects of a payroll processing system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
55 views5 pages

Unified Model Approach - CT

The document discusses the Unified Modeling Language (UML) approach to modeling software systems. It describes the five main views used in UML - user model, structural model, behavioral model, implementation model, and environmental model. Each view is defined using different diagrams. It then provides examples of use case diagrams, class diagrams, sequence diagrams, and collaboration diagrams to illustrate how UML can model different aspects of a payroll processing system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

UNIFIED MODELING APPROACH

INTRODUCTION

The Unified Modeling Language allows the software engineer to express an analysis
model using the modeling notation that is governed by a set of syntactic semantic and
pragmatic rules. A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set of diagram, which
is as follows.

User Model View

This view represents the system from the users perspective.

The analysis representation describes a usage scenario from the end-users


perspective.

Structural model view

In this model the data and functionality are arrived from inside the system.

This model view models the static structures.

Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the


interactions of collection between various structural elements described in the user model and
structural model view.

Implementation Model View

In this the structural and behavioral as parts of the system are represented as they are
to be built.

Environmental Model View

1
In this the structural and behavioral aspects of the environment in which the system is
to be implemented are represented.

USE CASE DIAGRAM

Use Case diagrams show the various activities the users can perform on the system.
The System is something that performs a function. They model the dynamic aspects of the
system. It provides a users perspective of the system.

Actor

An actor is a user of the system playing a particular role.

Use case

Use case is a particular activity a user can do on the system.

Relationship

Relationships are simply illustrated with a line connecting actors to use cases.

Employee Detai ls Val idity Check

Admi nistrator

System

Payroll Processing

Employee

Database

Vi ew and Print the Salary Details

2
CLASS DIAGRAM

A class diagram describes the types of objects in the system and the various kinds of
static relationships that exist among them i.e., A graphical representation of a static view on
declarative static elements. A class is the description of a set of objects having similar
attributes, operations, relationships and behavior.

employee database
emp id empid
name system name
department age
age show details() des ignation
des ignation validity check()

view()

administrator
empid
name
department
age
payroll basic pay
processing HRA
PF
bas ic pay
net pay
HRA
PF
insert()
net pay
delete()
update()
calculation()

SEQUENCE DIAGRAM

3
employee administrator system database payroll
processing

provide ID
Enter ID
Validation check
Provide details
Processing

Send details
Give details

View details

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction


diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. Sequence diagrams are sometimes called event
diagrams, event scenarios, and timing diagrams

COLLABORATION DIAGRAM

A Collaboration diagram is very similar to a Sequence diagram in the purpose it


achieves; in other words, it shows the dynamic interaction of the objects in a system. A
distinguishing feature of a Collaboration diagram is that it shows the objects and their
association with other objects in the system apart from how they interact with each other. The
association between objects is not represented in a Sequence diagram. A Collaboration
diagram is easily represented by modeling objects in a system and representing the
associations between the objects as links. The interaction between the objects is denoted by
arrows. To identify the sequence of invocation of these objects, a number is placed next to
each of these arrows.

4
2: Enter ID
1: provide ID administrat
or system
employee
7: Give details
8: View details

6: Send details
5: Processing

3: Validation check

4: Provide details
database payroll
processing

This pay roll processing involves with two types of users.

USER

ADMINISTRATOR

This has been depicted clearly through use case diagram and other UML diagrams.

REFERENCES

http://sourcecodesonline.blogspot.in/2010/12/payroll-system-using-case-
tools.html

http://creately.com/diagram/example/grrj6nrf6/Payroll+Usecase+System

csehelpline.weebly.com/uploads/7/1/7/1/7171317/payroll_system.doc

You might also like