Towards a taxonomy of architecture integration strategies
ISAW '98 Proceedings of the third international workshop on Software architecture
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Towards a taxonomy of software connectors
Proceedings of the 22nd international conference on Software engineering
The 4+1 View Model of Architecture
IEEE Software
Acquiring COTS Software Selection Requirements
IEEE Software
Definition and Classification of COTS: A Proposal
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Reconciling Software Requirements and Architectures: The CBSP Approach
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
AcmeStudio: Supporting Style-Centered Architecture Development
Proceedings of the 26th International Conference on Software Engineering
A comprehensive approach for the development of modular software architecture description languages
ACM Transactions on Software Engineering and Methodology (TOSEM)
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
A Taxonomy of Software Component Models
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Proceedings of the 5th India Software Engineering Conference
Pattern-oriented knowledge model for architecture design
Proceedings of the 17th Conference on Pattern Languages of Programs
| Hi-index | 0.00 |
Technical design of a business application is an involved process which needs an experienced designer to describe an implementation of the application functionality using a set of hardware and software infrastructure elements such that the non-functional requirements are satisfied. The process is extremely knowledge intensive. For instance, it demands the designer to thoroughly understand various architecture styles, a set of technical capabilities available, how different COTS products can realize these capabilities, and how the functional modules can make use of these capabilities. In reality, such experienced designers are hard to come by. Furthermore, to optimize the budget, the project team often involves inexperienced designers to create the technical design. In order to assist an inexperienced designer to create the technical design, we have built a knowledge-based design assistant tool, called Technical Design Assistant Tool (TDAT). In this paper we describe the ontology knowledge model that describes the underlying technical design knowledge. The ontology models the notion of a architecture style, various technical capabilities, a COTS component, and capability features. We have conducted a few experiments to evaluate the usefulness of the ontology and the tool and found encouraging responses. As a part of the project we are populating the knowledge base for the popular open source and commercial software products.