COMPUTER SCIENCE 260CT SOFTWARE ENGINEERING

Transcription

1 COMPUTER SCIENCE 260CT SOFTWARE ENGINEERING Module Leader: Yih Ling AJR BOOKING SYSTEM CREATED A SKI BOOKING SYSTEM USING C# ACCORDING TO THE CLIENTS SPECIFICATION User: Jubad Miah Miahj5@uni.coventry.ac.uk Student ID:

2 Individual Report 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 Introduction The project is based on a given case study, the Sphere Booking and Check-in (SBC) System, this project involves a group of 4 who came up with a set of key functionalities to create an online or stand alone system according to client specifications. This report includes computer aided software engineering (CASE screenshots) to produce UML class diagrams. Also Use Case diagrams based on chosen functionality then make the system. Design Specification Use case Description Name of use case: Booking in Task Pre-Conditions: The receptionist selects booking and checks the customer if registered or not Post-Conditions: The session is booked for the customer Purpose: To book a session allocated Description: To make a session booking from the system and enters a requested slot for the customer and makes a session if the slot is free or an available slot is found Main Success Scenario: 1. The customer phones in or comes in person 2. The slope operator selects booking 3. The slope operator asks for customer details 4. The system checks for availability requested by customer 5. The system checks whether the requested slot is free based on information given by the customer. 6. System identifies requested availability then informs the receptionist of the booking results. 7. The slope operator selects the slot requested from the screen 8. The customer may wish to continue with the booking process 9. If the customer already registered then print out confirmation and the customer the details 10. If customer not registered then redirect to registration screen. Alternative: 5.1 A possible slot is not available The System informs the receptionist by displaying a message with a possible slot is not available. Coventry University Jubad Miah 1

3 Use Case Diagram [diagram 1] Use Case Diagram based on the booking in functionality, shows the different tasks taken place by different actors and how they are communicating. Benefit of this so that you have an idea on how the functionality will work. The final class diagram (produced in a CASE tool) for your own functionality only [Diagram 2] The above diagram1 is the four-layered model, this is to show how booking functionality works, which is a step by step process. layers building on top of each other to essentially to build a product. The diagram is a design phase of the product specification. Basically, it s an algorithmic way, Step by step, so it s logical that it s the Coventry University Jubad Miah 2

4 process to develop a software. There are many advantages by creating this model as it will guide you through the software development cycle, it s a way of visualising how to carry out the task, once the layered model is made, the developer can think of how to do it such as looking for the correct tools (tools are to create the system). The four-layered model of how booking functionality works, User interface layer is the boundary class where slope operator got the full control. Then booking controller falls under control class where attributes customer and slope operator does the controlling, this layer known as Application (Business) Logic Layer where the implementation of the core functionality of the system take place and encapsulates the relevant business logic. Domain Data Layer is the entity class where customer information and booking information are within the boundaries of the system and it can be used to access other networked systems also this type of layer can expose generic interfaces where components in the business layer can consume. Data Persistence Layer (SBC repo) is the database built within the system and are used to store relevant data sources. The advantages of using this method is that it allows replacement of entire layers if the interface is maintained, redundant facilities for example authentication can be provided in each layer to increase dependability of the system. The disadvantages would be the performance where multiple levels of interpretation of service request processed at each layer. Repository (SBC repo) this the core part of the system as it manages the central repository so that it is accessible to the all the system components, components are only linked through repository as it is not able to interact directly. The advantage of this is that components can be independent, as changes made by one component can be used to circulated to all the components. The disadvantage would be that the repository may fail which will affect the entire system. Necessary design details based on the GRASP use case controller pattern. Coventry University Jubad Miah 3

5 [diagram 3] The GRASP use case controller pattern represents one use case and controls the functionality in carrying out the use case. Diagram 3 describes how use controller carried out. In this case, the slopeoperatorui is the user interface on the booking in functionality which interacts with booking in customer(bookcustomer) the user can view customer (ViewCustomer) and payment controller which got the payment details. This model based on three layered model which are User Interface, Application Logic and Data Domain Layer. Booking controller is the main booking form and slope operator UI got the options to control booking, view and pay controller. When the slope operator enters details of the customer, it will give user to move onto next part of the controller such as PayController which is then stored in to next domain data layer, it holds the necessary data for the data sets, BookingController, ViewController, PayController must match with the domain data layer of the customer in order to store. GRASP use controller is an efficient way of showing the methods of different booking controllers in the system and how each controller communicates with the rest to make the booking functionality work. I have implemented this method in my controller class (booking controller), it enabled the controller to create objects or instances without the need of direct access to instantiate. At least ONE Gang of Four (GoF) pattern of your choice applied to the design Coventry University Jubad Miah 4

6 [diagram 4] Gang of Four is a design pattern, general reusable solution to commonly occurring problem within a given context in software design. Basically, this isn t the final pattern that can be transformed into code. Factory method defines the interface for creating an object which lets subclass decide which class to instantiate, way of letting factory method defer instantiation to subclasses. Singleton pattern was used, this is basically a design pattern that limits the use of a class to one object, this is helpful as you can manage across the system. Singleton GoF pattern is broadly used, it works by providing global point of access. This pattern is just to show how the instructor can be selected in booking form, it s a way of handling the data types using the factory method. This is an external implementation to show the user if instructor required or not. Commented source code for your own functionality only- Booking In Bookingform.cs 1. using System; 2. using System.Collections.Generic; 3. using System.ComponentModel; 4. using System.Data; 5. using System.Drawing; 6. using System.Linq; 7. using System.Text; 8. using System.Threading.Tasks; 9. using System.Windows.Forms; 10. using System.Configuration; 11. using System.Data.SqlClient; namespace Group_AJR SBC_Booking_System.Booking Coventry University Jubad Miah 5

7 14. { 15. public partial class Bookingform : Form 16. { 17. int memtype; 18. bool isreg = false; //set to false will change if user is in the system. 19. SqlConnection con; //connection 20. //string connectionstring; public Bookingform() 23. { 24. InitializeComponent(); 25. //connectionstring = connectionstring = ConfigurationManager.ConnectionStrings[ "@"Data Source = (LocalDB)\MSSQLLocalDB; AttachDBFilename = DataDirectory \SBCDatabaseV2. mdf; Integrated Security = True; Connect Timeout = 30""].ConnectionString; 26. } private void checkid_click(object sender, EventArgs e) 29. { 30. con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFilename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 31. con.open(); 32. SqlCommand checkid = new SqlCommand(); 33. checkid.commandtext = "select * from [CustomerTable]"; 34. checkid.connection = con; SqlDataReader rd = checkid.executereader(); while (rd.read()) 39. { 40. memcheck.text = "..."; 41. if (rd[0].tostring() == idbox.text) //the zero here is calling to the id co l 42. { //here we are saying that if rd var is == to the value user input is a ma tch then isreg before true. 43. isreg = true; 44. //we then print it out to the label. 45. } 46. if (isreg == true) 47. { 48. if (rd[6].tostring() == "0") 49. { 50. memcheck.text = "Member: 20"; 51. memtype = 2; } 54. else if (rd[6].tostring() == "1") 55. { 56. memcheck.text = "Premium Member: 15"; 57. memtype = 1; } 60. else 61. { 62. memcheck.text = "Non-Member: 25"; 63. memtype = 3; } 66. } 67. //code to ask for the correct price from the user so no mistakes are made 68. } 69. if (isreg == true) 70. { 71. cusidbox.text = idbox.text; 72. idlabel.text = "Customer is registerd"; 73. } 74. else 75. { 76. idlabel.text = "Customer is not registered"; Coventry University Jubad Miah 6

8 77. } isreg = false; 81. con.close(); con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFilename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 84. SqlDataAdapter checkup = new SqlDataAdapter("SELECT * FROM [CustomerTable] WHER E CustomerId ='" + idbox.text + "'", con); //this will get all the data 85. DataTable sd = new DataTable(); checkup.fill(sd); 88. datagridview2.datasource = sd; 89. } private void check _click(object sender, EventArgs e) 92. { 93. con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFilename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 94. con.open(); 95. SqlCommand check = new SqlCommand(); 96. check .commandtext = "select * from [CustomerTable]"; 97. check .connection = con; SqlDataReader rd = check .executereader(); string pattern ]+)((\.(\w){2,3})+)$"; //check for invalid inputs 102. RegexStringValidator myregexvalidator = new RegexStringValidator(pattern ); try 105. { 106. myregexvalidator.validate( box.text); //checking what has been t yped and if it matches the pattern } 109. catch (Exception) 110. { 111. MessageBox.Show(" is invalid"); } while (rd.read()) 116. { 117. if (rd[3].tostring() == box.text) //the 3 here is calling to th e column 118. { //here we are saying that if rd var is == to the value user input is a match then isreg before true isreg = true; 120. //now we print it out to the label } 122. if (isreg == true) 123. { 124. if (rd[6].tostring() == "0") 125. { 126. memcheck.text = "Member: 20"; 127. memtype = 2; 128. } 129. else if (rd[6].tostring() == "1") 130. { 131. memcheck.text = "Premium Member: 15"; 132. memtype = 1; } 135. else 136. { Coventry University Jubad Miah 7

9 137. memcheck.text = "Non-Member: 25"; 138. memtype = 3; } 141. } 142. //code to ask for the correct price from the user so there are no mi stakes made from the user } 145. if (isreg == true) 146. { label.text = "Customer is registerd"; 148. } 149. else 150. { label.text = "Customer is not registered"; 152. } //isreg = false; 155. con.close(); 156. con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFil ename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 157. SqlDataAdapter checkup = new SqlDataAdapter("SELECT * FROM [CustomerTabl e] WHERE ='" + box.text + "'", con); //this will get all the data where ma tches 158. DataTable sd = new DataTable(); checkup.fill(sd); 161. datagridview2.datasource = sd; 162. con.close(); } private void Bookingform_Load(object sender, EventArgs e) 169. { } private void search_click(object sender, EventArgs e) 175. { 176. con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFil ename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 177. SqlDataAdapter sdf = new SqlDataAdapter("SELECT * FROM [Session] WHERE d ate ='" + datetimepicker1.value.tolongdatestring() + "' AND limit < 30", con); 178. DataTable sd = new DataTable(); //datagridviewer will be filled with dat a of sessions available on the day which has less than 30 people booked onit sdf.fill(sd); 181. datagridview1.datasource = sd; 182. con.close(); con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFil ename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); 185. SqlDataAdapter staffcheck = new SqlDataAdapter("SELECT * FROM [staffsche dule] WHERE date ='" + datetimepicker1.value.tolongdatestring() + "' AND booked = 0", con) ; //this will get all the data where matches 186. DataTable staffdata = new DataTable(); //datagridviewer will be filled w ith with staff members who are not booked on the day the customer wants one staffcheck.fill(staffdata); 189. datagridview3.datasource = staffdata; 190. con.close(); 191. } private void Submit_Click(object sender, EventArgs e) Coventry University Jubad Miah 8

10 194. { 195. //factory booking = new factory(int.parse(cusidbox.text.tostring()), int.parse(sessionbox.text.tostring()), int.parse(staffschbox.text.tostring()), Convert.ToDateT ime(datetimepicker1.text), memtype); 196. // booking.factoryset(); con = new SqlConnection(@"Data Source=(LocalDB)\MSSQLLocalDB;AttachDBFil ename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Connect Timeout=30"); //cr eate a new sql connection if (cusidbox.text == String.Empty 201. sessionbox.text == String.Empty datetimepicker1.text == Strin g.empty) //this code here will check if the all the values have been entered 202. { 203. MessageBox.Show("Error, missing values", "Please Complete Form", Mes sageboxbuttons.ok, MessageBoxIcon.Error); //show the error if they are not } else 207. { 208. try 209. { con.open(); // open sql connection 214. SqlCommand limit_increment = new SqlCommand("UPDATE Session set limit = limit + 1 WHERE id ='" + this.sessionbox.text + "';", con); 215. int incremnt_check = limit_increment.executenonquery(); 216. if (incremnt_check!= 1) 217. { 218. MessageBox.Show("Failed to increment Session limit"); //simp le error checks } 221. con.close(); //this will incrment the limit com in session tabl es everytime user enters con.open(); 224. SqlCommand cmd2 = new SqlCommand("INSERT INTO Bookingtable (staf fschedule, customerid, cost, sessionid) @sessio nid)", con); 225. cmd2.parameters.addwithvalue("@staffschedule", staffschbox.text) ; 226. cmd2.parameters.addwithvalue("@customerid", cusidbox.text); 227. cmd2.parameters.addwithvalue("@cost", typepayment.text); 228. cmd2.parameters.addwithvalue("@sessionid", sessionbox.text); 229. int b = cmd2.executenonquery(); if (b == 1) 232. { 233. MessageBox.Show("Booking has been made: "); //simple error c hecks } 236. else 237. { 238. MessageBox.Show("Booking couldn't be made, Please try again" ); 239. } } catch (Exception ex) 244. { 245. MessageBox.Show("Unexpected error:" + ex.message); 246. } 247. Coventry University Jubad Miah 9

11 248. } } private void button1_click(object sender, EventArgs e) 253. { 254. this.close(); 255. MainUIform main = new MainUIform(); 256. main.show(); 257. } int a, b, c; private void datagridview2_cellcontentclick(object sender, DataGridViewCellE ventargs e) 264. { 265. a = e.rowindex; //needs to know the row that has been clicked 266. DataGridViewRow row = datagridview2.rows[a]; 267. cusidbox.text = row.cells[0].value.tostring(); 268. } private void label4_click(object sender, EventArgs e) 271. { } private void AvLabel_Click(object sender, EventArgs e) 276. { } private void label1_click(object sender, EventArgs e) 281. { } private void datagridview1_cellcontentclick(object sender, DataGridViewCellE ventargs e) 286. { 287. b = e.rowindex; //needs to know the row that has been clicked 288. DataGridViewRow row = datagridview1.rows[b]; 289. sessionbox.text = row.cells[0].value.tostring(); 290. } private void datagridview3_cellcontentclick(object sender, DataGridViewCellE ventargs e) 293. { 294. c = e.rowindex; //needs to know the row that has been clicked 295. DataGridViewRow row = datagridview3.rows[c]; 296. staffschbox.text = row.cells[0].value.tostring(); 297. } } 300. } Controller.cs 1. using System; 2. using System.Windows.Forms; 3. using System.Data.SqlClient; namespace Group_AJR SBC_Booking_System 6. { Coventry University Jubad Miah 10

12 7. class Controller 8. { 9. private TextBox textbox1, textbox2, textbox3, textbox4, textbox5; 10. public Controller(TextBox textbox1, textbox2, textbox3, textbox4, textbox5, CheckBo x checkbox6) 11. { Id = textbox1; 14. customerid = textbox2; 15. cost = textbox3; 16. sessionid = textbox4; 17. staffschedled = textbox5; } public Controller() 23. { } public bool Update() 28. { 29. Bookingtable type = Factory.getType(b.Checked); 30. bool gettype = type.type(b.checked); Booking = new booking(int.parse(id.text.tostring()), int.parse(customerid.text. ToString()), int.parse(cost.text.tostring()), int.parse(sessionid.text.tostring()), int.par se(staffschedled.text.tostring()); 33. bool i = booking.update(); 34. return i; 35. } public bool getbooking() 38. { 39. Booking booking = new Booking(); 40. bool i = Booking.getBooking(int.Parse(CustomerID.Text.ToString())); if (i) 43. { 44. Id.Text = Booking.firstname.ToString(); 45. customerid.text = Booking.lastname.ToString(); 46. cost.text = Booking. .ToString(); 47. sessionid.text = Booking.Phonenumber.ToString(); 48. staffschedled.text = Booking.address.ToString(); 49. } 50. return i; 51. } public bool Save() 54. { 55. Bookingtable type = Factory.getType(b.Checked); 56. bool gettype = type.type(b.checked); BookingIn = new Booking(int.Parse(Id.Text.ToString()), int.parse(customerid.tex t.tostring()), int.parse(cost.text.tostring()), int.parse(sessionid.text.tostring()), int.p arse(staffschedled.text.tostring()); 59. bool i = BookingIn.Update(); 60. return i; 61. } public bool manualtest() 64. { 65. Console.WriteLine("BEGINING TEST"); 66. using (SqlConnection Connection = new SqlConnection(@"Data Source=(LocalDB)\MSS QLLocalDB;AttachDBFilename= DataDirectory \SBCDatabaseV2.mdf;Integrated Security=True;Conne ct Timeout=30")) 67. { Coventry University Jubad Miah 11

13 68. try 69. { 70. Connection.Open(); 71. SqlCommand cmd = new SqlCommand("UPDATE Bookingtable SET Id=3 AND custo merid=3, cost= 10, sessionid=3, staffscheduled=2",connection); 72. int i = cmd.executenonquery(); if (i > 0) 75. { 76. Console.WriteLine(" UPDATE PASS "); 77. cmd = new SqlCommand("SELECT Count(*) FROM Bookingtable WHERE Id=3 AND customerid=3, cost= 10, sessionid=3, staffscheduled=2", Connection); 78. i = (int)cmd.executescalar(); if (i > 0) 81. { 82. Console.WriteLine("--VERIFY PASS-"); 83. Console.WriteLine("--ALL PASS--");//controller passsed 84. Connection.Close(); 85. return true; 86. } 87. else 88. { 89. Console.WriteLine("--VERIFY FAIL-- ");// to show verification failure. 90. Connection.Close(); 91. return false; 92. } 93. } 94. else 95. { 96. Console.WriteLine("--UPDATE FAIL-- ");//if update dont work then show error update fail. 97. Connection.Close(); 98. return false; 99. } 100. } 101. catch (Exception ex) 102. { 103. Connection.Close(); 104. MessageBox.Show(ex.ToString()); 105. Console.WriteLine("--UNKNOWN FAIL--"); 106. return false;//if it fails the close connection with an error 107. } 108. } 109. } 110. } 111. } goffactory.cs 1. using System; namespace Group_AJR SBC_Booking_System 4. { 5. interface InstructorType 6. { 7. bool type(bool i); 8. } class Yes : InstructorType 11. { 12. public bool type(bool i) 13. { 14. return true; 15. } Coventry University Jubad Miah 12

14 16. } class No : InstructorType 19. { 20. public bool type(bool i) 21. { 22. return false; 23. } 24. } class Factory 27. { 28. static public InstructorType gettype(bool i) 29. { 30. InstructorType type = null; switch (i) 33. { 34. case false: 35. type = new Yes(); 36. break; 37. case true: 38. type = new No(); 39. break; 40. } 41. return type; 42. } 43. } 44. } Automated unit testing test script Tool used Microsoft Visual Studio Self automated test 1. using System; 2. using Microsoft.VisualStudio.TestTools.UnitTesting; namespace bookingunittest 5. { 6. [TestClass] 7. public class UnitTest1 8. { [TestMethod] 11. public void CodedUIBookingTest() 12. { 13. //Perform automated test 14. this.uimap.recordedmethodupdate(); string rtxt = UIMap.UIUpdateBookingWindow.UICustomerIDWindow.label1.Text; 17. string rtxt = UIMap.UIUpdateBookingWindow.UICustomer IDWindow.label2.Text; this.uimap.recordedmethodsubmit(); //Validation that the data is there 22. Verify verify = new Verify(); 23. bool i = verify.getsessionavailability(aa, 32aa, *?/@); 24. if (i == false) 25. { 26. Assert.Fail(); 27. } 28. } 29. Coventry University Jubad Miah 13

15 30. // <summary> 31. //Gets or sets the test context which provides 32. //information about and functionality for the current test run. 33. //</summary> 34. public TestContext TestContext 35. { 36. get 37. { 38. return testcontextinstance; 39. } 40. set 41. { 42. testcontextinstance = value; 43. } 44. } 45. private TestContext testcontextinstance; public UIMap UIMap 48. { 49. get 50. { 51. if ((this.map == null)) 52. { 53. this.map = new UIMap(); 54. } return this.map; 57. } 58. } private UIMap map; 61. } 62. } Databases built in C# Coventry University Jubad Miah 14

16 Report-screenshot Screen shot demo of at least TWO prototypes for the group integrated program Login.form We kept the login form as it is, this represents prototype one and two. Coventry University Jubad Miah 15

17 MainForm.form main user interface with 3 different functionalities, this is prototype 1 and 2. Registration.form Prototype 1 Coventry University Jubad Miah 16

18 Prototype 2 Booking.form (my functionality) Prototype 1 This was the first prototype that i made then showed the client for any feedbacks and this is what I got from the lecturer(client) Error handling bugs Validation for customer ID and address Hide datagridview if possible to make the interface look good Coventry University Jubad Miah 17

19 Check with 4 layered model to see if all components matches Final feedback from lecturer programs seems to be working fine Prototype 2 In the prototype, I have improved the interface to allow the user to interact as efficiently as possible, validated customer ID and customer accordingly for example should check I couldn t manage to hide the data grid view but managed to make it more user friendly. My four-layered model seems to correct and in line with the functionality created. The lecturer(client) approved this final booking form design. (working booking form) below is an example where invalid address was input. For future improvements, I can make search for customers more user friendly so users can easily access the data with few click of a button. Also make it online system in real time so customers can check online for availability. Coventry University Jubad Miah 18

20 Checkin.form Harvard Reference product?, How. "How To Describe The Architecture Of A Software Product?". Softwareengineering.stackexchange.com. N.p., Web. 4 Apr "Chapter 5: Layered Application Guidelines". Msdn.microsoft.com. N.p., Web. 5 Apr Coventry University Jubad Miah 19

21 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 Evidence of how the prototyping method is applied to the project, which should include: Group meeting records (as a group) Week 1 Group Introductions and agreeing on the software to use, and assigning the functionalities to the group members and exchanging contact information. Week 2 We have agreed on using the C# in visual studio. Jubad has been assigned booking, Asis has taken the responsibility to create login screen and registration forms. Rakshak has been assigned the check in Form and Harvey has been assigned Manager User interface. Designing use case diagrams for the project We also started working on producing the use case diagrams and use case description for our individual functionality. We are also researching about how to use C# language. We have been introduced to the layered models, therefore, we have started working on understanding how to come up with a layered model for our own functionality. Week 3 We have started learning about grasp patterns where we had to learn about different types of controllers and how they function. Made a start on programming our functionalities in c#. We ve also started working on designing the database for the system and the front end look of the system. Week4 and Week5 Week 6 Still continuing to work on the creating the system, since C# is a new language to all four of us, we are starting from the basics, and working our way up. We have completed use case diagrams and use case descriptions. At this point we have finished creating the database and tables. We are further researching on the connectivity of the database to the forms created. This week we met up for a group meeting outside of lessons to complete the 4 layered model for one of the system functionality. This week we are learning about gang of four design patterns. We have managed to complete system analysis and how the user interface of the system should look. Some of the issues we had are going forward with database connectivity with forms. Therefore, we have decided to use different external methods to create database and connecting it by importing it. Coventry University Jubad Miah 20

22 Rakshak has started working on the SQLite studio, whereas Jubad was trying to use Microsoft SQL server software to create database. On the other hand, the Asis and harvinder have been working on getting their layered models done as well as their functionalities. Asis has finished his login screen Week 7 and 8 Week 9 Week 10 Week 11 In this week we have managed to design all the forms should look, but the booking and check in systems are quite hard to implement on code, as they are quite complex. We have also been attending some of the support sessions to get more help on the layered models, Rakshak, jubad and Asis have managed to complete the finalised version of their layered models. Whereas, harvinder is still yet to complete his model. We have also started preparing for the in class test. Asis has finished his 4 layered model and we have all started working on the user case controller pattern. Rakshak and jubad and harvinder are still working on their functionalities. Asis has managed to figure out how to update a table inside a database, through windows form. Booking functionality has also been partly done, and in order to do checking in functionality, booking functionality needs to be fully completed. Harvinder is still working on the four layered model and his Manager Tools functionality. In this week we have completed the booking and registration completely and we are working on checking in functionality. Asis and jubad have received feedback on their functionalities and have started making the appropriate changes based on the feedback received. This week we have created GitHub accounts and started making commits with all the work we have produced. Rakshak is working his checking in functionality. On the other hand we have been working on implementing the gang of four patterns, which we have been struggling for a while. We have also been writing our evaluation reports on our system and started to put all the work we did into our portfolios. We have also started working on the unit testing and assignment tasks. The groups is still awaiting on Harvinder s layered model and functionality This week Rakshak has completed his checking in system, and has received feedback. He has completed his feedback functionality and has started working on this assignment tasks. Whilst Rakshak has been working on his feedback, Asis and jubad have been on completing their program based on the feedback given and completing the assignment submission. Harvinder is still yet to finish his layered model, use case diagram and functionality. Coventry University Jubad Miah 21

23 Project planning (e.g. Gantt Chart) (as a group) we created this Gantt chart to keep track of the time and workload, this is useful as the group knows what to work on how long they should take to complete the task. Summary of feedback from the tutor (acting as the client) (as an individual) On the 27 th of March 2017, I have received some feedbacks from the tutor(client) which was very useful and understandable, the feedbacks that I received changed my form to better and more efficient looking booking functionality. The tutor(client) specification was met as the functionality working to an appropriate level. Overall the entire system the group designed and produced is working without any errors. By showing the client we have prevented many errors and fixed many due to clients feedbacks. Our GitHub Account and all the necessary code and commits uploaded for future use, evidence of group uploading regular commits. Coventry University Jubad Miah 22

24 Commits Github commits above. Coventry University Jubad Miah 23

25 Evaluation of the prototyping method (in form of a formal report and the Coventry University Harvard style in a maximum of 1,000 words) for the following areas only: (as an individual) Software development methodology is basically a framework of activities and actions suitable to build a project, the main phases of SDM is communication, planning, modelling, construction and deployment. All these phases are undertaken to complete a system accurately as possible. I have used incremental prototyping method, prototyping method is a system development method (SDM) where prototype is built, tested and then carried on working until an adequate prototype is reached to develop the complete system. The prototyping method works best in scenarios (as I was given sphere skiing scenario at the start of project start date) because the requirements are known as an advantage, this is useful for me as I can think about the system tools and design also visualise to come up with a system language. This is an iterative process which takes place between the myself and the client. The steps that that I have carried out to create the system using prototyping method are to define requirements as much detail as possible, carry out user interviews to represent different part of the project task, I have created initial design to build the new system. First prototype I created (booking in system) to get feedback from the clients as this is very important part of the process as this narrows down the appearances of the final system. The first prototype must be evaluated correctly by the user to further scale down any weaknesses and perhaps add or remove errors or validations. All the feedback received from the client was useful as it gave me second thought as to what needs changing and what needs adding to construct second prototype. I have modified the first prototype based on the feedbacks given by the tutor (client) and then came up second prototype which was then evaluated in the same manner as the first prototype, got feedback from the tutor (client) and there wasn t much to change or add as the system was working as it should. The previous steps are iterated as many times as necessary till the final system is constructed to client s satisfaction. By using this method, it helped me to create my Booking functionality as well as members of the groups functionalities, the Booking function that I have created using this method is known as completed functionality as I have achieved the client s requirements. The advantage of using this prototyping process model is to reduce time and cost, basically it can improve the quality of the requirements and specifications provided as if I was to build a system then change it, the earlier the detection of what the client wants can result in rapid and less expensive software system. Another advantage is that prototyping requires tutor (client) involvement where I am to get feedbacks along each prototype that I can come up with to complete feedback and better specifications, having regular communications with the client increases better result in the final product as it is more likely to satisfy the clients desire for look, feel and performance. The disadvantage of using this type of prototype model is that there is insufficient analysis which can result in poorly engineered final design system as the prototype is limited in functionality. Another disadvantage is that there could be confusion of prototype and finished system as user may delete final prototype system accidently to construct prototype 2. However, the expense of implementing prototype from scratch as in Coventry University Jubad Miah 24

26 looking for the right development team to focus on the task will cost as many companies have their own methodologies and changing that would cost. The problems that I have come across was linking creating SQL database within visual studio where I couldn t link the database connection so I decided to use Microsoft SQL server management which worked fine but then when I was creating more tables within the database, my booking function stopped working and came with so many errors so with so much research I have decided to use in built visual studio database to link different tables to go with my functionality, the main database was linked and working as it should. Comparison of the Prototyping Method applied and the Agile Scrum Method. I have researched Agile Scrum method alongside the prototyping method that I have used in the project, agile scrum is based on iterative and incremental method where specifications and solutions advanced through relationship between cross functional teams. Agile methods are generally a disciplined project management that allows regular inspection and adaptation, usually divided into small iterations which are called Sprints. From my research this is a better methodology due to its continuous planning, testing, integration, risk evaluation and control on the progress of the project. Agile is flexible methodology, very accommodative to changes, its rapid delivery helps to satisfy customers/clients. The key difference between the two methodologies are as follows; Prototype Agile Scrum The product specifications are met when client s requirement is included Project regular inspection and backlogs including minimum functionality and requirements on every sprint The product gets updated but definition The project gets updated in every Sprint. This method involves a lot of reverse engineering as going back and forth because of raised problems In this method, incremental and changes to the project are based on user which allows access to add updates to next project backlog. To conclude prototype method was a good methodology for our group project as the client is our tutor and we are more likely to get feedbacks whenever possible on each prototype constructed, however in the future I would use Agile as it is more professional as well as less stressful. Coventry University Jubad Miah 25

27 Harvard Reference "Advantages & Disadvantage Of Prototyping Process Model". IOTAP Inc. N.p., Web. 4 Apr "CS 410/530 - Software Engineering Class Notes". Cs.ccsu.edu. N.p., Web. 4 Apr "An Empirical Framework For Learning (Not A Methodology)". Scrummethodology.com. N.p., Web. 5 Apr Coventry University Jubad Miah 26