Sie sind auf Seite 1von 55

Chapter-1

INTRODUCTION TO THE PROJECT


Those were old days when employees on Gas Agency have to store all the information related to stock and billing into the very huge bundle of files. So the idea of automated Gas Agency Control and Billing has come forward. This system is developed in that respect for the stock, Bookings of Cylinders by customers and bills schedule, the data will be stored in the database from where we can retrieve the data which is required with in few seconds and we can modify the data easily. As soon as related authority makes the entries and click on the Save button Items will be entered in the master table and we can take the printout and can issue it to the customers. Before issuing the products/Items to the customers we have to enter all the available stock and purchase bills. This Gas Agency Management System is such

software, which helps user to do their work very easily and with fewer efforts. Once all the Master data is entered then all the available stock from purchase has to be entered in the database from front end. There is a user name and password so that any unauthorized person cannot be open and make changes into the stored data. Interface of the system is in Visual Basic 2005

(VB.Net), which is very much user friendly and backend is in

MS ACCESS used to stored the data base and for reports Crystal Reports are used.

VB.NET
(Need and Importance)

Till text was

recently, the

applications of

generally

provided

a The

characterbased interface. In a characterbased system, medium information exchange. application displayed text that prompted the user for the required information. It also specified the valid options, if any. The user then responded to these prompts by specifying the required information. With the advent of graphical operating systems like windows, the world of computing went through a dramatic change. It opened up a whole new world of graphics. VB.NET is also one of the visual programming tool, through which we can design very attractive and userfriendly software. A visual programming environment automates the process of creating a user interface. The interface provided by the visual programming environment to the programmer is called the visual interface. Using the visual interface, the programmer designs the user interface visually instead of writing code. The biggest advantage of visual programming is its Readytouse environment components. displays a list of Visual available programming components,

programmer picks up the required component from tool box. These components can be moved, resized and even deleted,
3

if so required. This software is designed in VB.NET using MS ACCESS database, with some Oracle commands for different queries.

CHAPTER-2

We use the computer technology in many ways, from visible to invisible, spectacular to routine, video games and special effects for films and television to microwave ovens, electronic cameras and automobile ignition system. In business too, computers and information system occupy a special place. Computers make possible the smooth and efficient operation of airline reservations, hospital record, departments accounting and payroll functions, electronics banking, telephone switching systems, Gas Agency stock and billing and countless other operations both large and small. To be of any use, a computerbased information system must function properly, be easy to use and suit the organization for which it has been designed. If it helps people do their jobs better and more efficiently, they will use it. If it is not helpful, they will surely avoid it.

WHAT IS A SYSTEM?
A system is a body of related components that function in harmony to achieve a common objective. We come across many systems in our day-to-day life. We all live according to an economic system in which goods and services are exchanged for other goods and services of comparable value, which benefits the participants to the exchange. A person communicates by means of a language, a highly developed system of words and symbols that convey meaning to each other. The complex central nervous system is responsible for our experiencing physical sensations like heat, cold, touch. A system is simply a set of components that interact to accomplish some purpose. Or A system is an orderly grouping of interdependent components linked together according to a plan to achieve a specific objective. The components that make up systems may actually be other smaller systems; that is, systems may be made up of levels of systems or sub-systems. Organizations consist of many business systems, each having the features of the general system.

The purposes of information systems are to process input, maintain files of data about the organization and produce information, reports and other output. An Information System can be defined as a sub-system of the business. Specifically, and it is an arrangement components of that interdependent human machine

interact to support the operational, managerial and decision making information needs of an organization. Information systems consist of sub-systems, including hardware, software and data storage for files and databases. The set of subsystems that uses the specific equipment, programs, files and procedures constitutes information systems application. Thus, information systems can be sale and purchase, accounting or payroll applications. Categories of Information Systems What is Systems Analysis and Design? Systems development has two major components: Systems Analysis and Systems Design Systems analysis refers to the process of examining a business situation with the intent of improving it through better methods and procedures. Systems design is the process of planning a new business system to replace the old system. Before this planning can be done, we must thoroughly understand the old system and determines how the computer can be best used to make its operation more effective.

Systems understanding

analysis the

then,

is

the

process by

of

totally and

current

system

gathering

interpreting facts, diagnosing problems and using the facts to improve the current system. Having determined the requirements and what the system is intended to do, the new system is designed, keeping in mind the objectives set during the system analysis. Thus, Analysis specifies what the system should do, that is it sets the objective and Design states how to accomplish this objective. Members of the Systems Development Team: User/Management Group: request to modify it. Systems Analyst: A Systems Analyst studies the problems and needs of an organization to determine how people, method and computer technology can best accomplish improvements for the business. When compute technology is used, the analyst is responsible for the efficient capture of data from its business source, the flow of that data to the computer and the timely information back to business users. Systems Designer: A Systems Designer designs the new system keeping in mind the objectives set during systems analysis. It is the job of the designer to convert the requirements specified by the
9

These are the people who

recognize a problem in the existing system and initiate a

analyst,

into

technical

specifications. Very often the systems analyst and the systems designer are the same person. Programmer: specifications A from programmer the designer takes and the turns technical them into

workable programs for the user/management. Group.

10

SYSTEM DESIGN
System design specifies how the system will work. It consists of five parts: 1. Output Design: The starting print of the design process is the proper knowledge of system requirements, which will normally be converted in terms of output. 2. Input Design: Once the output requirements have been finalized, the next step is to find what data need to be made available to the system to produce the desired output. The basic documents in which these data are available need to be identified. 3. File Design: Once the input data is captured in the system, these may have to be preserved either for a short or long period. These data will generally be stored in files in a logical manner. The designer will have to devise the techniques of storing and retrieving data from these files. 4. Procedure Design: This step involves specification of how processing will be performed. In this, there are two aspects: A. Computer Procedure Procedure 5. Control Design: The control design indicates necessary procedures, which will ensure correctness of processing, accuracy of data, timely output etc. this will ensure that system is functioning as per plan. B. Non-Computer

11

SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)


As already mentioned Systems development is a

process consisting of the two major steps of Systems Analysis and Design. It starts when management or the systems development personnel realize that a particular business system needs improvement. The Systems development life cycle is a sequence of events carried out by analysts, designers and users to develop and implement an information system. These activities are carried out in different stages. Most life cycles leave you with the impression that the phases of a project must be completed in a sequence. That is, you must finish one phase or task before starting the next. In reality phases of systems development life cycle can overlap. Each phase is subject to change, based on the outcome of reviews held at the end of each phase. This section examines each of the seven events that make up the systems development life cycle. Most systems activities are all closely related and are usually inseparable. Even the order of the steps in thse activities may be difficult to determine. Different parts of the project can be in various phases at the same time. stages. Phases of Systems Development Life Cycle are as follows:
12

Some components may

be

undergoing analysis while others are at advanced design

1. Preliminary Investigation (feasibility study) 2. Determination of Systems requirements (Analysis) 3. Design of the System 4. Development of Software 5. Systems Testing 6. Systems Implementation 7. Systems Maintenance Here we will concentrate on the Preliminary

Investigation (Feasibility Study)

13

PRELIMINARY INVESTIGATION (FEASIBILITY STUDY)


Preliminary Investigation starts as soon as someone, either a user or a member of a particular department recognizes a problem or initiates a request, to modify the current computerized system or to computerize the current manual system. An important outcome of the preliminary investigation is determining whether the system requested is feasible or not. The major purposes of this study are listed below: 1. Identify the responsible users and develop an initial scope of the system. 2. Identify current deficiencies in the users environment. 3. Determine objectives for the new system. 4. Determine whether it is feasible to automate the system options. The seven major areas to consider while determining the feasibility of a project are: Technical Feasibility The organization being pioneer in the area of education and training is well equipped with hardware as well as software. As far as the hardware setup is concerned, the organization is self-sufficient. Maximum polytechnics are ISO certified institutions.
14

and

it

so,

suggest

some

acceptable

Economical Feasibility Organization is already equipped with all the latest software and is also has a self-sufficient hardware setup. System is designed so as to fit in the current software present in the organization. If at all purchasing new software is required for long run and hence it is not an overhead. So system is economically feasible. Operation Feasibility The points to be considered are: 1. What changes will be brought with the system? 2. What organizational structures are disturbed? 3. What new skills will be required? Does the existing staff have these skills? If not, can they be trained in due course of time. Personnel, who understand the parts of the business that are relevant to the project and are skilled in system analysis and design process, carry out this feasibility system. The system incorporates user-friendly, default processing and required validation. These all are done keeping in view the individual with minimum computer knowledge. Social Feasibility Social proposed concerned feasibility be with, or is not. determination to the This of whether who a are will acceptable people,

determination

typically

examines the probability of the project being accepted by the group directly affected by the proposed system. Change.
15

Management Feasibility It is a determination of whether proposed project is acceptable to management. If management does not accept a project or gives a negligible support to it, the analyst will tend to view the project as a not-feasible one. Legal Feasibility It is determination of whether a proposed system infringes on known Acts, Statutes, as well as any pending legislation.

Time Feasibility It is determination of whether a proposed system can be implemented fully within a stipulated time frame. If project takes too much time it is likely to be rejected.

16

SOFTWARE ENGINEERING PARADIGM APPLIED QUALITY ASSURANCE


The software life cycle include has various the goal stages of of

development assurance.

and

each

stage

quality

1 Quality factors specification: The goal of this stage is to describe various factors mainly responsible quality of this proposed system. They are follows: Correctness: The extent to which a program meets system specification and user objectives. Reliability: The degree to which the system performs its intended functions over a time. Efficiency: Computer resources required by a program to perform a particular function. Usability: Efforts required to understand and operate a system. Maintainability: The ease with which the program error are detected and removed. Testability: The efforts required to test a program to ensure its correct performance. Accuracy: The required precision in input,editing, computation and output. Error Tolerance: Error detection and correction versus error avoidance.

17

Expandability: database.

Ease

of

expanding

the

existing

Access Control and Audit: Control of access to the system and the extent to which that access can be audited. Communicativeness: Usefulness and effectiveness of the inputs and outputs of the system. 2. Software requirements Specifications: The quality

assurance goal of this stage is to generate the requirement documents that help in providing technical specifications for developing software. 3. Software design specification: In this stage, the software design document defines the overall architecture of the software that provides the functions and features given in the software requirement document. 4. Software testing and implementation: The quality

assurance goal of the testing phase is to ensure that completeness and accuracy of the system and minimize the retesting process in the implementation phase, the goal is to provide a logical order for the creation of the modules and in turn the creation of the system. 5. to Maintenance comply with goal and the is to support: original be This phase provides The the

necessary software development for the system to continue specification. a quality for assurance developing procedure

correcting errors and enhancing software.


18

LEVELS OF QUALITY ASSURANCE


1. Testing: system testing is quite expensive and time consuming process. The common view of testing held by users is that it is performed to prove that program is error free. But this is quite difficult since the analyst cannot prove that software is free from all sort of error. 2. Verification with Validation: It is also intended to find error. Executing a program in a simulated enviournment performs it. Validation refers to a process of using software in alive environment to find errors. 3. Certification: The last level of quality assurance is to certify that the software package developed conforms to standards. With a growing demand for purchasing ready to use software, importance of certification has increased. A package that is certified goes through a team of computer specialists who test, review and determine how well it meets the users requirements and vendors claim. Certification is issued only if the package is successful in all the tests.

19

Chapter-3

20

SOFTWARE AND HARDWARE REQUIREMENT SPECIFICATION


SOFTWARE SELECTION The criteria for software selection are: Reliability: gives consistent results without any failure for a specified time period. Functionality: functions to standards. Capacity: satisfies volume requirements of the user. Flexibility: adapts to the changing needs. Usability: is user friendly. Security: maintains integrity and prevents unauthorized user. Performance: delivers the results as expected. Serviceability: supports. Ownership: has right to modify and share use of package. Minimum Cost : is justified and affordable for intended application. HARDWARE SELECTION Selecting a system is a serious and time-consuming business. The time spent on the selection process is a function of the application and whether the system is a basic microcomputer or a mainframe. In either case, planning system selection and acquiring experienced help where necessary pay off in the long run. There are various important factors, which should be considered prior to system selection. They are:
21

have

good

documentation

and

vendor

Define system capabilities that make sense for the business. Specify the magnitude of the problem; that is clarify whether selection entails a few peripheral or a major decision concerning the mainframe. Access the competence of the in-house staff. Hardware and software should be considered as package. Develop a time frame for the selection process. Provide user indoctrination: This is crucial, especially for the first time user. Selling the system to the user staff, provide inadequate training and creating an environment conductive to implementation and pre-requisites for the system acquisition. The selection process consist of several process: Requirement analysis: The first selection in understanding the users requirement within the framework of the organizations objectives and the environment in which the system is being installed. System specification: System specification must be clearly defines. These specifications must reflect the actual file application to be handled by the system and include system objectives, flowcharts, input-output requirements, structure and cost. Request for proposal: After the requirement analysis and system specification have been defined, a request for

22

proposal is prepared and sent to selected vendors for bidding. Evaluation and validation: The evaluation phase ranks

various vendor proposals and determines the one best suited to the users requirements. It looks into items such as price, availability and technical support. System validation ensures that the vendor can, in fact, match his/her claims, especially system performance. Vendor Selection: This step determines the vendor with the best combination of reputation, reliability, service record, training, delivery time, lease/finance systems. The selected vendors are invited to give a presentation of their system. The system chosen goes through contract negation before implementation.

HARDWARE AND SOFTWARE REQUIREMENTS


Hardware Profile: 23

1. Processor 2. RAM 3. Hard Disk 4. Printer 5. Monitor Software Profile: 1. Operating System 2. Front End 3. Back End
4. Report
VB.Net)

Pentium IV 1.5 GHz or above. 128 MB or above. 40 GB or above. Any type of printer Any colored monitor

Windows Operating System. VB.Net SQL Server 2000 Crystal Report


(alrea dy with

24

Chapter-4

25

SYSTEM STUDY
Existing System Any Gas Agency have different types of products/items to sales. They firstly purchase Items from refineries and then maintain manually. Following is the flow of existing system: 1. They purchase Items as per demand or requirement. 2. Make the manual entry of purchased Item in file. 3. Sale the item to the customer. 4. Provide a manual bill to customer of the item sold 5. At day end they have to calculate all the purchased and sold item manually which take a lot of time to calculate. 6. Accuracy was not in the manual calculation. Problem In Existing System 1. The system required more manpower. 2. As the system is manual data redundancy take place. 3. This Leads to wastage of time, man-hours and money. 4. Difficulty to get quick information due to much of paper handling. 5. Data security cannot be achieved. 6. Report generation takes lot of time as they are done. 7. Manually, fatal errors may occur at these points. Now the main problem is to maintain Stock, Purchase entry and sales entry. On which we have concentrated our project work.
26

their

Stock

record

on

paper.

Billing

is

also

NEED FOR THE SYSTEM


Need of computerization 1. Easy to keep track of all records. 2. Proper and regular modifications are done in time. 3. Easy and quick report generation. 4. Fast processing of data, which help in giving correct outputs.

PROPOSED SYSTEM
Proposed system scope The main purpose of the system is allow user to fill all the details related to Item Master, Tanks and Machines. It saves lots of time user and the organization, the cost incurred on the system is one time and not like manual system where there are recurring costs. Quick assessment of task is possible. Reports are generated in no time. It can store information of the Items Master, Stock-in Entry and Sold Item etc.

27

FACT FINDING TECHNIQUE


By applying the structure System Analysis and Design methodologies, the background information is collected. Interview As this is the most efficient way of gathering information from the individuals, various person where

interviewed which gave quantitative information such as adjective, constraint, problem, failures and allocation of duties. Observation The obstacles were found by observing the daily work in the Institute. This gave and idea about the environment of the Institute. Record Searching Various resisters and files were scanned to obtained information about the manual procedure and difficulties faced. Sample of various document were studied. They proved to be very helpful in developing this system.

28

IMPLEMENTATION
Minimum requirement for implementing the system is hardware, which is already available and the users of the system, which are familiar with the basics of the computers. A short training program will be concluded to the user to help them to understand the system. Once the training program is over implementation of the system is done. Pilot-run of the system In this phase the historical data will be entered in the system as test data and the outputs of the system will be checked against the historical reports. As both input and output are available, this phase is not taking much time. Parallel run of the system In this phase both the manual system as well as computer system will process. As in some cases of test it is necessary to do some paper work. Rest entire College Admission System will be computerized.

29

Chapter-5

30

ENTITY RELATIONSHIP (ER) DIAGRAM


The object /relationship pair is the cornerstone of the data model. These pair can be represented graphically using the ENTITY/RELATIONSHIP DIAGRAM. The ERD was originally proposed by Peter Chen for the design of relational database system and has been extended by others. The primary purpose of the ERD is to represent data objects and their relationships . A set of primary components is identified for the ERD. These are:

ENTITIES
Which specify distinct real world items in an application

RELATIONSHIPS
Which connect entities and represent meaningful dependencies between them.

ATTRIBUTES
Which specify properties of entities and relationships

31

METHODOLOGY

Information Gathering

Analysis

Designing Solution Developing Solution Coding

Testing

Implementati on

32

E-R DIAGRAM OF MACHINE AND TANK

33

Chapter-6

34

DATABASE USED MS ACCESS


MS Access is a Relational Data Base Management System. In MS Access has much advantage over other DBMS. The user can create Table and store related data in it. MS access provides easy way to create tables we can create tables in design mode or by using the in build Wizards. User can also create form layout in MS Access.

To create table in MS Access follows These Steps.


1) 2) Start MS Access form Start -> Program File -> MS Office -> MS Access. In the File Menu Select New to create new database. 3) MS Access Ask You to save the database name in specified location. Type the file name in file save dialog box and click save button. 4) 5) 6) MS Access opens a table design window in which you can design the table by using design view of by using wizard. Select Create Table in Design View to open design table windows Here you can type the field name, specify the data type and the size of the fields. This window also allows the user to define the different constraints like Primary Key constraints and Not Null Key constraints. 7) Select save button in tool bar to save the table by giving a suitable name.

35

THE TABLE DESIGN WINDOW

36

To attach the MS Access with Visual Basic the three major tools are widely used.

1) 2) 3)

The Data Control The Data Access Object (DAO) The Active Data Object (ADO) Data Control

With

data

control

we

can

access

database

without

any

programming. We can set to property of data control i.e. Database name to database, and Record Source to table name. We can display the data in regular controls like textboxes etc. The Data Access Object The Data Access Object is a structure of object s for accessing database through VB code. All the function of Data Control available in VB Code.

Record Sets

Record Sets are the objects that represent collection of records from one or more tables. In database programming, Record Sets are equivalent of a variable in regular programming. We can access a table directory via a Record Set Object. A Record Set is
37

constructed of columns and rows and is similar to a table, but it can contain data from multiple tables. The Record Set work like a bridge between the Visual Basic and The Database. There are three types of Record Sets 1) DynaSets, which are updateable views of data 2) Snapshots, which are static (read-only) views of data 3) Tables, Which are direct views of tables.

The SQL Statements


The SQL statements are used to extract data from a database. SQL statements are basically Record Set definitions. With SQL statements we can extract data from multiple table at a given time. We can make query, sub query with SQL statements. The SQL Statements are beginning with the SELECT statement.

38

39

40

41

VALIDATION CHECKS
1. Name should not contain any non-alphabetic characters. 2. Date should be in correct format. 3. Fields should not be left blank. 4. Phone No. should be numeric with mark. 5. Item Code in master table should be unique. 6. Tank No. in master table should be unique. 7. Bill No. should be unique.

IMPLEMENTATION, EVALUTION AND MAINTENANCE

Implementation is the processes of having system personnel check ou

and put new equipment into use, train users, install the new application

and constructs any files of data needed to use it. This phase is less

creative than system design. Depending on size of organization that wil

be involved in using the application and the risks involved in its use

system developers may choose to test the operation in only one area o

the firm with only one or two persons. Sometimes they will run both old

and new system in parallel way to compare the results. In still othe start using the new one the next.

situations, system developers stop using the old system one day and

Evaluation of the system is performed to identify its strengths and dimensions:


42

weaknesses. The actual evaluation can occur along any of the following

Operation Evaluation: Assessment of the manner in which the reliability and level of utilization.

system functions, including case of use, response time, overal

Organizational Impact: Identification and measurement of benefits o efficiency and competitive impact.

the organization in such areas as financial concerns, operationa

User Manager Assessment: Evaluation of the attitudes of senior and user manager within the organization, as well as end users. Development Performance: Evaluation of the development proces

in accordance with such yard sticks as overall development time and management criteria.

effort, conformance to budgets and standards and other projec

Maintenance is necessary to eliminate errors in the working system

during its working life and to tune the system to any variations in its

working environments. Often small system deficiencies are found as a

system is brought into operations and changes are made to remove them

System planners must always plan for resources availability to carry ou continue to bring the new system to standards.

these maintenance functions. The importance of maintenance is to

MAINTENANCE ISSUES
43

When

the

systems

are

installed,

they

are

normally

used

for

considerable period. Average life of system is generally 4 to 6 years with

the oldest applications often in use for over 10 years. However this period

of constant use brings with it the used to continually maintain the system

When system is fully implemented analyst must take precautions to testing the ability to perform it is provided through proper practices.

ensure that the need for maintenance is controlled through design and

Maintenance is necessary to eliminate errors in the working system

during its working life and to tune the system any variations in its working

environment. Often small system deficiencies are found as a system is

brought into operations and changes are made to remove them. System

planners must always plan for resources availability to carry out these bring the new system to standards. a system is spent on maintenance. 2. Often maintenance is not done very efficiently.

maintenance functions the importance of maintenance is to continue to

1. From 60% to 90% of the overall cost of software during the life o

3. Software demand is growing at a faster rate than supply. Many on new software development.

programmers are spending more time on system maintenance tha

Type of System maintenance Category Corrective Emergency Activity fixes


44

routine

Relative Frequency 20%

Adaptive

debugging. Accommodation of changes to data and files and to hardware and system software. User enhancement documentation,

20%

Perfective

improved for

60%

recording

computational efficiency.

Adaption maintenance means changing the program functions. Enhancing

the performance or modifying the program according to users additiona amount spend of on maintenance perfective that is on for user enhancement and and

or changing needs are included in perfective maintenance the greates

improved

documentation of the system for better efficiency. More time and money corrective adaptive together.

maintenance

The key to reduce the need for maintenance while making it possible to carry with essential tasks more efficiently is as follows: development. 2. Preparation of system documentation in a better way. communicating it to project team members. 4. Making better use of existing tools and techniques. 5. Managing the systems engineering process effectively .

1. More accurate defining the users requirement during system

3. Using more effective ways for designing processing logic and

TESTING
45

Testing plays an important role while developing particular system to part of the manual procedure is not considered at all.

It help us to know if there as any fault in the system, which would be due

The data is observed at every stage of the system of the system and

verified the data movement updates are appropriate. Data process and verified and compared with the already available result.

results are observed at every stage of the system. Then results are

Testing is the process to find errors in the software. The testing is for testing the software.

done with the philosophy to find errors. There are two general strategies

Code Testing: in the testing, the analyst develops that cases to execute every instructions and path in a program.

Specification Testing: in this testing, analyst examines the program operates under specific conditions .

specification and then rites test data to determine how the program

46

LEVEL OF TESTING:
There are two level of testing:

Unit Testing: It is also called a program testing. Unit testing gives

stress on the modules independently of one another, to find error. The

analyst tests the program making up a whole system; it tends to delete are: modules alone. It avoids the error resulting from interaction between modules.

errors in each every modules of system independently. Its main features

It helps the tester in deleting errors in syntax and logic of particula

System Testing: Testing the system as a whole. System testing

makes the assumption that if all the parts of a system are correct then the

ultimate goal will be successfully achieved. A newly developed system

has many subsystems or parts that are in a working order but all of them

work independently. Under system testing all of them come under one

pool and tested simultaneously as a whole system to detect the steps: errors within the program are detected and connected. rules of the languages it is written e.g. Omitted Key Words. Improperly defined fields.

interaction caused errors and correct them. System testing is of five

Program Testing: Under this testing the logical and syntactica

Syntax Error: It is a program statement the violated one or more

47

Logical errors: Deal with incorrect data fields out of range items and

invalid combinations. These errors are not detected by the compiler, so

that programmers must examine the output carefully to detect the error is there in the program are traced to detect the problem.

The actual output is compared with the expected output and if difference

String Testing: The programs of a system are interrelated to one

another so . Their interaction results are checked. Each modules checked

to see whether it works with union with other subsequent module or not o

in other words the interactive functioning of different modules is checked. System Testing: System testing is designed to uncover

the

weaknesses that were left in earlier tests. This includes forced system ensure that no data are los during the emergency.

failures are used to test the recovery and feedback after major failures to

System Documentation: All design and test documentation should are kept safe for failure maintenance of the new system.

User Acceptance Testing: It is tested to the whether the use

accepting the system or not it verifies that the system procedure operates is ultimately developed according as the requirements predefined earlier.

to system specification. It is vital steps, which determines that he system

Benchmark Testing: It is process in which a s/w is tested for its as well as software on the basics of terms given by vendors.

reliability. It is a kind of software that is used to check the hardware par

48

The benchmark is a special program, which is specially designed to

evaluate the performance of different computers and their software. As validation of vendors claims in respect of following points: Minimum hardware configuration. Time required to execute a program

regard, Evolution of software benchmarking is mainly concerned with

Affect of performance of package & new software on existing

programs and running software. The common benchmarks test the speed

of the central processor, with typical instructions executed in a set o

programs, as well as multiple streams of jobs in a multiprogramming

environment. The same benchmark run on several different computers he central processors.

will make apparent any speed and performance different attributable to

Benchmark can also be centered around an expected languages mix applications requirements. having widely varying input and output volumes

for the programs that will be run a mix of different sets of programs and

and

Thus benchmarking is one of the evolution techniques used by he

computer purchaser to determine which marking is best for them in both speed & cost.

marking is best for them in marking out their requirements in terms o

SYSTEM SECURITY MEASUREMENT

The measurements for data protection taken by an organization management treats computers
49

reflect its awareness and attitude towards information technology. If top as a dehumanized, intangible,

bu

necessary evil, the measures taken to protect data, individual privacy and management considers information as an important resources

data integrity would, be lackadaisical. On the other hand, if the

and

computers as an aid in decision making one would find a positive

approach and involvement by the management towards security o and the workers consider the computer corresponding as or an ally.

information. This attitude naturally percolates down to the lower levels

One of he best and first steps in ensuring data security is to create an in which information can be lost/altered and what would be

awareness and develop a culture within the organisaion towards the way

the

concequence, of such an occurrence, o the organization and indivisuals The others steps that can be taken are: IT Planning Selection of Technology. Three types of security: Physical Security Software Security Network Security

COST ESTIMATION OF THE PROJECT


Software costs constituted a small percentage of

the overal

computer-based cost. As order of magnitude error in estimates o

software cost had relatively little impact. Today, software is the mos
50

expensive element of virtually all computer-based system. For complex

custom system, a large cost estimation error can make the difference

between profit and loss. Cost overrun can be disastrous for developer

Software cost and effort estimation will never be an exact science. Too

many variable-human, technical, environmental, political can affec

ultimate cost of software and effort applied to develop it. However series of systematic steps that provide estimates with acceptable risk. To achieve reliable cost and effort estimates, a number of options arise: achieve 100% accurate estimates after the project is complete) completed. project cost and effort estimates. estimation.

software project estimation can be transformed from a black art to a

1. Delay estimation until late in the project (obviously, we can

2. Base estimates on similar projects that have already been

3. Use relatively simple decomposition techniques to generate

4. Use one or more empirical models for software cost and effor

Unfortunately, the first option, however attractive, is not practical

Cost estimates must be provided up front. However, we should know, the less likely we are to make serious errors in our estimates.

recognize that the longer we wait, the more we know and the more we

The second option can work reasonably well, if the current project is customer, business condition, the SEE, deadlines are

quite similar to past efforts and other project influences (e.g. the

equivalent

unfortunately, past experience has not always been a good indicator o

future result. The remaining options are viable approaches to software


51

project estimation. Ideally the techniques noted for each option should be applied in tandem, each used as a cross-check for the other.

52

FUTURE SCOPE AND FURTHER ENHANCEMENT

After the successful completion and Implementation of this project I will work to append the software to the II phase.

In this phase Ill like to add automatic generation of ordering of items according to the available stock of Items Now, in the III and last phase: Salary of the employees can be added automatically. any efforts.

On the basis of this phase we can maintain and can calculate benefits with ou

53

CONCLUSION
proposed system Gas Agency Management System. During the development

It was enlightening experience to have work on the development on the

had come across different approaches to overcome and as a result my knowledge in

that area. While developing the project I learned how to integrate the software and my approach . This system satisfied most of the objective like: The proposed system features updation. It will generate various reports. It will perform with proper speed and accuracy.

hardware to achieved the desired result. The completion of the project has improved

54

BIBLIOGRAPHY

I take help from the following books to maintain this proposal. The lis of books is:-Books:Elias M.Awad, System Analysis and Design, Galgotia Publications (P) Ltd., 5, Ansari Road, Darya Gang, New Delhi110002, year 2002, second Edition. Bhatia Parteek, Singh Gurvinder, Simplified Approach to DBMS, Kalyani Publishers, V.K. Printers, New Delhi and Published By Mrs. Usha Raj Kumar for Kalyani Publishers, New Delhi-110002, year 2004, First Edition.

Website Consulted:
1) GOOGLE for searching information

55

Das könnte Ihnen auch gefallen