|
This paper presents the
methodology I have used for managing development of web-enabled applications.
It indicates the phases involved in development and outlines the deliverables
at the end of each phase. For small web-enabled development projects that most
SME companies or departments within larger organisations might want to
undertake, it’s not really necessary to stick rigidly to all the methods and
techniques detailed in these papers and a “lite” version can be deployed.
Methodology
Ian Hope (T/A Blue-Equity)
follows a methodology that incorporates the best practices of Rapid
Application Development (RAD), the Waterfall approach and iterative prototype
approach. This methodology seamlessly integrates the iterative nature of
prototyping with the controlled systematic approach of the Waterfall
methodology to provide a framework for the Rapid Development of incremental versions of the Application system
which is to be developed. Overall management of the project from business-case
assessment through to product delivery can be managed within a PRINCE2
framework. This approach can be used to extensively leverage a repository of
reusable and customisable components. This methodology is a part of my Software
Engineering Life Cycle (SELC) process.
Rapid
Application Development (RAD)
My methodology extensively uses the RAD methodology to develop
rapid iterative prototypes that evolve to the final application.
The
RAD (Rapid Application Development) model enables rapid development of high
quality products and applications. The key factors in the delivery of
solutions through this approach are tools, people (technical, functional and
user community), methodologies (JAD, JRP and use cases) and the quality
processes that govern the project. The four phases of the approach are
1.
Requirements planning (JRP, use cases)
2.
User Design (JAD, functional prototyping)
3.
Construction
4.
Implementation
Joint
Requirements Planning
Joint
Requirements Planning (JRP) Sessions are non-technical workshops for the
purpose of gathering the user requirements. The focus of these sessions is
the business need and not the underlying systems. The participants are
business/domain experts, end users and the system designers.
The benefits that accrue through the use of
JRP sessions are
·
Involvement of business experts during the planning
stage
·
Definition of key requirements at an early phase
·
Quick resolution of user issues
The
participants prepare use cases, which are models that help to define, explain
and represent complex requirements.
Joint
Application Development
Joint
Application Development (JAD) Sessions involve the detailed design of the
envisioned system. The participants at this stage include the development
team in addition to the teams involved in the JRP sessions. The most significant
benefit of JAD sessions is the direct impact on process productivity during
later stages.
Deliverables
at the end of the JAD phase are logical data models, dataflow diagrams and
functional prototypes of the envisioned system.
Construction
Construction
begins soon after the completion of the design phase. The key factors for
these stages are: -
·
Innovation and speed
·
Close networking between team members and
·
Effective communication at all points
The
construction of the system is achieved through the iterative prototyping
approach depicted in the Spiral
Prototypic Model.
|