UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
A Relational Approach to Defining Transformations in a Metamodel
UML '02 Proceedings of the 5th International Conference on The Unified Modeling Language
APSEC '00 Proceedings of the Seventh Asia-Pacific Software Engineering Conference
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Moving Toward Component-Based Software Development Approach
TOOLS '98 Proceedings of the Technology of Object-Oriented Languages and Systems
Maintaining Evolving Component-Based Software with UML
CSMR '03 Proceedings of the Seventh European Conference on Software Maintenance and Reengineering
Separation of Concerns in Model-Driven Development
IEEE Software
Applications of clustering techniques to software partitioning, recovery and restructuring
Journal of Systems and Software - Special issue: Applications of statistics in software engineering
Formalizing refactorings with graph transformations: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice
An Aspect Oriented Model Driven Framework
EDOC '05 Proceedings of the Ninth IEEE International EDOC Enterprise Computing Conference
Business Component Identification of Enterprise Information System: A hierarchical clustering method
ICEBE '05 Proceedings of the IEEE International Conference on e-Business Engineering
Software customization in model driven development of web applications
Proceedings of the 2007 ACM symposium on Applied computing
An XML-based framework for bidirectional transformation in model-driven architecture (MDA)
ACM SIGSOFT Software Engineering Notes
AspectJ in Action: Enterprise AOP with Spring Applications
AspectJ in Action: Enterprise AOP with Spring Applications
| Hi-index | 0.00 |
This paper incorporates the concepts of aspects and software reuse in archetype driven architecture. The proposed work develops the software by partitioning the whole system into different independent components and aspects to facilitate component reuse. The authors illustrate the ease of modeling the components separately and emphasize concerns that the OOP paradigm has failed to address. This paper places emphasis on designing and modeling the software rather than coding. Identification of reusable components is carried out using the hybrid methodology and aspects are identified by domain experts. Along with the components, the PIM and aspects developed are stored in separate repositories to be used in development of other software of similar requirements and basic structure.