CS2SENU: Software Engineering and Professional Development

Module code: CS2SENU

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

Credits: 20

Level: Level 2 (Intermediate)

When you'll be taught: Semester 1

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

NUIST module lead: Gaofeng Wu, email: 003387@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

This module is designed to introduce students to software engineering as a systematic engineering approach to software development. Students will be exposed to study and practise software development paradigm, methodology, and software engineering methods and techniques which can be applied to inform software development, innovation, management, and sustainability in response to the fast-changing world in the digital ear.  

Students will also be able to demonstrate their profession skills of: 

• creative problem-solving and critical thinking; 
• communication and team-work; and 
• professional and effective writing for requirement documents and project reports. 

Module learning outcomes

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

1. Develop understanding of software engineering in relation to software architecture, methodology, and principles; 
2. Employ software engineering knowledge and skills in a given problem context; 
3. Apply a range of requitements methods, techniques, and quality management for meeting stakeholders’ needs and expectations; and 
4. Utilise professional skills in software engineering practices through software development projects. 

Module content

The module will cover the following topics: 

• Software architecture, framework and standards 
  • services-oriented enterprise architecture (corporate structure and functions, human factors, governance and norms, IT resources, ROI), integration architecture for evolving portfolios of software applications 
• SE paradigms, methodologies and tools 
  • requirements engineering and iterative development, software development processes and principles for design, implementation/prototyping, testing, evaluation, deployment, and versioning 
• Software development management 
  • software evolution, systems integration, scalability and performance, and maintenance, software project planning (e.g. time, budget, resources), managing people (environmental factors, teams, stakeholders’ behaviour, communication, leadership, and creativity) 
• Management of risk and ethics 
  • risk analysis and management framework, risk in relation to ethical and professional responsibilities, quantitative and qualitative risk evaluation 

Structure

Teaching and learning methods

This module will take a problem-based learning approach. Lectures will introduce students the software engineering theories and tools specified in Module Content. Students will be supervised through a series of practical sessions to apply the software engineering knowledge and skills in a given problem context and develop a technical solution. 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 two pieces in the forms of written coursework assignment and examination. 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 when appropriate.   

Reassessment

Additional costs