Many companies claim to adhere to standards for software project development. This is often used as a marketing tool when eliciting business. But how does the customer or project manager know that these standards are being completely and consistently applied in their projects? In the paper ‘Managing standards compliance’ [http://www.cs.ucl.ac.uk/staff/w.emmerich/publications/TSE/stdscompl.html] we identify this problem and describe a support environment to provide identification and correction of non-compliance to standards. This paper details the experiences gained while implementing such a tolerant support system.
KeywordsCompliance Quality Requirements engineering Requirements management Software standards
Unable to display preview. Download preview PDF.
- 1.Stevens R, Brook P, Jackson P, Arnold S. Systems engineering. Prentice-Hall, Hemel Hempstead, UK, 1998.Google Scholar
- 2.Sommerville, I. Software engineering (5th edn). Addison-Wesley, Wokingham, UK, 1995Google Scholar
- 3.Mazza C, Fairclough J, Melton B, De Pablo D, Scheffer A, Stevens R. Software engineering standards. Prentice-Hall, Hemel Hempstead, 1994Google Scholar
- 5.Emmerich W, Finkelstein A, Montangero C, Antonelli S, Armitage S, Stevens R. Managing standards compliance. http://www.cs.ucl.ac.uk/staff/w.emmerich/publications/TSE/stdscompl.html IEEE Transactions on Software Engineering in 1999 (to appear)Google Scholar
- 6.Quality Systems and Software Ltd. DOORS reference guide (v4.0), Oxford, 1998Google Scholar
- 7.Quality Systems and Software Ltd. DXL reference (v4.0), Oxford, 1998Google Scholar
- 8.Cohen D. AP5 reference manual. http://www.isi.edu/software-sciences/relab/ap5/refman.html, 1992Google Scholar