Implementation of Timeline - Assignment Example

Insert your name here Subject: Management Title: Agile Development 19th April 2011 1. Implementation of Assignment Timeline The 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 boxing April 13th 2011 The planning of the agile development Time boxing Prototypes April 14th 2011 Prototype usability Demonstration of the proposed system Demonstration of user interaction April 15th 2011 Architecture in development and environmental implementation Process and documentations April 16th 2011 Function ability of the prototype for the registration of per owner Review of prototype for the pet owners register 2. Project plan using time boxing There 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 consolidations As shown in the table below. Kick off investigation refinement consolidations close out The 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 3. Prototype requirements’ Table First 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 details Diagram below shows the model to be used by K U management for their client database. Registration number name type user owner 1st release 1,2,3 Prototype A Registration and details of the owner stored in accessible central database Administrator Director 2nd release 4 & 5 Prototype B Input and list of appointments for the next week Administrators, Nurses and the Vet Director 3rd release 6 & 7 Prototype C Staff and clinic information and particular Administrative assistant and system administrator Director 4th release 8 Prototype D Report on past appointments System admin and manages Director 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 system Class diagram should be compartmentalized in several manners and it should show all the process which will be implemented by the prototype system. Clinics, staff id Name Address Telephone Date of birth Gender National insurance number Position Annual salary Appointments, details of the pet owner Details of the pet Staff, vets Nurses Secretaries Cleaners Pets, details of the pet Appointment history if the pet has been booked for appointment in the past Different staff should have different responsibility in order for the successful implementation of The prototype this should be as shown in the sequence below Administrator/secretary Will get the name of the client List the problem List the requirement Check if there was other appointment client Give the details of him and the pets details Book an appointment Appointments The pet will be viewed by the staff which includes a vet and nurses Treatment conclusion Next appointment if necessary 4. Architecture There are different types of environment which might be used to manage the data base these include the use of computer of filing system although computer is turning out to be the most suitable mode of operation since it can be connected to central data base. The design and page layout are also easily accessible. The project for Ku pets should be aimed at centralizing all the functions of Ku clinics in UK and should enable central accessibility to all administrative staff in a sense that if a pet’s appointment was booked in one location when the pet owner books into another clinic his details and that of the pet will be readily accessible to the person who is booking the appointment at that time. An interface prototype should be able to have the requirements with the most used rule being the MoSCoW rule which is the acronym for the most important rules of must have, Should have, could have and won’t have this time. The MoScoW rule should basically be used when filling out the information forms. This should be in the form of a request form as below: New requirement ID: Old requirement ID Owner Name of requirements Priority Users of the new requirements Description of new requirements and its functions and future appointments Description of the nonfunctioning requirements Signature date A change form should also be provided to enhance the usability of the prototype. A sample which is shown below Prototype name Priority Fields to remove Fields to add Change of field names Manger signatures Date In conclusion this information then will be fed on the prototype which is stored in the computer. The information stored in the data base should be able to give an indication of the pet owner’s details and the pets need when it was booked and the details of the vet who took care of the pet and what the condition was by that time. It should also give details of where the pet owner lives and how to contact the pet owner in the future. References: 1. Time boxing CIM320, Kingston University London Read More