Don't forget to hit the ⭐ if you like this repo.
This course is designed to give students an introduction to an engineering approach in the development of high-quality software systems. It will discuss the important software engineering concepts in the various types of the common software process models. The students will also learn the concepts and techniques used in each software development phase including requirements engineering, software design and software testing. This course will also expose the students to utilizing object-oriented method (e.g., UML) and tools in analyzing and designing the software. At the end of this course, students are expected to be able to appreciate most of the common software engineering concepts and techniques as well as producing various software artifacts and deliverables.
- Apply the fundamental of software engineering, software process, requirements engineering to solve software engineering case studies.
- Build suitable software architecture, object-oriented design model and develop test cases in software engineering case studies.
- Construct software requirements model, software architecture, object-oriented design model and test cases with state-of-the-art methods and tools for a real-world software engineering problem.
- Ability to establish good rapport, interact with others, work effectively in a team and comprehend the interchangeable role of leaders and followers with team members.
Weekly | Module | Description |
---|---|---|
1 | 1: Introduction to Software Engineering | Software definition, software engineering as a layered technology, types of software, inherent difficulties in software engineering, SE quality focus, Documentation Standard. |
2 | 2: Software Process Model | Plan Driven or Agile Process Model, general software process model waterfall, incremental, reuse oriented, software process model which cope with change spiral model and Rational Unified Process |
3 | 3: Agile Software Development | Agile methods, Agile development techniques, Agile project management, scaling Agile methods |
4 | 4: Requirements Engineering | Types of requirements, functional and non-functional requirements, requirements specification, requirements engineering processes |
5 | 5: Requirements Analysis and modelling ME | Use case modelling and specification, domain modelling, activity diagram, sequence diagram, state chart/state machine diagram |
6 | Industry Day I: Project requirement sharing. | |
7 | MID-SEMESTER BREAK | |
8 | Software Engineering project – Requirements analysis and models. Produce requirements document* that includes all the required analysis models | |
9 | 6: Architectural Design | Architectural design and detailed design, Architectural design decision, architectural view, component diagram in relation to architectural view, architectural pattern: Model-View-Controller (MVC), layered, repository, client server and pipe filter |
10 | 7: Object-Oriented Detailed Design | Relationships among analysis, design and implementation, object-oriented design using UML, object-oriented design principles, elaborating UML diagrams from analysis. |
11 | Software Engineering project – Design model. Produce design document* that includes all the required design models | |
12 | 8: Software verification, validation and testing | Introduction to verification and validation, verification and validation planning, software inspections. System testing, Component testing, Test case design, Test Case Design using Black-box and white box |
13 | Software Engineering project – Test case design. Produce testing document* that includes all the required test cases | |
14 | TENTATIVE - ALTERNATIVE ASSESSMENT (TBC) | |
15 | Industry Day II: Project demonstration and hand over. |
- Software Engineering | Introduction to Software Engineering
- Software Engineering Tutorial
- The Importance of Software Engineering
- Software Cost Estimation
- Tools EVERY Software Engineer Should Know
- The Anatomy of A Skilled Software Engineer
- Software developer road map 2023
- Document standards by IEEE
- 830-1998 - IEEE Recommended Practice for Software Requirements Specifications
- 1016-2009 - IEEE Standard for Information Technology--Systems Design--Software Design Descriptions
- 829 - IEEE Standard for Test Documentation Overview-Test Plan Outline
- 829-2008 - IEEE Standard for Software and System Test Documentation
- IEEE Standards
Please create an Issue for any improvements, suggestions or errors in the content.
You can also contact me using Linkedin for any other queries or feedback.