Professional Documents
Culture Documents
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
formalize
must do ª every statement can be read in redundant
redundant inconsistent
inconsistent
ª ...and all the things it must not do! exactly one way reduce
ª Responses to all classes of input ª define confusing terms in a glossary
ª Structural completeness, and no resolve
TBDs!!
➜ Verifiable
ª a process exists to test satisfaction add
➜ Consistent of each requirement
explanations
ª “every requirement is specified not
not understandable
understandable
ª doesn’t contradict itself (I.e. is
satisfiable) behaviorally”
ª Uses all terms consistently
➜ Understandable (Clear)
ª Note: timing and logic are especially
ª by non-computer specialists
prone to inconsistency incomplete
incomplete
Modifiable
➜
…etc!
ª It must be kept up to date!
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
ª E.g. a formal specification language (e.g. Z, VDM, SCR, …) ª Forwards: each requirement traces to parts of the design that satisfy that
requirement
➜ Exploit redundancy ª Note: traceability links are two-way
¾ hence other documents must trace into the SRS
ª Restate a requirement to help the reader confirm her understanding
¾ Every requirement must have a unique label.
ª ...but clearly indicate the redundancy
ª May want to use a more formal notation for the re-statement ➜ Useful Annotations
ª E.g. relative necessity and relative stability
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
Consists of:
System or Segment
➜ CSCI= Com puterSoftw are (SSS)
ª a guidebook, Configuration Item
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
ª links between requirements at different levels ª unique identifiers ª database tools, with queries and
¾ each requirement gets a unique id; report generation
Traceability process
database contains cross references ¾RTM (Marconi)
➜ ª syntactic similarity coefficients ¾SLATE (TD Technologies)
ª Assign each sentence or paragraph a unique id number ¾ searches for occurrence of patterns of ¾DOORS (Zycad Corp)
words ª hypertext-based tools
ª Manually identify linkages
¾Document Director
ª Use manual tables to record linkages in a document ➜ Limitations ¾Netscape Navigator
ª Use a traceability tool (database) for project wide traceability ª All require a great deal of manual ª general development tools that
effort to define the links provide traceability
ª Tool then offers ability to
ª All rely on purely syntactic ¾RDD-100 (Ascent Logic) - documents
¾ follow links information, with no semantics or system conceptual models
¾ find missing links context ¾Foresight - maintains data dictionary
and document management
¾ measure overall traceability
University of Toronto Department of Computer Science University of Toronto Department of Computer Science
Contribution Structures
➜ ‘author’ attribute too weak
ª does not adequately capture ownership of information
ª refers to person that wrote the document rather than the person who
originated the content
ª fail to capture situations where many people participate
ª fail to capture changing patterns of participation
➜ Contribution structures
ª link requirements artifacts (contributions) to agents (contributors) via
contribution relations
➜ Roles
ª Principal
¾ who motivated the artefact (responsible for consequences)
ª Author
¾ who chose the structure and content (responsible for semantics)
ª Documentor
¾ who recorded/transcribed the content (responsible for appearance)
© 2001, Steve Easterbrook 25