Module: Software Engineering: Process, Principles & Methods (C)

Module Specifications.

Current Academic Year 2024 - 2025

All Module information is indicative, and this portal is an interim interface pending the full upgrade of Coursebuilder and subsequent integration to the new DCU Student Information System (DCU Key).

As such, this is a point in time view of data which will be refreshed periodically. Some fields/data may not yet be available pending the completion of the full Coursebuilder upgrade and integration project. We will post status updates as they become available. Thank you for your patience and understanding.

Date posted: September 2024

Module Title	Software Engineering: Process, Principles & Methods (C)
Module Code	CA4004 (ITS) / CSC1099 (Banner)
Faculty	Engineering & Computing	School	Computing
Module Co-ordinator	Paul Clarke
Module Teachers	-
NFQ level	8	Credit Rating	7.5
Pre-requisite	Not Available
Co-requisite	Not Available
Compatibles	Not Available
Incompatibles	Not Available

Coursework Only
Category 1: A resit is available for all elements of the module

Description

The difference between writing a small program and developing a large-scale software product is not a difference of size as much as it is a difference of nature. While the construction of small programs is a purely technical issue, the development of larger software products is a multi-dimensional problem, which involves technical considerations as well as managerial and organizational considerations. The objective of this module is to explore all three inter-related perspectives and to provide the learner with the foundational skills necessary to understand and apply these skills in an industry context.

Learning Outcomes

1. Identify important historical and current literature addressing software engineering, software process, software methodologies, software quality and associated standards
2. Evaluate the concepts embodied in the most prevalent software methodologies and models, including knowledge of their advantages and disadvantages, and when it may be appropriate to use each approach
3. Explain and construct quality-oriented software development processes and explain the principles behind SPI models / standards and their implementation in software development organization and select the most appropriate model / standard for a given situation.
4. Develop a detailed understanding of specific software systems development topics through structured research.
5. Demonstrate a solid understanding of the available methods for building software systems, including high dependency systems.

*Type*	*Hours*	*Description*
Workload	Full-time hours per semester
Lecture	36	Course content, including supplementary material on key topics and associated tutorial material will be made available online using the DCU Loop e-learning system and other appropriate electronic means.
Independent Study	151	This comprises time for reading, reviewing given and other exercises, group interaction on project, project time and write-up and revision
Total Workload: 187

All module information is indicative and subject to change. For further information,students are advised to refer to the University's Marks and Standards and Programme Specific Regulations at: http://www.dcu.ie/registry/examinations/index.shtml

Indicative Content and Learning Activities

Introduction / overview (1 lecture)
Introduction to software engineering process, principles and methods

Software process, lifecycle and models (5 lectures)
Tradition (plan-based) approaches; Formal approaches; Agile approaches and methodologies; Standards and process reference models

Software lifecycle (14 lectures)
Requirements engineering; Architectural design and re-design; Software design, patterns and reuse; Software evolution, refactoring, maintenance and test

Dependable Software Construction (8 lectures)
Dependability and reliability specification; Formal models and verification; Security guidelines and considerations

Software Management (8 lectures)
Project management; Project planning; Software metrics and measurement; Software estimation and cost modelling; Risk management; Quality management; Configuration management; Process assessment and improvement; and Software quality and management standards

Assessment Breakdown
Continuous Assessment	100%	Examination Weight	0%

Type	Description	% of total	Assessment Date
Course Work Breakdown
Group assignment	Writing a research paper that examines an important aspect of software engineering / processes, and presenting findings / fielding Q&A. Each student will identify and be assessed on specific individual contributions.	70%	n/a
In Class Test	Evaluation of major learning outcomes in an in-class quiz format.	30%	Week 12

Reassessment Requirement Type
Resit arrangements are explained by the following categories: Resit category 1: A resit is available for both* components of the module. Resit category 2: No resit is available for a 100% continuous assessment module. Resit category 3: No resit is available for the continuous assessment component where there is a continuous assessment and examination element.
* ‘Both’ is used in the context of the module having a Continuous Assessment/Examination split; where the module is 100% continuous assessment, there will also be a resit of the assessment
This module is category 1

Indicative Reading List

Ian Sommerville: 2010, Software Engineering, Pearson Education,
Hans van Vliet: 2000, Software Engineering: Principles and Practice,
Sami Zahran: 2006, Essential Software Process Improvement, Essential Software Process Improvement,
Daniel Galin: 2003, Software Quality Assurance: From Theory to Implementation,
Christopher Fox: 2006, Introduction to Software Engineering Design: Processes, Principles and Patterns with UML2,,
Leszek Maciaszek and Bruc Lee Liong: 2004, Practical Software Engineering: A Case-Study Approach,
Shari Lawrence Pfleeger and Joanne M. Atlee: 2012, Software Engineering: Theory and Practice,
Watts Humphrey: 1995, Discipline for Software Engineering, Addison Wesley,
Erich Gamma, John Vlissides, Ralph Johnson, and Richard Helm: 1998, Design Patterns: Elements of Reusable Object-Oriented Software,
Eric Freeman, Bert Bates, Kathy Sierra, Elisabeth Robson: 2004, Head First Design Patterns,
Stephen H. Kan: 2003, Metrics and Models in Software Quality Engineering,
Robert T. Futrell, Donald F. Shafer, Linda I. Safer: 2002, Quality Software Project Management,

Other Resources

65310, IEEE, 0, Website, The Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), http://www.computer.org/web/swebok, 65311, 0, Wesbite, http://sourcemaking.com/,