Title: Agile Development19th April 2011Implementation of Assignment TimelineThe first section will show the implementation of the breakdown of work for the successful completion of the assignment. This is important in a sense that it will enable the people involved to be able to fully implement the assigned timeline. This is done by using the agile development and time boxingApril 13th 2011The planning of the agile developmentTime boxingPrototypesApril 14th 2011Prototype usabilityDemonstration of the proposed systemDemonstration of user interaction April 15th 2011Architecture in development and environmental implementationProcess and documentationsApril 16th 2011Function ability of the prototype for the registration of per ownerReview of prototype for the pet owners registerProject plan using time boxingThere are various stages of time boxing and these starts from kick off towards the close out with three steps in between which are investigations, refinement and consolidationsAs shown in the table below. Kick offinvestigationrefinementconsolidationsclose outThe kick off plan is where people meet to form a development team to understand the objectives of the time box and be able to accept and implement.
The main purpose of this is to ensure that there is common understanding, feasibility of the time box and what can be the expected outcome, acceptance of the criteria.
It is also used to review and access availability of the team members and dependencies and also the risk involved. Investigation stage details all the products required including the agreement of the qualitative and deliverability of the time box. Refinement is where the development and testing of the time box is done and agreed priorities implemented. Consolidation is where loose ends are tied to ensure that the products all meet the accepted criteria. Close out is the rolling out of the time box and acceptance of the implementations. In the time box implementation there should be increment which should give the user something that is useful in its own self and have maximum functionality and this should be done in different time boxes and each should contain three main iterations to identify, plan implement and review the concept this is done in three steps first ids to investigate the results that are expected from the time box.
Secondly to refine the results and thirdly to consolidate the result Prototype requirements’ TableFirst in order to be able to build a prototype you need to be able to build a model which is easier to use.
Most models change along with dimension of abstraction, formality or level of detailsDiagram below shows the model to be used by K U management for their client database. Registration numbernametypeuserowner 1st release1,2,3Prototype ARegistration and details of the owner stored in accessible central databaseAdministratorDirector 2nd release4 & 5Prototype BInput and list of appointments for the next weekAdministrators, Nurses and the VetDirector 3rd release6 & 7Prototype CStaff and clinic information and particularAdministrative assistant and system administratorDirector 4th release8Prototype DReport on past appointmentsSystem admin and managesDirector Prototyping is important in a sense that it will demonstrate to the cluent the functionality of the system and enable the implementers to rectify any misunderstanding which may arise.
It also enables the implementers to identify the requirements which were missed before and any difficulties in the interface. It also tests the feasibility of the prototype. Class diagram of the proposed systemClass diagram should be compartmentalized in several manners and it should show all the process which will be implemented by the prototype system.