Scribd
Upload
28 views

Waterfall SDLC Mode: Jinnah University For Women Department of Computer Science & Software Engineering Assignment 1

The document is an assignment for a computer science course. It includes questions about software development lifecycles, requirements for a patient monitoring system project, definitions of software errors/faults/failures, and causes of software errors. Specifically: 1) It asks students to describe the waterfall and V-shaped SDLC models in their own words and discuss their advantages and disadvantages. 2) It provides a scenario for developing a patient monitoring system and asks students to identify functional and non-functional requirements and select an SDLC methodology. 3) It defines software errors, faults, and failures and asks students to explain the differences and provide an example of a new software failure appearing after years of use.

Uploaded by

naimish khan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
28 views

Waterfall SDLC Mode: Jinnah University For Women Department of Computer Science & Software Engineering Assignment 1

The document is an assignment for a computer science course. It includes questions about software development lifecycles, requirements for a patient monitoring system project, definitions of software errors/faults/failures, and causes of software errors. Specifically: 1) It asks students to describe the waterfall and V-shaped SDLC models in their own words and discuss their advantages and disadvantages. 2) It provides a scenario for developing a patient monitoring system and asks students to identify functional and non-functional requirements and select an SDLC methodology. 3) It defines software errors, faults, and failures and asks students to explain the differences and provide an example of a new software failure appearing after years of use.

Uploaded by

naimish khan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

JINNAH UNIVERSITY FOR WOMEN

DEPARTMENT OF COMPUTER SCIENCE & SOFTWARE ENGINEERING


ASSIGNMENT 1

1. Write any two software development life cycle (SDLC) model in your own
words.
Waterfall SDLC Mode
A cascade is an SDLC model,in which the development process looks
like a flow,going through phases of phased
analysis,projecting,recovery,testing,implementation and support.
 Its simple to use and understand.
 High risk.
 Not the best choice for complex projects.
V-shaped SDLC Model
V-shaped SDLC model is an extension of classic waterfall model.
This is also called “Verification and Validation” model.
 Good for small projects.
 Bad choice for small projects.
 Big risks.
2. Scenario:
The real-time software development unit of a hospital’s information systems
department has been assigned to develop an advanced patient monitoring system.
The new monitoring unit is to combine of patient’s room unit with a control unit.
The patient’s room unit is meant to interface with several types of medical
equipment, supplied by different manufacturers, which measure various indicators
of the patient’s condition. A sophisticated control unit will be placed at the nurses’
station, with data to be communicated to cellular units carried by doctors.
The project leader estimates that 14 months will be required to complete the
system; a team of five will be needed, with an investment of a total of 40 man-
months. She estimates that only 15% of the components can be obtained from the
reusable component library. The SDLC methodology was chosen to integrate
application of two prototypes of the patient’s room unit and two prototypes of the
control
JINNAH UNIVERSITY FOR WOMEN
DEPARTMENT OF COMPUTER SCIENCE & SOFTWARE ENGINEERING
ASSIGNMENT 1

unit for the purpose of improving communication with the users and enhancing
feedback of comments at the analysis and design phases.
a) Write down the functional & non-functional requirement for the above
scenario.
b) Select SDLC methodology.

3. (1) Define software error, software fault and software failure. Explain the
differences between these undesirable software statuses.

 Failure: External behavior is incorrect


 Fault: Discrepancy in code that causes a failure.
 Error: Human mistake that caused fault

(2) Suggest a situation where a new type of software failure (“bug”) appears in a
software package that has been serving 300 clients for the first time six years since
the software package was first sold to the public.
Let’s refer to a meteorological application based on remote measuring stations; in
this case the remote unit is required to initiate a protective closing operation that
prevents damage being caused to cold-sensitive measuring equipment each time
the temperature drops below minus 20ºC. The fault only turned into a failure once
a Russian version of the system had been developed and installed in various
northern sites of Russia, causing severe damage to the measuring stations’
equipment.
4. A programmer claims that because only a small proportion of software errors
turn into software failures, it is unnecessary to make substantial investments in the
prevention and elimination of software errors.
(a) Do you agree with this view?
Considering the damage caused by software errors, one must invest as much effort
as possible in eliminating software errors to reduce these damages to a minimum.
(b) Discuss the outcome of accepting these views.
Some possible outcomes:
JINNAH UNIVERSITY FOR WOMEN
DEPARTMENT OF COMPUTER SCIENCE & SOFTWARE ENGINEERING
ASSIGNMENT 1

 Lack of control over the extent of possible failures especially of severe


failures.
 A software failure may threaten a patient’s life.
 Software failures are not limited to user’s waste of time until the failure is
repaired, but cause damage to other systems.
5. List and briefly describe the various causes of software errors.
 Faulty requirements definition
 Client-developer communication failures
 Deliberate deviations from software requirements
 Logical design errors
 Coding errors
 Non-compliance documentation & coding instructions
 Shortcomings of the testing process
 User interface and procedure errors
 Documentation error

You might also like