61 Questions
What is the primary purpose of a software requirements specification (SRS)?
To guide the design, build, and verification of a solution
What type of requirements are often stored in a software requirements specification (SRS)?
Both functional and nonfunctional requirements
What document contains the business requirements of a product?
Vision and Scope document
What is the output of the requirements development process?
A documented agreement among stakeholders
In what form can user requirements be captured?
In the form of use cases
What is an advantage of formal specifications in software requirements?
They provide the greatest rigor and precision
What is a limitation of formal specifications in software requirements?
Few software developers and customers are familiar with them
What type of language can be used to represent software requirements?
Either natural or formal languages
What is a characteristic of well-structured natural language in software requirements?
It is carefully written
What is a common limitation of software developers and customers regarding formal specifications?
They are not familiar enough with them
What is the primary purpose of a Software Requirements Specification (SRS)?
To describe the system's functions, capabilities, and constraints
Which of the following is NOT a recommended component of an SRS?
Detailed coding and programming instructions
What is a characteristic of a well-structured SRS?
Completely and precisely describes the system's behaviors and qualities
Which of the following is a potential use of an SRS?
Basis for system testing and user documentation
Which of the following is NOT a synonym for an SRS?
System Design Document
Why do we create different models and the SRS?
To cater to the diverse needs of multiple audiences
Who may not go through the SRS?
User representatives
What do developers need in addition to use cases?
More than just the use cases
What is a challenge in creating a single deliverable for all audiences?
Meeting the needs of all stakeholders
What is a benefit of having multiple models and the SRS?
Catering to the needs of multiple audiences
Why are simple numbered or bulleted lists considered inadequate for software requirements?
They cannot provide unique and persistent identifiers for each requirement
What is the main purpose of having a unique and persistent identifier for each software requirement?
To refer to specific requirements in change requests and modification history
How does the use of unique identifiers help in requirements traceability?
By helping refer to specific requirements in the traceability matrix
What challenge arises when trying to reuse requirements in multiple projects without unique identifiers?
Loss of specificity in referring to requirements
Why is it important for requirements to have persistent identifiers?
To provide a distinct identification for each requirement throughout the project
What does the prefix in a sequence number indicate in requirements labeling methods?
The requirement type
What is a consequence of deleting a requirement in sequence numbering method?
The requirement is removed from the sequence
What type of tools commonly use sequence numbering method for requirements labeling?
Commercial requirements management tools
What is a benefit of using sequence numbering method for requirements labeling?
Unique identification of each requirement
What is a characteristic of sequence numbering method for requirements labeling?
Uses a combination of alphabets and numbers for labeling
What is a disadvantage of using sequence numbering for requirements labeling?
It does not provide any logical or hierarchical grouping of related requirements
Why are numeric labels considered inadequate for indicating the intent of a requirement?
They do not convey the purpose or meaning of the requirement
What is the main drawback of the sequence numbering method for requirements labeling?
It lacks a logical or hierarchical grouping of related requirements
Why is it important for requirements labels to provide logical or hierarchical grouping?
To ensure related requirements are easily understood in context
What information does a numeric label fail to convey about a requirement?
The intent or meaning of the requirement
What is a limitation of hierarchical numbering as a requirements labeling method?
Number labels can grow to many digits in medium-sized SRS
Which statement best describes a disadvantage of hierarchical numbering as a requirements labeling method?
Number labels do not indicate anything about the intent of a requirement
Why might numeric labels be inadequate for indicating the intent of a requirement?
Numeric labels do not convey any information about the content or purpose of the requirement
What aspect of hierarchical numbering as a requirements labeling method can be considered a potential drawback?
Number labels do not indicate anything about the intent of a requirement
Which statement is true about the limitations of hierarchical numbering as a requirements labeling method?
Number labels can grow to many digits in medium-sized SRS
What is a suggested method for labeling individual functional requirements within major sections?
Numbering the major sections hierarchically and using short text codes with sequence numbers
What can happen to labels when changes like insertion, deletion, or merging occur in a document processed using word processors?
A lot of the labels will change
How are individual functional requirements identified within major sections according to the text?
By using short text codes followed by sequence numbers
What is a drawback of not effectively labeling requirements according to the text?
Limits the ability to work effectively and sensibly
Why does the text suggest using hierarchical numbering for major sections of requirements?
To ensure a logical organization of requirements
Why is it important for hierarchical textual tags to be structured and meaningful?
To ensure that tags are unaffected by changes in other requirements
What purpose does the tag 'Print.ConfirmCopies' serve in the context provided?
Confirming any request to print more than 10 copies
Why do hierarchical textual tags add value to requirements labeling?
By staying unaffected by changes in other requirements
In what way do hierarchical textual tags ensure the integrity of requirement labels?
By being structured and meaningful
How do hierarchical textual tags specifically contribute to the print function?
By organizing and structuring the labels
What is a benefit of incorporating user interface designs in the SRS?
It makes the requirements tangible to both users and developers
What is a drawback of including screen images and user interface architectures in the SRS?
It makes the SRS much larger and can frighten people
Why is it important to include specific UI controls in the SRS if necessary?
To ensure that the functionality is implemented correctly
What can happen if the UI design drives the requirements?
Functional gaps are created
What is a risk of delaying the baselining of the SRS until the UI design is complete?
It slows down development and tries the patience of the people involved
Why is it important to include functional requirements in the SRS and not just screen layouts?
To ensure that the requirements are implemented correctly
What is the purpose of using visual emphasis in an SRS?
To highlight important information and facilitate understanding
What is the advantage of using cross-references instead of hard-coded page or section numbers?
It allows for easy updating of the document
What is the purpose of including a table of contents in an SRS?
To help readers find specific information
Why is it important to consider color blindness when using color highlighting in an SRS?
To make the document more accessible to people with color blindness
What is the purpose of defining hyperlinks in an SRS?
To allow readers to jump to related sections or files
Study Notes
Requirements Labeling Methods
- Hierarchical numbering is a simple and compact method, but numeric labels don't provide information about the intent of a requirement.
- Cons of hierarchical numbering: labels can grow to many digits, and word processors don't generate persistent labels.
- Mitigation: number major sections hierarchically and identify individual functional requirements with a short text code followed by a sequence number (e.g., Section 3.5 Editor Functions has ED-1, ED-2… etc.).
Hierarchical Textual Tags
- Tags are structured, meaningful, and unaffected by adding, deleting, or moving other requirements (e.g., Print.ConfirmCopies).
User Interfaces and the SRS
- Incorporating user interface designs in the SRS has both benefits (makes requirements tangible) and drawbacks (can make the SRS large and scare people).
- Don't expect developers to derive underlying functionality and data relationships from screen shots.
SRS Readability Tips
- Use an appropriate template to organize information.
- Label and style sections, subsections, and individual requirements consistently.
- Use visual emphasis (bold, underline, italics, color, and fonts) consistently.
- Create a table of contents to help readers find information.
- Number all figures and tables, give them captions, and refer to them by number.
Requirements Labeling Methods – Sequence Number
- Pros: easy to retain a unique identifier, doesn't imply any order.
- Cons: doesn't provide logical or hierarchical grouping of related requirements.
Requirements Specification
- The result of requirements development is a documented agreement among stakeholders about the product to be built.
- The vision & scope document contains business requirements, and user requirements can be captured in the form of use cases.
- Functional and nonfunctional requirements are often stored in a software requirements specification (SRS).
SRS
- The SRS states the functions, characteristics, and constraints of a software system.
- It should describe the system's behaviors under various conditions and desired system qualities.
- It is the basis for project planning, design, and coding, as well as system testing and user documentation.
SRS Audience
- A single requirements deliverable cannot meet the needs of all audiences.
- Different models are created to cater to different audiences (e.g., business objectives, high-level big picture, user's perspective, or detailed requirements).
Labeling Requirements
- Every requirement needs a unique and persistent identifier.
- This helps refer to specific requirements in change requests, modification history, or requirements traceability matrix.
Learn about the importance of requirements specification in software development. Understand how stakeholders reach an agreement on the product to be built through documents like vision & scope, user requirements, and software requirements specification (SRS).
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
