Capability Maturity Model at Array Systems Computing

Home
My Life
Resume
Transcript
Documents
Galleries
Code
E-Books
Resources
Greeting Cards
My University
IEEE
Pakistan Pics

Background:

Array Systems Computing (ASC) is a small software company developing highly specialized computer applications for some high profile government agencies and private companies. Being a small company, ASC does not tolerate many mistakes and therefore puts very high emphasis on the quality of its products.

CMM at Array Systems Computing

ASC practices a Compatibility Maturity Model (CMM) in it’s initial stages. It shows some CMM characteristics from maturity level two and level three. In this report we will take into consideration the company goals, process culture and frame work to report on its CMM maturity level.

Characteristics of level 2: the Repeatable Level

Level 2 means that a company has effective management processes institutionalized for software projects, which may allow it to repeat successful practices developed on earlier projects, although specific processes implemented by the project may differ. The typical characteristics of level 2 are discussed in the context of ASC.

·        The organization establishes policies and procedures for managing software projects based on the past experiences gained from other projects.

ASC has a system that defines the company policies and procedures. There is also a clear definition of employee titles and roles. Projects are assigned to well defined groups. Each group has a project manager to coordinate the project tasks, budget, time and functionality. Members of each group are chosen based on their knowledge and experiences gained from the past projects. So, if ASC gets a project similar to another done in the past, then the group chosen for the new project would likely be the same one that worked on the previous project.

·        Software project standards are defined and faithfully followed.

·        The software project managers track software cost, schedule and functionality. Problems in meeting commitments are identified when arise.

ASC does not have project standards defined as such for each project, neither is there a specific body or committee to see to the process compliance. There is, however, some general standards in place that apply to all projects equally. ASC has an internal Quality Assurance department (QA) that acts as a watch dog overlooking company operations, employee interactions, security issues, etc. But QA acts as a silent body and does not routinely audit company procedures and their compliance. QA comes into action only when something seriously goes wrong, such as if security is breached.

It is doubtful that the employees faithfully follow the project standards. “Things” at ASC go wrong fairly often. Though they are identified at some time before the project completion date. In such cases, employee roles and duties are set aside and CMM maturity level 1, ad hoc, process is implemented to try to put out the fire. And if “things” still go wrong, the project manager, who is responsible for the whole of the project, bears all the blame, which could lead to his/her reassignment to a different project or even job termination.

·        Realistic project commitments are based on the results observed on previous projects and on the requirements of the current project.

ASC makes very precise measurements of the budget and time needed for a certain project and generally it is successful at meeting these projections. However, it is unknown whether or not this method of calculation evolves as new experience is gained.

·        Baseline Software requirements are defined and the whole products developed to satisfy them, and to control their integrity.

·        The software project works with its subcontractors, if any, to establish a strong customer-supplier relationship.

ASC puts major emphasis on setting software requirements at the time the contract is signed. ASC prides itself in developing high quality products for its customers, some of whom are government defense agencies requiring top secrecy of the product and its design. Therefore, project privacy and security is considered very important. Customers are restricted from the company work areas. Hiring of screened individuals, electronic monitoring and oaths of confidentiality from employees are a standard procedure. Unfortunately, such circumstances do not leave much ground for good customer-supplier relationship.

Characteristics of Level 3: the Defined Level

ASC fulfills at least one clause from this level:

·        The organization documents the standard process for developing and maintaining software across the organization.

ASC shows a definite interest in the documentation of the standard procedures and software maintenance. Customer contracts and company guidelines require documentation. Such documentation is especially encouraged because of its importance in case things go wrong.

New ideas require documentation as well. And if the ideas are seen promising by the upper management then in depth proposal is asked for submission.

Conclusion

ASC deploys basic management procedures to track cost, schedule and functionality. The necessary process discipline is in place to repeat earlier success on the projects with similar applications. The planning and tracking of the software projects is stable. Software processes and development activities are documented. These characteristics put ASC at a stage between the CMM maturity level 2: the repeatable level, and level 3: the defined level.