Identifying Stakeholders

The main functional requirement identified for the ERP system to be developed for the Blanch Construction company are presented below:

Remote Access: The system should be able to provide the employees of the organization the option to access the system from anywhere. In addition to this, the organization also wants the application to be open for accessing remotely for the customers as well.

Automated system: The system should be automated and should be able to perform the tasks on its own without any interference from the in house staffs of the organization.

 Accounts management: The system should be able to update the accounts of the people who are enrolled in the systems and also the business accounts of the company should be handled separately by the system.

Auto update: The system functionalities are allocated to the cloud vendors and hence, the software updates for the system are to be installed and downloaded automatically into the system.

Data Back up: The data in the system should be backed up automatically so that there are no loss in the data during any type of accidental events or even in case of natural calamities.

The discuss of the non-functional requirements are based on the FURPS+ framework and the description of the non-functional requirements are provided below:

Functionality: The aspect of functionality of the ERP system is dependent on the technology oriented requirements of the system. These requirements such as data storage and authentication facilities are to fulfilled efficiently by the system as would ensure that the system is fully functional lacking which the system would be incomplete and would lack efficiency to a great extent.

Usability: All the functions defined in the system should be usable appropriately by the users of the system. This is very important for the ERP system as this would be help in organization of the staffs and customer data efficiently for the organization.

Reliability: The ERP system developed for the Blach construction company should be reliable enough so that the system does not crash very often and the security sectors of the system are efficiently implemented so that they do not leak out data.

Performance: The efficiency of the ERP system would give the measure of performance for the system. The throughput of the system and the response time of the ERP system should be efficient enough so that the customer satisfaction can be maintained for the organization.

Supportability: The ERP system should be supported on all type of device and environments so that both the customers and staffs should be able to login to the system from remote areas.

The stakeholder analysis is concerned with the identification of the potential stakeholders of the system and mapping them according to their involvement in the project.

The stakeholder map is used for the classification of the stakeholders into four types:

 External Executives, Internal Executives, External operators and Internal Operators:

The descriptions of the stakeholders who are involved with the ERP system implementation of the Blach construction company is provided below:

Stakeholder	Descriptions
Contractors	The contractors would not be using the system directly, however after implementation their data would be stored in the system and hence they are the External Executives of the system.
Owners	The owners of the system are not associated directly with the system, however they are the once who would don the entire funding of the project, hence they are the External Executives of the system.
Cloud Vendor	The cloud vendors would be providing the architectural service to the organization for the ERP implementation.
Tech Support	The tech support would be support the project development and also the maintenance phase would be supported by the tech support.
Project Manager	The project manager is the main architect behind the development of the project and plays an important role in its implementation as well.
Board of Directors	The board of directors are responsible for the approval of the procedures that take place within the system.
End Users	The end users of the system play an important role as they are the ones for whom the system has been developed.
Clients	The clients would be uploading their data on the system and would be able to view and update their data as well.
Organizational Staffs	The organizational staffs would be handling the system and performing all the functions on the system and hence, they are regarded as the Internal operations.

The questionnaires designed in this section of the report are directed for the owner of the Blach construction company. The questionnaires have been described below:

• What are areas that your company currently lack in?
• What type of system would you propose for the mitigation of the problems in the organization?
• What are your expectations of the ERP system which is to be developed?
• What are benefits of moving the solution to a cloud based infrastructure?
• What about the type of services that you expect from the vendors?
• What are the expected security features that is expected from the system?
• What do your employees expect from the deployment of the system?
• What do you think are the challenges that you can come across during the development of the system?
• What are the aspects which are to be improved in future for the system?

Use Case	Description
Login	The employees and the clients would be able to log in to the system.
Register	The employees and the clients would be able to register themselves to the system.
Search Products	The clients would be able to search for the products on the system.
View Products	The system would be showing a list of products to the clients
Buy products	The clients buy the products online in the system.
Manage Accounts	The accounts would be managed by the administrator.
Make Payments	The payments would be made by the clients in the system.
Add accounts	The staffs would be able to add an account.
Delete Accounts	The staffs would be able to delete accounts of a particular clients who is no longer required.
Place Order	The orders are placed by the clients.
View Orders	The clients would be able to view the orders created  by them.
Log Out	The employees and the clients would be able to log out of the system.
Add products	The products would be added to the system by the staffs.
Update products	The employees are responsible for making updates for the products registered with the system.
Delete Products	The employees delete the product which are no longer available for the clients.
Manage Orders	The orders would be managed by the employees.

The use case of managing orders has been used for description in this part.

Use Case Title:	Manage orders
Actors:	Employees
Description:	The employees would be able to manage the orders as per requirement of the clients.
Precondition	The orders are placed by the clients.
Flow	1. Login 2. Search products 3. View products 4. Buy products 5. Place order 6. Manage order 7. Make Payment 8. Log out

References

Gambhir, K., Gupta, A., & Singh, J. (2016). U.S. Patent No. 9,372,740. Washington, DC: U.S. Patent and Trademark Office.

Grubbs, R. H., & Wenzel, A. G. (Eds.). (2015). Handbook of Metathesis, Volume 1: Catalyst Development and Mechanism (Vol. 1). John Wiley & Sons.

Lee, J., Park, J. G., & Lee, S. (2015). Raising team social capital with knowledge and communication in information systems development projects. International Journal of Project Management, 33(4), 797-807.

Martin, G. (2015). A conceptual framework to support adaptation of farming systems–Development and application with Forage Rummy. Agricultural Systems, 132, 52-61.

Oinas-Kukkonen, H., & Harjumaa, M. (2018). Persuasive systems design: key issues, process model and system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge.

Pred, A. (2017). City-systems in advanced economies: past growth, present processes and future development options. Routledge.

PYD, M. P. O. (2015). Positive youth development and relational-developmental-systems. Handbook of child psychology and developmental science, theory and method, 1, 607.

Rainey, L. B., & Tolk, A. (Eds.). (2015). Modeling and simulation support for system of systems engineering applications. John Wiley & Sons.

Savignon, S. J. (2018). Communicative competence. The TESOL Encyclopedia of English Language Teaching, 1-7.