[Spoorthi]

WHAT IS CONFIGURATION MANAGEMENT?
configuration management covers the processes used to control,coordinate,and track:code,requirements,documentation,problems,change requests,designs,tools/compilers/libraries/patches, changes made to them, and who makes the changes.

WHAT IF THE SOFTWARE IS SO BUGGY IT CANT REALLY BE TESTED AT ALL?
test site/location.
outside test organizations to be utilized and their purpose, responsibilities,deliverables,contact persons, and corordination issues.
relevant proprietary,classified,security, and licensing issues.
open issues
appendix-glossary, acronyms, etc.

WHAT IS A TEST CASE?
a test case is a document that describes an input,action, or event and an expected response, to determine if a feature of an appplication is working correctly. a test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup,input data requirements,steps,and expected results.
note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. for this reason, its useful to preapre test cases early in the developement cycle if possible.

HOW CAN IT BE KNOWN WHEN TO STOP TESTING?
this can be difficult to determine. many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. common factors in decideing when to stop are:
deadlines (release deadlines, testing deadlines etc...)
test cases completed with certain percentage passed.
test budget depleted
coverage of code/functionality/requirements reaches a specified point.
bug rate falls below a certain level.
beta or alpha testing period ends

[nani_i]

Hai spoorthy,



Can u explain a little bit clear about configuration Manangement.


Thanks
Nani.i

[RisingSun]

good post

[Spoorthi]

hi nani here is abt SCM...


Software configuration management(SCM) is a discipline of applying constructive views for discovering , coordinating and controlling changes made to a software under developement. it enables reconstuction of a procudt. SCM reduces the number of errors to increase productivity and hence maintains integrity between various modules of the project to implement changes properly.


SIGNIFICANCE OF AN SCM:

A software under construction undergoes variety of changes at every stage of developement. it is highly impracticable to aviod changes during developement. implementing changes lead to confusion if they are not properly scrutinized. SCM processes recognize,manage and report changes made to existing sofyware. It enables
1.Testing & reuse of high quality software.
2. To identify status of documents (functional & physical characteristics) & code.
3. To maintain different versions of the application.
4.To confirm specified requirement.
5.Maintenance support.
6.chaos and confusion elimination.

PEOPLE INVOLVED IN SCM:

everybody in a project is involved in SCM process. This includes various categories of people like project manager,developers ,testers etc. customers are also involved as they work with the product after change implementation.CCB(change control board) is another governing body which takes care of change to be carried out.

CONFIGURATION MANAGEMENT:
configuration management allows a developer to re-construct an existing process. SCM operations include
1.pre condistions
2.baselining
3.change management
4.workspace amangement
5.configuration management status
6.configuration review.


PRE CONDITIONS:
any change before implementation should be analyzed. analysis will detect the need for the change and how effective it would prove after implementation.a detailed study is made on the change which is to be put into practice.


BASELINING:
at this phase check in and check out of changes into the repository take place.


CHANGE MANAGEMENT:

changes can happen at any phase of the developement cycle which could arise due to several reasons. the main objective of an SCM process is to ensure changes are made effectively. the sequences of activities are as follows
1.a change request is made which includes complete information about the change to be implemented.
2.review of the change request followed by authorizing the change takes place.
3.the change is executed in a workspace.
4.changes are then checked in end checked out of repository.


WORKSPACE MANAGEMENT:

workspace is the environment which enables a developer to implement the change. this environment should resemble the same as when the product was initially developed.managing the workspace provides easy access to the relevant information in the SCM repository.


CONFIGURATION STATUS MANAGEMENT:

the status of the component undergoing change should be frequently updated and documented.this will give information regarding the type of change,location of modification,people involved in implemeting the change,duration of implemetation etc.


CONFIGURATION REVIEW:
this is the final stage of SCM process. Detailed audits or reviews are made to ensure effectiveness. verification for correctness of the modification made and proper documentataion is also done. this ends the SCM process.



Software configuration management(SCM) is a discipline of applying constructive views for discovering , coordinating and controlling changes made to a software under developement. it enables reconstuction of a procudt. SCM reduces the number of errors to increase productivity and hence maintains integrity between various modules of the project to implement changes properly.

SIGNIFICANCE OF AN SCM:
A software under construction undergoes variety of changes at every stage of developement. it is highly impracticable to aviod changes during developement. implementing changes lead to confusion if they are not properly scrutinized. SCM processes recognize,manage and report changes made to existing sofyware. It enables
1.Testing & reuse of high quality software.
2. To identify status of documents (functional & physical characteristics) & code.
3. To maintain different versions of the application.
4.To confirm specified requirement.
5.Maintenance support.
6.chaos and confusion elimination.

PEOPLE INVOLVED IN SCM:

everybody in a project is involved in SCM process. This includes various categories of people like project manager,developers ,testers etc. customers are also involved as they work with the product after change implementation.CCB(change control board) is another governing body which takes care of change to be carried out.

CONFIGURATION MANAGEMENT:

configuration management allows a developer to re-construct an existing process. SCM operations include
1.pre condistions
2.baselining
3.change management
4.workspace amangement
5.configuration management status
6.configuration review.


PRE CONDITIONS:

any change before implementation should be analyzed. analysis will detect the need for the change and how effective it would prove after implementation.a detailed study is made on the change which is to be put into practice.


BASELINING:

at this phase check in and check out of changes into the repository take place.


CHANGE MANAGEMENT:

changes can happen at any phase of the developement cycle which could arise due to several reasons. the main objective of an SCM process is to ensure changes are made effectively. the sequences of activities are as follows
1.a change request is made which includes complete information about the change to be implemented.
2.review of the change request followed by authorizing the change takes place.
3.the change is executed in a workspace.
4.changes are then checked in end checked out of repository.


WORKSPACE MANAGEMENT:

workspace is the environment which enables a developer to implement the change. this environment should resemble the same as when the product was initially developed.managing the workspace provides easy access to the relevant information in the SCM repository.


CONFIGURATION STATUS MANAGEMENT:

the status of the component undergoing change should be frequently updated and documented.this will give information regarding the type of change,location of modification,people involved in implemeting the change,duration of implemetation etc.


CONFIGURATION REVIEW:

this is the final stage of SCM process. Detailed audits or reviews are made to ensure effectiveness. verification for correctness of the modification made and proper documentataion is also done. this ends the SCM process.