OOAD Assaignment (BCSM-F18-068)
OOAD Assaignment (BCSM-F18-068)
OOAD Assaignment (BCSM-F18-068)
Q1:
Purpose of this Assignment:
Problem:You are to determine the user requirements for a web phone-mail product.
The primary purpose of this product is to give phone-mail users (e.g., faculty and
staff) the ability to access the functionality of the phone-mail system from a web page.
In general, the product should enable users of the phone-mail system to do their usual
phone-mail activities via a web page.
You will need to determine what are those activities, in the form of product
requirements.
Customer: You will need to assume the role of a hypothetical customer to identify the important user-
level requirements. You will also need to assume the roles of engineer and user in order to develop the
full requirement specification.
1. Determine requirements for the web phone-mail interface. This should include any requirements
that you think are necessary or very desirable in order to meet the customer needs.The initial
requirements should include 10 functional requirements and 10 nonfunctional requirements.
2. Evaluate these requirements. Do your requirements satisfy the eight criteria: Understandable,
Verifiable, and Independent of implementation, Consistent, Complete, Unambiguous,
Realistic, and Necessary? Explain your answers. Weed out any requirements that you do not
think are good user requirements.
3. Prioritize the requirements as to whether they are (1) absolutely necessary, (2) desirable, or (3)
optional.
Solution:
Requirements.
Because the web phone mail system is to provide the basic functionality of the existing system, it should
probably include most of the following:
2. Requirement evaluation.
All the above requirements satisfy the 8 criteria: Understandable, Verifiable, and Independent of
implementation, Consistent, Complete, Unambiguous, Realistic, and Necessary.
3. Prioritization.
The first six functional requirements are high priority. All of the above non-functional requirements are of
high priority; none of them are optional.
4. Risks:
There is a significant risk that the programmers will not be able to produce the product in time, especially
if they are not experienced. Other likely risks include the likelihood that the customer will change the
requirements, or that some of the staff will leave, or that the funding will be cut.
5. System requirements:
Review mailbox contents. When user requests "view mailbox" the mailbox contents will be transparently
encrypted and transmitted to client browser.
A locking mechanism will guarantee that only one user session can update the
mailbox at one time.
All user accessible fields of the phone-mail database will be displayed and selectable
in an html form
Users will select action to perform by mouse click.
After action is selected, user input will be validated for correctness before converting
to a proposed database update.
User display will be updated displaying proposed changes before allowing more user
input actions.
Database updates will be finalized when user logs out.