Artifacts of the Process.docx
- 文档编号:14614634
- 上传时间:2023-06-25
- 格式:DOCX
- 页数:31
- 大小:1.67MB
Artifacts of the Process.docx
《Artifacts of the Process.docx》由会员分享,可在线阅读,更多相关《Artifacts of the Process.docx(31页珍藏版)》请在冰点文库上搜索。
ArtifactsoftheProcess
Chapter6ArtifactsoftheProcess
KeyPoints
∙Theartifactsoftheprocessareorganizedintofivesets:
management,requirements,design,implementation,anddeployment.
∙Themanagementartifactscapturetheinformationnecessarytosynchronizestakeholderexpectations.
∙Therequirements,design,implementation,anddeploymentartifactsarecapturedinrigorousnotationsthatsupportautomatedanalysisandbrowsing.
Conventionalsoftwareprojectsfocusedonthesequentialdevelopmentofsoftwareartifacts:
buildtherequirements,constructadesignmodeltraceabletotherequirements,buildanimplementationtraceabletothedesignmodel,andcompileandtesttheimplementationfordeployment.Thisprocesscanworkforsmall-scale,purelycustomdevelopmentsinwhichthedesignrepresentation,implementationrepresentation,anddeploymentrepresentationarecloselyaligned.Forexample,asingleprogramthatisintendedtorunonasinglecomputerofasingletypeandiscomposedentirelyofspecial-purposecustomcomponentscanbeconstructedwithstraightforwardtraceabilityamongalltherepresentations.
However,thisapproachdoesn'tworkverywellformostoftoday'ssoftwaresystems,inwhichthesystemcomplexity(inmanydimensions)resultsinsuchnumerousrisksandsubtletraceabilityrelationshipsthatyoucannotefficientlyuseasimplisticsequentialtransformation.Mostmodernsystemsarecomposedofnumerouscomponents(somecustom,somereused,somecommercialproducts)intendedtoexecuteinaheterogeneousnetworkofdistributedplatforms.Theyrequireaverydifferentsequenceofartifactevolutionandaverydifferentapproachtotraceability.
Overthepast20years,thesoftwareindustryhasmaturedandhastransitionedthemanagementprocesstobeiterative.Ratherthanbeingbuiltsequentially,theartifactsareevolvedtogether,andtheconstraints,thedifferentlevelsofabstractions,andthedegreesoffreedomarebalancedamongcompetingalternatives.Recurringthemesfromsuccessfulprojectsdemonstratethatthesoftwareartifactsevolvetogetherwithbalancedlevelsofdetail.Artifactsdonotevolveinaone-way,linearprogressionfromrequirementstodesigntoimplementationtodeployment.Choicesaboutimplementationanddeploymentaffectthewayinwhichtherequirementsarestatedandthewayinwhichthedesignproceeds.Informationanddecisionscanflowinvariouswaysamongartifacts.Thepurposeofagooddevelopmentprocessistoremoveinappropriate,prematureconstraintsonthedesignandtoaccommodatetherealengineeringconstraints.
Andwhatistheimpactofiterativedevelopmentonevolvingartifacts?
Theprimarydifferencefromtheconventionalapproachisthatwithineachlife-cyclephase,theworkflowactivitiesdonotprogressinasimplelinearway,nordoesartifactbuildingproceedmonotonicallyfromoneartifacttoanother.Instead,thefocusofactivitiessweepsacrossartifactsrepeatedly,incrementallyenrichingtheentiresystemdescriptionandtheprocesswiththelessonslearnedinpreservingbalanceacrossthebreadthanddepthofinformation.
6.1THEARTIFACTSETS
Tomakethedevelopmentofacompletesoftwaresystemmanageable,distinctcollectionsofinformationareorganizedintoartifactsets.Eachsetcomprisesrelatedartifactsthatarepersistentandinauniformrepresentationformat(suchasEnglishtext,C++,VisualBasic,Java,astandarddocumenttemplate,astandardspreadsheettemplate,oraUMLmodel).Whileasetrepresentsacompleteaspectofthesystem,anartifactrepresentscohesiveinformationthattypicallyisdevelopedandreviewedasasingleentity.Inanygivenorganization,project,orsystem,someoftheseartifacts--andevensomesets--maybetrivialorunnecessary.Ingeneral,however,someinformationneedstobecapturedineachsettosatisfyallstakeholders.
Life-cyclesoftwareartifactsareorganizedintofivedistinctsetsthatareroughlypartitionedbytheunderlyinglanguageoftheset:
management(adhoctextualformats),requirements(organizedtextandmodelsoftheproblemspace),design(modelsofthesolutionspace),implementation(human-readableprogramminglanguageandassociatedsourcefiles),anddeployment(machine-processablelanguagesandassociatedfiles).
Theemergenceofrigorousandmorepowerfulengineeringnotationsforrequirementsanddesignartifactsthatsupportarchitecture-firstdevelopmentwasamajortechnologyadvance.Inparticular,theUnifiedModelingLanguagehasevolvedintoasuitablerepresentationformat,namelyvisualmodelswithawell-specifiedsyntaxandsemanticsforrequirementsanddesignartifacts.VisualmodelingusingUMLisaprimitivenotationforearlylife-cycleartifacts.TheartifactsetsareshowninFigure6-1;theirpurposesandnotationsaredescribednext.
Figure6-1Overviewoftheartifactsets(Page85)
6.1.1THEMANAGEMENTSET
Themanagementsetcapturestheartifactsassociatedwithprocessplanningandexecution.Theseartifactsuseadhocnotations,includingtext,graphics,orwhateverrepresentationisrequiredtocapturethe"contracts"amongprojectpersonnel(projectmanagement,architects,developers,testers,marketers,administrators),amongstakeholders(fundingauthority,user,softwareprojectmanager,organizationmanager,regulatoryagency),andbetweenprojectpersonnelandstakeholders.Specificartifactsincludedinthissetaretheworkbreakdownstructure(activitybreakdownandfinancialtrackingmechanism),thebusinesscase(cost,schedule,profitexpectations),thereleasespecifications(scope,plan,objectivesforreleasebaselines),thesoftwaredevelopmentplan(projectprocessinstance),thereleasedescriptions(resultsofreleasebaselines),thestatusassessments(periodicsnapshotsofprojectprogress),thesoftwarechangeorders(descriptionsofdiscretebaselinechanges),thedeploymentdocuments(cutoverplan,trainingcourse,salesrolloutkit),andtheenvironment(hardwareandsoftwaretools,processautomation,documentation,trainingcollateralnecessarytosupporttheexecutionoftheprocessdescribedinthesoftwaredevelopmentplanandtheproductionoftheengineeringartifacts).
Managementsetartifactsareevaluated,assessed,andmeasuredthroughacom,binationofthefollowing:
∙Relevantstakeholderreview
∙Analysisofchangesbetweenthecurrentversionoftheartifactandpreviousversions(managementtrendsandprojectperformancechangesintermsofcost,schedule,andquality)
∙Majormilestonedemonstrationsofthebalanceamongallartifactsand,inparticular,theaccuracyofthebusinesscaseandvisionartifacts
∙
6.1.2THEENGINEERINGSETS
Theengineeringsetsconsistoftherequirementsset,thedesignset,theimplementationset,andthedeploymentset.Theprimarymechanismforevaluatingtheevolvingqualityofeachartifactsetisthetransitioningofinformationfromsettoset,therebymaintainingabalanceofunderstandingamongtherequirements,design,implementation,anddeploymentartifacts.Eachofthesecomponentsofthesystemdescriptionevolvesovertime.
RequirementsSet
Structuredtextisusedforthevisionstatement,whichdocumentstheprojectscopethatsupportsthecontractbetweenthefundingauthorityandtheprojectteam.Adhocformatsmayalsobeusedforsupplementaryspecifications(suchasregulatoryrequirements)andusermockupsorotherprototypesthatcapturerequirements.UMLnotationisusedforengineeringrepresentationsofrequirementsmodels(usecasemodels,domainmodels).Therequirementssetistheprimaryengineeringcontextforevaluatingtheotherthreeengineeringartifactsetsandisthebasisfortestcases.
Requirementsartifactsareevaluated,assessed,andmeasuredthroughacombinationofthefollowing:
∙Analysisofconsistencywiththereleasespecificationsofthemanagementset
∙Analysisofconsistencybetweenthevisionandtherequirementsmodels
∙Mappingagainstthedesign,implementation,anddeploymentsetstoevaluatetheconsistencyandcompletenessandthesemanticbalancebetweeninformationinthedifferentsets
∙Analysisofchangesbetweenthecurrentversionofrequirementsartifactsandpreviousversions(scrap,rework,anddefecteliminationtrends)
∙Subjectivereviewofotherdimensionsofquality
DesignSet
UMLnotationisusedtoengineerthedesignmodelsforthesolution.Thedesignsetcontainsvaryinglevelsofabstractionthatrepresentthecomponentsofthesolutionspace(theiridentities,attributes,staticrelationships,dynamicinteractions).Thedesignmodelsincludeenoughstructuralandbehavioralinformationtoascertainabillofmaterials(quantityandspecificationofprimitivepartsandmaterials,labor,andotherdirectcosts).Designmodelinformationcanbestraightforwardlyand,inmanycases,automaticallytranslatedintoasubsetoftheimplementationanddeploymentsetartifacts.Specificdesignsetartifactsincludethedesignmodel,thetestmodel,
andthesoftwarearchitecturedescription(anextractofinformationfromthedesignmodelthatispertinenttodescribinganarchitecture).
Thedesignsetisevaluated,assessed,andmeasuredthroughacombinationofthefollowing:
∙Analysisoftheinternalconsistencyandqualityofthedesignmodel
∙Analysisofconsistencywiththerequirementsmodels
∙Translationintoimplementationanddeploymentsetsandnotations(forexample,traceability,sourcecodegeneration,compilation,linking)toevaluatetheconsistencyandcompletenessandthesemanticbalancebetweeninformationinthesets
∙Analysisofchangesbetweenthecurrentversionofthedesignmodelandpreviousversions(scrap,rework,anddefecteliminationtrends)
∙Subjectivereview
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- Artifacts of the Process
![提示](https://static.bingdoc.com/images/bang_tan.gif)