0% found this document useful (0 votes)
234 views7 pages

Software

The document discusses software reliability and its relationship to hardware reliability. It provides definitions of software reliability as the ability of software to perform required functions under stated conditions for a specified time period. It notes that software relies on instructions to function while hardware is mechanical. Software reliability depends on the likelihood of hardware failures and time to repair hardware components, as physical flaws can impact software systems. Reliable software has zero failures, fulfills user needs, and avoids and recovers from errors over its usable lifetime.

Uploaded by

AIMAN SUBHAN
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
0% found this document useful (0 votes)
234 views7 pages

Software

The document discusses software reliability and its relationship to hardware reliability. It provides definitions of software reliability as the ability of software to perform required functions under stated conditions for a specified time period. It notes that software relies on instructions to function while hardware is mechanical. Software reliability depends on the likelihood of hardware failures and time to repair hardware components, as physical flaws can impact software systems. Reliable software has zero failures, fulfills user needs, and avoids and recovers from errors over its usable lifetime.

Uploaded by

AIMAN SUBHAN
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/ 7

Software Engineering

Date: 26/10/2022
AIMAN SUBHAN

ROLL NO 212011

CLASS BSGM3

SUBMITTED TO DR. ADNAN

ASSIGNMENT 02:

QUESTION 01:
The department of public works for a large city has decided to develop a Web-based
pothole tracking
2

and repair system (PHTRS). A description follows: Citizens can log onto a website and
report the location

and severity of potholes. As potholes are reported they are logged within a “public
works department

repair system” and are assigned an identifying number, stored by street address, size
(on a scale of 1 to

10), location (middle, curb, etc.), district (determined from street address), and repair
priority

(determined from the size of the pothole). Work order data are associated with each
pothole and include

pothole location and size, repair crew identifying number, number of people on crew,
equipment

assigned, hours applied to repair, hole status (work in progress, repaired, temporary
repair, not repaired),

amount of filler material used, and cost of repair (computed from hours applied, number
of people,

material and equipment used). Finally, a damage file is created to hold information
about reported

damage due to the pothole and includes citizen’s name, address, phone number, type of
damage, and

dollar amount of damage. PHTRS is an online system; all queries are to be made
interactively.

Draw a UML use case diagram for the PHTRS system. You’ll have to make a number of
assumptions about

the manner in which a user interacts with this system.

ANSWER:
3

The department of public works for a city has decided to develop a web-based Pot Hole
Tracking and Repair System (PHTRS). A UML use case diagram states the relationship
between the actors in the system with the use cases.

To construct a unified modeling language (UML) use case diagram first identify the
actors for the system. For PHTRS, actors can include:-

1. Citizen
2. PHTRS employees
3. Contractor
4. Repair Crew

Then identify the functionalities to be identified as use cases for the system. For
PHTRS, functionalities can include:-

1. Citizens report pothole information like its severity and location.


2. Record pothole information like identification number, size, location, address,
repair priority of PHTRS.
3. Issue work order with data like size, location, repair crew id number, crew size,
equipment assigned, hours worked, status, cost or repair etc.
4. Create a PHTRs damaged file with information like citizen name, phone number,
and address type of damage and cost of damage.

UML DIAGRAM:

Now , construct a UML use case diagram for the PHTRS using above information

Contractor

Repair crew

Contractor
4

Repair crew

PHTR Report
S Pothole
citizen information
Log
information
Of Pothole
PHTRS

Issue Work
PWD employee
order
citizen

Repair
Pothole get
material etc.

Create citizen
damaged
file
5

PHTR Report
S Pothole
citizen information
Log
information
Of Pothole
PHTRS

Issue Work
PWD employee order
citizen
Repair
Pothole get
material etc.

Create citizen
damaged
file

Date: 26/10/2022
6

QUESTION 02:
Q2. Explain software reliability and define how it is related to hardware reliability.

ANSWER:

RELIABILITY:

Reliability of software may be defined with the following points.

1. Accuracy of the software.


2. Presence of zero percent failure in software.
3. To fulfill the user's needs.
4. Capacity of error avoidance.
5. Capacity of recovery.
6. Maturity of software.

DEFINITION:

The ability of a software or component to perform its required functions under stated
condition for a specified period of time.

EXPLANATION:

Reliability of a software can be defined as a software which has no failure and working
in a special time period with a special environment. probability of failure may be defined
with the probability that the software will be fail on the next input selected.

OTHER DEFINITION:

The process of optimizing the reliability of software through a program that emphasizes
software error prevention, fault detection and removal and the use of measurements to
maximize reliability in light of project constraints such as resources, schedule and
performance.
7

SOFTWARE AND HARDWARE RELATED RELIABILITY:

A software that is reliable will not fail and will function properly in a particular time
frame and environment. Software relies on instructions to function, whereas hardware
is a component of mechanical. In the functional domain of software, both hardware and
software play a significant role. Because we employ hardware components to control
the programme, if we discover any flaws, it will affect how everything works. Software
reliability is kept up until a hardware issue that affects the data path is discovered. A
software's reliability is determined by the likelihood that a hardware component will fail
and by estimating how long it will take to maintain that component. There are always
physical flaws in software systems.

You might also like