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 ENGINEERING AND SYSTEMS ARCHITECTURE
Code CKIT534
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 deep and comprehensive knowledge of the software engineering discipline.
  2. To prepare students for employmnet in the software engineering industry.
  3. To provide students with a critical ability to use state of art software engineering tools.
  4. To provide students with the necessary skills to work within software development teams.
  5. To provide students with a critical understanding of recent developments in the techniques, technologies and tools of software engineering.

 

Learning Outcomes

Articulate software engineering as a problem-solving process that produces quality software system solutions based on resilient architectures.

Evaluate critically approaches to the project management of software development projects.

Create software artifacts as a member of a virtual global agile software development team using team communication and collaborative tools.

Apply the software engineering techniques of requirement analysis, architecture design and testing in the context of a variety of software development projects.

Evaluate critically techniques for software configuration management, maintenance and support.

Syllabus
1 
Week 1: Introduction to the Software Engineering discipline
Definition of software engineering as a problem solving process. Introduction to software management approaches. Software development phases (requirements, analysis, design, building, deploying, maintenance, etc), and the purpose of each phase. Software systems as products of software engineering and their architectures. Software development teams and tools.
 
Week 2: Methodologies for managing software development projects
Approaches to managing software development projects. The waterfall, iterative, incremental and agile software development approaches and when to use each; differences and similarities.
 
Week 3: Working in software development teams
Roles and responsibilities of software development team members. Communication and collaboration tools to foster teamwork. Emphasis is on global and virtual teams.
 < /div>
Week 4: Gathering and modelling Requirements
Type of requirements (functional and non-functional). Techniques for gathering requirements. Requirement engineering, analysis and modelling.
 
Week 5 : Designing a baseline software system architecture
System modelling from requirements, modelling tools (e.g. UML), various models (e.g. functional, structural, behavioural), software system architecture, architecture styles, validating software architectures.
 
Week 6: Designing and implementing software modules/components
Technologies (e.g. Object-Oriented) and strategies (e.g. using design patterns) for the design and implementation of software modules/components.
 
Week 7: Delivering software systems, support, maintenance and improving the software development process
Software delivery issues (training and documentation). Strategies, techniques, and tools for software maintenance and support. Methods, tools and standards to improve the development process.
 
Week 8: Software engineering constraints and technology trends
Constraints of non-functional r equirements such as reliability, availability, security and performance. New and evolving trends in software engineering (e.g. model-based development, domain-specific languages, cross-platform development).

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 assessment 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 assessment 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  Two weeks: 1500-­ 2  Weeks 1-2  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project on Software Development (Part 1) 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  Week 3  10  No reassessment opportunity  Standard UoL penalty applies  Report: Self-managing development teams and their benefits. 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  Week 4  10  No reassessment opportunity  Standard UoL penalty applies  Design Output: Modelling 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-­20  Weeks 4-5  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project on Software Development (Part 2) 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  Weeks 5-6  10  No reassessment opportunity  Standard UoL penalty applies  Design Output: Baseline Software Architecture 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-­20  Weeks 7-8  10  No reassessment opportunity  Standard UoL penalty applies  Report: Group Project on Software Development (Part 3) 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.