Unified Software Engineering (USWE)
Critical Look at Existing Software Engineering -- Overview
Our motivations are to:
1) Highlight all existing problems and pitfalls of existing software engineering aspects (more than 60 sub-aspects).
2). Address and discuss a critical look at each existing software engineering aspect, such as methodologies, modeling, domain analysis, functional and non-functional requirements, software design, software architecture, economics, research, teaching, etc.
3) Point out the many nonsense issues of existing software engineering in each aspect
4) Research and state that existing software engineering is limited to programming and business as usual.
5) Address and apply discoveries and innovations in each aspect of software engineering and establish an actual stable and unification software engineering (USWE)
6) Submit funded research proposals for each aspect listed in 1) to 5)
7) Seeking Letters of support and endorsements from Software Engineering Leaders, well-known academics, practitioners, Professionals, and Companies in Software Industries.
The goals are to:
1) True unification of Software Engineering
2) Software Engineering in all aspects
Many software engineering practitioners and academics are presenting many false claims about SWE. All that they see and know is the programming aspects of software engineering, and they are missing the essential stages of SWE:
What? No one knows the “What” and how to specify the “What.”
1) The Problem Space (Analysis) – Understanding the problem and representing the “WHAT.”
We discuss “the functional and non-functional requirements, the responsibility, the collaboration of the classes, and the testing aspects within the modeling aspects of these problem properties.” Unfortunately, this Problem Space is ignored in teaching, training, research, and practice. Do you know why? Because no one knows how to specify it.
“How-To”?
2) The Solution Space (Design, Architecture, Coding) – Creativity is the solution and represents the “HOW-TO.” This phase has many problems: Many solutions would lead to different modeling techniques.
3) The majority of research in SWE IS USELESS. Examples are all over the solution space, with many different modeling and architecture techniques and too many other tools and languages. So look at this statement carefully – evidence exists to show the misunderstanding of 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 have maintenance nightmares, which cause a lot of system failures and cancellations after 5 to 6 years.
Unfortunately, in practice, coding represents 95% of the software development of any system.
(Use Aspects)
In this work, we will examine and critically look at the many issues and provide solutions to them: SWE Research Issues, Economic Issues, Teaching and Training aspects, Modeling Issues, Development Issues, Software Methodology Issues, Software Aspects, critical current research on SWE, etc. Research agencies and organizations, societies, and associations of magazines, journals, media, conferences, and Professional Societies do not promote innovations in SWE. Why? All the editorial boards and conferences’ committees meet the following quotes: “The one who lacks the thing cannot give it to others” and “Collective fear stimulates herd instinct and tends to produce ferocity toward those who are not regarded as members of the herd.” ― Bertrand Ruse.
Invitations are extended to as many professionals and academies as possible to present specific issues and solutions or participate in panels / Discussion Groups on Fayad’s Critical issues on SWE.
https://www.linkedin.com/groups/14363864/
Major Findings
1) Large categorial list of critical issues in SWE, such as SWE lifecycle & Methodologies, SWE Research, SWE Teaching, SWE Economics, SWE Innovations, Domain Analysis, SWE Modeling, SWE Courses, SWE Books, SWE Projects, SWE Systems, and SWE Applications, SWE Quality Factors (Applications), Artificial Intelligence, and Smart Systems, SWE Standards, Software science, etc.
2) Innovative solutions are provided for each issue.
https://youtu.be/aaY7RcFYSeE
Dear Mohamed Fayad ,
Critical Success Factors for Software Development
Clear Objectives and Goals. ...
Clear Requirements and Specifications. ...
A Realistic Schedule. ...
Good Management. ...
User Research and Testing. ...
Regular Monitoring, Reporting, and Feedback. ...
Experienced Developers and Correct Team Structure.
https://www.zartis.com/7-critical-success-factors-for-software-development/
Regards,
Shafagat
To: Shafagat Mahmudova
To: Shafagat Mahmudova
Your article is "Empty talk" Why?
You provided a long list of successful factors and I don't think you know what and how-to be done.
Example: Your first factor is ""Clear Objectives and Goals"
Too many Objectives and Goals! What do you think?
How do you abstract "Clear Objectivea and Goals"? How you justify the clarity of the objectives and goals?
Do you know each one of the following words: Requirement, Schedule, Design, Architecture, Schedule, Feedback, Report, Test, and research?
has
(1) Only unified and ultimate goal.
(2) Fuctional requirements
(3) Non-Functional requirements
(4) Responsibility per scenario
and more then 50 discoveries
Whould you know?
- Badges
- Science topic
- Similar topics
- Geoscience
- Asia
- India