|
 |
At
Seattle Web Development & Consulting, LLC the starting point for every web
project begins with a free initial consultation. Here, we take the time to
listen and establish a trusting partnership to identify your objectives. |
 |
Clarifying
the Vision: Insuring shopper goals, business goals, sustainable competitive
advantages, critical business process, needed features and functions are
defined. Depending on your online venture, the scope may vary dramatically. |
 |
Planning
and designing: Sadly, this phase is commonly omitted with applications. In this
phase of the project, the vision is more fully defined, identifying, on a
technical level, what is going to be built and how. |
 |
Developing the application: In this phase, the pieces necessary to build the
application are compiled and logic code written. The actual development of
the site will consist of implementing the user interface and data services
tiers. |
 |
Testing and piloting: After incorporating user feedback into the site and
additional application test performed, the site will be moved to a deployment
server. Again, depending on the size and structure of your company, this phase
can be as simple as moving files or rather complex.
|
|
|
|
 |
|
|
Mailing Address: |
|
|
| P.O. Box 17481 |
| Seattle, WA 98127 |
|
|
Email: |
|
|
| info@seawebdev.com |
| sales@seawebdev.com |
| custsvc@seawebdev.com |
|
ComputerRepair@seawebdev.com |
|
|
Phone: |
|
|
| (206) 354 - 6053 |
|
 |
|
|
|
 |
Planning for security: As part of every phase in the development of the
application, security concerns must be addressed. Issues such as authentication
and authorization must be considered. Authentication simply refers to
discovering who a particular user is and testing their identity against a
secure source. Authorization refers to the functions of the site, in which a
user is allowed to take access. |
 |
| Planning
the architecture: Before advancing too deeply in the development phase,
architectural issues must be considered. Whenever possible, we design
e-commerce applications following a classic n-tier design. The purpose of
separating the application into three basic layers, presentation, business, and
data services is to provide logical separation segmentation. |
 |
|
|
 |
Deploying
the application: After the application’s code has been written and tested,
appropriate security concerns implemented, and the physical architecture
decided upon, it is time for application deployment. This involves moving the
application from the development server to a production server that has been
properly configured for the application. |
 |
Administering the application: For your organization to be responsive to
changing market dynamics, your web application must remain flexible and
scalable. These considerations must be planned for. The application
developed must be adaptable to accommodate needs not yet known.
Additionally, functionality such as administrative controls must be built in to
make your application an ongoing success. |
|