Product Line Working Group Charter

Similar documents
INCOSE Tool Integration and Model Lifecycle Management Working Group Charter

1.5 Model based Conceptual Design

INCOSE Principles. Approved 12 July 2015

INCOSE Healthcare Working Group Charter

Healthcare Working Group Charter

PURPOSE GOAL. management. approaches. a. members, people who

INCOSE MBSE Patterns Working Group Charter

Selftestengine COBIT5 36q

A MODEL BASED SYSTEMS ENGINEERING PROCESSES DEPLOYMENT FRAMEWORK

Braindumps COBIT5 50q

Architecture Practice: a fundamental discipline for information systems

Dragon1 Official Statement

SOA Maturity Model - Guiding and Accelerating SOA Success. An Oracle White Paper September 2008

Wipro s PLM Harmonization Framework for Successful M&A

An overview of The Open Group's Enterprise Architecture and Evolution of IT4IT

A Proposed Community Roadmap for Advancing the Practice of Model-Based Systems Engineering in Government Programs and Enterprises

Five Guiding Principles of a Successful Center of Excellence

ADVANCED ASSET HEALTH MANAGEMENT FOR EFFECTIVE MAINTENANCE AND ASSET REPLACEMENT PLANNING

A Systems Process Lifecycle Standard for Very Small Entities: Development and Pilot Trials

AASHTO Guide for Enterprise Risk Management: An Overview. Tim Henkel, Assistant Commissioner, Mn DOT NCHRP Project 08-93

COMPARISON CHART OF CWG-IG CHARTER AND REVISED CCWG-IG CHARTER

Strategic Asset Management Plan

WEBINARS. Model Based Requirements Engineering (MBRE) Tuesday, 06 February 2018

The Method Framework for Engineering System Architectures (MFESA)

Flexible Analytics for Management of Grid Assets. J.-L. COULLON Alstom Grid France

Boost Your Skills with On-Site Courses Tailored to Your Needs

Research and Innovation Roadmap Call for Tender Appendix I Statement of Work

Program Lifecycle Methodology Version 1.7

TEC-103: Standards October 20, 2017

Step 2: Analyze Stakeholders/Drivers and Define the Target Business Strategy

Systems Engineering Concept

WAPP Integration and Technical Assistance Project

Iasa Engagements enhance Corporate Membership

Model Based Systems Engineering The State of the Nation

Making SOA Mature: BIAN Helps Credit Suisse to Improve Its IT Series of Webinars offered by Banking Industry Architecture Network (BIAN)

CGEIT Certification Job Practice

TOPIC DESCRIPTION SUPPLEMENT for the SYSTEMS ENGINEERING SURVEY DESCRIPTION

Hidden Impacts of Producibility on System Affordability and Design- Manufacturing Interdependence

MID-TERM REVIEW OF TRANSPARENCY INTERNATIONAL S 2020 STRATEGY

E2E220. SAP Test Management Overview COURSE OUTLINE. Course Version: 17 Course Duration: 3 Day(s)

Designing Systems Engineering Profiles for VSEs

Enterprise Risk Management Aligning Risk with Strategy and Performance COSO ERM Framework Update

Flexible Analytics for Management of Grid Assets

SharePoint- Not Really an IT Project. Richard Machanoff Machanoff CIO Services

Establishing Architecture for Large Enterprise Solutions in Agile Environment

CHAPTER 2: IMPLEMENTATION PHASES AND OFFERINGS

Operational Improvement Consulting. SDL Language Solutions

A Three-tier Knowledge Management Scheme for C2 Software Engineering Support and Innovation (CCRTS Paper #C-064)

Information Systems Development

Product Documentation SAP Business ByDesign February Business Configuration

Survival guide to PACBASE end-of-life

Methodological approaches based on business rules

Healthcare

Does your organization Establish Career Path for all Organizational Project Management Roles"?

Improving Acquisition in Government Requirements Management Leading Practices: CMMI-ACQ Visualization

Intermediate Systems Acquisition Course. Lesson 2.11 Program Approval ADE-2. Program Approval ADE-2

Demystifying the Worlds of M&S and MBSE

Project Plan. CxOne Guide

IEEE SoSE Conference, 2018

Livestock Emergency Guidelines and Standards: Raising Awareness, Ensuring Uptake

CSA Security as a Service Working Group Charter

PART 1: INTRODUCTION. Purpose of the BIZBOK Guide. What is Business Architecture?

Training and Consulting

The Open Group Exam OG0-091 TOGAF 9 Part 1 Version: 7.0 [ Total Questions: 234 ]

Enterprise Architecture Development and Implementation Engagements Process

Primary control - description of main technical and design characteristics

Services Description. Transformation and Plan Services. Business Transformation and Plan Services

IBM United States Announcement , dated March 11, 2008

copyright Value Chain Group all rights reserved

PMO In A Box. Prepared for UBS

Enterprise Architecture: an ideal discipline for use in Supply Chain Management

Progressive Value Generation. Application Management. Siemens IT Solutions and Services

Ice s

Architecture Practice Study for C4I Systems Development

Requirements Analysis and Design Definition. Chapter Study Group Learning Materials

Guidelines for SCM Theses

Career Renewal Ministry St. Anne Church. Comprehensive Preparation for a Successful Job Search

Design for Manufacturing Integration Ontologies and Analysis in Computer Aided Designing

Anti-Bot Working Group. Charter

ICANN Strategic Planning Issues Paper September 2005

It s about your success

EXECUTIVE SUMMARY 1. RECOMMENDATION FOR ACTION

The Network of Centers for Very Small Entities (VSEs) Suzhou, China May 26th, 2016 ISO/IEC JTC 1/SC 7- Working Group 24

Copyright 2004 John Koenig All Rights Reserved

Hospital Accountability Planning Submission (HAPS) Frequently Asked Questions (FAQ)

IBM WebSphere Service Registry and Repository V6.1 optimizes the business value of SOA governance

Iasa Architect Readiness Training. Building Partner Capability

Today s customer experience goes beyond borders. Do you have the world covered?

Bridging the Gap Between Governance and Agility. Mario E. Moreira

Using CMMI with Defense Acquisition

The RIS3 Self Assessment Key

Past and future of OMG s Manufacturing Technology and Industrial Systems DTF

SE Effectiveness Leading Indicators. Garry Roedler

Managing Trust in Models

Leo Slegers (ING), Guy Rackham(BIAN), Hans Tesselaar (BIAN) BIAN Introduction Webinar, July 20, Datum, Referent

DOD PARTICIPATION WORKING GROUPS IN NATO NSA/NCS VOLUME 1

MBA BADM559 Enterprise IT Governance 12/15/2008. Enterprise Architecture is a holistic view of an enterprise s processes, information and

Project Stakeholders Management. Unit 13

Question Paper Solution (75:25), April 2015 Subject : Software Project Management

Quality Assurance for Systems Engineering (INSE 6280/2-WW)

Transcription:

1 PURPOSE To promote Product Lines Organization and the best related Systems Engineering practices. In the industry, Systems are more and more often developed to address multiple needs, promoting the reuse of existing components or existing know how. Setting up new Systems Engineering practices specific to the Product Line Management is being currently generalized. This generalization does not mean that it is systematically profitable. The Systems Engineering Processes must be adapted to the Product Lines Organization in order to meet the best efficiency. 2 GOAL The main goals of the Product Lines International (PL IWG) are: 1. To share experience, good practices and traps to avoid. 2. To acquire Know How, comparing State of Art. 3. To help setup and evolve Product Lines in the Enterprises. 4. To grow the membership of the PL IWG. 5. To provide a professional service to our members through outstanding administration. 3 SCOPE 3.1 PRODUCT LINES SCOPE Product Lines encompass: All types of Systems: in a single system production or in mass production, with a few or a lot of variabilities, All types of Market: Needs driven by the market, captured through Market analysis, Very specific needs specified by one Customer; All types of Organization: Domain development : systems developed with self funding (investment), to be reused and to meet future needs, Application development for one Customer, then assets Capitalization to be reused; All the Processes : whatever the System Engineering Processes, whatever the System Engineering Artifacts (needs, requirements, architecture, integration and tests ), All the maturity levels of the Product Line Organization: from Opportunistic practices, through a completely Integrated and Anticipated one INCOSE Product Line Charter draft 4 th of March, 2013 page 1 of 7

3.2 SCOPE OF THIS EFFORT Potentially, the Product Lines encompasses all the System Engineering processes and methods, all the System Engineering Artifacts (needs, requirements, architecture, integration and tests, plan ): Technical processes, Management processes, Support and enabling processes, Modeling. But only the processes and methods specific to Products Lines are in the scope, which can be defined as the tailored standard processes adapted to the Product Lines Life cycle. 3.3 SCOPE OF WORKS The results of the survey conducted in Jacksonville at the end of January 2013 show: 1. A strong interest for the AFIS Product Lines Handbook which needs to be translated into English, 2. An interest for a lot of topics among technical processes, management processes and modeling: The topics proposed for this survey were the main chapters of the AFIS Product Lines Handbook (AFIS is the French chapter of INCOSE). The questions were: 1. On what topic do you want to work: results in blue bars 2. On what topic have you some experience to share: results on red bars This survey will to be will be carried out again when the PL IWG will be set up with more members (only 8 forms filled at Jacksonville) and mainly when the topics will be better targeted with the help of the AFIS Product Lines Handbook translation. INCOSE Product Line Charter draft 4 th of March, 2013 page 2 of 7

4 SKILLS AND EXPERTISE REQUIRED Implementing a Product Line needs to have a good knowledge of Systems Engineering standard practices. It is not the purpose of the PL IWG to explain / explicit the INCOSE SE Handbook. For the future works it is needed to have people having a good knowledge of: The notion of process maturity level (as defined by the SEI). The ISO works on ISO 2655x standards. The OMG works on the CVL standard (already participating in the AFIS WG). 5 MEMBERS, ROLES AND RESPONSIBILITIES As decided at Jacksonville, the leader of the PL IWG is Alain Le Put (also leader of the French PL WG). The other roles and responsibilities will be defined and assigned when the PL IWG will grow up. 6 OUTCOMES (PRODUCTS/SERVICES) The main outputs for the period are: The AFIS Product Lines Handbook transalated into English. A Share working space on the INCOSE web site. The list of PL IWG members. The list and the roadmap of PL works at the IWG level and others WG level. INCOSE Product Line Charter draft 4 th of March, 2013 page 3 of 7

7 APPROACH 7.1 PRIORITY TASK As stated during the Jacksonville workshop held on the 28th of January, 2013, the first main task is to translate into English the AFIS Product Lines Handbook. The requirements for this translation are: Get a technical paper of good quality (i.e. translated by a domain expert). Get a good quality English document (i.e. corrected by a native English speaking people). Ensure the full consistency with the ISO standard not only in the glossary, but all along the document. Ensure the translation of all the pictures. Having the index and the cross references. The AFIS Product Lines Handbook results from the French Chapter works, it addressed the three first goals: 1. To share experience, good practices and traps to avoid as it results from 30 meetings between miscellaneous AFIS PL WG members from the industry and research. 2. To acquire Know How, comparing State of Art as it is the synthesis of the know how of these members 3. To help setup and evolve Product Lines in the Enterprises as it proposes recommendations to build one s own strategy. 7.2 FIRST EXCHANGES BETWEEN PL IWG MEMBERS When this Handbook will be translated and distributed to the PL IWG, it will enable a high level exchange between its members and will permit to identify needs of complements that could be brought up by the members. The way to share information is to be defined, it could be a wiki to post questions and answers and mainly to add return of experience; live meetings could be necessary. 7.3 FUTURE TASKS After a common vision of PLs will have arisen from these first exchanges, a new survey will be carried out to focus the PL IWG works on specific topics of common interest. INCOSE Product Line Charter draft 4 th of March, 2013 page 4 of 7

7.4 GENERAL ORGANIZATION We may have at the same time: Common works at the PL IWG level. Specific works at the chapter level, for instance the AFIS WG will continue to work on its own targets. INCOSE Chapter Local T2.1 INCOSE International T0.1 Global T0.2 AFIS Local INCOSE Chapter Local T3.1 T3.2 T1.1 T1.2 So, it is very important: To let the chapters to decide specific works, and to validate their work products. organize the synchronization and to ensure the consistency between works: to avoid parallel works and loss of energy, and to ease PL IWG members to work on specific topics even if they are not conducted at the IWG level or in their local chapter. To share the results To achieve this: One common detailed list of tasks and associated work products is to be set, updated and made available at the IWG level. Main results are to be published at the IWG level (or at least to be announced and presented, in the case of results published locally in a non English native language, for awareness and possible translation if necessary). 7.5 MAIN RISKS The translation of the AFIS Product Lines Handbook is the main risk for this PL IWG: It is a long and costly task. It is a prerequisite to launch other works. INCOSE Product Line Charter draft 4 th of March, 2013 page 5 of 7

8 MEASURES OF SUCCESS The main measure will be the availability date of the AFIS Product Lines Handbook turned into English (goals 1 to 3). Measures of success for the goal 4 are: Size of membership. Number of enterprises involved in the project. Measures of success for the goal 5 are: Availability date of the Share working space on the INCOSE web site. Availability of the list of PL IWG members. Availability of the list of PL works at the IWG level and others WG level. 9 RESOURCE REQUIREMENTS Resources needed from INCOSE are: Funding for the translation the AFIS Product Lines Handbook. Web site for sharing data. Microsoft live meetings. Services are needed from INCOSE for: Promoting the PL IWG works. Committing new members (and the involvement of other INCOSE chapters). Establishing relationship with the ISO and eventually the SEI. 10 DURATION Typically, the duration of this PL IWG could be long and needs this charter to be renewed at least every year. This first version of the charter applies only on 2013. 11 SIGNATURES Established by Alain Le Put, on the 4 th of March, 2013 1 st Level of Approval Technical Director, INCOSE Date 2 nd Level of Approval (Note this will be added by the INCOSE Technical Director when deemed appropriate.) Chairman, INCOSE Board of Directors Date INCOSE Product Line Charter draft 4 th of March, 2013 page 6 of 7

12 REVISION HISTORY Date Revision Description Author 03/04/2013 0.0 Initial Draft Alain Le Put INCOSE Product Line Charter draft 4 th of March, 2013 page 7 of 7