Don't forget to hit the ⭐ if you like this repo.

Software Engineering (WBL)

Course Synopsis

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.

Course Learning Outcomes

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.

🔥 Important things

Lecture Notes
Student Information
- 🧑‍💻 Section 01
- 👨‍💻Section 02
Task 1: Additional Notes
Lab exercise
Project 1: Student Portfolio Showcase (HTML)
Project 2: Student Portfolio Showcase (Bootstrap)
Student Portfolio Showcase
Book
Software Requirements Document (SRD): Academic Course Registration System
Class exercise: Module 4
🆕 Carry marks

Weekly Schedule

No	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	Proposal	A proposal in software engineering is a document that outlines a proposed solution to a problem or need related to software development. It typically includes an overview of the problem, the proposed solution, the benefits and risks of the proposed solution, the resources required to implement the solution, and a plan for implementing and testing the solution.
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	UML and tools	A UML (Unified Modeling Language) diagram is a visual representation of a system or process that uses standardized symbols and notations to depict the structure, behavior, and relationships between different components of the system. It provides a clear and concise way to communicate and document the design and architecture of a software system, enabling stakeholders to understand and analyze the system's various aspects.
6	5 : Requirements Analysis and modelling ME	Use case modelling and specification, domain modelling, activity diagram, sequence diagram, state chart/state machine diagram
7	Figma	Learn Figma
8	KRISA	Metodologi KRISA meliputi 6 fasa utama yang perlu difahami, diguna pakai dan dilaksanakan oleh agensi. Setiap fasa menerangkan aktiviti, teknik dan pendekatan, serta dokumentasi serahan.
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	🔥UML	The UML exercise is designed to familiarize students with Unified Modeling Language (UML), a standardized visual modeling language used in software engineering. Through this exercise, students gain hands-on experience in creating UML diagrams, such as class diagrams, sequence diagrams, and use case diagrams. By applying UML, students can effectively analyze, design, and communicate software system structures and behaviors.
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		Project demonstration and hand over.

Project

No	Module	Description
1	Project 1	Student Portfolio Showcase (HTML)
2	Project 2	Student Portfolio Showcase (Bootstrap)
3	Proposal	Guideline for Software Engineering Proposal
4	System Documentation	System Requirements Specification (SRS), System Design Document (SDD), and System Testing Document (STD).

Submission

No	Topic	File
1	Proposal
2	System Requirements Specification (SRS)
3	System Design Descriptions (SDD)
4	System Test Descriptions (STD)
5	Project

Tools

Diagrams are visual representations of information or data that help convey complex concepts, processes or systems in a clear and concise manner. Flowcharts are diagrams that use shapes and arrows to illustrate the steps in a process or algorithm [More info...].