|
|

 






Dinakar KS
1PI09MBA26

Communication of the ACM, May 2008/Vol.51 No.5 (Pg 59-64)

 ABSTRACT
± What is Traceability?
± What is Software Configuration
Management(SCM) ?
± How can we integrate Traceability and SCM
practice to improve Software Development?
± Investigated using Hospcom as an example.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 INTRODUCTION
± Hospcom develops Embedded Software
Systems.
± 2 yrs study was conducted in development of
an Embedded System for Telecommunication
and Television Management system in
Hospitals.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 TRACEABILITY PROCESS
Create
Plan Traceability Establish
Traceability
Management Traceability
Environments

Impact Analysis

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

Software Configuration Management
Process
Create CM Change & Deliver
Plan CM Configuration
Environments
Items

Monitor &
Report Manage Baseline
& Release
Configuration
status

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

Comparison of Traceability, SCM and
Integration of Traceability & SCM
processes

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Planning
   |

±Organization wide ±Organization wide not ±SCM & Traceability plans
developed developed are developed in
conjunction with one
another for effective
±Knowledge about ±Knowledge about Change Management.
dependency & rationale for dependency & rationale for
changes are not managed changes are managed but ±Provides detail at which
isolated from SCM knowledge about changes
is to be documented and
linked to version and
configuration in SCM.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-

64)
 Manage Work-Process environments
   |

±SCM Tools typically used ±Traceability tools used to ±Enables linking of fine-
to manage Source code at manage finer grain knowledge about
file level but not other dependencies across dependencies to specific
artifacts like requirements various artifacts. versions and
and design. configurations.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Manage Change Requests, Make and
Deliver changes
   |

Only brief Textual Impact of changes can be ±Specific changes to
comments are used to identified through software artifacts can be
describe changes knowledge about documented in detail and
incorporated in specific dependencies and be linked to specific
artifacts. rationale behind changes. versions.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Manage baseline and release
   |

Completeness and Though traceability tools Enables linking
consistency checks are are used to establish links requirements in specific to
difficult by using among requirements, design elements in versions
information from SCM design models, source of design modules and
tools. code etc. they are not source-code modules. This
specifically linked to enables checking
various versions of these completeness and
artifacts. consistency.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Monitor and report configuration
status

 |
Status of configuration
items can be determined
using knowledge about
changes and textual
comments


Used to check status of Configuration status
specific configuration of reports can be more
artifacts complete as they can bring
together knowledge about
changes to specific
versions of software
artifacts and how various
configurations were
derived.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Conclusion
± Project Managers should recognize the extent
to which SCM & Traceability processes are
intertwined.
± This should be implemented organization
wide.
± This should be implemented to meet the
organization needs.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

 Contd͙.
± For effective Change Management clear
Traceability process should be defined and
associated with appropriate SCM processes.

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)

Communication of the ACM, May 2008/Vol.51 No.5(pg59-64)