1)Software Process:-A software process is a set of activities and associated resultswhich produce a

software product.These activifies are mostly carried out by software engineers.

Software Process Activities:-The four fundamental process activities are

(1. Software Specification 2. Software Development 3. Software validation 4. Software Evolution)

-> Software Specification:-The functionality of the software and constraints on its operation must
be defined.

-> Software Development:-Software fo meet the specificationmust be produced.

-> Software Validation:-The software must be validated to ensure that it does what the customer
wants.

-> Software Evolution:-The software must evolve to meet changing customer needs.

2)Waterfall Model

-> Requirement analysis and definition:-The s/m's services, constraints and goals are established
by consolation with s/m users. They are then defined in detail and serve as s/m specification.

->System and Software design:-The s/m's design process partitions the requirement to either
hardware or s/w s/m. It establishes an overall s/m architecture. s/w design involves identifying
and describing the fundamental s/w abstraction and their relationships.

-> Implementation& Unit testing:-During this stage, the s/w design is realised as set of programs
or program unit.Unit testing involves verifying that each unit meets its specification

-> Integration and System testing:-The individual program units or programs are integrated and
tested as a complete system to ensure that the software requirement have been met. After
testing, the s/w s/m is delivered to the customer.

-> Operation and Maintenance:-(Normally this is the longest life cycle phase. The s/m is installed
and put into practical use. Maintenance involves;) correcting errors which were not discovered in
earlier stages of the life cycle.

Advantages:-Documentation is produced at each stage.This model is used when the s/w project is
part of larger engineering project. It fits with other engineering process models

Disadvantages:-Its inflexible partitioning of project into distinct stages. The following phase should
not start until the previous has finished Commitments are made at early stages in the process
which makes it difficult respond to changing customer requirement.

3)Software Prototyping:-Prototype A prototype is an initial version of a software system which is

used to demonstrate concepts, try out design options and generally, to find out more about
problem and its possible solution.
Prototyping Benefits:- Misunderstanding between software users and developers are exposed.
Missing services may be detected Confusing services may be identified. A working system is
available early in the process. The prototype may serve as a basic for deriving a system
specification. Prototyping Benefits Improved system usability A closer match of the system to the
user need.Improved design quality .Improved maintainability Reduced development efffort.

4) Requirement Validation:-Requirements validation is the critical engineering process of checking

the requirements for Validity, Consistency, Completeness, Realism, and Verifiability

-> Validity Checks: - A user may assume only certain types of the functions that software system
has to perform. 2. Consistency Checks: - Conflicting requirements lead to inconsistency in a
software system to be developed. 3. Completeness Checks:- The functions (capabilities expected
by the system) and constraints (conditions) imposed by the software system to be developed. 4.
Realisms Checks:- Requirements specifications must be acceptable for particular reasons of
implementation with existing technology and well within the budget allocated and schedules
being fixed for a software system to be developed. 5. Verifiability Checks: - Verifiability should
emphasise that the software system be developed must meet the requirements. For which
requirements of software system must be drafted in black and white.

5)Explain Boehm’s spiral model : The spiral model, originally proposed by Boehm‘s(BOE 88). The
spiral model is an evolutionary software process model that couples the iterative nature of
prototyping with the controlled and systematic aspects

-> Customer communication:- Task required to established communication between developer and
customer. 2)Planning: - Task required defining resources, timelines, and other projects related
information. Requirements are gathered during the planning phase. Requirements like ‗BRS‘ that
is 3) Risk analysis: - Task required to access both technical and management risks. In the risk
analysis phase, a process is undertaken to identify risk and alternate solutions. 4) Engineering: -
Tasks required to build on or more reorientation of the application. 5) Construction and realize: -
Task required constructing, tasking, installing and providing user support (e.g documentation and
training). 6) Customer evaluation:- Task required to obtain customer feedback based on the
evolution of software representation created during the engineering stage. - Product
maintenances- Product enhancement project - New product development projects - Concept
development projec

6)system:-A system can be defined as a collection of interrelated components working together

towards some common objective. A system may including software, mechanical, electrical and
electronic hardware and be operated by people.

-> Requirement Definition:- System Requirement Definition specifies what the system should do
(its functions) and its essential and desirable system properties.->System Design:- It is concerned
with how the system functionally is to be provided by the components of the system.-> Subsystem
Design:- Typically parallel projects developing the hardware, software, and communication. May
involve some COTS (Commercial off the shelf) systems procurement.-> System Integration:- The
process of putting hardware, software, and people together make a system. Should be tackled
inclemently so that sub-system are integrated one at a time. -> System Installation: -
Environmental assumptions may be incorrect. May be human resistance to the introduction of a
new system. Operator training has to be identified.-> System Evolution:- the large system has a
long lifetime they must evolve to meet changing requirements. Evolution is inherently costly;
changes must be evolved from technical and business perspective.

7)A software requirement can be of 3 types:

Functional requirements:-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

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.

Domain requirements: Domain requirements are the requirements which are characteristic of a
particular category or domain of projects. The basic functions that a system of a specific domain
must necessarily exhibit come under this category.

Requirement Engineering Process

The requirement engineering process is carried out such that a requirement Specification serves as
the basis for an agreement to be signed between the clients and the software developers. a)
Feasibility Study: - In this phase, an estimate is prepared to verify possibilities as user needs or
capabilities as expected by clients can be met using available hardware and software systems. -
Consequently, a feasibility study would reveal as for whether the proposed software could be
developed well within allocated budget and proven to be a cost—effective software. b)
Requirements Analysis: - Here in this phase, software development ,staff counsel end— users and
customers to find out the services the software system should provide. - They also gather
information such as conditions under which the software must perform, hardware constraints,
required performance of the system etc, through a series of discussions with potential users, and
observing the performance of existing software systems.

c) Requirements Definition: - Here in this phase, the requirements are defined in terms of a
document by translating the necessary information gathered during requirements analysis phase. -
Requirement document would reflect customer needs and must be understood both by the end—
user and customer of the software system 'being developed.

) Requirements Specification: - It's an iterative process along with requirements definition and
analysis phase/stages. - A final description of the user and system requirements are charted out,.