The Z notation: a reference manual
The Z notation: a reference manual
IEEE Transactions on Software Engineering
Exploiting style in architectural design environments
SIGSOFT '94 Proceedings of the 2nd ACM SIGSOFT symposium on Foundations of software engineering
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
ICSE '94 Proceedings of the 16th international conference on Software engineering
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Specification Case Studies
A Study of 12 Specifications of the Library Problem
IEEE Software
An object-oriented modeling method for algebraic specifications in CafeOBJ
ICSE '97 Proceedings of the 19th international conference on Software engineering
A pedagogical view on software modeling and graph-structured diagrams
ICSE'05 Proceedings of the 2005 international conference on Software Engineering Education in the Modern Age
Hi-index | 0.00 |
A number of modeling methods have been proposed and practiced for the analysis process of software development. As many modeling methods cover the design process as well, it would be natural to ask how those methods affect the critical decisions made during the transition phase from the analysis to the architectural design, but little research activities seem to be visible tackling this problem. The reasons might be the difficulties of finding an appropriate approach and an appropriate comparison framework. We take an approach of analyzing a set of case studies that treat a common example problem and use a formal method to clarify critical design issues. This paper reports some significant results obtained by the analysis of example problem solutions, based on a formally described comparison framework.