Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
This presentation is on the processes developed, the team members involved, and the items
delivered which were
used to plan, design, and deploy Web based applications.
These are
the standard processes used in approving, prioritizing, designing, planning, building and executing Web
based applications.
Maintenance in
this respect is much more than keeping server hardware and software up and running – difficult in itself - it is
Customer Satisfaction based
enhancement, and part of the design, development, product documentation, training, sales and marketing
business ventures that maintain and
increase customer base and financial future. In the following slides we will cover the individual
phases, including details of the
requirements, output or artifacts, and those team members who contributed to the successful implementation of both
within the company and in contract
companies.
While the
processes and procedures may not occur in the exact timeline as illustrated in this slide, each stage
comes to the forefront and becomes the
most integral part of the project generally in a similar order. As Web based deployments are iterative
processes this may vary starting at
Stage 8, where content management, and deployment are part of the added feature set gained from
Application Enhancement often based on
Customer Feedback, and is a part of maintenance.
As illustrated by the colored lines above, as the
Web Project progresses more human
resources are consumed of an increasingly complex nature. As the Test phase comes into play planning,
software development and content
creation all decrease the amount of effort in hours.
So let’s discuss the
phases in order. Note that some processes are over definitively, and others continue throughout the
project.
Team Members of the Project Approval,
Priority Evaluation and Collaboration Phase.
It was recognized that this is an golden
opportunity to test the water with a small but significant project.
It was not
anticipated how complex this project was, how time and resource consuming, and how many departments at the company would
be integral to completing this project;
what was learned is significant and valuable for future Wonderlane business projects success.
The widely discussed feedback is that is an excellent
piece of strategy that management agreed to
do the Web site, a smaller “figurehead” project first before jumping headlong into Web Development. This information
is potentially much more valuable to the
company than even the positive marketing inroads made by the successful release of the Web site application itself.
Requirement Gathering
and Product Management Phase
contributors.
Analysis and Design takes the business
requirements and turns them into feature sets and user interface design plans
through scoping, application design and the other things mentioned here. Some
considerations such as Capacity planning and whether or not there is exist
software and hardware to support some of the features or their implementation
come into consideration.
Team Members listed here:
Team Members on this phase listed here.
The Web site allows
endusers to work on a proposal in multiple sessions. Endusers can choose to go back, save and finish later, or complete a
quote. It supports multiple browsers, and
shares the COM design with the legacy database but as it does not
directly interact with
legacy Databases,
thereby reducing the load on
legacy databases.
Features common
to
Registration, such as User Name Recovery, Password Recovery, the ability to Change
addresses, Add/Change phone
numbers, Change password, add/change email address will be future functionality
implemented in the Open Networks Web
Access Control software.
Team members listed here. As you can see by the graphic, Content Creation and Business Information Management take a large chunk of
time in the project. Business Information
Management is a component of Content Development but it differs significantly based on business processes. When Code and Content
development is complete then after the systems
are hardened the product is ready for the rigors of Test / Quality Assurance.
Team members
listed here, also approving the changes include Project Owners.
Team members
from security listed here.
Management and Content Development Team
members listed here
Team members listed here:
Team members listed here.
Team members
listed here: