Communications of the ACM
The software engineering laboratory: an operational software experience factory
ICSE '92 Proceedings of the 14th international conference on Software engineering
Using event contexts and matching constraints to monitor software processes
Proceedings of the 17th international conference on Software engineering
Decentralised process enactment in a multi-perspective development environment
Proceedings of the 17th international conference on Software engineering
How to deal with deviations during process model enactment
Proceedings of the 17th international conference on Software engineering
A framework for formalizing inconsistencies and deviations in human-centered systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
Software process validation: quantitatively measuring the correspondence of a process to a model
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software Engineering Standards
Software Engineering Standards
Inconsistency Handling in Multiperspective Specifications
IEEE Transactions on Software Engineering
Yeast: A General Purpose Event-Action System
IEEE Transactions on Software Engineering
Provence: A Process Visualisation and Enactment Environment
ESEC '93 Proceedings of the 4th European Software Engineering Conference on Software Engineering
Analyzing Inconsistent Specifications
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Applying refinement calculi to software process modelling
ICSP '96 Proceedings of the Fourth International Conference on the Software Process (ICSP '96)
Managing Requirements Inconsistency with Development Goal Monitors
IEEE Transactions on Software Engineering
2nd international workshop on living with inconsistency
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
2nd international workshop on living with inconsistency (IWLWI01)
ACM SIGSOFT Software Engineering Notes
TRAM: a tool for requirements and architecture management
ACSC '01 Proceedings of the 24th Australasian conference on Computer science
The REVERE Project: Experiments with the Application of Probabilistic NLP to Systems Engineering
NLDB '00 Proceedings of the 5th International Conference on Applications of Natural Language to Information Systems-Revised Papers
Consistency Management of Financial XML Documents
CAiSE '01 Proceedings of the 13th International Conference on Advanced Information Systems Engineering
A Foolish Consistency: Technical Challenges in Consistency Management
DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Journal of Systems and Software
ViewPoints: meaningful relationships are difficult!
Proceedings of the 25th International Conference on Software Engineering
Information management
Compliance Flow - Managing the compliance of dynamic and complex processes
Knowledge-Based Systems
Efficient online monitoring of web-service SLAs
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Checking structural integrity for metadata repository systems by means of description logics
DASFAA'10 Proceedings of the 15th international conference on Database systems for advanced applications
Hi-index | 0.00 |
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.