CS2SDNU: Software Systems Design

Module code: CS2SDNU

Module provider: Computer Science; School of Mathematical, Physical and Computational Sciences

Credits: 20

Level: Level 2 (Intermediate)

When you'll be taught: Semester 2

Module convenor: Dr Lily Sun, email: lily.sun@reading.ac.uk

NUIST module lead: Loza Sappa, email: 100087@nuist.edu.cn

Pre-requisite module(s):

Co-requisite module(s):

Pre-requisite or Co-requisite module(s):

Module(s) excluded:

Placement information: NA

Academic year: 2024/5

Available to visiting students: No

Talis reading list: No

Last updated: 21 May 2024

Overview

Module aims and purpose

The module is designed to equip students with a solid understanding of object-oriented analysis and design (OOAD) concepts and principles. The module is focused on using Unified Modelling Language (UML) to design software systems from conceptual structure and physical behaviour perspectives. Students will learn a suite of UML techniques that they can apply in real-world problem contexts.  

Through the module, students will gain an understanding of software engineering methodology in relation to software development and learn UML techniques for modelling system requirements and specifications that meet stakeholder needs. The practical activities will give students hands-on experience that will enhance their abilities in professional software development. 

This module also encourages students to develop a set of professional skills that will benefit them in their careers. These skills encompass problem-solving, teamwork, and effective communication. Additionally, it promotes critical reflection on the quality and impact of the software design process and outcomes, as well as the importance of meticulousness and precision in requirements analysis and solution design, professional and articulate writing skills for technical report composition, while nurturing creativity, critical thinking abilities, and effective task and time management. The module helps students to develop these skills through project work, group work, and designated assignments. 

Module learning outcomes

By the end of the module, it is expected that students will be able to:

1. Understand the object-oriented analysis and design theory in software engineering;
2. Adopt a “Systems Thinking” approach in conducting users’ requirements analysis and then generating the software system’s specifications;
3. Master the UML methods and techniques including their individual design role, concepts, and principles as well as their interrelationships; and
4. Apply the UML techniques in a given domain context and evaluate design decisions.

Module content

The module covers the following topics: 

• OO analysis and design theory and process; 
• UML methodology for guiding articulation of requirements and formulation of specifications; 
• UML techniques specific design concepts and principles; 
• Modelling requirement specifications in a given domain context; 
• Validation of models based on their interrelationships through input/output; and  
• Evaluation of ethics, extensibility and reusability of the design. 

Structure

Teaching and learning methods

This module will take a problem-based learning approach. The lectures will introduce students the theories, concepts and underpinning principles specified in the module content. Students will be supervised in the practical sessions to apply the concepts and principles to a given problem context and develop a technical solution.  

The lectures and practical sessions will enable students to inquiry innovative solutions, and critically apply the UML methodology and the techniques to design and document the resultant models. 

There will also be learning materials in digital forms when they are required to support learning.  

There are two types of assessment (i.e., formative assessment and summative assessment) which will support and reinforce students’ learning. A formative assessment is carried out through weekly learning activities. Summative assessment consists of one piece of written coursework assignment which requires students to demonstrate both individual and group achievements. Appropriate feedback will be timely communicated with students for enhancing learning.  

Study hours

At least 44 hours of scheduled teaching and learning activities will be delivered in person, with the remaining hours for scheduled and self-scheduled teaching and learning activities delivered either in person or online. You will receive further details about how these hours will be delivered before the start of the module.

Please note the independent study hours above are notional numbers of hours; each student will approach studying in different ways. We would advise you to reflect on your learning and the number of hours you are allocating to these tasks.

Semester 1 The hours in this column may include hours during the Christmas holiday period.

Semester 2 The hours in this column may include hours during the Easter holiday period.

Summer The hours in this column will take place during the summer holidays and may be at the start and/or end of the module.

Assessment

Requirements for a pass

Students need to achieve an overall module mark of 40% to pass this module.

Summative assessment

Penalties for late submission of summative assessment

The Support Centres will apply the following penalties for work submitted late:

Assessments with numerical marks

• where the piece of work is submitted after the original deadline (or any formally agreed extension to the deadline): 10% of the total marks available for that piece of work will be deducted from the mark for each working day (or part thereof) following the deadline up to a total of three working days;
• the mark awarded due to the imposition of the penalty shall not fall below the threshold pass mark, namely 40% in the case of modules at Levels 4-6 (i.e. undergraduate modules for Parts 1-3) and 50% in the case of Level 7 modules offered as part of an Integrated Masters or taught postgraduate degree programme;
• where the piece of work is awarded a mark below the threshold pass mark prior to any penalty being imposed, and is submitted up to three working days after the original deadline (or any formally agreed extension to the deadline), no penalty shall be imposed;
• where the piece of work is submitted more than three working days after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.

Assessments marked Pass/Fail

• where the piece of work is submitted within three working days of the deadline (or any formally agreed extension of the deadline): no penalty will be applied;
• where the piece of work is submitted more than three working days after the original deadline (or any formally agreed extension of the deadline): a grade of Fail will be awarded.

The University policy statement on penalties for late submission can be found at: /cqsd/-/media/project/functions/cqsd/documents/qap/penaltiesforlatesubmission.pdf

You are strongly advised to ensure that coursework is submitted by the relevant deadline. You should note that it is advisable to submit work in an unfinished state rather than to fail to submit any work.

Formative assessment

Formative assessment is any task or activity which creates feedback (or feedforward) for you about your learning, but which does not contribute towards your overall module mark.

Each topic in a week has defined learning tasks which will enable students to self-reflect on the learning. Each practical session in a week will be severed as to facilitate the learning with personalised feedback provided towards the overall learning in this subject. 

Outcomes of the formative assessment for each topic may be shared in the first 30 mins in the practical session in each week.   

Reassessment

Additional costs