OntoMaven: Maven-based Ontology Development and Management of Distributed Ontology Repositories

In collaborative agile ontology development projects support for modular reuse of ontologies from large existing remote repositories, ontology project life cycle management, and transitive dependency management are important needs. The Apache Maven approach has proven its success in distributed collaborative Software Engineering by its widespread adoption. The contribution of this paper is a new design artifact called OntoMaven. OntoMaven adopts the Maven-based development methodology and adapts its concepts to knowledge engineering for Maven-based ontology development and management of ontology artifacts in distributed ontology repositories.Comment: Pre-print submission to 9th International Workshop on Semantic Web Enabled Software Engineering (SWESE2013). Berlin, Germany, December 2-5, 201

Information engineering of a software engineering ontology

In this paper, we describe the preliminary result of the development and implementation of a Java-based system for information gathering, knowledge extraction and maintenance of software engineering ontology. The system is capable of manipulative ontology instances from the information repositories and information sources. Design of Software Engineering Ontology through the use of the body of software engineering knowledge together with Prof Ian Sommerville's book, as well as project management experiences, has not been a difficult task. However, the maintenance of the software development ontology and security of the Ontology are issues

Mining for Process Improvements: Analyzing Software Repositories in Agile Retrospectives

Software Repositories contain knowledge on how software engineering teams work, communicate, and collaborate. It can be used to develop a data-informed view of a team's development process, which in turn can be employed for process improvement initiatives. In modern, Agile development methods, process improvement takes place in Retrospective meetings, in which the last development iteration is discussed. However, previously proposed activities that take place in these meetings often do not rely on project data, instead depending solely on the perceptions of team members. We propose new Retrospective activities, based on mining the software repositories of individual teams, to complement existing approaches with more objective, data-informed process views.Comment: In IEEE/ACM 42nd International Conference on Software Engineering Workshops (ICSEW'20

Creating Responsive Information Systems with the Help of SSADM

In this paper, a program for a research is outlined. Firstly, the concept of responsive information systems is defined and then the notion of the capacity planning and software performance engineering is clarified. Secondly, the purpose of the proposed methodology of capacity planning, the interface to information systems analysis and development methodologies (SSADM), the advantage of knowledge-based approach is discussed. The interfaces to CASE tools more precisely to data dictionaries or repositories (IRDS) are examined in the context of a certain systems analysis and design methodology (e.g. SSADM)

Software engineering sub-ontology for specific software development

In this paper we propose software engineering sub ontology. We called it application-specific ontology, for specific software development. It enables remote team members browsing, searching, sharing, and authoring ontological data under the distributed software engineering projects environment. We transform explicit meaningful human knowledge into application-specific ontology, where knowledge structures and semantics are linked, and we go through a formal hand-shaking agreement establishing process before the semantic contents are updated in ontology repositories. The application-specific ontology is used for communication over project agreement to facilitate better, highly consistent communications and formalized domain knowledge sharing. We assume that object-oriented development is deployed in the distributed projects. The knowledge of object-oriented development formed in the application-specific ontology clarifies the object-oriented development concepts in a machine understandable form. Software agent, for example, can be utilised to extract information

Developing knowledge factory system as a best practice platform in software process environment

Knowledge’ is one of the main outcomes systematic approaches of software engineering. It is considered as a crucial resource of each organization and, therefore, needs to be managed carefully especially for the software development process and the roles involved in each phase. The effectiveness application of software engineering relies on experiences, and organizations need to capitalize on their experiences by capturing and reusing them. In all approaches of experience reuse, repositories play a central role in enhancing the knowledge in experience transfer of process knowledge between projects. Like in a factory beside the production there are the people who produce. Experiences should not be stored on a dusty shelf, but engineered into best practices and processes that could be guidance to all roles in the software project especially for the developer. This paper presents the approach to the implementation of the project knowledge based on software development life cycle.It also describe on how the knowledge factory solution can be used as a decision support system for software project managers in day-to-day development activities. The paper concludes with an evaluation of our approach to date and a description of future research directions

Enhancing Software-As-A-Service With Insufficient Domain Knowledge

This study addresses the question “How do Software-as-a-Service (SaaS) vendors enhance their software with insufficient domain knowledge?” Results were obtained by analyzing a dataset from a SaaS vendor that provides administrative software to small schools around the world. The dataset includes archived data (email messages, company documents, and Skype messages) and access to the company’s online repositories (sales pipeline, client online chats, and engineering repository). We identified three types of domain knowledge that are relevant to SaaS vendors – organization specific, industry-wide, and regional variation. We also generated six propositions explaining how industry-wide and regional variation knowledge influences the SaaS enhancement process, and at which points in the process these two types of domain knowledge come into play. This study refines our current knowledge by highlighting the unfolding stages between insufficient levels of domain knowledge and software enhancement outcomes