LAW 393 Lecture Notes - Lecture 1: Requirements Management, Ishikawa Diagram, The Who
Requirements Discovery
the process and techniques used by system analysts to identify or extract system problems and solution
requirements from the user community.
System Requirements
something that the information system must do or a property that it must have. Also called a business
requirement.
Functional Requirement
something the information system must do
Nonfunctional requirement
a property or quality the system must have
- Performance
- Security
- Costs
Criteria for System Requirements
1. Consistent
2. Complete
3. Feasible
4. Required
5. Accurate
6. Traceable
7. Verifiable
Consistent
not conflicting or ambiguous.
Complete
describe all possible system input and responses.
find more resources at oneclass.com
find more resources at oneclass.com
Feasible
can be satisfied based on the available resources and constraints
Required
truly needed and fulfill the purpose of the system.
Accurate
stated correctly.
Traceable
directly map to functions and features of system.
Verifiable
defined so can be demonstrated during testing.
Results of incorrect requirements
- cost more than projected
- delivered later than promised
- may not meet users' expectations
- cost of maintaining and enhancing systems may be excessively high
- system unreliable and prone to errors and downtime
- Reputation of IT staff is tarnished as failure will be perceived as a mistake by the team.
Process of requirements discovery
1. problem discovery and analysis
2. Requirements discovery
3. Documenting and analyzing requirements
4. Requirements management.
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Requirements discovery the process and techniques used by system analysts to identify or extract system problems and solution requirements from the user community. System requirements something that the information system must do or a property that it must have. Functional requirement something the information system must do. Nonfunctional requirement a property or quality the system must have. Criteria for system requirements: consistent, complete, feasible, required, accurate, traceable, verifiable. Complete describe all possible system input and responses. Feasible can be satisfied based on the available resources and constraints. Required truly needed and fulfill the purpose of the system. Traceable directly map to functions and features of system. Verifiable defined so can be demonstrated during testing. Cost of maintaining and enhancing systems may be excessively high. System unreliable and prone to errors and downtime. Reputation of it staff is tarnished as failure will be perceived as a mistake by the team.
