Software Engineering is one of the recently evolving subjects in research and education. Instructors and books that are talking about this field of study lack a common ground of what subjects should be covered in teaching introductory or advance courses in this area. In this paper, a proposed ontology for software engineering education is formulated. This ontology divides the software engineering projects and study into different perspectives: projects, products, people, process and tools. Further or deeper levels of abstractions of those fields can be described on levels that depend on the type or level of the course to teach. The goal of this separation of concerns is to organize the software engineering project into smaller manageable parts that can be easy to understand and identify. It should reduce complexity and improve clarity. This concept is at the core of software engineering. The 4Ps concerns overlap and distinct. The research will try to point to the two sides. Concepts such as; ontology, abstraction, modeling and views or separation of concerns (which we are trying to do here) always include some sort of abstraction or focus. The goal is to draw a better image or understanding of the problem. In abstraction or modeling for example, when we model students in a university in a class, we list only relevant properties, meaning that there are many student properties that are ignored and not listed due to the fact that they are irrelevant to the domain. The weight, height, and color of the student are examples of such properties that will not be included in the class. In the same manner, the goal of the separation of the concerns in software engineering projects is to improve the understandability and consider only relevant properties. In another goal, we hope that the separation of concerns will help software engineering students better understand the large number of modeling and terminology concepts.
