ITM 305 Chapter 2: ITM 305 - System Analysis and Design Chapter 2 Notes (Week 3).docx

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 305
• Professor: Jim Tam

Document Summary

Define requirements: the analyst uses information gathered from users and documents to define requirements for the new system, system requirements include the functions the system must perform (functional requirements) Evaluate requirements with users the activities of evaluating requirements with users and documenting the requirements are fully integrated. Requirements and models that represent them are a key focus of analysis phase activities. Most of the analyst"s time is devoted to requirements: gathering information about them, formalizing them by using models and prototypes, refining and expanding them, prioritizing them, and generating and evaluating alternatives. System requirements: the activities a system must perform or support and the constraints that the system must meet. Functional requirements: the activities that the system must perform. Nonfunctional requirements: system characteristics other than the activities it must perform or support. Furps: is an acronym that stands for functionality, usability, reliability, performance, and security. The f in furps is equivalent to the functional requirements defined previously.