Paper Example on Evolutionary Prototyping: Rapid System Design & Development

Introduction

Prototyping refers to the rapid growth in designing a system or software (Arvola, 2004). It is majorly used to help developers and customers understand the requirements of the system. For this project, the most suitable prototyping technique that would be selected is evolutionary prototyping. Evolutionary prototyping refers to an approach where the prototype is generated and polished through a few phases to the final system (Arvola, 2004). The primary objective of evolutionary prototyping is to provide the end users with a working system. The technique is suitable for developing a system whose requirements cannot be developed prior such as the user interface systems (Broderick, & Boudreau, 1992). Substantially, evolutionary prototyping accelerates system delivery and enables users to interact through the system. The design, specification, as well as, implementation are all linked, and the system is developed as a chain of augmentations that can be conveyed to the end users.

Is your time best spent reading someone else’s essay? Get a 100% original essay FROM A CERTIFIED WRITER!

Save 25%

Management Plan

The software company under this study must first design a management plan that comprises of nine phases for designing the kiosk. Reports have indicated that such a proposal may create room for installation, designing, operating, and controlling the designed software for the kiosk (Kaplan, & Norton, 2008). The primary management phases will include the initiation stage, concept development stage, planning stage, specification examination, design development, test, and implementation, as well as, operation, and maintenance phases.

Explanation of Management Plan Stages

The initiation phase is the first stage in the management plan formulation. It encompasses the formulation of a concept proposal and project charter. First, a commencement meeting with the partners is conducted to collect views from everyone. It also entailed a comprehensive analysis of every objective depicted in either subjective or quantitative terms. More importantly, obligations and parts of the project director and manager or group are differentiated to guarantee that all worries are handled and everyone involved in the process is in agreement (Kaplan & Norton, 2008).

Concept development is the second phase, and it entails the process through which the state establishes the project scope statement. The stage involves articulation of the venture scope, as well as, the work breakdown structure. The range of degree will formulate the objectives and activities of the venture in terms of its significance and maps out procedures to be followed. Reportedly, with the administration, the scope will be able to monitor the progress of the project (Kaplan & Norton, 2008).

Planning phase is the next stage and it third where plans for managing risk, project, communication, change, stakeholder, and staffing are formulated as they are essential during the planning stage. The phase entails deciding the time required to complete each step, as well as, the expenses needed in each period. Here, the project manager draws a timetable for completion of each stage and appoint relevant personnel to complete tasks involved in each phase.

The requirement analysis stage is the fourth phase where operational requirements guide and the plan for testing the program are incorporated. This is followed by the design stage which is regarded as the most critical stage for the company group that wants to design the system. In this phase, the plan for conversion, document detailing the system design, guide for the operations, maintenance and training are put together. Reportedly, the design stage generates a logical answer to the needs collected and the scope of the projected system that will be developed.

The development phase is the next stage after the design phase, and it is where integration documents, software development manuals, as well as, test analysis reports are critical. The development phase is then followed by the test phase. Undoubtedly, the development phase comes the testing of the codes developed, a process that most engineers find very interesting. In this stage, the project manager confirms that the developed system meets the business requirement and determines whether the developed system has errors and deserts.

The next phase is a very critical implementation stage. During the last step that entails the closing or disposition plan. It is critical to note that during the entire nine phases described above, customer satisfaction is not considered. Nonetheless, deliverables must be analyzed for success, and establish customer satisfaction, as well as, other critical components when developing any design.

Estimation of the Duration for Completion of Each Stage

The whole process of a management plan for the software will take about 8- 12 months. The initiation stage together with the formulation of the project scope will be completed within a month. Importantly, completion of each stage will depend on its predecessors. It is estimated that the planning stage takes about 3-6 months while the requirement analysis will be formulated within 21 days. Similarly, the design stage will be completed within 30 days while the development phase will last for two months. Testing and implementation will take about three months. These phases are allocated sufficient time to enable the software developer to seal the loop within the management system.

Comparing and Contrasting the Interfaces

Comparing the interface kiosk's interface with self-log in of the receptionist requires a detailed examination of environments with congest traffic flow such as DMV. This is the case in this paper as it will make it easy for the users to process tasks thereby minimizing waiting time especially in the reception section. In the kiosk, self-check will save receptionists from numerous duties and replace the registration process or renewal of driving license. Further, it will make it easy for clients to access their driving history and detect any cases of double entries within the system. The system will also enable customers to easily change their personal information and pay by themselves.

The kiosk will ask clients similar identify verification and security questions that they are likely to be asked by receptionist at the receiving pay (Broderick & Boudreau, 1992). Besides, it will save the money that DMV could use to pay wages or salary for the customer service representative. The key benefit of ensuring that there is receptionist's check in clients during free hours will provide clients with the opportunity to ask questions and fulfill more urgent needs. Principally, DMV kiosks need powerful features to carry out all the transactions motor vehicle give to its customers. Therefore, those kiosks that are serving in a motor vehicle must offer one-stop customer experience and must lower wait time. Reportedly, DMV kiosks for a motor vehicle can process numerous applications such as renewal of registration, PIN management, and change of address, replacement of title, ordering new plates and paying for citations (Broderick, & Boudreau, 1992).

Conclusion

In conclusion, as discussed in the paper, my software development form will adopt an evolutionary prototyping technique to allow clients to self-log in through a new generation kiosk. Principally, evolutionary prototyping technique has challenges such as problem management in which competent persons are needed to continuously develop them team and expensive long term maintenance costs because of continuous changes that corrupt the system structure. Despite these challenges, evolutionary prototyping is established to engage end users in the process of development that leads to a high level of customer satisfaction. Principally, this software development firm will fulfill the needs of customers as it will deliver a kiosk that can minimize customers' wait time and offer a better alternative to provide services. Precisely, the organization will meet the expectations of customers by developing a whole and perfectly formulated management plan that consider all phases involved in designing customer interface.

References

Arvola, M. (2004). The interaction character of computers in co-located collaboration. In People and Computers XVII-Designing for Society (pp. 37-51). Springer, London.

Broderick, R., & Boudreau, J. W. (1992). Human resource management, information technology, and the competitive edge. Academy of Management Perspectives, 6(2), 7-17.

Kaplan, R. S., & Norton, D. P. (2008). Mastering the management system. Harvard business review, 86(1), 62.