Presentation Title: Polarion Customization at Vorwerk · 2016-12-15 · SVN WorkItem „BuildRecord“ Jenkins Info: • Version • Location • Result_StaticCodeAnalysis • Result_TestSmoke

Presentation Title: Polarion Customization at Vorwerk (presented by GARANTIS IT Solutions)

Presenter Name: Konstantin KlioutchinskiRoom name: Room I (Foyer 1)Presentation date: 18th October 2016

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/alm4you(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]

http://www.garantis.solutions/alm4you

http://www.garantis.solutions/

mailto:[email protected]

Agenda

You will get insight into the • common challenges we faced• solution chosen, strategies applied• lessons learned and experience gained• summary of success and savings achieved

Agenda

Overview

Case Study about Managing Software Development Project for kitchen appliance “Thermomix” Key words: Embedded Software with Internet Of Things technology

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

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


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


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

Feature-driven development (FDD) is an iterative and incremental software development process. It is one of a number of lightweight or Agile methods for developing software. Its main purpose is to deliver tangible, working software repeatedly in a timely manner.

The process includes/uses principles:

- Build feature list

- Plan by feature

- Design by feature

Features are grouped into collections known simply as feature sets.

How is itImplemented in Polarion

What is FDD


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


Work Items (Traceability)

User Story Feature Requiremet Test CaseFeature Set


TM-31 - Cloudstick WiFi TM-475 –000_Cloudstick Visualization

TM-512 –001_Cloudstick WiFiSignal

TM-722 – WiFi Signal icon shall be grayed out if connection fails

TM-800 – WiFi Signal icon Inactive

TM-723 – WiFi Signal icon shall be in vividcolor if connection isestablished

TM-801 – WiFi Signal icon Active

TM-513 –002_Cloudstick SyncButton

TM-724 – SynchButtongrayed out if there is NO connection with server

TM-821 – SynchButtonInactive

TM-725 – SynchButton in vivid color if there isconnection with server

TM-822 – SynchButtonActive

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

depend

dependspecifyspecify

verify

verify

1:N

1:N

auto-create

Change Type To

implements

impacts

Level 1 Level 2 Level 3

Data Model in Polarion - Complete


Custom Wiki Page ( replaced „Home“ page for some „Spaces“)

Custom LiveDoc( contains Feature, Specification Text , Requirements, Test Cases – found automatically/linked toRequirements)

Customization of Documents


LiveDoc

Space „Home“

Features are grouped into collections known as “feature sets”.

“Feature Set” is a work item in Polarion. It is linked to multiple “Feature” work items.

Each „Space“ - is one „Feature Set“. Home page of Space is programmed to display all info aboutFeature Set: linked Features, Test Cases and latest Test Results.

How FDD maps onto PolarionFeature Set


The FDD process includes:


- Plan by feature

- Design by feature

FeatureSet and Features – organized as Documents


Feature Set

Related Test Cases and Test Results



- Plan by feature

- Design by feature

Plan by FeatureThe FDD process includes:


- Plan by feature

- Design by feature

By Definition: A feature is a small, client valued function that can be implemented in two weeks.

Plans are based on Features +ChangeRequest, +Issue


Design by Feature

Polarion LiveDoc exists for each Feature.

It contains:- Embedded Feature work item- Chapter „Specification“ with list of Requirements for this Feature- Chapter „Design“ describing the software design- Chapter „Testing“ with list of TestCases



- Plan by feature

- Design by feature


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)



- Plan by feature

- Design by feature

Numbers for „TM5“ project:• Total: 6.400 work items

• 40 Spaces

• 400 Documents

• 120 users

Facts & Figures

Polarion Performance = Good (no problem with speed)


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


- FDD development model was chosen for our SW Development project- Polarion was chosen as ALM Platform (for managing Requrements, Specifications, Tests, Plans, Reports,

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

- 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)


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.

Lessons learned


Our Advice…

- Polarion solved Linking & Traceability, because it is integrated tool/technology inside Polarion- Reporting was good after a bit of customization- Workflows, Custom Fields , Views allowed to quicky implement FDD process

Polarion – from First Steps to Success

What we added(some small ideas)


What we added – Team CalendarThe „Team Calendar“ consists of:• new Work Item type in Polarion• Wiki page to display scheduled WorkItems


What we added – Release Note

SVN

WorkItem „BuildRecord“

Jenkins

Info: • Version• Location• Result_StaticCodeAnalysis• Result_TestSmoke• Related Sprints

BinaryImage

1

2

3

45

ReleaseNote 1.1.5


What we added – Release Note

SVN

WorkItem „BuildRecord“

Jenkins

Info: • Version• Location• Result_StaticCodeAnalysis• Result_TestSmoke• Related Sprints

BinaryImage

1

2

3

45

ReleaseNote 1.1.5


Release Note contains:

• Info about software build – Version/Tag

• Link to Jenkins and Jenkins job ID

• Test runs and test results for this build

• „Missing“ test cases

• Features/Requirements/Tasks/Issues for this build

• Static Code Analisys data

Release Note helps to analyse Test Results, done in different TestRuns for the same Build Record


What we added – AutoDocWikiPagesPolarion

The „Auto Documentation of Wiki pages“ consists of:• Each Wiki page has Description (in source code)

and screenshot of the page (as attachement)• Wiki page to display list of all Wiki pages, extract

the Description and screenshot of the page

„AutoDocWikiPagesPolarion“

You can:• See Overview of your wiki pages (total number,

status, comments, ToDos, etc)• See examples (screenshots) and be able to

compare and choose the right report for yourneeds

Use Case : 400 Documents in project• Increased maintenance complexity• Questions came: what is located where, what

is the description, what is the status

What we added – Meeting Minutes


The „Meeting Minutes“ consists of:• new Work Item type in Polarion• Wiki page to display Meeting Minutes

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

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

Thank you!Questions & Answers

http://www.garantis.solutions/alm4you