Embed Size (px)
Citation preview
AnArtificialEnvironmentforExploringSystemsEngineeringEffectiveness.
FacultyResearchers:RichardTurner,StevensInstitute,PIAliceSmith,AuburnUniversity,Co-PIJeffSmith,AuburnUniversity
StudentResearchers:AuburnUniversity:Gokhan Ozden,Donghuang LiStevensInstitute:RickScarpetti,Lymari CastroUSC:AlexeyTregubov
SoSCIE WebinarDecember6,2016
SSRR2016 2
Agenda
• OverviewandStatus
• Observationsfrominitialprototype
• ExamplesofRefinedDefinitions
• Walkthroughofexample
• Nextsteps
SSRR2016 3
Agile/LeanSE
• In2011,theICidentified4criticalproblemstotheSERC:1. IneffectivenessofIMS/IMPswithin
large,evolvingoperationalSoSs2. ScarceSEresourcesinadequateto
supportschedule-drivenprojects3. Decisionsmadelateoratalevel
removedfromthecontext4. Lackofvisibilityintothestatus
ofSoS-widecapabilitydevelopments• SERCpostulatedagile/leanapproachesandadaptivegovernancemechanismsaspossiblesolution
• Twoyearinvestigationdevelopedproposedconcepts
• Issues:―Howtoevaluatevalidity―Howtotransitionknowledge/mechanisms
SSRR2016 4
KeyConcepts
•Pull(kanban)scheduling• Value-basedselection• LimitedWIP• ClassesofService
• SEasaService• Valuenegotiation• Scarceresource-driven• Collaborative/Negotiated
• Integratedworkanddataflow
• Informationradiatorsatalllevels
•Appropriateorganizationalstructures
Capability)Engineering)Individual)Product)Team)
Execu9ve/Stakeholder))Management)(Customer))
SLA$establishment$and$monitoring$Strategic$planning$Capability$priori7za7on$
Dash%
Analyze$needs$and$alterna7ves$$Refine$capabili7es$Develop$requirements$Allocate$requirements$
Form$cross$organiza7onal$teams$Cross@product$and$specialty$engineering$
Validate$and$fully$enable$capabili7es$
Network)Domain)Team)
Pharmacy)Domain)Team)
Users$$$$$$$$$$User)Support)
$
Product/Domain)Engineering)
KSS$
KSS$
Dash%
KSS$
Customer$rela7ons$Ini7al$Triage$
Product$SE$Iden7fy$SW$Features$
Allocate$features$to$SWDT$Integrate$features$into$requirements$
SW)Development)Team$$
Dash%
KSS$
KSS$
KSS$
Dash%
Work$Flow$Visibility$
KSS$
Needs%Backlog*%
*$$All$organiza7ons$can$contribute$to$the$Needs$Backlog$
AMulti-levelNetworkofKanban-basedSchedulingSystems
SSRR2016 5
DemonstrationandAnalysisToolforAdaptiveSEManagement(DATASEM)
• Keyenablerforbothconductandtransitionoftheresearch
• Asimulation-basedresearchinfrastructuretostudy,validate,anddemonstratetodecisionmakersthecosts,benefits,andrisksofadaptiveapproaches
ObjectivesEnable realisticexperiments tounderstandhow governancemodels,organizationalstructuresandworkflowsinteractacrossaSoS• Investigatenewapproachesinawidevarietyofacquisitionanddevelopmentenvironments• Understandtheimplicationsoforganizationswithmixedgovernancemodelsacross
components• ApossiblemeansofmeasuringthevalueofsystemsengineeringProvideaframeworktocalibrateassumptionsofperformance• Builddataforincreasinglysophisticatedexperiments• Resourcecapabilities,teammaturity,turnover• Overheadcosts,complexityofwork,rateofenvironmentalchangeIntegratedexperiment-generationtools thatprovidetheuserwith• Abroadselectionofcalibratedandexperimentalpatternsfororganizationsandgovernance
models• Sophisticatedstochasticsupportforgeneratinglargeworkitemnetworks• Comparisontoothersimilarexperiments• Graphicdemonstrationofbenefit/costtoconvincerisk-aversedecisionmakers
SSRR2016 6
ExperimentDescriptionInfrastructure
• DomainSpecificLanguage: Defineenvironmentalandmanagementcharacteristics―Organizations: Capturesvariousorganizational
structures,includingSoS―Workflows: Definesthetechnicalworktobe
accomplished―Governance: Specifieshowworkisaccomplished
acrossandwithinorganizations
• Implementationinfrastructure: SoftwarelibrariesthatimplementtheDSLmodelsforsimulation―EnablersforexecutingtheDSLsyntaxandsemantics
• Simulationengine(s): Softwarethatperformsandcontrolsthesimulations― InitiallyusingRePast anagent-basedsimulator―Researchshouldgeneratesufficientdatatoadd
othersimulationmodesorspecializedsimulationssuchassystemsdynamicsmodels
R-126deliveredaninitialprototypeofDATASEMinaweb-accessibleandstandaloneeditioninDecember2015.However,...
SSRR2016 7
Status
• InitialprototypewascompletedanddeliveredtothesponsorinDecember2015
• Startof2016workdelayeduntilMarch
• Reviewandvalidationactivities
oftheprototypebytheteamledtoanumberofobservationsandthedecisiontoaddresssomefoundationalissues
• Haverevisedthedefinitionsofmanyofthemodelingstructures―Currentlyundergoingreview―RevisingtheDSLtoalignwiththechanges
―Beginningrevisionofthesoftware
SSRR2016 8
ObservationsfromRT-126(-)andResponsesinRT-152(+)
• Vaguedefinitionsofgovernancestrategiesandmechanisms―Thedefinitionsweremisunderstoodandsoimplementedincorrectly➕Definitionshavebeenupdatedandclarified➕Newdefinitionsbeingreviewedbyindustryandsponsors➕Buildingasetofrealworldscenariosshowinghowmechanismswork
• Interactionoforganization,workandgovernancemodelsandworkflowdefinition―Hadassumed(incorrectly)thatthemodelswereindependent
➕Newdefinitionsandtemplates➕ incorporateinteraction
• DSL―Tensionbetweenelegance,extensibility,andpracticality
➕DSLbeingrevisedbasedonthenewdefinitions
SSRR2016 9
RefinedDefinitionsOrganizationalComponents(OCs)
OCsarecompanies,organizations,teams,individuals,resources– aredefinedaccordingtotheircapabilities,governancemodelsandrelationshipsinadata-richgraph.
EachOChasarequestedworkqueue andanacceptedworkqueue
EachOChas4keyfunctions:AcceptworkallocateResourcesExecuteworkitems,Monitorandreportstatus.
EachOChasaGovernanceModel,definesthescope,concurrenceandactivityofthetechnicalprocessandmanagementmechanisms.
TwotypesofOCsBasic. BasicOCshaveonlyinternalresources.Canrepresenttoolsorspecialequipment(forexampleatestsuiteconfiguration),orindividualstaffresources.Delegating. DelegatingOCsperformworkusinginternalresourcesorbyarrangingtodelegateworkwithexternalOCs ofanytypeTwotypesofrelationshipsintheOCsgraph:Workflowrelationship. Arelationshipthatdefineshowrequestsforworkcanflowbetweenorganizationalcomponents.ThedirectionalityandparametersoftherelationshiparedefinedintheindividualOC’sgovernancemodel.Managementhierarchy. Identifieswheretherearehierarchicalormanagementrelations.EveryOCoperatesaccordingtoagovernancemodel.UnlessagovernancemodelcomponentisspecificallydefinedforanOC,theOCinheritsthecomponentfromitsparentinthehierarchy.
SSRR2016 10
DefinitionsExampleOrganizationGraphs
Multi-teamOrganization
Single-teamOrganization
SSRR2016 11
RefinedDefinitionOCOperation
• Squareboxesshowartifactsordatastructures
• Diamondsshowagents’governancemechanismscomponentsoractivities/functions
SSRR2016 12
RefinedDefinitions:OCSchedulingApproach
• Becausethereisarelationshipbetweenthetechnicalworkdecompositionandschedulingmechanisms,twotypesofschedulingapproachesweredefined
• Thissimplebinarychoiceisaninitialrepresentationofanextendedspectrum
• UsingthePMIdefinitions,wehavedescribedtheapproachesas―Predictive.Workisscheduledfaraheadoftime,batchsizeoftasksisusuallylarge,progressisbasedonthatschedule,andthescheduleisadjustedrarely.
―Adaptive.Workisscheduledcontinuallyorinshortiterations,batchsizesareusuallysmaller,valuemaybeusedtoprioritizework,andflowcontrolsmaybeused.
SSRR2016 13
RefinedDefinitionOrganizationalComponentAcceptanceActivity
Acceptance chooseswhatandhowmanyWIstotakefromtheexternalqueueintotheacceptedqueue.Acceptancecaneitherbetriggeredbyaneventorbycadence.
TheacceptanceprocesshasthefollowingsetofparametersforadaptiveOCs:
Cadence - howoftenacceptanceisperformed
SchedulingMechanism- aninstanceofaschedulingmechanism(e.g.schedule,sprint,kanban-pull,...)
ValueDetermination - thismechanismusesuser-specifiedparameters(e.g.weightsofdifferentcriteria,methodofaggregationofdifferentcriteria,etc.)todeterminethevalueofworkitemsinthequeue
WorkFlowMechanisms– CoSs,WIPlimits.
IfbasicOC
start
Acceptanceforadap-vetechnicalprocesses
end
Accepteverythingfromexternal
queuethatOCcanworkon
(checkWIs’servicesrequiredvs.
OC’sservicesprovided).WIs
requiringservicesnotprovidedin
thisOCarerejected.
Yes
No
ComputevalueforallWIs
fromexternalqueue
(orderthembyimportance
anddependencies)
Value
determinaGon
funcGon
use
ApplyCoSrules
andacceptWIs.
AcceptasmanyWIsasWIP
limitallows.AcceptWIs
withhighervaluefirst.
1
3
2
4
5
ComputecurrentWIPWIP
limituse
IfWIPis
exceededNo
end
Yes
ForallWIsthatrequire
workdecomposiGon,create
analysistasksforwork
decomposiGonandput
thesetasksintoaccepted
queue.
6
IfconGnuous
yes
IfGmer
triggeredNo
yes
end
No
Rules(examples):
-IfWIisExpediteacceptit.
- If WI is DateCertain and
due date is close (e. g.
120%oftheworkesGmate
before the date certain)
changeCoStoExpedite.
Applied before WIP
limits. Only determines
mandatoryacceptance.
Simple WIP. No WIP
limits for different CoS
(futurework).
SimpleWIP.Computeall
WI that were accepted.
A g g re gaGon node s
countasoneWI.
SometypesofWI
requiredecomposiGon.
Forexample:
-Requirementsare
decomposedintoWI.
-Tasksremainthesame.
NotethatactualgeneraGonofconsGtuentWIswill
happenwhenanalysistaskisdone.Moredetailswill
beprovidedonworkexecuGonflowchart.
SSRR2016 14
RefinedDefinitionOrganizationalComponentAcceptanceActivity
TheacceptanceprocesshasthefollowingsetofparametersforpredictiveOCs:• Cadence• Acceptancepolicy towardsnewwork
intheexternalqueue.Currentlytherearethreepoliciesforacceptance:1.Accepteverythingfromexternalqueueandassigntoresourcesinparalleltoalreadyexistingplan.Firsttrytoutilizeavailableresources,andonlythenmultitaskbusyresources.2.Rescheduleeverythingeverytimesomethingnewappearsintheexternalqueue.3.Ignoreexternalqueuebetweenrescheduling.Nomatterwhatacceptancepolicyisused,reschedulingisalsodonewithacertaincadence(everymonth,year,etc.).Reschedulingcadenceisauser-definedparameter.
IfbasicOC
start
Acceptanceforpredic.veprocesses
end
AccepteverythingfromexternalqueuethatOCcanworkon
(checkWIs’servicesrequiredvs.OC’sservicesprovided).WIs
requiringservicesnotprovidedinthisOCarerejected.
Yes
No
AcceptallWIinexternalqueue,donotchange
schedule.
ForallWIsthatrequireworkdecomposiHon,createanalysistasksforworkdecomposiHon
andputthesetasksintoacceptedqueue.
1
3
2
If“accepteverything” If“reschedule
everyHme”
If“ignoreworkbetween
rescheduling”
1 23
AcceptallWIinexternalqueue.
ForallWIsthatrequireworkdecomposiHon,createanalysistasksforworkdecomposiHon
andputthesetasksintoacceptedqueue.
5
4
Createareschedulingtask(anewWI)and
assignittoaresource.
Donothing
IfHmetoupdate
schedule
IfHmetoupdate
scheduleYes Yes
end
NoNo
IfHmetoupdate
schedule
NewWIsinexternalqueue
Yes
No
end
No
Yes
6
7
Simply check if newwork is added to theexternalqueue.
This a special type ofWI. Once reschedulingtask is complete, a newschedule is developedandthenused.
If it is Hme to updatescheduleisdefinedcadence.ThisacHonisdonebyHmer.
SSRR2016 15
RefinedDefinitionsWorkdefinitionandworkflow
• DescribedbyWorkItems(WIs)inaWINetwork(WIN)withmultiplelevelsresemblingatraditionalworkbreakdownstructure(WBS).
• Usersspecifyinformationforthefirstfewlevelsofwork(e.g.capabilities,requirements,workpackages);therestofthenetworkisstochasticallygeneratedusingparametersOCtechnicalapproachandgovernancemodels
• StochasticworkitemdecompositionisperformedwhentheWIisacceptedbyanOC.AWorkDecompositiontaskiscreated.Oncethattaskiscomplete,aWIN-generationalgorithmcreatesanewsetofnodesusingparametersdefinedintheWIandtheOC’sgovernancespecification.
Capabili'es Userrequests
Workdefini'on
AsequenceofworkWIthatappearsinwork
queuesofOCs. Thisisaresultofcapabilitya n a l y s i s t a s k s ,architecture/design tasks,etc. All the tasks thatfurther breaks downworktoWIdoablebyresources.
This isnotaone'meac'on,this is a process (algorithms,governancemechanisms)thatdescribes how work itemsnetworkevolvesover'me.
Work defini'on may requiredifferent inputs depending ongovernancestrategyselected.For example, IMS may requirepar'alplans,KSSNmayrequireworkdecomposi'onrules,andetc.
Capabili'es Userrequests
Workdefini'on
AsequenceofworkWIthatappearsinworkqueuesa<eranalysistasks.
Predic'veExample
Par'alplansforeachcapabilityandprojectlevelrequirement
Capabili'es Userrequests
Workdefini'on
AsequenceofworkWIthatappearsinwork
queuesofOCs.
Adap'veExample
WIgraphdensityrules.Forexample,❑eachcapabilityinto10
requirements,❑eachrequirementinto20
tasks,❑etc.
SSRR2016 16
Example(usingthenewdefinitions)
• Organizationalstructure
SSRR2016 17
Exampleofusingthenewdefinitions(cont-d)
R1
C1
R2 R3
C2 C3
R4
PR1 PR2 PR3 PR5 PR6PR4
Team32FTE
Skills:s3predictive
Ext.QDoneQ
AR M
E
Team24FTE
Skills:s2adaptive
Ext.QDoneQ
AR M
E
SETeam1FTE
Skills:s0adaptive
Ext.QDoneQ
AR M
E
ProcessindependentWIs(inputfromuser,fromDSL)
C1 C2 C3
A01 A02 A03
R1 R2 R3 R4
A04 A05 A06 A07
PR1
PR2 PR3
PR5 PR6
PR4
T1 T2
A11
T3 T4
A21
T5
A22
T6 T7
A23
Team12FTE
Skills:s1,s2adaptive
Ext.QDoneQ
AR M
E
T8
A31
T9 T10
A32 P31
Inheritance–decompositionhierarchyPrecedence(sourceprecedes/causesdestination).
Generatedby(sourcetaskcreatesdestinationtasks,butnotschedulesthem).Onlyforpredictiveprocesses.
Generatedby(sourcetaskcreatesdestinationtasksand/orrelationships).Asourcetasksisadecompositiontask.
T1 T10… TasksgeneratedbyOCs
A01 A32… DecompositiontaskscreatedbyOCs.Thisisgovernanceoverhead.
P31PlanningtaskscreatedbyOCs.Thisisgovernanceoverhead.
WIsintroducedbysimulation
Assigned/delegatedbysimulator
Created bypredictiveprocess
SSRR2016 18
ExampleProcess-independentworkdefinition
C1 C2 C3 R1 R2 R3 R4 PR1 PR2 PR3 PR4 PR5 PR6
Value 40 30 30 20 35 30 15 10 10 35 15 15 15
ValuedistributionforconstituentWIs.
- - - - - - Distributevalueproportionally(divideparent’svalueproportionally).
Estimatedsize 10 10 10 5 5 5 5 2 3 5 2 3 5
Estimatederror 0 0 0 0 0 0 0 0 0 0 0 0 0
Requiredskills S0S1S2
S0S2S3
S0S2S3
S0S1S2
S0S2
S0S2S3
S0S3
S1 S2 S2 S2 S3 S3
DistributionofskillsforconstituentWIs
- - - - - - - S1-100%
S2-100%
S2-100%
S2-100%
S3-100%
S3-100%
Probabilityofchange 0 0 0 0 0 0 0 0 0 0 0 0 0
ConstituentWIsinternalrelationshipscomplexity
- - - - - - - 0-90%1-10%
0-90%1-10%
0-90%1-10%
0-90%1-10%
0-90%1-10%
0-90%1-10%
ConstituentWIsexternalrelationshipscomplexity
- - - - - - - 0-100%
0-100%
0-90%1-10%
0-10%
0-100%
0-100%
Deadline(days) 8 12 20 8 8 12 20 8 8 8 12 12 20
SSRR2016 19
IllustrationComponents
SSRR2016 20
Futurework
• Calibrationandvalidation. DATASEMneedstobevalidatedthroughrigorousexperimentationforsensitivity,andthroughtheuseofrealdatafromdevelopmentorganizationsforimprovedaccuracyandrealism.AnexperimentalvalidationframeworkwascreatedbyForrestShullfromtheSEI.― Validationoftoolindevelopmentandacquisitionenvironments(ongoing)
• Conceptsstilltobeimplementedorfurtherstudied― Valuedeterminationandagreement(ongoing)― Interfaceofpredictiveandadaptivegovernancemechanisms
(beginning)― ExtendDATASEMtoaddressacquisition(ongoing)― Modelhumanbehaviorindecisionmakingandnegotiation
amongcomponentsofasystemofsystems(Notyetbegin)― ConflictsbetweenSoSE andconstituentsystems(notyetbegun)― Negotiationofservicesandcontracts(notyetbegun)― IncorporateDATASEMintotheSEEA(notyetbegun)
• Developuserinterfacefornon-developers. DATASEM’sUIenhancedsoatypicalsystemsengineeringorengineeringmanagercancreateproductsreadilyunderstandablebydecisionmakersandexecutives.― Simplifiedgraphicdesignanddisplayinterface(beginning)
SSRR2016 21
Howyoucanhelp
• Survey-basedreviewversionofthenewmechanismsdefinitionsisavailable
• Link:https://www.surveymonkey.com/r/DATASEM
• Pleasecompletethereviewandsharethelinkwithcolleagueswithinterestinthiswork
• Understandingthecommunity’spreferenceswillhelpusinrefiningandimplementingthedefinitions
SSRR2016 23
Backups
SSRR2016 24
UseScenarioExample(stillbeingdefined)
• Title:SystemsofSystems
• Description: ASystemsofSystemsprojectprovidesopportunitiesforagoodmixofworktobecompletedinhouseandworktobecontractedout,whichisoftennotaneasydecisionforacompanytomake.
• PotentialConsiderations:Workitemvaluecanpotentiallyserveadualpurpose,thefirstbeingthetraditionalsenseofvaluedeliveredtocustomer,buttheworkitemsmayhaveintrinsicvaluetotheOCperformingtheworkifithelpsdevelop/maintaindomainknowledgerelatedtoacorevaluestream.Itmaynotbeinthecompany’slongterminteresttodelegateWI’srelatedtoavaluestreamevenifitenhancesvaluedeliveredintheshortterm. RickScarpetti’s ongoingwork…
SSRR2016 25
Exampleofusingthenewdefinitions(cont-d)
Process-independentworkdefinition(blueWIsonthenextchart)includesthreecapabilities,theirdecompositionintorequirementsandprojectlevelrequirements.TheSEteamdelegatesprojectlevelrequirementstoOCsthatdecomposethemintotasklevelWIs(redWIsonthenextchart).Theworkdecompositionsteps:
• CapabilitiesareallocatedtoSEteam.Simulationengineallocatescapabilities(rootsoftheWIsgraph)basedonrequiredskills.
• CapabilitiesaredecomposedintorequirementsbySEteam.
• RequirementsaredecomposedintoprojectlevelrequirementsbySEteam.
• SEteamdelegatesPRstootherteam,otherteamsdecomposePRsintotasksusingtheirgovernancesettings
SSRR2016 26
Agile(Adaptive)SEgoals
• Identifyagile,lean,andotheradaptiveprocessesandgovernancemechanismstohelpsystemsengineers― Identify,analyzeandquicklyreact toissuesinanenvironmentofacceleratingchange―Keeppacewithevolving requirements,risksandopportunitiesthroughout the
extendeddevelopmentlifecycle―Understandandmanagethechangingeconomicandpoliticalfactorsthatundergird
andenablesystemdevelopment―BroadenSEinfluenceand holistically approach
o Creationandevolutionofsystemsofsystemso Interoperabilitybetweenlegacyandnewcapabilitieso Reductionismresultinginpointsolutionsorlocallyoptimizeddecisions
• Amodelingenvironmenttovalidateandexperimentwith―Adaptivemechanismperformance―TheirinteractionswithmoretraditionalSE―Howtheycanbalanceadaptabilitywithdisciplineinabroadvarietyofenvironments.
• InformorganizationscontemplatingchangestotheirsystemdevelopmentprocessesincomplexsystemorSoS environmentswheredifferentdevelopmentapproachesareappliedconcurrently.
SSRR2016 27
Managementapproachesconsidered
• Adaptive, value-based governancemechanismsthathavebeensuccessfulinsomesoftware,productdevelopment,andmanufacturingenvironments―Value-based pullschedulingatmultiplelevelsthroughouttheorganization―Value-drivencollaboration amongdevelopers,systemsengineers,andstakeholders
―Visibility ofcurrentvalueofworkitemsandstatusthroughouttheSoS―Improvedflow andmorerapiddeliveryofstakeholder-influencedvaluethroughotheragile/leanmechanisms(e.g.,limitedworkinprogress,queuingdisciplines)
• ProvidingSE resourcesascoordinatedandnegotiatedservices
―Value-based negotiatedschedulingofSEserviceslikeallotherworkservices
―Moreeffectiveutilization ofscarceSEresourcesandfewerdelaysduetoSEresponses
SSRR2016 28
RefinedDefinitionValueFunctionMechanism(Example)
SSRR2016 29
RefinedDefinitionOrganizationalComponentRequestingActivity
Adaptive technicalprocessesoftenusemultipleiterationsorincrementswithconstantorchangingcadencestoprovidecontinuousvalueandvalidation.TheymayorderWIsaccordingtosomevalueformulation,orhandleresourceconstraintsduetothechangingenvironmentoftheproject.TheymayenforcebroadClassesofServicethatareusedbyotherOCs,internalWorkInProcesslimits,orothermethodstosupportbetterflow.
start
Reques&ngexecu&on(‘resourcing’,orderingandresourcealloca&on)foradap&veprocesses
ComputevalueforallWIsfromacceptedqueue
(ifvaluefunc7onisnotdefined,considereverythingequallyvaluable)
Valuedetermina7on
func7onuse
AssignacceptedWIstointernalexecu7onifinternallyprovidedservicesandcapacity/throughput
allowdoingthat.
AssignallotheracceptedWIstoexternalexecu7onbyfindingother
lowerlevelOCsthatproviderequiredservices
end
1
2
3
4
ApplyCoSrulesandacceptWIs.
Calledevery7ck/7meframe
WIs remain in theacceptedq u e u e i f r e s o u r c ea s s i g nm e n t w a s n o tsuccessful
Rules(examples):- If WI is Expedite assign it to internalexecu7on(ifpossible)orexternalexecu7on.-IfWIisDateCertainandduedateisclose(e.g.2dayleN)assignittointernalexecu7on(ifpossible)orexternalexecu7on
SSRR2016 30
RefinedDefinitionOrganizationalComponentRequestingActivity
Predictive technicalapproachesusuallygenerate(orobtain)ascheduleandthenexecuteitascloselyaspossible,redevelopingscheduleswhentheyreachsomedefinedlevelofincongruencetoprovideinsightandmakemanagementadjustments.
start
Reques&ngexecu&on(‘resourcing’,orderingandresourcealloca&on)forpredic&veprocesses
Schedule
end
1
2
Checkthefollowingforeachnon-aggrega6ngWIthatwasassignedtothisOCbyschedule:-OChasrequiredskillstoexecuteworkinternally.-dependenciesareresolved-startdateiscloseoralreadypast-internalresourceisavailableorifitisbusycheckifitscapacityallowshimtoacceptaWI.Ifallcondi6onsaresa6sfied,assignWItointernalexecu6on.WIwillbeexecutedbythisOC.
use
Checkthefollowingforeachnon-aggrega6ngWIthatwasassignedtothisOCbutnotbeingexecutedinternally:-lowerlevel(connected)OCshaverequiredskillstoexecutework.-dependenciesareresolved-startdateiscloseoralreadypast
Ifallcondi6onsaresa6sfied,assignWItoexternalexecu6on.
use
Calledevery6ck/6meframeThis ac6on simply reads thescheduleandexecutesitinternally.
This ac6on simply reads thescheduleandexecutesitexternally.
SSRR2016 31
MoreDefinitions…
IfWIscompleteness
orstatusupdated
start
Monitoring
end
UpdateallhigherlevelWIsbyrecalcula9ngtheirproper9es(e.gcompleteness,status,etc.)
Yes
No
ForeachacceptedWIdo:
do
whendone
1
2
3
Updateoutputindictors
4start
Internalworkexecu/on
endForeachWIassignedtointernalexecu4ondo:
UpdateWIcompletenessusingresourceperformanceparameters(capacity,
throughput).
1
2
3
IfWIisadecomposi4onof
workNo
AddnewWIsintoacceptedqueue
GenerateWINfortheassociatedaggrega4ngWI
Schedulingalgorithm
use
WINgenera4onalgorithm
use
Yes
Schedule
Yes
4
Developanewscheduleusingnewandexis4ngWIsandcurrentscheduleif
available
IfWIisareschedulingWI
Schedule asanar4fact.
Any WI that generatesotherWIs (e.g. analysistasks , reschedul ingtasks, etc.). This isdetermined by type oftheWI.
Every analysis/reschedulingtask has a parent, which isanaggrega4ngWI
SSRR2016 32
Publicationsfromthisresearch-1(inorderofpublication)
• Turner,R.andWade,J.(2011)."LeanSystemsEngineeringwithinSystemDesignActivities,"Proceedingsofthe3rdLeanSystemandSoftwareConference,May2-6,2011,LosAngeles,CA.
• Turner,R.;Madachy,R.;Lane,J.A.;Ingold,D.;Levine,L.;“Agile-LeanSoftwareEngineering(ALSE):KanbaninSystemsEngineering,”A013- FinalTechnicalReportSERC-2011-TR-022-1,Dec31,2011.http://serc2cdn1.mannadesignworks.netdna-cdn.com/wp-content/uploads/2014/11/SERC-2011-TR-022-1-Kanban-in-SE-RT-035.pdf
• Turner,R.,Madachy R.,Ingold D.,andLaneJ.,“ImprovingSystemsEngineeringEffectivenessinRapidResponseDevelopmentEnvironments,”ProceedingsoftheInternationalConferenceonSoftwareandSystemProcess2012,2012.
• Turner,R.,Madachy R.,Ingold D.,andLaneJ.,“ModelingKanbanProcessesinSystemsEngineering,”ProceedingsoftheInternationalConferenceonSoftwareandSystemProcess2012,2012.
• Turner,R.,Madachy R.,Ingold D.,andLaneJ.,AndersonD.,“Effectivenessofkanbanapproachesinsystemsengineeringwithinrapidresponseenvironments,”ProceedingsoftheConferenceonSystemsEngineeringResearch2012,Procedia ComputerScience,Vol.8- 2012,Elsevier,March,2012.
• Turner,R.,“Considerationofamulti-layeron-demandschedulingsystemforcomplex,rapid-response,system-of-systemsdevelopmentenvironments,”Proceedingsofthe4thLeanSoftwareandSystemsConference,May13-16,2012,Boston,MA;BlueHolePress,2012.
• Turner,R.;“ALeanApproachtoSchedulingSystemsEngineeringResources,”CrossTalk,May/June,2013.• Turner,R.;Madachy,R.;Lane,J.A.;Ingold,D.;Levine,L.;“Agile-LeanSoftwareEngineering(ALSE):EvaluatingKanban
inSystemsEngineering,”A013- FinalTechnicalReportSERC-2013-TR-022-2,March6,2013.http://serc2cdn1.mannadesignworks.netdna-cdn.com/wp-content/uploads/2014/11/SERC-2013-TR-022-2-Kanban-In-SE-RT-035.pdf
SSRR2016 33
SERCPublicationsfromthisresearch-2
• Lane,J.A.andTurner,R.“ImprovingDevelopmentVisibilityandFlowinLargeOperationalOrganizations,”4thInternationalConferenceonLeanEnterpriseSoftwareandSystems,Galway,Ireland,December1-4,2013,Proceedings,LectureNotesinBusinessInformationProcessing,Vol.167,pp 65-80,Springer-Verlag,Heidelberg,2013.
• Turner,R.,"Value-basedschedulinginsystemofsystemsevolution,"SystemofSystemsEngineering(SOSE),20149thInternationalConferenceon,pp.301-306,9-13June2014.URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6892505&isnumber=6892448
• Tregubov,AlexeyandJoAnnLane,“SimulationofKanban-basedSchedulingforSystemsofSystems:InitialResults,”Procedia ComputerScience,Volume44,2015,Pages224-233.
• Turner,R.etal.“ModelinganOrganizationalViewoftheSoS TowardsManagingitsEvolution,”ProceedingsoftheIEEEConferenceonSystemofSystemsEngineering,SanAntonio,TX,May,2015
• Ens,Richardetal.“TheImpactOfTaskBoardsinAgileSoftwareDevelopmentProjects,”CrossTalk,[IssueTBD],2015.
• Shull,Forrest,“AFrameworkofEmpiricalStudiesofKanban-BasedSchedulingforSoftware-IntensiveSystems,“CMU/SEI-2015-TH-010,December2015.
• Turner,R;L.Yilmaz;J.Smith;D.Li;S.Chada;A.Smith;A.Tregubov.“DATASEM:AsimulationsuiteforSoSEmanagementresearch,”11thSystemofSystemsEngineeringConference(SoSE),Kongsberg,Norway,June2016.
