Fiat Slug

UC Santa Cruz Extension

Software Requirements Analysis & Design - Summer 1998


Frequently Asked Questions

Here are the questions, slightly edited, asked of me by student groups.


Melora wrote:

>Seeking to apply the insights conveyed during last weeks's class meeting,

>we'd like to request clarification of a number of areas pertaining to the

>class project assignment that you handed out on Tuesday July 14. 

>

>Here is the first set of questions:

>

>Regarding your role in the project and our mutual expectations...

>  1.  In the handout describing our assignment, you have indicated

>      that you are the "project liason".  We'd like to get a better

>      understanding of what that title and role means to you and the

>      customer. 

>      - As project liason, how do you define your role in this project

>        and how do you personally expect to benefit from it?

>      - In your role as project liason, what responsibilities can we

>        reasonably expect you to perform?  On whose behalf are you

>        performing each of these responsibilities (i.e., are you

>        employed as a member of our project team, are you employed

>        directly by a customer, are you acting independently, etc.? 

>      - In your role as project liason, what expectations do you have

>        of our project team?

You may assume that I will serve as a contact point for a prospective client, who, if convinced by your presentation, might fund a project to develop your proposed system.

You only need to define a successful product that satisfies the market and profitability standards you choose.  You are to make your case as a presentation to me, with supporting documentation, during the ninth class meeting.  You have complete liberty to answer all of the questions concerning your market niche,

profitability, who, if anyone, your primary competitors will be, as well as the details of your product as specified by the requirements templates.

I emphasize at all points that any statements (claims) that you make must be backed up by credible claims.  Your job in the presentation is to convince the

client to provide the funds necessary to develop the product.

>Regarding our means of interaction and communication...

>  1.  Our understanding of last week's in-class discussion with you

>      is that email is your preferred medium for communication with

>      our project team. (If this has been misunderstood, please

>      suggest an alternate means of carrying out future discussions.)

Your understanding is correct.

>  2.  Do you prefer to get questions from us one at a time or in batches?

>      (If batches are preferred, do you have any preferences as to how

>       large of a list you're prepared to deal with at any one time

>       or with respect to how often?)

No preference.

>  3.  What kind of turn around time are you willing to guarantee

>      with respect to getting back to us when we contact you, and

>      what expectation do you have with respect to how much time

>      is reasonable for you to wait for a response from us?

By next class meeting.

>  4.  Is there any requirement for us to appoint an "official"

>      point of contact with you within our project team? 

No.

>  5.  Does the customer have any requirements with respect to

>      tracking the communications that occur between us?  Do you?

No.

>Regarding the problem statement...

>  1.  What problem is this system intended to solve? 

You decide.

>Regarding the deliverables described in the handout...

>  1. Do you or the customer have a preferred or required format for

>     the requirements specification?  What are the schedule

>     requirements for this deliverable?

You may use the template provided, or choose one of your own.  You must deliver softcopy by the ninth meeting.

>  2. Do you or the customer have a preferred or required format for

>     the design specification?  What are the schedule

>     requirements for this deliverable?

Same as above.

>  3. Do you or the customer have a preferred or required format for

>     the presentation?  What are the schedule

>     requirements for this deliverable?

No preference.  A wide variety of media have been used in the past.  Extra credit for creativity.  Same schedule.

 

At 11:43 AM 7/22/98 -0700, John Lowery wrote:

>1. Is this desktop a type of software that will allow the user to

>modify an existing operating system's standard desktop?

Your decision.

>2. If the answer to the above question is "Yes", what are the

>specific operating systems that the software needs to run on?

Also your decision.

>3. What is the target market for this product?

See above.

>4. How much will we charge for the product?

What do you think it's worth?

>5. Where will this product be sold?  Retail stores?

Good question.

Rita wrote:

>Here is a list of questions our team has developed for our "Computer

>Desktop" product.

Here is a general answer, which may change the nature of your questioning.

=====

You may assume that I will serve as a contact point for a prospective client, who, if convinced by your presentation, might fund a project to develop your proposed system.

You only need to define a successful product that satisfies the market and profitability standards you choose.  You are to make your case as a presentation to me, with supporting documentation, during the ninth class meeting.  You have complete liberty to answer all of the questions concerning your market niche,

profitability, who, if anyone, your primary competitors will be, as well as the details of your product as specified by the requirements templates.

I emphasize at all points that any statements (claims) that you make must be backed up by credible claims.  Your job in the presentation is to convince the

client to provide the funds necessary to develop the product.

=====

>General:

>1. When we design this desktop system,  will we define a market in which

>this desktop is to be targeted?  Do we need to be specific about what

>segments of the market are not targeting?

>Or we can just briefly mention that these segments are ignored?

>

>2. Are we designing this desktop for a client?  ( In that case, the

>requirements are provided by our customer.  As a designing company, we might

>not have that much say about the system requirements.  Does that mean we

>only need to focus on the business requirement ? )

>Or are we representing a group of users who would like to have the lists of

>the features we provide? (In this case, we have a say about what needs to be

>on the requirements list.) 

>

>

>Client:

>3. Who is the Client and what is the business of the client?

>4. What  is the value of this  new product to the client?

>5. What is the criteria for accepting or rejecting this proposal?

>6. When do the client want this product?

>7. What are the risks of not meeting the product delivery date?

>8. Which is  preferred by the client - a desktop which

>    will match the market's most competitive desktop but

>    with some added features and at a much lower price or

>    a really fancy one but will cost much more?

>

>

>Users:

>9. Which users would the client  like to ignore for the "Computer Desktop"

>product?

>10. Which are the most favored users?

>

>

>Expectations:

>11. What is the client  and users most looking forward to in this "Computer

>Desktop"?

>12. Which part of the system will be most valuable to the client and users?

>13. What problems do the users expect that this product will solve?

>

>Preferences/ Constraints

>For each of the following attributes, please indicate whether they are

>preferences or constraints.

>Please also provide metrics if they are constraints:

>

>14. Physical Dimensions (Footprint, Size, Shape, Color )

>15. Network Readiness (Internet, Intranet)

>16. User Interface (Basic requirements vs Special requirements)

>17. Storage (Internal, External or Network)

>18. Reliability

>19. Power Saving Feature

>20. Security

>21. H/W ,S/W, Network Standards (Open vs Proprietary)

>22. Budget of the Client

>23. Delivery Date

>24. Maintainability

>25. Performance (Speed, Response time)

>26. Price (Basic vs what the user is willing to pay for extra preferences)

>27. Expandability (Ease like Plug and Play)

>28. What is the environment of the desktop?  stand-alone?

>    LAN?

>

>

>

>Limitations

>Please indicate any limitations that could affect the use of this product:

>

>29. Environmental conditions

>30. User limitations (e.g. Disabilities)

 

As you have probably noticed, I have not responded to your specific questions.  I am not trying to be difficult or toying with you.  I want you to have complete freedom to choose your target market, and to justify why you made that choice.


More questions? Send me email at brian@coyotevalley.com


Last updated: 14-May-1998

Lizard