Web Project Planning, Design and Implementation - Lab Report Example

Recommended Software Development Methodology - Extreme Programming Brief description Extreme Programming (XP) is a rather recent development of the incremental model that puts the client in the driver’s seat. Each feature or feature set of the final product envisioned by the client and the development team is individually scoped for cost and development time. The client then selects features that will be included in the next build (again, a build is an operational system at some level of functionally) based on a cost-benefit analysis. The major advantage of this approach for small to medium-size systems is that it works when the client’s requirements are vague or continually change. This development model is distinguished by its flexibility because it can work in the face of a high degree of specification ambiguity on the user’s part. As shown in Figure below, this model is akin to repeated rapid prototyping, in which the goal is to get certain functionality in place for critical business reasons by a certain time and at a known cost. Extreme Programming model Why extreme programming model? Extreme Programming model is devised I this project as its principle are best suited for the Risk mitigation of small and medium sized projects. XP is a methodology that addresses risk at all levels of the development process. Risk is the main problem of software development, it may involve following aspects: 1. Schedule slips : There might be slippage in the data storage of some of the hospitals. 1. Project canceled: The hospitals might not be interested in taking up the service. 1. Business Changes: The requirement might change according to the number of services provided, change in staff, etc. 1. Staff Turnovers: The staff of hospital might turn over and ask for the new services. Four control variables in RESTful web services software development: 1. Cost: The cost may vary according to the number of hospitals using this service and there strength of staff, services provided etc. 1. Time: The time taken is variable as it may differ for various hospitals. 1. Quality: Quality could only be assured if regular costumer feed back is available. Which is possible with xp. 1. Scope: The scope of various functionalities provided by the project is different so it is well taken care in this approach. The values of all four variables need to be visible: If the client (in our case the hospital facility) can see all four variables they can consciously choose which variables to control. If they do not like the resulting value of the fourth variable, they can choose to change the inputs or choose to control a different set of three variables. By adjusting project scope based on the values of the other three, you increase your chance of success. This perspective is backed by XP practices, which are: 1. Practice making estimates 1. Implement most important requirements first Conclusion: Due to the following features of extreme programming this is the most favorable approach for this project: 1. Cost of Change could be reduced if the bug is caught early in the life cycle. 1. XP is predicated on the notion that given the right set of practices, the cost curve can be flattened 1. Simple Design, Automated Tests and Refactoring. 1. Rapid Feedback 1. Incremental Change 1. Embracing Change 1. Quality Work Functional specification: Ref # Function Category Attribute Details/Constraints Return type Error/Exception handler 1 login Evident Username, password The login functionality provides the user to login as doctor, patient or hospital administrator. Void If the entries do not match database fields the prompt shows the “Login failed” message. 2 Multiple administration security levels. Evident Security contexts The system will support three levels of administrative security: Doctors will be able to add and delete hash code and chose the right kind of service. Patients will be able to retrieve the available slots and book the slots for the available hash code. Hospitals will be able to add a slot for a given service at a given time and date, remove a slot that has not yet been booked and retrieve a list of booked slots between any two specified dates. Shows a prompt if the services not assigned to the user are accessed by it. 3 Hash code generation Evident doctor's identity, the patient's identity, the date of their consultation and the code number for the id of the service the patient requires A unique hash code is generated according to the given attributes. The return type is a string. Gives the message box if the hash code is already generated. 4 Hash code approval Evident Hash code The hash code is approved on the basis of uniqueness. The return type is true or false (boolean). Gives the message box if the hash code is already generated. 5 Hash code matcher Hidden Hash code It checks whether the hash code is already generated or not. The return type boolean (true or false). 6 Service code generator Evident Patient id It generates the service code for a given patient. It returns the String. Gives the prompt for successful generation and an error message if not. 7 Slot generator Hidden Service Requested It generates the slot based on the location and service requested. It returns the string. 8 Slot extractor Evident Hash code Returns the available slot based on the hash code. It returns the list of string. Gives the list of slots available for the given hash code. Ref # Function Category Attribute Details/Constraints Return type Error/Exception handler 9 Book slot Evident Slot Books the slot which is selected. It returns Boolean (true or false) for a given slot. Gives the prompt whether the slot is booked or not. 10 Slot updater Hidden Booked Slot The slot which is selected is deleted from the view of available slot. Return type is void. 11 Slot adder Evident Slot It is used by the hospital to add the slot for the given time. It returns the list of string. Gives the prompt whether the slot is added successfully or not. 12 Slot remover Evident Slot list It removes the slot which is not yet been booked. It returns the list of string. Gives the prompt whether the slot is removed successfully or not. 13 Slot retriever Evident Slot list It retrieves the list of It returns the list of string for a specified date. Returns the list of slots available for a given time period. 14 Log out Evident Logout function exists from the current session. It returns back to the login page. Estimation of efforts and duration: Ref # Function Size (KLOC) Cost Driver Values Values of constant Effort = A (Size)^P1 Duration=B (Effort) ^P2 1 Hash code generation .032 RCPX 1 PDIF .85 PERS .75 PREX 1 FCIL 1.13 SCED 1 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.468384 1.557143627 2 Service code generator .072 RCPX .85 PDIF 1 PERS .75 PREX 1.13 FCIL 1 SCED 1 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 1.046304 2.030098442 3 Slot extractor .032 RCPX 1 PDIF .85 PERS .75 PREX 1 FCIL 1.13 SCED .62 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.464352 1.552707359 4 Book slot .019 RCPX 1 PDIF .85 PERS .75 PREX 1 FCIL 1.13 SCED 1 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.278901 1.312286071 5 Slot adder .023 RCPX 1 PDIF .85 PERS 1 PREX 1 FCIL 1.13 SCED 1 TEAM 1 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.335685 1.395042807 6 Slot remover .067 RCPX 1 PDIF .75 PERS .85 PREX 1.19 FCIL 1.13 SCED 1 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.976458 1.984338109 7 Slot retriever .043 RCPX 1 PDIF .75 PERS .75 PREX 1 FCIL 1.13 SCED 1 TEAM 1.20 PEFF 1 A 2.1 B 2.0 P1 1.00 P2 .33 0.62307 1.710909955 Conclusion: Total Effort = 8.69568 Total duration = 11.54252637 Read More