Software Engineering Ontology for Multisite Development: Concept Clarification and Communi, Slides of Applications of Computer Sciences

Download Software Engineering Ontology for Multisite Development: Concept Clarification and Communi and more Slides Applications of Computer Sciences in PDF only on Docsity!

Development of a Software Engineering

Ontology For

Multisite Software Development

INTRO:

This paper aims to present an ontology model of software engineering to represent its knowledge and gives an analysis of what software engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios

Software engineering training and practice are quite different between cities and countries. It can be difficult to communicate between teams and among team members, if strict software engineering principles and discipline are not understood and followed.

Communication is the real challenge that we face and we need different ways of tackling this through better communication and conferencing systems, and through systems that help resolve differences between the teams.

Ontology is an important part of developing a shared understanding across a project.

Representing software engineering knowledge in the form of ontology is helping to clear up ambiguities in the terms used in the context of software engineering.

Ontologies are becoming increasingly important in the area of software engineering as they provide a critical semantic foundation

Fig. 1. Schematic overview of software engineering knowledge representation

The whole set of software engineering concepts representing software engineering domain knowledge is captured in ontology.

Based on a particular problem domain, a project or a particular software development probably uses only part of the whole set of software engineering concepts.

For each project in the developmental domain, there exists project information or actual data including project agreements and project understanding. The project information especially meets a particular project need and is needed with the software engineering knowledge to define instance knowledge in ontology.

Once all domain knowledge, sub domain knowledge, and instance knowledge are captured in ontology, it is available for sharing among software engineers through the Internet.

The software engineering ontology is organized by concepts, not words. This is in order to recognize and avoid potential logical ambiguities.

The software engineering ontology has been developed for communication purposes; thus, it may differ greatly from other ontologies developed for different purposes.

The main purpose of the software engineering ontology is to enable communication between computer systems or software engineers in order to understand common software engineering knowledge and to perform certain types of computations.

The key ingredients that make up the software engineering ontology are a vocabulary of basic software engineering terms and a precise specification of what those terms mean.

For software engineers or computer systems, different interpretations in different contexts can make the meaning of terms confusing and ambiguous, but a coherent terminology adds clarity and facilitates a better understanding.

Software engineering ontology has specific instances for the corresponding software engineering concepts. These instances contain the actual data being queried in the knowledge-based applications.

Knowledge Sharing

Fig. 12. An example of use case diagram showing knowledge sharing

Knowledge sharing through the software engineering ontology eliminates misunderstandings, miscommunications, and misinterpretations.

Software engineering ontology presents explicit assumptions concerning the objects referring to the domain knowledge of software development.

Sharing project information drawn based on a consensus of domain knowledge of software engineering formed in the software engineering ontology makes information explicit.

Having attached domain knowledge, it makes project information more understandable, linear, predictable and controllable.

Users learn about some missing pieces that make sense of the attentive interaction among users.

Communications

Software engineering knowledge formed into software engineering ontology facilitates communication framework among users and provides consistent understanding of the domain knowledge.

For example, one would like to communicate changes of project design.

Fig. 13a shows the original design of an activity diagram, while Fig. 13b shows an updated activity diagram. Comparing Figs. 13a and 13b, the software engineer has revised the transition of activity “Update View.” Originally, activity “Update View” transited to activity “Ask for New Employee Data.” Revision has been made by activity “Update View” transited to activity “Notify Employee by Email” and activity “Notify Employee by Email” transited to activity “Ask for New Employee Data.”

This example shows that a user can communicate any project information that is captured as ontology instances. Docsity.com