Need help with your Assignment?

Get a timely done, PLAGIARISM-FREE paper
from our highly-qualified writers!

Webstore Implementation and Maintenance Plan

Webstore Implementation and Maintenance Plan

Recommended Strategy for Phases of Implementation


Module integration in software development is done after successful integration testing (Noortaj, 2019). It is good practice to develop different modules independently and then integrate them. This enables software developers to focus on the function of each module before integrating them into one system. For example, the Healthy Harvest Online Store App would have several modules. These would include a login module, a cart module, a payment module, etcetera. Each module would be developed separately and tested before being integrated as one application. This would ensure that the modules work as expected and that there would be no errors and bugs introduced into the app after integration. Also, debugging modules independently is easier and faster than debugging an already integrated system. Another aspect of integration in the Healthy Harvest Online Store App would be when the app is connected to an external system. For example, the app could be integrated with an online payment platform that allows customers to make electronic payments for the groceries they order. Integration of the app with an external system would only be done after the app is tested and approved for live operations. Do you need urgent assignment help ? Get in touch with us at We endeavor to provide you with excellent service.


Testing of the Healthy Harvest Online Store App would be done based on the various available testing options. For example, after testing the different modules and debugging accordingly, some types of tests could still be done. These include performance testing, security testing, stress testing, and user acceptance testing (Noortaj, 2019). Performance testing is done on the finished product to ensure that it works as expected in terms of speed, responsiveness, and stability. Security testing would include testing security features such as access control. For example, the app should only allow authorized users to order online. This would be achieved by creating an account with a username and password. Stress testing would check the app’s robustness to ensure that it does not crash when using it. User acceptance testing would be done by users to ensure that it is user-friendly and meets the needs of the users.


Verification checks whether the app performs as intended (Noortaj, 2019). For example, in the Healthy Harvest Online Store App, verification would include checking whether a customer can create an account and allow the changing of passwords. It could also check whether the customer can order groceries and if the correct prices are provided. On the backend, it could check whether any added goods are displayed online in real-time. Such processes must work for the app to be considered efficient. For instance, if the app does not accurately compute the total of ordered goods, it would inconvenience the store and the customers. For that reason, the verification step is important before launching the app on a live platform. Verification would be done on individual modules and the system after integration.

Documentation Requirements  

Systems Operation Documentation (Document how the system should be used):

This type of documentation describes the operations that the software handles (Chomal & Saini, 2014). For example, the Healthy Harvest Online Store App would have documentation that describes the operations that are executed on the system. This would include how a customer would create an account and make online purchases. For the employees at the store, the documentation would include the different user roles and what the users can do. An authorized employee would be able to make changes on the App display, such as price changes, including discounts. The store owner or employee in charge of sales would be able to access reports on sales made, payments received, etcetera. This kind of information would guide the system administrator on how to assign user roles. It would also be useful in providing user training for new employees. A user manual or demo for customers can be created and made available on the front end of the app from the system operations documentation.

Systems Training (Explain what types of training are needed and how it can be structured):

The Healthy Harvest Online Store App would require two types of training. The pieces of training include user training and technical training (Noortaj, 2019). User training would be done before user acceptance testing. This would enable users to provide objective feedback after they have interacted with the system. For instance, before a user knows what to do so that they can order some groceries, he could rate the app as difficult to use. Therefore, with user guides and demos for training, a user would know how to order on the app; hence, the feedback would be on functionality. Technical training would be for employees who will be providing user support and manual updates such as pricing or additional photos. Therefore, technical training would be essential in ensuring that app operations continue as expected. This would ensure that business operations are efficient and that customers are not inconvenienced.

User Support (Outline user support needs and strategy):

User support for the Healthy Harvest Online Store App would begin with making product documentation available online (Chomal & Saini, 2014). This would provide basic user support for customers without calling the store or the email system administrator. Customers would be able to quickly check on what the problem they are experiencing is about. For example, if the customer’s smart device does not have an internet connection or the connection is unstable, the error that appears would be documented on the user support documentation page that would describe the error in detail. The customer would ensure they have a good internet connection and try to access the app again. That would be time-saving compared to if there was no documentation and the customer had to resolve the problem on their own or make a call to the grocery store. The other type of user support would be to provide a chat option on the app where customers can chat with user support staff.

Maintenance Recommendations  

Alternative Organizational Structures:

Maintenance for the online store App would be coordinated based on the available alternative organizational structures depending on the type of maintenance. The available structures include central or hierarchical, project, and departmental (Raziq et al., 2020). This could also be described as horizontal, vertical, or both. Maintenance that includes major changes to the app requires senior management authorization while periodical maintenance could be authorized by departmental or project heads. For instance, patching the app is periodic maintenance that is critical for software security; therefore, it should be authorized by the department head. Adding features to the app would require authorization from senior management through the department head because this would make major changes to the app compared to a patch update.

Quality Measurement (Explain how the system should run optimally and what quality measurements should be used to determine its performance):

Quality measurements used to check the grocery’s app include usability, compatibility, security, maintainability, performance efficiency, and portability (López et al., 2022). The app would be user-friendly and usable on different platforms. Access controls would be checked to ensure that authentication processes are efficient, data confidentiality, availability, and integrity. In addition, the app should be easy to modify by authorized technical persons when needed. The app should have speed and accuracy for its operations on performance efficiency. Users should be able to install the online store App on their smartphones. This would describe portability, where the app is optimized so that it remains light and easy to download and install.

Change Request Processes (How should system changes and updates be communicated?):

As the Healthy Harvest store expands, there will be a need for some app processes to be changed. This could be on the backend, frontend, or both. Therefore, it would be essential for the store to define how the changes would be effected. Best practices require that a document requesting the process changes is prepared (Nordin & Suhailan, 2012). This is important as it acts as a reference in the future. Based on the type of process to be changed, the petitioner would be required to write the process(es) and request approval. If it is a major change, it would require taking the document to the immediate manager, who would forward it to the senior management for approval.

Configuration Management (How should configuration management be handled?):

Configuration management controls the change of code to ensure that there is consistency and that quality is maintained (Estublier, 2015). This is achieved through monitoring change requests. For example, at the Healthy Harvest store, the App development and maintenance would be guided to ensure that configuration remains as per the requirements. If need be, the petitioner for change would be required to prepare a document detailing the changes required. Once the changes have been approved, the configuration should be effected and documented for future reference. Subsequently, this would eliminate confusion when a technical team is looking at the app’s configuration in the future. Besides, it would ensure that only necessary configurations are made.


Chomal, V. S., & Saini, J. R. (2014). Significance of Software Documentation in Software Development Process. International Journal of Engineering Innovation & Research3(4), 410-416.

Estublier, J. (2015). Software Configuration Management a Road Map [Doctoral dissertation].

López, L., Burgués, X., Martínez-Fernández, S., Vollmer, A. M., Behutiye, W., Karhapää, P., Franch, X., Rodríguez, P., & Oivo, M. (2022). Quality measurement in agile and rapid software development: A systematic mapping. The Journal of Systems & Software186(2022), 1-26.;jsessionid=8427AF4AC1414D5640875145C13C4450?sequence=3

Noortaj, N. (2019). Testing in the Software Development Life Cycle and its Importance. International Journal of Engineering and Information Systems3(9), 15-20.

Nordin, A. M., & Suhailan, S. (2012). Managing Software Change Request Process: Temporal Data Approach. International Journal of Computer Science and Security3(3), 201-209.

Raziq, M. M., Ahmad, M., Iqbal, M. Z., Ikramullah, M., & David, M. (2020). Organizational Structure and Project Success: The Mediating Role of Knowledge Sharing. Journal of Information & Knowledge Management, 1-34.


We’ll write everything from scratch


Joan’s team at Healthy Harvest is ready to review how to implement and maintain the new online store app.

Use the Healthy Harvest Implementation and Maintenance Plan Template to prepare a 5- to 6-page documentation for implementation and maintenance activities for the new Healthy Harvest app.

Webstore Implementation and Maintenance Plan

Webstore Implementation and Maintenance Plan

The template includes sections for you to document the following information:

Recommend an implementation strategy for the app, including testing and verification processes. Support your recommendation by explaining the advantages of the process.
Outline the documentation requirements, which include instructions on using the system and training and supporting users.
Outline the maintenance needs of the store app. Include:
Alternative organizational structures
Quality measurement
Change request processes
Configuration management

Cite any references to support your assignment.

Format your citations according to APA guidelines.

Submit your assignment.

Order Solution Now