Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Requeriments Chapter 1 - Coggle Diagram
Software Requeriments Chapter 1
The essential software requirement
What, why, and who
Levels and types of requeriments
Constraint
A restriction that is imposed on the choices available to the developer for the
design and construction of a product
External interface requirement
A description of a connection between a software system and a user, another
software system, or a hardware device
Business rule
A policy, guideline, standard, or regulation that defines or constrains some aspect of the business. Not a software requirement in itself, but the origin of several types of software requirements.
Feature
One or more logically related system capabilities that provide value to a user and are described by a set of functional requirements.
Business requirement
A high-level business objective of the organization that builds a product or of a customer who procures it.
Functional requirement
A description of a behavior that a system will exhibit under specific conditions.
Nonfunctional requirement
A description of a property or characteristic that a system must exhibit or a constraint that it must respect
Quality attribute
A kind of nonfunctional requirement that describes a service or performance
characteristic of a product.
System requirement
A top-level requirement for a product that contains multiple subsystems, which
could be all software or software and hardware.
User requirement
A goal or task that specific classes of users must be able to perform with a system, or a desired product attribute.
Levels of Software requirements
User requirements
Use cases (Kulak and Guiney 2004)
User stories (Cohn 2004)
Event-response Tables
Functional requirements
Development
Testing
Quality assurance
Project Management
Related to project functions
Business requirements
Funding sponsor of project
The acquiring customer
The manager of the actual users
Product visionary