The Z notation: a reference manual
The Z notation: a reference manual
Knapsack problems: algorithms and computer implementations
Knapsack problems: algorithms and computer implementations
Constraint diagrams: visualizing invariants in object-oriented models
Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
IEEE Software
Seven More Myths of Formal Methods
IEEE Software
An Overview of RoZ: A Tool for Integrating UML and Z Specifications
CAiSE '00 Proceedings of the 12th International Conference on Advanced Information Systems Engineering
A Formal Mapping between UML Models and Object-Z Specifications
ZB '00 Proceedings of the First International Conference of B and Z Users on Formal Specification and Development in Z and B
Visualization of Formal Specifications
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
Program slices: formal, psychological, and practical investigations of an automatic program abstraction method
An empirical study of slice-based cohesion and coupling metrics
ACM Transactions on Software Engineering and Methodology (TOSEM)
Concept location in formal specifications
Journal of Software Maintenance and Evolution: Research and Practice
Software engineering and formal methods
Communications of the ACM - Enterprise information integration: and other tools for merging data
Derivation of UML class diagrams as static views of formal b developments
ICFEM'05 Proceedings of the 7th international conference on Formal Methods and Software Engineering
The exterminators [software bugs]
IEEE Spectrum
| Hi-index | 0.00 |
Due to their accuracy in describing systems, formal specifications can play an important role during forward as well as reverse engineering activities. However, besides dense mathematical expressions, their lack in visually appealing notations impedes their use and exchange among different stakeholders. One solution to this problem is to enrich the specification by other views, in most cases Unified Modelling Language (UML) diagrams. But the mapping is not trivial, and existing approaches have their impediments, among them the assignment of methods to classes--which has to be re-done by hand quite often. By the example of Z, this paper demonstrates that the situation can be improved. The new approach combines existing mapping strategies, but additionally lets the assignment of methods rest on quality-related measures. The basic idea is to balance the values of coupling for all methods within and between the UML classes. With that, two issues are addressed: firstly, the mapping of sets, types, and operations (to UML classes and UML methods) is based on reproducible measures that are intuitively comprehensible. Secondly, implementations based on the resulting UML class diagrams very likely also have comparable quality-related properties.