University Standard Module Template
Faculty: Technology, Engineering and the Environment | School/Department: Computing, Telecommunications and Networks |
Module Title: Software Design UG2 | |
Programme(s) on which the module is delivered: BSc (Hons) Computer Science
| |
Date of publication of template to students: | |
Module Code: | Level (e.g. level 3, 4, 5, 6 or 7): 5 |
Where necessary, agreed abbreviated module title for the SRS (maximum 3 alpha characters e.g. EDU for Education; JEW for Jewellery) | |
Credit value: 15 | |
ECTS Credit value[1]: 7.5
| |
Module Leader: | |
Module start date(s) during the current academic year: September 2013 | |
Module finish date(s) during the current academic year: March 2014 | |
Assessment weightings: Assessment 1 - Coursework – 40% Assessment 2 - Examination – 60% | |
Date of Module Approval / Review | Version Number | Version Date |
For SRS Team Use Only: | |
Created By:
|
Date:
|
Relationship with Programme Philosophy and Aims
This module provides part of the skills needed by developers to create modern software applications. It focuses on popular modelling techniques used in the design and construction of software systems. The techniques cover how a software system can be designed from a variety of viewpoints, different levels of mathematical abstraction and with various degrees of granularity. This feeds into the overall mathematical and scientific basis of the Computer Science course.
|
Indicative content
|
Study mode / delivery method(s): The module will be delivered using weekly practical classes, consisting of both lecture and activity material. Additional resources will be available on Moodle for self-study.
Practical activities will adopt a problem base approach to learning in conjunction with case studies to enable learning through practice and experience. |
Intended Learning Outcomes:
| |
Learning outcomes: | Learning and Teaching methods
|
1. Produce a design specification by applying appropriate analysis and design techniques to a problem domain |
This module will primarily be taught in weekly practical classes, where the materials will be introduced, students will have the opportunity to work on sample problems and to receive feedback. Students will also be provided with practice exercises to work on between classes and will be encouraged to use Moodle for peer discussion. A substantial part of the learning process will take place whilst the students are constructing their coursework solution.
|
2. Construct object-oriented models of software using UML
| |
3. Critically evaluate the role that design techniques play within the software industry
| |
4. Formalise a design using appropriate modelling techniques and mathematical abstractions
| |
Breakdown of study time[2]:
| |
Scheduled learning and teaching activities | 25% |
Guided independent learning | 75% |
Placement/study abroad | 0% |
Assessment and Feedback:
|
Summative assessment:
This module will be assessed by a Coursework, submitted mid-way through the module, and an Examination. The Phase Test is included to allow students to track their progress early on and for any common issues to be addressed.
Assessment 1 - Coursework – 40% Students will be required to construct a design specification for a given scenario using object modelling technique.. This assessment tests learning outcomes 1 and 2
Assessment 2 - Examination – 2 hours duration - 60% Unseen closed book examination involving UML modelling and mathematical abstractions, as well as incorporating a written question. This assessment tests learning outcomes 3 and 4
|
Breakdown of summative assessment methods[3]:
| |
Written exams: Practical exams: Coursework: | 60% |
0% | |
40% | |
Formative assessment:
Students will be provided with regular practice activities which can be reviewed in class for formative assessment reasons. Students will also be provided with sample papers for the Examination.
|
Feedback:
Feedback will be available regularly during teaching sessions.
Students will receive individual feedback of their coursework submission.
Cohort feedback will be made available after the examination detailing common errors and suggesting methods for improvement.
|
Related Modules This module builds on the programming concepts explored in the Level 4 module, Software Development UG1, providing the technical and scientific skills that underpin Computer Science.
|
Learning ResourcesRecommended Reading
Fowler. M. (2003), UML Distilled: A Brief Guide to the Standard Object Modeling Language – Third Edition, Addison Wesley
Freeman, E. (2004), Head First Design Patterns – First Edition, O’Reilly Media
McLaughlin, B., Police, G. and West, D. (2006), Head First Object-Oriented Analysis and Design: A Brain Friendly Guide to OOA&D – First Edition, O’Reilly Media
Pressman, R. (2009), Software Engineering – A Practitioner’s Approach – Seventh Edition, McGraw-Hill Higher Education
Somerville, I. (2009), Software Engineering – Ninth Edition, Pearson Education
Stevens, P. and Pooley, R. (2005), Using UML: Software Engineering with Objects and Components – Second Edition, Addison Wesley
|
[1] ECTS is the European Credit Transfer and Accumulation System which was developed to promote the international recognition of qualifications and student mobility within Europe.
[2] Please refer to the module specification guidance when completing this section
[3] Please refer to the module specification guidance when completing this section