1 / 21

Tools for Requirements Management Software Engineering 2007

Tools for Requirements Management Software Engineering 2007 Bernd Schoeller <bernd.schoeller@inf.ethz.ch>. Tools for Management. Overview What is Requirements Management ? Tasks Tool support Presentation of a tools: DOORS (by Telelogic) Summary. What is Requirements Management ?.

annora
Télécharger la présentation

Tools for Requirements Management Software Engineering 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tools for Requirements Management Software Engineering 2007 Bernd Schoeller <bernd.schoeller@inf.ethz.ch>

  2. Tools for Management Overview What is Requirements Management ? Tasks Tool support Presentation of a tools: DOORS (by Telelogic) Summary

  3. What is Requirements Management ?

  4. What is Requirements Management ? (cont.)

  5. Tasks of Requirements Management tool Extract Capture Store Collaborate Version Identify Categorize Trace Merge Present

  6. Extract Sources for requirements Word Documents PDF Documents Diagrams Photos E-Mails Video, Audio, ... Requirements are extracted from these documents Requirements are linked to the source Sometimes it is difficult to “link into the source”

  7. Videos as requirements ?

  8. Capture Are requirements always plain text? “A picture can say more than a thousand words.” Technical applications are often specified with mathematical equations. Even more difficult: video, audio, photos, etc.

  9. Extract vs. Capture What is the difference between “Extract” and “Capture” ?!

  10. Store More or less a database issue. For large and long-term projects, the database with requirements can become very large. Fast retrieval of data ? Query mechanisms or languages ? Dynamic Schema Custom fields

  11. Collaborate • If there are many people working on the same requirement data: • How can everybody access the data ? • Tracking “Who changes what” • Collision detection

  12. Version Software Development is a process that happens over time. Requirements are a moving target. Documents are constantly changed. Certain versions of the documents form the basis for contractual agreements.

  13. Identify Every requirement needs an identification This identification has to be unique and stable over time and space The identification should be human-readable: Facilitates communication between developers and stakeholders

  14. Tasks of Requirements Management tool Extract Capture Store Collaborate Version Identify Categorize Trace Merge Present Tasks of Software Configuration Management

  15. Categorize Categorization: intuitive approach to organize data Standard techniques: hierarchical structure tags (labels) numbering Development of a good categorization structure is critical. Categorizations can be reused between projects. Categorization schema depend on the software development methodology. the problem domain.

  16. Trace Requirements do notstand alone. During the requirements process we identify: Requirements that complement other requirements Requirements that contradict other requirements Requirements that are derived from other requirements A tools has to Record connections Present connections Allow a “What if?” analysis of a possible change.

  17. Example of a trace Customer: Access to the server should be available at any time. Manager: The system has to have a 99.999% availability. Hardware Maintainer: The software must run in a distributed environment with a seamless failover functionality and no single point of fail.

  18. Merge • Many sources for requirements • At least one for every stakeholder • A single document should be produced. • A tool can support this process: • Showing differences between documents. • Identifying similarities between documents.

  19. Present The final requirements document has to form the contractual basis between client and supplier. be well sorted. readable. understandable. The tools should be able to automatically generate a current version of the requirements document at any time.

  20. DOORS Developed by Telelogic Available for Windows, Linux, Solaris and HP-UX http://www.telelogic.com/products/doors/ Current Version: 8.2 Made for large projects Has its own database engine Short Tool Demonstration

  21. Tools: summary and discussion There are numerous requirements management tools out there. They all have their strength and weaknesses. Evaluate the tools on the basis of the 10 criteria presented in this talk. List of requirements engineering tools can be found at http://easyweb.easynet.co.uk/~iany/other/vendors.htm

More Related