odd: extending v-model development 1.3

Obstacle Driven DevelopmentExtending V-model Development 1.3

©odd.enterprises01/02/2016

Obstacle Driven Development

25/01/2016 ©odd.enterprises 2

ODD Circle Model


ODD Triangle Model


Background

Ideas of Obstacle Driven Development (ODD) are based on numerous development processes including:

• ISO V-model

• Test Driven Development

• ISO specifications

• Requirements analysis spiral

• Agile principles

• SOLID Principles


V-model

V-models are used in engineering for requirements, designs and testing.

• V-models give framework of Obstacle Driven Development

• Development for safety critical design processes

• Described by international standards


International Organisation for Standardisation

Standards and processes provided for requirements, specifications, guidelines or characteristics.

• Ensures products, services and components are fit for purpose

• Sets standards required for state of the art and markets

• ODD designed to be compatible with international standards


ISO V-model

V-model to apply ISO standards for software development.

• Model links various levels of development

• Testing for levels from software up to vehicle tests

• Testing for feedback and ensures each level is verified


Test Driven Development 1

TDD is software development with tests written before code.

• Creating tests first ensures code is testable and tested

• Unit tests ran through test suites for automated testing

• Allows for improved code through error detection


Write Test

Write Code

Refactor


Tests are written before the code with TDD .

1. Test is written and ran to observe a fail

2. Simplest code is written to pass the test

3. Code is refactored according to SOLID principles

4. Repeat until coding complete


Write Test

Write Code

Refactor


Development of ODD began with a question when using TDD:

• Where do the tests come from?


Write Test

Write Code

Refactor

Test Driven Development V-model 1

V-model combined with Test Driven Development is demonstrated.

• Helps create tests and integrate a system

• System created according to designs through tests

• Tests help integrate low level code to high level


Test Driven Development V-model 2

ODD extends and inverts V-models so development stages are separated.

• Models consist of V-models with TDD and unit testing

• Inverted V-models allow for separation of stages

• Inverted V-models link with V-models through


Inverted V-models

V-models are inverted to provide a stage between Problem and Solution domains.

• V-models help integrate a solution

• Inverted V-models help decompose a creation

• Testing is adapted for decomposition of elements


Extending a Specification 1

• Traditional Problem and Solution Space– Specification is a

small interface

• Extended Specification– Specification is

separate stage

15©odd.enterprises25/01/2016

Extending a Specification 2

Extending a specification allows V-models combined with Test Driven Development.

• V-model compatible with Safety Integrity Levels

• TDD processes for V&V of Specification

• Specification used to create tests


Verification and Validation 1

Verification and validation between each stage is adapted to become two questions.

• Verification

Is it built in the right way?

• Validation

Is it built right?


Verification and Validation 2

Verification and validation processes link the stages.

• Specification– Verification and validation (of behaviours)

• Solution– Testing and design

• Production– Quality assurance and control

• Analysis– Utilisation and elicitation


Problem Driven Development 1

PDD finds solutions to problems and is an earlier model of ODD.

• Inverted V-model and V-model combine to create N-model

– Analysis

– Specification

– Solution

• Testing between each stage is similar to TDD


Problem Driven Development 2

Tests to verify and validate code are extended to create a new development model.

• Applications to hardware, software and embedded

• Links stages with tests for verification and validation

• Suitable for students and research projects


N-model Comparison

N-model was created from extending a V-model.

• Verification and validation between Analysis and Specification

– Verification by creating a test

– Validation by solving a test

• Interface between problem and solution is extended


Obstacle Driven Development 1

ODD is TDD and V-models adapted and repeated between four stages in sequence.

• Analysis

• Specification

• Solution

• Production


Specification

Solution

Production

Analysis

Obstacle Driven Development 2

Verification and validation link stages and provide feedback.

• Verification ensures a product is built in the right way

• Validation ensures a product is built right

• Creating and solving tests give verification and validation


ODD for Embedded

ODD develops software, hardware and embedded applications.

• Stages are defined to help create physical products

• Benefits of software, hardware and embedded principles

• Suitable for safety critical applications


ODD Production

ODD continuously develops products through linking a Production stage.

• Solution produced with assured and controlled quality

• Links with Analysis to ensure feedback

• Product utilisation elicited for requirements


M-Model Comparison

ODD model links four separate stages through unit testing.

• Verification and validation appropriate to each stage

• Extends traditional problem and solution domain

• Unit testing processes links stages


ODD Checkpoints 1

Checkpoints provide expected outputs from each stage.

• Requirements found from Analysis

• Documents from Specification

• Prototype integrated from Solution

• Product assembled by Production


ODD Checkpoints 2

Checkpoints are verified and validated against those indicated.

• Requirements compared to Prototype

• Prototype tested for Requirements

• Documents describe a Product

• Product documented in Documents


Integration of Analysis

Analysis integrated from events in a situation tree to give complex situations.

• Situations identified in bottom-up process

• Situations are analysed to identify hazards

• Hazards are processed into Safety Integrity Levels (SILs)

• Requirements found from SILs


Integration of Solution

Solutions integrated from materials into components, components into subsystems etc.

• Solutions created with bottom-up process

• Each level is integrated into a higher level

• Higher level tests provide integration testing


Decomposition of Specification

Specification decomposed from high level behaviours to ensure they are performed.

• Specifications created with top-down process

• Each level decomposed until all levels are specified

• Enables integration testing of a solution


Decomposition of Production

Production decomposed from high level to assure efficiency and high quality levels.

• Production created with a top-down process

• Each level decomposed for efficiency of lower levels

• Efficiency through testing of production quality


Information Flow

Flow of information proceeds in several directions due to unit tests.

• Integration, decomposition, feedback and feedforward

• Information flow through each stage with integration or decomposition

• Stages linked by tests to give feedback and feedforward processes


Feedforward Processes

Verification of each stage is a feedfoward process where tests are created for a next stage.

• Verification

• Testing

• Quality assurance

• Utilisation


Feedback Processes

Validation of each stage is a feedback process where tests are solved for an obstacle.

• Validation

• Design

• Quality control

• Elicitation


ODD Flowchart


ODD Continuous Process

• Process repeats for continuous improvement

• Further stages may be added as needed

• Proceed clockwise through each stage


ODD Materials

ODD is explained in further presentations.

• Obstacle Driven Development

• ODD: Extending TDD

• ODD: Extending V-models

• ODD: Requirements Analysis

• ODD Is Not Agile or Waterfall

ODD Is Not Agile or

Waterfall

Obstacle Driven Development

ODD: Requirements

Analysis

ODD: Extending a Specification

ODD: Extending V-models

ODD: Extending TDD


http://www.odd.enterprises/obstacle-driven-development.html

http://www.odd.enterprises/odd-extending-tdd.html

http://www.odd.enterprises/odd-extending-v-models.html

http://www.odd.enterprises/odd-requirements-analysis.html

http://www.odd.enterprises/odd-requirements-analysis.html

Further Information and Questions

• Website

• Presentations

• Facebook

• Twitter

• Email


http://odd.enterprises/

http://www.odd.enterprises/odd-presentations.html

https://www.facebook.com/odd.enterprises

https://twitter.com/odd_enterprises

mailto:[email protected]

Legal Stuff

ReferencesTest Driven Development for Embedded C

James Grenning, 2011

International Organisation for Standardisation

http://www.iso.org/iso/home/standards.htm

Suresoft Automotive, V-model Compliant with ISO 26262

http://www.suresofttech.com/en/solution/solution/

Assessment of the ISO 26262 Standardhttp://www.sae.org/events/gim/presentations/2012/qi_volpe.pdf

V-model, One Stop Testing

http://www.onestoptesting.com/sdlc-models/v-model.asp

DisclaimerThe ODD M-model and associated processes are provided by odd.enterprises and may be used for any purpose whatsoever.

The names odd.enterprises and associated logos should not be used in any representation, advertising, publicity or other manner whatsoever to endorse or promote any entity that adopts or uses the model and/or associated processes.

odd.enterprises does not guarantee to provide support, consulting, training or assistance of any kind with regards to the use of the model and/or processes including any updates.

You agree to indemnify odd.enterprises and its affiliates, officers, agents and employees against any claim or demand including reasonable solicitors fees, related to your use, reliance or adoption of the model and/or processes for any purpose whatsoever.

The model is provided by odd.enterprises “as is” and any express or implied warranties, included but not limited to the implied warranties of merchantability and fitness for a particular purpose are expressly disclaimed.

In no event shall odd.enterprises be liable for any damages whatsoever, including but not limited to claims associated with the loss of data or profits, which may result from any action in contract, negligence or other tortious claim that arises out of or in connection with the use or performance of the model.


http://www.iso.org/iso/home/standards.htm

http://www.suresofttech.com/en/solution/solution/

http://www.sae.org/events/gim/presentations/2012/qi_volpe.pdf

http://www.onestoptesting.com/sdlc-models/v-model.asp

odd: extending v-model development 1.3

Engineering