|
| FUNCTIONAL
REQUIREMENTS:-
|
S.S. Technologies believes that any successful
software system is the result of sound strategic planning and documentation.
To create a successful system, we must determine the needs of its
users.
Prior to development, the S.S. Technologies executives meet with
the client team (this meeting includes everyone who has a vested
interest in the project) to discuss the parameters of the project
from both "design" and "functionality" perspectives.
The "findings" from this meeting are then developed into
a set of Functional requirements that are presented to our clients
for review, modification and ultimately approval.
In the interest of professional integrity, S.S. Technologies follows
the following process to assure positive client relations and successful
deployment of web applications.
|
|
| (1)
A S.S. Technologies project manager and other impacted personnel
hold an initial meeting with the client to discuss the parameters
of the project in terms of both design and functionality. It is
helpful at this point if the client can provide documents detailing
the number and complexity of Web pages the site will have, a proposed
site map if site organization has been considered, brief descriptions
of any functionality that will be required, details of special
needs such as security, interaction with existing databases, use
of existing design elements, etc, and references to other sites
that sport a design the client finds appealing.
|
| (2) S.S. Technologies
prepares a rough estimate of time and costs to complete the entire
project and a fixed estimate to complete enough of the Analysis
and Design work (described briefly below) such that the client can
be provided with a accurate estimate for the entire projects. (The
initial rough estimate could vary as much as 50% or more if the
project has not yet been well defined; fixed estimates can be guaranteed
within 10%). Estimates will be incorporated into the Inception section
of the Blue Book described below. |
| The
project is awarded to S.S. Technologies assigned project manager
establishes job codes and schedules the development process. |
| Client approves the proposed
development schedule and a Custom Development Agreement and necessary
software licensing agreements are signed. |
|
| (5) Our staff members
begin work on the project, documenting their progress in a special
notebook referred to as the "Project Papers". This notebook
will contain several sections- Inception, Analysis, Design, Deployment,
Transition and Appendices. The Project Book is a dynamic set of
documents that will continue to develop throughout the development
and deployment processes. The client will keep a copy of the Project
Papers and additions will be explained our project manager. The
Project Papers may be simplified for smaller projects. |
| |
| (6) Design and development
begins. Although many types of work occur concurrently, the rough
process goes through the following "steps" :- |
(a) Inception- Brainstorming, establishing
relevant facts, defining assumptions and creating a development
overview, a project summary, a purpose statement and a rough
feature list.
(b) Analysis- Required functionality and design are defined
using the Universal Modeling Language (UML). The Actor Models,
Use Case Models and User Interface Models are established.
(c) Design- Software and hardware architecture is established.
(d) Deployment- The deployment of a preliminary version of the
site is planned and implemented.
(e) Transition- The testing model is established and implemented.
Training and hand-off procedures are defined.
|
| (7) The client makes final approval and
subsequent phase or projects may be planned. |
| |
