Discuss what it will take to build 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.
To build web architecture, System analyst should analyze the company’s business needs and develop a clear statement of the goals. Since we have the old site running it is important to understand the business and technology issues involved in the project. Determine whether the IT staff has the necessary skills and experience to implement the project. Consider training, additional resources, and the use of consultants if necessary. Develop the project in modular form so users can test and approve the functional elements as you go along. Test every aspect of the site exhaustively. In this case we have Tony’s chips website already running, it is essential to gather the existing functional requirements. System analyst while gathering requirements can interview people from the old company, production support, gather system documentation and using FACT finding techniques. Once the requirements are gathered and reviewed system analyst should decide whether to develop the software in-house or go for packaged solutions. In this case if we develop in-house then it is essential to build 3-tier web architecture. I would advise the company to use Linux as the Operating system, Apache as the Web server, MYSQL for the Database and JEE as the language to develop the website. Linux, Apache and MYSQL are all open source and the company do not need to worry about the licenses. By writing the software in Java it helps us to deploy the code on any platform and also it is easy to find people who are experienced in Java. While building the new architecture, the design of the system should satisfy business requirements. A successful system must be effective, reliable and maintainable. The system is effective if it supports business requirements and meets user needs. Design considerations involve non-functional requirements (scalability, availability, maintainability) users, data and system architecture. It is important to consider the economic feasibility and total cost of ownership. Web-based systems introduce additional security concerns, as critical data must be protected in the internet environment. While building the new system it is important to think of data conversion from old system to the new system. When a new system replaces an existing system, you should automate the data conversion process, if possible. The old system might be capable of exporting data in an acceptable format for the new system or in standard format, such as ASCII or ODBC. You must maintain strict input controls during the conversion process when the data is extremely vulnerable. System changeover is the process of putting the new information system online and retiring the old system. I would adopt Direct Cutover approach for moving the old system to the new system. Direct Cutover is the least expensive changeover method because the IT group has to operate and maintain only one system at a time. Direct cutover, however, involves more risk than other changeover methods but adopting this methodology with DR plan you will not have any downtime. Once tested thoroughly, having the data converted with a solid test plan, Direct cutover would be best strategy to shift the users from old website to the new website. I would build a Disaster recovery environment similar to production environment. Disaster recovery plans are often part of business continuity plan, which goes beyond a recovery plan, and defines how critical business functions can continue in the event of a major disruption. A hot site is an alternative IT location, anywhere in the world, that can support critical systems in the event of...
Please join StudyMode to read the full document