The paper “ Web Project Planning, Design and Implementation” is a forceful variant of a lab report on logic & programming. 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 an extreme programming model? The extreme Programming model is devised in this project as its principle is 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 the following aspects: Schedule slips: There might be slippage in the data storage of some of the hospitals. Project canceled: The hospitals might not be interested in taking up the service. Business Changes: The requirement might change according to the number of services provided, change in staff, etc. Staff Turnovers: The staff of the hospital might turn over and ask for the new services. Four control variables in RESTful web services software development: Cost: The cost may vary according to the number of hospitals using this service and their strength of staff, services provided, etc. Time: The time taken is variable as it may differ for various hospitals. Quality: Quality could only be assured if regular customer feedback is available.
Which is possible with XP. 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 the 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: Practice making estimatesImplement the most important requirements first Conclusion: Due to the following features of extreme programming, this is the most favorable approach for this project: The cost of Change could be reduced if the bug is caught early in the life cycle. XP is predicated on the notion that given the right set of practices, the cost curve can be flattenedSimple Design, Automated Tests, and Refactoring. Rapid FeedbackIncremental ChangeEmbracing ChangeQuality Work