01-11-2016, 03:18 PM
1463060599-pandey.doc (Size: 3.32 MB / Downloads: 5)
Introduction
Courier Management system is a well-planned system designed in order to provide well structured mechanism to store record of all couriers. It maintains complete record of couriers, their charges and senders or receivers.
This proposed application will manage all the needs from both ends from consumer end as well as from management end. By using this application any organization can manage its all on going processes and also can generate reports that are very much important and fruitful in the growth of organization
Objective
This application would help very much keeping record about courier sent and on the basis of that total revenue can be calculated.
Management should be able to know the record of all couriers and how the performance of their business is going on. Integrity of records can be maintained because all data is kept in computerized format and chances of discrepancies are very low.
Site Feature and Available Information
There are mainly two modules in the project-
3.1. Admin
3.2. Member
3.1 Admin Features
a) Add new changed courier charges
b) See the different reports related to courier records
c) Can have information about various users and their password
3.2 Member Features
a) Registration (Sign Up)
b) Login
c) Add new courier records.
d) Can generate reports according to courier status.
e) Can generate reports about all couriers according to different criterion
f) Can generate reports about receiver’s details.
g) Edit personal details of sender.
4. System Analysis
System analysis is the main features of the software development. It can be said that it is the heart of any of the system. The analysis needs an expert supervision and person should be minimum System analysis with experience of 3 to 5 years. One can use Analysis tools to analyze the system.
Some of the tools we have used to analyze the problem is given below
4.1 Analysis Tools
4.1.1 Data Collection Tools:
In order to get the information for our proposed application we approached the
Analyze Infotech, and collected the information related to our application. This was necessary to make a general software, which can be used by any Business/Organization.
4.1.2 Charting Tools
The graphical Representation of system and activities help us to understand the minor problems and the flow of information very easily, which can become very helpful in analysis as well as to generated the new systems requirement. Graphical representation is always better than normal text. We made E-R diagram and Data Flow Diagram to collect all the information and build relationship among the external entities. In order to understand the flow of information in the system the Data Flow Diagram plays a very important role. E-R Diagram are used to convert the entities and relationship in the relational tables.
4.1.3 Dictionary Tool
This tool helps us to maintain and record the data & description of system element through data items, Processes and data sources. This basically helps us about the information flow among various units.
4.2 Identification of Need
Goal of analysis hear is recognition of the basic problem elements as perceived by the top management as well as Business administrator and understand application in the system context. In order to identify the need, there is a need to establish contact with various Business staff and software development organization.
4.3 Feasibility Study
All projects are feasible given unlimited resources and infinite time! Unfortunately, the development of computer based system is more likely to be plagued by a scarcity of resources and difficult delivery dates. It is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time. Months or years of effort, Money loss and untold professional embarrassment can be averted I few better understand the project at its study time.
This type of study determines if an application can and should be developed. Once it has been determining that, application is feasible.
After that analyst can go ahead and prepares the project specification, which finalizes project requirements. Feasibility studies are undertaken within tight time constraints.
The developed system is started after considering the main three types of feasibilities that are discussed below :-
4.3.1. Technical Feasibility
As we know the technical feasibility is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include:
• The facility to produce outputs of advertisements, shopping and mailing in a given time for ease of use.
• Response time under certain condition is minimal.
• Ability to process a certain volume of transaction at a particular speed.
• Facility to communicate data to distinct location.
In examining the technical feasibility, configuration of the system is given more importance than the actual make of hardware. The configuration should give the complete picture about the system’s requirements- how many workstations are required, how these units are interconnected so that they could operate and communicate smoothly.
4.3.2 Economical Feasibility
Economic analysis is the most frequently used technique for evaluating the effectiveness of the proposed system. More commonly known as cost/benefits analysis, the procedure is to determine the benefits and savings that are expected from the purposed system and compared with costs.
If benefits outweigh cost, a decision is taken to design and implement the system. Otherwise, further justification or alternative of the proposed system will have to be made if it has a chance of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle.
The analysis part also clears the doubt of economic problems which could be possible in developing the system. As already mentioned that the company has to just pay the developed software cost and not other investment is needed at the time of implementation of the new system as the preliminary requirements already exist in the company.
4.3.3 Operational Feasibility
Proposed projects are beneficial only if they can be turned into information system that will meet the financial management requirements of the business/organization. This test of feasibility asks if the system will work when it developed and installed. Are there major barriers to implementation?
Some of the important questions that are useful to test the operational feasibility of a project are given below:
• Is there sufficient support for the project from the implementation? From user? If the present system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.
• Are current business methods acceptable to the user? If they are not, user may welcome a change that will bring about a more operational and useful system
• Have the user been involved in the planning and development of the
project? If they are involved at the earliest stage of project development, the chances of resistance can be possibly reduced.
• Will the proposed system cause harm? Will it produce poorer result in any case or area?
• Will the performance of staff member fall down after implementation? Issue that
• appears to be quite minor at the early stage can grow into major problem after
implementation.
Therefore, it is always advisable to consider operational aspects carefully.
The system is developed keeping in mind that it should be user friendly and easy to operate hence the system is operational feasible.
Software Engineering Paradigm Applied
To solve actual problems in an industry setting a software Engineer or team of Engineers must incorporate a development strategy that encompasses the process methods and tools.
A process model for software engineering is chosen based on the nature of the project and application, the methods and tools to be used and the controls and deliverables that are required.
5. Design
Software Design is the first of three technical activities design, coding and
testing that are required to build and verifies software. The flow of information during this technical phase of the software requirement, manifested by information, functional and behavioral models feed the design step. Using one of a number of
design methods the design step produces a data design, an architectural design and a procedural design. The data design transforms the information domain model created during analysis into the data structures that will be required to implement the software. The architectural design defines the relationship among major structural components of the programs. The procedural design transform structural component into a procedural description of the software. Source code is generated and testing is conducted to integrate and validate the software.
Software design is the process through which requirement are translated into a representation of software. From a project management point of view, Software design is conducted in two steps
• Preliminary Design
• Detail Design
Designing of this software is done with high cohesiveness i.e. there is minimum interaction between two different modules. There is no intra modular relationship between modules. Most of the modules are self-independent. At same time modules are loosely coupled i.e. inter modular relation exists. Designing part includes its data flow diagrams, Database Tables and process logic of each and every modules, input design and output design. Input design includes input screens such as Business Login screen, Business Registration Screen, Unit Creation Screen, Unit Operator Creation Screen, Session Creation Screen, Session Termination Screen and many more for Transaction and output design includes Output screens such as Business Details, Unit Details, Unit Operator Details and various reports.