T1 ontologybased software architecture documentation. Keywordssoftware architecture documentation, software ar. This technique allows us to have the possibility of au tomating semantic analysis with lightweight processing, not heavyweight nlp techniques. However, this involves several major hurdles such as the complexity of functional requirements and the dif. The usefulness of software architecture sa documentation depends on how well its architectural knowledge ak can be retrieved by the stakeholders in a software project. Knowledgeenabled software requirements to architecture documentation. Ontologybased software architecture documentation vrije. In this way some level of automation can be introduced into specification writing. An ontologybased approach for modelling architectural styles. Abstractrequirements modeling and analysis are important in successful software engineering projects. The term paid content is in this article used as the nonfree sales and distribution of information based content products. When building software systems, deciding implementation details manually for specific system requirements is time consuming and often leads to suboptimal choices. Open source software development, software architecture documentation, modeldriven software engineering 1. Citeseerx ontologybased software architecture documentation.
Infonea is a softwarearchitecture for knowledge communication. A case for improved methodology support, authorantony tang and jun han and rajesh vasa, journalieee software, year2009, volume26, pages4349. Ontology based specifications for software reliability. An automated, knowledgebase driven approach to select from possible technology alternatives can replace or reduce manual effort in realizing these requirements. Consequently, the resulting formalization is easy to understand and might also be used as an architecture documentation at the same time. An ontologybased approach for documenting and validating. Improving access to software architecture knowledge an. Introduction the basic format in which software requirements and architecture designs are documented has not changed in many decades. We have evaluated this ontologybased approach in a controlled industry experiment involving software professionals.
Our ontologybased solution enables the provisioning of. Ontologybased software architecture documentation ieee. How organisation of architecture documentation affects. Better knowledge organisation improves retrieval efficiency and effectiveness. We compare retrieval from filebased and ontologybased architecture documentation. Introduction open source software oss development allows for distributed collaboration on software projects that can sometimes compare in the size and scope of traditional enterprise applications. In all proposed architectures, the adaptation module is explicitly separated from the domain module, but another component is introduced in protus 2. This approach offers a singledimensional perspective on the architectural knowledge contained.
This motivated us to develop such a knowledge system which can. How organisation of architecture documentation a ects. Flexible software architectures for ontologybased information systems michael wessel. The approach was applied to construct a useful ontology in industry. This is particularly imperative since in many projects the requirements cannot initially be stated completely and precisely. An ontology based knowledge management system for software testing shanmuganathan vasanthapriyany, jing tian, dongdong zhaoz,shengwu xiongxand jianwen xiang hubei key laboratory of transportation internet of things school of computer science and technology wuhan university of technology wuhan, p.
Towards ontologybased software architecture representations. We have employed a software ontology in a semantic wiki optimized for architecture documentation. Stephen withalls book software requirements patterns 7 provides 37 requirements patterns. A reference architecture for provisioning of tools as a. The place of software architecture in business is outlined from many perspectives in this context. Software architecture documentation, knowledge sharing, ontology, semantic wiki i. The from 4 for annotating knowledge in requirement and original intention of the. Recent findings show that the use of ontologybased sa documentation is promising.
Reference architecture documentation requirements and the corresponding solutions. Kowien prototype the software development partner will use his infoneasuite1 as a basis to develop the kowien prototype figure 2. Software architecture documentation, software architectural knowledge, architectural knowledge retrieval, software ontologies, semantic wiki, ontology based documentation. Ontology driven software development for automated documentation. An ontologybased approach for software architectural. Along this line, a sad must be clear in explaining. Towards an ontologybased distributed architecture for paid. Class diagrams are a useful standard for modeling static structures of information systems. Software architecture sa plays a critical role in designing, developing and evolving cloud. Few ontology engineering approaches for software architecture documentation exist. We propose an ontology engineering approach for use in software projects. In this paper, we compare the organisation and retrieval of architectural knowledge in a file based documentation approach and an ontology based documentation approach. Improving access to software architecture knowledge an ontology based search approach adriana maria figueiredo, julio c.
Ontologybased architecture with recommendation strategy in java tutoring system comsis vol. Software architecture software 2014 ontology ontology based documentation knowledge acquisition knowledge management abbreviations. Therefore, ontology based specifications has been proposed to serve as prototype that may be used as an evolutionary approach for software development. We investigate how the organisation of knowledge affects knowledge retrieval. The author describes enterprise architecture along with business architecture to show the role of software architecture in both areas. Ontology based data management 3 data is widespread into separate pieces of documentation that are often di cult to access and rarely conforming to common standards. Architectural knowledge needed by diverse document users was acquired and modeled. Analyzing conflicts in software specifications is crucial when multiple stakeholder concerns need to be addressed. The concepts related to software architecture and their instances are automatically identified and extracted by parsing the.
In a development project, the software architecture is typically captured by the software architecture documentation sad, which acts as a channel of communication and knowledge sharing among the stakeholders of the project clements et al. In 12, built an ontology for software architecture documentation which is used to retrieve architectural knowledge for the stakeholders 12. An exploratory study on ontology engineering for software. Ontologybased software architecture documentation abstract. Supporting swfmea through an ontologybased methodology. We also report a costbenefit analysis and survey on both documentation approaches. They implemented the trex on a case study and compared its outcome vs. Graaf provided the documentation software requirements and architecture design. One dimension represents the categories originating in the domain ontology and the other dimension represents the functional concerns that originate from user requirements.
The benefit of such an ontology is that it preserves the complex graphs of interrelated design decisions and supports use cases such as reasoning and recommendations to support software architects during the decisionmaking process. In order to support a communitywide infrastructure for software architecture research and collaboration, an essential requirement is interoperability of a. A common approach to software architecture documentation in industry projects is the use of file based documents. This approach offers a singledimensional perspective on the architectural. A common approach to software architecture documentation in industry projects is the use of filebased documents. The book outlines quality attributes and how managers can use software architecture to build high quality products. The ontology and the corresponding mappings to the data sources provide a common ground for the documentation of all the data in the organisation, with obvious ad. Knowledge retrieval from file based architecture documentation is efficient if the organisation of knowledge supports the needs of the readers. Ontology based support for security requirements specification process 195 experienced sr personnel 2, 3. Towards an ontology based distributed architecture for paid content 258 and receive over the internet has the potential to be a digital product. Ontologybased software architecture documentation klaas.
Technology system architecture and software architecture in acme style 21. Improving access to software architecture knowledge an ontology. Pdf ontologybased software architecture documentation. This scenario implies the need for a tool based framework that is capable of supporting the srs process. Ontologybased approach to represent the artefacts of. It is essentially file based with the support of semiautomated tools such as requisitepro and doors for. In this paper we develop an ontology based approach to manage ak in order to partly mitigate the deficiencies of existing ak approaches in a distributed software devotement. In this paper we describe an approach aimed at addressing architecture documentation retrieval issues. Nevertheless, the documentation can be automatically verified, since the approach is based on powerful means of the semantic web, i. Chapter 4 ontologybased architecture documentation approac h in this chapter we in vestigate how an on tology can be used for retrieving ak from sa documentation rq2. Requirements pattern software specification ontology.
Software architecture, architectural knowledge management, architectural design. An ontologybased knowledge management system for software. Ontologybased architecture with recommendation strategy in. An ontologybased approach for software architecture. The views are used to describe the system in the viewpoint of different stakeholders, such as endusers, developers and project managers. Sa, software architecture ak, architectural knowledge html, hypertext markup language wysiwyg, what you see is what you get gui, graphical user interface cf, contextual factor a b s t r a c t. Ontology based software development techniques by motoshi saeki an ongoing research project at the tokyo institute of technology is looking at supporting software requirements elicitation and composing software from reusable architectures, frameworks, components and software packages. Software architecture model driven reverse engineering. In computer science and information science, an ontology encompasses a representation, formal naming and definition of the categories, properties and relations between the concepts, data and entities that substantiate one, many or all domains of discourse. Ontologybased software architecture documentation ieee xplore. Ontologybased requirement conflicts analysis in class diagrams.
1377 635 1404 436 96 146 860 1304 1131 875 1077 1039 1467 1621 266 2 179 1669 412 1540 604 1627 493 568 597 460 1002 900 715 577 675 70 595 823