What is Software?
Software encompasses:
(1) instructions (computer programs) that when executed provide desired features,
function, and performance;
(2) data structures that enable the programs to effectively store and manipulate
information and
(3) documentation that describes the operation and use of the programs.
Software products
Generic products
◦ Stand-alone systems that are marketed and sold to any customer who wishes to buy them.
◦ Examples – PC software such as editing, graphics programs, project management tools; Computer-Aided-Design
(CAD) software; software for specific markets such as appointments systems for dentists.
Customized products
◦ Software that is commissioned by a specific customer to meet their own needs.
◦ Examples – air traffic control software, traffic monitoring systems.
Why Software is Important?
The economies of ALL developed nations are dependent on software.
More and more systems are software controlled ( transportation, medical, telecommunications, military,
industrial, entertainment,)
What / who / why is Process Models?
What: Go through a series of predictable steps--- a road map that helps you create a timely,
high-quality results.
Who: Software engineers and their managers, clients also. People adapt the process to their
needs and follow it.
Why: Provides stability, control, and organize an activity that can if left uncontrolled, become
quite disordered. However, modern software engineering approaches must be agile and
demand ONLY those activities, controls and work products that are appropriate.
What are the steps: The process you adopt depends on the software that you are building. One
process might be good for aircraft system, while an entirely different process would be used for
website creation.
Definition of Software Process
A framework for the activities, actions, and tasks that are required to build high-quality
software.
A GENERIC PROCESS MODEL
A process was defined as a collection of work activities, actions, and tasks that are
Performed when some work product is to be created.
Each of these activities, actions, and tasks reside within a framework or model that
Defines their relationship with the process and with one another.
Generic Process Model:
There are five generic process framework: 4. Construction: Consists of code generation
and testing part.
1. Communication: Software development
starts with the communication between 5. Deployment: consists of delivering the
customer and developer. product to the customer and take feedback
from them,.
2. Planning: it consists of complete estimation
,scheduling for the project development and
tracking.
3. Modelling: Modeling consists of complete
requirement analysis and the design of project
like algorithm, flowchart etc.
The Essence of Practice
George Polya outlines the essence of problem solving, suggests:
[Link] the problem (communication and analysis).
[Link] a solution (modeling and software design).
[Link] out the plan (code generation).
[Link] the result for accuracy (testing and quality assurance).
Process Flow types
Linear process flow executes each of the five
activities in sequence.
An iterative process flow repeats one or more
of the activities before proceeding to the next.
An evolutionary process flow executes the
activities in a circular manner. Each circuit
leads to a more complete version of the
software.
A parallel process flow executes one or more
activities in parallel with other activities (
modeling for one aspect of the software in
parallel with construction of another aspect of
the software.
The Waterfall Model
The Waterfall Model
It is the oldest paradigm for SE.
The waterfall model, sometimes called the classic life cycle,
Suggests a systematic, sequential approach to software development that
Begins with customer specification of requirements and progresses through
Planning, modelling, construction, and deployment in ongoing support of the completed
software
The V-Model
The V-Model
Also know as Verification and Validation Model.
Extension of Waterfall Model.
Testing is associated with every phase cycle.
Verification Phase (Requirement analysis ,system design, architecture design, model design)
Validation Phase (Unit Testing ,Integration ,system ,acceptance testing )
The V-model provides a way of visualizing how verification and validation actions are applied
The Incremental Model
The Incremental Model
❖Module by module working.
❖Customer Interaction maximum.
❖Large Projects.
❖Early release product demand.
❖Flexible to change.