Chapter 5 Software Configuration Management Choose the answer that mostly suits each of the sentences given: 1. No matter where you are in the system lifecycle, the system will change, and the desire to change it will persist through out the life cycle. 2. Software changes are caused by a. Changes in product requirements or business rules b. Changes in user requirements c. Changes in project priorities or software engineering team structure 3. Software changes are caused by a. Changes in product requirements or business rules b. Changes in project priorities or software engineering team structure c. Changes in budget or schedule 4. Software changes are caused by a. Changes in product requirements or business rules b. Changes in project priorities or software engineering team structure c. Changes in budget or schedule 5. Software changes are caused by a. Changes in software language b. Changes in user requirements c. Changes in users positions
6. Software changes are caused by a. Changes in software designers b. Changes in software programmers c. Changes in software documentation 7. A baseline is defined as: any of the versions of a product that has been formally reviewed and agreed upon, that thereafter served as the basis for further development, and that could be changed only through formal change control procedures. 8. A baseline is defined as: a specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. 9. A baseline is defined as: an accumulated specifications of a product that has been formally reviewed and agreed upon, that thereafter served as the basis for further development, and that could be changed only through formal change control procedures. 10. Some of the main objectives of the SCM process tasks are to: a. Identify all items that collectively define the software configuration. b. Manage changes to one or more of these items. c. Facilitate the construction of different versions of an application. 11. Some of the main objectives of the SCM process tasks are to: a. Manage changes to one or more of these items. b. Facilitate the construction of different versions of an application. c. Ensure that software quality is maintained as the configuration evolves over time.
12. Some of the main objectives of the SCM process tasks are to: a. Identify all parameters that collectively define the software testing. b. Manage changes to one or more of these parameters. c. Facilitate the construction of different versions of an application. 13. Some of the main objectives of the SCM process tasks are to: a. Identify all parameters that collectively define the software modules. b. Manage work done on one or more of these parameters. c. Facilitate the construction of different modules of an application. 14. Some of the main objectives of the SCM process tasks are to: a. Identify all items that collectively define the software configuration. b. Manage design of one or more of these items. c. Ensure that software maintenance is conducted over time. 15. The five SCM tasks are: identification, version control, change control, configuration auditing, and reporting. 16. The identification of objects in SCM is defined as, each object should be separately named and then organized using an object-oriented approach. 17. A version control system implements or is directly integrated with some major capabilities, such as: a. a project database that stores all relevant configuration objects
b. a version management capability that stores all versions of a configuration object (or enables any version to be constructed using differences from past versions); c. a make facility that enables the software engineer to collect all relevant configuration objects and construct a specific version of the software. 18. A version control system implements or is directly integrated with some major capabilities, such as: a. a repository that stores all relevant configuration objects b. a make facility that enables the software engineer to collect all relevant configuration objects and construct a specific version of the software. c. an bug tracking capability that enables the team to record and track the status of all outstanding issues associated with each configuration object. 19. A version control system implements or is directly integrated with some major capabilities, such as: a. a version management facility that saves all versions of a configuration object b. a tool that enables the software engineer to collect all related configuration objects and construct a specific version of the software. c. a tracking capability that enables the team to record and track the status of all outstanding issues associated with each configuration object. 20. Some version control systems establish a change set that includes a. A collection of all changes to some baseline configuration that is required to create a specific version. b. All changes to all files in the configuration along with reason for changes. c. details of who made the changes and when. 21. Some version control systems establish a change set that includes a. all changes to some baseline configuration that is required to create a specific version, b. changes to some files in the configuration along with reason for changes, c. details of where the changes have been made,
22. Change control authority decides, either the change request is queued for action or the change request is denied, where the requester is informed 23. Change control authority assigns individuals to configuration objects 24. Change control authority establishes a baseline for testing 25. In the change control process, appropriate version of software is rebuilt. 26. Change control authority checks out configuration objects 27. In the change control process, quality assurance and testing activities are performed. 28. The software configuration audit complements the formal technical review by a. The software process has been followed b. Software engineering standards have been properly applied c. The changes have been highlighted in the SCI.
29. The software configuration audit complements the formal technical review by a. Changes specified in the ECO have been made. b. What additional modifications have been incorporated? c. A formal technical review has been followed to assess technical correctness 30. The software configuration audit complements the formal technical review by a. Changes specified in the ECO have been made. b. Software engineering standards have been properly applied c. The changes have been highlighted in the SCI. 31. The software configuration audit complements the formal technical review by a. Changes specified in the ECO have been made. b. A formal technical user has been testing the system to assess technical correctness c. Formal procedures for noting the designing, and installation have been followed 32. The software configuration audit complements the formal technical review by a. Changes specified in the LOC have been made. b. Other additional testing procedures have been incorporated c. The parameter values in the configuration have been followed.