OSLC Embedded Systems User Group Charter

OSLC ES User Group Charter - Required

• name of User Group- Embedded Systems

• purpose and scope of User Group (e.g. embedded systems: model based analysis and test; tool integration framework for HW/SW co-design)- We adopt the broadest scope of Embedded Systems to cover all its application domains &

development phases. - We recognising however the need to split this user group to more focused groups as needs

and interests of other OSLC User Groups develop. The scope of this User Group will hence be narrowed down in the course of its initial meetings.

- In particular, we will align this User Group with the other new ALM/PLM User Group being formed.

• Founding members (minimum 3 organizations)- The following members have offered their support for the creation of the “Embedded

Systems” OSLC User Group, and stated that they wish to be a Supporting Entity at launch• The Royal Institute of Technology - KTH (Prof. Martin Törngren)• Siemens Corporate Technology (Rainer Ersch) • Atego (Hedley Apperly) • Creative Intellect Consulting Ltd (Bola Rotibi)

OSLC ES User Group Charter - Required

• Initial Leader- Jad El-khoury (KTH)- The user group intends to put the group leadership for a vote within the first

3 months from launch.

• Liaison relationships (if any, e.g. EU projects)- The founding members have active participation in the following projects of

relevance to this group:• EU project iFEST - http://www.artemis-ifest.eu • EU project MBAT - http://www.mbat-artemis.eu • EU project Crystal (Kickoff on May 2nd, 2013)• EIT ICT LABS activity CPSE (http://www.fortiss.org/en/cpse) • INCOSE

• Clear statement that the User Group will not generate any patentable materials- the User Group will not generate any patentable materials

OSLC ES User Group Charter - Optional

• Examples of potential user stories/use cases/scenarios- One of the first activities of the User Group would be to identify use cases and

scenarios.

• OSLC specifications that may be related- ALM-PLM Interoperability- Architecture Management- Automation- Change Management- Requirements Management

• Potential additional events

• Proposed meeting frequency- The group will meet on a bi-weekly basis, for 1hr meeting.

• Why the StC should accept the proposal