Last Lecture-Lec 2

Types of Software's
Characteristics of Softwares
Software Development

Crises
Solution
Myths
Reality
Process
 Crises reasons
Changing Nature of Requirements
Poor Maintainability
Schedule Slippage
Poor Maintainability
Technical Incompetence of development
Adhoc software Development
Not Planned well
Poor understanding of requirements
No control on Review
 Crises-Failure rate of
software
increasedfailure
rateduetosideeffects
Failure
rate

change
actualcurve

idealizedcurve

Time
 Solution-Successful s/w
Development Complete
Usable
Used
Useful
Cost effective and maintained.
MYTH
 Myth

Software Mythsbeliefs about software

and the process used to build it can be
traced to the earliest day of computing.
Myths have a number of attributes that
have
Management myths
Customer myths (User)
Practitioners myths (Developer)
 Myths
Management Myths:
If we get behind schedule, we can add more
programmers and catch up
All information can be acquired from manual.
Users Myths:
Software is flexible
Project requirements continually change, but
change can be easily accommodated
Developers Myths:
Once we write the program and get it to work, our
job is done. Testing is too expensive. Only fully
developed products are tested. The only deliverable
work product for a successful project is the working
program
 Reality
Management:
Adding people to a late software project makes it later
Training time, increased communication lines
Software projects need to be controlled and managed
User:
Impact of change depends on where and when it occurs in the
software life cycle (requirements analysis, design, code, test)

Developer:
60% to 80% of all effort expended on software occurs after it
is delivered
Formal technical reviews of requirements analysis documents,
design documents, and source code (more effective than
actual testing)
Software, documentation, test drivers, test results
Software is about coding
Reality Programming is a small
part of Development
 Agile Software
Review and Validation at every stage
Iteration to iteration work
 Process Preview
Abstract Layers towards successful
software.
Activities to be carried out in a
particular
Feasibility
Planning
and order
Requirements

Design

Operation and
Implementation Maintenance
 Process

A layered Technology
 Next Lecture-Lect4
Software Life cycle and Models