Specification Flashcards
(21 cards)
What is the main focus of a software specification?
A specification focuses on WHAT should be built in a software system, detailing exactly what is to be implemented, but not necessarily HOW it should be built.
How are specifications different from requirements?
Requirements describe what stakeholders need or want from a system, while specifications detail what the software must do to meet those requirements, often in a more precise and testable way.
Give an example of a functional requirement and its related specification.
Requirement: “A module convenor needs to check if a student has prerequisite knowledge.”
Specification: “A module interface shall show a list of students who want to take the module; allow viewing of modules/grades; show additional student comments; let the convenor accept/reject students; and allow contacting students for clarification.”
What are the typical qualities of a good specification?
Good specifications are correct, necessary, feasible, unique, concise, complete, clear, consistent, traceable, and verifiable.
Why is traceability important in specifications?
Traceability ensures that every specification can be linked back to a user requirement, making it clear which needs are being addressed and helping manage changes and verification.
What does it mean for a specification to be testable?
A testable specification is one that can be objectively verified as met or unmet, often by being measurable (e.g., “must load within 10s” instead of “must load fast”).
Who are the typical readers or users of specifications?
Specifications are read by developers, testers, project managers, clients, and other stakeholders involved in the software development process.
What are some common formats for writing specifications?
Specifications can be written in natural language, structured/tabular formats, or graphical forms such as UML diagrams.
What are the advantages and disadvantages of natural language specifications?
Advantages: Expressive, intuitive, and universal.
Disadvantages: Can be ambiguous, vague, and open to interpretation.
What guidelines help improve natural language specifications?
Use a standard format linked to user requirements, distinguish between mandatory (“shall”) and desirable (“should”), emphasize important elements, avoid jargon, and ensure specifications are measurable.
When should structured or tabular specifications be used?
Structured or tabular specifications are useful when details such as logic, inputs/outputs, conditions, or options need to be explicitly listed, or when exactness is required.
What is the purpose of graphical specifications like UML diagrams?
Graphical specifications help visualize complex system behaviors and interactions, making it easier to understand and communicate how the system should work.
What is the difference between requirements diagrams and specifications diagrams?
Requirements diagrams illustrate what stakeholders need, while specifications diagrams show what the system will do to fulfill those needs.
What is involved in a specification review process?
A team systematically reviews each specification, checking for validity, consistency, completeness, realism, and verifiability, ensuring the specifications are correct, necessary, and important.
What makes a specification ‘bad’?
A bad specification is ambiguous, incomplete, inconsistent, not testable, not traceable to requirements, or not feasible to implement.
Why is it important for specifications to be concise and unambiguous?
Concise and unambiguous specifications reduce misunderstandings, make implementation and testing easier, and help ensure the system meets stakeholder needs.
What is the relationship between requirements, specifications, and testing?
Requirements define stakeholder needs, specifications translate those needs into precise system behaviors, and testing verifies that the implementation meets the specifications.
What are some best practices for managing specifications in a team project?
Use version control tools (like git) for coordination, ensure all outputs are in markdown, use meaningful tags, and maintain clear links between requirements, specifications, and documentation.
What is the role of priorities and risks in specifications?
Specifications often include information about the priority and risk of each requirement, helping teams focus on the most critical aspects and manage potential challenges.
Why should specifications avoid jargon unless clearly defined?
Avoiding undefined jargon ensures that all stakeholders have a shared understanding, reducing the risk of misinterpretation.
Guidelines for writing specifications
Use a standard format
Distinguish between mandatory (shall) and desirable (should)
Emphasise important elements with bold, italics etc
Avoid jargon, unless clearly specified in the key words section
Make sure the specification is measurable in some form
