Term
|
Definition
| a set of computing hardware network hardware and topology, and system software employed by an organization |
|
|
Term
|
Definition
| organization and construction of software resources to implement an organization’s information system |
|
|
Term
|
Definition
| the activities a system must perform or support and the constraints that the system must meet |
|
|
Term
|
Definition
| the activated that the system must perform |
|
|
Term
| Non functional requirements |
|
Definition
| system characteristics other than the activities it must perform or support |
|
|
Term
|
Definition
| a requirements classification framework (acronym stands for functionality, usability, reliability, performance, and security |
|
|
Term
|
Definition
| operational characteristics related to users such as the user interface, related work procedures, online help and documentation |
|
|
Term
|
Definition
| requirements that describe system dependability |
|
|
Term
|
Definition
| operational characteristics related to measures of workload, such as throughput and response time |
|
|
Term
|
Definition
| requirements that describe how access to the application will be controlled and how data will be protected during storage and transmission |
|
|
Term
|
Definition
| an extension of FURPS that includes design constraints as well as implementation, interfaces, physical, and supportability requirements |
|
|
Term
|
Definition
| restrictions to which the hardware and software must adhere |
|
|
Term
| Implementation requirements |
|
Definition
| constraints such as required programming languages and tools, documentation method and level of detail and a specific communication protocol for distributed components |
|
|
Term
|
Definition
| required interactions among systems |
|
|
Term
|
Definition
| characteristics of hardware such as size, weight, power consumption, and operating conditions |
|
|
Term
| Supportability requirements |
|
Definition
| how a system is installed configured monitored and updated |
|
|
Term
|
Definition
| representation of some aspect of a system |
|
|
Term
|
Definition
| text based system models such as memos reports, narratives and lists |
|
|
Term
|
Definition
| system models that use pictures and other graphical elements |
|
|
Term
| Unified modeling language (UML) |
|
Definition
| standard set of model constructs and notations defined by the object management group |
|
|
Term
|
Definition
| persons who have an interest in the successful implementation of the system |
|
|
Term
|
Definition
| - persons within the organization who interact with the system or have a significant interest in its operation or success |
|
|
Term
|
Definition
| - persons outside the organization’s control and influence who interact with the system or have a significant interest in its operation or success |
|
|
Term
|
Definition
| persons who regularly interact with a system in the course of their jobs or lives |
|
|
Term
|
Definition
| persons who don’t interact directly with the system but who either use information produced by the system or have a significant financial or other interest in its operation and success |
|
|
Term
|
Definition
| person or group that provides the funding for a system development project |
|
|
Term
|
Definition
| questions such as “how many forms a day do you process?” that are used to get elicit specific facts |
|
|
Term
|
Definition
| sequence of processing steps that completely handles one business transaction or customer request |
|
|
Term
|
Definition
| describes user (or system) activities, the person who does each activity, and the sequential flow of these activities |
|
|
Term
|
Definition
| – activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths |
|
|
Term
|
Definition
| activity diagram column containing all activities for a single agent or organizational unit |
|
|
