Modules

Module title: Software Engineering
SCQF level: 09:
SCQF credit value: 20.00
ECTS credit value: 10
Module code: SET09102
Module leader: Xiaodong Liu
School School of Computing
Subject area group: Software Engineering
Prerequisites

Module code: SET08103

Examples of equivalent learning: Any module that gives a grounding in Software Engineering.
2018/9, Trimester 1, Face-to-Face, Edinburgh Napier University
Occurrence: 001
Primary mode of delivery: Face-to-Face
Location of delivery: MERCHISTON
Partner: Edinburgh Napier University
Member of staff responsible for delivering module: Xiaodong Liu
Module Organiser:


Learning, Teaching and Assessment (LTA) Approach:
The teaching comprises a blend of conventional lectures and guest lectures from practitioners supported by classroom tutorials and practical computer-based development activity. The most important aspect of this module is an end-to-end integrated Development Environment (IDE). Systems analysis and design has developed into a holistic activity and this is evident in how the practical’s and tutorials are conducted (LOs 1, 2, 3 and 4).
Formative Assessment:
To Support formative feedback, the Software Engineering subject group utilise a lab based teaching approach across their provision. During these lab sessions, staff will discuss and evaluate student progress and provide feedback on how well they are progressing with their work. All modules in the subject group also require students to demonstrate their coursework on submission to provide further formative feedback on how the work could be improved.

Summative Assessment:
Assessment is by practical submissions and an end-of-module examination.

The coursework is one piece of work including three deliverables, an initial model, an elaborated model and a tested and implemented system. These contribute to LO1, LO2, LO3 and LO4 respectively to the overall assessment. There is also a two hour examination at the end of the module worth 50% (LOs 1, 2, 3 and 4).

The activities and the summative assessment are characterised by the application of theory to practice and including reflective elements in which the student is encouraged to have a deeper understanding of the subject by examining and assessing other published sources. The assessment by practical work encourages students to work steadily through the duration of the module. The tools used are extensively used in the commercial context and their use here supports the students development of their skills portfolio.
Student Activity (Notional Equivalent Study Hours (NESH))
Mode of activityLearning & Teaching ActivityNESH (Study Hours)
Face To Face Lecture 24
Face To Face Practical classes and workshops 24
Face To Face Tutorial 12
Independent Learning Guided independent study 140
Total Study Hours200
Expected Total Study Hours for Module200


Assessment
Type of Assessment Weighting % LOs covered Week due Length in Hours/Words
Practical Skills Assessment 50 1,2,3, 4 12 HOURS= 50, WORDS= 0
Centrally Time Tabled Examination 50 1,2,3,4 14/15 HOURS= 2, WORDS= 0
Component 1 subtotal: 50
Component 2 subtotal: 50
Module subtotal: 100

Description of module content:

This module is primarily concerned with the advanced methodologies and technologies for software development in practice. The contents include:

Modelling and developing event-driven and persistent systems;
Requirement engineering methods and tools;
Model-driven software engineering;
Good design practice such as modularity and quality engineering;
Testing and frameworks: system, integration and unit testing, test methods, test model and documentation, test-driven development, testing tools ;
Software Management: configuration management and version control;
Software Evolution: concepts, approaches and process.
Learning Outcomes for module:

Upon completion of this module you will be able to:
LO1: Construct models of the problem domain and develop appropriate applications with the learnt advanced methodologies and technologies;
LO2: Manage the software artefacts of a project that incorporates version control and learnt advanced practices;
LO3: Design test strategies using current technologies;
LO4: Engineer software systems in the full life cycle, particularly at the evolution stage.

Indicative References and Reading List - URL:

Core - BENNETT, MCROBB AND FARMER (2006) OBJECT-ORIENTED SYSTEMS ANALYSIS AND DESIGN USING UML: MCGRAW-HILL, 3rd ed. - ISBN: 0077110005
Core - SOMERVILLE (2006) SOFTWARE ENGINEERING: ADDISON WESLEY, 8th ed. - ISBN: 9780321313799
Core - AVISON AND FITZGERALD (2006) INFORMATION SYSTEMS DEVELOPMENT: MCGRAW-HILL, 4th ed. - ISBN: 0077114175
Core - K BARCLAY & J SAVAGE (2004) OBJECT ORIENTED DESIGN WITH UML AND JAVA: ELSEVIER, 0
Core - GRAIG LARMAN (1998) APPLYING UML AND PATTERNS: PRENTICE HALL PTR, 0
Core - E. BURNETTE (2005) ECLIPSE IDE (POCKET EDITION): O’REILLY, 0 - ISBN: 0596100655
Click here to view the LibrarySearch.
 

Related information