Any model that shows what the system is required to do without committing to any one technology.
A system requirement that describes an activity or process that the system must perform.
Characteristics of the system other than activities it must perform or support, such as technology, performance, usability, reliability and security. - doesn't mean that it is not working, it means that it is not something the system does.
A system requirement that describes an operational characteristic related to an organization's environment, hardware, and software.
A system requirement that describes an operational characteristic related to workload measures, such as throughput and response time.
A system requirement that describes an operational characteristic related to users, such as the user interface, work procedures, online help, and documentation.
A system requirement that describes the dependability of a system, such as how it handles service outages, incorrect processing, and error detection and recovery.
A system requirement that describes user access to certain functions and the conditions under which access is granted.
A type of workflow diagram that describes the user activities and their sequential flow.
A symbol in an activity diagram to control the splitting or uniting of sequential paths.
Questions that require discussion and do not necessarily have a simple, short answer.
Joint Application Design (JAD)
A technique to define requirements or design a system in a single session by having all necessary people participate.
Group Support System (GSS)
A computer system that enables multiple people to participate with comments at the same time, each from their own computer.