Alcoa: the alloy constraint analyzer
Proceedings of the 22nd international conference on Software engineering
Software Development with Z: A Practical Approach to Formal Methods in Software Engineering
Software Development with Z: A Practical Approach to Formal Methods in Software Engineering
Systems testing and statistical test data coverage
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
Business-oriented constraint language
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Statistical constraints for EAI
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Modeling of architectures with UML panel
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Hi-index | 0.00 |
Statistical constraints have been introduced to UML models to describe their most salient aspects, allowing a natural expression of what is usually the case while tolerating exceptions. They are defined using well-known statistical constructs in terms of OCL collections. They offer more freedom and flexibility than the standard logical quantifiers ('exists' and 'forAll'). This is achieved in a way that is mathematically well formed so that such constraints can be interpreted and verified at run time when a system (represented by a UML model) has been deployed. To make the constraints intelligible to non-IT people, a grammar has been defined that supports more than one syntactic style. The syntax of OCL is supported in addition to other styles that are more accessible to persons without mathematical or computer-science training, and the styles can be mixed. The paper shows examples of statistical constraints, particularly in cases where application systems are being extended by the addition of new capabilities and a new software package for business-to-business (B2B) trading on the Internet. The scenarios involve setting up routing and transformations using a message broker with verification on both extracted and sample data. There are also examples of limiting the complexity of transformations by constraining their definitions.