Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Behaviour Engineering; Taming Complexity, Growing Understanding
Transcript of Behaviour Engineering; Taming Complexity, Growing Understanding
Growing Understanding Dan Powell
Director, Dendronix Motivation 46% of the pieces are missing, don't fit or require interpretation Cost Overruns Schedule Overruns Not Fit For Purpose High TCO Project Failure and Abandonment Critical Success Factor Behaviour Engineering A process and
a supporting notation To develop and refine a
deep, accurate and shared
understanding of needs between
all stakeholders Notation The Process Why the notation works? The representation allows us to localise complexity. We simply repeat a unit level operation that does not tax short term memory. 15476735386
------------------ Notation supports repeated unit level operation
Localises Complexity Why the notation works? The notation preserves vocabulary and intent
It is human readable enabling validation
It is machine readable enabling analysis and transformation Formulate Integrate Validate Resolve Refine Translate one requirement (use case step, user story, ...) at a time into its corresponding Behaviour Tree (and Composition Tree)
Localises Complexity Formulate Integrate Metrics BT preserves vocabulary and intent
Can walkthrough scenarios depicted in trees with subject matter experts
Defects Detected - BT walkthrough : Defects Detected Review = 5:1 Validate Risk identification does not imply risk mitigation To mitigate risk, resolve issues in the model with stakeholders Risk Mitigation Represents shared vocabulary Shared
of behaviour ROI: BE Model-Based Requirements Development
> 1600% Many analysis and design artifacts are 'free' Additional ROI Support FMEA
Support development of system safety case and assessment of Technical Integrity Risk
Support development of a (literal) compliance picture and gap analysis
Support reliability analysis and calculation
Support Model-Based Testing Analysis (Current Uses) Behaviour Engineering and the RUP Thank You Dan Powell
+61 (0)404 922 177