4. What application domain questions need to be answered to understand the CAS problem domain?

6. What elicitation techniques would you use to gather needs and desires for the CAS, and which stakeholders would you use them on?

Introduction: A group of system administrators must keep track of which computers are assigned to computer users in the community they support. Currently this is done by hand, but this is tedious, error prone, and inconvenient. System administrators want to automate this task to ease their workload. Product Vision: The Computer Assignment System (CAS) will keep track of computers, computer users, and assignments of computers to users; answer queries, and produce reports about users, computers, and assignments. Project Scope: Developers in the same enterprise will implement CAS. CAS will be the simplest system meeting basic system administrator needs, developed by a small team in a short time. Target Market: Only the system administrators will use CAS. Stakeholders: System Administrators, Software Developers, Computer Users, Accountants, and Managers. Assumptions and Constraints: CAS will be accessible over the Internet to authorized users. Three people must develop CAS in three months or less. CAS must require no more than one person-week per year for maintenance. Business Requirements: CAS must maintain the location, components, operational status, purchase date, and assignment of every computer in the organization. CAS must maintain the name, location, and title of every computer user in the organization. CAS users must take no more than one minute per transaction, on average, to maintain this information. CAS must answer queries about computers, users, and assignments. CAS must provide data for quarterly reports sufficient for accountants to compute equipment depreciation in preparing tax returns