(10 points) Read Computer Assignment System (CAS) on page 116 and do Exercise 7 of Chapter 4.

4.7 Make a Stakeholders-goals list for the CAS product.

Stakeholder Goals
Category
System Admins - System is accessible over the internet to authorized persons.
- System must be able to answer queries about Computers, Users, and
Assignments
Software Developers - Have a system that does not require more than 1 person week per
year to maintain.
- 3 people must be able to develop the system in three months or less.
Computer Users - System must not take more than 1 minute on average per
transaction.
Accountants - System must provide data for quarterly reports, sufficient for
accountants to compute equipment depreciation in preparing tax
returns.
Managers - System must be able to answer queries about Computers, Users, and
Assignments

(10 points) 5.13 Explain the difference between correctness and verifiability.

- Verifiability refers to the ability to follow a specified procedure to determine whether a

statement or action is correct. If it can be tested by following a specified procedure, then it is
verifiable. Correctness refers more to the ability of a requirement or action to return the desired
or intended response. For instance, if testing the correctness of an addition function add(x,y),
then the function should return x + y, in order to be correct. If the function were to refer
something else, then this would not be correct.

(10 points) 5.14 Make a list of an inspection Moderator’s responsibilities.

Inspection Moderator’s Responsibilities:

1. Schedules meetings.
2. Ensures that everyone has proper materials for meetings.
3. Facilitating meetings.
4. Reporting inspection results.
5. Monitoring follow-up activities.

(10 points) 6.1 Consider a software system that sells products over the Web. Classify the following
activities as probably too big (B), too small (S), or the right size (R) to be use cases in this system:

(a) Enter Credit Card Number

o Too Small (S)
(b) Set Printing Parameters
 o Too Small (S)
(c) Buy an Item
o Right size (R)
(d) Manage Web Site
o Too Big (B)
(e) Select Mailing Address
o Too Small (S)
(f) Modify Shopping Cart
o Right Size (R)
(g) Search for an Item
o Too Small (S)

(10 points) 6.15 Must every use case have preconditions? Why or why not?

- No, not every use case must have preconditions. For example, if the use case is sufficiently
simple, and in a well known problem area, then the preconditions may not need be written out.
However, even for basic use cases, it is beneficial to the system designers as well as the system
stakeholders to see the assumed preconditions for a use case. Even if the preconditions are
“user has a login id, and is logged into system”, this is beneficial to have clearly shown and helps
add readability to the Use Case.

(10 points) 6.16 Must every use case have postconditions? Why or why not?

- Yes, every use case must have postconditions. Use cases deal with completing meaningful tasks
for a given actor with the system, and as such, at the completion of a meaningful task,
something should have been accomplished. The postconditions of a Use Case serve as the area
to mark the accomplishments or changes guaranteed to have occurred by the completion of the
Use Case.