Software Engineering

Q.1.Explain the different phases involved in waterfall life cycle.

Ans:

Phase I – Modeling Phase

In this phase we view the software product as part of a larger system or
organization where the product is required. This is basically a system view
where all the system elements are created.
Phase II – Software Requirements Analysis
Here we have a phase where the requirements are gathered. The information
domain for the software is understood. The function, behaviour, performance
and interfacing of the software are determined. The requirements of the
software and the customer are decided upon.
Phase III – Design
This determines the data structures, the software architecture, the interface
representations and the procedural (algorithmic) detail that goes into
the software.
Phase IV – Code Generation
Here the actual programming is done to obtain the machine code; it is an
implementation of the design.
Phase V – Testing
The testing is a process that goes hand in hand with the production of the
machine code. There are a number of testing strategies. First unit testing is
done and then integration testing. Alpha testing is to see if the software is as
per the analysis model whereas beta testing is to see if the software is what
the customer wanted.
Phase VI – Installation
The software is released to the customer.
Phase VII - Maintenance
This is the largest phase of the software life cycle. Maintenance can be of
different types: to modify the software as the requirements of the customer
evolve, to remove the residual bugs in the software etc.
Q.2.What is the difference between SRS document and design
document?
Ans.
SRS document is a contract between the development team and the customer.
Once the SRS document is approved by the customer, any subsequent
controversies are settled by referring the SRS document. SRS document
defines the customer’s requirements in terms of Functions ,performance,
external interfaces and design constraints.
 SRS Includes
 Functional
 Non functional
 User
 Interface
 System
Design Document
The purpose of a design is to describe how the enhancements will be
incorporated into the existing project. It should contain samples of
the finished product. This could include navigational mechanism
screenshots, example reports, and component diagrams.

D e s i g n I n c l u d e s :

E-R Diagrams
Data flow diagrams
Data Dictionary
Q.3. What is Software Development Life Cycle (SDLC)?
Ans:-
SDLC is a process followed for software building within a software
organization. SDLC consists of a precise plan that describes how to
develop, maintain, replace, and enhance specific software. The life cycle
defines a method for improving the quality of software and the all-around
development process.
Stages of the Software Development Life Cycle
SDLC specifies the task(s) to be performed at various stages by a software
engineer or developer. It ensures that the end product is able to meet the
customer’s expectations and fits within the overall budget. Hence, it’s vital
for a software developer to have prior knowledge of this software
development process.
The SDLC model involves six phases or stages while developing any
software. SDLC is a collection of these six stages, and the stages of SDLC
are as follows:
Stage-1: Planning and Requirement Analysis
Planning is a crucial step in everything, just as in software development. In
this same stage, requirement analysis is also performed by the developers of
the organization. This is attained from customer inputs, and sales
department/market surveys.
The information from this analysis forms the building blocks of a basic
project. The quality of the project is a result of planning. Thus, in this stage,
the basic project is designed with all the available information.
Stage-2: Defining Requirements
In this stage, all the requirements for the target software are specified. These
requirements get approval from customers, market analysts, and
stakeholders.
This is fulfilled by utilizing SRS (Software Requirement Specification).
This is a sort of document that specifies all those things that need to be
defined and created during the entire project cycle.
Stage-3: Designing Architecture
SRS is a reference for software designers to come up with the best
architecture for the software. Hence, with the requirements defined in SRS,
multiple designs for the product architecture are present in the Design
Document Specification (DDS).
This DDS is assessed by market analysts and stakeholders. After evaluating
all the possible factors, the most practical and logical design is chosen for
development.
Stage-4: Developing Product
At this stage, the fundamental development of the product starts. For this,
developers use a specific programming code as per the design in the DDS.
Hence, it is important for the coders to follow the protocols set by the
association. Conventional programming tools like compilers, interpreters,
debuggers, etc. are also put into use at this stage. Some popular languages
like C/C++, Python, Java, etc. are put into use as per the software
regulations.
Stage-5: Product Testing and Integration
After the development of the product, testing of the software is necessary to
ensure its smooth execution. Although, minimal testing is conducted at
every stage of SDLC. Therefore, at this stage, all the probable flaws are
tracked, fixed, and retested. This ensures that the product confronts the
quality requirements of SRS.
Documentation, Training, and Support: Software documentation is an
essential part of the software development life cycle. A well-written
document acts as a tool and means to information repository necessary to
know about software processes, functions, and maintenance. Documentation
also provides information about how to use the product. Training in an
attempt to improve the current or future employee performance by
increasing an employee’s ability to work through learning, usually by
changing his attitude and developing his skills and understanding.
Stage 6: Deployment and Maintenance of Products
After detailed testing, the conclusive product is released in phases as per the
organization’s strategy. Then it is tested in a real industrial environment. It
is important to ensure its smooth performance. If it performs well, the
organization sends out the product as a whole. After retrieving beneficial
feedback, the company releases it as it is or with auxiliary improvements to
make it further helpful for the customers. However, this alone is not enough.
Therefore, along with the deployment, the product’s supervision.
Q.4. What is Spiral Model. Explain its

The spiral model is a systems development lifecycle (SDLC) method used

for risk management that combines the iterative development process model
with elements of the Waterfall model. The spiral model is used by software
engineers and is favored for large, expensive and complicated projects.

When viewed as a diagram, the spiral model looks like a coil with many loops.
The number of loops varies based on each project and is often designated by
the project manager. Each loop of the spiral is a phase in the software
development process.

Spiral model example

The spiral model enables gradual releases and refinement of a product

through each phase of the spiral as well as the ability to build prototypes at
each phase. The most important feature of the model is its ability to manage
unknown risks after the project has commenced; creating a prototype makes
this feasible.
Uses of the spiral model
As mentioned before, the spiral model is best used in large, expensive and
complicated projects. Other uses include:

 projects in which frequent releases are necessary;

 projects in which changes may be required at any time;

 long term projects that are not feasible due to altered economic priorities;

 medium to high risk projects;

 projects in which cost and risk analysis is important;

 projects that would benefit from the creation of a prototype; and

 projects with unclear or complex requirements.

Spiral model phases

When looking at a diagram of a spiral model, the radius of the spiral represents the
cost of the project and the angular degree represents the progress made in the current
phase. Each phase begins with a goal for the design and ends when the developer or
client reviews the progress.Every phase can be broken into four quadrants: identifying
and understanding requirements, performing risk analysis, building the prototype and
evaluation of the software's performance.

Phases begin in the quadrant dedicated to the identification and understanding of

requirements. The overall goal of the phase should be determined and all objectives
should be elaborated and analyzed. It is important to also identify alternative solutions
in case the attempted version fails to perform.

Next, risk analysis should be performed on all possible solutions in order to find any
faults or vulnerabilities -- such as running over the budget or areas within the software
that could be open to cyber attacks. Each risk should then be resolved using the most
efficient strategy.
In the next quadrant, the prototype is built and tested. This step includes: architectural
design, design of modules, physical product design and the final design. It takes the
proposal that has been created in the first two quadrants and turns it into software that
can be utilized.

Finally, in the fourth quadrant, the test results of the newest version are evaluated.
This analysis allows programmers to stop and understand what worked and didn’t
work before progressing with a new build. At the end of this quadrant, planning for
the next phase begins and the cycle repeats. At the end of the whole spiral, the
software is finally deployed in its respective market.

Steps of the spiral model

While the phases are broken down into quadrants, each quadrant can be further broken
down into the steps that occur within each one. The steps in the spiral model can be
generalized as follows:

1. The new system requirements are defined in as much detail as possible. This
usually involves interviewing a number of users representing all the external or
internal users and other aspects of the existing system.

2. A preliminary design is created for the new system.

3. A first prototype of the new system is constructed from the preliminary design.
This is usually a scaled-down system, and represents an approximation of the
characteristics of the final product.

4. A second prototype is evolved by a fourfold procedure: (1) evaluating the first

prototype in terms of its strengths, weaknesses, and risks; (2) defining the
requirements of the second prototype; (3) planning and designing the second
prototype; (4) constructing and testing the second prototype.

5. The entire project can be aborted if the risk is deemed too great. Risk factors
might involve development cost overruns, operating-cost miscalculation and
other factors that could result in a less-than-satisfactory final product.
Benefits of the spiral model
As mentioned before, the spiral model is a great option for large, complex projects.
The progressive nature of the model allows developers to break a big project into
smaller pieces and tackle one feature at a time, ensuring nothing is missed.
Furthermore, since the prototype building is done progressively, the cost estimation of
the whole project can sometimes be easier.

Other benefits of the spiral model include:

 Flexibility - Changes made to the requirements after development has started can
be easily adopted and incorporated.

 Risk handling - The spiral model involves risk analysis and handling in every
phase, improving security and the chances of avoiding attacks and breakages. The
iterative development process also facilitates risk management.

 Customer satisfaction - The spiral model facilitates customer feedback. If the

software is being designed for a customer, then the customer will be able to see
and evaluate their product in every phase. This allows them to voice
dissatisfactions or make changes before the product is fully built, saving the
development team time and money.

Limitations of the spiral model

Limitations of the spiral model include:

 High cost - The spiral model is expensive and, therefore, is not suitable for small
projects.

 Dependence on risk analysis - Since successful completion of the project depends

on effective risk handling, then it is necessary for involved personnel to have
expertise in risk assessment.
Q.5.Differences between Black Box Testing vs White Box Testing:

Black Box Testing White Box Testing

1. It is a way of software testing in 1. It is a way of testing the software in

which the internal structure or the which the tester has knowledge
program or the code is hidden and about the internal structure or the
nothing is known about it. code or the program of the software.

2. Implementation of code is not needed 2. Code implementation is necessary

for black box testing. for white box testing.

3. It is mostly done by software

3. It is mostly done by software testers.
developers.

4. No knowledge of implementation is 4. Knowledge of implementation is

needed. required.

5. It can be referred to as outer or 5. It is the inner or the internal

external software testing. software testing.

6. It is a functional test of the software. 6. It is a structural test of the software.

7. This testing can be initiated based on 7. This type of testing of software is

the requirement specifications started after a detail design
document. document.

8. No knowledge of programming is 8. It is mandatory to have knowledge

required. of programming.

9. It is the behavior testing of the

9. It is the logic testing of the software.
software.

10. It is applicable to the higher levels of 10. It is generally applicable to the

testing of software. lower levels of software testing.

11. It is also called closed testing. 11. It is also called as clear box testing.
 Black Box Testing White Box Testing

12. It is least time consuming. 12It is most time consuming.

13. It is not suitable or preferred for

13It is suitable for algorithm testing.
algorithm testing.

14. Can be done by trial and error ways 14Data domains along with inner or
and methods. internal boundaries can be better tested.

Example: Search something on google by Example: By input to check and verify

using keywords loops

Black-box test design techniques-

White-box test design techniques-
 Decision table testing
 Control flow testing
 All-pairs testing
 Data flow testing
 Equivalence partitioning
 Branch testing
 Error guessing

Types of Black Box Testing: Types of White Box Testing:

 Functional Testing  Path Testing
 Non-functional testing  Loop Testing
 Regression Testing  Condition testing

It is less exhaustive as compared to white It is comparatively more exhaustive than

box testing. black box testing.
 WEB DESINGING
Practical No 01
Create an HTML Page to display the following table:

<html>
<body>
<table border="a" width="600px" cellpadding="0">
<tr><th>First Name</th>
<th>Last Name</th>
<th>Point</th>
</tr>
<tr><td>Eve</td>
<td>Jackson</td>
<td>94</td>
</tr>
<tr><td>John</td>
<td>Doe</td>
<td>80</td>
</tr>
<tr><td>Adam</td>
<td>Johnson</td>
<td>67</td>
</tr>
<tr><td>Jill</td>
<td>Smith</td>
<td>50</td>
</tr>
</table> </html>
 Practical No:-02
Design a html form using fieldset and legend

<html>
<head>
<title>APPLICATION FORM </title>
</head>
<body leftmargin="200px">
<center><h3>APPLICATION FORM </h3></center>
<form>
<fieldset>
<legend>Personal Details</legend>
<table width="100%" cellpadding="10px">
 <tr>
<td>Applicant's full name </td>
<td>
<select >
<option>--Select --</option>
<option>Mr.</option>
<option>Ms.</option>
<option>Others</option>
</select>
<input type="text" size="20"/>
</td>
<td>Care Of </td>
<td><label>Parents</label><input type="radio" name="care"
checked/><label>Guardian </label><input type="radio" name="care"/></td>

</tr>
<tr>
<td>Father's Name </td>
<td>
<select disabled >
<option>Mr.</option>
</select>
<input type="text" size="20"/>
</td>
<td>Mother's Name </td>
<td>
<select disabled >
<option>Mrs.</option>
</select>
<input type="text" size="20"/>
</td>
</tr>

<tr>
<td>Gender</td>
<td>
<label>Male</label><input type="radio" name="Gender"/>
<label>Female </label><input type="radio" name="Gender"/>
<label>Others </label><input type="radio" name="Gender"/>
</td>
<td>Date of Birth</td>
<td>
<input type="date"/>
</td>
</tr>
<tr>
<td>Marital Status</td>
<td>
 <select>
<option>--Select--</option>
<option>Single</option>
<option>Married</option>
<option>Divorced</option>
<option>Widowed</option>
</select>
</td>
<td>Category </td>
<td>
<select>
<option>--Select--</option>
<option>General</option>
<option>OBC</option>
<option>SC</option>
<option>ST</option>
</select>
</td>
</tr>
<tr>
<td>Handicapped </td>
<td><label>No</label><input type="radio" name="Handicapped"
checked/><label>Yes</label><input type="radio" name="Handicapped"/></td>
<td>Ex-Serviceman </td>
<td><label>No</label><input type="radio" name="Serviceman"
checked/><label>Yes</label><input type="radio" name="Serviceman"/></td>
</tr>
<tr>
<td>EWS </td>
<td><label>No</label><input type="radio" name="EWS"
checked/><label>Yes</label><input type="radio" name="EWS"/></td>

<td>Religion </td>
<td>
<select>
<option>--Select--</option>
<option>Hindu</option>
<option>Muslim</option>
<option>Jain</option>
<option>Christianity</option>
</select>
</td>
</tr>
</table>
</fieldset>
<fieldset>
<legend>Contact Details</legend>
 <table width="100%" cellpadding="10px">

<tr>

<td>Mobile Number</td>
<td><input type="tel"/></td>
<td>Email ID</td>
<td><input type="email"/></td>
</tr>
<tr>
<td>Address Line 1</td>
<td><input type="text"/></td>
<td>Address Line 2</td>
<td><input type="text"/></td>
</tr>
<tr>
<td>City</td>
<td><input type="text"/></td>

<td>State</td>
<td>
<select>
<option>--Select--</option>
<option value="Andhra Pradesh">Andhra Pradesh</option>
<option value="Andaman and Nicobar Islands">Andaman and Nicobar
Islands</option>
<option value="Arunachal Pradesh">Arunachal Pradesh</option>
<option value="Assam">Assam</option>
<option value="Bihar">Bihar</option>
<option value="Chandigarh">Chandigarh</option>
<option value="Chhattisgarh">Chhattisgarh</option>
<option value="Dadar and Nagar Haveli">Dadar and Nagar Haveli</option>
<option value="Daman and Diu">Daman and Diu</option>
<option value="Delhi">Delhi</option>
<option value="Lakshadweep">Lakshadweep</option>
<option value="Puducherry">Puducherry</option>
<option value="Goa">Goa</option>
<option value="Gujarat">Gujarat</option>
<option value="Haryana">Haryana</option>
<option value="Himachal Pradesh">Himachal Pradesh</option>
<option value="Jammu and Kashmir">Jammu and Kashmir</option>
<option value="Jharkhand">Jharkhand</option>
<option value="Karnataka">Karnataka</option>
<option value="Kerala">Kerala</option>
<option value="Madhya Pradesh">Madhya Pradesh</option>
<option value="Maharashtra">Maharashtra</option>
<option value="Manipur">Manipur</option>
<option value="Meghalaya">Meghalaya</option>
 <option value="Mizoram">Mizoram</option>
<option value="Nagaland">Nagaland</option>
<option value="Odisha">Odisha</option>
<option value="Punjab">Punjab</option>
<option value="Rajasthan">Rajasthan</option>
<option value="Sikkim">Sikkim</option>
<option value="Tamil Nadu">Tamil Nadu</option>
<option value="Telangana">Telangana</option>
<option value="Tripura">Tripura</option>
<option value="Uttar Pradesh">Uttar Pradesh</option>
<option
value="Uttarakhand">Uttarakhand</option>
<option value="West Bengal">West
Bengal</option>
</select>
</td>
</tr>
<tr>

<td>Pin Code</td>
<td><input type="text"/></td>
</tr>
</table>
</fieldset>
<fieldset>
<legend>Qualification Details</legend>
<table width="100%" cellpadding="10px">
<tr>
<th>Sr No.</th>
<th>Qualification</th>
<th>Board/University</th>
<th>Passing Year</th>
<th>Max Marks</th>
<th>Marks Obtain</th>
<th>Percentage</th>
</tr>

<fieldset>
<legend>Language Knowledge</legend>
<table width="100%">
<tr>
<td>Language</td>
<td>Reading</td>
<td>Writing</td>
<td>Spoken</td>
</tr>
<tr>
<td>Hindi</td>
 <td><input type="checkbox"/></td>
<td><input type="checkbox"/></td>
<td><input type="checkbox"/></td>

</tr>
<tr>
<td>English</td>
<td><input type="checkbox"/></td>
<td><input type="checkbox"/></td>
<td><input type="checkbox"/></td>

</tr>

</table> </fieldset>
<fieldset>
<legend>Identification Details</legend>
<table>
<tr>
<td>Aadhar Card Number</td>
<td><input type="text" maxlength="12"/></td>
<td>PAN Card Number</td>
<td><input type="text" maxlength="9"/></td>
</tr>

</fieldset>
<br/>
<center>
<input type="submit" value="Submit"/>
<input type="reset" value="Back"/>
</center>
</form>
</body>
</html>
 Practical No:-03

HTML code for creating the following output

<html>
<body>
<table>
<tr>
<th><u>Online Courses</u></th>
</tr>
<tr> <td> <ol> <li>
Web Programming
<ul type="square">
<li>HTML 5</li>
<li>CSS 3</li>
<li>JavaScript</li>
</ul>
</li>
<li>
PHP Framework
<ul type="square">
<li>Laravel</li>
<li>Cupcake</li>
<li>Slim</li>
</ul>
</li>
</ol>
</td>
</tr>
<tr>
<td>20% Dicount for the ten Student Contact us on 9900990000</td>
</tr>
</table>
</body>
</html>
 Practical No:-04

HTML Code design Time Table using rowspan and colspan

<!doctype html>
<html>
<head>
<title>Table Assignment 2 </title>
</head>
<body>
<table border="1" align="center" width="60%"
cellpadding="10px">
<tr>
<th colspan="6">Time Table</th>
</tr>
<tr>
<th rowspan="6">Hours</th>
<th>Mon</th>
<th>Tue</th>
<th>Wed</th>
<th>Thu</th>
<th>Fri</th>
</tr>
<tr>
 <td>Science</td>
<td>Maths</td>
<td>Science</td>
<td>Maths</td>
<td>Arts</td>
</tr>
<tr>
<td>Science</td>
<td>Maths</td>
<td>Science</td>
<td>Maths</td>
<td>Arts</td>
</tr>
<tr>
<th colspan="5" align="center">LUNCH</th>
</tr>
<tr>
<td>Science</td>
<td>Maths</td>
<td>Science</td>
<td>Maths</td>
<td rowspan="2">Project</td>
</tr>
<tr>
<td>Science</td>
<td>Maths</td>
<td>Science</td>
<td>Maths</td>
</tr>
</table>
</body>
</html>
 Practical No:-05

Css code to design a circle using div with following specifications

<!DOCTYPE HTML>
<html>
<head>
<style type="text/css">
.circle{
width:200px;
height:200px;
border-radius:50%;
background:red;
border:2px double black;
}
.circle:hover{
background:yellow;
}
</style>
</head>
<body>
<div class="circle"></div>
</body>
</html>
 Practical No:-06
Write a CSS Code which change the Shape of Square into Circle when User
Move the mouse over square.

<!DOCTYPE HTML>
<html>
<head>
<style type="text/css">
.circle{
width:200px;
height:200px;
background:red;
border:2px double black;
}
.circle:hover{
background:yellow;
border-radius:50%;
}
</style>
</head>
<body>
<div class="circle"></div>
</body>
</html>

Output:-
 Practical No:-07
<!DOCTYPE html>
<html>
<head>
<title>Page Title</title>
</head>
<body>
<h1>This is a Heading</h1>
<h2>This is a Heading</h2>
<h3>This is a Heading</h3>
<h4>This is a Heading</h4>
<h5>This is a Heading</h5>
<h6>This is a Heading</h6>
<h7>This is a Heading</h7>
<p>This is a paragraph.</p>
</body>
</html>
Output :

This is a Heading

This is a Heading
This is a Heading

This is a Heading
This is a Heading

This is a Heading