UNTERNEHMENSWEITE RE KERNDATENMODELLE · UNTERNEHMENSWEITE RE KERNDATENMODELLE ALS BASIS FÜR ÜBERGREIFENDE ZUSAMMENARBEIT DR. STEFAN JOOS, DR. ... e.g. "power supply voltage range"

UNTERNEHMENSWEITE RE KERNDATENMODELLE

ALS BASIS FÜR

ÜBERGREIFENDE ZUSAMMENARBEIT

DR. STEFAN JOOS, DR. JÜRGEN THIELEMANN (BOSCH GMBH), ANDREAS KRESS (HOOD GROUP)

Cross Divisional Group - Software, Methods and Tools | CDG-SMT/ESM4 | 20.03.2017© Robert Bosch GmbH 2017. Alle Rechte vorbehalten, auch bzgl. jeder Verfügung, Verwertung, Reproduktion, Bearbeitung, Weitergabe sowie für den Fall von Schutzrechtsanmeldungen.

2

RE Core Data Model for Engineering CooperationBosch – System Engineering – Four Business Sectors

2 C/CCB; C/CCD | April 2016© Robert Bosch GmbH 2016. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

IndustrialTechnology

Energy and Building Technology

Consumer GoodsBosch – System Eng.————————————Mission statement————————————The RE Core data Model————————————Specification Structure————————————Status Rollout————————————Experiences————————————Outlook – Big picture

Mobility Solutions


3

RE Core Data Model for Engineering CooperationBosch – Mobility Solutions – System Engineering

3 C/CCB; C/CCD | April 2016© Robert Bosch GmbH 2016. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

IndustrialTechnology

Energy and Building Technology

Consumer Goods

Systems Expertise and Networking

Electromobility

Connected and Automated Driving

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model————————————Specification Structure————————————Status Rollout————————————Experiences————————————Outlook – Big picture

Mobility Solutions

RE Core Data Model for Engineering Cooperation

Cross Divisional Group - Software, Methods and Tools | CDG-SMT/ESM4 | 20.03.2017

Bosch – a global networkThe 375,0001 Bosch associates make thesesolutions possible.

Bosch has four business sectors, with more than4401 subsidiary companies and regional subsidiaries in some 601 countries.

Including its sales and service partners, Bosch isrepresented in some 1501 countries.

© Robert Bosch GmbH 2017. Alle Rechte vorbehalten, auch bzgl. jeder Verfügung, Verwertung, Reproduktion, Bearbeitung, Weitergabe sowie für den Fall von Schutzrechtsanmeldungen.4 C/CCB; C/CCD | April 2016

© Robert Bosch GmbH 2016. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.4

1 As of 12.15


System Levels (0..n)


Cross Divisional Group - Software, Methods and Tools | Bosch-Joos, Thielemann, HOOD-Kress | 20.03.2017© Robert Bosch GmbH 2017. Alle Rechte vorbehalten, auch bzgl. jeder Verfügung, Verwertung, Reproduktion, Bearbeitung, Weitergabe sowie für den Fall von Schutzrechtsanmeldungen.

5

System-Domain Engineering Dimensions Requirements• Exchange• TraceabilityCooperation

System 0

System C System B System A

System An

System A1

System A0

Mechanics Electronics Software

System

Sub System

Engineering Domain

… …

…

Engineering Domains




6

� Exchange & cooperation of requirements and common understandingDefinition of a Bosch RE Core Data Model as the minimum of harmonization needed for a reasonable exchange of requirements for Software Engineering (SWE), Electrical and Electronical Engineering (EE) and Mechanical Engineering (ME) projects

� Enabling Integrated Cross Engineering Domain Requirements Engineering� System Engineering in & between project teams

� ‘External’ Collaboration� Exchange of requirements (documents) with Customers (Roundtrip)� Derivation of requirements documents for internal and external suppliers

Mission statement Mechanics

Customer Electronics

Software

System

Bosch – System Eng.

Mission statement————————————

————————————The RE Core data Model————————————Specification Structure————————————Status Rollout————————————Experiences————————————Outlook – Big picture



7

Conceptual Approach RE Core Data Model

Inner Core CustomerAdditional

Data Elements

SystemAdditional

Data Elements

ElectronicAdditional

Data Elements

SoftwareAdditional

Data Elements

MechanicAdditional

Data Elements

Data Element:• Data field name• Syntax• Data format• Content• Valid values• ……

Common data elements,needed in all Engineering Domains

Extended (Add-on) Data Elements, dependent on Engineering domains

Extended (Add-on) Data Elements, forCustomer Requirements

StructureBosch – System Eng.————————————Mission statement

The RE Core data Model————————————

————————————Specification Structure————————————Status Rollout————————————Experiences————————————Outlook – Big picture



8

Inner Core Model fragment ID Data Element Description Mandatory Format

I-001 Identifier ID, unique in RBe.g. DOORS-Instance_DOORS-ID x alfa-numeric

I-002 Heading A one sentence statement of the intension of the requirement, e.g. "power supply voltage range"

Text

I-003 Content (Atomic) Requirement Specification, Description of the requirement x Text, Grafics,

ScreenshotsI-004 Revision time stamp (GMT, universal time)

Year, Day, Hour, Minute, Second x alfa-num

I-005 Owner Person(s) who is (are) reponsible for this requirement (further processing) x LDAP User

I-006 Source, Source Reference Organisation that is requesting the requirement e.g. OEM, customer, internal organisational unit (e.g. HW development, Quality Managemet), role....

Text, Link

I-008 Status Status of the requirement x select list

I-008.1 Implementation Status Status of implementation of the requirement (could be defined as reference to work item/task).

select list

I-009 Allocation: Referenced by Child of requirement e.g. sub requirement, derived requirement

Link

I-010 Priority Urgency, German: "Dringlichkeit", rating of the customer value select list

I-019 Release (Target) Release this requirement is planned for Text

I-021 Project ID ID or Name of the project the requirements belongs to

I-012 Acceptance criteria, Acceptance criteria reference

Validation / Verification / TestSupport of traceability to test cases for the given requirement. The text contains e.g. the test to be implemented. Should be

Text, Link

I-013 Technical Comments Annotation, hints cocnerning possible solutions for the requirement

Text

… … …

Bosch – System Eng.————————————Mission statement





9

Mechanical add-on Core Model ID Data Element Description Format Value Range

ME-001 Drawing Reference Link or reference to a drawing or an element within a drawing (Data or Document)

Text

ME-002 (Sub-) Supplier Relevant for named Parts Supplier(s) (valid for part requirement specification)

select list project specific

ME-003 Unit(s) The unit(s) of named product property(ies) Text

ME-004 Value range The value, value range or value plus tolerance of named properties

Text

ME-006 Assembly Allocation Which Assembly Group(s) are concerned by the requirements

select list multi value project specific

ME-007 PDM Docu Reference URL, text

ME-008 Norm Docu Reference Customer or internal Standard/Norm Document URL, text

ME-009 KPF Key Product Feature Reference Text Example: Injection pressure = 2700 bar

ME-011 Peer Disciplines Which Peer Disciplines are invovled select list Roles of the PEP core team or the PEP enhanced core team e.g. Engineering, ME-012 Importance "Wichtigkeit" select list high, medium, low

ME-019 Variants To which product variant(s) this requirement belongs to

select list




Tailoring of Model, example for Software Engineering



10

Project & Team Tailoring of Core Data Model

Bosch

Inner Core

Bosch

SWEAdditional

Data Elements

Bosch Software CoreBusinessadd-ons

SWEAdditiona

l Data Elements

Productaddons

SWEAdditiona

l Data Elements

Bosch CommonBusiness Groups

ProjectsProduct Groups

Projectsadd-ons

SWEAdditiona

l Data Elements






11

Context of RE Core data Model� Reference

Use Case Specification of Cooperation and Exchange (for Engineering domains, internal + subcontracting)

� Used Standards� Volere, IEEE 1362-1998, IEEE 830-1998

� Exchangeable by formats � e.g. ReqIF

� Implementation reference for RE Tools� e.g. DOORS, DOORS Next Generation (DNG)

RE Core Data Model







12

Specification Structure (Cooperation) RequirementsTraceability

System 0

System A


System

Sub System

Engineering Domain

…

…

Engineering Domains

RE Core Models

CustomerSpecification

SystemSpecification A

MechanicSpecification

ElectronicSpecification


…

…SystemSpecification A

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model

Specification Structure————————————

————————————Status Rollout————————————Experiences————————————Outlook – Big picture




13

Specification Structure (Subcontracting)RequirementsTraceability

System 0

System A


System

Sub System

Engineering Domain

…

…

Engineering Domains

RE Core Models


SystemSpecification A

MechanicSpecification



…

…SystemSpecification A


Requirementssubcontracting

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model

Specification Structure————————————

————————————Status Rollout————————————Experiences————————————Outlook – Big picture



14

Status� Current status of RE Core Data Model

� … was piloted successfully and decided as reference for new product generations� … currently is in rollout in four Bosch divisions in 7 product lines� … is maintained by central clearing board

� Tool support� Implementation in Bosch preferred RE tool ‒ DOORS and DOORS Next Generation (IBM)

� Implementation as four DOORS templates for modules (CRS, SE, ME, EE, SWE)� Team + project specific extensions by adding attribute definitions

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model————————————Specification Structure

Status Rollout————————————

————————————Experiences————————————Outlook – Big picture



15

Experiences� Typical „Swine Cycle“ in Requirements Data Modeling

1. Start very lean/minimal - people like to make the world more easy2. Continue adding more or less specific attributes3. Tend to define a „Hüllkurvenansatz“, one-fits-all, less variants4. Reduce a complex model and continue with 2)5. End in a finite number of iterations (hopefully)

� Relative few team or project specific customizations� User Acceptance & Feedback

� 80% grateful to get a defined and common accepted starting point for RE� 20% dissatisfied with a central initative by „guys not knowing the real world“

� Definition of Core Model take time!� Stakeholder Interviews, Working group (SE, SWE, EE, ME), … ~3/4 year� Decision and agreement by Bosch Steering board for IT Engineering

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model————————————Specification Structure————————————Status Rollout

Experiences————————————

————————————Outlook – Big picture



16

�Focus on methods – Identifying & filling gaps

Outlook – Big picture

Tools

concepts

Preferred Tools:DOORS Classic

DOORS Next Gen

RE CoreModels

RE Cooperation & Exchange Use

CasesFormal techniques Semiformal techniques

Abstractions and clustering Requirements Architecture

Natural language specifications Requirements based testing

Requirements reuse, variants Knowledge engineering

Requirements validation and verification Prototyping and execution of specification

RE and agile development

Method Categories

Identify + fillRE Method

gaps

Bosch – System Eng.————————————Mission statement————————————The RE Core data Model————————————Specification Structure————————————Status Rollout————————————Experiences

Outlook – Big picture————————————

Documents

UNTERNEHMENSWEITE RE KERNDATENMODELLE · UNTERNEHMENSWEITE RE KERNDATENMODELLE ALS BASIS FÜR ÜBERGREIFENDE ZUSAMMENARBEIT DR. STEFAN JOOS, DR. ... e.g. "power supply voltage range"