Module 11224 (2010)

Syllabus page 2010/2011

06-11224
Introduction to Software Engineering
Level 1/C

Alan Sexton
10 credits in Semester 2

Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus

The Module Description is a strict subset of this Syllabus Page. (The University module description has not yet been checked against the School's.)

Relevant Links

Module Web Page

Outline

Introduction to Software Engineering: the software life cycle and methodologies for software development.

Aims

The aims of this module are to:

  • introduce strategic and tactical thinking about program design and development
  • introduce issues and solutions for software engineering "in the small"
  • demonstrate the relationship between the practice of good program design and development and software engineering "in the small"

Learning Outcomes

On successful completion of this module, the student should be able to: Assessed by:
1 demonstrate facility with basic strategies of program design Examination and continuous assessment (typically class tests)
2 demonstrate facility with recording and communicating program designs Examination and continuous assessment (typically class tests)
3 understand and be able to apply software engineering approaches in the small Examination and continuous assessment (typically class tests)

Restrictions, Prerequisites and Corequisites

Restrictions:

None

Prerequisites:

None

Co-requisites:

06-18190 (Software Workshop 1) (or equivalent)
Knowledge of a programming language and experience in programming are essential.

Teaching

Teaching Methods:

2 hrs lectures per week

Contact Hours:

24

Assessment

  • Sessional: 1.5 hr examination (80%), Continuous Assessment (typically class tests) (20%)
  • Supplementary (where allowed): 1.5 hr examination (100%)

Recommended Books

None

Detailed Syllabus

  1. Talking about programs
    • Pseudo-code
    • Class Diagrams
    • Interface designs
  2. Program design strategies
  3. Eliciting and recording requirements
    • Specifications
    • Use Cases
    • Interviews
    • Useability
  4. Correctness
    • Testing
    • Debugging
    • Proving Correctness
  5. Managing code
    • Code quality
    • Documentation
    • Commenting
    • Coding Style
    • Code Walkthroughs
    • Versioning
    • Deployment

Last updated: 03 Sep 2010

Source file: /internal/modules/COMSCI/2010/xml/11224.xml

Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus