1. 1 Week 9 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam

2. 2 Review Chapters 7-10 Chapter 11 Configuration Management, Integration, and Builds Appendix D Essential Test Plan Quiz 3

3. 3

4. 4

5. 5 What does configuration management really manage? Software artifacts Change control activities (including inter-relationship) System build activities The management of all the artifacts produced as a part of the software development and software support activities, for example - requirements specifications - design documentation - source code - test scenarios - executable code - data base tables - initialization data - customer problem calls - problem fixes - user documentation

6. 6

7. 7

8. 8 Original Module 1 – v0 Modified Module 1 – v1 Modified 2 nd time Module 1 – v2 Modified 3 rd time Module 1 – v3

9. 9 Link the versioning of code modules to design artifacts Further add the relationship of requirements to design and code artifacts. Now relate the test scenarios to these Add in the possibilities of multiple releases and the support of these multiple releases that can have fixes applied to them Finally, consider these in terms of the world-wide market where we may have Japanese version, German version, French version, Chinese version, Brazilian version, Indian version, etc.

10. 10 A software artifact must be uniquely identifiable with a “name” composed of: PP : two position product code CC : two position country code RRR: three position release code VVV: three position version code TT : two position artifact type code FF : two position format code VIN? A sample artifact identifier: PP.CC.RRR.VVV.TT.FF where “.” Is used as the delimiter

11. 11 Basic functions to: Create a part Delete a part Access functions for View a part Modify a part Return a part Control and service functions Import part(s) Export part(s) List parts Set release or version numbers Increment release or version numbers Change part name, version, release, artifact type, etc Gather parts Merge into a part Promote parts Compare parts Lock / unlock parts Where-used and cross-referencing the parts

12. 12 Tier 1 : Version control and change control: Revision control system (RCS) Source code control system (RCCS) Concurrent version system (CVS) Tier 2: Builds Make utility Odin Cons Scons Tier 3: Configuration Management for large systems PVCS : ChangeMan (Serena Software) Rational Clear Case (IBM) Visual SourceSafe (Microsoft) Perforce (Perforce Software) - we just got this into SPSU(2011)

13. 13

14. 14 Download Software Development Plan by tapping on image above Top-level view of a Software Development Project

15. 15 1. What is a naming model used for? Ans: A naming model is needed for configuration management in order to uniquely identify and control the pieces and parts of the artifacts. Page: 236

16. 16 2. List the four major activities associated with software configuration management. Ans: These are: a) understand and agree on organization’s policies, process activities, and the resulting artifacts that need to be managed, b) determine and define the framework that needs to be used to manage the artifacts, c) determine and bring in any tool that is needed to facilitate the management, and d) train and ensure that the agreed upon configuration management process is practiced and adhered to. Page: 230 3. What are check-in and check-out? Ans: Check-in refers to storing or returning an artifact to a configuration management’s library while check-out refers to retrieving an artifact from the configuration management’s library. Page: 238 4. List three concerns you may need to look into before choosing a configuration management tool. Ans: There are many concerns and should include these: a) is the tool easy to learn and what kind of education is provided by the tool vendor, b) does the tool have all the needed functionalities to accommodate the organization’s naming model and access model and c) can the tool accommodate geographically separate, multi-site development and support. Page: 241-243

17. 17 5. What are the build steps of a single program? Ans: Software system build is a set of activities where all the software source code and data artifacts are gathered for compilation into an executable. All the cross references and external names are resolved. The complete set of artifacts are compiled and linked together into an executable. Page: 240-241 6. What is linking and what are we linking in a build process? Ans: Linking is an activity to tie together all the needed, externally reference items for the software. Page: 240

18. 18 7. Explain the difference between the view and the modify functions in the storage and access model of configuration management. Ans: The “view” function is the retrieval of an artifact for the purpose of reading the artifact and may be performed by all at all times. The “modify” function is the retrieval of an artifact for the purpose of making changes to the artifact. Thus in the case of modify, only those authorized should be allowed to perform the function. In addition, to prevent conflicts, when an artifact X is retrieved for modification, that X is locked from other modify function until it is returned. X may still be viewed by others. Page: 238-239 8. Name a tool from each of the three tiers of automating the configuration management activities. Ans: The tools for the three tiers are: First tier = Performing version control – Revision Control System (RCS) and Source Code Control System (SCCS) Second tier = Include the build function – MAKE utility in UNIX systems and Odin Third tier = Integrate the configuration, development, and support activities – ClearCase, PVCS (Serena ChangeMan), and Visual SourceSafe. Page: 241-242

19. 19