The Community for Technology Leaders
Green Image
<p><b>Abstract</b>—Software engineering standards determine practices that “compliant” software processes shall follow. Standards generally define practices in terms of constraints that must hold for documents. The document types identified by standards include typical development products, such as user requirements, and also process-oriented documents, such as progress reviews and management reports. The degree of standards compliance can be established by checking these documents against the constraints. It is neither practical nor desirable to enforce compliance at all points in the development process. Thus, compliance must be managed rather than imposed. We outline a model of standards and compliance and illustrate it with some examples. We give a brief account of the notations and method we have developed to support the use of the model and describe a support environment we have constructed. The principal contributions of our work are: the identification of the issue of standards compliance; the development of a model of standards and support for compliance management; the development of a formal model of product state with associated notation; a powerful policy scheme that triggers checks; a flexible and scalable compliance management view.</p>
Software processes, software engineering standards, software development environments, compliance, consistency management.
Stefano Antonelli, Anthony Finkelstein, Carlo Montangero, Wolfgang Emmerich, Stephen Armitage, Richard Stevens, "Managing Standards Compliance", IEEE Transactions on Software Engineering, vol. 25, no. , pp. 836-851, November/December 1999, doi:10.1109/32.824413
47 ms
(Ver 3.3 (11022016))