0% found this document useful (0 votes)
362 views

Software Engineering Lab Manual

The document discusses the software development life cycle (SDLC) process, which includes planning, requirements analysis, design, coding, testing, deployment, and maintenance. It explains the phases of the SDLC in detail and lists some common SDLC models like waterfall, prototyping, and spiral. The SDLC is used by software engineers to design, develop, and maintain high-quality software.

Uploaded by

Shivansh Pundir
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
362 views

Software Engineering Lab Manual

The document discusses the software development life cycle (SDLC) process, which includes planning, requirements analysis, design, coding, testing, deployment, and maintenance. It explains the phases of the SDLC in detail and lists some common SDLC models like waterfall, prototyping, and spiral. The SDLC is used by software engineers to design, develop, and maintain high-quality software.

Uploaded by

Shivansh Pundir
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Software Engineering Lab Manual

Experiment-1

Ques. Explain the term SDLC.


Ans. SDLC stands for software development life cycle. It is a
process used by the software industry to design, develop and
test high quality software.
It consists of a detailed plan describing how to develop,
maintain, replace and change or improve specific software.
Major software development activities include gathering
requirements, software design and implementation, code
testing, documentation and maintenance.

Many different software processes but all involve:


i) Specification – Defining what the system should do, all
the functionalities it should have.
ii) Design and implementation- Defining how to do the
project, designing a blueprint of the project and then
implementing it with technical tools and coding.
iii) Validation- checking that it does what the customer
wants’, all the functions are terminated successfully.
iv) Evolution- Changing the system in response to changing
customer needs.

Phases of Software Development Life cycle


1. Planning: Project leaders evaluate the terms of the
project. This includes calculating labor and material costs,
creating a timetable with target goals, and creating the
project’s teams and leadership structure.
Planning should clearly define the scope and purpose of
the application.  It also keeps the boundaries to help the
project from expanding or shifting from its original
purpose.
2. Requirement Analysis : Requirements include defining
the resources needed to build the project.
3. Design and Prototyping: The Design phase models the
way a software application will work. Some aspects of
design include architecture, user interface,
platforms(for ios, Android, Web app ) ,Programming
language, Security etc.
4. Coding: This is the actual writing of the program. A
small project might be written by a single developer,
while a large project might be broken up and worked
by several teams. Coders May use pre written
libraries to avoid complex errors and to make the
code look clean.
5. Testing: This is also an important part of sdlc. Once
the project code is completing it must be tested
against random input and see the delivered output.
Whether they match the user requirements or not.
Automated software’s are also used to generate the
test cases and see how our code works.
6. Deployment: In this phase the software is made
available to the user. The software can be deployed
on cloud or Google play store, apple store depending
on access level of user.
7. Maintenance: There can still be some bugs or errors
which were not detected during the testing phase and
the user might come across these bugs. Therefore
the code has to be maintained.
Some SDLC Models are:-
 Code and fix Model
 Waterfall Model
 V- Model
 Incremental Implementation
 Prototyping model
 Spiral model
Experiment -2
Software crisis

Objective To identify the problem related to software crisis for a given scenario

ProblemDescription

In the context of this background, for each of the scenario mentioned below,
identify the most appropriate problem related to software crisis and mention the
same in the table provided.

Scenario A
Railways reservation software was delivered to the customer and was installed
in one of the metro station at 12.00 AM (mid-night) as per the plan. The system
worked quite fine till the next day 12.00 PM(noon). The system crashed at
12.00 PM and the railways authorities could not continue using software for
reservation till 02.00 PM. It took two hours to fix the defect in the software.

Scenario B
A polar satellite launch vehicle was scheduled for the launch on August 15th.
The auto-pilot of the rocket to be delivered for integration of the rocket on may
15th. The design and development of the software for the auto-pilot more effort
because of which the auto-pilot was delivered for the integration on June 15 th
(delayed by a month). The rocket was launched on Sep 15th (delayed by a
month).

Scenario C
Software for financial systems was delivered to the customer. Customer
informed the development team about a mal-function in the system. As the
software was huge and complex, the development team could not identify the
defect in the software.

Scenario D
Due to the defect in the software for the baggage handling system. There was
also of & 2M of revenues for the airport authorities.
Scenario Situation (as given A to D)

Situation for scenario A

Failure at customer site


The software developed is very in efficient and of low quality.

The project work fine from 12 AM to 12 PM but later it crashed, it may be due to
busy server or database connection failure. But it surely depicts that the project
was not efficient enough to handle such amount of requests from the user.

Situation for scenario B

Time slippage
The code for the autopilot of the project was delivered late.

It may be due to lack of planning, bugs in the code or the designing took too
much time. The lack of programming may have made the developers to go out of
course which may have taken time.

Situation for scenario C

Intractable code after delivery


The code was difficult to maintain and Projects were a mess and unmanageable.

The developers coded and delivered the project to the user. But later when the user
discovered a bug and informed about the bug. The Code being so unmanageable is
not understood by the new team which is handling the maintenance part.

Situation for scenario D

Cost slippage

The budget of the project crossed the budget which was deciced during the start of
the project.

Experiment-3
Objective: To identify the suitable software development model for the given case
studies/scenario.
Case Study-1

“ABC” is a new enterprise recently started by a few young entrepreneurs, intended to develop
robotic systems using IT based solutions. “TENZ” is a well-established automobile
manufacturing plant, interested in automating some of the operations of the plant as first step
towards automation, TENZ has decided to deploy a robotic arm to pick and place large number
of bolts from one tray of a conveyer belt to another tray of a different conveyer belt. Moving
one bolt at a time. TENZ has asked ABC for demonstration the robotic arm for the said purpose
as a proof of concept. This is the first project being executed by ABC.TENZ would like to have a
first experience of the robotic arm before signing the MOU (Memorandum of Understanding)
with ABC. After MOU sign-off, TENZ would provide the complete set of requirement of the
robot.

Ans- Prototype or incremental.

Case Study-2

ABC is an international software house. ABC is currently working on a project that is totally new
for the development team and even the client is confused about the requirements of this
project. Hence this company is facing difficulties because they fail to apprehend user
requirements properly. For this project, it is decided to build a sample application and show it
to the client for feedback. In the context of this above scenario as a project manager what will
be the choice of the software lifecycle model?

Ans- Prototype Model, as the customer is not aware about the requirements.

Case Study-3
SMART_TECHY is a software development company working for online shop of
electronic equipment. The different tasks that are expected from the teams in the
company are as follows:

· The registered users must be allotted with an initial password after registration the
user should be able to change the password keep his/her account secure.

· The people who are browsing through the shopping website, want to subscribe
through the mailing list so that they can get updates about discount, availability of the
product and they can buy the product.

· The graphics on the website must be catchy, to the point and must be optimized for
memory and time.

· The admin must give security support so that there is no unauthorized access by
earlier employees or other intruders.

· The shopping must be available on mobile app, so that all the data can be saved on
cloud, and it can be accessed from anywhere.

· Finally, all the information should be stored in a database in a proper data model

Suppose you are a project manager for a software product in a new and growing market
with your competitors who are also developing a product will be the same product.
Which model to select and why? How will you decide the tasks and the assignment to
the team members?

Ans) Waterfall model will be used. The customer is very clear about his/her requirements. The
requirements are also fixed. First requirements will be analyzed, based upon the analysis a
design would be made followed by coding, testing and at last deployment.

Case Study-4

There is a software project called “Election management system” and we want to choose a
process model. What do you think is the suitable one? The software requirements are clear.

Ans) Waterfall model as requirements is very clear. Even the time taken will be more due to
security purpose.

Case Study-5
Video-Rental LTD is a small video rental store. The store lends videos to customers for a fee,
and purchases its videos from a local supplier. A customer wishing to borrow a video provides
the empty box of the video they desire, their membership card, and payment – payment is
always with the credit card used to open the customer account. The customer then returns the
video to the store after watching it. If a loaned video is overdue by a day the customer’s credit
card is charged, and a reminder letter is sent to

them. Each day after that a further card is made, and each week a reminder letter is

Sent. This continues until either the customer returns the video, or the charges are equal to the
cost of replacing the video. New customers fill out a form with their personal details and credit
card details, and the counter staff give the new customer a membership card. Each new
customer’s form is added to the customer file. The local video supplier sends a list of available
titles to Video-Rental LTD, who decide whether to send them an order and payment. If an order
is sent, then the supplier sends the requested videos to the store. For each new video a new
stock form is completed and placed in the stock file.

Ans) Waterfall model.

Case Study-6

To develop the Home Health portion of General Hospital that keeps track of the billing and
Medicare requirements and payments. The current system was not scalable to the growing
needs and transformation within the environment. Thus, in addition to specific desirable
criteria of the chosen software, our explicit purpose in helping General was twofold: 1) to
modernize their operations with current technology; and 2) to provide the best patient care
available to their clients in the Home Health arena.

Ans)

Case Study-7
The Income tax filing portal, will undergo changes as and when the change in the income tax
rules come into effect. The requirements are clear and already existing systems may have to
undergo changes.

Ans) incremental

Case Study-8

The required LMS is a digital learning environment used to support learning in schools with
students from age 4 to 18. It is intended to replace an existing system (Glow) that was specially
built for the purpose and which includes its own applications for e-mail, etc. Clients are from
non-technical background. Users did not care about the system requirements and did not have
time to interact with the development team. Secondly, stakeholders simply did not understand
the terminology or approaches used – terms such as use-case simply made no sense to them.

Case Study-9

Airbus 340 flight control system is a safety critical system that implements the fly-by-wire flight
system on the Airbus. The Airbus A340 is a long-haul aircraft that includes a critical fly-by-wire
flight control system that mediates pilot commands and controls flight surface actuators. This is
a development of the first fly-by-wire system which was introduced in the Airbus A320 aircraft.

Ans) Spiral model as there is high risk analyses involved in the process.

Case Study-10

You are interacting with the MIS department of a very large oil company with multiple
departments. They have a complex regency system. Migrating the data from this legacy

system is not an easy task and would take a considerable time. The oil company is very

particular about processes, acceptance criteria and legal contracts.

Ans) Spiral model. Risk is high.

Experiment 4 (Requirement Development)


Objective :

To identify the various requirement development activities viz. elicitation,


analysis, specification and verification for the given scenarios.

Problem Description:

Identify the requirement development activities associated with each of the


following scenarios,

a. Joe is creating an online survey questionnaire for requesting user feedback on


the desired features of the application to be developed.

Ans) Elicitation

b. Mark is preparing a formal document which includes all of the desired features
identified by the survey.

Ans) Specification

c. Jack identified an incomplete requirement statement.

Ans) Verification

d. Jones is identifying all security related requirement and separating them from
the performance related requirements.

Ans) Analysis

e. Merlin a team member is sent to client to observe the business case and collect
typical user requirements.

Ans) Elicitation
f. Leo is team member is working on requirement and ensuring that requirement
collected should not be vague and unclear.

Ans) Validation

g. Lee is conducting a facilitated meeting with the stakeholder to capture the


requirements.

Ans) Elicitation

h. Amit a team member is distributing questionnaires to stack holder for gathering


user requirements.

Ans) Elicitation

Experiment 5
REQUIREMENT CLASSIFICATION

Problem Description: Classify the following requirement by selecting the


appropriate option.

1. ATM machine shall validate PIN of the user during login along with bio-
metric verification. Ans) Functional as working of machine is told.How
it should work.
2. “Peak transaction-20,000calls in Volume(s)a busy hour, average duration
20 Sec, grade of services 99.98%. Ans) Non Functional, no functioning
is mentioned only limitations are told.
3. “Brahe System sounds the alarm Shall for 10 seconds at frequency of 100H
when the brake is applied”. Ans) Functional as when brakes are applied
function happens.
4.“Mean Time Failure (MTTF) to -There should be no more than three
Severity-1 out age per month”. Ans) Non Functional

Experiment -6
Objective: SRS of Library Management System.

1. Introduction

1.1 Purpose: The objective of the project is to manage the


records of the books lend or returned by a student from the
library through a library Management System.

1.2 Project Scope:

1.2.1 The scope of the project is to provide assistance to the


library staff by automating their work.
1.2.2 To collect the information of the student who have
borrowed the book from the library.
1.2.3 To store the record of the books and stock of the books.

1.3 Definitions, acronyms and abbreviations:

1.3.1 SE- Software Engineering.


1.3.2 ML- Machine Learning.
1.3.3 CN- Computer Networks.
1.3.4 DAA – Design and analysis of Algorithms.
1.3.5 OS – Operating System
1.3.6 DBMS – Database Management System.
1.4 References:
1.4.1 IEEE Standard 830-1998 recommended practice for
software Requirements Specifications - Description.

2. Overall Description:

2.1 Product Perspective: The Library Management System will


keep the records of the books all the time. It will enable the
Organization to track which book is borrowed by a student
and for how many days. Accordingly, it can help to calculate
the penalty of defaulters.

2.2 Product Features:

2.2.1 Admin Login: Enables the Admin to login.


2.2.2 Add Books: Enables the admin to add books to stock.
2.2.3 Search Book: Enables the admin to search for book.
2.2.4 Search student: Enables the admin to search which student
have which book.

2.3 User Classes:

2.3.1 The system is for the university staff which can monitor
the book allotment process. They will have to login with
their username and password and do their desired work.

2.4 Operating Environment:


2.4.1 Operating System – Windows as it is easy to use.
2.4.2 Database- MySQL non distributed.
2.4.3 Backend language- node Js
2.4.4 Server: Apache

3 Specification Requirements:
3.1 Librarian should be able to allot books
3.2 Library staff should be able to deallocate books once returned
3.3 Data of student should be kept till he returns book.
3.4 Search for availability of books.
4 Other non-functional Requirements:
4.1 Performance Requirements: The system should be able to
handle minimum 10 users at a time.
4.2 Safety Requirements: The system should be secure and should
not leak any sensitive data.
4.3 Maintenance: It should be fast and regular changes must be
updated to make system run smoothly.

Experiment -7
Objective: To draw use case diagram of a bank management System.

You might also like