CS2SS20-Software System Design with UML

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

Module Convenor: Dr Lily Sun
Email: lily.sun@reading.ac.uk

Type of module:

Summary module description:

This module delivers the Unified Modelling Language (UML) methodology and its selected techniques which aid to articulate system users’ needs and then transform the needs on to software application solutions. Students will be engaged in an interactive learning environment in that they develop professional application design knowledge and skills.

Aims:

The module aims to enable students to master the UML methodology and apply it to a given real life scenario. Students will produce a set of design models and validate them by adopting the UML design principles. The UML methodology will be studied and practised through the theoretical learning and interactive workshops.

This module also encourages students to develop a set of professional skills, such as problem solving; end-user awareness; creativity and critical thinking; technical report writing for technical and non-technical audiences; team working; negotiation and persuasion; effective use of commercial software; and organisation and time management.

Assessable learning outcomes:

A student completing the module should be able to

• Understand the object-oriented (OO) systems theory;


• Establish a “Systems Thinking” approach for conducting requirement analysis and software design;


• Master the UML methodology including its techniques to modelling requirements specifications; and


• Apply the UML techniques in a context domain and evaluate design decisions.

Additional outcomes:

A student completing the module should also develop the competencies as follows.

• Team work and communication;


• Systems thinking in problem solving;


• Critical reflection towards implications;


• Rigorousness and preciseness in requirement analysis and solution design; and


• Professional writing.

Outline content:

• OO design theory and process;


• UML design methodology;


• UML techniques with their concepts and principles;


• Requirement specifications modelling in both static and dynamic perspective in a given context; and


• Validation of the models and their input and output.

Brief description of 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 indicative content. Students will be supervised in the practicals to apply the concepts and principles to a given problem context and develop a technical solution. The lectures and tutorials will enable students to inquiry innovative solutions, and critically apply the UML methodology and its techniques to design and document the res ultant products.

Contact hours:

��	Autumn	Spring	Summer
Lectures	10
Practicals classes and workshops	10
Guided independent study:	��	��	��
�� �� Wider reading (independent)	10
�� �� Peer assisted learning	10
�� �� Advance preparation for classes	10
�� �� Preparation of practical report	30
�� �� Completion of formative assessment tasks	5
�� �� Group study tasks	10
�� �� Reflection	5
��	��	��	��
Total hours by term	100	0	0
��	��	��	��
Total hours for module	100

Summative Assessment Methods:

Method	Percentage
Written exam	50
Set exercise	50

Summative assessment- Examinations:

One 1.5-hour examination paper in May/June.

Summative assessment- Coursework and in-class tests:

One group assignment on software systems modelling.��

Formative assessment methods:

The seminar sessions are used for conducting the formative assessment where feedback is provided to the design work throughout the term.

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 2-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 (50% exam, 50% coursework).

Additional Costs (specified where applicable):

1) Required text books:��students may purchase own text book.

2) Specialist equipment or materials:�� None

3) Specialist clothing, footwear or headgear:�� None

4) Printing and binding:�� None

5) Computers and devices with a particular specification:�� None

6) Travel, accommodation and subsistence:�� None

Last updated: 30 March 2023