Unified Model Approach - CT
Unified Model Approach - CT
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.
In this model the data and functionality are arrived from inside the system.
In this the structural and behavioral as parts of the system are represented as they are
to be built.
1
In this the structural and behavioral aspects of the environment in which the system is
to be implemented are represented.
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
Use case
Relationship
Relationships are simply illustrated with a line connecting actors to use cases.
Admi nistrator
System
Payroll Processing
Employee
Database
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
COLLABORATION DIAGRAM
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
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