5.sourcegear

V0.
7March3rd20101OSLCPLMWorkgroupOSLCinActionAnoverviewoftheCMandRMscenariosandspecsMarch3rd2010open-services.
netV0.
7March3rd20102OrganiserstodayWorkgrouplead:RainerErsch,SiemensCoordinator:GrayBachelor,IBMSpeakers:SteveSpeicher,IBMIanGreen,IBMV0.
7March3rd20103AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd20104RollcallPleasestateyourname,organisation,roleIfyouareinthewebconferenceputyourdetailsinachatSendto"All"Ifnotpleasesendanemailtogray_bachelor@uk.
ibm.
comV0.
7March3rd20105AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd201066V0.
7March3rd20107AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd20108CMScopeThegoalofthiseffortistodefineacommonsetofresources,formatsandRESTfulservicesfortheuseinChangeManagementtoolsandusebyALMtools.
ChangeManagement(CM)resourcesdefinethechangerequestsandtasksofthesoftwaredeliverylifecycle.
Theseresourcesinteractrelateandinteractwithmanyotherresources,suchasproject,category,etc.
V0.
7March3rd20109CMParticipantsFormedJan2009,V1.
0specinMay2009ParticipantsIBMTasktopTechnologiesAccentureRallyOracleSourceGearBSDGroupV0.
7March3rd201010CM1.
0ScenariosFindandFixaDefectPlanChangeRequestsinanAgilePlanningToolSetupandconfigurationV0.
7March3rd201011CM1.
0–FindandFixaDefect1.
Abuildisdeployedtoaconfiguredtestmachine(physicalorvirtual)2.
Atestisexecuted1.
Testfails(continue)2.
Testpasses(ifverifyingadefect,closeit.
Otherwisestop)3.
Adefectissubmitted(ChangeRequesttype=defect)4.
Defectistriaged1.
Fixdefect(continue)2.
Don'tfixit(stop)5.
Achangesetisdeliveredtofixthedefect6.
Thebuildexecutes.
1.
Buildpasses(continue)2.
Buildfails(stop)7.
ThebuildIDcapturesthebuildstatus&identifieslinkstoadditionalinformationaboutthebuild(locationofthephysicalbits,theBillOfMaterials).
8.
Teammembersarenotified.
(feeds,monitoringthebuildidetc)1.
ThebuildIDisreferencedalongwiththeBOMtodeterminewhatchangesareincludedinthebuild2.
Startat1V0.
7March3rd201012IdentifyKeyResourcesV0.
7March3rd201013CM1.
0SpecificationsOverviewV0.
7March3rd201014CM2.
0ScenariosStreamlineddevelopertaskmanagementReportingChangeManagementofRequirementsOtherThemesAlignment–corespecCrossdomain–Reporting,RM,SCMPlannedtofinalize2.
0Specs-June2010V0.
7March3rd201015AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd201016RequirementsManagementRemit"Supporteffectiveuseofrequirementsacrossdevelopmentlifecycle""…requirementsofasystemortheoutcomeofsomeprogrammeofwork[…]withoutprejudicetosoftware,hardware,IT,regulatory,businessetc.
"PrinciplesandapproachOpen,democratic,cross-disciplineScenarioled,incremental,deliveringvalueLoosecoupling,cohesive,extensibleV0.
7March3rd201017RMWorkgroupFormedQ109/firstcall5thMayParticipationAccentureCitigroupEADSN.
V.
IntegrateSystemsEngineeringIBMNorthrop-GrummanCorp.
SiemensAGStoneworksRavenflowV0.
7March3rd201018RMActivitiesScenariodevelopmentSourced,articulated,elaborated,documentedCross-disciplineawareness~30scenariosinbacklogScoping&TechnicalanalysisValuetocommunityAlignmentwithbusinessobjectivesFeasibilityProducingspecificationEnoughtosupportneedsGeneralizeacrossdisciplinesWebServiceArchitectureV0.
7March3rd201019RMScenarios2009Requirementsareimplemented,deliveredandvalidatedAchangerequestissatisfiedV0.
7March3rd201020RMScenarioRequirementsareimplemented,validatedanddeliveredPre-conditionsAninterestingcollectionofrequirementshasbeenidentifiedforinclusioninaproduct.
Weassumethattherequirementsprocessiscompleteandtherequirementshavebeenapprovedandplannedforinclusionintheproduct.
Howthatcametobeisnotdealtwithhere.
Scenario:TherequirementsarebrokendownintoimplementationrequestsfortheimplementationoftheproducttosatisfytherequirementsEachrequirementislinkedtooneormoreimplementationrequestsEachimplementationrequestcouldfurtherbebrokendownintosmallerimplementationrequests,eachofwhichislinkedtoitsparent.
TheimplementationrequestsareassignedtoforcompletionAtestplantovalidatetheserequirementsiscreatedThetestplanislinkedtotherequirementsthataretobequalified.
Testcasestovalidateeachrequirementarewrittenandlinkedtoeachrequirementthatistobequalified.
ImplementationrequestsaremarkedascompletedandproductisdeliveredProductgetspickedupbythenextintegrationTheteststepsfromthetestcasesarerunonthenewintegrationIfanyteststepfails,aqualificationchangerequestiscreatedandlinkedtotheteststep.
ResumequalificationuponresolutionofthequalificationchangerequestIfalltestsstepspass,continueLinkscanbeusedtoinspectthecontentoftheintegrationLinksbetweenarequirementandachangerequestcanbeusedtocheckthatarequirementhasbeendeliveredLinksbetweenarequirementandatestcasecanbeusedtocheckthattheimplementationmeetsthatrequirementPost-conditionsTherequirementsaresatisfied(allimplementationrequestscompleted,testcasespassing).
Theresultingintegrationmeetstherequirementsplacedupontheproduct.
V0.
7March3rd201021RM1.
0Specification6documents(30pagesofwiki)DescriptionofresourceformatsDescriptionofbehaviourofthoseresourcesFunctional,Partial&Precisespecs.
WebserviceprotocolsConstrainsserviceproviders(servers)Informsserviceconsumers(clients)Pervasive"lowbar"technology(W3C)V0.
7March3rd201022RMScenarios2010TraceabilityinvestigationsScenarioT1-ArequirementiselaboratedScenarioT2-ArequirementisreviewedScenarioT3-TheimpactofachangeisassessedScenarioT4-RequirementsaretradedScenarioT5-QualificationactivitiesareplannedScenarioT6-QualificationstatusisassessedScenarioT7-AtraceabilityreportisgeneratedScenarioT8-ChangesthataffectarequirementareassessedSimpleRM/AMworkflowRelationshipManagementOtherThemesAlignment–corespecCrossdomain–Reporting,CM,AMPlannedtofinalize2.
0Specs-June2010V0.
7March3rd201023AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd201024HowtoshareexperienceofputtingOSLCSpecsintopracticeinthePLMcontextTheaimistointroduceexamplesofusageinaPLMcontext,whatwouldbeuseful…BusinesscontextandpurposePLMcontextscenarioSystemContextsummaryOSLCSpecusageLessonslearntWhatexamplesareavailableDoweneedtoestablishsomePLMcontextfirstHowtodothisinpracticeV0.
7March3rd201025AgendaIntroductionRollcallOverviewofWorkgroupwayofworkingScenariosandspecsoverviewChangeManagement(CM)ScenariosandspecsexampleRequirementsManagement(RM)HowtoshareexperienceofusageQ&ASummaryCloseV0.
7March3rd201026ProposednextmeetingsNextmeetingofthePLMWorkgroupProposal:March16that11amEasternAimsActivitiesLogisticsV0.
7March3rd201027Thankyourainer.
ersch@siemens.
comgray_bachelor@uk.
ibm.
comV0.
7March3rd201028HowtokeepintouchOpenservices(OSLC)homehttp://open-services.
net/html/Home.
htmlRegisteronopen-services.
netPlmHomepagehttp://open-services.
net/bin/view/Main/PlmHomeCommunitymailinglisthttp://open-services.
net/html/Community.
htmlPLMWorkgroupmailinglisthttp://open-services.
net/mailman/listinfo/oslc-plm_open-services.
netWikihttp://open-services.
net/bin/view/Main/WebHomeUserListhttp://open-services.
net/bin/view/Main/UserList