Requirement Analysis & Specification

Determining the System Requirements At the heart of system analysis is a detailed understanding of all the important facets of the business area under investigation. The key questions that come to our mind are: What is being done? How is it being done? How frequently does it occur? How well is the being performed? Does a problem exist?

To answer the above questions, system analysts discuss with different category of personas to collect various facts about the business process and their opinions of why thing happen as they do and their views for changing the exiting process.

Feasibility Analysis Economic feasibility: The cost of developing this project is merely the man-hours that are put into it, apart from this, on the institutional front the costs that it will be bearing is to comply with the minimum system requirements for the same. Technical feasibility: The minimum hardware configuration for his Project to run is as follows: Pentium I onwards 32 MB RAM

Analysis:Analysis is a detail study of the various operation performed by a system and their relationship within and outside of the system. A key question is what should be done to solve the problem? One aspect of analysis is to define the boundaries of the system and determine whether or not a candidate system should consider other related system data flow diagram, interview on site observation and questionnaire.

Testing: The testing of this project was carried out in various stages. The primary testing was carried out at the designing phase where each module was tested as soon as it was created. The second phase of testing was carried out after integration of the modules. The third and final testing was carried out through cyclomatic complexity- a system of data within which such a domain that would have to test each and every line of the code as well as ensure the integrity of the overall project. This method was sufficient enough to recognize the loop holes present and also helped us efficiently in removing them. System testing: Testing is an intension to find an error in the system during the development. The basic objective of testing is:1. To test the software with intent to find errors. 2. A good test case i s the one, which finds some yet undiscovered errors. During the development, the software has to pass through the number of stages. At each of these stages, we have the chance to commit the errors, because specifications might be faulty or the design may contain errors. It is actually the inability of the human to communicate with perfection that introduces a step of

quality assurance, which is carried out after software development. Testing represents the ultimate review of specification, designing and coding. Testing is carried out with the intent of finding errors, which always exists in software, no matter how strictly the checks may be. This step can never show the defeats, it can only show their presence.

Software & Hardware Requirements Hardware Requirement Hardware Processor RAM Monitor HDD Minimum Hardware Intel I core 3rd Gen 1 G.B. VGA 128 G.B. Space

Software Requirement
Software MS Access Visual Basic Operating System Minimum Requirement 2007 And Above 6.0 And Above Windows XP, 7

System Design After the detailed analysis of the existing system comes the most challenging of all phases in the system life cycle the design phase. In this phase the design of the new system. One that meets the user requirements is prepared the first step in this phase was preliminary design in which a general design plan was prepared and after that a detailed design for the system output, input, processing and files was prepared. The system was design keeping in the mind the following goals suitable i.e. make sure the system meets the user requirements, reliability i.e. user can count on the system to work as specific to work as specific and to produce valid and accurate output simplicity and easy to use. The design of an information system produces the details that how a system will meet the requirement identified during system analysis. This stage is referred to as logical design and the process of developing programmed software is known as physical design. System design has two phases. 1. Preliminary Design 2. Detailed Design

Preliminary Design Phase After analysing the current system and identifying the current requirements the preliminary design is prepared. Preliminary design is concerned with the transformation. In this phase context diagram for the system cycle and entity relationship diagram data flow diagram are prepared. This help in designing and deciding different forms screens responses temporary files and their attributes. In designing of the system we used the result of system analysis the first step is the preliminary designing is to identify the entities involved in the system. The entities are identified on the basis of different activities taking place in the system. After the identification of various sections their relationships are

established on the basis of their functioning. This will lead to foundation of logical database. The logical database is the result of preliminary design phase. In this phase after identifying the main modules of the proposed system, fields involved in the database are also identified.

Preliminary Design
In the preliminary design we need to arrange the different sections identified during analysis phase according to their relationship and their functionality.

Detailed Design
After the designs of the logical structure and the physical structure have been designed in this phase the input is taken from the preliminary design phase and the actual structure is designed. The screens and table format of the system are also designed in this phase. The physical design is compared with the logical design and all the required corrections have been made in the physical design. Designing is done keeping in mind the coding strategy. After the physical design the main processes involved in the system are prepared on the basis of the flow chart and the data flow diagrams. The detailed design consists of an input and an output and design of the proposed system. In this phase modular design is an important activity modularity means the proposed system should be divided into separable names and addressable elements called modules. These modules are integrated to satisfy the problem requirements. The biggest advantage of the modularity is in the maintenance of the system.

Input Design
The design decisions for handling input specify that how data are accepted for computer processing. These are two ways to enter the data one is directly and another is by using source documents such as variables.

Objectives of Input Design

SYSTEM DESIGN
Data Flow Diagram The functional model consists of multiple data flow diagrams which specify the meaning of operations & constraints. A DFD shows the functional relationships of the values computed by a system including input, output & internal data stores. A data flow data is a graph showing the flow of data from their sources in object through processes that transform them to their destinations in other objects.

OBJECT_ORIENTED COMPUTAONAL MODEL

Information saved

Input packet and saved information

Courier Service
Search data

Information

HOST

Request
FILE BROWSE

Response

CLIENT

WEB SERVER

IMPLEMENTATION
It is the process of having system personnel check out and put new equipment into use, trained user, install the new application and construct any files of data needed to use it. Depending upon the size of the organisation that will be involved in using the application and risk associated with its use, system developers may use to pilot the operation in only one area of the film, say in one department or with only one or two persons. Some times they will run old and new systems together to compare the results. In still other situations developers will stop using the old system one-day and begin using the new one the next. As we will see, each implementation strategy has its merits depending upon on the business situation in which it is considered. Regardless of the implementation strategy used, developers strive to ensure that the systems initial use is trouble free. Once installed, applications are often used for many years, however both the organization and the users will change and the environment will be different over weeks and months. Therefore the application will be undoubtedly have to maintain modification and changes will be made to the software, files or procedure to meet user requirements. Since the organisation system and business environment undergo continuous change; the information system should keep pace. In this sense, implementation is an on going process.

CONCLUSION
The system has been designed to be flexible as possible allowing updations done. At the same time, multiple updations are allowed in the system, there will be consistence preservation excite may be hosted by any of the sophisticated user or naive user, in a securely managed environment. The system must gather information. The courier agency may be updated by visiting their agencies at same time. The multiple system can also be taken as consideration. There will be consistence preservation excited may be hosted. The basic need of this project is to reduce the difficulties in order to perform the whole process. In the current scenario there are many problems prevailing in existing system. The existing system more based on human resources. Its time consuming and faced problem during updations. In this existing system problem are solved, also provide better security facility towards regular updations, also save time. The basic need of these project is highlight the problem concerned with mailpost and at the same time lightening the quick and fast services of courier agency. These system are less time and money consuming.