Scribd
Upload
164 views

Symptoms of The Software Crisis

Symptoms of the software crisis include: - Organizations spending increasingly large portions of their budgets on software. - Software products becoming more expensive than hardware. - Software products being difficult to alter, debug, enhance and optimize, often failing to meet requirements, and frequently crashing or being delivered late. The main differences between a simple program and large software product are: size and functionality; users (a program's user is the programmer vs many external users); development team size (one programmer vs many); and importance of the user interface. The main aim of software engineering is to systematically apply engineering principles to the design, development, testing and maintenance of software.

Uploaded by

Ch.Faisal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
164 views

Symptoms of The Software Crisis

Symptoms of the software crisis include: - Organizations spending increasingly large portions of their budgets on software. - Software products becoming more expensive than hardware. - Software products being difficult to alter, debug, enhance and optimize, often failing to meet requirements, and frequently crashing or being delivered late. The main differences between a simple program and large software product are: size and functionality; users (a program's user is the programmer vs many external users); development team size (one programmer vs many); and importance of the user interface. The main aim of software engineering is to systematically apply engineering principles to the design, development, testing and maintenance of software.

Uploaded by

Ch.Faisal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Question 1:

State four symptoms of the present software crises.

Symptoms of the software crisis:


- Organizations are spending larger and larger portions of their budget on
software.
- Software products turning out to be more expensive than hardware.
- Software products are difficult to alter, debug, and enhance; use resources
non- optimally; often fail to meet the user requirements; are far from being
reliable; frequently crash; and are often delivered late.
- The expenses that organizations all around the world are incurring on
software
purchases compared to those on hardware purchases.

Question 2:

List at least four basic characteristcs tha differentiate a simple programe from a software
product.What is the ami of software engineering?

Ans: Programs are small in size and have limited functionality but software products are
extremely large. In case of a program, the programmer himself is the sole user but on the
other hand, in case of a software product, most users are not involved with the
development.In case of a program, a single developer is involved but in case of a software
product, a large number of developers are involved.

For a program, the user interface may not be very important, because the programmer is the
sole user. On the other hand, for a software product, user interface must be carefully
designed and implemented because developers of that product and users of that product are
totally different.

The main aim of software engineering is to apply engineering to the design, development,
implementation, testing and maintenance of software in a systematic method.

Question# 3: Trace the problem one would face, if he tries to develop a large software
product without using software engineering principles.
Answer: Without using software engineering principles it would be difficult to develop
large applications. The problem with developing large software is that the complexity
and difficulty levels increase exponentially with the increase in software size.

Complexity

For example a program of size 1,000 lines of code has some complexity. But a program with
10,000 LOC is not just 10 times more difficult to develop, but may as well turn out to be
100 times more difficult unless software engineering principles are used.

Question# 4: Differentiate between different SDLC Models.


Properties of
Water-Fall Model Incremental Model Spiral Model Rad Model
Model
Planning in
Yes Yes Yes No
early stage
Returning to an
No Yes Yes Yes
earlier phase
Handle Large-
Not Appropriate Not Appropriate Appropriate Not Appropriate
Project
Detailed
Necessary Yes but not much Yes Limited
Documentation
Cost Low Low Expensive Low
Requirement Time boxed
Beginning Beginning Beginning
Specifications release
Flexibility to
Difficult Easy Easy Easy
change
User Only at the
Only at beginning Intermediate High
Involvement beginning
Promotes
Maintenance Least Typical Easily Maintained
Maintainability
Duration Long Very long Long Short
Risk High Low Medium to high risk Low
Properties of
Water-Fall Model Incremental Model Spiral Model Rad Model
Model
Involvement
Framework
Linear Linear + Iterative Linear + Iterative Linear
Type
After completion of At the end of the After completion
Testing After every iteration
coding phase engineering phase of coding
Overlapping Yes (As parallel
No No Yes
Phases development is there)
Easily
Maintenance Least Maintainable Maintainable Yes
Maintainable
Re-usability Least possible To some extent To some extent Yes
Time-Frame Very Long Long Long Short
Working
At the end of the At the end of every At the end of every At the end of the
software
life-cycle iteration iteration life cycle
availability
Rapid
Objective High Assurance Rapid Development High Assurance
development
Team size Large Team Not Large Team Large Team Small Team
Customer
control over Very Low Yes Yes Yes
administrator

Properties of
Agile Model V Shape Model Prototype Model
Model
Requirement
Frequently Change Beginning Frequently Change
Specifications
Understanding
Well understand Early Understood Not Well understood
Requirements
Cost Very High Expensive High
Guarantee Of
Very High High Good
success
Resources Control No Yes No
Cost Control Yes Yes No
Simplicity Complex Intermediate Simple
Risk involvement Reduce Low No

Expertise Very High Medium Low


Properties of
Agile Model V Shape Model Prototype Model
Model
Required
Change
Difficult Difficult Medium
incorporated
Risk analysis Yes Yes Easy
Time-Frame High At the beginning No risk Ananlysis
Working software
Yes At the end of every iteration At the end of every iteration
availability
Objective High Assurance Rapid Development High Assurance
Team size Large Team Not Large Team Large Team
Customer control
Very Low Yes Yes
over administrator

You might also like