Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IBM webinar Profesia su Requirements Quality assistant

107 views

Published on

Il webinar è una finestra su IBM Requirements Quality Assistant.
Abbiamo mostrato come RQA ci aiuta a migliorare la qualità dei requisiti e quindi delle applicazioni che rilasciamo.
Abbiamo visto inoltre come IBM RQA può supportarci quando utilizziamo tool come IBM Jazz.
Il webinar è condotto da Profesia e un esperto di prodotto. Richiedi una demo personalizzata scrivendo a sales@profesia.it

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

IBM webinar Profesia su Requirements Quality assistant

  1. 1. IBM Engineering Requirements Quality Assistant, piacere di conoscerti!
  2. 2. Profesia - Lynx Group
  3. 3. Agenda Requirements management with AI Requirements Quality Assistant Demo Q&A Applying AI to Engineering: IBM Requirements Quality Assistant
  4. 4. IBM Requirements Quality Assistant Use the power of Watson AI to improve the quality of project requirements as you write them. Now bundled with DOORS® Next SaaS version
  5. 5. The connectedness of everything and AI is transforming how businesses and the world work.
  6. 6. Optimize engineering with AI Inject automation and intelligence across the engineering lifecycle Market Analysis System V & V System Test System Requirements System Design Deploy or Release to Mfg Customer Requirements Operations and Maintenance Implementation Component test Component Design Electrical / Electronics Design Mechanical Design Lean Software Engineering Requirements Quality Analysis Automatic Model Generation from Requirements Traceability and Impact Analysis Test Case Generation from Requirements IBM Engineering Lifecycle Management
  7. 7. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation 47%of unsuccessful projects fail to meet goals due to poor requirements management 50%of projects are unsuccessful primarily due to poor management of requirements The cost to low performers nearly 10 cents for every dollar spent.
  8. 8. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation The Heavy Cost of Poor Requirements IEEE – Defects in a launched project cost up to 200x more to correct than defects found during requirements.5 Inspecting Requirements – 80% of rework and 50% of project defects can be traced to requirement errors.4 Project Management Institute – 47% of failed projects missed goals because of poor requirements gathering.6 1.Money and time are wasted on unnecessary work 2.Reworking costs money and blows your deadline 3.Extra work puts you over budget 4.Software misses key requirements 5.Business performance is jeopardized by ineffective solutions 6.Users don’t adopt ineffective applications 7.Frustration grows Time not spent on requirements is time spent in rework (at cost 700x) 9
  9. 9. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation High quality requirements are critical for a project’s success Requirements Quality Completeness Unfinished requirements lead to preventable confusion and delays Consistency The more consistent requirements are the fewer opportunities there are for errors Accuracy Accurate requirements reliably articulate the objectives of stakeholders Requirements Quality
  10. 10. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Current solutions…and why they can miss errors – Peer review – Difficult to enforce across teams – Manual, tedious review of long documents – Wasted time on trivial, novice mistakes – Checklists – Limited capacity to keep track of all quality indicators (cognitive span is 7 +/- 2 things) – Rules engines – Simple key word searches cannot understand words in context – Ex. of “clear” – Ambiguous: “The GPS system shall provide a clear perspective of the road” – Not ambiguous: “The GPS System shall clear the display on transition to power off mode”
  11. 11. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation12 Introducing Requirements Quality Assistant IBM Watson IoT / © 2018 IBM Corporation New Watson capability embedded inside DNG … • Removes risk and ambiguity in the requirements authoring phase out-of-the-box by using AI (Watson Natural Language Understanding) • Pre-trained to detect key quality indicators designed to be consistent with the INCOSE Guidelines for Writing Good Requirements • Authors receive coaching from Watson to improve the quality of the requirement as it is being written Enterprise benefits (400 engineers example) • Reduce the cost of defects by 60% to save $3.9M • Reduce cost of manual reviews by 25% • Retain engineering expertise for junior engineers
  12. 12. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Best Practice Guidelines INCOSE Guide for Writing Requirements Written by a worldwide cross-industry team GE, Madrid Technology University, Harris Corporation, Systems Engineering Global, Airbus, Continental AG, Motorola, NASA, Loughborough University and more Rules reflected in the Systems Engineering Handbook and ISO 15288
  13. 13. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation IBM Requirements Quality Assistant • Grades requirements against a criteria that was designed to be consistent with the INCOSE Guidelines for Writing Good Requirements • Pre-trained to detect 10 quality issues – Unclear actor or user – Compound requirement – Negative requirements – Escape clause – Missing units – Missing tolerances – Ambiguity – Passive – Incomplete requirements – Unspecific quantities • Add to the list of quality issues or do deeper training through a 3 week services engagement with IBM services team
  14. 14. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation IBM Requirements Quality Assistant • Identifies exactly what’s wrong with the requirement • Displays the issue to the requirements engineer
  15. 15. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation IBM Requirements Quality Assistant • Learns from the requirements engineer • Becomes “smarter” over time
  16. 16. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Measuring requirements quality with RQA
  17. 17. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Our approach: Pre-train Watson for you Watson Services + + Customer Solution Watson Natural Language Understanding IBM Requirements Quality Assistant Architecture and pre-built NLP model – ability to tweak for your needs w/ IBM services team Requirements Public Domain Data
  18. 18. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Get up and running in a single step… ✔ Copy and paste the URL ✔ Offering is automatically added to the mini dashboard and connected to Watson ✔ Buy packs of requirements checks for the year ✔ Packaged quick start services to extend as needed
  19. 19. Mechanical Design Lean Software Engineering IBM Watson IoT / © 2018 IBM Corporation Demo
  20. 20. Contatti sales@profesia.it +39-011-0120371 Follow us www.profesia.it GRAZIE! Q&A
  21. 21. www.profesia.it A closer look at the 10 quality issues... Quality Issue Guidance Unclear actor Pronouns such as “it,” “they,” or “them” refer to other nouns. The noun that a pronoun refers to can be unclear. To increase clarity and precision, repeat the noun instead of using a pronoun. Compound requirement This requirement includes more than one statement, actor, or action. Effective requirements are single and atomic. To make the requirement more precise and easier to verify, refine it to a single statement with one actor and action. Negative statement This requirement includes a negative statement. Effective requirements use positive statements because they are more direct, easier to verify, and less likely to be duplicated. Rewrite the requirement to state what should happen, not what shouldn’t happen. Imprecise verb Statements with verbs such as “be able to” or “be capable of” are broad and difficult to verify. For example, a system might be able to do something, but might not do it consistently. Effective requirements include a specific action that can be conclusively verified. Broad statements are appropriate in capability requirements. In system requirements, replace imprecise verbs with specific and measurable actions. Escape clause This requirement includes a phrase such as “when possible,” “if necessary,” or “as required” that makes the requirement unclear and difficult to verify. Effective requirements use specific wording that can be interpreted only one way. Eliminate or replace phrases that are unclear or provide loopholes. Missing unit This requirement has a value with a missing or unclear unit of measurement. Effective requirements are specific and measurable. Ensure that numbers and values include a unit of measurement, and that the same units of measurement are used consistently across all requirements.
  22. 22. www.profesia.it … continued 23 Quality Issue Guidance Missing limits This requirement has a value with missing or unclear limits. Effective requirements state specific boundaries so that results are easier to measure and verify. For example, instead of stating “The water station shall maintain the flow of water at 150 liters per second for 20 minutes,” include limits such as "The water station shall maintain the flow of water at 150 ±20 liters per second for greater than 20 minutes" to show exactly which values are acceptable. Unclear term This requirement includes a term that makes the requirement unclear. Effective requirements use specific and precise terms that have only one interpretation. Replace vague and general terms with specific, descriptive terms. Unspecific quantity This requirement includes a general or unspecific quantity that makes the requirement unclear. Effective requirements include clear and specific quantities. Ensure that all quantities are precise. For example, instead of stating “The system shall use minimum power,” specify what “minimum” means. Passive voice The person or thing that performs the action is missing, unclear, or not the focus of the statement. Effective requirements clearly state who or what performs an action. Rewrite the requirement to clearly identify and focus on the actor. Incomplete requirement This requirement is incomplete because the actor, action, object or imperative is missing. Rewrite the requirement to clearly identify the object of the action.

×