Engineering Assignment: Requirements Documentation & Lifestyle Management Report For ABC pty ltd

Question

Task: Task Summary
This engineering assignment requires you as a group to write a requirements document and lifecycle management report in response to a case study. The report should focus on the following two areas:

a) Requirements Documentation
b) Requirements Lifecycle Management
Context
The focus of previous assignment was on the elicitation of requirements. In this second assessment, you will come together as a team and progress to the next step in the requirements process: requirements analysis & documentation, and requirements lifecycle management. Here you will focus on specifying, modelling, verifying and validating requirements using Business Analysis best practice after which you will focus on Requirements Lifecycle Management. This assessment aims to assist you in developing workplace relevant business analysis skills in a predictive planning context.

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.

Answer

Introduction:
The following engineering assignmentis regarding the case study of ABC pty ltd which is an Australian startup technology working on developing the online delivery system. Therefore, in the following assignment the primary focus is to develop the requirementdocumentation of the project and the requirement lifecycle management of the project which is proposed in the following case study. Therefore, to attain the following the goals and the objective of the project is taken into consideration. In addition to that, the stakeholders will be defined in the following assignment. Finally, based on the following, the requirement lifecycle has been identified where the various stages of the requirement lifecycle have been identified for the following case study.

Requirement Documentation:
Project Scope:
The primary scope of the following project for the startup technology company ABC pty ltd is that they are developing an online delivery system which would be applicable for three users that is the supermarket, customers and the service providers. The following implementation of the software is done using the website and the mobile application. The project is for the creation of a more convenient platform which would help all the three users to use the following application.

Business goals and objectives:
Goals:
The primary goal of the following project is to create a system or platform which could be used by the customers, service providers and the supermarkets in a seamless manner.
To create and develop the system within the next 6 months and also help with the requirement analysis of the project.

Objectives:

Swim lane diagram:

Figure 1: Swimlane diagram

Business requirements:
The primary business requirements for the following project are:
To complete the entire project within the next 6 months.
To form the two systems which are both website and mobile application.

Three stakeholders and their requirements:
In the following project of the ‘serviceplease’ the stakeholders of the following are playing one of the major roles when it comes to the development of the software. Therefore, there are involvement of the stakeholders in the project and hence, because of that there are both the key stakeholders for the project. Below are the three stakeholders of the project and they are:
1. Customers – They are the primary user of the system as they would be the last people who would be handling the software or the mobile application using which they would be availing the service from the supermarkets and the service providers. They are the one who would be interacting with the software or the application the most and also availing the service.
2. Supermarkets – They are the ones who would be registering with the application or the website and with the help of the following they would be placing all the service providers within them. Other than that, they would also be interacting with the application as they would be putting the service providers as per their importance.

3. Service providers – They are the ones who would be providing service to the customers with the help of the supermarket. They are also the stakeholders of the following as they would be having the access to the application or the website.
Therefore, the above three are the key stakeholders of the system and also, they are the one who needs to meet the higher-level user requirements.

Functional requirements:
Some of the functional requirements of the ‘serviceplease’ app for the following project are:
Provide the login and registration facility for the customers, service providers and the supermarkets.
Integration of the application and the website with the national crime check, VEVO and the Australian business registry.
Seamless experience for the customers to avail their service.
Seamless experience for the supermarket to handle the service providers and provide feedback.
Privacy and protection of the data of all the major stakeholders or the users of the system.

Nonfunctional requirements:
Create a user interface which would be different for the customers, service providers and the supermarket to give their own customer experience of using the app or website.
Connecting the website or the site with the Australian business registry so that the supermarket and the service providers are able to have access to the data and seamless verification process.
Having a minimal UI and readable user interface for the customers which is also making the application or the website accessible for all kinds of users.
Creating a separate UI or interface for the supermarket and the service providers so that, they are able to handle the customers and also the supermarkets are able to handle the service providers.
Having a separate server which can store the data of the customers, supermarket and the service providers and make it intrusion proof.

Requirement Lifecycle Management:
Each stage of requirements lifecycle:
The requirement lifecycle is the area which is taken into consideration, and they are the knowledge area which are describing the tasks which the business analysts are performing so that they are able to manage and also maintain the requirements of the business (Satyarthi & Pandey, 2017). This is done from the initiation phase all the up to the final implementation of the entire project. There are a total of five stages in the following requirement lifecycle which is taken into consideration, and they are known as Trace, maintain, prioritize, assess and the approval of the project.

Trace:
Description:
In the following it involves the analysis and the relationship which is maintained between the requirements of the project. Other than that, the solution for the following is also taken into consideration which would impact the overall analysis, the allocation of the project and the overall coverage (Fallah, Trautner&Pauker, 2019). Therefore, here in the following the requirements of the ABC pvt ltd would be traced with the help of which the overall project would be completed in the following part.

Objective:
The primary objective in the following is to trace the relationship between the customers, service providers and the supermarkets in the following project. Other than that, the relationship developed would be related to the requirements of the project discussed previously.

Activities:
Some of the activities which would be performed in the following are stage are:
Process modelling
Scope modelling

Output:
At the following stage the inconsistencies and the flaws would be found and understood and all the required changes which needs to be made in the system. Finally, using the tracing stage it could be established if the requirement of the following project is met or not.

Maintain:
Description:
In the following stage the requirement of the project is kept current and accurate throughout the cycle. Other than that, it would also enable to reuse the following requirements when needed (Tufail et al. 2017). Therefore, in the following at the maintenance stage it is assured that, the requirements in the following are projects are met and they are consistent.

Objective:
The primary objective of the following stage is to maintain the validity of the process. This could be done by organizing the overall process. Other than that, the requirements of the project would be maintained using the following stage.

Activities:
Some of the activities which could be taken into consideration in the following stage are:
User stories
Process modelling
Output:
Therefore, after the analysis of the following stage using the process the requirements of the stakeholders will be maintained in the following and therefore, thus the design of the following system would be maintained throughout the whole process.
Prioritize:
Description:
When it comes to the prioritization of the stages in the following the tasks which are present in the project they are being prioritized and ranked (Violante, Vezzetti&Alemanni, 2017). Other than that, the priorities in the following of the tasks are also done based on the importance of the stakeholders.

Objective:
The ultimate objective of the following stage in the requirement lifecycle is to secure the maximum value for the stakeholders. There are three key stakeholders in the following project, and they are the customers, the supermarkets and the service providers.
Activities:
Some of the activities which could be taken into consideration in the following stage of the requirement lifecycle are:
Risk analysis
Prioritization

Output:
The output of the following stage would be that the overall project would be prioritized as per the stakeholders and the tasks which would be taken into consideration. Therefore, because of the following the overall tasks would be completed within the time set for the overall project that is 6 months for the app and the website.

Assess:
Description:
When it comes to the assess stage of the requirement lifecycle in the following stage all the requirements of all stakeholders are being analyzed (Tufail et al. 2017). Therefore, using the following the decisions are being made and it also helps in having an informed decision in the following stage.

Objective:
The primary objective of the following stage in the lifecycle is that the requirements of all the stakeholders within the project are met. Other than that, it is also the objective that, the decisions which are taken for the projects in the following are meeting the needs and the requirement of the stakeholders.

Activities:
Some of the activities which are taken into consideration for the following are:
Decision analysis
Interface analysis

Output:
After the following stage the output which is attained in the following is that the decisions which are taken are seamless and also, they are in favor of the stakeholders. Moreover, the delivery timeline for the following project is maintained and thus there are no hamper done to the overall time period assigned to the project.

Approve:
Description:
During the process of approving the requirements for the project the business analysts are working with the stakeholders of the project with the role of governance (Morshedzadeh et al. 2018). The primary reason for the following is to approve on the changes or the requirements or designs as in the case of ‘serviceplease’.

Objective:
The objective of the following stage of the requirement lifecycle is that they are able to have a clear communication with the stakeholders of the project. Other than that, it is also taken into consideration that the process is seamless, and the approval is attained by the business analyst.

Activities:
Some of the activities which are taken into consideration in the following stage are:
Understanding the roles of the stakeholders
Proper communicating and the tracking of the approval.

Output:
The output of the following stage is that, the stakeholders approving the output of the app and the design which is useful for all the three stakeholders of the following app or website that is the customers, supermarkets and the service providers.

Importance of managing the requirement lifecycle and the implications of not managing the lifecycles: One of the primary purposes of the requirement lifecycle is that, to ensure that, the business, the stakeholders and the approved solution for the business are all aligned with each other. Other than that, it is also taken into consideration that, the solution is implementing the overall solution of the overall lifecycle. Therefore, as per the ultimate goal of the requirement lifecycle is not only to have an aligned system between the business, stakeholder and the solution but also that the requirements in the following are maintained and they are implemented in the solution of the initiatives (Harkin, 2021).

It is important to manage the requirement lifecycle of the project because there are various aspects of the project and therefore, it is important that the project is aligned with the needs and the requirements of the stakeholders. Other than that, it is also important that, the stakeholders are able to take that, into consideration and they are able to approve the proposed project. Some of the other importance of the following are:

Prevention of the chaos – It is important that, the errors are being identified and also the needs of the following project are being discovered. Therefore, using the following the mistakes of the following would be eliminated and thus the failure could be reduced to a significant level (Harkin, 2021).

Matching the expectations – Quality is not provided by accidents. Therefore, to attain the quality it is important to involve all the relevant stakeholders of the project. Therefore, with the help of the management of the requirement lifecycle there is an increased chance of getting the project or the application in the following project getting delivered. However, in case of poor requirement lifecycle management several negative consequences may be appeared. First of all, holding poor requirement lifecycle management is having the capability of adding a huge amount of money investment in order to acquire resources.
In addition to that, it can also enhance the entire expense of sustainment as well as development. Apart from that, it may be the main reason behind the overruns of schedule as well. As per the research, it has been found that approx half of the product defects comes from the requirements, which shows how poor requirement lifecycle management can impact negatively.

Requirements Traceability Matrix (RTM):

Conclusion:
The primary purpose of the following study is to evaluate the requirement management and the requirement lifecycle management. Therefore, in the following the scope of the projects is being defined in the following along with the requirement of the business. Other than that, the stakeholders of the following project have been defined in the following. Along with that, the functional and the non-functional requirements have been identified in the following project. Based on the following the requirement lifecycle has been defined where the five stages of the requirement lifecycle have been identified. Finally, the requirement traceability matrix has been defined. Therefore, it could be concluded that, the following project could be completed with the help of the following requirement traceability matrix. Some recommendations are listed in the following section:

First of all the requirements should be specified for the proposed application following different tasks, such as approval of requirements, assess the changes in requirement, prioritization of requirements, maintenance of requirements as well as tracing the requirements. Following these steps will help to avoid missing any crucial requirements;

Furthermore, for the purpose of better requirement lifecycle management, different emerging tools could be utilised as well, for example Visure, ReQ Test, The Sparx Systems and so forth.

References:
Fallah, S. M., Trautner, T., &Pauker, F. (2019). Integrated tool lifecycle. Procedia CIRP, 79, 257-262. https://www.sciencedirect.com/science/article/pii/S2212827119301763/pdfmd5=c0710aab5081f37d9080fee1d7420c1d&pid=1-s2.0-S2212827119301763-main.pdf

Harkin, K. (2021). The crucial importance of requirements management. Theneweconomy.com. Retrieved 14 October 2021, from https://www.theneweconomy.com/technology/the-crucial-importance-of-requirements-management.
Morshedzadeh, I., Oscarsson, J., Ng, A., Jeusfeld, M., & Sillanpaa, J. (2018). Product lifecycle management with provenance management and virtual models: an industrial use-case study. Procedia CIRP, 72, 1190-1195. https://www.sciencedirect.com/science/article/pii/S2212827118303159/pdfmd5=96566860a5128a0e30a95e17fb95f983&pid=1-s2.0-S2212827118303159-main.pdf
Satyarthi, S., & Pandey, D. (2017). Framework for Requirement Management using Requirement Traceability. International Journal of Advanced Research in Computer Science, 8(5). http://search.ebscohost.com/login.aspxdirect=true&profile=ehost&scope=site&authtype= crawler&jrnl=09765697&AN=124636473&h=Wq83nvmyHFhYZjvqHEreXBhI5nUJ0x%2Fo7ZmRe73kTeqf% 2Bfhqz0VlkDfJIxLWsHN8zZhTrQk85uXjvE4UzknnAA%3D%3D&crl=c
Tufail, H., Masood, M. F., Zeb, B., Azam, F., & Anwar, M. W. (2017, December). A systematic review of requirement traceability techniques and tools. Engineering assignmentIn 2017 2nd International Conference on System Reliability and Safety (ICSRS) (pp. 450-454). IEEE. https://www.researchgate.net/profile/Hanny-Tufail/publication/322873285_A_systematic_review_ of_requirement_traceability_techniques_and_ tools/links/5bf3bd4b92851c6b27cc2345/A-systematic-review-of-requirement-traceability-techniques-and-tools.pdf
Violante, M. G., Vezzetti, E., & Alemanni, M. (2017). An integrated approach to support the Requirement Management (RM) tool customization for a collaborative scenario. International Journal on Interactive Design and Manufacturing (IJIDeM), 11(2), 191-204. https://link.springer.com/content/pdf/10.1007/s12008-015-0266-3.pdf