Professional Documents
Culture Documents
ENGINEERING BASICS
Source code
Executable
User manual
Requirement analysis and design documents
Installation Manual
.co
Software crisis: A number of large size projects failed called software runaway because of following
reasons:
an
A software life cycle model is a type of process that represents the order in which the activities
will take place for development of software.
Requirement analysis
System analysis
Program implementation
Testing
Installation and maintenance
gi
st
en
The need for a software life cycle model: For clear understanding systematic and disciplined
development of software.
Types of software application
Stand-alone applications
Interactive transaction-based applications
Embedded control systems
Batch processing systems
Build
Fix
an
.co
gi
st
en
Design phase: Transform the requirements specified in the SRS document into a structure
that is suitable for implementation in some programming language. Two approaches are
available:
Object-oriented design approach: objects and different relationships that exist among
these objects are identified.
acceptance testing: It is the system testing performed by the customer himself after
the product delivery to determine whether to accept or reject the delivered product.
Maintenance Phase:-
corrective maintenance: Correcting errors that were not discovered during the product
development phase
3. Spiral model
The diagrammatic representation of this model appears like a spiral with many
loops.
The exact number of loops in the spiral is not fixed.
Each loop of the spiral represents a phase of the software process.
en
gi
st
an
.co
Develop and validate the next level of the product after resolving the identified risks.
Review the results achieved so far with the customer and plan the next iteration around the
spiral.
Progressively more complete version of the software gets built with each iteration around
the spiral.
.co
an
gi
st
en
Risk identification
Risk analysis and quantification
Risk planning
Risk monitoring
Schedule
(a)Task Network Representation
(b) Gantt Chart Representation
(c) PERT Chart Representation
Project Resources
(a) People
(b) Hardware and Software
(c) Special Resources
Staff Organization
(a) Team Structure
(b) Management Reporting
.co
an
gi
st
Risk Management Plan
(a) Risk Analysis
(b) Risk Identification
(c) Risk Estimation
(d) Risk Abatement Procedures
en