Design with UML

Advanced Business Systems (ABS)

Student’s name,

Professor’s name,

The course title,

Date

Use Case Diagram

Contract Manager

The contract manager places a request for staffing in the system.

The contract manager validates the contracts placed by contracting clients.

The contract manager views the current status of current contracts in the system.

The contractor or client that places a contract which is then validated by the contracting manager. The placement specialists then selects valid contractors and the contracting client can then view the clients’ records to determine the status of the contract (Bajpai & Gorthi, 2012).

The contract manager creates the contracting requirements in the contracting system.

Contract Specialist

The contract specialist views staffing request on the contracting software.

The contract specialist qualifies contract proposal placed by clients on the contracting software.

The contract specialist updates the status contract proposal placed by clients on the contracting software.

The contract specialist searchers for contractors to fulfill the requirements of the staffing services on the contracting software

Contract client

The contract client places a proposal in the system for the contracting service

The contract client views the status of the contract in the system

Activity Diagram

The activity diagram specifies the processes in the system and the sequence of events in the system. The sequence or flow of events in the proposed contracting system takes place between three main people. These are the client or contractor, the contract manager and the staffing manager. The contract manager places a contracting request and then the contractor places their proposals (Casamayor, Godoy & Campo, 2012). The contracts are entered in the contracts database in the contracting system. The contract manager then validates the contracts and requests the contracting specialist to receive the contracts and qualify them. The contract client then is able to view the status of the contract in the systems portal. The database layer of the activity diagram represents the layer used for data storage (Somerville, 2007). It is whether the database management system is implemented and where the database for the contract management system resides. All the processes and activities will require data to be stored or retrieved from the database and this layer will implement this functionality.

Functional Requirements for the system

System Specifications

The system should be able to maintain a database for contractors

The contracting system should be able to maintain a database of current contracts.

The contracting system should be able to maintain a database for staffing professionals

The contracting system should be allow a contract manager to review staff request

The contracting system should be allow a contract specialists to review staff request

The contracting system should allow a contract manager to validate current contracts

The contracting system should allow the contracting specialist to qualify the contracts.

The contracting system should allow the contract manager to view the current status of a contract.

The contracting system should allow the contract client to view the current status of a contract

The contracting system should allow the contract manager to store contracts in the database.

The contracting system should allow the system administrator to create new contract managers in the database.

The contracting system should allow the system administrator to create new contract specialists in the database.

The contracting system should allow the system administrator to create new contract clients in the database.

None-functional requirements

Apart from the functional requirements for the contractor management system, there are also non-functional requirements that the system must meet. These requirements include:

1. Performance requirements

The contract management system should be able to run on the available operating systems such as Windows, Linux and MC OS operating system. Further, the system should be robust enough to be able to recover from any form of failure. This is achieved through the use of exception handling during the implementation of the system.

2. Security requirements

The contractor management system should be able to meet the minimum security requirements. This means that the system should make use of encryption algorithms for data and passwords in order to protect the data from any unauthorized third parties.

Validation of functional models for the use case

Validation of the use case model is intended to ensure that the developed system represents the actual system described in the use case diagram.

Analyzing input and output values

The validation of the use case will be conducted by analyzing the input values and the output values for the system to ensure that the system performs the correct processing (Ministry of Finance Malaysia, 2013). Sample data for example data on new contracts and contract clients will be fed into the system and the reports evaluated to determine whether the system performs the calculations accurately. The outcomes will then be used to correct modules of the system that may not be working as per the functional and non-functional requirements.

Expert intuition

This validation method will be performed by letting recruitment experts use the system and their judgment and expert opinion used to validate the system. The expert intuition method of validating use cases is a one-stop method for validating the systems against use case models to ensure that the system enables the actors described in the use case diagram to perform the actions described for each actor (Ministry of Finance Malaysia, 2013). For the contractor management system expert intuition will involve obtaining expert opinion on whether the system enables the contract manager, the contract client and the staffing professionals to perform their functions in the system.

Real System Measurement

Real system measurement will be used to validate the functional requirements for the contractor management system. This will involve comparing the functional requirements of the system with the performance of the specified use cases in a real system. This can only be performed when the proposed contract management system has been completed.

The non-functional requirements of the system can be validated by measuring the response time and also by performing penetration tests in order to determine the robustness of the encryption algorithms and layers used for securing the applications. The validation process is intended to identify loopholes and seal them. Further, it is intended to ensure that the system meets the minimum functionalities of a contract management system.

REFERENCES

Somerville, I., (2007). Software Engineering. Addison-Wesley, Harlow, England.

Bajpai, V., & Gorthi, R. P. (2012). On non-functional requirements: A survey. In Electrical, Electronics and Computer Science (SCEECS), 2012 IEEE Students' Conference on (pp. 1-4). IEEE.

Casamayor, A., Godoy, D., & Campo, M. (2012). Functional grouping of natural language requirements for assistance in architectural software design. Knowledge-Based Systems, 30, 78-86.

Ministry of Finance Malaysia. (2013). Malaysia’s government procurement regime.