Description
Tony’s Chips has recently been sold to a new independent company. The new company has hired you 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 your job, you must complete a 10-to-15 page paper that follows this project through the system development life cycle (SDLC). This assignment will require you 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.
- Design high-level logical system characteristics (user interface design, design of data, and information requirements).
- Use contemporary CASE tools in process and data modeling.
- Use technology and information resources to research issues in systems analysis and development.
- Write clearly and concisely about Systems Analysis and Development topics using proper writing mechanics and technical style conventions.
Criteria
1. 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. Describe and justify the operating system choices.
Weight: 10%
Did not submit or incompletely discussed 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. Incompletely described and justified the operating system choices.
Insufficiently discussed 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. Insufficiently described and justified the operating system choices.
Partially discussed 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. Partially described and justified the operating system choices.
Satisfactorily discussed 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. Satisfactorily described and justified the operating system choices.
Thoroughly discussed 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. Thoroughly described and justified the operating system choices.
2. Evaluate alternatives to the company self-hosting the site.
Weight: 5%
Did not submit or incompletely evaluated alternatives to the company self-hosting the site.
Insufficiently evaluated alternatives to the company self-hosting the site.
Partially evaluated alternatives to the company self-hosting the site.
Satisfactorily evaluated alternatives to the company self-hosting the site.
Thoroughly evaluated alternatives to the company self-hosting the site.
3. Build a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
Weight: 15%
Did not submit or incompletely built a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
Insufficiently built a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
Partially built a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
Satisfactorily built a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
Thoroughly built a Gantt chart using Microsoft Project or equivalent software, showing all tasks associated with implementing the Website; at least five (5) tasks, each with three (3) subtasks.
4. Explain and justify the system architecture you have selected.
Weight: 10%
Did not submit or incompletely explained and justified the system architecture you have selected.
Insufficiently explained and justified the system architecture you have selected.
Partially explained and justified the system architecture you have selected.
Satisfactorily explained and justified the system architecture you have selected.
Thoroughly explained and justified the system architecture you have selected.
5. Illustrate the system architecture using Visio or an equivalent software.
Weight: 20%
Did not submit or incompletely illustrated the system architecture using Visio or an equivalent software.
Insufficiently illustrated the system architecture using Visio or an equivalent software.
Partially illustrated the system architecture using Visio or an equivalent software.
Satisfactorily illustrated the system architecture using Visio or an equivalent software.
Thoroughly illustrated the system architecture using Visio or an equivalent software.
6. Create a use case that documents the event of a customer ordering a bag of chips from the new Website. Provide both graphic and text descriptions.
Weight: 15%
Did not submit or incompletely created a use case that documents the event of a customer ordering a bag of chips from the new Website. Incompletely provided both graphic and text descriptions.
Insufficiently created a use case that documents the event of a customer ordering a bag of chips from the new Website. Insufficiently provided both graphic and text descriptions.
Partially created a use case that documents the event of a customer ordering a bag of chips from the new Website. Partially provided both graphic and text descriptions.
Satisfactorily created a use case that documents the event of a customer ordering a bag of chips from the new Website. Satisfactorily provided both graphic and text descriptions.
Thoroughly created a use case that documents the event of a customer ordering a bag of chips from the new Website. Thoroughly provided both graphic and text descriptions.
7. Discuss the support operations that the internally hosted Website will require after implementation.
Weight: 10%
Did not submit or incompletely discussed the support operations that the internally hosted Website will require after implementation.
Insufficiently discussed the support operations that the internally hosted Website will require after implementation.
Partially discussed the support operations that the internally hosted Website will require after implementation.
Satisfactorily discussed the support operations that the internally hosted Website will require after implementation.
Thoroughly discussed the support operations that the internally hosted Website will require after implementation.
8. Explain how you will evaluate the performance of the new site and the success of your project.
Weight: 5%
Did not submit or incompletely explained how you will evaluate the performance of the new site and the success of your project.
Insufficiently explained how you will evaluate the performance of the new site and the success of your project.
Partially explained how you will evaluate the performance of the new site and the success of your project.
Satisfactorily explained how you will evaluate the performance of the new site and the success of your project.
Thoroughly explained how you will evaluate the performance of the new site and the success of your project.
9. Clarity and writing mechanics.
Weight: 10%
Explanation & Answer
Hello buddy. Here is the final paper. In case you have any rectifications that you would like made on the paper, feel free to communicate. Thanks😎
Running Head: SYSTEM DEVELOPMENT LIFE CYCLE
System Development Life Cycle
Name
Affiliation
SYSTEM DEVELOPMENT LIFE CYCLE
Web Architecture
System analysis and design is the process under which the development of a system
undergoes before it is launched as (Shelly, 2012) suggests. Web architecture incorporates the
planning and general design of the functional, visual and technical components of a web
application. Ideally, it is used by developers as a roadmap to how a web application or a website
is going to be developed. The following components are among the elements that are used to
design and plan an effective web architecture. For the technical component, the developer is
mandated to have requirements such as servers, storage, memory and communication interfaces.
The servers will be used as entities to host the web application such that it can be accessed
remotely. The storage is used to store information relevant to the site as well as the website
user’s information among other entities. The memory on the hand provides a platform where the
processes and temporary data handled by the website is stored. The final technical component is
the communication interface. Websites communicate with other entities such as its users in order
to complete and achieve its objectives.
The functional aspects of the web application include elements such as the type of
services offered by the website or ideally the type of processes run on the site. In the case study
under scrutiny, one of the processes that the website will run includes customers ordering
products online from the website. This acts as a service that the site offers to its customers.
Another component of the web architecture is the visual appearance; that is the user interface. A
component that is pertinent to the website owners as much as the customer accessing the site.
The user interface consists of tables, buttons, menus, colors and other important elements
needed for a website. Finally, the most important elements after all the former have been
completed is the security of the site. The latest technological trends emphasize on ensuring the
SYSTEM DEVELOPMENT LIFE CYCLE
security of a web application. Users are getting more concerned about the security of their data
and the web application is mandated to ensure that user information is secured from illegal
access. How the web application handles secure access control and transaction processing is
deemed to determine the ultimate success of the website. Thus the above components are all
important to the creation of an ideal website according to current standards.
Migration
Based on the case study in question, a website is already created, however, the challenge
comes with the migration of the site from the externally hosted solution to an internally hosted
solution. It is also imperative to note that the company’s management places emphasis on the
importance of eliminating site redundancy when migrating the site. My trajectory to finding the
solution of migrating to another host server with minimal downtime would be to build a
temporary server for starters. This is usually a costly venture however, it appears to be one of the
best solutions for minimizing the downtime of the site. As a recommendation, I would refrain
from canceling the plan from the external host solution until the migration is complete. After
creating the temporary server, I would bring down the primary server; that the external host
solution and copy the files of the site including the programs and packages held by the site to the
temporary site created.
It is also important to ensure that the database files that were in the site are not corrupted
during the transfer. Considering the fact the site is adding an additiona...
Review
Review
