Describe the steps involved with the Rapid Evolutionary Prototyping Approach
as it applies to developing a Web application. How is it related to agile development?
The definition of Rapid Evolutionary Prototyping Approach can be defined as an easily extensible model of a proposed system that provides users of the application with a representation of the part of the system (Philips, n.d.). In this aspect, we can develop the project in the structured manner, or we can distribute the task in accordance to phases or steps for the elaboration of this we can say that this is the method in which prototype is firstly being created, and then during the each steps and phases, sometimes after the periods, if any requirement of modification appear, we can do that.
The main reason in terms of this distributed project in different phases is that it makes the complex task broken down with hard real time constraints in phases, and different developers can develop the hard real time constrains (Philips, n.d.). Hence, from the description above, it is obvious that in Rapid Evolutionary Prototyping Approach every project or Web Application under development undergoes different phases, which means that it is regarded as the best technique to develop any project t in today’s time.
Particularly, not only will the developers be able to provide review or modification about their task at any time or in any phase, but it also gives opportunity to end users or stakeholders to request any modification in project at any time during the project development. As well as this, the feature of Rapid Evolutionary Prototyping Approach simply reveals that this technique is fully flexible in nature and really helpful for developer and the end user. However, lots of steps will be needed in the Rapid Evolutionary Prototyping Approach mentioned below (adi, 1997):
A. Step for project plan, analysis, and requirements for creation database
This is the most important part of the project development, so the a prototype is made in this part based on the user requirements. Project management, resource management and planning are also decreased in this step.
B. Step for design of system
In this step, the design team will be employed for the work related to the detailed design of project, like what it will include, how it will look like, how it will perform tasks in accordance to a detailed manner and design mode. In addition, this step also takes output of previous phase as its input.
C. Step for testing
Testing step is usually implemented when the coding part of the project development cycle is completed. In this step, a lot of types of software testing tools will be available, depending on the project, such as Black box testing and White box testing for the testing of modules or integrated parts of modules, which simply makes the coding part more reliable by eliminating the factors of bugs or errors in the system.
D. Implementation step
This step is considered as the back-bone step during the project development because this step consists of actual development of the project. In this step coding part of the project gets done by software programmers. This step also takes the output from its previous steps as its input as well
E. Step for operation and maintenance
This step is regarded as the last phase of the Rapid Evolutionary Prototyping Approach as it stays for the lifetime of project. This step consists of the maintenance, servicing and operations of actual system. Therefore, this was the description of what actually Rapid Evolutionary Prototyping Approach means and different steps that it undergoes during the development of any Web Application. Thus, in this step, the product is under operation and the maintenance of system is performed through its life.
How is it related to agile development?
Agile development methods are a progression on the rapid evolutionary prototyping approach, and customers plays an important role in either EP or agile development. Therefore, both are customer centric. In other words, both methods of development use rapid, frequent delivery of software to the user. Working closely with the business and constant communication are required in agile development and the rapid evolutionary prototyping approach (Szalvay, n.d.). This is in contrast to software development methodologies that use a planned approach such as the waterfall model. More importantly, both of them pay more attention on the working piece of code for software product rather than its documentation, because both of them have the iterative nature of development management can be clearly carried even though there are changes, for example, a change could be addressed in the next iteration. Therefore, E, steps involved in EP and agile development are similar.
References
Phillips,G. (n.d.). Evolutionary Rapid Prototyping. Retrieved March 30, 2010, from http://phillips.rmc.ca/courses/493-1998/lectures/rapid-prototyping/rapid-prototyping.html
Szalvay, V.(n.d.). An Introduction to Agile Software Development. Retrieved March 30, 2010 from http://danube.com/docs/Intro_to_Agile.pdf
No comments:
Post a Comment