Scribd
Upload
7 views2 pages

Software Homework1

Uploaded by

splendiferousbee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
7 views2 pages

Software Homework1

Uploaded by

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

Problem 2.

1
a.Not verifiable: Descriptions like "user-friendly" and "easy to use" are
pretty vague because they mean different things to different people.
What’s simple for one person might be a headache for someone else.
Without some concrete way to measure it, there’s no real way to test
it.Why it’s not testable: To make it testable, we’d need some clear
standards, like how long it takes users to complete a task, how many
mistakes they make, or getting feedback on user satisfaction from a
group of testers.
b.Verifiable: This one is specific and easy to measure because you can
count the number of clicks.Acceptance Test:Test Setup: Open the
system and go through different screens (like settings, reports, user
management, etc.).Test Execution: Keep track of how many clicks it
takes to reach each screen.Pass Criteria: Make sure none of the
screens take more than 10 clicks to get to.Expected Outcome: If all
screens take fewer than 10 clicks, the requirement is good.
c.Not verifiable: "Minimum training" is tricky because it’s different for
everyone. Without more details, there’s no way to create a test for it.
d.Verifiable: This one is clear and measurable.Acceptance Test:Test
Setup: Connect the system to broadband internet (with a speed of at
least 25 Mbps).Test Steps: Open the web app and click on links to
different pages. Use a tool to track how long it takes for the new page
to start loading after you click. Do this for several links.Expected
Result: The time between clicking the link and the page starting to load
should be less than 1 second.Pass Criteria: If all the links show a
response time of under 1 second, it passes the test.
e.Not verifiable: Saying something is "easy to recover" or that there's
"minimum loss of important data" is too broad. What counts as
"minimum loss" isn't clear, so it can’t be tested.

Problem 2.3REQ1: The system needs to regularly check the patient’s


vital signs, like heart rate and blood pressure, at least every minute. It
will have preset safe ranges and alert the hospital if something’s off.
REQ2: The system should know when the patient is exercising and
adjust those safe ranges based on what their doctor says.REQ3: The
system must make sure its sensors are working and notify the hospital
if there’s a problem.REQ4: The system should keep an eye on its
battery level and warn the patient when it’s running low.

Problem 2.14
Actors and Goals:Patient: Gets their vitals checked regularly.Goal:
Keep their vitals within safe levels.Hospital: Receives alerts for
emergencies or system problems.Goal: Act fast if the patient’s vitals
go out of range or replace the system if something’s wrong.
Use Cases:
• Monitor Vital Signs: The system keeps track of the patient’s heart
rate and blood pressure on a regular basis.
• Detect Abnormal Vital Signs: If something’s off with the vitals, the
system flags it as an issue.
• Adjust Safe Ranges for Exercise: When the system notices the
patient is working out, it adjusts the safe ranges for the increased
activity.
• Alert Hospital: If abnormal vitals are detected, the system sends
an alert to the hospital.
• Check Sensor Status: The system runs regular checks to make sure
the sensors are working. If not, it sends a notification to the hospital.
• Alert on Low Battery: It warns the patient when the battery is low.

You might also like