Individual Report. Student Name: Conor Flanagan SID:

Transcription

1 Individual Report Student Name: Conor Flanagan SID: Task 1: To complete design specification, implementation, testing and integration evidence with a report supported by research with references in the CU Harvard referencing style in a maximum of 1,000 words Design Report The key functionality I have chosen to design and implement is that of check-in customers to booked sessions. The Class Diagram above details my design for the check-in functionality for the Sphere Booking & Check-In System case study. The design adheres to the layered architectural style, utilizing the User Interface Layer to present the GUI boundary class named CheckInGUI which presents the menu UI, handling inputs and outputs of the functionality. This class will simply contain the UI objects, as well as code generated by our chosen library to generate the main GUI. The Application Logic Layer contains a facade controller class named CheckInController which represents the whole functionality and controls all the other classes, takes input from and outputs to the User Interface Layer via a one-to-one multiplicity with the CheckInGUI class, and requests and sends data to the database via the data classes. Customer and Session data are stored via their respective data classes in the Domain Data Layer, and their equivalent Data Access Layer classes (customerdb and sessiondb) handle the data reading and writing, and permeate the data to the SQL server database (YL Hedley 2016). This design attempts to apply the principles of the General Responsibility Assignment Software Patterns (henceforth referred to as GRASP). GRASP implies that responsibilities of a system can be provided by applying specific principles and idioms as a pattern, a structured format describing the problem and solution (C Larman 1998). Each pattern has a name, definition, and requires forethought to program into the system. The CheckInController class uses a Facade Controller pattern, which means that the responsibility for receiving and handling system events is assigned to the class. This ensures that all system events are managed by the same class in the same use case scenario. The Information Expert pattern requires that responsibilities for handling data are assigned to the class that has the information necessary to fulfill it. For my functionality, the information required to check-in a customer would be the session data and the customer data from the database. As each of these are stored in a database and accessed individually, the information can be fed to the controller class as the expert for the information. SQL database access via SQL queries is per request from the controller class, but the responsibility of performing these queries is given to the database classes themselves, as they have the information necessary and are the only classes able to Coventry University Conor Flanagan 1

2 interact directly with the SQL database. Low Coupling means that elements are less strongly connected to other elements within the same system. Ideally, elements should only have a strong connection with two or other element or class (with the exception of a controller). A class with high coupling relies too much on other classes. My design bears this in mind and only has each class from layers other than the application logic layer coupled with only 1 other class excluding the controller (C Larman 1998). The two data classes, customer and session, do not actually store a large amount of data, they simply store individual records of the data retrieved from the database. This aligns with the Indirection pattern, where an intermediate object mediates between other components, in this case the data classes mediate information between their database classes and the controller. The current design of my functionality supports the use of the facade Gang of Four (GoF). The Facade pattern is a structural pattern that defines the relationships between classes or entities. It requires that one class act as a simplified interface with a more complex subsystem. The facade class contains members which access the subsystem on behalf of the user, hiding the methods of implementation (R Carr 2008). In the case of my design, the controller class acts as a facade, all of it s attributes being generated by other classes and it s operations only running or modifying other classes or modules. The GUI interface allows the user to control the controller class, and in-turn SQL commands will be run in the database classes (customerdb and sessiondb) using information from the data classes (customer and session). More operations can be performed using the subsystems of these classes, however for the specified functionality, only those which can be performed via the controller are required and so the required system segment is fully available for use by the user (SourceMaking 2016). Functionality Source Code: checkincontroller.py import checkingui as gui import customer import session import db import sys import re class checkincontroller : def init ( self ): """Initializes the GUI using the PyQt4 library""" app = gui. QtGui. QApplication ( sys. argv ) mainwindow = gui. QtGui. QMainWindow () self. ui = gui. Ui_CheckInWindow () self. ui. setupui ( mainwindow ) self. ui. checkinbutton. clicked. connect ( self. checkin ) self. ui. uncheckbutton. clicked. connect ( self. uncheck ) mainwindow. show () #Generating mediator classes self. customer = customer. customer () self. ssn = session. session () sys. exit ( app. exec ()) def checkin ( self ): """Function to check-in the customer by changing the SQL database""" sdb = db. sessiondb () #Generates database class that opens the database #Setting mediator variables via the GUI input self. ssn. setid ( self. ui. sessionidedit. toplaintext ()) Coventry University Conor Flanagan 2

3 self. ssn. setcustomerid ( self. ui. customeridedit. toplaintext ()) self. ssn. setcheckin ( 1 ) self. sessionid = self. ssn. getid () self. customerid = self. ssn. getcustomerid () self. checkedin = self. ssn. getcheckedin () #Calls query function, runs SQL query to modify database query = sdb. checkincustomer ( self. sessionid, self. customerid ) #Error handling if query == 2 : self. ui. typeerrorwindow ( 'TypeError', 'Incorrect type used', 'Error' ) elif query == False : self. ui. errorwindow ( 'StandardError', 'Session booking does not exist', 'Error' ) #Success message elif query == True : self. ui. successwindow () def uncheck ( self ): sdb = db. sessiondb () #Generates database class that opens the database #Setting mediator variables via the GUI input self. ssn. setid ( self. ui. sessionidedit. toplaintext ()) self. ssn. setcustomerid ( self. ui. customeridedit. toplaintext ()) self. ssn. setcheckin ( 0 ) self. sessionid = self. ssn. getid () self. customerid = self. ssn. getcustomerid () self. checkedin = self. ssn. getcheckedin () #Calls query function, runs SQL query to modify database query = sdb. uncheckcustomer ( self. sessionid, self. customerid ) if query == 2 : self. ui. typeerrorwindow ( 'TypeError', 'Incorrect type used', 'Error' ) elif query == False : self. ui. errorwindow ( 'StandardError', 'Session booking does not exist', 'Error' ) elif query == True : self. ui. successwindow () c = checkincontroller () sys. exit ( app. exec ()) checkingui.py - Automatically generated by PyQt using PyQt Designer # -*- coding: utf-8 -*- # Form implementation generated from reading ui file 'checkingui.ui' # # Created by: PyQt4 UI code generator # # WARNING! All changes made in this file will be lost! from PyQt4 import QtCore, QtGui from PyQt4. QtGui import QMessageBox try: _fromutf8 = QtCore. QString. fromutf8 except AttributeError: def _fromutf8 ( s ): return s Coventry University Conor Flanagan 3

4 try: _encoding = QtGui. QApplication. UnicodeUTF8 def _translate ( context, text, disambig ): return QtGui. QApplication. translate ( context, text, disambig, _encoding) except AttributeError: def _translate ( context, text, disambig ): return QtGui. QApplication. translate ( context, text, disambig) class Ui_CheckInWindow ( object ): def setupui ( self, CheckInWindow ): CheckInWindow. setobjectname ( _fromutf8 ( "CheckInWindow" )) CheckInWindow. resize ( 419, 246) CheckInWindow. setminimumsize ( QtCore. QSize ( 419, 246 )) CheckInWindow. setmaximumsize ( QtCore. QSize ( 419, 246 )) self. centralwidget = QtGui. QWidget ( CheckInWindow) self. centralwidget. setobjectname ( _fromutf8 ( "centralwidget" )) self. title = QtGui. QLabel ( self. centralwidget) self. title. setgeometry ( QtCore. QRect ( 10, 10, 496, 39 )) font = QtGui. QFont () font. setpointsize ( 24) self. title. setfont ( font) self. title. setobjectname ( _fromutf8 ( "title" )) self. description = QtGui. QLabel ( self. centralwidget) self. description. setgeometry ( QtCore. QRect ( 60, 40, 291, 21 )) self. description. setobjectname ( _fromutf8 ( "description" )) self. widget = QtGui. QWidget ( self. centralwidget) self. widget. setgeometry ( QtCore. QRect ( 80, 70, 261, 71 )) self. widget. setobjectname ( _fromutf8 ( "widget" )) self. gridlayout = QtGui. QGridLayout ( self. widget) self. gridlayout. setobjectname ( _fromutf8 ( "gridlayout" )) self. sessionidlabel = QtGui. QLabel ( self. widget) self. sessionidlabel. setobjectname ( _fromutf8 ( "sessionidlabel" )) self. gridlayout. addwidget ( self. sessionidlabel, 0, 0, 1, 1) self. sessionidedit = QtGui. QTextEdit ( self. widget) self. sessionidedit. setobjectname ( _fromutf8 ( "sessionidedit" )) self. gridlayout. addwidget ( self. sessionidedit, 0, 1, 1, 1) self. customeridlabel = QtGui. QLabel ( self. widget) self. customeridlabel. setobjectname ( _fromutf8 ( "customeridlabel" )) self. gridlayout. addwidget ( self. customeridlabel, 1, 0, 1, 1) self. customeridedit = QtGui. QTextEdit ( self. widget) self. customeridedit. setobjectname ( _fromutf8 ( "customeridedit" )) self. gridlayout. addwidget ( self. customeridedit, 1, 1, 1, 1) self. widget1 = QtGui. QWidget ( self. centralwidget) self. widget1. setgeometry ( QtCore. QRect ( 180, 150, 161, 61 )) self. widget1. setobjectname ( _fromutf8 ( "widget1" )) self. verticallayout = QtGui. QVBoxLayout ( self. widget1) self. verticallayout. setobjectname ( _fromutf8 ( "verticallayout" )) self. checkinbutton = QtGui. QPushButton ( self. widget1) self. checkinbutton. setobjectname ( _fromutf8 ( "checkinbutton" )) self. verticallayout. addwidget ( self. checkinbutton) self. uncheckbutton = QtGui. QPushButton ( self. widget1) self. uncheckbutton. setobjectname ( _fromutf8 ( "uncheckbutton" )) self. verticallayout. addwidget ( self. uncheckbutton) CheckInWindow. setcentralwidget ( self. centralwidget) self. statusbar = QtGui. QStatusBar ( CheckInWindow) self. statusbar. setobjectname ( _fromutf8 ( "statusbar" )) CheckInWindow. setstatusbar ( self. statusbar) self. retranslateui ( CheckInWindow) QtCore. QMetaObject. connectslotsbyname ( CheckInWindow) def typeerrorwindow ( self, etype, text, title ): window = QMessageBox () window. seticon ( QMessageBox. Critical) window. settext ( etype) window. setinformativetext ( text) Coventry University Conor Flanagan 4

5 window. setwindowtitle ( title) window. setstandardbuttons ( QMessageBox. Ok) window. exec_ () def errorwindow ( self, etype, text, title ): window = QMessageBox () window. seticon ( QMessageBox. Critical) window. settext ( etype) window. setinformativetext ( text) window. setwindowtitle ( title) window. setstandardbuttons ( QMessageBox. Ok) window. exec_ () def successwindow ( self ): window = QMessageBox () window. seticon ( QMessageBox. Information) window. settext ( 'Operation Succesful') window. setinformativetext ( 'Customer check-in status has been changed') window. setwindowtitle ( 'Success') window. setstandardbuttons ( QMessageBox. Ok) window. exec_ () def retranslateui ( self, CheckInWindow ): CheckInWindow. setwindowtitle ( _translate ( "CheckInWindow", "CheckInWindow", None )) self. title. settext ( _translate ( "CheckInWindow", "SPHERE Customer Check In", None )) self. description. settext ( _translate ( "CheckInWindow", "Enter a session ID and a customer ID to check a customer in", None )) self. sessionidlabel. settext ( _translate ( "CheckInWindow", "Enter Session ID:", None )) self. customeridlabel. settext ( _translate ( "CheckInWindow", "Enter Customer ID:", None )) self. checkinbutton. settext ( _translate ( "CheckInWindow", "Check-In", None )) self. uncheckbutton. settext ( _translate ( "CheckInWindow", "Uncheck", None )) if name == " main ": import sys app = QtGui. QApplication ( sys. argv) CheckInWindow = QtGui. QMainWindow () ui = Ui_CheckInWindow () ui. setupui ( CheckInWindow) CheckInWindow. show () sys. exit ( app. exec_ ()) customer.py class customer: """Mediator class for storing customer data""" def init ( self ): self. ID = None self. firstname = None self. lastname = None #Functions for getting attributes def getid ( self ): return self. ID def getfirstname ( self ): return self. firstname def getlastname ( self ): return self. lastname #Functions for setting attributes def setid ( self, id ): self. ID = id return self. ID Coventry University Conor Flanagan 5

6 def setfirstname ( self, firstname ): self. firstname = firstname return self. firstname def getlastname ( self, lastname ): self. lastname = lastname return self. lastname session.py class session: """Mediator class for storing session data""" def init ( self ): self. ID = None self. customerid = None self. checkedin = None #Functions for getting attributes def getid ( self ): return self. ID def getcustomerid ( self ): return self. customerid def getcheckedin ( self ): return self. checkedin #Functions for setting attributes def setid ( self, id ): self. ID = id return self. ID def setcustomerid ( self, customerid ): self. customerid = customerid return self. customerid def setcheckin ( self, checkedin ): self. checkedin = checkedin return self. checkedin db.py import pymysql import re class customerdb: """Class to access customer table in the database""" def init ( self ): self. conn = pymysql. connect ( host = 'localhost', port = 3306, user = 'rppt', passwd = '', db = 'sphere') self. c = self. conn. cursor () def hasletters ( self, inputstring ): #Checks if the input is empty return bool ( re. search ( r '^[a-za-z]+$', inputstring )) def query ( self, sql ): #Executes the specified sql command self. c. execute ( sql) self. conn. commit () self. closedb () def querydata ( self, sql ): Coventry University Conor Flanagan 6

7 #Checks if sql command returns data but does not commit it self. c. execute ( sql) return self. c. fetchall () def closedb ( self ): self. conn. close () class sessiondb: """Class to access session table in the database""" def init ( self ): self. conn = pymysql. connect ( host = 'localhost', port = 3306, user = 'root', passwd = '', db = 'sphere') self. c = self. conn. cursor () def hasletters ( self, inputstring ): #Checks if the input is empty return bool ( re. search ( r '^[a-za-z]+$', inputstring )) def query ( self, sql ): #Executes the specified sql command self. c. execute ( sql) self. conn. commit () self. closedb () def querydata ( self, sql ): #Checks if the sql command returns data but does not commit it self. c. execute ( sql) return self. c. fetchall () def checkincustomer ( self, sid, cid ): #Checks in customer to specified session, if the session table contains the combination if self. hasletters ( sid ) == True or self. hasletters ( cid ) == True: return 2 elif self. querydata ( "SELECT * FROM session WHERE (sessionid = " + str ( sid ) + " AND customerid = " + str ( cid ) + ")" )!= (): self. query ( "UPDATE session SET checked_in = 1 WHERE (sessionid = " + str ( sid ) + " AND customerid = " + str ( cid ) + ")") return True else: return False def uncheckcustomer ( self, sid, cid ): #Unchecks the customer to specified session, if the session table contains the combination if self. hasletters ( sid ) == True or self. hasletters ( cid ) == True: return 2 elif self. querydata ( "SELECT * FROM session WHERE (sessionid = " + str ( sid ) + " AND customerid = " + str ( cid ) + ")" )!= (): self. query ( "UPDATE session SET checked_in = 0 WHERE (sessionid = " + str ( sid ) + " AND customerid = " + str ( cid ) + ")") return True else: return False def closedb ( self ): self. conn. close () Coventry University Conor Flanagan 7

8 Functionality Demo Screenshots Initial GUI window Outcome of check-in pressed with correct input data Coventry University Conor Flanagan 8

9 Evidence of correct data being changed on the MySQL server Outcome of check-in pressed with invalid input data Coventry University Conor Flanagan 9

10 Outcome of check-in pressed with incorrect data type Uncheck button returns the same feedback for success, error and TypeError, simply changes the database field to a different value. Coventry University Conor Flanagan 10

11 Automated Unit Testing Automated testing was completed using the python unittest library. Completed automated testing on the methods checkincustomer and uncheckcustomer using the following test source code. import unittest import db import session import pymysql class TestFunctions ( unittest. TestCase ): def test_checkin ( self ): self. conn = pymysql. connect ( host = 'localhost', port = 3306, user = 'root', passwd = '', db = 'sphere' ) self. c = self. conn. cursor () testdb = db. sessiondb () checkedinsession = self. c. execute ( "SELECT sessionid FROM session WHERE sessionid = 1" ) self. assertequal ( testdb. checkincustomer ( 1, 1 ), True ) #Valid data self. assertequal ( testdb. checkincustomer ( 1, 2 ), False ) #Invalid data self. assertequal ( testdb. checkincustomer ( 10, 10 ), False ) #Invalid data self. assertequal ( testdb. checkincustomer ( 'text', 'text' ), 2 ) #Incorrect data type self. assertequal ( testdb. uncheckcustomer ( 1, 1 ), True ) #Valid data self. assertequal ( testdb. uncheckcustomer ( 1, 2 ), False ) #Invalid data self. assertequal ( testdb. uncheckcustomer ( 10, 10 ), False ) #Invalid data self. assertequal ( testdb. uncheckcustomer ( 'text', 'text' ), 2 ) #Incorrect data type self. conn. commit () self. c. close () def test_getters ( self ): ses = session. session () self. assertequal ( ses. getid (), ses. ID ) self. assertequal ( ses. getcustomerid (), ses. customerid ) self. assertequal ( ses. getcheckedin (), ses. checkedin ) def test_setters ( self ): ses = session. session () self. assertequal ( ses. setid ( 1 ), ses. ID ) self. assertequal ( ses. setcustomerid ( 1 ), ses. customerid ) self. assertequal ( ses. setcheckin ( 0 ), ses. checkedin ) if name == " main " : t = TestFunctions () unittest. main ( exit = False) Coventry University Conor Flanagan 11

12 Outcome of running specified test file: (If not readable due to compress, states Ran 3 tests in 0.037s OK ) Group Integrated Program Demo - Functionality Integrated with Mir Gabare s Functionality Integrated our two functionalities together using a main menu GUI. Both functionalities use and access the same database. MainMenu.py # -*- coding: utf-8 -*- # Form implementation generated from reading ui file 'C:\Users\Conor\Desktop\260CTSphere\Mir+Conor\MainMenu.ui' # # Created by: PyQt4 UI code generator # # WARNING! All changes made in this file will be lost! from PyQt4 import QtCore, QtGui import os import sys from os import system as sh try: _fromutf8 = QtCore. QString. fromutf8 except AttributeError: def _fromutf8 ( s ): return s try: _encoding = QtGui. QApplication. UnicodeUTF8 def _translate ( context, text, disambig ): return QtGui. QApplication. translate ( context, text, disambig, _encoding) except AttributeError: def _translate ( context, text, disambig ): return QtGui. QApplication. translate ( context, text, disambig) class Ui_MainWindow ( object ): def setupui ( self, MainWindow ): MainWindow. setobjectname ( _fromutf8 ( "MainWindow" )) MainWindow. resize ( 800, 600) MainWindow. setminimumsize ( QtCore. QSize ( 800, 600 )) Coventry University Conor Flanagan 12

13 MainWindow. setmaximumsize ( QtCore. QSize ( 800, 600 )) self. centralwidget = QtGui. QWidget ( MainWindow) self. centralwidget. setobjectname ( _fromutf8 ( "centralwidget" )) self. pushbutton = QtGui. QPushButton ( self. centralwidget) self. pushbutton. setgeometry ( QtCore. QRect ( 280, 160, 161, 61 )) self. pushbutton. setobjectname ( _fromutf8 ( "pushbutton" )) self. pushbutton_2 = QtGui. QPushButton ( self. centralwidget) self. pushbutton_2. setgeometry ( QtCore. QRect ( 280, 230, 161, 61 )) self. pushbutton_2. setobjectname ( _fromutf8 ( "pushbutton_2" )) self. pushbutton_3 = QtGui. QPushButton ( self. centralwidget) self. pushbutton_3. setgeometry ( QtCore. QRect ( 280, 300, 161, 61 )) self. pushbutton_3. setobjectname ( _fromutf8 ( "pushbutton_3" )) self. label = QtGui. QLabel ( self. centralwidget) self. label. setgeometry ( QtCore. QRect ( 200, 60, 321, 71 )) self. label. setminimumsize ( QtCore. QSize ( 321, 71 )) font = QtGui. QFont () font. setpointsize ( 22) self. label. setfont ( font) self. label. setobjectname ( _fromutf8 ( "label" )) MainWindow. setcentralwidget ( self. centralwidget) self. statusbar = QtGui. QStatusBar ( MainWindow) self. statusbar. setobjectname ( _fromutf8 ( "statusbar" )) self. pushbutton_2. clicked. connect ( self. removeinstructor) self. pushbutton_3. clicked. connect ( self. checkincustomers) MainWindow. setstatusbar ( self. statusbar) self. retranslateui ( MainWindow) QtCore. QMetaObject. connectslotsbyname ( MainWindow) def retranslateui ( self, MainWindow ): MainWindow. setwindowtitle ( _translate ( "MainWindow", "MainWindow", None )) self. pushbutton. settext ( _translate ( "MainWindow", "Add Instructor", None )) self. pushbutton_2. settext ( _translate ( "MainWindow", "Remove Instructor", None )) self. pushbutton_3. settext ( _translate ( "MainWindow", "Check-In Customers", None )) self. label. settext ( _translate ( "MainWindow", "SPHERE Main Menu", None )) def removeinstructor ( self ): #Integrates remove instructor functionality #import gui #import controller sh ( "python controller.py") def checkincustomers ( self ): #Integrates check-in customers functionality #import checkingui #import checkincontroller sh ( "python checkincontroller.py") if name == " main ": app = QtGui. QApplication ( sys. argv) MainWindow = QtGui. QMainWindow () ui = Ui_MainWindow () ui. setupui ( MainWindow) MainWindow. show () sys. exit ( app. exec_ ()) Coventry University Conor Flanagan 13

14 Main Menu GUI Remove Instructor button opens the RemoveInstructor GUI Coventry University Conor Flanagan 14

15 Check-In Customers button opens the CheckInCustomers GUI Check-In GUI is fully functional and still operates the program as it did prior to implementation. Here the GUI was modified to display all the text on the monitor, as the demo shown to the client (tutor) had an issue with font scaling. Also the operation of checking-in, changing a customer s checked_in field, can be reversed with the uncheck button. Coventry University Conor Flanagan 15

16 Task 2: To evaluate the management of the project evidence with a report supported by research with references in the CU Harvard referencing style in a maximum of 1,000 words Group Meeting Records Group Meetings Sphere Development Team (Conor Flanagan, Dawid Lominski, Mir Gabare, Myles ) Date Time (24 Hour System) Group Location Group Members who Attended 6 th Feb 12:00 Library DML Conor Flanagan, Dawid 10 th Feb 13:00 EC 2 nd Floor Conor Flanagan, Dawid 13 th Feb 11:30 Library DML Conor Flanagan, Dawid 17 th Feb 13:30 EC 2 nd Floor Conor Flanagan, Dawid 20 th Feb 10:00 EC 2 nd Floor Conor Flanagan, Dawid 24 th Feb 13:00 EC 2 nd Floor Conor Flanagan, Dawid 27 th Feb 10:30 Library DML Conor Flanagan, Dawid 6 th Mar 16:30 EC 2 nd Floor Conor Flanagan, Dawid 10 th Mar 09:30 Library DML Conor Flanagan, Dawid Contact Number Coventry University Conor Flanagan 16

17 13 th Mar 16:00 EC 2 nd Floor Conor Flanagan, Dawid 17 th Mar 12:30 Library DML Conor Flanagan, Dawid 20 th Mar 13:30 EC 2 nd Floor Conor Flanagan, Dawid 24 th Mar 16:00 Library DML Conor Flanagan, Dawid 27 th Mar 13:30 EC 2 nd Floor Conor Flanagan, Dawid 31 st Mar 16:30 Library DML Conor Flanagan, Dawid Coventry University Conor Flanagan 17

18 Group Planning Gantt Chart Client Feedback (from Tutor) Client (tutor) requested a way to view bookings from the check-in page. View bookings would potentially be a separate functionality and so would be implemented elsewhere, however a button linking the two would increase usability. Another request was a window saying Are you sure? when selecting Check-In to reduce the possibility of accidental data manipulation, however the addition of an Uncheck button allows the staff member to reverse the data change if they were to accidentally or unintentionally check-in a customer. A comment was also made about the GUI scaling, however the tutor was viewing the system on a smaller monitor than the standard 1920x1080 monitor which the system was developed on. It is my belief that this issue is due to how PyQt does not modify font scaling to match window GUI scale. Coventry University Conor Flanagan 18

19 Evidence of work via GitHub A sample of regular commits to github: Coventry University Conor Flanagan 19

20 Prototyping Evaluation Report The main prototyping model we decided to use was the Incremental model. This model entails that the software model is designed, implemented and tested incrementally until the system is complete. It involves several stages of development and testing before the product can be defined as finished when it meets all requirements. In the incremental model the product system can be broken down into components, termed as builds, which are each completed separately and validated upon their completion. For the Sphere system each functionality we have chosen could be delivered as a single component build, validated by the client, and then integrated into the main system (A Ghahrai 2008). Incremental prototyping greatly reduces the time between when the software is developed and when it is usable by the user. Because segments of the system are being developed in parallel, more parts of the system as a whole are available to use and review earlier in development. What's more, each build can be tested and debugged on completion, with both processes being easier without the system interference from other modules or components. Components which are considered faulty or a risk to the system can be handled or redeveloped at the development stage, preventing damage to the system as a whole. Once parts of the development team have completed development, testing, debugging and implementation of their initial component build they can help with a component currently in development, or begin a new component (ISTQB 2016). This model of prototyping isn t without it s limitations however. Components that require heavy communication or cooperation between them have to either be merged into one complex component, or require an extra stage where they are implemented together, then tested, debugged, and finally can be implemented into the main system. This can slow down completion time significantly. For systems where this is clear from the design stage, it would be better to select another prototyping method. We encountered some of these problems during our project. My functionality required that bookings for customers and sessions were already made, however no-one from the group had selected that functionality. This required me to hard code some examples into the MySQL database. However, were the system fully functional, this would not be the case, with both booking creation and a view bookings functionalities being implemented. One popular development model is Scrum, a type of agile software development in which the product is built over numerous fixed-length iterations (called sprints). The end of a sprint, called a milestone, provides a framework for implementing and shipping usable software iterations on a regular basis. The scrum model works like a cycle containing all the usual stages of development, implementation, testing, debugging (Radigan 2015). Unlike the incremental method, the scrum method is slow, and during a sprint any new developments will not be available until the next milestone. Depending on the length of each sprint and the complexity of the system, the development may be prolonged due to the constant need to halt development for the next milestone. Software components are required to be developed at similar rates which limits time until the system is usable to the time taken to make the most complex component so. More importantly, scrum is limited by how easily team members can meet and communicate, requiring development to take place with developers in ongoing interaction. Incremental prototyping allows for minimal interaction between team members, however it is still recommended to ensure consistency. Unlike incremental, scrum makes it easier for bugs and issues to be identified or predicted, and can be dealt with on the fly due to group interaction. Scrum encourages and ensures progress is made consistently throughout the length of the project (PM Expert 2009). Using the scrum method would have increased the efficiency and consistency of our development of the system, however for the way that this task was given to us, incremental seemed like a logical decision for us to develop with. Coventry University Conor Flanagan 20

21 References: Yih-Ling Hedley (2016) Architectural Design Patterns [online] Available at: 0v2%20-%20Presentation.pdf [Accessed on: 1 Apr. 2017] Craig Larman (1998) Applying UML and Patterns [online] Available at: [Accessed on: 1 Apr. 2017] Richard Carr (2008) Facade Design Pattern [online] Available at: [Accessed on: 1 Apr. 2017] SourceMaking (2016) Design Patterns: Facade [online] Available at: [Accessed on: 1 Apr. 2017] Amir Ghahrai (2008) Incremental Model [online] Available at: [Accessed on: 2 Apr ISTQB Exam Certification (2016) What is Incremental model - advantages, disadvantages and when to use it? [online] Available at: [Accessed on: 2 Apr. 2017] Dan Radigan (2015) Scrum [online] Available at: [Accessed on: 2 Apr. 2017] MyPMExpert (2009) The Advantages and Disadvantages of Agile SCRUM Software Development [online] Available at: html [Accessed on: 3 Apr. 2017] Coventry University Conor Flanagan 21