C. V.

RAMAN COLLEGE OF ENGINEERING

DEPT OF CS & IT

SOFTWARE ENGINEERING LAB MANUAL

(IT40306)
 Control Information
Document Name Software Engineering Laboratory manual

Version Version 1.0

Prepared on:

Prepared By: Sushreeta Mohanty

1601227416
Verified on:

Verified By:

Released on:

Applicable to: 7th Semester B.Tech IT Students

Experiment No. Topic Date Remarks

1. Study of specific problem

case and prepare the system
requirements,
specifications.
2. Analyze the problem and
create the data flow
diagram.
3. Develop the module
structure chart for the
problem.
4. Develop Use Case model
for a problem.

5. Identify entity objects and

classes and develop class
relationship using UML.
Experiment 1: Prepare Analysis document

Employee Management System

1.Overview

Employee Management system is an application that enables users to create and store
Employee Records. The application also provides facilities of a payroll system which enables
user to generate Pay slips too. This application is helpful to department of the organization
which maintains data of employees related to an organization .

2. General Description

Employee Management System is open to admins, HRs, Managers, and regular employees.
Among all users, only the admins have all privileges to access all the information of system.
So the admins will insert, update, remove the employees, departments, generate reports and
whereas other users will have limited roles. Once the user’s login they can perform few tasks
specific to their role. Employee information can be modified by either Admin, Managers or
by the employee himself/herself. Suppose if we want to keep track of a list of all changes
made to an employee profile, we need to maintain logs.

3. Functional Requirement

This section provides requirement overview of the system. Various functional modules that
can be implemented by the system will be -

3.1 Initial Step

Create initial setup which includes: Generating company information (includes creating
departments, company history, CEOs information etc.) Generating employee information
(adding/deleting/updating employee information, feedback’s, salaries) Generating unique
employee ID for each employee

3.2 Registration
If employee wants to register then he/she must be registered, unregistered user can’t go to
the admin page.

3.3 Login
Employee login to the system by entering valid user id and password for validating or
changing details.

3.4 Logout

3.5 Report generation.

After all validation the system can generate the portable document file (.pdf) and then sent
one copy to the employee’s Email address and another one for the system data base
to calculate the monthly salary.

4. Operational Scenario
 It must provide a user in employee mode with the details of an employee, which
includes his/her name, department, date of joining and salary.
  It must validate a user to enter in administrator mode using password. It must provide
a user to enter in administrator mode to view or modify an employee’s details using
employee ID. It must also allow the user to add a new employee and delete records of
an existing employee.

Experiment 2 : Prepare Data Flow Diagram (DFD-0, DFD-1,DFD-2)

The DFDs are used to:
 discuss with the user a diagrammatic interpretation of the processes in the system and
clarify what is currently being performed
 determine what the new system should be able to do and what information is required
for each different process that should be carried out
 check that the completed system conforms to its intended design

2.1 Components of Data Flow Diagram

Luckily there are only four different symbols that are normally used on a DFD. The elements
represented are:

 External entities
 Processes
 Data stores
 Data flows

Figure 1: DFD level 0 for Employee Management System

Figure 2: DFD level 1for Employee Management System

Figure 3: DFD level 2 for Employee Management System

Experiment 3: Structure Chart
Structure chart is a chart derived from Data Flow Diagram. It represents the system in more
detail than DFD. It breaks down the entire system into lowest functional modules, describes
functions and sub-functions of each module of the system to a greater detail than DFD.
Structure chart represents hierarchical structure of modules. At each layer a specific task is
performed. The symbols used in construction of structure charts are as follows:

 Modules
 Condition
 Jump
 Loop
 Data Flow
 Control Flow

Figure 4: Structure Chart for Employee Management System

Experiment 4: Use Case Diagrams

What is a Use Case Diagram?

A use case diagram is a dynamic or behaviour diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases. Use cases are a set of actions, services, and
functions that the system needs to perform. In this context, a "system" is something being developed
or operated, such as a web site. The "actors" are people or entities operating under defined roles
within the system.

Why Make Use Case Diagrams?

Use case diagrams are valuable for visualizing the functional requirements of a system that will
translate into design choices and development priorities.

They also help identify any internal or external factors that may influence the system and should be
taken into consideration.

They provide a good high level analysis from outside the system. Use case diagrams specify how the
system interacts with actors without worrying about the details of how that functionality is
implemented.

Basic Use Case Diagram Symbols and Notations

 System

Draw your system's boundaries using a rectangle that contains use cases.

 Use Case

Draw use cases using ovals. Label the ovals with verbs that represent the system's functions .

 Actors

Actors are the users of a system. When one system is the actor of another system, label the
actor system with the actor stereotype.

 Relationships

Illustrate relationships between an actor and a use case with a simple line. For relationships
among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship
indicates that one use case is needed by another in order to perform a task.
Figure 5: Use Case for Employee Management System
Experiment 5: Object and Class Diagrams using UML

What is an object diagram in UML?

A UML object diagram represents a specific instance of a class diagram at a certain moment
in time. When represented visually, you'll see many similarities to the class diagram. An
object diagram focuses on the attributes of a set of objects and how those objects relate to
each other.

Object diagrams are simple to create: they're made from objects, represented by rectangles,
linked together with lines. Take a look at the major elements of an object diagram.

 Objects
 Class Titles
 Links

Figure 6: Object and Class Diagram for Employee Management System