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

Transcription

1 Presentation Title: Vorwerk: Modern Times, Polarion ALM and Teamcenter for an IoT Product (presented by GARANTIS IT Solutions) Presenter Name: Konstantin Klioutchinski Room name: Nizza Presentation date: 24th October 2017 Company Name: Contacts: Web: GARANTIS IT Solutions Ltd.

2 // // About Garantis IT Solutions IT company providing consultancy services for Polarion ALM Based in Berlin, Germany and in Reading, UK. 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 More useful info for you : (Downloads, Blog, WhitePapers, Analysis Reports, Extensions for Polarion) Web: info@garantis.solutions

3 Agenda Case Study about: Managing System + + Mechanic + Electronic Development Project(s) for kitchen appliance Thermomix using Polarion for other Products as Corporate Standard Key words: Embedded with Internet Of Things technology Agenda You will get insight into the How it all started why IoT? requirements management, planning & execution common challenges we faced solution chosen, strategies applied lessons learned and experience gained summary of success and savings achieved

4 Photo from movie Back to the Future 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

5 Generations of Thermomix The Thermomix is a kitchen appliance made by the Corporate Group Vorwerk. more more Features more Complexity TM5 Thermomix provides 12 functions: steaming emulsifying blending precise heating mixing milling whipping kneading chopping weighing grinding time stirring + internet

6 Thermomix TM5 Eco System

7 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 Manual Cooking Polarion was chosen as ALM tool Customization was done for FDD Guided WiFi Cooking Connection User Interaction Cloud Recipe Synchronization Recipe Chip Features define functionality of Thermomix

8 Project Scope (2016) Adding IoT functionality to Thermomix.

9 Why Polarion for TM5 Project? Polarion allows: 1. Traceability by Linking Work Items 2. Requirements Management 3. Specification & Design Documents 4. Change & Configuration Management SVN, Commit Comments link to Work Items automaticaly 5. Test and Quality Management 6. Issue & Risk Management 7. Audit & Metrics, Reports 8. 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 verify impact depends

10 Feature Driven Development (2016) What is the next great Idea? 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 Conceptual Design Reflection in Polarion Great Idea Description Specification Implementation Stakeholder SW Architects & Requirements Engineers SW Development

11 Project Data Model in Polarion (2016) impacts specify specify depend auto-create depend 1:N verify 1:N verify implements Level 1 Level 2 Level 3 Change Type To

12 Data Model in Polarion - Core Work Items (2016) specify depend specify depend Space Work Item + LiveDoc Work Item(s) embedded in LiveDoc Embedded Work Item Embedded Work Items Text Wiki

13 The FDD process includes: - Build feature list - Plan by feature - Design by feature How FDD maps onto Polarion Work Item Feature Set linked to multiple work items Feature Plans based on Features & Tasks (+ChangeRequest, +Issue) Design is described in Live Documents Test Runs are formed from test cases linked to Features

14 1 year ago in 2016 We had 1 project We used about 60% of Polarion features We assumed it was COMPLEX Feature Driven Development (FDD) approach to accelerate development of software for the Thermomix TM5 product PLM Europe 2016 in Berlin - PRESENTATION (PDF, 2MB) Polarion was used to describe PART of the

15 Now in : 2017: We have many projects for many products We had 1 project We used about 60% of Polarion features We thought it was COMPLEX We use about 90% of Polarion features Maybe it is COMPLEX but we want to GO FORWARD to the Digital Factory concept

16 From ONE project to CORPORATE STANDART EXPAND

17 GROWTH of projects HISTORY: From 1 project to many From Project we moved to: System Electronics projects (1) We started here: FDD for IoT functionality of Thermomix SYSTEM (2) Now we are moving towards - Complete Thermomix product to be described in Polarion: System Electronics Electronics

18 GROWTH of projects Reuse predefined templates for different PRODUCTs SYSTEM Electronics System Electronics System Electronics System Electronics System Electronics System Electronics

19 Our Journey Template for any PRODUCT SYSTEM System Electronics 1 FDD project to develope IoT technology for Thermomix 2 We developed set of TEMPLATES for complete PRODUCT FDD for IoT Electronics 3 More projects started to use Polarion and TEMPLATE 4 EVALUATION of integration Polarion + Teamcenter System Electronics System Electronics System Electronics System Electronics

20 Project Data Model in Polarion Template for any PRODUCT SYSTEM Electronics SYSTEM Electronics

21 Testing of Universal Components Universal Component TESTING project 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 System Electronics System Electronics System Electronics System Electronics

22 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

23 Challenges Release Management across sub-projects How to keep track of Releases of Hardware (HW), Firmware (FW), (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 Electronics // //

24 Customization of Polarion how much you need? Customization Our estimation of Customization small medium high Workitems Workflows (+) Documents TestCases Custom Fields Views (+) TestRuns Plans Wiki pages/reports Spaces (home pages) 60% Standard 40% Customization

25 What kind of change requests we process TYPE OF WORK (most common): 1. Configuration 2. Scripting 3. Report Pages 4. User Management 5. Server Maintenance Types of user requests over time

26 Types of user requests over time TYPE OF WORK: The Polarion server was running on old version of Windows. It needed to be upgraded to completely new Windows and new version of Polarion. Scripting for Report Pages Regular Peak of work every 2 weeks after visiting customer and discussing requirements Configuration (workitems, workflows, etc ) Regular Peak of work every 2 weeks after visiting customer and discussing requirements Server Maintenance Sporadic ativities during upgrades Graph shows number of created requests per week

27 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

28 BALANCE 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 ($$) CREATIVITY DISCIPLINE MAINTENCE Improvements Proposals Ideas Special ways of working Process changes Folow the RULES Obey the PROCESS Try to Adapt not to CHANGE Optimal Customization & Development Training & Documentation Support & Updates/Fixes How Robust are new/special PROCESSES / Functions? Too Little Too Much Optimal modifications / customizations

29 Polarion from First Steps to Success Common Challenges (before introducing Polarion) - 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 Strategies Applied - 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 Benefits and Success - 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 Customization at Vorwerk (presented by GARANTIS IT Solutions), Konstantin Klioutchinski, GARANTIS IT Solutions Ltd., Slide #19

30 ADVICE: from First Steps to Success Our Advice (2016) still VALID 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 (2017) Performance review & optimization Regular backups, data integrity checks => keep system healthy Regular Upgrades

31 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 Electronics System Electronics

32 Managing Polarion Requests workitem Simple Workflow All requests/changes for Polarion are DOCUMENTED Can ANALYSE what is going on in the projects (Change Management) FUTURE IMPROVEMENTS GARANTIS is working on ITIL Template for Polarion

33 Integration ALM+PLM Questions and Experiences from real project at Vorwerk

34 ALM + PLM Template for any PRODUCT SYSTEM System Electronics 1 FDD project to develope IoT technology for Thermomix 2 We developed set of TEMPLATES for complete PRODUCT Electronics 3 More projects started to use Polarion and TEMPLATE Our NEXT STEP 4 EVALUATION of integration Polarion + Teamcenter System Electronics System Electronics System Electronics System Electronics

35 What we want to achieve Template for any PRODUCT SYSTEM Electronics SYSTEM?

36 Technichally it is getting Better-and-Better

37 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, customized Reports, and offers LiveDoc TEAMCENTER is powerful in CAD, Material Management, BOM, etc.

38 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, customized Reports, and offers LiveDoc Our Choice TEAMCENTER is powerful in CAD, Material Management, BOM, etc.

39 Where to Store What our point of view Use Case System Requirement Mechanic Requirement Requirement Design Test Electronic Requirement Electronic Design Electronic Test Mechanic Requirement Mechanic Design Mechanic Test

40 Best configuration for Integration TODAY BEST INTEGRATION v1.3.0 = Polarion ALM 17 + Active Workspace Siemens Teamcenter 11.3 (today) * only in Active Workspace can work with Links

41 // // Thank you! Questions & Answers More useful info for you : (Downloads, Blog, WhitePapers, Analysis Reports, Extensions for Polarion)

42 ITIL template in Polarion for Ticket System projects Almost in every company there is a need for a Ticket System to process requests/complaints/bug reports/problem reports from the field (from clients). GARANTIS is working on development of ITIL Template for Polarion ALM Incident Management Change Management: Service Request Change Management: Change Orders ITIL, formally an acronym for Information Technology Infrastructure Library ITIL describes processes, procedures, tasks, and checklists which can be applied by an organization for establishing integration with the organization's strategy, delivering value, and maintaining a minimum level of competency. It allows the organization to establish a baseline from which it can plan, implement, and measure. It is used to demonstrate compliance and to measure improvement. (from Wikipedia)

43 New project Polarion Project Maintenance Work Items: Requirement requirements to Polarion projects Task tasks are bigger than Polarion Request Polarion Request requests from user to make some changes in Polarion Issue report something is not working Topix - News & Announcements - Page in Polarion describes a wikipage (report) Test Case test to check some special functionality (script, extension usually after upgrade)

44 Managing Report Pages SITUATION: Many report pages were created across different projects. Some reports were similar, some had some small changes. Problem was to update the report pages across different projects, and not to forget some of the projects/pages. SOLUTION: Created special work item Page in Polarion, which stores links to all related Pages. The Page contains link (reference) to the workitems. There is special report page, which shows wich workitem Page in Polaion is linked to which page, and also shows additional information (Status, picture preview of the page, responsible person)

45 AutoDocWikiPagesPolarion Overview of ALL pages + Info To find pages across projects To identify similar pages To filter by Status of Page, other fields Count Page Visits To identify pages used very often To identify page Not used anymore => move to Archive

46 AutoDocWikiPagesPolarion Use Case : 400 Documents in project Increased maintenance complexity Questions came: what is located where, what is the description, what is the status 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 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 your needs