ISEM570 Homework 2 Service Design For This Assignment

ISEM570 Homework 2 Service Designfor This Assignment Use The Itil V3

Use The ITIL V3 Official Introduction pdf found in Module 1 Materials folder. 1. What is the main purpose of Service Design restated from the text, in your own words? a. The main purpose of the Service Design stage of the lifecycle is the design of new or changed service for introduction into the live environment. It is important that a holistic approach to all aspects of design is adopted and that when changing or amending any of the individual elements of design all other aspects are considered. Thus, when designing and developing a new application, this shouldn’t be done in isolation, but should also consider the impact on the overall service, the management systems and tools (e.g. the Service Portfolio and Catalogue), the architectures, the technology, the Service Management processes and the necessary measurements and metrics. 2. Name at least 3 Business Values from Service Design. a. Reduced total cost of ownership b. Improved quality of service c. Improved consistency of service d. Easier implementation of new or changed services e. Improved service alignment f. More effective service performance. 3. Identify at least three design process activities and explain. a. Requirements collection, analysis and engineering to ensure that business requirements are clearly documented and agreed b. Design of appropriate services, technology, processes, information and process measurements to meet business requirements c. Review and revision of all processes and documents involved in Service Design, including designs, plans, architectures and policies Liaison with all other design and planning activities and roles, e.g. solution design d. Production and maintenance of IT policies and design documents, including designs, plans, architectures and policies e. Revision of all design documents and planning for the deployment and implementation of IT strategies using roadmaps, programs and project plans f. Risk assessment and management of all design processes and deliverables g. Ensuring alignment with all corporate and IT strategies and policies. ISEM570 Homework #2 Service Design 4. A Service Catalog should include these activities (list at least two): a. Definition of the service b. Production and maintenance of an accurate Service Catalogue c. Interfaces, dependencies and consistency between the Service Catalogue and Service Portfolio d. Interfaces and dependencies between all services and supporting services within the Service Catalogue and the CMS e. Interfaces and dependencies between all services, and supporting components and Configuration Items (CIs) within the Service Catalogue and the CMS 5. The objectives of Service Level management are (list 2 and explain using external scholarly references or case studies. Note your references on a separate page at the end.): a. Define, document, agree, monitor, measure, report and review the level of IT services provided b. Provide and improve the relationship and communication with the business and customers c. Ensure that specific and measurable targets are developed for all IT services d. Monitor and improve customer satisfaction with the quality of service delivered e. Ensure that IT and the customers have a clear and unambiguous expectation of the level of service to be delivered f. Ensure that proactive measures to improve the levels of service delivered are implemented wherever it is cost-justifiable to do so. 6. List three key activities within the SLM process should include. Explain using external scholarly references or case studies. Note your references on a the references page at the end): a. Determine, negotiate, document and agree requirements for new or changed services in SLRs, and manage and review them through the Service Lifecycle into SLAs for operational services b. Monitor and measure service performance achievements of all operational services against targets within SLAs c. Collate, measure and improve customer satisfaction d. Produce service reports e. Conduct service review and instigate improvements within an overall Service Improvement Program/Plan (SIP) f. Review and revise SLAs, service scope OLAs, contracts and any other underpinning agreements ISEM570 Homework #2 Service Design g. Develop and document contacts and relationships with the business, customers and stakeholders h. Develop, maintain and operate procedures for logging, actioning and resolving all complaints, and for logging and distributing compliments i. Log and manage all complaints and compliments j. Provide the appropriate management information to aid performance management and demonstrate service achievement k. Make available and maintain up-to-date SLM document templates and standards. Points: 200 Term Paper: Website Migration Project Criteria Unacceptable Below 60% F Meets Minimum Expectations 60-69% D Fair 70-79% C Proficient 80-89% B Exemplary 90-100% A 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% More than 8 errors present 7-8 errors present 5-6 errors present 3-4 errors present 0-2 errors present

Paper For Above instruction

Building a Web architecture that ensures minimal downtime and robust disaster recovery capabilities is essential for maintaining high availability of a website, especially in today's digital environment where user expectations for continuous access are high. This process involves careful planning, selection of appropriate technologies, and implementation of strategies to mitigate potential failures, all while ensuring a seamless transition during migration with minimal service interruptions.

To achieve this, a layered Web architecture should be designed using scalable and reliable operating systems such as Linux or Windows Server. Linux, particularly distributions like Ubuntu Server or CentOS, is favored for its stability, security, and open-source flexibility, making it suitable for hosting mission-critical websites (Sharma & Soni, 2022). Windows Server, on the other hand, offers deep integration with Microsoft technologies, which can be advantageous for sites that rely heavily on Microsoft-based applications (Khan et al., 2021). The choice between these systems depends on the existing infrastructure, application requirements, and organizational preferences, but both can be configured for high availability and disaster recovery.

Building a web architecture entails deploying load balancers, redundant servers, and a secure network design. Load balancers like HAProxy or F5 balance incoming traffic across multiple servers, ensuring no single server becomes a bottleneck. Redundant web servers—configured in active-passive or active-active modes—provide failover capabilities, so that if one server goes down, others continue to serve requests seamlessly. Data storage should utilize RAID configurations and regular backups to prevent data loss, alongside geographically dispersed disaster recovery sites (Rimal et al., 2020). Cloud-based hybrid solutions, such as AWS or Azure, offer flexibility with auto-scaling, elastic load balancing, and automated backups, providing further robustness.

Minimizing downtime during migration also requires meticulous planning. A phased migration approach is recommended, where the new architecture is tested thoroughly in parallel with the old system before switching over. This includes DNS updates, which should be coordinated carefully, and synchronization of databases to prevent data inconsistency. Techniques such as blue-green deployment or rolling updates help ensure that during the cutover, service disruptions are minimized (Chen & Zhang, 2019). Monitoring tools like Nagios or Zabbix should be employed to provide real-time insights and alerts, enabling quick response to any issues.

Disaster recovery (DR) planning is critical to guarantee site availability. A comprehensive DR plan involves establishing recovery point objectives (RPO) and recovery time objectives (RTO), creating off-site backups, and automating failover processes. Regular disaster recovery testing validates the effectiveness of the plan and readiness of the infrastructure (Alharkan et al., 2020). Cloud-native DR strategies, such as replicating data across multiple regions, further enhance resilience by allowing rapid failover in case of regional failures.

In conclusion, building a web architecture capable of minimal downtime, seamless migration, and robust disaster recovery requires a combination of strategic planning, appropriate technology selection, and continuous monitoring. Operating system choices like Linux and Windows Server each offer advantages adaptable to organizational needs, with considerations for stability, security, and integration. Employing load balancing, redundancy, and cloud solutions enhances resilience, while phased migration techniques and thorough testing ensure service continuity. Finally, a comprehensive disaster recovery plan embedded within the architecture ensures the website remains available regardless of failures, maintaining trust and satisfaction of users.

References

• Alharkan, I., et al. (2020). Disaster Recovery Planning in Cloud Computing: A Systematic Review. Journal of Cloud Computing, 9(1), 22.
• Chen, L., & Zhang, W. (2019). Strategies for Zero Downtime Deployment in Web Applications. International Journal of Computer Networks & Communications, 11(3), 45-54.
• Khan, R., et al. (2021). High Availability and Disaster Recovery in Windows Server Environments. Journal of Information Technology, 36(2), 165-177.
• Rimal, B., et al. (2020). Cloud-Based Disaster Recovery Solutions: Framework and Challenges. IEEE Cloud Computing, 7(1), 87-95.
• Sharma, V., & Soni, J. (2022). Linux Server Deployment and Management. Journal of Systems and Software, 189, 110399.