The object-oriented systems life cycle
Communications of the ACM
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Object-oriented system development
Object-oriented system development
On the purpose of object-oriented analysis
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
Object-oriented development: the fusion method
Object-oriented development: the fusion method
Introduction—object-oriented design
Communications of the ACM
Beyond programming: to a new era of design
Beyond programming: to a new era of design
From object-oriented to goal-oriented requirements analysis
Communications of the ACM
Knowledge engineering and management: the CommonKADS methodology
Knowledge engineering and management: the CommonKADS methodology
Introductory paper: Reflections on conceptual modelling
Data & Knowledge Engineering
System Requirements Engineering
System Requirements Engineering
An Integrated Approach to Software Engineering
An Integrated Approach to Software Engineering
Elements underlying the specification of requirements
Annals of Software Engineering
Representing Software Engineering Knowledge
Automated Software Engineering
Contemporary Application-Domain Taxonomies
IEEE Software
Towards a General Purpose Approach to Object-Oriented Analysis
ISOOMS '94 Proceedings of the International Symposium on Object-Oriented Methodologies and Systems
The Semantics of Parts Versus Aggregates in Data/Knowledge Modelling
CAiSE '93 Proceedings of Advanced Information Systems Engineering
A framework supporting the utilization of domain knowledge embedded in software
ER '07 Tutorials, posters, panels and industrial contributions at the 26th international conference on Conceptual modeling - Volume 83
| Hi-index | 0.01 |
Several authors have pointed out that current conceptual models have two main shortcomings. First, they are clearly oriented to a specific development paradigm (structured, objects, etc.). Second, once the conceptual models have been obtained, it is really difficult to switch to another development paradigm, because the model orientation to a specific development approach. This fact induces problems during development, since practitioners are encouraged to think in terms of a solution before the problem at hand is well understood, thus anticipating perhaps bad design decisions.An appropriate analysis task requires models that are independent of any implementation issues. In concrete, models should support developers to understand the problem and its constraints before any solution is identified. This paper proposes such an alternative approach to conceptual modelling, called "problem-oriented analysis method".