Software Engineering

LAB FILE
submitted towards the partial fulfillment of

the requirement for the award of the degree of

Bachelor of technology
In
Computer Engineering
Submitted By-

Abhay Sharma
2K20/CO/015
 EXPERIMENT - 1
Software is a program or set of programs containing instructions that provide
desired functionality. Engineering is the process of designing and building
something that serves a particular purpose and finds a cost-effective solution to
problems.

Software Engineering is a systematic, disciplined, quantifiable study and

approach to the design, development, operation, and maintenance of a software
system.

Dual Role of Software:

1. As a product –

● It delivers the computing potential across networks of Hardware.

● It enables the Hardware to deliver the expected functionality.
● It acts as an information transformer because it produces, manages,
acquires, modifies, displays, or transmits information.

2. As a vehicle for delivering a product –

● It provides system functionality (e.g., payroll system)

● It controls other software (e.g., an operating system)
● It helps build other software (e.g., software tools)
Objectives of Software Engineering:
1. Maintainability –
It should be feasible for the software to evolve to meet changing
requirements.
2. Efficiency –
The software should not make wasteful use of computing devices such
as memory, processor cycles, etc.
3. Correctness –
A software product is correct if the different requirements as specified in
the SRS document have been correctly implemented.
4. Reusability –
A software product has good reusability if the different modules of the
product can easily be reused to develop new products.
5. Testability –
Here software facilitates both the establishment of test criteria and the
evaluation of the software with respect to those criteria.
6. Reliability –
It is an attribute of software quality. The extent to which a program can
be expected to perform its desired function, over an arbitrary time
period.
7. Portability –
In this case, the software can be transferred from one computer system
or environment to another.
8. Adaptability –
In this case, the software allows differing system constraints and the
user needs to be satisfied by making changes to the software.
 9. Interoperability – Capability of 2 or more functional units to process
data cooperatively.

Program vs Software Product:

1. A program is a set of instructions that are given to a computer in order
to achieve a specific task whereas software is when a program is made
available for commercial business and is properly documented along
with its licensing. Software=Program+documentation+licensing.
2. A program is one of the stages involved in the development of the
software, whereas a software development usually follows a life cycle,
which involves the feasibility study of the project, requirement gathering,
development of a prototype, system design, coding, and testing.

Experiment - 2
Existing process of the getting information for the student is done manually. All
the wanted information need to be provided by the administration. If the students
want to know the results of the particular subject so their should wait for long time
because work done manually. The information about their courses , results and
other information accessing is not possible. Sometimes the existing system have
time consuming to fetch the data and in proper manner
Existing algorithm/programs:

As mentioned previously, today there exists some computer program which helps
users to find and store basic information such as a student's name ,marks and
seat number. Rest all the computational work either needs a different program or
is done manually by faculties of that institution.

Disadvantages of existing system:

● O.S dependency if the computer program is coded in C language.

● The use of linear search in file handling might increase time complexity.
● NO advanced feature benefit can be used such as in web application.

Proposed approach and its advantage over existing system:

● User friendly (as faculties can easily use web based applications ).
● ALL time availability.(system remains available as long as the computer is
well connected with the network).
● Easy computation.
● Easy Storage of data.
● More efficient.
● Requires less effort and time.
 Experiment - 3
Elicitation Techniques
Stakeholder Analysis

Stakeholders can include team members, customers, any individual who is impacted by the
project or it can be a supplier. Stakeholder analysis is done to identify the stakeholders who
will be impacted by the system. This technique will make sure that all people who are
impacted by the system have a say in the project.

Brainstorming

This technique is used to generate new ideas and find a solution for a specific issue. The
members included for brainstorming can be domain experts, subject matter experts.
Multiple ideas and information give you a repository of knowledge and you can choose from
different ideas.

This session is generally conducted around table discussion. All participants should be
given an equal amount of time to express their ideas.

This technique will make sure that there is no communication gap. Things like what is to be
expected and risk factors are discussed.

Document Analysis/Review

This technique is used to gather business information by reviewing/examining the available

materials that describe the business environment. This analysis is helpful to validate the
implementation of current solutions and is also helpful in understanding the business need.

Document analysis includes reviewing the business plans, technical documents, problem
reports, existing requirement documents, etc. This is useful when the plan is to update an
existing system. This technique is useful for migration projects.
We can do a survey and research on different hotel management systems to gain more
insights about what all features can be implemented. It will help us in gaining an idea about
customer response towards online registration systems.

Prototyping

Prototyping is used to identify missing or unspecified requirements. In this technique,

frequent demos are given to the client by creating the prototypes so that client can get an
idea of how the product will look like. Prototypes can be used to create a mock-up of sites,
and describe the process using diagrams.

It will help to get a visual representation of the product and stakeholders can also provide
feedback easily.

Questionnaire

For Survey/Questionnaire, a set of questions is given to stakeholders to quantify their

thoughts. After collecting the responses from stakeholders, data is analyzed to identify the
area of interest of stakeholders.

Questions should be based on high priority risks. Questions should be direct and
unambiguous. Once the survey is ready, notify the participants and remind them to
participate.

We can use this technique to get a clear idea about what customers are expecting from the
product.

Experiment - 4
Functional Requirements
The functional requirements of this system are:

● Register new students.

● Record the attendance of students.
● Record the internal marks of students.
 ● Record the feed details of students.
● Register a new teacher/employee.
● Register a new user for the system.
● Record the salary details of employees.
● Record the course details and subject information.
● Record the scholarship details and information.
● Generate various reports for all transactions in the system.

Non- Functional Requirements of the College

Management System
In this system, the authentication of the user is an important factor. In this
system, user authentication will be done by login by username and password
and classified by user type. Users will get access to the system as
permissions are classified for that type of user.

The system has a consistent interface so that the system is easy to use and
in the interface of our system buttons and forms are used to enter data
related to a specific module.
 Experiment - 5
Use case diagram
Experiment - 6
ER Diagram