Professor Stan Buch
In this paper I will assume a new company has hired me to manage a project that will move the old Website from an externally hosted solution to an internal one. The company’s leadership is very concerned about redundancy for their site, insisting that a back-up site be available as a failover in case the main site goes down. In addition, they want the site redesigned to allow customers to order products online.
As part of my job, I must complete a 10-to-15 page paper that follows this project through the system development life cycle (SDLC). This assignment will require I to do the following: * Discuss what it will take to build a Web architecture, move an existing Website with minimal downtime, and provide a disaster recovery solution to ensure the site is always available. *
* The Web architecture should describe and justify operating system choices (i.e., Linux, Apache, MYSQL, PHP, Windows, IIS, SQL, etc.). * Evaluate alternatives to the company self-hosting the site. * Build a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website. * The chart should include a minimum of five (5) tasks, each with three (3) sub-tasks. * Explain and justify the system architecture you have selected. * Illustrate the system architecture using Visio or equivalent software. * Create a use case that documents the event of a customer ordering a bag of chips from the new Website. * The use case should include a graphical representation using Visio or equivalent software and a text description of the events. * Discuss the support operations that the internally hosted Website will require after implementation. * Explain how you will evaluate the performance of the new site and the success of your project.
Whether you are planning to implement a new site or upgrading an existing site to meet growing needs, the following provides guidelines for meeting the performance and availability demands of today’s online business environment. The mature business site is multi-tiered, with several hardware components, including: • Firewalls and routers
• Load balancers
• Web servers/front ends
• Application servers
• Database servers
• File servers
• Storage hardware
The software environment that runs on this hardware can be equally complex, and may include: • Operating system software (i.e., Linux, Apache, MYSQL, PHP, Windows, IIS, SQL, etc.) • Web/application server software
• Database software and applications
• Storage management software (backup/recovery, clustering and failover, etc.) Design an architecture that ensures availability. Build redundancy and scalability in your design so the architecture will grow as your business grows. Choose highly available and manageable system platforms. Make sure that the foundation for the various components is as robust as possible, while creating an operating environment in which you can manage constantly. All of the critical components of the site should be built on platforms that optimize the availability and manageability of the total solution. The combined hardware/software platform should keep downtime of all kinds low – including unplanned failures and planned, administrative downtime. Requirements are a high mean time between failures for all hardware components, fast recovery from outages when they do occur, good administrative tools and policies for system maintenance, and support for online administrative activities where possible. Choose solutions that optimize performance regardless of system load, as the site needs to run at peak performance, all the time. Many factors affect site performance, from architecture to application design to processor speeds. Good application design is the most important contributor to performance. After that, processor speed is significant. Building on...