Module Details |
The information contained in this module specification was correct at the time of publication but may be subject to change, either during the session because of unforeseen circumstances, or following review of the module at the end of the session. Queries about the module should be directed to the member of staff with responsibility for the module. |
Title | SOFTWARE MODELLING AND DESIGN | ||
Code | CKIT537 | ||
Coordinator |
Mr K Dures Computer Science K.Dures@liverpool.ac.uk |
||
Year | CATS Level | Semester | CATS Value |
Session 2022-23 | Level 7 FHEQ | Whole Session | 15 |
Aims |
|
1. To provide students with a comprehensive understanding of the role of software modelling and design within the context of the modern software development process. |
Learning Outcomes |
|
(LO1) Evidence a deep and systematic understanding of the process of software modelling and design within the context of the software life cycle. |
|
(LO2) Analyse software requirements and specifications and convert them into a number of alternative formal representations. |
|
(LO3) Apply the tools and techniques of software modelling and design in the workplace. |
|
(LO4) Demonstrate a deep and comprehensive knowledge of the Agile and object-oriented modelling and design processes. |
|
(LO5) Use pattern-centric design approaches and an ability to evaluate the fitness of design patterns for specific purposes. |
|
(LO6) Demonstrate a systematic understanding of how CASE tools are being used for different aspects of software engineering. |
|
(S1) Organisational skills |
|
(S2) IT skills |
|
(S3) Communication and collaboration online participating in digital networks for learning and research |
|
(S4) Information literacy online |
|
(S5) Problem solving/ critical thinking/creativity |
|
(S6) Team (group) working respecting others, co-operating, negotiating / persuading, awareness of interdependence with others |
Syllabus |
|
Week 1: The Concept of Software Modelling and Design : |
Teaching and Learning Strategies |
|
Teaching Method 1 - online Learning |
Teaching Schedule |
Lectures | Seminars | Tutorials | Lab Practicals | Fieldwork Placement | Other | TOTAL | |
Study Hours |
60 |
60 | |||||
Timetable (if known) | |||||||
Private Study | 90 | ||||||
TOTAL HOURS | 150 |
Assessment |
||||||
EXAM | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
CONTINUOUS | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
Report: Group Project: on Usage of CASE tools Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 7-8 | 0 | 10 | ||||
Report: Group Project on Software Design Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 5-6 | 0 | 10 | ||||
Report: Group Project: on User requirements Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 3- 4 | 0 | 10 | ||||
Report: Software requirements Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 3 | 0 | 10 | ||||
Report: Ad-hoc software development methodologies Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 2 | 0 | 10 | ||||
Report: Modelling skills within software requirements Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 1 | 0 | 10 | ||||
Moot/debate: 8 Discussion Questions Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Whole session | 0 | 40 |
Recommended Texts |
|
Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module. |