Engineering Assignment: Report On “ServicePlease" Online Delivery System By ABC Pty Ltd

Question

Task: Case Study

ABC Pty Ltd is a start-up tech company based in Adelaide Australia, who are currently seeking to develop an online delivery system named “ServicePlease”. The system aims to create a convenient platform to be used by service providers, customers, and supermarkets for home delivery of groceries to customer residents. The application will be available in both forms of website and mobile app, with separate views for service providers, supermarket, and customers. ABC Pty Ltd wants to launch this system to market in the next six months and have secured an investment for this. You have been hired by ABC Pty Ltd as the Business Analyst (BA) to help them with the requirement analysis for this project.

The “ServicePlease” application should provide the service providers to register with the system. During registration service providers will be asked to complete the background checking process. Criminal history or background will be checked through National Crime Check (NCC). Right – to – work will be checked through Visa Entitlement Verification Online (VEVO), which will confirm their citizenship, residency or visa status that allows them to work in Australia. All service providers will need to provide an Australian Business number (ABN), which will be checked through ABN Lookup. Service providers also need to give proof for delivery capability by car through driving license and vehicle registration certificate. Upon successful completion of registration, the service provider will be eligible and available for grocery delivery service in “ServicePlease”.

Supermarkets can register with “ServicePlease” online delivery system. When registered, customers will be able to find the supermarket in “ServicePlease” system. Supermarkets can accept and prepare an order to be picked up by the service provider authorized by a customer. The system should enable supermarkets to rate service providers and certify as their preferred one.

To use this service, resident customers need to sign-up first. Sign up can be verified with a valid mobile phone number and an email address. Customers need to set-up the payment method using credit card, debit card or PayPal, to pay for the service when used.

While ordering, the application should enable customers to search and select a supermarket first (pickup location). Then the customer needs to authorise a service provider from the available list (certified service providers will be shown at the top of this list, then based on rating) to pick up groceries from a selected supermarket and deliver to their residence (drop-off location). Once the job is completed, payment can be made securely through the app. Customer will get email confirmation after successful completion of an order. Customers also can rate and review the service provider, as well as the supermarket.

Engineering Assignment Task Summary
This final assessment requires you to respond to the given case study used in Assessment 1 and 2, so that you can develop insights into the different facets of Requirements Analysis in agile. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:

1. A Product Roadmap for the project
2. Product Backlog of coarse granularity including Epics and User stories
3. Personas who typifies the future system end user
4. Decomposition of Epics into User stories for first release
5. Minimum Viable Product (MVP) definition for first release
6. Story Mapping for MVP - ordering User stories according to priority and sophistication
7. Story elaboration of User stories for MVP to ensure that the User story is clear, along with the acceptance criteria for the elaborated stories to ensure the ‘definition of done’.
8. A paragraph detailing the similarities and differences between ‘traditional predictive’ and ‘Agile’ requirements analysis and management.

Answer

1. Introduction
The report on engineering assignment is based on ABC Pty Ltd, a start-up company located in Adelaide, Australia. The company is currently seeking out to build an online delivery system, naming "ServicePlease". It aims to create a convenient platform for the home delivery of groceries to the customer residents. The online delivery system process can be used by the customers, service providers or supermarkets. The project also explains their system launching to the market in the next six months, for which the company have already secured an investment. The researcher is going to work as a business analyst to meet the requirements of this project. The report includes the requirement engineering details. This is the reason for which various digital technologies are going to be included to build this project. The entire project is going to be managed and developed by using the agile and traditional methodology. Several charts are going to be included in this report to justify the requirements.

2. A Product Roadmap
The website and mobile application "ServicePlease" online delivery system of ABC Pty Ltd will help the supermarkets deliver groceries to the resident customers. The system will be a convenient platform for the customers, supermarkets, and service providers, which will engage the service providers with the supermarkets and customers to ensure better communication and home delivery services. The system creates efficiency in managing proper user interactions (Rupere, &Jakovljevic, 2021). "ServicePlease '' will ensure registration of the users through checking the background history of the service providers. The customers and the supermarkets will also have to log in to the system using proper credentials. The system will verify the driving license and vehicle registration certificate. Acceptance and preparation of orders for the supermarkets will be managed through the system. The payment method will help the customers to pay for their orders. However, the application will also enable the customers to select pick-up locations, drop-off locations. Notification through email after the confirmation of the order will also be generated through the system. Rating and reviews can also be provided to the supermarkets through the customer feedback process.

Product Roadmap

Figure 1: Product Roadmap

Source : (Developed by the author)

3. Product Backlog - Epic and User Stories
The product backlog and user stories help to assume the outcomes of the system, which may help satisfy the needs of the end-users (Rødseth, &Schjølberg, 2017).

Website and mobile application

Table 1: Epic and User Stories

Source : (Developed by the author)

The website and mobile application features will help the users create a proper interaction with the system. The user stories related to each task will help ensure the effective operation of the "ServicePlease" online home delivery system. The registration, login, and verification processes will help the users to input their correct details and credentials so that the system can ensure proper functionality. The supermarkets will be able to accept, confirm and cancel the orders as per the availability of the groceries. Through order pick-up and drop-off, the customers will be able to select the supermarkets to ensure their order. The service providers will be engaged in managing the services by delivering the orders to the resident customers.

4. Persona typifying the future system end-user
The project manager will engage in creating proper project delivery through developing the system for ABC Pty Ltd. Project manager has the responsibility to ensure product delivery to the end-user (Hoxha, & McMahan, 2018). The project manager will be engaged in giving proper direction to the employees of ABC Pty Ltd for the development of the "service please" online home delivery system. The service providers will also be engaged in managing the services of order delivery through operating the system. It will help the service providers to ensure proper communication within supermarkets and the resident customers. The service providers will also prepare the orders on behalf of the supermarkets that are authorised by the customers. Proper delivery operations through the system will help to satisfy the end-users.

Table 2: objectives and criteria of the target group

Source : (Developed by the author)

5. Decomposition of Epics into User Stories for the first release

Table 3: Epic, user stories, and task

Source : (Developed by the author)

User story 1: The registration process within the system will help the users, such as customers and service providers, to provide their basic details to register themselves within the "ServicePlease" home delivery system.

User story 2: The login process will help the users to enlist their credentials for secure login. Security within the system can be ensured through generating passwords (Booker, 2017).

User story 3: Order acceptance and confirmation will be managed through the supermarkets, which will help them to deliver good services to the customers.

User story 4: Order placement through the "ServicePlease" online home delivery system will enable the customers to place their orders. However, the payment option will help the customers to ensure payment to the supermarkets.

6. Minimum Viable Product (MVP) definition for first release 200
The MVP will address the minimum features which the "ServicePlease" home delivery system will have. The requirements of the system help to ensure proper services to the users (Naumchev, & Meyer, 2017). The specifications such as login, registration, order placement, order acceptance, order confirmation, and payment can be considered minimum viable products. The minimum viable features of the products will help the "ServicePlease" home delivery system to operate correctly for the end-users. The features will help the users to interact with the system. MPV determines the system's efficiency to ensure the proper delivery of the products to the resident customers. The features of MPV are,

• Registration process
• Log in through credentials
• Order placement by the resident customers
• Order acceptance
• Order confirmation by the supermarkets
• Search bar for products
• Payment options for customers
• Notification to the users regarding payment

7. Story Mapping for MVP
Priority 1

• The business analyst wants to log into the system to access all the functionalities and features of the online system.
• The business analyst wants to register on the system to post all the grocery details and other facilities.
• The business analyst wants to add the feature of the National Crime Check to check the criminal history of the service provider.
• The customer wants to register through the mobile application to create their profile to get various discounts for purchasing groceries.
• The service providers will be asked to complete the background checking process.

Priority 2

• The business analyst wants to add new features to the system so that customers can purchase the products easily.
• The business analyst wants to add various products so that the customers can select the items of their own choice.
• The customer wants to search for the products based on their requirements.
• The service providers need to add their Australian Business number, which is going to be checked through the ABN Lookup.

Priority 3

• The business analyst wants to add the filter system based on the price and quantity of the grocery item.
• The business analyst wants to add the online payment system to make no-contact delivery.
• The service providers need to give legal documents of their capability in delivering the products by car.
• The business analyst wants to modify the details of each product so that the customers can purchase the items easily.
• The business analyst wants to add the facility of replying to the feedbacks of customers so that they can give them a better facility.

8. Elaboration of stories for MVP to ensure the user story is clear

Table 4: Elaboration of the User Stories

(Source: Developed by the author)

9. Acceptance Criteria for elaborated stories to ensure the 'definition of done.'

Table 5: Acceptance criteria

(Source: Developed by the author)

10. Similarities and differences between 'traditional predictive' and 'Agile' requirements

Similarities
Expression of the business need
The company needs to meet the business needs to develop a sound quality system or product. The business analyst needs to focus on the business vision and the objectives of establishing the project. It is also essential to figure out the requirements so that the target of the project should be easily achieved.

Methodologies need to be testable.
A testable requirement needs to be broken down for a level through which the inspection and analysation can be precise. Both the methodologies need to be testable to meet the requirements.

Differences

Table 6: Difference between Traditional and Agile methodology

(Source: Developed by the author)

11. Conclusion
It can be argued that user stories have been one of the most critical topics required to accomplish the project. Four user stories have been mentioned as per the case study. The details have been elaborated the stories properly to meet the requirements in building the online grocery delivery system. ABC Pvt. Ltd has taken legal requirements to verify the background and criteria of the candidates. The acceptance criteria are also included to understand that criteria are also considered an essential process to implement the online delivery system.

References
Booker, B. (2017). Password know-how equals online security. Philadelphia Tribune, 2b, 2.https://lesa.on.worldcat.org/v2/oclc/7129296424

Duong-Trung, N. (2017). Agile methodology for design and implementation of databases and websites for sales and administration of computer hardware.CuvillierVerlag. https://lesa.on.worldcat.org/v2/oclc/1003262866

Hoxha, L., & McMahan, C. (2018). Does a project manager's work experience help project success? International Journal of Construction Project Management, 10(2), 155–172.https://lesa.on.worldcat.org/v2/oclc/8205121976

Naumchev, A., & Meyer, B. (2017).Seamless requirements. Engineering assignment Computer Languages, Systems & Structures, 49, 119–132. https://lesa.on.worldcat.org/v2/oclc/7072655717

Rødseth, H., &Schjølberg, P. (2017).Maintenance backlog for improving integrated planning. Journal of Quality in Maintenance Engineering, 23(2), 195–225. https://lesa.on.worldcat.org/v2/oclc/7029823574

Rupere, T., &Jakovljevic, M. (2021).Usability and user evaluation of an integrated multimedia e-learning management system. Knowledge Management & E-Learning, 13(3), 334–366.https://lesa.on.worldcat.org/v2/oclc/9322725659