|
The System Innovations Process for Internet Development This section defines how System Innovations works with Clients to define Internet strategies, clarify the vision for the web site and define the requirements. It describes our process methodology for conducting a development project, all the way from start to finish.
1. Gather Project Information - We start by interviewing the client to explore the goals and parameters for the website. We may also fill out a project profile questionnaire, or provide one for your use. The business case for the web design project should be explored at this stage, with input from the web producer (such as Sytem Innovations) as well as input from the client on the benefits, target audience demographics, marketing strategy and expected budget range. Business models are developed at this stage, indicating scenarios that customers visiting the site would likely follow, and the broad outlines of business information as it flows through the site. For an excellent business book that profiles specific examples of successful websites, see StrikingItRich.com, by Jaclyn Easton. To get an idea of how web projects flow, you might also see Secrets of Successful Web Sites. I'd take some of the time and cost information in this book with a grain of salt, but it's a good introduction to the complexities of web project management. 2. Clarify Vision and Site Requirements - to help get a clear picture of the vision for the site, we develop a mock-up of the desired site, indicating data needs, business data definitions, target customers and more information about the audience for the site. Usability design starts now and will continue through the actual site development. The object of good web design is to invite and retain site visitors through a design that's intuitive, engaging, and produces an experience of flow for the visitor. The design will include the site map showing all the pages in the site and the desired navigation flow between pages. We will build a basic list of project requirements, and determine expected volume and traffic projections at a ball-park level. We also establish the initial project approach plan at this stage and develop a high-level estimate covering options depending on the client budget range. 3. Identify and Integrate Needed Components - next we define the logical components needed to develop the web site and support the business processes required to conduct business on the site. We'll define the technical architecture requirements, logical data model & data sourcing if necessary and determine the availability of the desired information. Working with the client, we decide on the features the site will implement, and the options for doing so. Now is the time to research the feasibility of any implementation options that require the use of new technology. We also define the human resources that will be required by the project and help the Client locate and select appropriately skilled service providers for every stage of the site's development. Development estimates of time and cost will be finalized at this stage, and a release strategy put in place. The release strategy is characterized by short development cycles (~3 months), prioritization of needs and the use of reusable components which allow us to benefit from prior experiences on similar projects. Release 1 is often defined as developing just enough to illutrate the site concept, address the initial target market and start generating revenues. To accomplish those goals, we develop and publish a skeleton site with simplified functionality, many of the backend business processes performed manually and technical "feats" minimized. For a discussion of some of the issues involved in releasing software on the Internet, see the Internet World Guide to Maintaining and Updating Dynamic Web Sites. 4. Build Technical Design & Templates - The next step is to develop or verify design guidelines, to ensure a consistent look & feel throughout the site. We also build the technical and physical design, adding more detailed information to the earlier documents. Database design and access is determined if developing a database-backed web site, and design for any special customer features is completed. Page templates or style sheets are developed to execute the site design, providing consistent branding and navigation for all pages. If you have a technical orientation or background, one of the best books on actually building web sites is Philip and Alex's Guide to Web Publishing by Philip Greenspun, a computer science educator at MIT. 5. Develop & Test Actual Site - The project schedule is detailed as appropriate, and test plans are defined. We will discuss and determine any special hardware/software needs for the client business site or development platform. Site security, backup and recovery planning takes place at this stage. A project site is established for client communication and iterative testing of the site as it is developed. Seven different dimensions of system performance will be tested, including:
We recommend using a combination of developer/non-developer, project insider and project outsider to perform the testing. Test results are logged, reported to the client and final reports receive a client signoff approval before the site is released for publication. Internet promotion planning also begins at this stage. 6. Deliver Published Site - once the site has gone through rigorous testing it is ready for publication on the web. Moving the html and databases into production will necessitate some final adjustments and tuning to the code. Problem logs maintain a record of issues & their resolutions for use in improving our process for the next time around. When the client agrees it's ready, the site is released for public viewing. Internet promotion plans are implemented, with search engine sign up and tuning of keywords, web rings joined and placement of desired banner ads. 7. Ongoing Support & Site Administration - future releases of the site represent an ongoing support effort. Usually developed in 3-month cycles, they flesh out the skeleton published in release 1. Future releases gradually automate more business processes and the implementation of site functionality becomes more sophisticated. In short, tested technology is wisely employed to add value. The benefits of the released approach include:
[Company Profile] [Services] [Home] [Forum] [Laura's Bio]
|
