DEFENSE FINANCE AND ACCOUNTING SERVICE

Configuration Management Plan

For

Program Name

Date of Issue and Status: Date plan acknowledged as acceptable (mm/dd/yyyy) and whether plan is draft or approved. Also include version number.

Issuing organization: Identify the organization issuing this plan.

CONFIGURATION MANAGEMENT PLAN

1. Purpose. This plan specifies processes and procedures for the execution of configuration management (CM) to support the entire software change/modification process.

2. Scope. This plan applies to all activities related to the establishment of system/configuration baseline and change and release of application configuration items (CIs). These CIs are identified in appendices to this plan.

3. Software Configuration Management Structure.

3.1. Organizational Components. Identify the organizational units or teams responsible for the system’s CM activities.

3.1.1. Systems Engineering. Identify and describe the systems engineering activities and tasks that will be accomplished and how the results of these efforts will be documented.

3.1.2. Configuration Management. Identify and describe CM tasks that will be performed.

3.1.3. Development Platform Engineering Team (DPET). Identify and describe the integration of release management procedures with informational and technical requirements necessary for release of software for test and production.

3.1.4. Configuration Control Board (CCB). Identify and describe the membership, roles, and responsibilities of the CCB.

3.2. Configuration Management Responsibilities. Describe the responsibilities of the organizational components performing CM activities.

3.2.1. Configuration Item Identification. Identify who is responsible for CI identification.

3.2.2. Configuration Control. Identify who is responsible for configuration control and describe the procedures for accomplishing configuration control (CI identification, establishing baselines, changes, deviations, waivers, configuration change orders (CCOs), CCB requirements).

3.2.3. Configuration Status Accounting. Identify who is responsible for configuration status accounting and describe the procedures for accomplishing configuration status accounting (CIs, baselines, records, databases, etc.) requirements.

3.2.4. Audits and Reviews. Identify the responsibilities involved in audits and reviews and describe what will be accomplished during each audit and review.

4. Software Configuration Management (SCM) Activities.

4.1. Configuration Identification. Describe the procedures for meeting the CI requirements, including a description of activities for identifying CIs and baseline items, formation of releases, and baselining of products.

4.2. Configuration Control. Describe the configuration control activities, including level of authority for approval, change proposal processing, and CCB roles and procedures.

4.3. Configuration Status Accounting. Identify reports required for status accounting, i.e., the status of CIs, SCRs, and releases.

4.4. Audits and Reviews. Describe the formal review/audit procedures to be used for configuration audits and reviews (functional configuration audits and physical configuration audits).

4.5. Scheduling and Tracking of SCM Activities. Describe the scheduling and tracking of CM activities that will be accomplished for each release.

5. Library Management. Describe the procedures to be used for development library environment management, release management library environment management, validation testing library environment management, and release certification.

6. Tools, Techniques, and Methodologies. Identify tools and techniques and describe any unique methodologies used to accomplish effective CM.

7. Records Collection and Retention. Identify CM information to be retained and the locations and methods of retention.

8. Procedures for Updating Plan. Describe the steps required to modify the plan to include version number and methodology.

9. Change Information Sheet. List the changes and additions included in the current version of the plan.

CONFIGURATION MANAGEMENT PLAN

APPENDIX A – ACRONYMS

Describe the acronyms as they are used in the plan.

APPENDIX B – DEFINITIONS

Describe the key terms as they are used in the plan.

APPENDIX C – REFERENCES

Provide a complete list of documents referenced in the text of the plan. Each reference shall contain, as approp

DEFENSE FINANCE AND ACCOUNTING SERVICE

Review Checklist

for

Program Name

Date of Issue and Status: Date checklist is acknowledged as acceptable (mm/dd/yyyy) and whether checklist is draft or approved. Also include version number.

Issuing organization: Identify the organization issuing this checklist.

REVIEW CHECKLIST

1. Purpose. The Review Checklist is used to ensure the reviews are conducted in an appropriate and successful manner. This checklist is used for all product reviews, including but not limited to System Requirements Review, Functional Requirements Review, Critical Design Review, peer reviews.

2. Scope. Identify extent of use of this checklist.

3. Project Name. Name of Project or Application

4. Date of Review. Date review actually took place

5. Type of Review. Identify review in which checklist applies

6. Duration of Review. Actual time elapsed during review

7. Release or System Change Request (SCR) Numbers. Release identifier or SCR numbers reviewed

8. Review Participants. Include full name and role in the review (i.e., review coordinator, moderator, software quality assurance (SQA) representative, etc).

9. Questions. Questions should be posed to require a “yes/no” response. “Yes/no” questions should be presented so that all “yes” answers indicate successful completion of a task and “no” a lack thereof.

Sample Questions:
GENERAL
1. Was written notification provided at least three (3) working days prior to the review?YN
2. Was an agenda prepared?YN
3. Were scheduled facilities adequate?YN
4. Was a review package prepared?YN
5. Were the participants notified of review materials location at least three (3) working days in advance?YN
6. Was a review checklist prepared?YN
7. Was the review agenda followed?YN
8. Was the review checklist completed?YN
9. Did the Recorder take minutes of the meeting?YN
10. Did the Recorder distribute minutes of the meeting?YN
11. Did the Review Coordinator summarize review findings?YN
12. Were open/action items identified?YN
13. Did the Recorder prepare the review report?YN
14. Did the Recorder distribute the review report?YN
15. Were the review metrics recorded in the metrics repository?YN
16. Were open/action items tracked to resolution?YN
17. Were Release Quality Findings/Recommendations: (List Release program trouble reports (PTRs) Action Items (Responsibility and Completion Date) discussed during PTR?YN
18. Were Customer Support Findings/Recommendations: Action Items (Responsibility and Completion Date) discussed during PTR?YN
19. Were Training Findings/Recommendations: Action Items (Responsibility and
Completion Date) discussed during PTR?YN
20. Were User Documentation Findings/Recommendations: Action Items (Responsibility and Completion Date) discussed during PTR?YN
21. Were Overall Release Findings/Recommendations: Action Items (Responsibility and Completion Date) discussed during PTR?YN
FUNCTIONAL REQUIREMENTS
22. Have requirements in all categories (functional, regulatory, user interface, performance, interface, infrastructure, security, user training) been adequately defined, analyzed, and documented?YN
23. Do the requirements, as documented, reflect appropriate functional mandates specified in the Federal Financial Management Regulations (FFMRs) and “A Guide to Federal Requirements for Financial Management Systems (commonly called the Blue Book)?YN
24. Do the requirements, as documented, comply with the release plan?YN
25. Are adequate security and information assurance requirements identified? Do they comply with the requirements of the DoD Information Technology Security Certification and Accreditation Process (DITSCAP)?YN
26. Are risks identified and mitigation plans in place?YN
27. Have requirements adequately been traced back to the System Requirements Specification (SRS)?YN
28. Has sufficient attention been placed on the human factors?YN
29. Does the design team feel the Software Requirements Description (SRD) is complete, consistent, and unambiguous enough to create a complete design?YN
30. Does the test team feel the requirements contained in the SRD are unambiguous and testable?YN
31. Is the application using DFAS standard data elements?YN
32. Does the application’s operational, systems, and technical architecture comply with those at the enterprise level?YN
33. Have the Oracle Designer quality checking reports been run and have deficiencies been addressed?YN
34. Are ther

Read more on PR Newswire via Yahoo! Finance

One can now find software associates specializing in just one particular area or subject so that you get the best on that subject from them. They try their best to get an in-depth knowledge in your area of work so that they can concentrate more on the needs of the subject and bring prospective changes to help you. For example if you are involved in hospital management then you can find software experts specializing in hospital technology. They would have researched and studied all your needs and requirements and will easily be able to provide you with what is appropriate for your needs and requirement in the managing of the hospital smoothly. Like wise take any field and you may be able to find software specialist for them.

The technological advance in software industry has made us watch number of functions and activities being regulated into one system and performed by it very smoothly. It takes over the manual labor of many people and is also capable of doing multiple functions at the same time The installation of software systems are behind many a successfully run business. It has substantially lowered the time gap between the completions of many activities. It can help you keep track and record of almost all your business activities. Any document or details you need about your business can be had in a matter of seconds.

The software technology makes it possible to give any business a new look and entirely different dimension.

The most dedicated and experienced of software associates will help you find what you are looking for and more. They will know your business as well as you so you would not have to spend time teaching them what your business activities are like. So if you choose specialists in your field of work then you can expect to get the best of software technology that money can buy.

You can get a customized system just to work for your needs and inculcate into your business exactly as you want to, all because of what a few associates worked hard to perfect. And when they think of new things to be included they will notify you to update your system.