Unified Software Engineering (USWE) (BASE)

Professor Dr. Mohamed E. Fayad

Unified Software Engineering (USWE) Using 

Core Knowledge and Unified Words: New Approach

Where Core Knowledge consists of Stable Analysis, Design, and Architecture Patterns

Motivations: 

1. No uniformity in the existing (SWE) content and materials across many universities and industries. 

2. Limitation of the offering of SWE. 

3. Unified SWE needs to be unified in what in different universities. 

4. Existing SWE needs more qualified questions, assignments, and team projects; 5. The scope and level of depth of the content and materials of SWE courses are varied.

5. The challenges do not exist within many Existing SWE courses and materials.

6. The instructors of SWE courses don’t usually have practical experience in SWE (lack of expertise). 

7. Lack of existing content and materials for teaching and applying SWE on a unified base where every student in different universities learns the right school of SWE. 

8. The key knowledge areas in SWE change-over-time overtime on a very faster basis; and 

9. There needs to be an appropriate way to teach and develop SWE to the level and depth to achieve maturity level.

10. many software engineering practitioners and academics present false claims about SWE in Existing SWE. All they see and know is the programming aspects of software engineering, and they are missing the most important stages of SWE: 

1) The Problem Space (Analysis) – Understanding the problem and representing the “WHAT.” 

We are talking about the functional and non-functional requirements, the responsibility, the collaboration of the classes, and the testing aspects of modeling these problem properties. This Problem Space must be addressed completely in teaching, training, research, and practice. We consider the Problem Space the most important stage of software development, and if you don’t have it, you will face many major problems, including many failures. 

Why? No one knows how to do it. 

2) The Solution Space (Design, Architecture, Coding) –Creativity of the solution and represent the “HOW-TO.” 

This phase has many problems to deal with 1) there are many solutions, 2) Would lead to many different modeling techniques 3) The majority of research in SWE IS USLESS. Examples are all over the solution space that are many different modeling, architecture techniques, and too many different tools and languages. Look at this stamen carefully – if you don’t understand the Problem Space, the outcome of the Solution Space is one of the following alternatives: a) Useless Development and cancelation of the development – Billions of $s and b) Software systems with maintenance nightmare which causes a lot of system failures and cancelations after 5 to 6 years. 

Unfortunately, in practice, coding represents 95% of the software development of any system. 

Partial List of Goals:

1. Unification

2. Stability & Endurability 

3. Creativity

4. Adaptability with no internal changes

5. Scalability

6. Reusability

7. Evolving 

8. Suitability to any Domain,

9. Measurements and Assessment

And others

Where BASE means that the USWE contains true and unique software engineering  and considered to be an introduction to more than 12 volumes of software engineering domain, such as Unified Software Functional Requirements (USFR),  Unified Software Non-Functional Requirements (US Non-FR),  Unified Software Design (USD), Unified Software Architectures (USA), etc.