1. Chapter 6– Artifacts of the process22

2. Artifacts Definition
An artifacts represents cohesive information that typically developed & reviewed as a single entity
To make the development of a complete software system manageable, distinct collection of information are organised into artifacts sets 22

3. Life cycle software artifacts
Life cycle software are organized into five sets
Management set – Ad-hoc textual formats
Requirements – organised text & models of the
problem space
Design – Models of solution space
Implementation – Human-readable programming
language & associated source files
Deployment – machine-processable language &
associated files 22

4. Management & Engineering set
The Management artifacts capture the information
necessary to synchronize stakeholder expectations
( English text )
The Engineering artifacts (requirements,design,
implementation & deployment ) are captured in rigorous notations that support automated analysis & browsing ( C++, Visual Basic, java, standard document template, a standard spreadsheet template, or a UML ) 22

5. Overview of the artifact sets
Requirements Sets
 1   Vision document
2 Requirements models
Design Sets
1   Design Model
2   Test Mode
3 Software
\ architecture description
Implementation Sets
v     Source code baselines
v     Associated Compile-time files
v     Components executables
Deployment Sets
v     Integrated product executable baselines
v      
v     Associated run-
time files
v     User manual
Management Sets
Planning Activities Operational Activities
1 Work breakdown structure Release Description
2 Business case Status Assessments
3 Release Specification Software change order database
4 Software Development Plan Deployment document
9. Environment 22

6. The Management Set( 1 of 3 )
The management set captures the artifacts associated with
Process planning Activities
Process Execution ( Operational ) Activities
These artifacts use ad-hoc notations including text, graphics or whatever presentation required to
capture the contracts among project personnel & stakeholder
Specific artifacts include under this are
Work breakdown Structure – Activity breakdown & financial tracking mechanisms
Business case – Cost, Schedule, Profit expectations
Release Specifications – Scope, Plan, Objectives for release baselines
Software development plan – Project process instance 22

7. The Management Set (2 of 3 )
Process Execution( Operational ) Activities
Specific artifacts include under this are
Release descriptions – results of release baselines
Status assessment – Periodic snapshots of project progress
Software change order database – Descriptions of discrete baseline changes
Deployment documents – Cutover plan, training course, sales rollout kit
Environment – Hardware & Software tools, process automation, documentation,
training collateral necessary to support the execution of the
process described in the development plan & production of the
engineering artifacts 22

8. The Management Set (3 of 3 )
Management set artifacts are evaluated, assessed & measured through
a combination of the following
Relevant stakeholder review
Analysis of changes between the current version of the
artifacts & previous versions
Major milestone demonstrations of the balance among all artifacts 22

9. The Engineering Set ( 1 of 5 )
The Engineering sets consists of
Requirements set
Design set
Implementation set
Deployment set 22

10. The Engineering Set ( 2 of 5 )
Requirements artifacts are evaluated, assessed & measured through
a combination of the following
Analysis of consistency with the release specification of the
management set
Analysis of consistency with the vision & the requirement models
Mapping against remaining engineering artifacts sets to evaluate the consistency & completeness
Analysis of changes between the current version of requirements
artifacts & previous version
Subjective review of other dimensions of quality 22

11. The Engineering Set ( 3 of 5 )
Design set are evaluated, assessed & measured through
a combination of the following
Analysis of the internal consistency & quality of the design model
Analysis of consistency with the requirements models
Translation into implementation & deployment sets & notations
to evaluate the consistency & completeness
Analysis of changes between the current version of design model
& previous version
Subjective review of other dimensions of quality 22

12. The Engineering Set ( 4 of 5 )
Implementation sets are evaluated, assessed & measured through
a combination of the following
Analysis of consistency with the design models
Translation into deployment set notations to evaluate
the consistency & completeness among artifact sets
Analysis of changes between the current version of implementation set
& previous version
Subjective review of other dimensions of quality 22

13. The Engineering Set ( 5 of 5 )
Deployment sets are evaluated, assessed & measured through
a combination of the following
Testing against the usage scenarios & quality attributes defined
in the requirement set to evaluate the consistency & completeness
Testing the partitioning, replication & allocation strategies in
mapping components of the implementation set to physical
resources of the deployment system
Testing against the defined usage scenarios in the user manual
Analysis of changes between the current version of deployment set
& previous version
Subjective review of other dimensions of quality 22

14. Life cycle focus on artifacts sets
Life cycle focus on artifacts sets
inception
Elaboration
Construction
Transition
Management
Requirements
Design
Implementation
Deployment 22

15. Artifact Evolution over the Life Cycle
Engineering Stage
Inception
Elaboration
Inception
Inception
Elaboration
Inception
Elaboration
Construction
Deployment
Construction
Depolyment
Management
Management
Management 22

16. Artifact Evolution over the Life Cycle
Production Stage
Construction
Transistion
Inception
Inception
Elaboration
Construction
Inception
Elaboration
Construction
Deployment
Depolyment
Management
Management
Management 22

17. Test Artifacts To software development.
Conventional software testing followed same document driven approach that was applied
To software development.
Development team & testing team prepare their required procedures in the form of
document driven which lead to many problems
In the modern process exactly same sets,notations & artifacts are used both for
Testing & production activities. This forced several engineering disciplines into the process
The testing artifacts must be developed concurrently with the product from
inception through deployment
The test artifacts are communicated, engineered & developed within the same artifacts
Sets as the developed product
The test artifacts are implemented as software programs
Testing artifacts are documented similar to product is documented
Developers of test artifacts use the same tools, techniques & training as the software
engineers developing the products 22

18. Management Artifacts
All the Management artifacts are studied in detail
Business case
Software development plan
Work Breakdown structure
Software change order database
Release specifications
Release descriptions
Status Assessment
Environment
Deployment 22

19. Engineering Artifacts
Related Engineering Artifacts are explained for
Vision Document
Architecture Description
Software User Manual 22

20. Artifacts sequences across a typical life cycle
Informal version
Controlled baseline
Management set
1.Work breakdown structure
2. Business case
3. Release Specifications
4. Software Development Plan
5.Release Description
6. Status Assessment
7. Software change order data
8. Deployment document
9. Environment
Elaboration
Construction
Deployment
Inception
iteration1
iteration2
iteration3
iteration4
iteration5
iteration6
iteration7 22

21. Artifacts sequences across a typical life cycle
Informal version
Controlled baseline
Requirement set
1.Vision Document
2. Requirement Model(s)
Design set
1 Design Model(s)
2 Test Model
3 Architecture description
Implementation set
1. Source code baselines
2. Associated compile-time files
3. Component executables
Deployment set
1. Integrated product-executable
baselines
2. Associated run-time files
3. User Manual
Elaboration
Construction
Deployment
Inception
iteration1
iteration2
iteration3
iteration4
iteration5
iteration6
iteration7 22

22. Pragmatic Artifacts
Conventional document driven approach is changed to more effective
Approach which redirect this documentation effort to improving the rigor &
Understandability of information source & allowing on-line review of native
Information source by using smart browsing & navigation tools
This philosophy raises the following cultural issues
People want to review information but don’t understand the language
of the artifacts
People want to review the information but don’t have access to the tools
Human-readable engineering artifacts should use rigorous notations that
are complete,consistent & used in a self-documenting manner
Useful documentation is self-defining : it is documentation that gets used
Paper is tangible;electronic artifacts are too easy to change 22