1. Requirements Presentation
Phil Dudas
Bryan Schnebly
Sponsor:
Harlan Mitchell

2. Introduction Background and Problem Statement Business Issues
Product Description
Requirements (functional and non)

3. Problem Statement
The way that things work now at Intel are that with each new chip manufacturing tool, a station controller has to be developed to control that tool according to the user’s guidelines. Software needs to be developed to help station controller developers gather requirements for each new station controller.

4. Business Issues Developer Productivity Tool User Productivity
Improved Information Flow
-         Developer Productivity
Station controller developers now spend a good deal of time doing requirements acquisition. This product will shorten that time dramatically
-         Tool User Productivity
Tool users will have a station controller that they had a direct impact on designing. The controller will be produced to the users specifications, which will have a number of beneficial effects Being able to see and touch a life like prototype will reduce changes to the look, feel, and functionality of the alpha version of the product. The prototype will also better allow users to define features and functionality
Improved Information Flow
One area where the process can be improved upon is the time it takes to get requirements from the users. Our tool will allow faster and better communication of requirements between users and developers

5. Product Description SCRAT CSCP SCST
Station Controller Requirements Acquisition Toolkit
CSCP
Customizable Station Controller Prototype
SCST
Station Controller Survey Tool

6. CSCP

7. CSCP
The CSCP will enable the user to customize a prototype station controller.
The fields (size and position) and menu items can be changed to let the user get the most efficient use of the tool.
User will be able to step through a “run” of a batch process.

8. SCST Allow a developer to write a list of questions.
Present these questions to the user, allowing them to enter answers.
The answers will be used to create a list of requirements for the developer.

9. CSCP Requirements (functional)
Change size of text fields.
Change position of text fields.
Change items in pull down menus.
Save current configuration (field and menu properties).
Run a demo of SC through all states in a production run.

10. SCST Requirements (functional)
Load list of questions
Produce form from question list
Collect answers from form
Generate an MS Word requirements document from answers

11. Non-Functional Requirements and Constraints
Easy to use (desired user is not a Computer Scientist)
Easy to get to users
Small footprint
The system must run on Windows 98, 2000, and NT version 4.0