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 2018-19 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.
 
2.  To provide students with an in-depth and critical understanding of the tools and techniques of software modelling and design.
 < /div>
3.  To provide students with a comprehensive understanding of the Object Oriented and Agile software development processes.
 
4.  To provide students with the opportunity to apply the skills learnt on this module in the context of practical software engineering scenarios so that they will be ready to apply immediately these skills in the workplace.

Learning Outcomes

Evidence a deep and systematic understanding of the process of software modelling and design within the context of the software life cycle.

Analyse software requirements and specifications and convert them into a number of alternative formal representations.

Apply the tools and techniques of software modelling and design in the workplace.

Demonstrate a deep and comprehensive knowledge of the Agile and object-oriented modelling and design processes.

Use pattern-centric design approaches and an ability to evaluate the fitness of design patterns for specific purposes.

Demonstrate a systematic understanding of how CASE tools are being used for different aspects of software engineering.


Syllabus
1 
Week 1: The Concept of Software Modelling and Design:
The main concepts of software modelling and design, what software modelling and design are and why they are important, the evolution of software modelling, the concepts of meta-modelling and model transformation.
 
Week 2: Agile Software development and Object Orientation:
Approaches to software development, their advantages and disadvantage, and the Agile software development methodology and its link to object-orientation.
 
Week 3: Software requirements modelling:
The formal steps in capturing and representing software requirements, understanding the types of requirements, how to model software requirements, use-case representation and the role of prototyping.
 
Week 4: Static Modelling techniques in software design:
Static software modelling concepts, such as: class definition, association, generalization/specialisation, composition/aggregation and polymorphism; and how to represent them using UML and other notations.
 
Week 5: Dynamic Modelling techniques in software design:
Dynamic software modelling concepts, such as object interaction, sequencing, data flow and workflow, and how to represent them using UML and other notations.
 
Week 6: Design patterns and software implementation:
Common software architectures and design patterns, tehnadvantages of design patterns and how they provide reusability, how to choose suitable patterns and the available Integrated Devel opment Environment (IDE) tools for implementation and debugging.
 
Week 7: Analysis of CASE tools:
Aspects of software development that can be aided by CASE tools, available CASE tools, the concepts of Lower and Upper CASE tools, CASE for user-interface design and for Web development.
 
Week 8: Using CASE tools:
Using CASE tools for software simulation, testing, debuging, documentation, version- control and configuration management; as well as understand ing how they can be useful for marketing and cost reduction.

Teaching and Learning Strategies

online Learning - Weekly seminar supported by asynchronous discussion in a virtual classroom environment facilitated by an online instructor.

Number of hours per week that students are expected to attend the virtual classroom so as to participate in discussion, dedicated to group work and individual assessments is 7.5

Teaching Schedule
  Lectures Seminars Tutorials Lab Practicals Fieldwork Placement Other TOTAL
Study Hours           60
Weekly seminar supported by asynchronous discussion in a virtual classroom environment facilitated by an online instructor.
60
Timetable (if known)           Number of hours per week that students are expected to attend the virtual classroom so as to participate in discussion, dedicated to group work and individual assessments is 7.5
  		 
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
Coursework  Weekly Discussion Qu  Whole session  40  No reassessment opportunity  Standard UoL penalty applies  Moot/debate: 8 Discussion Questions There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  One week, 750-1000 w  Week 1  10  No reassessment opportunity  Standard UoL penalty applies  Report: Modelling skills within software requirements There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  One week, 750-1000 w  Week 2  10  No reassessment opportunity  Standard UoL penalty applies  Report: Ad-hoc software development methodologies There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  One week, 750-1000 w  Week 3  10  No reassessment opportunity  Standard UoL penalty applies  Report: Software requirements There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  Two weeks: 1500-2000  Weeks 3- 4  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project: on User requirements There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  Two weeks: 1500-2000  Weeks 5-6  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project on Software Design There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. 
Coursework  Two weeks: 1500-2000  Weeks 7-8  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project: on Usage of CASE tools There is no reassessment opportunity, The nature of the adopted online learning paradigm is such that no reassessment opportunity is available, instead students failing the module will be offered the opportunity to retake the entire module. Notes (applying to all assessments) (1) Due to nature of the on­line mode of instruction work is not marked anonymously. (2) Students who fail the module have the opportunity to repeat the entire module. (3) The "Standard UoL Penalty" for late submission that applies is the "Standard UoL Penalty" agreed with respect to online programmes offered in collaboration with Laureate Online Education. (4) For group work assessments groups typically comprise 3 to 4 students. Both group and individual contributions are assessed and integrated to produce a final mark for each student. 

Recommended Texts
Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module.
Explanation of Reading List:

The online programmes offered by the department of Computer Science in Collaboration with Laureate Online Education use online materials wherever possible including the online resources available within the University of Liverpool’s libraries. This module does not require a specific text book.