APPENDIX A: Coursework Front Sheet

GHANA TECHNOLOGY UNIVERSTY COLLEGE/COVENTRYUNIVERSTY

FACULTY OF COMPUTING & INFORMATION SYSTEMS
Family Name(s) Ashraf Module No.

Forename(s) Oppong

ID Number(s) (from your student card) 050118013

Estimated Time taken (hrs) (per

Faculty Date Stamp
student for group coursework)
(or signature and date)
Lecturer Mr.George Kodjo Anni Lab group / Tutorial group / Tutor (if applicable)

Module Code and Title GTU302CEM System Development

Assignment No. / Title Course work Extensions & late submissions allowed:
Estimated Time Assignment type: (Individual/Group) % of Module Hand out date:
80 hours

Penalties: Marks will be reduced by 10% of the original mark for every week late. No work will be accepted that is more than two weeks late. If you
are unable to submit coursework on time due to extenuating circumstances you may be eligible for an extension.
Declaration: I/we the undersigned confirm that I/we have read and agree to abide by the University regulations on plagiarism and cheating and
Faculty coursework policies and procedures. I/we confirm that this piece of work is my/our own. I/we consent to appropriate storage of our work
for checking to ensure that there is no plagiarism/ academic cheating.
Signature(s):
Section A – To be completed by the student - PLEASE PRINT CLEARLY

Section B - To be completed by the assessor

Marks breakdown and Assessor’s Feedback Max Awarded

Please continue on the reverse of this sheet if needed.

Assessor’s name Assessor’s signature Total

Coursework Mark Extension Agreed until: (Yes / No) Deduction for Late Submission (Penalty) Final Mark

Date: Date:
Signed internal moderator: Programme Leader Signature:
This work may have been moderated. You may find additional comments in the work.
1
Group Members.

 Ashraf Oppong - 050118013

 Aboagye Francis - 050919033

 Kingsley Abaka Quagraine - 050918051

2
Extreme Programming as our Preferred SDLC

Introduction.

The agile software development life cycle is a well-organized sequence of steps that helps with
product development. The agile software development life cycle includes a number of frameworks
and methods.
 The Extreme Programming technique has teams working in shorter iterations and an emphasis
on engineering processes.
 The Extreme Programming technique has teams working in shorter iterations and an emphasis
on engineering processes.
 The SCRUM methodology utilizes sprints, which are discrete periods of time with well define
roles.

Based on this information, we made the decision to recommend the extreme programming technique
as the method for developing the insulin pump.
An insulin pump is a device that monitors your blood sugar levels using an embedded sensor. The
results are sent to a pump controller, which calculates the amount of insulin required. The pump
controller then sends a signal to the insulin dispenser in the form of a needle, causing the user to
receive the proper dosage of insulin. The end result of the insulin pump has very little margin for
mistake because it is a medical equipment. Given this, the pump's development should focus heavily
on its technical features while also being of the greatest quality.
The interface should be straightforward and efficient, and the codes should be accurate with
readings. For diabetes patients whose pancreas cannot produce enough insulin, the insulin pump is
an essential medical tool. The importance of the insulin pump to the user necessitates an aggressive
approach in its manufacture. An incident involving this device's user that goes wrong might be lethal.
The extreme programming methodology's goal is to enable small to mid-sized teams to produce high-
quality software while adhering to changing and growing requirements. It is founded on ideals, rules,
and customs.

The Extreme Programing Method.

The Extreme Programming technique places a strong emphasis on the technical elements of software
development and is meticulous about engineers' working methods, allowing teams to produce high-
quality codes at a steady rate. Engineers use extreme programming in accordance with a set of ideals
and concepts that are crucial to the functionality, significance, and overall manufacturing of the
insulin pump.

3
These values and principles are as follows:
 Communication: Lack of communication inhibits the information from flowing throughout
development.

 Simplicity: Simplicity is the pursuit of the most straightforward course of action.

 Respect: One of the core tenets of XP is that everyone is invested in their job. If there is no
care and respect, no amount of technical expertise can rescue a project.

 Courage: Since the goal of the end product is to have as few faults and problems as possible,
courage is the capacity to take risky actions in development and the willingness to call out
mistakes.

 Feedback: XP teams want to get early, consistent feedback because they welcome change. The
necessity for a course correction should be communicated to developers as soon as feasible.

By skipping lengthy stages, Extreme Programming (XP) varies significantly from conventional
approaches.

1. In XP, there is no planning phase; planning occurs at the beginning of each development cycle,
which lasts typically only one week.
2. You test your application as soon as feasible, that is, before the real code is produced, as opposed
to testing episodes.
3. You work in tiny pieces and integrate those chunks as frequently as you can rather than building
things in isolation during protracted implementation phases and then struggle to blend your
contributions with the main line.
4
By its very nature, extreme programming is different from the other agile approaches while
simultaneously sharing many similarities with them.
The majority of alternative development methodologies include very few, if any, mentions on how to
complete the work. On the other hand, XP has strong feelings on the matter and emphasizes software
engineering principles.
Finally, because it is an extreme technique that delves deeply into the codes and minutiae while
putting a focus on engineering standards, we advocate using it to develop the insulin pump. To get
the greatest results, we advocate using not one, but two agile software development methodologies,
namely the extreme programming and SCRUM approaches.

Functional and Non-functional requirements of the insulin pump

Introduction

The insulin pump is a gadget that analyses a user's blood insulin level and transmits a signal to an
associated insulin pump with a needle that measures and injects the user with the necessary amount
of insulin. The insulin pump must meet the five functional and non-functional requirements listed
below.

Non-functional requirements.

1. No insulin should be given if the measurement falls below the safe minimum.

2. Insulin is only administered if the blood sugar level is rising and rising more quickly. This
delivery is only made once the reading is within the safe range.

3. When blood sugar levels are dangerously low and readings are higher than the safe range,
insulin should be administered.

4. If the blood sugar level is higher than the recommended level, insulin should be administered
unless the blood sugar level is failing and the rate of blood sugar decrease is accelerating. To
counteract the current blood sugar level, the appropriate amount of insulin should be
administered.

5. Only those with diabetes are allowed to use this gadget.

Functional requirements

1. Insulin from the cartridge is correctly dispensed by the pump. Additionally, it must function in
total quiet.

5
 2. A necessary graphical user interface (GUI): The user and health management desire a
straightforward GUI on the pump controller so they can enter values, examine logs, and
control insulin input.

3. The presence of a cartridge: The cartridge houses an insulin supply. It is essential that the
insulin cartridge be clean and sanitary because it will be injected into the circulation.

4. The infusion set: This device links the body to the insulin pump. It is made up of a needle and a
skinny tube.

5. The Processing Module: This component serves as the "brain" of the system and serves as the
main controller for all other functional blocks. It manages programming, data archiving,
dosing, user communication, and insulin pump options.

Data Models of the Insulin Pump.

Use-case Diagram

6
Entity Relation Diagram

7
Sequence Diagram

Reflective Report.

Introduction

This section details each of our unique contributions to finishing this project. We divided the project
into sections as a trio, assigning each person in the group a specific task. We collaborated, each
member's work overlapping the others' even though each had a specific assignment to do. Each
member of the group conducted independent research, collated their findings, and presented their
findings to the other members.

8
Kingsley Abaka Quagraine

I decided to base the data model architecture on the provided scenario. I had to comprehend the insulin
pump's design and operation, as well as all the components and tools that went into its creation, the
creation of each necessary diagram, and the manner in which data moves through the system before I
could produce all the model designs that were needed. I was able to develop all the necessary diagrams
to reflect how the gadget is supposed to work by outlining the interaction between the user and the
device. With the help of my group members' insightful comments, we were able to produce the
system's final designs after I drew several draughts of the diagrams and had each of them reviewed.
Lack of additional details on how the insulin pump truly operates in the provided situation was my
primary barrier. I was able to understand how the technology works, though, because of my study.

Ashraf Oppong

I selected the assignment of determining which SDLC would work best with an insulin pump. In my
study, I read a lot about the many Agile SDLC frameworks and kinds, how they each operate, and the
benefits they all offer. I was torn between using the SCRUM technique or the Extreme programming
style because of the nature and functionality of the insulin pump.
Both might be utilized, and it is suggested that more than one SDLC be used to build a product in order
to enhance the likelihood of success. After weighing the pros and cons of each choice, I came to the
conclusion that the Extreme programming style is best for the insulin pump.
I discussed my results with the group members and asked for their opinions on the system I had
selected. I gave them the advantages and disadvantages of each suggested framework, along with the
strategy I thought would work best for an insulin pump.

Aboagye Francis

I was tasked with identifying the functional and non-functional needs for the insulin pump. I had to
conduct study on the functioning details of the insulin pump, its system requirements, and its manner
of operations before discovering the answers to the inquiry. I was able to determine the insulin pump's
functional and non-functional needs after compiling my research. I had trouble figuring out which
needs were useful and which ones weren't. However, after talking with the other members of my
group, we were able to reduce it to 5 needs per person.

Conclusion
This work was completed as a group, even if certain elements were done independently. To make sure
the task was finished, every aspect was examined together. Corrective action was then taken as needed.
Each team member received a copy of the research's results, and they all contributed significantly to
the project's success.