1 / 10

OSLC ES User Group

OSLC ES User Group. Telco – 10 April 2013. Agenda. Attendees : Andreas Korff ( Atego ), Hedely , Frederic, Rainer, Jad Quick recall from last telco Decide on regular meetings & frequency ES User Group Charter – Finalize & approve Define high level UC Actions list.

diane
Download Presentation

OSLC ES User Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSLC ES User Group Telco – 10 April 2013

  2. Agenda • Attendees: Andreas Korff (Atego), Hedely, Frederic, Rainer, Jad • Quick recall from last telco • Decide on regular meetings & frequency • ES User Group Charter – Finalize & approve • Define high level UC • Actions list

  3. Quick recall from last telco • Timeplan & activities until proposal submission: • Define charter, webpage, interim leader, … • Define 3 parties (KTH, Atego, Siemens) • Establish & meet at our regular meeting points (Bi-weekly?) • Define high level UC (At our very first regular meetings) • Once all in place, invite new members

  4. Decide on regular meetings & frequency • http://www.doodle.com/vppxcwtkcpb4uifa#table • Weekly? Bi-Weekly? • Weekly basis until … • User Group launch [or] • A date [or] • First x Scenarios in place [or] • … • Bi-weekly basis afterwards. • Decision (10th April) • Bi-weekly • Fri 19th April + 3rd May, 10:00 CET • Thursdays, 4 PM CET, starting 16th, … • Duration: 1hr

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

  6. ES User Group Charter - Required • initial leader • Jad El-khoury (KTH) • We intend to re-elect the leader should be up 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 • EU project MBAT • EU project Crystal (Kickoff on May 2nd, 2013) • Xxx - CPSE ICT (Jad/Frederic: Check proper name) • INCOSE • Clear statement that the User Group will not generate any patentable materials • the User Group will not generate any patentable materials

  7. 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 • On bi-weekly,1hr duration … • Why the StC should accept the proposal

  8. Define high level Use Case(s) • Identify/learn how current scenarios are defined in OSLC WG. Examples: • http://open-services.net/wiki/requirements-management/Requirements-Management-Scenarios/ • http://open-services.net/wiki/architecture-management/Use-case-scenarios/ • http://open-services.net/wiki/alm-plm-interoperability/ALM-PLM-Interoperability-scenarios/ • How to proceed? • Reuse iFEST results (soon) • Filter existing scenarios for relevance for this group • …

  9. Define high level Use Case(s) • Discussion 10th April • Atego’s top 3 topics • Model-based development • Product line engineering • Systems of systems • Mission critical systems

  10. Action List • Jad finalizes & sends Charter to Rainer to present to the steering committee • Book regular bi-weekly meetings. • All: signup for an open-services.net account. • Next week agenda • Define high level Use Case(s) • House-keeping stuff (depends if things are in place or not.)

More Related