SEF9 - 06 When it comes to big and complex software, Software Engineering (SE) gets ...

A friend one day said, "Why do you study software engineering in university when any Tom, Dick and Harry (or Susan, Liz and Mona) can write programs easily and run them successfully?" He he he.

IN A QUICK RESPONSE, I said, "Oooooooh my friend, writing and running software programs is NOT software engineering. And software engineering is NOT just writing and running programs successfully.

My friend, your understanding is very much obsoleted (outdated, antiquated). Kah kah kah.

About Software Development Life Cycle (SDLC)
===========================================================

Software Engineering is SWEBOK, ha ha ha, a ritual diligently practised by software engineering professionals. The ritual is called the System or Software Development Life Cycle (SDLC). He he he.

Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure.

===> Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom-written code that drive our enterprises.

(1) When it comes to big and complex software, Software Engineering (SE) gets into the picture.

(2) When it comes to safety-critical and mission-critical software and systems where loss of lives can occur, Software Engineering again gets into the picture.

(3) Software Engineering is unlike (not like) your software programming exercises, where you solved problems based on the end of chapter questions in a textbook. In your software programming exercises, nobody will die if your programs failed or crashed. "Your programs are simply "throw-away" programs", a software engineering professional would say.

(4) To manage this complexity in Software Engineering, people have created a number of system development life cycle (SDLC) models: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, agile, and synchronize and stabilize, and many more.

IMPORTANT TO REMEMBER.
===========================================================

(5) If you do not know SDLC, you do not know Software Engineering.

(6) If you do not know SWEBOK, you do not know Software Engineering.

(7) If you do not know the WATERFALL MODEL, you do not know Software Engineering.

(8) Everything in Software Engineering revolves around the Waterfall Model.

(9) We can say that the Waterfall Model is in Software Engineering like the Pythagoras Theorem in Mathematics.

(10) And the Waterfall Model is just one of the many "types" of SDLC. The other types of SDLC are just "variations" of the Waterfall Model.

============================================================

--
WASSALAM
wruslan.hahaha

Microsoft Word Version
Return to Software Engineering Fundamentals (SEF9MMUWRY)
Previous Topic: 05 Why Software Engineering is (a) systematic, (b) disciplined, (c) quantifiable, etc?
Next Topic: 07 Weblink downloads SEF9 Resources (slides + tutorials + labs) from MMLS