Communications of the ACM
A proposal for a formal model of objects
Object-oriented concepts, databases, and applications
The object-oriented systems life cycle
Communications of the ACM
Object-oriented design
Object lifecycles: modeling the world in states
Object lifecycles: modeling the world in states
Object-oriented modeling and design
Object-oriented modeling and design
Beyond programming: to a new era of design
Beyond programming: to a new era of design
Estimating understandability of software documents
ACM SIGSOFT Software Engineering Notes
Subject-oriented design: towards improved alignment of requirements, design, and code
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Software Engineering with ADA
Representing Software Engineering Knowledge
Automated Software Engineering
The Semantics of Parts Versus Aggregates in Data/Knowledge Modelling
CAiSE '93 Proceedings of Advanced Information Systems Engineering
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Knowledge Sharing: Agile Methods vs. Tayloristic Methods
WETICE '03 Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
Requirements Engineering and Agile Software Development
WETICE '03 Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
A conceptual model completely independent of the implementation paradigm
Journal of Systems and Software - Special issue: Best papers on Software Engineering from the SEKE'01 Conference
The Knowledge Engineering Review
MDA Distilled
Software Architecture to Support Domain Semantics Representation
SWSTE '05 Proceedings of the IEEE International Conference on Software - Science, Technology & Engineering
On tool selection for illustrating the use of UML in system development
Journal of Computing Sciences in Colleges
Hi-index | 0.00 |
Software systems embed in them knowledge about the domain in which they operate. However, this knowledge is "latent". Making such knowledge accessible could be of great value to the organization both as a source of explicit knowledge and to systems development and maintenance. We propose a framework aimed at making domain knowledge embedded in software explicit. The framework is based on identifying domain knowledge acquired during the development process (especially in requirements analysis) and formalizing it. The software architecture is then partitioned into two parts: one represents the domain knowledge and the other responsible for the actual processing (using this knowledge). A specific object-oriented design approach is suggested to accomplish this partitioning.