Agile Software Development Lifecycle For VFUS System Project Essay.

The development of VFUS system for the organisation would be done through the agile methodology. The lifecycle of the agile software development could be considered as the structured sequence of the steps which are underwent by the products as it would move from the initiating point to the end point. The VFUS system project would include six main phases:

Requirements: The stakeholders would conduct the proper project assessment for determining the overall resources and time needed for process of development. The stakeholders of VFUS system would be consulted in this stage and the requirements would be gathered (Beerbaum, 2021).

Design: In this phase, the idea of the project would be proposed. After the project has been decided, now the next step would include the development of the team of software development. The product owner would be required to properly verify the availability of the colleagues as well as select the best possible people for this project while providing them with required resources and the tools (Malik, Ahmad & Hussain, 2019).

Development and coding: After gaining confirmation from the stakeholders, the team would start developing the VFUS system (Sun & Schmidt, 2018). The entire system would be completed in proper stages, in distinct sprints, and each would be designed for improving the present version of organisation. Any initial release is probable to undergo several changes for providing the enhanced functionality as well as the innovative features (Hayat et al., 2019).

Integration as well as testing: After the development plus coding would be completed, VFUS system would be made available for customers, and therefore the project team would be required to complete the series of tests for ensuring that software would be completely functional (Abdelghany, Darwish & Hefni, 2019). If any potential bugs or even the flaws are discovered, then developers would implement the fixes immediately. In this particular stage, the consumer feedback would also be gathered.

Implementation plus deployment: The VFUS system would be completely functional after completing the integration and testing and now it would be made available for using to the customers (Ribeiro & Domingues, 2018). This action would put the project in the maintenance stage. In this stage, the team of software development would provide the ongoing support for keeping VFUS system properly running as well as fix any emerging bugs. Over passing time, the additional iterations would be made possible for updating any existing product or even add any other functionality (Shakya & Shakya, 2020).

Review: This stage could be considered as the last phase of the development of the VFUS system. After the completion of all the stages of the development, development team would present the owner with the result that is being achieved in the meeting of requirement (ur Rehman et al., 2018). After completing this phase, the phases of the Agile software development would initiate again, with the new iteration or even moving to next stage plus scaling the agile methodology (Venkatesh, & Rakhra, 2020).

The two requirement gathering methods that could be used for determining the requirements of the stakeholders are interview and survey. If the interview method is selected, it would be ensured that proper interview is conducted with all the stakeholders of the organisation for gaining their personal thoughts on the system and then develop a proper set of requirements. If the survey method is selected, then the stakeholders would be provided with a set of questions that should be answered by them. After gaining all the responses from the stakeholders, a set of proper requirements would be developed for the new VFUS system.

• Epic 1: As a local shop owner, I want to use of the VFUS system for sending a list of products with details so that my products would be provided to the customers.
  • User stories 1: As a local shop owner, I want to use the system for seeing details that I entered during registration.
  • User stories 2: As a local shop owner, I want to use the system for checking products that I have listed for placing a request of modifications to VFUS admin.
  • User stories 3: As a local shop owner, I want to use the system for changing quantity of products that I could offer.
  • User stories 4: As a local shop owner, I want to use the system for editing names of products that I have listed.
  • User stories 5: As a local shop owner, I want to use the system for checking my email to check incoming mail of confirmation.
• Epic 2: As a delivery person, I want to use of the VFUS system for changing the status of my delivery so that I could confirm completion of delivery.
• User stories 1: As a delivery person, I want to use the VFUS system for checking the delivery address of my next delivery.
• User stories 2: As a delivery person, I want to use the VFUS system for entering my attendance so that I will be made available for making deliveries.
• User stories 3: As a delivery person, I want to use the VFUS system for checking the customer details for whom the delivery is being made so that correct delivery would be done.
• User stories 4: As a delivery person, I want to use the VFUS system for selecting the delivery that I am making so that I could update the delivery status.
• User stories 5: As a delivery person, I want to use the VFUS system for confirming the completion of delivery by clicking Finish on the system.

• System should allow the farmers to register in the system by providing all their personal details in the registration form.
• System should allow the local shops to update the quantity on hand of the products that are listed in the organisation
• System should allow the VFU admin to create a product listing with all the products
• System should allow the delivery person to change the status of any delivery for providing confirmation of the delivery.
• System should allow the customers to create their respective veggie box for week.

Design

Availability: The system should be made available 24x7 for all the various actors to complete their respective tasks on the system and gain confirmation of the completion of tasks. The only limitation of this requirement is that the payment module would not be available from 10 pm to 4am.

Security: The system should possess security protocols for preventing any unauthorised access in the database. The system should not allow any user to change the content on the website other than what has been allowed. The two-factor authentication should be implemented in the system for admins so that additional layer of security is ensured.

Usability: The system should allow all types of users to complete their tasks on the system. The VFUS system should be usable for users of various groups.

Scalability: The system should possess the ability of scaling the capacity on its own for accommodating the increased customers and users. It should allow the customers to make proper booking of veggie box easily. The limitation of this requirement is that it would mean additional storage space in the organisational database and it would incur additional costs.

Efficiency: The system should return the request of any query within 5 seconds and also provide the notification of any unavailable resources on the system. The limitation of this requirement is that during updating the system, the system would not be able to allow users to complete their tasks.

From the above provided final use case diagram of VFUS system, it could be observed that the additional actor being introduced is VFU manager. The VFU manager is vital part of the operations of the organisation because the farmers registration would only be completed by the VFU manager. They would ensure proper working of the business and proper availability of all the services.

References

Abdelghany, A. S., Darwish, N. R., & Hefni, H. A. (2019). An agile methodology for ontology development. International Journal of Intelligent Engineering and Systems, 12(2), 170-181.

Beerbaum, D. (2021). Applying Agile Methodology to regulatory compliance projects in the financial industry: A case study research. Applying Agile Methodology to Regulatory Compliance Projects in the Financial Industry: A Case Study Research (April 26, 2021).

Hayat, F., Rehman, A. U., Arif, K. S., Wahab, K., & Abbas, M. (2019, July). The influence of agile methodology (Scrum) on software project management. In 2019 20th IEEE/ACIS International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD) (pp. 145-149). IEEE.

Malik, R. S., Ahmad, S. S., & Hussain, M. T. H. (2019, March). A review of agile methodology in IT projects. In Proceedings of 2nd International Conference on Advanced Computing and Software Engineering (ICACSE).

Ribeiro, A., & Domingues, L. (2018). Acceptance of an agile methodology in the public sector. Procedia computer science, 138, 621-629.

Shakya, P., & Shakya, S. (2020). Critical success factor of agile methodology in software industry of nepal. Journal of Information Technology, 2(03), 135-143.

Sun, W., & Schmidt, C. (2018). Practitioners’ agile-methodology use and job perceptions. IEEE Software, 35(2), 52-61.

ur Rehman, F., Maqbool, B., Riaz, M. Q., Qamar, U., & Abbas, M. (2018, April). Scrum software maintenance model: Efficient software maintenance in agile methodology. In 2018 21st Saudi computer society national computer conference (NCC) (pp. 1-5). IEEE.

Venkatesh, D., & Rakhra, M. (2020). Agile adoption issues in large scale organizations: A review. Materials Today: Proceedings.