COMPX341-23A (HAM)

Advanced Software Engineering Design

15 Points

Edit Header Content
Division of Health Engineering Computing & Science
School of Computing and Mathematical Sciences
Department of Computer Science

Staff

Edit Staff Content

Convenor(s)

Lecturer(s)

Administrator(s)

: buddhika.subasinghe@waikato.ac.nz

Placement/WIL Coordinator(s)

Tutor(s)

Student Representative(s)

Lab Technician(s)

Librarian(s)

: alistair.lamb@waikato.ac.nz

You can contact staff by:

  • Calling +64 7 838 4466 select option 1, then enter the extension.
  • Extensions starting with 4, 5, 9 or 3 can also be direct dialled:
    • For extensions starting with 4: dial +64 7 838 extension.
    • For extensions starting with 5: dial +64 7 858 extension.
    • For extensions starting with 9: dial +64 7 837 extension.
    • For extensions starting with 3: dial +64 7 2620 + the last 3 digits of the extension e.g. 3123 = +64 7 262 0123.
Edit Staff Content

What this paper is about

Edit What this paper is about Content

Software Engineering is the systematic design, construction, testing and maintenance of large software systems. The various processes (and engineering specializations) comprising the methods of Software Engineering will be presented with a specific focus on assuring a high quality of software in requirements, design, construction, testing and maintenance.

Students will practice what they learn in class with four assignments (and two tests) focusing on evidence-based assurance of high quality in:

1) Software Requirements Specification & Software Design Specification;

2) Test Plan Specification & Acceptance/Regression Testing;

3) Software Construction;

and

4) Maintenance & DevOps.

The learning outcomes for this paper are linked to Washington Accord graduate attributes WA1-WA11. Explanation of the graduate attributes can be found at: https://www.ieagreements.org/

Edit What this paper is about Content

How this paper will be taught

Edit How this paper will be taught Content

The paper is taught via lectures, assignments, tests, and readings from recommended texts. Attendance at the lectures is highly encouraged!


Edit How this paper will be taught Content

Required Readings

Edit Required Readings Content
Edit Required Readings Content

Learning Outcomes

Edit Learning Outcomes Content

Students who successfully complete the course should be able to:

  • Comprehend and use software requirements of a software project (WA1-7, WA9)
    Linked to the following assessments:
    Assignment 1: Software Design Specification (2)
  • Elicit and specify software design specifications, viewed as contracts between client and developer, of a software project (WA1-5)
    Linked to the following assessments:
    Assignment 1: Software Design Specification (2)
  • Design software testing plans and suites with quality-assured methods (WA1-5)
    Linked to the following assessments:
    Assignment 2: Test Plan Specification & Acceptance/Regression Testing (3)
  • Construct software that meets and satisfies the requirements and design specifications, and passes all the tests in a test suite (WA1-5)
    Linked to the following assessments:
    Assignment 3: Software Construction (4)
  • Maintain and test software systems using a continuous development, integration and deployment maintenance lifecycle (WA1, WA4, WA5, WA8, WA10)
    Linked to the following assessments:
    Assignment 4: Maintenance and DevOps (5)
Edit Learning Outcomes Content
Edit Learning Outcomes Content

Assessments

Edit Assessments Content

How you will be assessed

Edit How you will be assessed Content

The paper will be assessed through four individual assignments and two in-class tests.

If you are enrolled in a BE(Hons), samples of your work may be required as part of the Engineering New Zealand accreditation process for BE(Hons) degrees. Any samples taken will have the student name and ID redacted. If you do not want samples of your work collected then please email the engineering administrator, Natalie Shaw (natalie.shaw@waikato.ac.nz), to opt out.

Please note that, as part of any assessment, students may be asked to complete an oral examination (viva voce) at a later date.


Edit How you will be assessed Content

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0. There is no final exam. The final exam makes up 0% of the overall mark.

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0 or 0:0, whichever is more favourable for the student. The final exam makes up either 0% or 0% of the overall mark.

Component DescriptionDue Date TimePercentage of overall markSubmission MethodCompulsory
1. Test 1
4 Apr 2023
9:00 AM
10
  • In Class: In Lecture
2. Assignment 1: Software Design Specification
7 Apr 2023
11:30 PM
20
  • Online: Submit through Moodle
3. Assignment 2: Test Plan Specification & Acceptance/Regression Testing
5 May 2023
11:30 PM
20
  • Other: GitLab
  • Online: Submit through Moodle
4. Assignment 3: Software Construction
19 May 2023
11:30 PM
20
  • Other: GitLab
  • Online: Submit through Moodle
5. Assignment 4: Maintenance and DevOps
2 Jun 2023
11:30 PM
20
  • Other: GitLab
  • Online: Submit through Moodle
6. Test 2
2 Jun 2023
11:00 AM
10
  • In Class: In Lecture
Assessment Total:     100    
Failing to complete a compulsory assessment component of a paper will result in an IC grade
Edit Assessments Content