CS1SE20-Software Engineering: Fundamentals and Professional Development

Module Provider: Computer Science
Number of credits: 20 [10 ECTS credits]
Level:4
Terms in which taught: Autumn / Spring term module
Pre-requisites:
Non-modular pre-requisites:
Co-requisites:
Modules excluded:
Current from: 2022/3

Module Convenor: Dr Muhammad Arifur Rahman
Email: muhammadarifur.rahman@reading.ac.uk

Type of module:

Summary module description:

This module introduces students to the concepts, practice and management in software engineering and the professional development to support it. It addresses the lifecycle activities associated with developing software as part of a system as well as the management activities required to ensure that the software is developed on time, within budget and is fit for purpose. The module also incorporates case studies and examples to show the application of the concepts and principles to real-world systems.

A learning approach is adopted which reflects software engineering theory and practice. Students ÌýÌýare given course material to read/view prior to the lectures, and are required to produce a number of assessments in teams.

Aims:

This module will provide an understanding of the concepts, practice and management of software engineering and how it relates to the wider context of systems engineering.

This module also encourages students to develop a set of professional skills, such as problem solving, end-user awareness, organisation and time management, creativity, self-reflection, software Ìýdesign and development, technical report writing, team working, initiative and self-motivation, action planning and decision making, effective use of commercial (and non-commercial) software, personal development planning, commercial awareness, appreciation of multiple perspectives and values of diversity.

Assessable learning outcomes:

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

• Understand the software engineering theory, and practice them in developing software applications in the wide domain context


• Describe the software lifecycle and the activities associated with each phase of it (feasibility, requirements, design, implementation, testing, handover, maintenance, evolution, and decommissioning)


• Create software application development project plans, and conduct risk analysis, configuration management and testing


• Distinguish the difference between plan-based and agile-based approaches to software development


• Appreciate the importance of software engineering to real-world projects


• Work jointly with others in a group project as well as being able to work independently


• Demonstrate innovative, creative, and critical thinking towardsa development of solution


• Perform in communication and documentation

Additional outcomes:

The module also aims to encourage the development of questioning and clarifying problem specifications.

Outline content:

The module draws on the IEEE’s articulation of knowledge on the subject, as presented in the Software Engineering Book of Knowledge v3 (SWEBOK).

• ÌýIntroduction to Software Engineering (e.g. models, methods, processes, and management).


• Human factors in Software Engineering


• Software requirements fundamentals, processes, requirements elicitation techniques/tools


• Software design fundamentals, architecture, design techniques and modelling approaches


• Software construction fundamentals, technologies/tools, environments


• Software validation methods, and testing techniques


• Software maintenance and configuration management


• Software quality requirements, measurement, and management


• Software Engineering professional practices (e.g. professionalism, legal, ethical, economic impact of software, documentation, communication skills in written and presentation form)


• Software Engineering in the modern computing era (e.g. DevOps transformation)

Brief description of teaching and learning methods:

This module will be delivered through lectures and interactions in tutorials/seminars as well as assignments.

Contact hours:

Ìý	Autumn	Spring	Summer
Lectures	10	10
Seminars	10	10
Guided independent study:	Ìý	Ìý	Ìý
Ìý Ìý Wider reading (independent)	15	15
Ìý Ìý Wider reading (directed)	5	5
Ìý Ìý Exam revision/preparation		10	10
Ìý Ìý Advance preparation for classes	10	10
Ìý Ìý Group study tasks	15	15
Ìý Ìý Essay preparation	15	15
Ìý Ìý Reflection	10	10
Ìý	Ìý	Ìý	Ìý
Total hours by term	90	100	10
Ìý	Ìý	Ìý	Ìý
Total hours for module	200

Summative Assessment Methods:

Method	Percentage
Written exam	30
Set exercise	70

Summative assessment- Examinations:

One 2-hour examination paper in May/June.

Summative assessment- Coursework and in-class tests:

There are two pieces of coursework:

• problem-based exercises in software engineering (30%, in Autumn Term)


• written assignment (40% in Spring Term)

Formative assessment methods:

Formative feedback occurs throughout weekly set exercise to support the learning.

Penalties for late submission:

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

• 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 five working days;
• where the piece of work is submitted more than five working days after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.

The University policy statement on penalties for late submission can be found at: /cqsd/-/media/project/functions/cqsd/documents/cqsd-old-site-documents/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.

Assessment requirements for a pass:

A mark of 40% overall

Reassessment arrangements:

One 3-hour examination paper in August/September.Ìý Note that the resit module mark will be the higher of (a) the mark from this resit exam and (b) an average of this resit exam mark and previous coursework marks, weighted as per the first attempt (30% exam, 70% coursework).

Additional Costs (specified where applicable):

1) Required text books:ÌýÌý

2) Specialist equipment or materials:ÌýÌý

3) Specialist clothing, footwear or headgear:ÌýÌý

4) Printing and binding:ÌýÌý

5) Computers and devices with a particular specification:ÌýÌý

6) Travel, accommodation and subsistence:ÌýÌý

Last updated: 11 October 2022