Rapid Prototype Blog

Archive for the ‘Prototyping Based Methodology’ Category

Agile denote nimbleness. Agile is a light weighted development methodology which is based on iterative development, where solutions evolve from tightly collaborated cross functional teams.

Agile denote nimbleness. Agile is a light weighted development methodology which is based on iterative development, where solutions evolve from tightly collaborated cross functional teams.

Principles of Agile methodology

Agile methodology primarily focuses on Individuals and their communication, Working Software over comprehensive documentation, Customer collaboration over contract negotiation, and responding to change over following a plan.

a) Customer Satisfaction

b) Good team with higher accountability

c) Light weight requirements, flexibility for rapid changes

d) Small and Iterative cycles

e) High degree of communication

An agile process facilitates the customer to have a quick view of the product. Agile process delivers early and often. As a rudimentary system is provided with in first couple of weeks, Customers has a chance to make requirement changes if they feel that what they see doesn?t match with what they envision. Requirements changes dynamically but they strictly adhere to deadlines.

]]>

As agile methodologies are rapid in nature, a team of good players needs to be accommodated. Though all players need not be strong players,players with higher accountability and user involvement is imperative. The team should comprise of developers, customers, and any other business related personalities. The team should be empowered to make decisions.

Requirements have to be light weighted. We can expect change in requirements late in development process. It should be noted that requirements evolve with fixed time scale. This differentiates agile methodology with conventional development methodology. Generally industries go with 80-20 acceptance policy.

Agile methodology advises to develop project in a small size with an incremental nature. Agile is iterative in nature. This nature reduces the risk of what you see vs. what you envision aspects. It also provides effective cost management, and less re-factor cost. Deliverables are given preference over documentation.

There should be a high degree of communication between the team members in order to implement agile methodology effectively. There should be significant interaction between the customers, developers and stakeholder. Just-In-Time [JIT] methodology has to be implemented for successful practice of agile methodology.

Agile methodology provides rapid delivery in a dynamic environment. This incremental nature provides cost-effective behavior for product development. This methodology not only enables to deliver cost effective prototype, but also provides flexible re-factoring. In a competitive environment, business always competes with others business by releasing innovative products in a dynamic rapid world, which can be completely supported in agile methodology.

Reference:

[1] Pavan Gorakavi, Build your project using Agile Methodology http://asapm.org/asapmag/articles/A1_AboutAgile.pdf

Once you are in the software development field, you will come across a variety of development methodologies followed while developing any software project. This methodology refers to processes used to plan the strategies for software development.

A software methodology used in one project may or may not be suited to another project. Each software methodology may have its own strengths and drawbacks. There are a variety of software approaches developed over time, which are well-matched to specific kind of projects. Read on to learn a few points on the various methodologies developed.

§         Waterfall Method: In waterfall method, which is the oldest software development methodology the software development stages are performed in a sequential manner to ensure the quality and reliability of the software. Even though this model provides complete documentation, over quality software and also the work is being done in stages, the waterfall methodology is cumbersome and slow in approach. The basic principles applied here is that the project is divided into different phases, which are sequential in nature. There is stress given on planning and implementation of the overall system and a firm control is maintained on the overall life of the project.

§         Prototyping Method: Software prototyping refers to creation of incomplete models of the software program during the software development process which may be different from the final product. Prototyping helps the software users to evaluate the software during the design stage before actually trying them out. In this model, the users are thoroughly involved in the software development process, which increases their acceptance of the final implementation. It also helps the users to understand the business problem, which is necessary to avoid solving the wrong problem.

Incremental Development Method: Incremental software development methodology involves breaking the project into small section, so as to make the change simplified during the development process.

§         Spiral Methodology: In this methodology various steps are staged for manifold deliveries. Spiral methodology works on the principle that the team is able to start small and help from the trial and error method.

§         Rapid application development: Rapid application development (RAD) refers to speedy development and delivery of best quality results at a relatively low investment cost.Rapid application development is asoftware development methodology that involves nominal planning, thus the software can be written in much shorter time. RAD takes benefit of preset tools and techniques to streamline the process of building information systems. Rapid Application Development has four important features:  methodology, people, management, and tools.Development would be slow, If any one of these ingredients is insufficient.

§         Extreme Programming: Extreme Programming is based on values of simplicity, admiration, communication, advice, and guts. In this changes are implemented as per the customer’s suggestion.

More Prototyping Based Methodology Articles