Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
The synthesis of complex systems
IEEE Spectrum
Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Analysis patterns: reusable objects models
Analysis patterns: reusable objects models
Object models (2nd ed.): strategies, patterns, and applications
Object models (2nd ed.): strategies, patterns, and applications
Determining role rights from use cases
RBAC '97 Proceedings of the second ACM workshop on Role-based access control
Pattern languages of program design 3
Building systems using analysis patterns
ISAW '98 Proceedings of the third international workshop on Software architecture
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The unified software development process
The unified software development process
Data Model Patterns: Conventions of Thought
Data Model Patterns: Conventions of Thought
CODASYS: a consulting tool for novice database designers
ACM SIGMIS Database
Object Analysis Patterns for Embedded Systems
IEEE Transactions on Software Engineering
An analysis of modeling flaws in HL7 and JAHIS
Proceedings of the 2005 ACM symposium on Applied computing
Facilitating change management with configurative reference modelling
International Journal of Information Systems and Change Management
Information Technology and Management
An analysis pattern for invoice processing
Proceedings of the 16th Conference on Pattern Languages of Programs
Composing analysis patterns to build complex models: flight reservation
Proceedings of the 16th Conference on Pattern Languages of Programs
A rule-based analysis method for cooperative business applications
GCC'05 Proceedings of the 4th international conference on Grid and Cooperative Computing
Conceptual modelling patterns for roles
Journal on Data Semantics V
| Hi-index | 0.00 |
The development of object-oriented software starts from requirements expressed commonly as Use Cases. The requirements are then converted into a conceptual or analysis model. Analysis is a fundamental stage because the conceptual model can be shown to satisfy the requirements and becomes the skeleton on which the complete system is built. Most of the use of software patterns until now has been at the design stage and they are applied to provide extensibility and flexibility. However, design patterns don't help avoid analysis errors or make analysis easier. Analysis patterns can contribute more to reusability and software quality than the other varieties. Also, their use contributes to simplifying the development of the analysis model. In particular, a new type of analysis pattern is proposed, called a Semantic Analysis Pattern (SAP), which is in essence a miniapplication, realizing a few Use Cases or a small set of requirements. Using SAPs, a methodology is developed to build the conceptual model in a systematic way.