| |
 |
 |
|
|
| The stages of
your project’s development are not isolated, and
often overlap to some extent. In order to accomodate this
dynamic, we use various tools to during the stages of
your project, many of which have been incorporated into
the Unified Modeling Language (UML). |
 |
|
|
|
 |
| Project
Scoping |
|
| Initially,
we’ll establish the business case for
your project, and determine its scope and
your initial requirements. We’ll also
obtain management’s buy-off on further
investigation. |
|
|
|
|
|
 |
| Design
Elaboration |
|
| During
elaboration, we’ll refine your project
requirements, establish priorities, determine
the risks involved, investigate approaches,
and develop a project schedule. |
|
|
|
|
|
 |
| Implementation |
|
| Implementation
is an iterative process of designing, building,
and testing code while we implement progressively
larger subsets of your project requirements.
This practice pays off in dramatically reduced
maintenance costs, saving you time, effort
and money. |
|
|
|
|
|
 |
| Delivery |
|
| When
we deliver your completed product, we’ll
conduct extensive testing specifically to
detect flaws. To minimize the likelihood,
we direct our development efforts exclusively
toward correcting flaws. |
|
|
|
|
|
| |
| If your system
centers on user interaction, we’ll develop Use Cases,
which play an integral role in the Design Elaboration
stage. Use Cases provide scenarios detailing the operation
of your system from a user’s perspective. |
| |
| We’ll also
develop Class Diagrams and Interaction and Activity Diagrams
at various levels of detail, which are useful during both
the Design Elaboration and Implementation stages of your
project. During the Implementation stage, we often find
that design patterns also become extremely useful. |
| |
| These distillations
of common approaches to software problem solving provide
conceptual building blocks that can be plugged directly
into designs. Besides helping us form a clean design structure,
they allow us to communicate complex concepts clearly
to others involved in your project. Information Technologies
advocates the use of these tools whenever appropriate,
particularly for systems defined in terms of user interactions.
In such cases, we’ll invest effort into providing
you with a proper foundation for implementation, for which
you will be more than repaid by reducing the amount of
restructuring and bug fixing that would otherwise be required
later. |
|
|
|
|
