Agile

SCHOOL OF COMPUTING, MEDIA AND THE ARTS

ICA SPECIFICATION

Module Title:

Agile Development

Module Leader: Tariq Alwada'n

Module Code:

CIS1017-N

Assignment Title:

Privacy Preferences for Electronic Medical Records

Deadline Date: Friday 15-January-2021

Deadline Time: 4:00pm

Submission Method: Blackboard

Online Submission Notes:

 Please follow carefully the instructions given on the Assignment Specification

 When an extension has been granted, a fully completed and signed Extension form must be submitted to the SCMA Reception.

Page 1 of 4

The work submitted MUST be your own. All cases of suspected plagiarism will be treated

seriously. Your attention is drawn to the sections on Plagiarism in the Student Handbook

for your course.

Introduction

This is an individual ICA, to be completed separately by each student. The deliverables are

a report containing answers to Element 1 below, and a Mendix project as a solution to

Element 2, which can be run by your tutors.

The Privacy Preferences for Electronic Medical Records Application.

This is described in documents posted on the Blackboard module site, Assessments

folder. These are:

• A description of the EMR application: RDTs_ICA_Application_oct18.pdf

• Example of different presentation: DifferentFormatForQuestions.pdf

Read the documents to gain an overall understanding of the proposed application.

You will develop a prototype application which will:

a. Provide login (by password) for Patients, Doctors and Healthcare

Administrators.

b. Enable a Patient to enter a decision as to whether their identifiable data can

be used for service planning and evaluation, Decisions to be recorded in the

Patient’s Electronic Medical Record.

c. Enable a Patient to enter a yes/no decision as to whether they consent to be

contacted for possible participation in a research study. If they do consent,

display a screen indicating the various sharing options available, eg

“Researchers in the NHS”, “Research by charities”, and record all decisions

in the Patient’s Electronic Medical Record.

d. If the response to the initial consent question in (c) above is “yes”, enable the

Patient to enter the names of research organisations, eg “Newcastle

University”, “Connected Health Cities”, which they would be happy to donate

their identifiable data to for research purposes. Also enter the type of

organisation, eg “University or academic researchers” if you had previously

entered “Newcastle University”. Record all decisions in the Patient’s

Electronic Medical Record.

e. Provide basic query facilities for the above data (this is already supported by

Mendix).

f. Enable Doctors and Healthcare Administrators to view the decisions and

information entered by the Patient as described above, but not to change

them.

Page 2 of 4

Note that this ICA does not require you to model and create an application which will store

details of medical problems, illnesses, operations, etc – you can assume these are stored in

another part of the application - not included in this ICA.

ICA Element 1 (50%) Report

Design

Determine a list of requirements for the project using:

a) Use Case Diagram

b) User Stories

c) Data Model (a screenshot of a Mendix domain model)

d) Wireframes for the user interfaces (Mendix template screens with non-

functioning buttons/links).

Test Plan

Design and develop a test plan for user acceptance testing. This should include a

test script (a set of user instructions and expected outcomes) for your user to follow

when testing your product. You should relate your test plan back to your original

requirements, eg to your user stories.

Screenshots of your running application

Evaluation

Write a critical evaluation of your application, (min 400 words).

Should include:

 Discuss the success of the application.

 Consider ways in which the application might be improved

ICA Element 2 (50%) Implementation

Implement a solution using Mendix, which is compatible with the designs described in your

Element 1 report. Enter a limited amount of test data.

Your Test Plan should give enough information to enable your tutors to run it.

Page 3 of 4

Assessment Criteria

A Completed to a

professional standard

B Good attempt

C Adequately

Demonstrated

D Satisfactory Attempt

E Little/No Evidence

Design (30 marks)

Use Case User Stories Wireframes

Evidence exists that the client has been considered fully in the design phase and in the development of a client focused solution. Design techniques applied rigorously without error.

Evidence exists that the client has been considered in the design phase and in the development of the application. Design techniques applied appropriately. Minor errors only.

Some evidence exists that the client has been considered in the design and in the development of the application. Some understanding of the design techniques is evident but there are some errors in their application.

Some evidence exists that the client has been considered. The designs contain some errors which are evidence of misunderstanding the brief. An attempt at the designs has been made but there are significant errors and inadequate evidence of understanding

No evidence exists that the client has been considered and the project brief has been largely misunderstood. There is little or no evidence of the application of basic design techniques. This has either not been attempt or not understood.

Test Plan (10 marks)

A test plan demonstrating detailed tests, expected and actual outcomes, has been designed and used fully.

A test plan demonstrating key tests, expected and actual outcomes has been designed and used fully.

A test plan demonstrating key tests, and results has been designed and used satisfactorily

A test plan has been designed but does not describe detailed tests and has not been implemented well.

Little or no evidence of testing or an approach for testing exists

Page 4 of 4

Evaluation (10 marks)

Evaluation document provides a comprehensive discussion of the success of the application and a detailed account of how the application might be improved.

Evaluation document provides a detailed discussion of the success of the application and a good account of how the application might be improved

Evaluation document provides a reasonable discussion of the success of the application and there is some account of how the application might be improved

Evaluation document provides a satisfactory discussion of the success of the application and there is some account of how the application might be improved

Little/No evidence of any discussion.

Implementation

Data Model (25 marks)

An excellent Data Model which is designed without errors. The application has been designed well for C/R/U/D

A good Data Model developed during the analysis phase. The application uses the database with only minor errors.

A basic but reasonable Data Model with no significant errors. The application could make better use of the data model.

Data Model contains significant errors but a satisfactory attempt has been made

The Data Model contains significant errors and does not satisfy the brief. The application has not been considered in the design of the database.

Controls (25 marks)

An excellent use of controls to create a very user friendly and professional application Tool used to the best of its capabilities

Good use of controls with no errors. Tool used reasonably well.

Satisfactory use of controls. Some inappropriate use of controls but no significant problems Tool used with some understanding of its potential

Use of controls has been demonstrated but the interface could be easier to use with some different choices. Tool not used well, but a satisfactory attempt has been made.

No evidence of thought regarding the usability of the application. Little/No evidence of appropriate use of the tool in developing a solution.

Assessment Marking Criteria % Overall Grade

40% and above Pass: A, B, C, D Less than 40% Fail