Date post: | 24-Dec-2015 |
Category: |
Documents |
Upload: | buddy-barrett |
View: | 226 times |
Download: | 0 times |
22 1
Chapter 6– Artifacts of Chapter 6– Artifacts of the processthe process
22 2
Artifacts DefinitionArtifacts Definition
An An artifactsartifacts represents cohesive represents cohesive information that typically developed & information that typically developed & reviewed as a single entityreviewed as a single entity
To make the development of a To make the development of a complete software system complete software system manageable, distinct collection of manageable, distinct collection of information are organised into information are organised into artifacts setsartifacts sets
22 3
Life cycle software artifactsLife cycle software artifacts
Life cycle software are organized into five setsLife cycle software are organized into five sets
Management setManagement set – Ad-hoc textual formats – Ad-hoc textual formats RequirementsRequirements – organised text & models of the – organised text & models of the problem spaceproblem space DesignDesign – Models of solution space – Models of solution space ImplementationImplementation – Human-readable – Human-readable
programmingprogramming language & associated source fileslanguage & associated source files DeploymentDeployment – machine-processable language & – machine-processable language & associated filesassociated files
22 4
Management & Engineering setManagement & Engineering set
The The Management artifactsManagement artifacts capture the capture the information information
necessary to synchronize stakeholder necessary to synchronize stakeholder expectationsexpectations
( ( English textEnglish text ) )
The The Engineering artifactsEngineering artifacts (requirements,design,(requirements,design,
implementation & deployment ) are captured implementation & deployment ) are captured in rigorous notations that support automated in rigorous notations that support automated analysis & browsing ( analysis & browsing ( C++, Visual Basic, java, C++, Visual Basic, java, standard document template, a standard standard document template, a standard spreadsheet template, or a UMLspreadsheet template, or a UML ) )
22 5
Overview of the artifact setsOverview of the artifact setsRequirements Sets
• 1 Vision document
2 Requirements models
Design Sets
1 Design Model
2 Test Mode
3 Software\ architecture
description
Implementation Sets
Source
code baselines
Associated Compile-time
files
Components executables
Deployment
Sets Integrated product executable baselines Associated run- time files User manual
Management Sets Planning Activities Operational Activities
1 Work breakdown structure 5. Release Description 2 Business case 6. Status Assessments 3 Release Specification 7. Software change order database 4 Software Development Plan 8. Deployment document 9. Environment
22 6
The Management Set( 1 of 3 )The Management Set( 1 of 3 )
The The management setmanagement set captures the artifacts associated with captures the artifacts associated with
Process planning ActivitiesProcess planning Activities Process Execution ( Operational ) ActivitiesProcess Execution ( Operational ) Activities
These artifacts use ad-hoc notations including text, graphics or whatever presentation required to These artifacts use ad-hoc notations including text, graphics or whatever presentation required to
capture the contracts among project personnel & stakeholdercapture the contracts among project personnel & stakeholder
Process planning ActivitiesProcess planning Activities
Specific artifacts include under this areSpecific artifacts include under this are
Work breakdown StructureWork breakdown Structure – Activity breakdown & financial tracking – Activity breakdown & financial tracking mechanismsmechanisms
Business caseBusiness case – Cost, Schedule, Profit expectations – Cost, Schedule, Profit expectations
Release SpecificationsRelease Specifications – Scope, Plan, Objectives for release baselines – Scope, Plan, Objectives for release baselines
Software development planSoftware development plan – Project process instance – Project process instance
22 7
The Management Set (2 of 3 )The Management Set (2 of 3 )
Process Execution( Operational ) ActivitiesProcess Execution( Operational ) Activities Specific artifacts include under this areSpecific artifacts include under this are
Release descriptions Release descriptions – results of release baselines– results of release baselines
Status assessmentStatus assessment – Periodic snapshots of project progress – Periodic snapshots of project progress
Software change order databaseSoftware change order database – Descriptions of discrete baseline changes – Descriptions of discrete baseline changes
Deployment documentsDeployment documents – Cutover plan, training course, sales rollout kit – Cutover plan, training course, sales rollout kit
EnvironmentEnvironment – Hardware & Software tools, process automation, – Hardware & Software tools, process automation, documentation,documentation,
training collateral necessary to support the execution of the training collateral necessary to support the execution of the process described in the development plan & production of theprocess described in the development plan & production of the engineering artifactsengineering artifacts
22 8
The Management Set (3 of 3 )The Management Set (3 of 3 )
Management set artifactsManagement set artifacts are evaluated, assessed & measured are evaluated, assessed & measured through through
a combination of the followinga combination of the following
Relevant stakeholder reviewRelevant stakeholder review
Analysis of changes between the current version of the Analysis of changes between the current version of the
artifacts & previous versionsartifacts & previous versions
Major milestone demonstrations of the balance among all artifacts Major milestone demonstrations of the balance among all artifacts
22 9
The Engineering Set ( 1 of 5 )The Engineering Set ( 1 of 5 )
The The Engineering setsEngineering sets consists of consists of
Requirements setRequirements set
Design setDesign set
Implementation setImplementation set
Deployment setDeployment set
22 10
The Engineering Set ( 2 of 5 )The Engineering Set ( 2 of 5 )
Requirements artifactsRequirements artifacts are evaluated, assessed & measured through are evaluated, assessed & measured through a combination of the followinga combination of the following
Analysis of consistency with the release specification of theAnalysis of consistency with the release specification of the management setmanagement set
Analysis of consistency with the vision & the requirement modelsAnalysis of consistency with the vision & the requirement models
Mapping against remaining engineering artifacts sets to evaluate Mapping against remaining engineering artifacts sets to evaluate the consistency & completenessthe consistency & completeness
Analysis of changes between the current version of requirements Analysis of changes between the current version of requirements artifacts & previous versionartifacts & previous version
Subjective review of other dimensions of qualitySubjective review of other dimensions of quality
22 11
The Engineering Set ( 3 of 5 )The Engineering Set ( 3 of 5 )
Design set Design set are evaluated, assessed & measured through are evaluated, assessed & measured through a combination of the followinga combination of the following
Analysis of the internal consistency & quality of the design modelAnalysis of the internal consistency & quality of the design model
Analysis of consistency with the requirements modelsAnalysis of consistency with the requirements models
Translation into implementation & deployment sets & notations Translation into implementation & deployment sets & notations to evaluate the consistency & completenessto evaluate the consistency & completeness
Analysis of changes between the current version of design model Analysis of changes between the current version of design model & previous version& previous version
Subjective review of other dimensions of qualitySubjective review of other dimensions of quality
22 12
The Engineering Set ( 4 of 5 )The Engineering Set ( 4 of 5 )
Implementation setsImplementation sets are evaluated, assessed & measured through are evaluated, assessed & measured through
a combination of the followinga combination of the following
Analysis of consistency with the design modelsAnalysis of consistency with the design models
Translation into deployment set notations to evaluate Translation into deployment set notations to evaluate
the consistency & completeness among artifact setsthe consistency & completeness among artifact sets
Analysis of changes between the current version of Analysis of changes between the current version of implementation set implementation set
& previous version& previous version Subjective review of other dimensions of qualitySubjective review of other dimensions of quality
22 13
The Engineering Set ( 5 of 5 )The Engineering Set ( 5 of 5 )
Deployment setsDeployment sets are evaluated, assessed & measured through are evaluated, assessed & measured through a combination of the followinga combination of the following
Testing against the usage scenarios & quality attributes defined Testing against the usage scenarios & quality attributes defined in the requirement set to evaluate the consistency & completenessin the requirement set to evaluate the consistency & completeness
Testing the partitioning, replication & allocation strategies in Testing the partitioning, replication & allocation strategies in mapping components of the implementation set to physical mapping components of the implementation set to physical resources of the deployment systemresources of the deployment system
Testing against the defined usage scenarios in the user manual Testing against the defined usage scenarios in the user manual
Analysis of changes between the current version of deployment set Analysis of changes between the current version of deployment set & previous version& previous version
Subjective review of other dimensions of qualitySubjective review of other dimensions of quality
22 14
Life cycle focus on artifacts setsLife cycle focus on artifacts sets
Management Requirements
Design
Implementation
Deployment
22 15
Artifact Evolution over the Life Artifact Evolution over the Life CycleCycle
22 16
Artifact Evolution over the Life Artifact Evolution over the Life CycleCycle
22 17
Test ArtifactsTest Artifacts
Conventional software testing followed same document driven approach that was appliedConventional software testing followed same document driven approach that was appliedTo software development.To software development.Development team & testing teamDevelopment team & testing team prepare their required procedures in the form of prepare their required procedures in the form of document driven which lead to many problemsdocument driven which lead to many problems
In the modern process exactly same sets,notations & artifacts are used both forIn the modern process exactly same sets,notations & artifacts are used both forTesting & production activities. This forced several engineering disciplines into the processTesting & production activities. This forced several engineering disciplines into the process
The testing artifacts must be developed concurrently with the product from The testing artifacts must be developed concurrently with the product from inception through deploymentinception through deployment
The test artifacts are communicated, engineered & developed within the same artifacts The test artifacts are communicated, engineered & developed within the same artifacts Sets as the developed productSets as the developed product
The test artifacts are implemented as software programsThe test artifacts are implemented as software programs
Testing artifacts are documented similar to product is documentedTesting artifacts are documented similar to product is documented
Developers of test artifacts use the same tools, techniques & training as the softwareDevelopers of test artifacts use the same tools, techniques & training as the software engineers developing the productsengineers developing the products
22 18
Management ArtifactsManagement Artifacts
All the Management artifacts are studied in detailAll the Management artifacts are studied in detail
Business caseBusiness case Software development planSoftware development plan Work Breakdown structureWork Breakdown structure Software change order databaseSoftware change order database Release specificationsRelease specifications Release descriptionsRelease descriptions Status AssessmentStatus Assessment EnvironmentEnvironment DeploymentDeployment
22 19
Engineering ArtifactsEngineering Artifacts
Related Engineering Artifacts are explained forRelated Engineering Artifacts are explained for
Vision DocumentVision Document Architecture DescriptionArchitecture Description Software User ManualSoftware User Manual
22 20
Artifacts sequences across Artifacts sequences across a typical life cyclea typical life cycle
Informal versionInformal version Controlled baselineControlled baseline
Management setManagement set
1.Work breakdown structure 1.Work breakdown structure
2. Business case2. Business case
3. Release Specifications3. Release Specifications
4. Software Development Plan4. Software Development Plan
5.Release Description5.Release Description
6. Status Assessment6. Status Assessment
7. Software change order data7. Software change order data
8. Deployment document8. Deployment document
9. Environment9. Environment
22 21
Artifacts sequences across Artifacts sequences across a typical life cyclea typical life cycle
Informal versionInformal version Controlled baselineControlled baseline
Requirement setRequirement set1.Vision Document1.Vision Document2. Requirement Model(s)2. Requirement Model(s)
Design setDesign set1 Design Model(s)1 Design Model(s)2 Test Model2 Test Model3 Architecture description3 Architecture description
Implementation setImplementation set1. Source code baselines1. Source code baselines2. Associated compile-time files2. Associated compile-time files3. Component executables3. Component executables
Deployment setDeployment set1. Integrated product-executable1. Integrated product-executable baselinesbaselines2. Associated run-time files2. Associated run-time files3. User Manual3. User Manual
22 22
Pragmatic ArtifactsPragmatic Artifacts
Conventional document driven approach is changed to more effective Conventional document driven approach is changed to more effective
Approach which redirect this documentation effort to improving the rigor & Approach which redirect this documentation effort to improving the rigor & Understandability of information source & allowing on-line review of native Understandability of information source & allowing on-line review of native Information source by using smart browsing & navigation toolsInformation source by using smart browsing & navigation tools This philosophy raises the following cultural issuesThis philosophy raises the following cultural issues
People want to review information but don’t understand the languagePeople want to review information but don’t understand the language of the artifactsof the artifacts
People want to review the information but don’t have access to the toolsPeople want to review the information but don’t have access to the tools
Human-readable engineering artifacts should use rigorous notations thatHuman-readable engineering artifacts should use rigorous notations that are complete,consistent & used in a self-documenting mannerare complete,consistent & used in a self-documenting manner
Useful documentation is self-defining : it is documentation that gets usedUseful documentation is self-defining : it is documentation that gets used
Paper is tangible;electronic artifacts are too easy to changePaper is tangible;electronic artifacts are too easy to change