Bit Rot Requirements

compared with
Current by bram van der werf
on Mar 24, 2011 17:49.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
*1.  Introduction*
*2.  System-Wide Functional Requirements*
{color:#0000ff}\[Statement of system-wide functional requirements, not expressed as use cases. Examples include auditing, authentication, printing, reporting.\]{color}
*3.  System Qualities*
{color:#0000ff}\[Qualities represent the URPS in FURPS\+ classification of supporting requirements.\]{color}
*3.1 Usability*
{color:#0000ff}\[Describe requirements for qualities such as easy of use, easy of learning, usability standards and localization.\]{color}
*3.2 Reliability*
{color:#0000ff}\[Reliability includes the product and/or system's ability to keep running under stress and adverse conditions. Specify requirements for reliability acceptance levels, and how they will be measured and evaluated. Suggested topics are availability, frequency of severity of failures and recoverability.\]{color}
*3.3 Performance*
{color:#0000ff}\[The performance characteristics of the system should be outlined in this section. Examples are response time, throughput, capacity and startup or shutdown times.\]{color}
*3.4 Supportability*
{color:#0000ff}\[This section indicates any requirements that will enhance the supportability or maintainability of the system being built, including adaptability and upgrading, compatibility, configurability, scalability and requirements regarding system installation, level of support and maintenance.\]{color}

{color:#0000ff}{*}4.            System Interfaces{*}{color}
{color:#0000ff}\[Interface Requirements are part of the + in the FURPS\+ classification of supporting requirements. Define the interfaces that must be supported by the application. It should contain adequate specificity, protocols, ports and logical addresses, and so forth, so that the software can be developed and verified against the interface requirements.\]{color}
{color:#0000ff}{*}4.1   User Interfaces{*}{color}
{color:#0000ff}\[Describe the user interfaces that are to be implemented by the software. The intention of this section is to state requirements relating to the interface. Interface design may overlap the requirements gathering process.\]{color}
{color:#0000ff}4.1.1   {color}{color:#0000ff}{*}Look & Feel{*}{color}
{color:#0000ff}\[Provide a description of the spirit of the interface. Your client may have given you particular demands such as style, colors to be used, and degree of interaction and so on. This section captures the requirements for the interface rather than the design for the interface.\]{color}

{color:#0000ff}4.1.2   {color}{color:#0000ff}{*}Layout and Navigation Requirements{*}{color}
{color:#0000ff}\[Capture requirements on major screen areas and how they should be grouped together{color}