Capture A Common Vocabulary


Published on

How to manage a glossary with Rational ReqPro

Published in: Education, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Capture A Common Vocabulary

    1. 1. Capture A Common Vocabulary Requirements Discipline
    2. 2. Why? <ul><li>There are tree Primary Reasons why this activity important? </li></ul><ul><ul><li>Clear definition of terminology used throughout entire project. </li></ul></ul><ul><ul><li>Consistent understanding across project team resources. </li></ul></ul><ul><ul><li>Reduces overall risk of incorrect assumptions. </li></ul></ul>
    3. 3. When? <ul><li>Creating a common vocabulary should be done… </li></ul><ul><ul><li>Early on in the project life-cycle.. </li></ul></ul><ul><ul><li>Prior to the beginning of the Elaboration phase. </li></ul></ul><ul><ul><li>As an on-going process throughout the project life-cycle. </li></ul></ul>
    4. 4. What? <ul><li>Inputs include </li></ul><ul><ul><li>Existing glossary documents: </li></ul></ul><ul><ul><ul><li>If the application already exists (or this is a new application replacing an existing application), there is likely existing documentation where terms have been defined previously. </li></ul></ul></ul><ul><ul><li>The Requirements Management Plan (RMP): </li></ul></ul><ul><ul><ul><li>The RMP will define all there is to know about the requirements on the project, for example the requirement types. </li></ul></ul></ul><ul><ul><li>The stakeholders: </li></ul></ul><ul><ul><ul><li>When eliciting requirements the stakeholders may use terms that are good to capture in the glossary. </li></ul></ul></ul>
    5. 5. Where? <ul><li>Outputs is to the glossary repository. </li></ul><ul><ul><li>The glossary repository is a ReqPro project where each term is defined as a requirement. </li></ul></ul><ul><ul><li>The properties of the TERM requirement are shown below. </li></ul></ul>
    6. 6. Who? <ul><li>The lead process analyst is the overall process owner, and takes responsibility for maintaining the ReqPro project. </li></ul><ul><li>Anyone on the project team will be capable of adding or editing a glossary term. </li></ul><ul><li>The main steps are: </li></ul><ul><ul><li>Identify Common Term </li></ul></ul><ul><ul><li>Add Glossary Term To Repository </li></ul></ul><ul><ul><li>Manage Glossary </li></ul></ul><ul><ul><li>Use term in the glossary </li></ul></ul>
    7. 7. How? <ul><li>Identifying common terms </li></ul><ul><li>Identify terms and their acronyms. </li></ul><ul><li>Utilize all existing documentation. </li></ul><ul><li>Interview subject matter experts. </li></ul><ul><li>All team members are responsible. </li></ul>
    8. 8. Add Term To Glossary <ul><li>Adding the term to the glossary repository. </li></ul><ul><li>Terms and acronyms are entered into ReqPro. </li></ul><ul><li>Use the Term requirement type. </li></ul><ul><li>Capture synonyms using traceability. </li></ul>
    9. 9. Add The Term To The Glossary
    10. 10. Manage The Glossary <ul><li>Managing the term in the glossary </li></ul><ul><li>As the project evolves terms will be updated. </li></ul>
    11. 11. Maintain Term In Glossary
    12. 12. Use The Glossary <ul><li>Using a glossary term </li></ul><ul><li>Use a hyperlink to reference the ReqPro ‘.rqs’ glossary file. </li></ul><ul><li>Make use of hyperlinks to reference glossary terms through RequisiteWeb. </li></ul>
    13. 13. Use The Glossary
    14. 14. Summary <ul><li>Use a glossary to capture all terms that are project specific or that are common words that could be open to misinterpretation. </li></ul><ul><li>Add terms to the ReqPro glossary. </li></ul><ul><li>Add acronyms to the term properties. </li></ul><ul><li>Maintain terms inside the ReqPro glossary. </li></ul><ul><li>Link terms that have the same meaning using traceability. </li></ul><ul><li>Use terms in documents using hyperlinks the term in ReqWeb. </li></ul>