|
RAD Development Approach |
||||
|
Spiral Prototypic Development LinksMultiple employs various packages and tools to aid the
process of rapid application development.
These products include requirements gathering tools, prototyping
tools, CASE tools, language development environments such as those for the
Java platform, group-ware for communication among development members, and
testing tools. The
objective of the model is to shrink delivery times by “crunching” preliminary
study times and focussing on initiating construction efforts as early in the
project as possible. Subsequently, the teams focus on prototype iterations
until user requirements are satisfied. To avoid “endless prototyping”, a
pre-agreed limit to the number of iterations can be imposed. This
model is best employed in situations such as e-Business application development
where requirements are sometimes not initially known with a great degree of
clarity or certainty. The teams focus on building solutions based on concepts
rather than definitive specifications. The model helps by ensuring that both
end users and owners of the system understand the application as it is being
built and have the opportunity to refine, improve and enhance the system as
it is being developed.
|
|  LinksMultiple also has considerable experience in delivering
solutions through the use of Unified Modelling Language (UML) methodologies.
UML is a standard notation for the modelling of real-world objects as a first
step in developing an object-oriented program. Its notation is derived from
(and unifies) the notations of three object-oriented design and analysis
methodologies. The
design of a system is essentially a blueprint or a plan-on-paper for a
solution of the system. A design methodology is a systematic approach to
creating a design by application of a set of techniques and guidelines. LinksMultiple’s design process is adapted from the Unified Modelling Language and the Unified Process and customised to
suit the requirements of each project. The
design essentially contains a detailed description of the processing logic
and data structures, sufficiently complete for coding. Some of the objectives
that have driven the design methodology are as follows: ·
Verifiability – How easily the correctness can be
established ·
Completeness – Requires all design components to be
specified ·
Consistency – No inherent contradictions in the
system ·
Efficiency – Optimal use of resources with better
algorithms and not due to code
tampering. ·
Traceability – All design elements should be traceable to the requirements ·
Simplicity and ease in understanding of the design The various “artifacts” that are produced as a part of the design
process are listed below: Use
Case Diagrams
Use
case diagrams describe the behaviour of a system from a user Sequence
Diagram
A
sequence diagram represents an interaction between objects that focuses on
the message broadcast chronology. An object is represented by a rectangle and
a vertical bar called the object Class
Diagram
Class
diagrams express, in a general way, the static structure of a system, in
terms of classes and relationships between those classes. Just as a class
describes a set of objects, an association describes a set of links; objects
are class instances, and links are association instances. The class diagram
does not express anything specific about the links of a given object, but it
describes, in an abstract way, the potential links from an object to other
objects. |
|
|
Back to the LinksMultiple eBay Auction | eBay Shopping home page
Copyright 2005 LinksMultiple - all
rights reserved. No part of this information may be copied or reproduced
without prior written permission.