System Software Process and Quality Factors
Essay Preview: System Software Process and Quality Factors
Report this essay
System/Software Process and Quality Factors
CMGT 555 / Systems Analysis and Development
March 6, 2006
Quality Factors
System quality factors are important to both hardware and software applications. Several factors must be considered when addressing hardware and software quality. Factors such as functionality, reliability, usability, efficiency, maintainability, and portability are among the considerations. Functionality and reliability quality factors can potentially affect other components of system quality. Thorough quality assurance programs can help ensure quality and overall system efficiency.
System functionality can save organizations time and money by creating and advancing efficient quickly operating systems. Functionality allows organizations to maximize efficiency and cost-effectiveness within lean operating budgets (Wimmer, 2005) Legacy systems fail to meet most organizations functionality needs. Systems that do not function properly create extra hours of work, slow transactions, expand timelines and generally cost organizations money. Improving functionality to meet an organizations needs is the responsibility of both the design team and organization. The organization must provide specification requirements, and the design team must elicit this information. Properly identifying functionality needs will assist in designing a quality system.
System reliability is of the utmost importance. Functionality is important. However, if the system is not reliable functionality will become a secondary concern. Reliability issues that arise in both hardware and software can have far-reaching implications. System reliability issues mirror some environmental issues (Neumann, 2006):
Dangerous contaminants may emerge and propagate, often unobserved
Detection, remediation, and prevention require a cooperative effort
Short sighted reasoning generally impedes long-term planning
When something goes wrong, resolutions are typically difficult
Reliability should be addressed during the design stage and continually reevaluated throughout the implementation and test and turn up functions. System functionality and system reliability are important building blocks for a quality operating system.
The Telecom industry addresses functionality by addressing a customers needs and building and adapting a system to fit those needs. Reliability in the Telecom industry tends to be redundancy when considering hardware. Software within the transport equipment is all redundant. Systems are typically backed up and diverse route designs are implemented. Considering functionality and reliability issues allows the Telecom industry to provide efficient and reliable services to customers. Customers benefit from such thorough designs and both organizations are successful in obtaining their goals.
Capability Maturity Model
The SEI Capability Maturity Model (CMM) assists in refining the system development process. The CMM provides a method for evaluating the maturity of the software development process using a scale of 1 to 5 (Wikipedia, n.d.). The more effective the system development process, the higher the organizations score. The CMM provides the following advantages towards the system development process (Wikipedia, n.d.):
a place to start
the benefit of a communitys prior experiences
a common language and a shared vision
a framework for prioritizing actions
a way to define what improvement means for your organization
A system development process using the tools and advantages provided by the CMM will have a better chance of success. An important step for any organization is to truly identify where it ranks on the maturity scale. This understanding will allow the organization to make adjustments accordingly and improve its system development process overall.
Assessment of where a company stands on the CMM scale can be categorized as follows:
Level 1 Initial – processes are not clearly defined and the organization lacks a stable environment. Frequent problems that arise at this level is budgeting issues and the inability to maintain a strict timeline.
Level 2 Repeatable – at this level, organizations are able to repeat previous successes. Basic project management for costs tracking and schedule are evident.
Level 3 Defined – processes are described in standards, procedures, tools and methods. These standards are improved upon over time.
Level 4 Managed – Precision in processes allow management to control the development effort. Management can find ways to adjust to new projects without significant loss of quality.
Level 5 Optimizing – continually improves processes by both incremental and innovative technological advancements.
The CMM is not used within my work group at AT&T. From the projects I have been involved with, I would give AT&T a 3 on the CMM rating scale. Processes are typically defined, yet the initial definition is rarely detailed. Processes tend to be worked out in the middle of a project. As a result, some design specifications and scheduling adjustments are required. An outline of the project is provided. This outline is generally gathered from existing information gained from