System Development

Running head: SYSTEM DEVELOPMENT
System Development
Name of the Student:
Name of the University:
Author Note

1
SYSTEM DEVELOPMENT
Table of Contents
Functional and Non-Functional Requirements..........................................................................2
Functional Requirements.......................................................................................................2
Non-functional Requirements................................................................................................2
Stakeholder Analysis..................................................................................................................3
Stakeholder map.....................................................................................................................3
Stakeholder description..........................................................................................................4
Questionnaires............................................................................................................................5
Domain Model Class Diagram...................................................................................................6
Use Case Description.................................................................................................................6
Fully developed use case description.........................................................................................7
Use Case Diagram......................................................................................................................8
Activity Diagram........................................................................................................................9
System Sequence Diagram.......................................................................................................11
Bibliography.............................................................................................................................12

2
SYSTEM DEVELOPMENT
Functional and Non-Functional Requirements
Functional Requirements
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.
Non-functional Requirements
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

3
SYSTEM DEVELOPMENT
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.
Stakeholder Analysis
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.
Stakeholder map
The stakeholder map is used for the classification of the stakeholders into four types:
External Executives, Internal Executives, External operators and Internal Operators: