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 2022-23 Level 7 FHEQ Whole Session 15

Aims

To provide students with a deep and comprehensive knowledge of the software engineering discipline.

To prepare students for employmnet in the software engineering industry.

To provide students with a critical ability to use state of art software engineering tools.

To provide students with the necessary skills to work within software development teams.

To provide students with a critical understanding of recent developments in the techniques, technologies and tools of software engineering.

Learning Outcomes

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

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

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

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

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

(S1) Organisational skills

(S2) IT skills

(S3) Communication and collaboration

(S4) Online learning skills

(S5) Problem solving/critical thinking/creativity

(S6) Team (group) working respecting others, co-operating, negotiating / persuading, awareness of interdependence with others

Syllabus
 

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.

Week 4: Gathering and modelling Requirements
Type of requirements (fu nctional 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 t rends
Constraints of non-functional requirements 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

Teaching Method 1 - Online Learning
Description: Weekly seminar supported by asynchronous discussion in a virtual classroom environment facilitated by an online instructor.
Attendance Recorded: Yes
Notes: 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

 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 Software Development (Part 3) 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 Development (Part 1) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 1-2  0    10       
Report: Group Project on Software Development (Part 2) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 4-5  0    10       
Design Output: Baseline Software Architecture Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 5-6  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       
Report: Self-managing development teams and their benefits. Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 3  0    10       
Design Output: Modelling Software Requirements Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 4  0    10       

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