Abstract
The user/purchaser of software products makes investments of resources in software as one of the means for improving its own products and business.The level of improvement obtained depends, among other factors, on the quality level of the acquired software. Making reference to the relevant standard, normative and methodological documents, the paper illustrates how the quality level of the subcontracted software depends not only on the quality of the software supplier's process, but also on the quality of purchaser/user's own production/business processes. Being the purchaser/user the primary responsible of the preparation of the software requirements, which specify why the purchaser wants to invest in software, and what the software must do to improve the purchaser's products or purchaser's business process, the paper highlights the quality management activities which have to be performed by the purchaser, or monitored on the side of the supplier, in order to ensure a successful achievement of the purchaser's business goals.
Preview
Unable to display preview. Download preview PDF.
References
AICQ Italia CentroNord — A. Salvini, docente — Text in support of the course on “Process Control” (Milano, October 18–19, 94)
AIPA, Autorità per l'Informatica nella Pubblica Amministrazione — Circolare 5 agosto 1994, n.AIPA/CR/5 — Gazzetta Ufficiale della Repubblica Italiana, n.191, 17-8-1994
ami (application of metrics in industry), Handbook — A quantitative approach to software development — The ami consortium, c/o The ami User Group, CSSE, South Bank University, 103 Borough Road, London SE1 OAA
A. Combelles-Quantitative Approach to Software Process Improvement-Springer Verlag, Proceedings of Objective Quality 1995, The 2nd Symposium on Software Quality Techniques and Acquisition Criteria, Florence, Italy, May 29–31, 1995
Basili, V. and Weiss, D. M. — A methodology for Collecting Valid Software Engineering Data — IEEE Transactions on Software Engineering, 1984
ESA PSS-05-0 Issue 2, February 1991 — European Space Agengy Procedures, Specifications, and Standards for Software Enginering, Issue 2
ESA PSS-05-02 — European Space Agengy, Guide to the User Requirements Definition Phase
ESA PSS-05-03 Issue 1, October 1991 — European Space Agengy, Guide to the Software Requirements Definition Phase
IEEE Std 829-1983, Standard for Software Test Documentation
IEEE Std 830-1993, Recommended Practice for Software Requirements Specifications
IEEE Std 982.1-1988, Standard Dictionary of Measures to Produce Reliable Software
IEEE Std 982.2-1988, Guide for the Use of Standard Dictionary of Measures to Produce Reliable Software
IEEE Std 1044-1993, Standard Classification for Software Anomalies
ISO 8402:1994 Quality management and quality assurance — Vocabulary
ISO 9000-1:1994 Quality management and quality assurance standards — Part 1: Guidelines for selection and use.
ISO 9000-3:1991 Quality management and quality assurance standards — Part 3: Guidelines for the application of ISO 9001 to the development, supply and maintenance of software
ISO 9001:1994 Quality systems — Model for quality assurance in design, development, production, installation and servicing
ISO 9004-1:1994 Quality management and quality system elements — Part 1: Guidelines
ISO 9004-4:1994 Quality management and quality system elements — Part 4: Guidelines for quality improvement
ISO/IEC 9126:1991 — Information Technology — Software Product Evaluation — Quality characteristics and guidelines for their use
NIST (National Institute of Standards and Technology) — FIPS PUB 64, Guidelines for Documentation of Computer Programs and Automated Data Systems for the Initiation Phase, 1979
NIST (National Institute of Standards and Technology) — FIPS PUB 65, Guideline for Automatic Data Processing Risk Analysis, 1979
Nocentini, S. Il sistema di qualità del software. Il processo di pianificazione, realizzazione e controllo.-ETASLIBRI, Collana di Informatica, 1993
Paulk, M. C. and others — SEI-93-TR-024 — Capability Maturity Model for Software, Version 1.1 — Software Engineering Institute, Pittsburgh, PA
Paulk, M. C. and others — SEI-93-TR-025 — Key Practices of the Capability Maturity Model, Version 1.1 — Software Engineering Institute, Pittsburgh, PA
SCE Staff — SEI-94-TR-006 — Software Capability Evaluation, Version 2.0, Method Description — Software Engineering Institute, Pittsburgh, PA
Kang, K. C. and Christel M. G. — SEI-92-TR-012 — Issues in Requirements Elicitation — Software Engineering Institute, Pittsburgh, PA
Higuera, R. P. and others — SEI-94-SR-001 — An introduction to Team Risk Management — Software Engineering Institute, Pittsburgh, PA
SPICE project (Software Process Improvement &Capability dEtermination) — Tutorial, at Fourth European Conference on Software Quality, October 17–20, 94, Basel, Switzerland
SPICE project — Baseline Practices Guide — Version 1.00, September 1, 94 — Doc Ref BPG/TP/BPG — (Document in internal use in SPICE Project)
T. Coletta —The SPICE Project: An ISO Standard for Software Process Assessment, Improvement and Capability Determination — Springer Verlag, Proceedings of Objective Quality 1995, The 2nd Symposium on Software Quality Techniques and Acquisition Criteria, Florence, Italy, May 29–31, 1995
Zultner, R. E. — Software Quality Function Deployment: Why, What, and How — Tutorial, at Fourth European Conference on Software Quality, October 17–20, 94, Basel, Switzerland
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1995 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Cicu, A. (1995). Process quality problems from the point of view of the user and of the purchaser of software. In: Nesi, P. (eds) Objective Software Quality. SQ 1995. Lecture Notes in Computer Science, vol 926. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-59449-3_30
Download citation
DOI: https://doi.org/10.1007/3-540-59449-3_30
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-59449-9
Online ISBN: 978-3-540-49268-9
eBook Packages: Springer Book Archive