SE LAB MANUAL

Name: Sureddy Tanuja

Regno: RA2132003010015

Lab Name: Software Engineering Lab.

Lab Code: PIT21C103J

Branch: Computer Science

Semester: 1st

Syllabus :

1. Develop requirements specification for a given problem (The requirements specification

should include both functional and non-functional requirements. For a set of about 20 sample
problems
2. Develop DFD Model (Level 0, Level 1 DFD and data dictionary) of the sample problem (Use of
a CASE tool required). (1 class)
3. Develop Structured design for the DFD model developed. (1 class)
4. Develop UML Use case model for a problem (Use of a CASE tool any of Rational rose, Argo
UML, or Visual Paradigm etc. is required)
5. Develop Sequence Diagrams
6. Develop Class diagrams.

Lab Objective

The Software Engineering Lab has been developed by keeping in mind the following objectives:

1. To impart state-of-the-art knowledge on Software Engineering and UML in

an interactive manner through the Web.
2. Present case studies to demonstrate practical applications of different concepts.
3. Provide a scope to students where they can solve small, real life problems.
Lab Outcome

1. Can produce the requirements and use cases the client wants for the software
being produced.
2. Participate in drawing up the project plan. The plan will include at least extent and
work assessments of the project, the schedule, available resources, and risk
management can model and specify the requirements of mid-range software and their
architecture.
3. create and specify such a software design based on the requirement specification that
the software can be implemented based on the design.
4. Can assess the extent and costs of a project with the help of several different
assessment methods.
 List of Experiments

1. Develop requirements specification for a given problem.

2. Develop DFD model (level-0, level-1 DFD and Data dictionary) of the project.

3. Develop Structured design for the DFD model developed.

4. Develop UML Use case model for a problem.

5. Develop sequence diagram.

6. Develop Class diagrams

 Lab Experiment No.1
Develop requirements specification for a given problem

1.Document the SRS of College automation system.

Objective:
The main objective of the college automation system is to manage the details of faculties,
branches, registration, students, Guardians , courses. It manages all the information about
faculties, login, courses, students, Guardians.
The project is totally built at administrative end and thus only the administrator is guaranteed the
access.
The purpose of the project is to build an application program to reduce the manual work for
managing the information regrading students, faculties, login, Guardians etc.
It tracks all the details about the registration, students, courses, Guardians.

Procedure:

Step 1:
Introduction:
Purpose
The purpose of this document is to present a detailed description of the College Management
System. It will explain the purpose and features of the system, the interfaces of the system,
what the system will do, the constraints under which it must operate and how the system will
react to external stimuli. This document is intended for both the client and the developers of
the system and will be proposed to the Administrative head for its approval.
This document describes the software requirements specification (SRS) for the Collage
Automation System that provides the access and management of information of different
modules in a collage-like Students, Guardians, Teachers/Faculty, Finance, Examination, HR. The
advantage of the management system is to avoid entries in hard copies and it saves the burden of
hard copies of data.
There are two users for this system 1. Admin (have full access to read and write of all modules in
management system) 2. Teacher (have access limited to write and manage the student’s marks,
attendance, etc.).
The purpose of this document is to retrieve and analyze the ideas that define the product and
requirements that the user needs. This document describes the details of our product, its
parameter, and its goals. This SRS document describes the target, audience, user interface of
product and Software/Hardware requirements of our product. This document also describes the
problem we have faced during the designing and implementation of the product and also
describes how we have solved this problem and make our product more efficient.

Project Scope
As Colleges are growing day by day more and more, and also increasing the complexity of
storing information of students and related to the college system, they face many related issues:
attendance and fee of students, salary details of employees, etc.
This project is based on the educational institute system where this application gives maximum
services in a single software product that is used by teacher and system administration. This
project is based on a desktop application that is sharing information on different departments in a
college.
The main focus of this project is to give the best GUI for the users and provide the many
modules in a single product. Admin can view all of the information that is stored in the database
through application and admin also can modify this information because the admin has full
access to the system.
The teacher can view and modify the information related to students, teachers have limited
access. This project can adjust any additional module at any time.
Step 2:
Overall Description

Product Perspective
The product will be a standalone application and may be run on multiple systems within an
Internet network. The product will require a keyboard, mouse and monitor to interface with the
users. The minimum hardware requirements for the product are specified in this document
Product Features
This software system will be a College automation system for the members of an organization.
This system will be designed to maximize the administrative, academic and overall productivity
by providing tools to assist in automating the technical procedures and proccesses, which
would otherwise have to be performed manually. By maximizing the users work efficiency and
production the system will meet the users needs while remaining easy to understand and use.
It is a user-friendly portal to interact, manage, access the information.

User Classes and Characteristics

The target audience for CAS product is the college Administrator/students/faculty/staff
(Technical/Non-
technical)
.The users for this system are
•Administrator The Super user of the system.
Mainly focuses on administratiive and academic related issues.
•Student A user with limited access rights.
•Staff A user of the system who has more access rights than a normal user.
•Users for specific task.
- Warden/HEC head: For Hostel management
- Mess Committee Head: For mess

Operating Environment
The CAS is expected to be deployed in a real environment to manage the DBMS inside the
college. The centralized database is used to store the information. The user only within the
college (members of college staff) can use this management system. Users outside form the
college cannot access the management system. This application is developed for windows
operating system that can be run on Windows XP and above.
The database is used in different departments within a branch of the college. The database used
to store the information is the centralized database. The software we have developed will be
installed on different computer systems within a college and software will be connected to a
centralized database through LAN within a college and then the user can interact with the system
and can store the data and other users can get access the stored through a centralized database.
Design and Implementation Constraints
During the implementation of the product, different challenges are faced. Choosing the interface
for the management system was a paramount issue. Connecting the database with the application
was a major problem.
For connecting the database we had to create our account in ORACLE and then we had to
download the driver(software). The connection of the database that is created in ORACLE with
C# is not very simple as like SQL. So the installation of ORACLE driver(software) is necessary
to create a connection between ORACLE and C#. But after installing the required driver it
creates a problem in installing and connecting with a server in the oracle server, so we decided to
leave the oracle and then we choose the SQL server to create the database.
The SQL Server is easy to install and connect with a server in SQL it is very easy to understand
the implementation of the database and also easy to create a new database and connect with the
GUI application.

Step 3:
System Features
This system provides the security of data by authentication of users and in this project right of
users are defined. In this system, admin is the main user of the system who has full rights of all
modules within the proposed system and the other user which is an employee of college also can
be a teacher within the college has limited access to the system like students attendance and
marks of the students are managed by the employee. In this product, different reports can be
generated, pay slips of employee salary, fee report of fee payment if students, student details,
attendance report, etc.
The main modules which are focused on this project:
 Student management
 Employee management
 Student Fee management
 Employee salary payment
 User registration
 Internal Marks of students
 Attendance of students
 Reports of all modules 

Functional Requirements
This section includes the requirements that specify all the fundamental actions of the software
system

ID:FR1
TITLE:Login into the Portal.
DESC: The user can login into the system by providing its loginid and password to the portal
which are unique and provided by the college.
RAT:To login into the portal and take advantage of the services provided by it.
DEP:None

D:FR3
TITLE:View/change profile details.
DESC:The user can view or change some of his/her personal details like email id, contact details
and address details. The profile will contain name, age,permanent address, parent’s name, their
address, their contact details, branch, year, semester, room alloted, hostel name and no. etc.
RAT:To update his/her profile and know his or her status.
DEP:FR1

ID:FR8
TITLE:Academics
DESC:This module on dashboard contains all the information about the academics and admin-
istration.
RAT:You can get all the information about academics after getting inside this module.
DEP:FR1

ID:FR11
TITLE:Faculty
DESC:This module provides the information about the faculties. This includes name, education
details, areas of interest and expertise, email id and contact details(optional).
RAT:You can get all the information about faculties in one place after getting inside this mod-
ule.
DEP:FR1,FR8

D:FR14
TITLE:Exam Schedule
DESC:The user can view the exam schedule.
RAT:By using this feature,the user can prepare and plan his efforts in a better way.
DEP:FR1,FR8

ID:FR26
TITLE:List of upcoming holidays
DESC:The user can view the list on upcoming holidays on the front page of the portal after
logging into the system.The user will also have the right and access to change/modify the list.
RAT:He/she plans for vacations and other co-curricular activites.
DEP:FR2
D:FR63
TITLE:Feedback/Complains
DESC: In this form, one can lodge a complaint or give a feedback by selecting the
domain:
Academics, Administration, Hostel, Mess, Transportation.The user will deal with the complains
and feedback information related to hostel.
RAT:The user can get relieve from his/her problems without much effort or conflicts.
DEP:FR55

D:FR18
TITLE:Result
DESC: Student can access their results of past semester and generate a pdf file and print by
logging into the portal. The user can not view results of other students.
RAT:The user can easily keep track of his/her academic performance.
DEP:FR1,FR8

ID:FR16
TITLE:Fee Receipt Generation
DESC: Student can generate fee receipt by giving the bank details in the system authenticated
by the administrative head for the current and the previous semesters.
RAT:This feature makes the process move convinient,fast and less cumbersome.
DEP:FR1,FR8

Step 4:
External Interface Requirements
User Interfaces
A first-time user of the web portal should see the log-in page when he/she opens the portal.
If the user has not registered, he/she should be able to do that on the log-in page. It will
also have a remember me button.If the user is not a first-time user, he/she should be
able to see the dashboard which contains different domains like academics, Hostel, Profile,
Mess, Transport.A news bulliten, some general information, list of holidays and different
timetables will also be visible on this page.Every user should have a profile page where
they can edit their e-mail address, phone number and password and other personal details.
Hardware Interfaces
Client:
•Hardware platform:
- PIII or above with
- RAM of 512 or above MB
- HardDisk 20GB or above GB

Server:
•Hardware Platform:
- PIII or above with
- RAM of 512 or above MB
- HardDisk 20GB or above GB

Software Interfaces
Client:
Software Platform:
Browser :
- Mozilla Fire-Fox v12.0 or higher
- Google Chrome v27.0.1453.116m or higher

Server:
Software Platform:
-HTML, PHP, JavaScript, MySQL, Apache, CSS, MVC, Bootstrap

Communications interfaces
The communication between the client and the server will be done through internet.

Nonfunctional Requirements

Performance Requirements
Performance should not be an issue because all of our server queries involve small pieces of
data.
Changing screens will require very little computation and thus will occur very quickly.
Server
updates should only take a few seconds as long as the phone can maintain a steady signal.

Security Requirements
Administrator and Users with valid credentials will be able to log in to Portal. Administrator
will have access to the database structures at back-end administrator will have the rights for
modifications as well as any updation work for the datasets and website. Access to the various
subsystems will be protected by a user log in screen that requires a user name and password. To
be updated in future

Safety Requirements
Reliability
Must maintain data integrity. Computer crashes and misuse should not affect a user’s history

Software Quality Attributes

Availability
The CAS Portal shall be available, up and running for 24*7 throughout the year except due to
the routine maintenance activities.

2. Document the SRS of Banking Management System.

Objective:
 The main aim of this project is to develop software for bank management system. This project is to
develop software for bank management system. This project has been developed to carry out the
processes easily and quickly, which is not possible with the manuals systems, which are overcome by this
software. This project is developed using VB language and. Hence it provides the complete solution for
the current management system.
Procedure:
Step 1: Introduction:
Purpose
The main purpose that banks have been serving since their inception is keeping our money safe for
us. While keeping our money safe, they also let us earn a certain amount of interest on the money
deposited with them. Traditional banks have been doing this, and internet banks continue the same
function. The only difference is in the way the transactions are made.We all know about internet
banking but few of us actually understand about the history of internet banking and how it all came
out. Knowing history of internet banking can be incredibly useful, especially since it will allow us to
have more respect for the little things that we take for granted internet banking has been around for
quite a few years now, but has really only become prominent over the past year or so in particular.
Project Scope
The Scope of this project is limited to the activities of the operation units of the banking system
which include opening of account, deposit of funds, withdrawal of funds & transfer. Any bank can
use this application to provide better service to their customers. Customers can access his/her all
accounts present in various branches of the same bank at one click. Bank can publish various
upcoming plans for customers through this application. Manager can access all accounts present in
the bank through this application. Reduction in work load of all employees will possible through this
application as transaction rights are provided online to customer.It can be extended for global
communication between all banks in the world.

Step 2: Overall Description

Product Perspective

3. Why we need SRS in any Project.

A software requirements specification is the basis for your entire project. It lays the framework
that every team involved in development will follow.

It’s used to provide critical information to multiple teams — development, quality assurance,
operations, and maintenance. This keeps everyone on the same page.

Using the SRS helps to ensure requirements are fulfilled. And it can also help you make
decisions about your product’s lifecycle — for instance, when to retire a feature.

Writing an SRS can also minimize overall development time and costs. Embedded development
teams especially benefit from using an SRS.

4. Which part of SRS is more important?

The important parts of the Software Requirements Specification (SRS) document are:
1. Functional requirements of the system
2. Non-functional requirements of the system, and
3. Goals of implementation

5.What is the difference between functional and nonfunctional requirement.

Functional Requirements: These are the requirements that the end user specifically
demands as basic facilities that the system should offer. All these functionalities need to be
necessarily incorporated into the system as a part of the contract. These are represented or
stated in the form of input to be given to the system, the operation performed and the
output expected. They are basically the requirements stated by the user which one can see
directly in the final product, unlike the non-functional requirements.
Non-functional requirements: These are basically the quality constraints that the system
must satisfy according to the project contract. The priority or extent to which these factors
are implemented varies from one project to other. They are also called non-behavioral
requirements.
They basically deal with issues like:
 Portability
 Security
 Maintainability
 Reliability
 Scalability
 Experiment No. 2

AIM OF THE EXPERIMENT:

Develop DFD model (level-0, level-1 DFD and Data dictionary) of the project.

1.what are the symbols used in a DFD.

Data Flow Diagram symbols are standardized notations, like rectangles, circles, arrows, and
short-text labels, that describe a system or process’ data flow direction, data inputs, data
outputs, data storage points, and its various sub-processes.
 2. What is an external entity?

An external entity, which are also known as terminators, sources, sinks, or actors, are an outside
system or process that sends or receives data to and from the diagrammed system. They’re either
the sources or destinations of information, so they’re usually placed on the diagram’s edges.
External entity symbols are similar across models except for Unified, which uses a stick-figure
drawing instead of a rectangle, circle, or square.

3.What is a context free diagram?

The context diagram is used to establish the context and boundaries of the system to be
modelled: which things are inside and outside of the system being modelled, and what is
the relationship of the system with these external entities.
 A context diagram, sometimes called a level 0 data-flow diagram, is drawn in order to
define and clarify the boundaries of the software system. It identifies the flows of
information between the system and external entities. The entire software system is
shown as a single process.

4.What is Data-dictionary?
Data dictionary lists all data items appearing in the DFD model of a system. The data
items listed include all data flows and the contents of all data stores appearing on the
DFDs in the DFD model of a system. A data dictionary lists the purpose of all data items
and the definition of all composite data items in terms of their component data items. For
example, a data dictionary entry may represent that the data grossPay consists of the
components regularPay and overtimePay.

5.Why balancing of DFD is required.

The concept of balancing states that all the incoming flows to a process and all the outgoing
flows from a process in the parent diagram should be preserved at the next level of
decomposition.
Process decomposition lets you organize your overall DFD in a series of levels so that each level
provides successively more detail about a portion of the level above it.
The goal of the balancing feature is to check your system internal consistency, which is
particularly useful as different levels of expertise are generally involved in a project.
When you decompose a process, PowerDesigner helps you initialize, in the sub diagram, the
objects from the upper-level to link to the sub-process. PowerDesigner automatically retrieves
global objects, such as external entities or data stores and creates object shortcuts, if need be.

Lab Experiment No.3

Develop Structured design for the DFD model developed.

1.Draw the DFD of College Automation System.

Level 0
 Level 1

Level 2

2.How we balance a DFD.

Parent dfd having inflow and out flow of data should match data flow at next child
level. This is known as balancing a DFD.
Rules of DFD / Balancing

 Data flow that comes into and out from one process must equal to data that comes into
and out from process details in level/stage under it

 Data flow name that comes into and out from one process must equal to data flow name
that enters into and out from the process details

 Total and outside entity name from a process must equal to the total and outside entity
name from the process details

 The matters that must be focused in DFD that has more than one level:

3.Draw the DFD of Banking Management System.

Level 0

Level 1
4.How we choose the level of DFD.
Leveling is done by drawing a series of increasingly detailed diagrams until the desired degree of
detail is reached. As shown in the Figure, DFD Leveling is first displaying the targeted system as
a single process, and then showing more detail until all processes are functional primitives.

5. What is the need of DFD in a project.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be
used as a communication tool between a system analyst and any person who plays a part in the
order that acts as a starting point for redesigning a system. The DFD is also called as a data flow
graph or bubble chart.

Experiment No.4
Develop UML Use case model for a problem

1.What is the importance of UML.

The Unified Modeling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the artifacts of software systems, as well as for business modeling
and other non-software systems. This study focuses on the importance of UML diagrams (class,
use case, sequence, activity, component, deployment) during s/w development. It has been found
that all the UML diagrams plays vital role in s/w development. But class diagram is the most
favoured diagram. After class diagram sequence & Use case diagrams are mostly used in s/w
development. Deployment diagram has been the least used diagram among the other UML
diagrams.

2.What are the UML foundations.

UML notations are used to describe UML semantics. In the present version (1.0), the meta-
model consists of five core UML concepts: Common concepts (basic types); Structural Elements
(types and relationships); Behavioural Elements (state machines and interactions); View
Elements and Standard Elements.
3. What is Use case.
 use case diagram is a graphical depiction of a user's possible interactions with a system. A
use case diagram shows various use cases and different types of users the system has and will
often be accompanied by other types of diagrams as well.

4.Who are the actors in a UML.

In UML, an actor is a model element that interacts with a system. As a model element, it can be
an abstract person (e.g. “customer”) or another external system. In the practice of modeling it is
recommended to define the role unambiguously with stereotypes – e.g. “User”, “Stakehoder” or
“External System”.
In principle, however, an actor can not only be
 the creator of an action (such as the initiator of an application case)
 but also the recipient of an expected result.

5.What is boundary in a USE CASE.

A system boundary is a rectangle that you can draw in a use-case diagram to separate the use
cases that are internal to a system from the actors that are external to the system. A system
boundary is an optional visual aid in the diagram; it does not add semantic value to the model.

6. Make ATM Diagram.

 Lab Experiment No.5
Develop sequence diagram

1.Draw the Sequence diagram of College Automation System.

2.What is the need of sequence diagram in a project?
The sequence diagram is a good diagram to use to document a system's requirements and to
flush out a system's design. The reason the sequence diagram is so useful is because it shows
the interaction logic between the objects in the system in the time order that the interactions take
place.
And it describes how—and in what order—a group of objects works together.

3.What is the difference between nested level and single level sequence?
If you choose Single Level, all sequence messages will be ordered with integers on diagram
base. On the other hand, if you choose Nested Level, all sequence messages will be ordered
with decimal place on diagram base.

4.Draw the Sequence diagram of Banking Management system.

 Experiment No. 6:

Develop Class diagram

1.Define Class.
A class diagram is an illustration of the relationships and source code dependencies among
classes in the Unified Modeling Language (UML). In this context, a class defines the methods
and variables in an object, which is a specific entity in a program or the unit of code
representing that entity.

2.What is the difference between Class diagram and UML.

The main difference between UML and class diagram is that the UML is a general-purpose
visual modeling language that helps to visualize, construct and document software systems
while class diagram is a type of UML diagram that represents the static view of an
application.
When developing software, it is not possible to develop it at once. It is important to get an
understanding of the system before implementing them. UML provides a solution to this issue. It
is a visual language that allows modeling the system. There are various UML diagrams. Class
diagram, which is a static diagram, is one of them.

3.What is dependency.

A dependency means the relation between two or more classes in which a change in one may
force changes in the other. However, it will always create a weaker relationship. Dependency
indicates that one class depends on another.

In the following UML class diagram examples, Student has a dependency on College

. 

4.What is composition.
The composition is a special type of aggregation which denotes strong ownership between two
classes when one class is a part of another class.

For example, if college is composed of classes student. The college could contain many students,
while each student belongs to only one college. So, if college is not functioning all the students
also removed.

5.Define Recursive Association.

A recursive association connects a single class type (serving in one role) to itself (serving in
another role). Example: In most companies, each employee (except the CEO) is supervised by
one manager. Of course, not all employees are managers.