Presentation Title: Vorwerk: Modern...

Presentation Title: Vorwerk: Modern Times, Polarion ALM and Teamcenter for an IoT Product (presented by GARANTIS IT Solutions)

Presenter Name: Konstantin KlioutchinskiRoom name: NizzaPresentation date: 24th October 2017

Company Name: GARANTIS IT Solutions Ltd.Contacts: [email protected]: www.garantis.solutions

mailto:[email protected]

http://www.garantis.solutions/

IT company providing consultancy services for Polarion ALM

Based in Berlin, Germany and in Reading, UK.

www.Garantis.solutions // [email protected] // +49 176 677 07771

About „Garantis IT Solutions“

More useful info for you : www.Garantis.solutions(Downloads, Blog, WhitePapers, Analysis Reports, Extensions for Polarion)

Services on-site/off-site:

• We provide Polarion Administration, Customization

• Rollout of new project, Maintenance, Training

Skills:

• Widgets, Velocity, SQL, HTML, GUI design

• Requirements Management, Process Definition

• Infographics, Reports

Plugins:

• TeamCalendar, AutoDocWikiPagesPolarion

Web: www.garantis.solutionsEmail: [email protected]



mailto:[email protected]

Agenda

You will get insight into the • How it all started• what „IoT“ ?• requirements management, planning & execution• common challenges we faced• solution chosen, strategies applied• lessons learned and experience gained• summary of success and savings achieved

AgendaCase Study about Managing Software Development Project for kitchen appliance “Thermomix” and using Polarion for other Products as “Corporate Standard”

Key words: Embedded Software with Internet Of Things technology

“Vorwerk: Modern Times, Polarion ALM and Teamcenter for an IoT Product” , Konstantin Klioutchinski, GARANTIS IT Solutions Ltd., 24.10.2017

Polarion Customization at Vorwerk –looking 1 year back

"Sometimes in order to go forward...you must go BACK."

• Analysis of old project • Ideas for new projects • Mistakes • Solutions• Recommendations

Ph

oto

fro

mm

ovi

e„B

ack

toth

eFu

ture

“


Generations of Thermomix

The Thermomix is a kitchen appliance made by the Corporate Group Vorwerk.

• more Software• more Features• more Complexity

time

TM5 Thermomix provides 12 functions:

• steaming• emulsifying • blending• precise heating• mixing • milling• whipping • kneading• chopping• weighing• grinding• stirring+ internet


Thermomix TM5 Eco System


Using FDD for Thermomix development• Vorwerk wanted to use Feature Driven Development (FDD)

approach to accelerate development of the software for the Thermomix TM5 product

• Polarion was chosen as ALM tool

• Customization was done for FDD WiFiConnection

Cloud Recipe Synchronization

Features define functionality of Thermomix

UserInteraction

GuidedCooking

ManualCooking

RecipeChip


Project ScopeAdding IoT functionality to Thermomix.

Software

(2016)


Why Polarion for TM5 Project ?

verify

impact

depends

Polarion allows:1. Traceability by Linking Work Items2. Requirements Management3. Specification & Design Documents4. Change & Configuration Management

• SVN, Commit Comments link to Work Items automaticaly

5. Test and Quality Management6. Issue & Risk Management7. Audit & Metrics , Reports8. Flexible architecture

• Easy to re-configure Workflows, WorkItems, Forms

9. Customization• Widgets & Scripts from Polarion Extensions web site or Do-It-Yourself.

10.Collaboration• Work simultaneously on the same documents stored in central repository. Notifications.

11.Polarion Support – quick comprehensive answers to all kind of questions


SW Architects & Requirements Engineers

Feature Driven Development

Feature Set A Feature A1 Feature A2 Feature Set B Feature B1

Feature Set C Feature C1 Feature Set D Feature D1 Feature D2

Feature Set E Feature E1 Feature E2 Feature E1 Feature E1

Stakeholder SW Development

What is the nextgreat Idea?

Specification Implementation

Conceptual Design

Reflection in Polarion

Great Idea Description

(2016)


depend

dependspecifyspecify

verify

verify

1:N

1:N

auto-create

Change Type To

implements

impacts

Level 1 Level 2 Level 3

Project Data Model in Polarion (2016)


Space Work Item + LiveDocWork Item(s) embedded in LiveDoc

depend

dependspecify

specify

Data Model in Polarion - Core Work Items

Text

Embedded Work Items

Wiki

Embedded Work Item

(2016)


Work Item „Feature Set“ linked tomultiple work items „Feature“

Summary: how FDD maps onto Polarion

Test Runs are formed from testcases linked to Features

Design is described in Live

Documents

Plans based on Features & Tasks

(+ChangeRequest, +Issue)

The FDD process includes:

- Build feature list

- Plan by feature

- Design by feature


1 year ago … in 2016

• We had 1 project• We used about 60% of Polarion features• We assumed it was COMPLEX

SoftwareFeature Driven Development (FDD) approach to accelerate development of software for the Thermomix TM5 product

Polarion was used to describe PART of the Software

PLM Europe 2016 in Berlin - PRESENTATION (PDF, 2MB)


http://garantis.co.uk/ru/download/plm-europe.org_2016.10.18_Polarion_Customization_At_Vorwerk_FDD_by_GarantisITSolutions.pdf

Now … in 2017

• We have many projects for many products

• We use about 90% of Polarion features

• Maybe it is COMPLEX … but we want toGO FORWARD to the Digital Factory concept

• We had 1 project

• We used about 60% of Polarion features

• We thought it was COMPLEX

2016: 2017:


From ONE projectto CORPORATE STANDART

EXPAND


GROWTH of projectsHISTORY:

• From 1 project to many

• From „Software Project“ we moved to:

„System“ + „Software“ + „Mechanics“ + „Electronics“ projects

Software

(1) We started here: FDD for IoT functionalityof Thermomix

Mechanics Electronics

SYSTEM

(2) Now we are movingtowards - CompleteThermomix product to bedescribed in Polarion:• System• Software• Mechanics• Electronics


GROWTH of projects

• SYSTEM

• Software

• Mechanics

• Electronics

Reuse predefined templates for different PRODUCTs

SoftwareMechanicsElectronics

SystemSoftwareMechanicsElectronics




System


Our Journey

• SYSTEM

• Software

• Mechanics

• Electronics

Template for any PRODUCT


System


System



System


SystemFDD project to develope IoTtechnology for Thermomix

1

We developed set of TEMPLATES for complete PRODUCT

2

3 More projects started to usePolarion and TEMPLATE

4EVALUATION of integrationPolarion + Teamcenter

FDD for IoT


Project Data Model in Polarion

• SYSTEM

• Software

• Mechanics

• Electronics


SYSTEM Software Mechanics Electronics


Testing of Universal Components

TESTING project


System


System



System

Test Cases are stored in central project „TESTING“

These Test Cases are uviversal, they test universal components.

Test Runs are stored inside product-specific projects

Universal Component


COMPLEXITY – how to control

• MORE projects MORE complexity

Use same/standardized templates

Use same/similar PROCESS

Control the CUSTOMIZATIONS (document, link/relate, unify)

Enforce discipline


Challenges

• Release Management across sub-projects

How to keep track of Releases of Hardware (HW), Firmware (FW), Software (SW)

• Test Management & QA across sub-projects (OR across products)

How to unite/aggregate the Test Results comming from HW, FW, SW teams ?

• Planning across sub-projects

How to plan for HW, FW, SW ?


System


Customization of Polarion … how much you need ?

Our estimation of Customization

40% Customization60% Standard

Customization

medium high

(+)TestRunsPlansWiki pages/ReportsSpaces (home pages)

(+)DocumentsTestCasesCustom FieldsViews

WorkitemsWorkflows

small


TYPE OF WORK:

The Polarion server was running on old version of Windows. It needed to beupgraded to completely new Windows and new version of Polarion.

What kind of change requests we process

TYPE OF WORK (most common):

1. Configuration – for different projects to change something in Administration

2. Scripting – to write come scripts

3. Report Pages – to create special Reports

4. User Management – because we did not use LDAP, user managementwas done on Polarion server by Admin

5. Server Maintenance – some work to be done on server (install newplugins, analyse logs, optimize performance, etc.)

types of user requests over time


Engineers can be CREATIVE, but have to follow the PROCESS

We shall Customize default processes only when this is really required by the business/ product / software development process.

If there is no real need – then do not change it. => you will need to maintain it ($$)

BALANCE

CREATIVITY DISCIPLINE MAINTENCE

• Improvements

• Proposals

• Ideas

• Spacial ways of working

• Process changes

• Folow the RULES

• Obey the PROCESS

• Try to Adapt not to CHANGE

• Customization & Development

• Training & Documentation

• Support & Updates/Fixes

• How Robust are new/specialPROCESSES / Functions ?

Optimal modifications / customizations

Too Little Too Much

Optimal


- Created own TEMPLATE for SYSTEM, SW, ELECTRONIC, MECHANIC project- Polarion was chosen as ALM Platform (for managing Requrements, Specifications, Tests, Plans, Reports,

Documents, Tasks, Builds, etc)- Customizaton of Polarion was done

- Documentation of requirements did not have Linking & Traceability. Documentation & Linking were separated.- Regular manual work was required to setup, maintain, analyse and correct Linking & Traceability- Reporting tools were not integrated, manual work was needed to create reports

- Reduced Errors- Saved Time & Effort, reduced errors for Linking & Traceability- Reporting gave good instant overview of differnet aspects of the project (testing, defect management, progress

and completness of specification)- Optimizing the cooperation of the team- Full Control of changes. Simple „recovery“ by SVN revert

Polarion – from First Steps to Success

Benefits and Success

Strategies Applied

Common Challenges (before introducing Polarion)

“Polarion Customization at Vorwerk (presented by GARANTIS IT Solutions)” , Konstantin Klioutchinski, GARANTIS IT Solutions Ltd., 18.10.2016 Slide #19

TYPE OF WORK:

The Polarion server was running on old version of Windows. It needed to beupgraded to completely new Windows and new version of Polarion.

Types of user requests over time

Sporadic ativities duringupgrades

Regular Peak of work every 2 weeks – after visiting customerand discussing requirements

Regular Peak of work every 2 weeks – after visiting customerand discussing requirements

Graph shows number of created requests per week

Scripting for Report Pages

Configuration (workitems, workflows, etc )

Server Maintenance


BENEFITS of regular Upgrade(s)BENEFITS:

• New functionality• In old version of Polarion some functionality required additional scripts, in new Polarion – it is available by default (no need for

maintenance of scripts, better integration into Polarion+Process)

• New widgets

• New templates• Templates look better (Home pages, Design), the reflect Agile/Scrum approach

• Templates are easier to use, the Home pages provide instructions „HowTo“ and point to teh „Next Steps“

• You are not trapped with OLD version• The longer you wait and do not upgrade – the more difficult upgrade can become

• You might need to migrate SVN data from one version to another

• You might loose some scripts due to changed API

• You definetly loose new functionality


Communication, Communication + Communication During setting up the project – have frequent meetings During maintenance - have regular meetings

One responsible person as Administrator – single point of contact Automate as much as possible, write generic, reusable scripts (very important for multiple projects) If you need support – ask Polarion Support or other experts Keep strict User Permissions and strict Linking Rules if you want to have your Polarion clean&tidy.

Our Advice…

ADVICE: from First Steps to Success

(2016) … still VALID

Performance review & optimization Regular backups, data integrity checks => keep system „healthy“ Regular Upgrades

Our Advice… (2017)


New project “Polarion Project Maintenance”SITUATION:

More new projects – more new requests from users. => Needed to manage growing number of requests, different in type of work to be done.

SOLUTION:

Created special project„Polarion Project Maintenance“ –to store and manage all requests


System


System


• Simple Workflow

• All requests/changes for Polarion are DOCUMENTED

• Can ANALYSE what is going on in the projects (Change Management)

Managing “Polarion Requests” workitem

GARANTIS is working on ITIL Template for Polarion

FUTURE IMPROVEMENTS


Questions and Experiencesfrom real project at Vorwerk

Integration ALM+PLM


ALM + PLM

• SYSTEM

• Software

• Mechanics

• Electronics



System


System



System


SystemFDD project to develope IoTtechnology for Thermomix

1

We developed set of TEMPLATES for complete PRODUCT

2

3 More projects started to usePolarion and TEMPLATE

4EVALUATION of integrationPolarion + Teamcenter

Our NEXT STEP


What we want to achieve

• SYSTEM

• Software

• Mechanics

• Electronics


SYSTEM Mechanics


Technichally it is getting Better-and-Better


WHERE – STORE - WHAT ?SITUATION:

Both tools - Polarion and Teamcenter - can store Requirements.

WHERE is it BETTER to store the Requirements, Specifications, Issues, etc ?

POLARION is powerful and flexible in managing Work Items & Documents.

It allows complex Queries, customizedReports, and offers LiveDoc

TEAMCENTER is powerful in CAD, Material Management, BOM, etc.


WHERE – STORE - WHAT ?SITUATION:

Both tools - Polarion and Teamcenter - can store Requirements.

WHERE is it BETTER to store the Requirements, Specifications, Issues, etc ?

POLARION is powerful and flexible in managing Work Items & Documents.

It allows complex Queries, customizedReports, and offers LiveDoc

TEAMCENTER is powerful in CAD, Material Management, BOM, etc.

Our Choice


Use Case

Where to Store What – our point of view

System Requirement

Software Requirement

ElectronicRequirement

MechanicRequirement

MechanicDesign

MechanicTest

ElectronicDesign

ElectronicTest

SoftwareDesign

SoftwareTest

MechanicRequirement


BEST INTEGRATION v1.3.0 = Polarion ALM 17 + Active Workspace 3.3 + Siemens Teamcenter 11.3

(today)

* only in Active Workspace can work with Links


Best configuration for Integration TODAY

www.Garantis.solutions // [email protected] // +49 176 677 07771

More useful info for you : www.GARANTIS.solutions(Downloads, Blog, WhitePapers, Analysis Reports, Extensions for Polarion)

Thank you!Questions & Answers


Presentation Title: Vorwerk: Modern...

Documents

Transcript of Presentation Title: Vorwerk: Modern...