CI7260 Research report

Kingston University Assignment Brief

School of Computer Science and Mathematics

Module Code CI7260

Module Title Software Quality Engineering

Assessment Title Research report

Element Label CWK Part 1

Type Summative 40% of module mark

Set by S. Khaddaj & J. Dehmeshki

Assessment due date and time 13/04/26 at 23:59

Formal feedback due date 27/04/2026

All assignments must be submitted by the date and time specified above.

You are required to submit an electronic copy of your completed assignment, in the file

format(s) specified by the module team (e.g., Word, PDF, programme code files), via the

Assignments section of Canvas and follow any specific instructions provided. Any change to this

instruction will be advised via Canvas.

If files are shared outside of Canvas (where specified by the module team), you must ensure

that the files are accessible and available for staff to access without the need to request

additional access privileges.

In line with University Regulations coursework submitted up to a week late will be capped at

50%. Coursework submitted after this time will receive 0%.

In case of illness or other issues affecting your studies please refer to the University Mitigating

Circumstances and Extensions Regulations. Please note that once you have submitted your work

you have judged yourself fit to undertake the assessment and cannot usually claim mitigating

circumstances retrospectively. Please refer to the Mitigating Circumstances Regulations for more

information.

Guidance on avoiding academic assessment offences such as plagiarism and collusion can be

found in the Digital Learning and Tools module on Canvas see Academic Integrity.

PURPOSE OF THIS ASSESSMENT / WHAT IS EXPECTED

Aim: To Develop a Software Quality Management System (SQMS) – Requirement Stage for

the following scenario:

Scenario: Healthcare Appointment Management System (HAMS)

The hospital seeks to develop an automated Healthcare Appointment Management System (HAMS) with

the following features:

Patient Portal: Book, reschedule, and cancel appointments via a web/mobile interface.

Doctor Management: Doctors can manage their availability, schedule, and patient interactions.

Automated Slot Suggestion: Automated scheduling system to optimise doctor-patient appointments

(optional)

Electronic Health Record (EHR) Integration: Secure data storage and retrieval.

Performance & Security: Ensuring system efficiency and protection against cyber threats.

Page 2 of 4 Version: 5.1 (5th August 2025)

Part1 – Software Quality Management System (SQMS) – Requirement

Stage

Each student must define and document the requirements for the HAMS project, ensuring compliance with

software quality assurance principles.

1. Standard Operating Procedures (SOPs) for Software Quality (10%)

o Define quality control procedures for software development.

o Outline roles and responsibilities for quality assurance.

o Specify compliance with ISO 25010 or relevant industry standards.

2. Software Requirement Specification (SRS) (10%)

o Functional Requirements: Define core features (appointment booking, scheduling,

notifications, etc.).

o Non-Functional Requirements: Performance, security, usability, and regulatory compliance.

o Use Cases diagrams: Visual representation of system interaction.

o User Stories: Describe user needs and interactions.

3. Software Quality Plan (SQP) (10%)

o Define quality metrics (e.g., performance, security, usability).

o Establish code review.

o Plan for configuration and version control (Git or other VCS).

4. Risk Analysis & Mitigation Plan (10%)

o Identify potential risks (e.g., system failures, data breaches, incorrect scheduling).

o Propose mitigation strategies to prevent issues.

o Perform a Risk Assessment Matrix (Probability vs. Impact).

LEARNING OUTCOMES

The following module learning outcomes and professional body learning outcomes are tested in

this assessment:

To understand the concepts and practices of software quality engineering in software

developments, and to establish in-depth understanding of principles of software quality

assurance and software testing techniques.

To provide a broad and strong understanding of applying theories and practices of software

quality assurance throughout the software development lifecycle.

Can I use Generative AI (GAI) as part of this Task?

Default use of GAI: you are permitted to use Generative AI for the following purposes:

Support spelling, punctuation and grammar.

Support ideation.

Create a structure or outline for the assignment.

Support research for the assignment (identifying sources, search).

Take the role of a constructive critic.

Aid understanding.

Page 3 of 4 Version: 5.1 (5th August 2025)

Produce media artefacts to support the assignment where the artefacts are not the

primary focus of the assessment.

Perform basic image / media editing encompassing cropping, noise reduction,

sharpening, enlarging, compression, changing format type and adjusting lighting.

Please note: all of the core writing, creativity, arguments, analysis and reasoning must be your

own

For further details on this GAI Assessment category please see:

Student Guide to GAI at Kingston University 2025/6 in the Digital Learning and Tools module in

Canvas (Generative AI section).

Do I need to declare my use of GAI tools?

Yes, if you use Generative AI for any part of your assessment, you must declare this. This

applies to all assessments including those in the default and explicit categories.

For this assignment the declaration should be provided at the end of the submission with the

heading Acknowledgement of GAI Contribution. This declaration should include a statement on

the use of generative AI including the extent of use, and how it was used as part of all stages in

creating the final submission.

For assessments that fall into the explicit category (does not apply to the purposes listed in the

Default category), any GAI content included in the assignment, e.g., a quoted paragraph of text

or an image, should be properly cited as with any non-GAI source.

Further guidance on completing this acknowledgement is provided in the Digital Learning and

Tools module in Canvas (Generative AI section).

The module team may also provide additional advice on the specific details required, depending

on the nature of the GAI tool used.

You will also need to read and accept the similarity declaration when submitting an assignment

in Canvas.

FURTHER INFORMATION ABOUT THIS ASSESSMENT

You will receive the feedback electronically using the feedback form.

MARKING CRITERIA

Page 4 of 4 Version: 5.1 (5th August 2025)

Assessment of your submission will be based on the following weighted assessment criteria as

given below which relate to the specified module and PSRB learning outcomes. Assessment

criteria are reproduced in Canvas in a rubric.

Standard Operating Procedures (SOPs) for Software Quality ( /10)

** VG G F P VP

Definition of quality control procedures

Outlining roles and responsibilities

Software Requirement Specification ( /10)

** VG G F P VP

Functional and non-functional requirements

Use Cases diagrams and user stories

Software Quality Plan (SQP) ( /10)

** VG G F P VP

Definition of quality metrics

Code review, configuration and version control

Risk Analysis & Report ( /10)

** VG G F P VP

Identification of potential risks and mitigation strategies

Report structure

Total 40 Marks

ACADEMIC SKILLS SUPPORT

For help and advice on this assessment please contact the assessment setter/s or the module

leader.

WRITE MY PAPER