Abstract
In a domain like software process that is intensively knowledge driven, transforming intellectual knowledge by formal representation is an invaluable requirement. An improved use of this knowledge could lead to maximum payoff in software organisations which is key. The purpose of formal representation is to help organisations achieve success by modelling successful organisations. In this paper, Software process knowledge from successful organisations was harvested and formally modeled using ontology. Domain specific knowledge base ontology was produced for core software process subdomain, with its resulting software process ontology produced.
Highlights
Software process is a knowledge driven and knowledge intensive process that involves several other sub-processes
Software process can be defined as the set of related activities that are used in developing software
Harvesting, representing and reusing knowledge within a domain leads to maximum payoff, which is desirable in most organisations [23]
Summary
Software process is a knowledge driven and knowledge intensive process that involves several other sub-processes. He made an attempt to provide an integrated solution for better dealing with KM-related problems in SE by means of a Software Engineering Ontology Network (SEON) It was designed with mechanisms for easing the development and integration of SE domain ontologies, covering the main technical software engineering subdomains (i.e requirements, design, coding and testing). He only represented a small portion of software engineering ontology. This paper represents a software process ontology covering major SE subdomains (i.e. requirement gathering, design and coding, implementation and maintenance). The purpose of most standards is to help software organisations achieve excellence by following the processes and activities adopted by the most successful organisations [26]
Published Version (Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have