Webstore Implementation Strategies and Its Maintenance Plan

Webstore Implementation Strategies and Its Maintenance Plan

 

System implementation is one of the most important phases in the process of developing a useful system that ensures that the web store is fully functional at the end of the day. Implementation involves building a system from scratch or building a new system from an existing system. Some of the tasks involved in implementing the system include coding, testing, installation, documentation, training, and support. Coding itself involves converting physical design specifications into executable computer code. Testing, on the other hand, is done by using various strategies to verify and validate the implemented product. With testing, the development team can either run it with the coding or wait until the coding is complete. After testing, the next step is installation, which includes the process and strategy involved in replacing the old system with the new system. In software development, critical phases such as implementation, which involve multiple activities, must be properly planned to avoid the risk of wasting time or resources.

Finally, there is a maintenance plan that can be defined as an end-to-end process that not only identifies but also proactively resolves incidents. Identifying the equipment and components necessary for the system to function optimally and ensuring that everything works as planned. Information system maintenance planning focuses on four main tasks: receiving maintenance requests, converting such requests into required changes, designing the changes, and finally implementing those changes. Pine Valley Furniture’s web store implementation plan and maintenance schedule is quite unique given the company’s unique processing needs. Since the final decision on the details of the implementation and maintenance of the PVF web store rests with the board, it should review the existing plans and thus eliminate some of the necessary, while also important, issues. corporate business strategy.

Review the plan

Usually, businesses that want to get involved in e-commerce do so in the marketplace first and then consider the option of developing their own web store. This decision makes a lot of sense given the amount of initial work involved in developing an independent web store. In addition, the broad base of ready customers, various payment options, fully developed shipping infrastructure and many other advantages make an independent web store from scratch always a business to the market. However, PVF decided to opt for the latter, citing reasons specific to its business model. Based on this, the plan that has been developed and maintained for the company’s web store is fully public and summarized by the directors to address the specific business strategy of the company. Below are some suggestions for a review plan.

Suggestions

Considering the performance and maintenance of the project product, the board decided on the installation strategy that best suits the newly designed website, ensuring that the chosen strategy is justified over others. Comparing strategies is an important task because the implementation of new products and maintenance provides a comprehensive understanding of what each strategy can offer, especially given the uniqueness of the corporate environment. There are several documentation, user training, and support sections that should be included in other proposal issues that you may want to look for. Also important are test plans, alternative organizational structures, quality measurement methodologies, as well as request handling and configuration management processes.

 

Installation strategy

System setup refers to the configuration of software or hardware with the goal of preparing it for execution. In general, there are four types of installation strategies that have been used for a long time. These strategies include direct deployment, single-site deployment, parallel deployment, and phased deployment. Direct installation involves switching from the old dispensation to the new one, immediately destroying the old system. The new system began to work (Phogat & Gupta, 2017). By contrast, a nearly parallel installation involves the old system being used alongside the new system until management deems it prudent to shut it down. A co-located installation strategy, on the other hand, involves testing information systems at different sites rather than relying on the same site’s expertise to install the rest of the organization’s sites. This strategy is also called test setup. The last strategy on the card is phased installation, where the old system to the new dispensation gradually moves from one or more functional parts of the system to the remaining parts until the entire system is fully built.

Parallel strategy and justification

In PVF, the board recommends using a parallel assembly strategy. The panel went through four networking strategies, weighing the advantages and disadvantages of each parallel deployment strategy for the rest. This is the only strategy that has been allowed for contingency measures that have been determined by the Council. When performing the installation of a new system, be careful not to let critical systems run on the old system for reliability reasons (Lau, 2019). The installation process must be thought out independently, to avoid the risk of mistakes at the beginning of the operation. To ensure this, the board has put forward some ideas on key elements such as data conversion, which focuses on things like debugging and uploading from legacy systems. The board also focused on closing the complex planning system of the PVF business cycle.

 

Advantages and disadvantages

A comparison of strengths and weaknesses among the four building strategies further confirmed the board’s decision. The direct installation strategy has the advantage of speed, but it does not provide the precision required by a large system for the PVF web store. On the other hand, the test setup strategy has the same advantages as the parallel setup strategy. However, it creates a lot of problems with data manipulation because it opens the door for other vulnerabilities in the system. The strategy divides the system into different modules, then configures each module independently, thus increasing the possibility of errors (Lau, 2019). The only problem with the parallel installation strategy is the high cost associated with its implementation, given the number of human resources required to monitor the operation of the two systems.

document

The Board of Directors also decides on documents related to the entry into force of two types of documents. There are two types of system documentation and user documentation.

System documentation

Of interest to the board, the system document details the design, specifications, internals, and functionality of the system. This document is prepared by the development team and covers every detail of the critical stages of development, from the discovery and analysis of requirements to the final stage. System documentation aims to help programmers and analysts understand and maintain the web store after it is built. Unlike user documentation, system documentation is a security document that cannot be trusted by random people or published publicly. Includes system source code and other integrated system components.

User documentation

The Board also recommends the development of user documentation known as user manuals. Documentation is used to help system users understand how the system works. User documentation is available in various forms, namely; procedure manual, reference document and training manual. This type of documentation focuses primarily on system usage rather than overall system functionality. The PVF company will publish user documentation on its website to improve access to users.

User support and training

System users are critical components that greatly affect the success of the system. The PVF Board of Directors has been wise to detail recommendations for training and user support. Support mainly includes ongoing educational support, as well as diagnostic skills and troubleshooting support for information system users (Będkowski et al., 2017). Given that the web store system for the company is developed in-house, the supporting materials and related work must be designed in-house. There is nothing unique about doing this, as developers who develop in-house often avoid situations that might lead them to seek outside tools for support. It is also recommended that company leaders take advantage of the necessary computing infrastructure that will see the successful implementation of all the resources required to carry out the first user operations. Some of these devices may include network devices, computers, firewalls, and others.

When it comes to user training, there are some specific topics that must be addressed regardless of the system’s purpose. This topic includes; system use, basic concepts of information systems, general computing concepts, organizational concepts, system construction and management, etc. are considered necessary. Electronic Productivity System Support System (EPSS) is another software domain that includes knowledge base software (Będkowski et al., 2017). EPSS can take many forms, such as text, expert system shells, or hypertext jumps to reference material. While the council agreed that providing support and training to users of the system was vital and that it could not be overlooked, the council knew that providing such a thing could often be an expensive affair. Everything is up to the help desk. In this case, the board recommends automating the support process to make it cheaper. Some ways to automate the support process include adopting Internet-based online support forums, using language knowledge or even voice response systems.

 

Test schedule

The trial plan shall include the scope, access to resources, and schedule of scheduled activities as recommended by the board. The scope of the test includes all the modules that make up the web store, on the other hand, the resources include the technical expertise provided by the system tester and all the documentation necessary to detail the requirements (Ravitch, 2016). The board has recommended a four-day trial period, in which three fast days should be spent testing various parts of the webshop system. The fourth day will be devoted to the integrated test, which will determine the day of submission of results.

Alternative organizational structure

Since the primary structure is a newly created web store that gives full control of all business functions to PVF, the board feels it is prudent to introduce an alternative structure for this organization. This alternative structure envisages a transition to a market with core processes compatible with PVF. The main motivation for having an alternative structure is the need to increase flexibility when changing tasks. However, PVF’s control over its core business will be reduced.

A measure of quality

PVF Web Store is a web-based business model, the quality of the system will focus on three main issues; navigation quality, search engine quality and expert search quality. All of these things will be measured by issues such as how quickly the user can find the information they want, if it matches what the user is looking for.