 |
A Practical Guide to
|
Management Control and Quality
Built In Quality, Achieved
No More Failed Projects, Lost Revenue!!
Highlights/Benefits:
-
Explains how to manage and control information technology development projects.
-
Defines software and firmware configuration management within the system development process.
-
Explains what it is and clarifies terminology in plain language.
-
Incorporates firmware configuration management.
-
Introduces the specification of a database system a controlled item.
-
Explains how S/FCM supports Total Quality Management (TQM).
-
Incorporates CASE and Software Library automation and support.
-
Identifies S/FCM system policy and procedures (and sign-off responsibility).
-
Discusses Object Oriented and Structured Methodologies.
-
Identifies who is responsible for each S/FCM activity.
-
Removes the confusion of S/FCM being considered Data Management or just Documentation.
-
Presents how the Small Business tailors S/FCM.
-
Presents Customer/User acquisition requirements.
Examples of Projects that Failed due to the lack of (S/FCM):
-
A Fortune 500 company lost millions of contract dollars because there was no coordinated effort to specify and document requirements (also accepted changes verbally and by telephone)
-
Several companies did not establish baselines for a product to control technical requirements and development costs (overruns)
-
A small company lost thousands and a large company lost millions of dollars by not specifying database systems on projects
-
A computer manufacturing company paid out of its capital to produce a prototype to satisfy a customer because of undocumented agreements and requirements
-
A company lost control of documentation and on-line versions of software and data because of not implementing a configuration control process
-
A Quality Assurance engineer overlooked critical parts of a specification (configuration documentation) because the criteria for review was not emphasized in the standard used as a guide and reference
-
A company did not prepare requirements and design documentation until a product was produced. Impacted development, test and rework costs, and quality
Future problems were corrected and mistakes prevented from reoccurring with an effective S/FCM system. Why is configuration management identified in International (ISO) and Department of Defense standards? Why are some commercial companies beginning or want to use S/FCM? Why, because S/FCM is an Engineering and Management tool and method, a disciplined activity that Builds in Quality.