PLMWorkgroupMainMeetingsMay25052010 < Main

This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

TWiki>

Main Web>PlmHome>PLMWorkgroupMainMeetingsMay25052010 (25 May 2010, GrayBachelor) (raw view)

-- Main.GrayBachelor - 14 May 2010

*PLM Workgroup Main Meeting -* *May 25* *th 2010 11am Eastern Time /5pm CET*

*Agenda:*

   1 Roll call and brief introductions- welcome new members
   1 Objective for today's meeting - Scenario walkthrough
   1 Focus on the Systems Engineering scenario to build up use-cases [[PlmSystemsEngineeringScenarioSystemsEngineerReactstoChangedRequirements][here]]
   1 Capture comments and views about existing Specs
   1 Discuss next steps
*Attendees:* <br />Rainer Ersch<br />Scott Bosworth<br />Gray Bachelor<br />Brenda Ellis<br />Mike Loeffler<br />Steve Speicher<br />Roch Bertucat<br /><br /> *Proceeedings:* <br />The meeting followed the published agenda with a focus on the selected SE Scenario and walkthrough<br /><br />The working files are posted on the wiki in the meeting minutes and in the scenario <br /><br /> *Notes taken relating to the scenario* <br />a1: Identification of org/owner/system of initerest (OOS for now). Can assist the assignment of context or phase the assignment to reduce looping<br />a2:URL is the generalized way to access<br />a3: Goal is re-uabaility of req. Context is system architecture, product, feature, version, configuration, effectivity, option and variant. Need to confirm that the CR is in the correct context<br />a4: Open the Req in context<br />a5: Context owns the LC of the system or product, create a revision for the context. More likely to select another existing requirement that is a better initial fit ? Have to open to make a change / make a version and CO. "New revision of the Req Context and check out "<br />a6: Req context open for edit<br />a7: Req in Context in Context and its Implement &gt; Req, aloocateed to behaviors, physical implemntation. Locate, search whatever altrnatives<br />Reursive<br />a1: Fix loose ends. e..g Behaviour same but different Physical iimplemented like connection. Can make change directly ia a CR to sub-teem. Child CR in orig Context. Option to add a new Req, may need a review.<br />a2. Approvals typically build up from the sub-teams with negotiation and collaborate between. Interrogate ? Calibration values (ESW Configuration)<br /><br /> *ACTIONS* <br /><br />1. Mike to share his topcased working file set<br />2. Gray to make updates to Activity diagram based upon   <br />3. Reminder to add the required covenant statements to the wiki<br />

Attachments

Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
ppt	Activity_diagram_anotation_V0.2.ppt	manage	188.5 K	25 May 2010 - 17:21	GrayBachelor	Working mark up of Activity diagram
pdf	OSLC_PLM_Workgroup_May_25_2010_V0.3.pdf	manage	69.7 K	25 May 2010 - 14:36	GrayBachelor	Today workinmg material

Topic revision: r5 - 25 May 2010 - 17:21:36 - GrayBachelor

Main

Webs
Main
Sandbox
TWiki

Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback