The IEEE defines Software Engineering as “the application of a systematic, disciplined, and quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.” Software engineering is a discipline applied throughout the entire software lifecycle, spanning the early phases of system specifications all the way to maintenance after system deployment. So why use an engineering approach to software? Quite simply, because the alternative would be to use an ad-hoc or disordered approach. An engineering approach means predictability and quantifiable results through the application of theories, methodologies, frameworks, and tools. When applied efficiently, the result is high-quality software created in a cost-effective manner.
Author Name: Mohamad Halabi
Author Description:
Mohamad is a solution architect, based in Sydney, currently working for MuleSoft/Salesforce. He’s an 8 time Microsoft MVP, Ex-Oracle, and holds a Masters degree in Enterprise Architecture.

Table of Contents

• Introduction
  19mins
• Software Processes
  47mins
• Requirements Engineering
  39mins
• Requirements Modeling – Structured Analysis
  23mins
• Requirements Modeling – Object Oriented Analysis
  40mins
• Design – Essentials
  30mins
• Design – Methodology
  47mins
• Construction
  17mins
• Testing
  32mins