![Cover image for The [12 + 3] Commandments of Software Engineering π¨βπ»](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fzry3xdxjf4qvnn0ihteg.jpeg)
What do the binary gods say to follow to reach the holy grail of software engineering? ππΏ
First, the basic premise that the objective of a software project is to decompose it into modules that can be implemented in parallel and by independent teams.
Therefore we must follow the SWEBOK emerald board.
Jeez wait my dear developer, What kind of magic is this SWEBOK? π€
Software Engineering Body of Knowledge, also known by the acronym SWEBOK.
It is a document, organized by the IEEE Computer Society (an international scientific society), with the support of several researchers and industry professionals.
The purpose of SWEBOK is precisely to document the body of knowledge that characterizes the area that we now call Software Engineering.
SWEBOK defines 12 areas of knowledge in Software Engineering:
1) Requirements Engineering
2) Software Design
3) Software Building
4) Software Testing
5) Software maintenance
6) ConfigurationManagement
7) Project Management
8) Software Processes
9) Software ModelsS
10) Softwarequality
11) Professional Practice
12) Economic Aspects
Border areas ποΈβπ¨οΈ
13) Fundamentals of Computing,
14) Fundamentals of Mathematics
15) Fundamentals of Engineering
Top comments (1)
βThere is no software engineering, but, maybe, someday, there will be.β
SoftwareBlueprints. - Bob Bockholt
wiki.c2.com/?SoftwareEngineeringBo...