Which methodology?
The most establish mythologies are normally the most widely used ones in that industry sector. Over the last 20 years a boom in software engineering methodologies has been seen particular in the Object Orientated (OO) development.It is essential to identify the right type of methods in the development area concerned. In performing such a task it allows the field to be narrow down in the sea of information methodologies available. A common mistake by now narrowing the field is to pick a whole methodology because it is renowned and employed widely in IT development. For example a project dealing with a web application, object orientated in design, focusing on search engine friendliness in the design process, so it would be foolish to adopted a methodology like Structured Systems Analysis and Design Method, (SSADM) just because it is one proven and recognised in the industry. SSADM methods concentrates on database design in greater detail, and in the proposed project above, SSADM would focus on the wrong area of concern to meet the goals.
It is for this reason much attention and research must go into determined the best suited methodology that will address the aims and goals of your project.
To better provide an informed decision on choosing an appropriate methodology that aids the project needs, the it may be best to narrowed down and investigated a broad range of web and application methodologies.
lets look at just two of the main methodologies now...
Repaid Application Development (RAD)
RAD methodology was created by James Martin and first published in 1991, and was proposed as an alternative to Software Development Life Cycle (SDLC) Model. RAD is a tried and tested methodology. One of the reasons why this methodology is so popular in web design applications today is that it uses fast CASE tools, giving web companies a fast turn around. Another reason why is popular with web design applications is that it uses the Waterfall Model. The waterfall model is a software development model as explained in the previous section. RAD also gives the developers a way to repair problems at very early stages because of the prototyping involved.Some RAD advantages
- Flexible, fast
- Incorporates lots of user feedback and users have good input into the system
- Prototyping stage so the user may see something before its even finished
- Ideal methodology where input into in project is large
- Ideal methodology if requirements change during development
- Foundation on Vilfred Pareto's law, 20% of the work is cost 80% of project etc
- Reusability
- Works better in team situations
- Difficult to use if project can not be split into sections.
- Technology used should be a well established one
- Consistency problems
Universal Modelling Language (UML)
UML is very flexible modelling language allowing a way to design using diagrams the whole proposed application (good planning), this way you can also see any possible problems the proposed application may have before spending time changing it after implementation.UML is another method particularly favoured by web application development projects, mainly because it is possible to cater for web application systems modelling in its own targeted approach. One such way is by using the model extensions.
One such well known extension is Web Application Extension (WAE) in UML, as can be read in “Building Web Applications with UML, by Jim Conallen.” The author of the book is the inventor of the notation and the diagram tools are now even available as a plug-ins for Microsoft Visio package.
Unfortunately Jim Conallen only extends the modelling language for a few server side languages (JSP and ASP). With the other techniques for ColdFusion support extensions in UML not tried and tested ones, the conclusion would be best to keep looking for a system which meets the project needs in a more direct manner.
This page was created on:
Last modified: 08/29/2006
