Configuration Management, Software Configuration Management Best Practices, Version control, and Advantages & drawbacks of SCM Tools.
Software Configuration Management
1. What are Software Configuration Management Best Practices?
The best practices of Software Configuration Management are as follows
• Identify and store artifacts in a secure repository
• Control and audit changes to artifacts
• Organize artifacts into versioned components
• Components reduce complexity
• It is easier to identify the quality level of a particular component baseline than that of numerous individual files
• Instantiating a physical component object in a tool helps institutionalize component sharing and reuse
• Mapping logical design components to physical SCM components helps preserve the integrity of software architectures
• Create baselines at project milestones
• Record and track requests for change
• Organize and integrate consistent sets of versions using activities
• Maintain stable and consistent workspaces
• Support concurrent changes to artifacts and components
• Integrate early and often
• Ensure reproducibility of software builds
2. What are the problems of not using Software Configuration Management (SCM)?
Multiple people have to work on software that is changing More than one version of the software has to be supported ie: Released systems, Custom configured systems, System(s) under development
3. What is a Software Configuration Management tool?
Software tools that automate and facilitate the application of the Software Configuration Management best practices.
4. What are Software Configuration Management processes?
The way SCM is performed on your project, specifically how an SCM tool is applied to accomplish a set of tasks
5. How can Software Configuration Management follows without tools?
Using File Copies to Support Early SCM – Storing backup versions of the software system – Storing intermediate working versions, of certain files or of all the files that make up the system, during the development process
5. How can we use Shared Copy Approach for Software Configuration Management?
An additional copy of the entire system directory structure can be created to store the latest versions of the software.
6. What are the Problems of not using Software Configuration Management tools?
The copy-over problem, which causes versions of files to be lost Recovery from inappropriate changes made to the common code is difficult or impossible The number of uncontrolled copies of files makes it difficult to determine where the latest version really exists
7. What is a Version?
A specific instance of a baseline or configuration item is known as Version.
8. What is Configuration?
Configuration is a collection of all the elements of a baseline and a description of how they fit together.
9. What is Baseline?
One or more software configuration items that have been formally reviewed and agreed upon and serve as a basis for further development
10. What baselines are required to be defined and managed?
Typically aligned with major milestones. Applies to documents as well as code.
11. How is the current software configuration defined?
A snapshot of everything the product has produced at some point in time.
12. Who must approve changes to baselines?
Usually, the Change Control Board (CCB) must approve changes to baselines.
13. What is the responsibility of the Configuration Control Board?
Group with the responsibility for reviewing and approving changes to baselines
14. How are baselines verified?
By reviews, inspections, and the testing of code
15. How and when are baselines created and physically controlled?
Through the use of document control systems, code control tools, and procedures to prevent the making of unapproved changes
16. Are baselines tied to project milestones?
Many are, but during coding many may not be tied to project milestones
17. What is Software Configuration Item?
A collection of software elements treated as a unit for the purposes of Software Configuration Management
18. What are the components of clear case?
Version Control Workspace Management Build Management Process Control
19. What is Version Control?
Version Control allows different projects to use the same source files at the same time It isolates work that is not ready to be shared by the rest of the project. It isolates work that should never be shared. It allows software engineers to continue development along a branch even when a line of development is frozen.
20. What is the use of Version Control?
Allows different projects to use the same source files at the same time Isolates work that is not ready to be shared by the rest of the project Isolates work that should never be shared Allows software engineers to continue development along a branch even when a line of development is frozen
21. What is the use of workspace?
Software engineers need a consistent and reproducible workspace area (a sandbox) in which they can develop and debug their code. They need to be able to share project files while shielding the project from the instability of their evolving code
22. What is Change Control?
Proposed changes to baselines must have some level of review. The impact of proposed changes must be identified and understood. When appropriate the approval of the CCB, key managers and project members must be obtained Approved changes must be properly implemented After changes are made all affected parties must be notified
23. What is UCM (Unified Change Management)?
It unifies the activities used to plan and track project progress with the artifacts being changed.
24. What is a view?
A way of seeing the objects in one or more VOBs (Versioned Object Base) Version selection is based on user-defined rules
25. What are the types of Views?
There are two types of views. They are Dynamic View: VOB objects are displayed from the VOB cache Snapshot View: VOB objects are copied to the client.
26. What is a view?
Selects versions of VOB directories and Files. It enables developers to work in parallel.
27. What are the different types of checkouts used in modern Software Configuration Management tools?
Modern Software Configuration Management tools support both reserved and unreserved checkouts.
28. What is the tool which supports Component-based Development?
ClearCase UCM is the tool that supports component-based development.
29. What is Activity-based Configuration Management?
Configuration Management based on task, defect and enhancement is known as Activity-based Configuration Management.
30. What is the basic concept of ClearCase UCM?
The ClearCase UCM is working on the following two basic concepts activity-based SCM and component management
31. What are the SCM activities?
The SCM activities are: management and planning of the SCM process, software configuration identification, software configuration control, software configuration status accounting, software configuration auditing, and software release management and delivery.
32. What is a Software Build?
A build is an operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the final product. A build comprises one or more implementation elements (often executable), each constructed from other elements, usually by a process of compilation and linking of source code.
33. What is a build report?
Build Reports list all the files, their location, and incorporated changes that make up a build for a specific version of the software
34. What are the configuration audit findings?
The Configuration Audit Findings identify a baseline, any missing required artifacts, and incompletely tested or failed requirements.
Useful Links
