Distributed Task Execution Framework- Non Functional And Functional Requirements

 FUNCTIONAL REQUIREMENTS

Read about the project

Server Listening

Here we start a listen port on the server side and assumed that the Server will be listening until the request will come from any of the client.As the client request to the Server and establish a connection with it the server GUI will be open in respond to it.

Job feeding

Here the client will come forward with the task to be submitted to the controller which he assumed to be performed by the Agents. The client feed the job through the GUI form on the client side, which is created dynamically.

Parsing

Here the client data will be written into both the TEXT or XML files and it is than transformed into the Object which is than passed to the Server.

Connection establishment

Here the Server responds to the client request by opening the GUI of it.

XML objects transformation

Here the parameter passed by the client in the form of object is again transformed into the appropriate XML files.

Scheduling

Here Server read the XML file data and then does appropriate action for Scheduling depending upon the priority of the job submitted by the client.

Dispatching

Here the Server when find the appropriate Agent machine capable of executing the task, will assign the task to them and remove those task from the waiting scheduler priority queue.

Job Execution

Here the job is executed by the Agent machines under the supervision and control of the Controller.

Log Creation

Here the Controller will create the appropriate log information of the task/job executed by it for the further reference by the humans on the client side and even required in the future for measuring the performance issue of the Server (controller).

Agent Feedback

Here Agent will send back the feedback of the task to the Controller. Controller on contemporary will send the status to the Client.

NON FUNCTIONAL REQUIREMENTS

 External Requirements

    External requirements include all the requirements that may arise from the external factors. These include interoperability requirements that define the compatibility of the proposed system with other systems, legislative requirements to ensure that the product complies with the state legislations and ethical requirements to ensure social acceptability.
    The proposed system is fully interoperable with existing system because it is being developed with the consideration of Crashes, Performance attributes are measured.

 Modifiability

    The proposed application must be structured to support later expected modification. Design of this project is tied to make in this way that if user wants some modification so that it can be done very easily. Since due to change in working environment requirements of users can also be changed.

Accuracy

    The document and working of system software satisfies its specifications and fulfills user objectives. No software can achieve 100% accuracy but developer tries to develop the software, which can achieve the user requirements and expectations as far as possible.

Reliability

    The system developed should be highly reliable. The unexpected error conditions are to be handled properly. For the specified input, only the specified output should be generated.

Efficiency

    The amount of computing resources and code required by the document by the document is performed for its function. The efficiency of source code is directly tied to the efficiency of algorithms defined during detailed design.

 Flexibility

    Modification of this software is done easily without many efforts.

 Reusability

    The function and structure are so created in a program (i.e. both source code and compiled components) can be used in other applications.

Domain Requirements

    These requirements are derived from the application domains employed in the design of the system. This may add a new set of functional requirements to the existing list. It may also pose new constraints on the system design. It is essential to satisfy these requirements as they may affect the compatibility of the system.

Acceptance Criteria

    Acceptance criteria actually tell whether the product is behaving as it was expected. Before delivering the product we do some validation like giving some input we check its output whether it is correct or not. So that before delivering the system, it has to be ensured that it meets all the requirements and functional specifications. The tests to be performed before acceptance will have suitable test cases that will satisfy all the conditions. 

Written By  Saju Thomas

Read more about Module Specifications
Read more about Java Programming features like Socket Programming,Swing,RMI ,NetBeans and XML
Read more about Project Description
Read more about Activity, Sequence and Class Diagrams