Iso 9000-3 for software development

Thus, they are more complex. When one of the authors of this book went from being an aircraft designer to a computer architect in , he was confronted by the complexity of the then newly developing multiprocessor computer.

In it, this Canadian professor of English literature stated that a supersonic air transport plane is far simpler than a multiprocessor computer system. This was an amazing insight for a professor of English literature, but he was correct.

One of the authors of this book worked on the structural optimization of the Concorde and on a structural aspect of the swing-wing of the Boeing SST. In he was responsible for making the Univac function as a three-way multiprocessor.

Every night at midnight he reported to the Univac test floor in Roseville, Minnesota, where he was assigned three mainframe computers. He connected the new multiprocessor CRT console he had designed and loaded a copy of the Exec 8 operating system modified for this new functionality. Ten times in a row the OS crashed at a different step of the bootstrap process. He began to wonder if this machine were a finite automaton after all. Of course it was, and the diverse halting points were a consequence of interrupt races, but he took much comfort from reading Marshall McLuhan.

Today, highly parallel machines are commonplace in business, industry, and the scientific laboratory—and they are indeed far more complex than supersonic transport aircraft none of which are still flying now that the Concorde has been taken out of service.

Software is different. Few potential problems can be detected in testing due to the complexity difference between software and hardware. None of them can be corrected by tuning the manufacturing process, because software has no manufacturing process!

Making copies of eight CD-ROMs for shipment to the next customer along with a box of installation and user manuals offers little chance for fine-tuning and in any case introduces no variability. It is more like book publishing, in which you can at most slip an errata sheet into the misprinted book before shipping, or, in the case of software, an upgrade or fix-disk. So, what is the solution? Our contention is that because errors in software are almost all created well upstream in the design process, and because software is all design and development, with no true manufacturing component, everything that can be done to create bug-free software must be done as far upstream in the design process as possible.

Hence our advocacy of Taguchi Methods see Chapters 2, 15, and 17 for robust software architecture. Software development is an immensely more taxing process than hardware development. Although there is no silver bullet, we contend that the Taguchi Methods described in the next chapter can be deployed as a key instrument in addressing software product quality upstream at the design stage. Processes are often described as having upstream activities such as design and downstream activities such as testing.

This book advocates moving the quality-related aspects of development as far upstream in the development process as possible. The RSDM presented in this book provides a powerful framework to develop trustworthy software in a time- and cost-effective manner. This introductory chapter is an overview of the software development situation today in the view of one of the authors. We have tried in this chapter to indicate when we are speaking from personal experience and sharing our personal opinions, and when we are referring to the experience of others.

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time. Pearson Education, Inc. This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies. To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:.

For inquiries and questions, we collect the inquiry or question, together with name, contact details email address, phone number and mailing address and any other additional information voluntarily submitted to us through a Contact Us form or an email.

We use this information to address the inquiry and respond to the question. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law. If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information informit.

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email.

Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature. We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

This standard contributes to the following Sustainable Development Goal :. CHF Buy. Life cycle Previously Withdrawn. Final text received or FDIS registered for formal approval. Proof sent to secretariat or FDIS ballot initiated: 8 weeks.

Close of voting. Proof returned by secretariat. Prevent records from being altered without approval. Safeguard records from damage or deterioration. Your quality record keeping system should:. Show that your quality system is implemented. Prove that your quality system works properly.

Specify how long old records should be retained. Allow information to be retrieved without difficulty. Produce documents that are dated and easy to read.

Permit customers to access records when required. Include quality records provided by subcontractors. Software quality records Software quality records are documents and files that prove that quality activities were performed and quality results were achieved. Quality records document the actual performance of your quality system. They document the past. Quality records can include reports, minutes, requisitions, approvals, annotations, reviews etc.

Specify how long you plan to retain electronic records. Make sure that retention times consider how fast your electronic media is likely to degrade. Make sure that retention times consider how long the required hardware and software is likely to be available. Develop internal audit procedures Develop internal quality audit procedures which:.

Determine whether quality activities and results comply with written quality plans, procedures, and programs. Evaluate the performance of your quality system. Verify the effectiveness of your corrective actions. These procedures should also ensure that:.

Audit activities are properly planned. Auditors are independent of the people whose activities are being audited. Audit results, corrective actions, and corrective action results and consequences are properly recorded. Audit conclusions are discussed with the people whose activities and results are being audited, and deficiencies are corrected by the managers of the audited areas.

Audit reports are fed back into quality system review process Develop an internal audit plan for your software projects Develop an internal audit plan. Identify the software projects you plan to audit. Select the stages that will be audited for each project. Define your audit schedule. Your internal audits should ensure that the quality plans, that control your software projects, do not contradict your organization's quality system requirements.

Develop training procedures Develop quality-training procedures. These procedures should be properly documented, and must ensure that:.

Quality system training needs are identified. Quality training is provided to those who need it. People are able to perform quality system jobs. People have the qualifications they need to do the work.

Accurate and appropriate training records are kept. Everyone understands how your quality system works. To manage software development projects. Identify your training needs by studying how software will be developed and managed.

Study the tools, techniques, methods, and resources that will be used during software development. Study the field or area that will be the focus of your software product e.

Document the training needs that must be met. Document the qualifications that must be met. Deliver the training that will be needed: To develop your software products. To manage your software development projects. Develop service procedures Develop and document quality service procedures.

Your procedures should specify how:. Products should be serviced. Product service activities are reported. The quality of product service is verified. Develop software maintenance procedures Develop procedures to control your software maintenance process. Your software maintenance procedures should:. Control the maintenance of your software programs. Control the detection of software problems. Control the analysis of problems and causes. Control the correction of software problems. Control the decision to use temporary fixes.

Control the decision to develop permanent fixes. Control how you verify the maintenance process. Control the maintenance of software documentation. Control the maintenance of data and data structures. Control the maintenance of software test plans. Control the maintenance of software specifications. Control the maintenance of customer documents. Control the maintenance of user documents.

Control the maintenance of development environment. Control the maintenance of development tools. Develop software maintenance plans Develop plans to control your software maintenance projects.

Your software maintenance plans should:. Define the scope of your maintenance activities. Control how the product's initial status is described. Identify who will support the maintenance process. Specify the maintenance activities that will be done. Describe the records and reports that will be kept.

Keep software maintenance records Keep a record of your software maintenance activities. For each software product:. Record the problems that have been reported. Record the current status of each problem. Record who is responsible for solving each problem. Record the corrective actions that should be taken. Record the priority assigned to each corrective action. Record the results achieved by each corrective action.

Record statistical maintenance data. Use your software maintenance records to: Evaluate and improve your software products.

Evaluate and improve the performance of your quality system. Process capabilities. Product characteristics. Explain how your techniques should be applied. Monitor and control how these techniques are used. Make sure that:. All statistical procedures are documented. Statistical records are kept. Analyze process and product qualities Use statistical techniques to:. Analyze software development process characteristics. Analyze software product characteristics. Use statistical data to evaluate process and product quality.

Evaluate software process characteristics qualities. Evaluate process maturity. Evaluate process outputs. Evaluate output defects. Evaluate defect resolutions. Evaluate milestone slippage.

Evaluate other process characteristics. Evaluate software product characteristics qualities. Evaluate product testability. Evaluate product usability. Evaluate product reliability. Evaluate product suitability. Evaluate product availability. Evaluate product upgradeabilty. Evaluate product maintainability. Evaluate other product characteristics. Select useful metrics Use effective metrics measurable characteristics.

Use metrics that are clearly defined. Use metrics that apply to software. Use metrics that apply to software development. Use metrics that apply to software products. Use metrics that are appropriate to your situation. Use metrics that apply to your development process. Use metrics that apply to your software products.

Use metrics that measure quality improvement. Use metrics to measure process quality improvement. Use metrics to measure product quality improvement. Use metrics that add value to process and products. Use metrics that add value to software development. Use metrics that add value to software products. It was replaced by ISO Home Page. Our Libraries. A to Z Index. How to Order. Our Products.

Our Prices. Praxiom Research Group Limited help praxiom. Updated on November 29, First published on July 9, Legal Restrictions on the Use of this Page Thank you for visiting this webpage. You are welcome to view our material as often as you wish, free of charge. And as long as you keep intact all copyright notices, you are also welcome to print or make one copy of this page for your own personal, noncommercial , home use. But, you are not legally authorized to print or produce additional copies or to copy and paste any of our material onto another web site or to republish it in any way.

All Rights Reserved. When appropriate, these procedures should make sure that you: Identify and document products every step of the way from the purchase of supplies and materials through all stages of handling, storage, production, delivery, installation, and servicing.

Configuration management methods may be used to: Identify software versions, changes, and status. Define your software configuration by identifying: Product structures. Use configuration management to control items Use configuration management methods to: Control documents and data. Develop procedures to ensure that every software item can be matched up with every related: Hardcopy document. These procedures should allow you to: Record software changes and status. Your plan should: Identify the organizations that will be involved in the configuration management process.

Your procedures must be documented, and should ensure that each process is: Approved and performed by qualified personnel. Your procedures should ensure that each process: Maintains a high standard of workmanship. Use these procedures to: Control the identity of software masters and copies.

Use these procedures to: Control how tests and analyses will be performed. Use these procedures to: Control how installation duties and responsibilities will be divided up between you and your customer.

Ensure that your customer will provide the necessary: Personnel. Your software test plans should: List your test objectives. Your procedures should ensure that: Final products are inspected and approved before they are made available for sale. These tests should: Prove that your software product meets the customer's contractual requirements. Your tests should: Prove that the validated product meets the customer's contractual requirements. Help your customer to: Define the testing procedure.

Your record keeping system should: Prove that your products have been formally inspected and tested using authorized procedures. Your procedures should specify: What kinds of measurements must be made. Your procedures should ensure that: Calibration methods are clearly defined. These procedures should ensure that: Each and every product is identified as having passed or failed the required tests and inspections. Distinguish between: Untested software. Make sure these products are: Identified, evaluated, and documented.

Nonconforming software may be: Rejected, or Repaired, or Accepted: Accepted with repairs. Ensure that: Nonconformity reports are handled properly.

Your procedures must: Use every appropriate source of information to detect potential nonconformities. Use sources such as: Work activities and processes. Consider the following methods: Perform regular software back-ups.

Develop procedures to: Collect and record this information create records. Your quality record keeping system should: Show that your quality system is implemented. These procedures should also ensure that: Audit activities are properly planned. Your plan should: Identify the software projects you plan to audit. These procedures should be properly documented, and must ensure that: Quality system training needs are identified.

Your procedures should specify how: Products should be serviced. Your software maintenance procedures should: Control the maintenance of your software programs. Your software maintenance plans should: Define the scope of your maintenance activities. For each software product: Record the problems that have been reported.

Make sure that: All statistical procedures are documented. Analyze process and product qualities Use statistical techniques to: Analyze software development process characteristics. Track your products. Develop and document procedures to identify and track products from start to finish. Identify and track your software products. Develop procedures to assign unique identifiers to software products and components.

Use configuration management to identify and track software items. Use configuration management methods to identify and track your software products and components. Use configuration management to control items. Use configuration management methods to: Control documents and data.

Configuration management accounting procedures. Develop configuration management accounting procedures to monitor and manage software status and changes. Configuration management plan. Develop a configuration management plan. Control production, installation, and servicing. Develop procedures to plan, monitor, and control your production, installation, and servicing processes. Control software replication process. Develop procedures to control the software replication process.

Control software release process. Develop procedures to control the software release delivery process. Control software installation process. Develop procedures to control the software installation process. Develop procedures to inspect, test, and verify that your products meet all specified requirements. Develop software test plans. Develop and document software test plans.