Due in class Tuesday, November 16, 1999

Instructions

Assignment 2 should have helped you imagine what the Cordless Phone redesign would encompass. In particular, you now should have a more concrete idea of the scope and potential functional and non-functional requirements of the system -- what needs to be specified and implemented. However, before you proceed with writing out the requirements, you need to plan your strategy for accomplishing the project, especially for verifying and validating the system you intend to build, and anticipate potential pitfalls which might cause delays or other problems.

Therefore in this assignment, you are asked to produce the following in a short (3 page) document:

1. Process Diagram

a. Diagram the software lifecycle process model you are following.

b. Annotate this process diagram with expected duration in time (e.g., days, months) of activities

2. Exposures

Identify and discuss potential pitfalls which might cause delays or other problems, especially, delivery of reduced functionality. This part builds on the extensions you were to discuss in Assignment 2, but will now also include extensions or problems with the lifecycle process.

Exposures might include requirements you anticipate changing as the lifecycle progresses. For instance, is there a requirement you think the client was not specific or certain about? Are there requirements that depend on some environmental concerns (interoperability with other software, requirements based on today's business procedures)? Are there requirements that are likely to fall behind schedule?

3. Validation and Verification

Describe (paragraphs) how you will validate and verify the requirements, design, and implementation; e.g., through specification reviews (e.g., requirements, design, interface/cognitive inspections and walkthroughs), unit testing, integration testing, regressions testing, special scenarios, data sets, etc.