28-08-2012, 05:13 PM
Remote Handling System
[attachment=32955]
INTRODUCTION OF THE PROJECT
“Remote Handling System” is configured to handle remote systems from a server in a network. The project created by using core java. The main components used are :
Core Java as language
Multithreading
Java Swings
Java Sockets
Java Remote Method Invocation
First of all the server and Client are connected to each other using sockets.The server program installed on server machine instructs the client program installed on client machine to perform a specific task using java RMI. Client program acts as instructed by the server and returns data to the server using sockets.
SYSTEM ANALYSIS
The main purpose of conducting system analysis is to study the various processes and to find out its requirements. These may include ways of capturing or processing data, producing information, controlling a business activity or supporting management. The determination of requirements entails studying the existing details about it to found out what these requirements are.
System analysis has been conducted with the following objectives in mind:
Identify the customers’ need.
Evaluate the system concept for feasibility.
Perform economic and technical analysis.
Allocate functions to hardware, software, people, database, and other system elements.
Establish cost and schedule constraints and Create a system definition that forms the foundation for all subsequent engineering work.
System Analysis includes requirement analysis. The requirement analysis task is a process of discovery, refinement, modeling, and specification. Requirement analysis allows the software engineer to refine the software allocation and build models of the data, functional, and behavioral domains that will be treated by software.
FEASIBILITY STUDY
Before getting started on a new system it was important to determine the feasibility involved in the development system so that the new system development could be developed. Feasibility is the determination is called feasibility study. Feasibility study is the measure of how beneficial or practical the development of an information system will be to an organization. The Feasibility analysis is a cross life cycle activity and should be continuously performed throughout the system life cycle.
THE METHODOLOGY ADOPTED
In this software project the spiral modal is used for development. Thespiral model, combines the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model, there in providing the potential for rapid development of incremental versions of the software. In this model the software is developed in a series of incremental releases with the early stages being either paper models or prototypes. Later iterations become increasingly more complete versions of the product.
ERD(Entity Relationship Diagram)
Definition:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.
Entity Relationship (ER) diagram:
This diagramming technique is used to visually present a database schema or data model and was original proposed by Chen in the 1970s. There are many different data modeling notations; some are very similar to UML class diagrams (with the exception of operations). However, the notation the used here is slightly different, as proposed by Elmasri, et al.
The database schema for this system is shown in figure. The table object has been left out of the diagram because the table management feature set had been dropped from the requirements before this stage of the design process.
Some important database design decisions are as follows:
To store the total price of an order with the order rather than calculating it on the fly when looking at past orders. This is because the price of menu items could change at any time, so the total price at the time of ordering must be stored so that the total price is not incorrectly calculated in future.
Similar to the previous point, the order receipt is stored as a hard-copy and not regenerated when reviewing past orders because things such as the restaurant name or VAT percentage are subject to change. Receipts stored need to be exactly the same as the customer copy in case of dispute.
[attachment=32955]
INTRODUCTION OF THE PROJECT
“Remote Handling System” is configured to handle remote systems from a server in a network. The project created by using core java. The main components used are :
Core Java as language
Multithreading
Java Swings
Java Sockets
Java Remote Method Invocation
First of all the server and Client are connected to each other using sockets.The server program installed on server machine instructs the client program installed on client machine to perform a specific task using java RMI. Client program acts as instructed by the server and returns data to the server using sockets.
SYSTEM ANALYSIS
The main purpose of conducting system analysis is to study the various processes and to find out its requirements. These may include ways of capturing or processing data, producing information, controlling a business activity or supporting management. The determination of requirements entails studying the existing details about it to found out what these requirements are.
System analysis has been conducted with the following objectives in mind:
Identify the customers’ need.
Evaluate the system concept for feasibility.
Perform economic and technical analysis.
Allocate functions to hardware, software, people, database, and other system elements.
Establish cost and schedule constraints and Create a system definition that forms the foundation for all subsequent engineering work.
System Analysis includes requirement analysis. The requirement analysis task is a process of discovery, refinement, modeling, and specification. Requirement analysis allows the software engineer to refine the software allocation and build models of the data, functional, and behavioral domains that will be treated by software.
FEASIBILITY STUDY
Before getting started on a new system it was important to determine the feasibility involved in the development system so that the new system development could be developed. Feasibility is the determination is called feasibility study. Feasibility study is the measure of how beneficial or practical the development of an information system will be to an organization. The Feasibility analysis is a cross life cycle activity and should be continuously performed throughout the system life cycle.
THE METHODOLOGY ADOPTED
In this software project the spiral modal is used for development. Thespiral model, combines the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model, there in providing the potential for rapid development of incremental versions of the software. In this model the software is developed in a series of incremental releases with the early stages being either paper models or prototypes. Later iterations become increasingly more complete versions of the product.
ERD(Entity Relationship Diagram)
Definition:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.
Entity Relationship (ER) diagram:
This diagramming technique is used to visually present a database schema or data model and was original proposed by Chen in the 1970s. There are many different data modeling notations; some are very similar to UML class diagrams (with the exception of operations). However, the notation the used here is slightly different, as proposed by Elmasri, et al.
The database schema for this system is shown in figure. The table object has been left out of the diagram because the table management feature set had been dropped from the requirements before this stage of the design process.
Some important database design decisions are as follows:
To store the total price of an order with the order rather than calculating it on the fly when looking at past orders. This is because the price of menu items could change at any time, so the total price at the time of ordering must be stored so that the total price is not incorrectly calculated in future.
Similar to the previous point, the order receipt is stored as a hard-copy and not regenerated when reviewing past orders because things such as the restaurant name or VAT percentage are subject to change. Receipts stored need to be exactly the same as the customer copy in case of dispute.