project report course registration system

93
Index Introduction about the software Software Development life Cycle Feasibility study Technical Feasibility Economic Feasibility Operational Feasibility Social Feasibility System Analysis Problem definition Problem analysis Analysis issues Software requirement specification Requirements process Requirements determination Requirements Anticipation Requirements Investigation Requirements Specification Testing Testing Information flow Data flow Testing Loop Testing System Testing Recovery Testing Security Testing Coding and Interface Forms

Upload: imran-khan-mewati

Post on 26-Nov-2014

123 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Project Report Course Registration System

Index

Introduction about the software

Software Development life Cycle

Feasibility study

Technical Feasibility Economic Feasibility Operational Feasibility Social Feasibility

System Analysis

Problem definition Problem analysis Analysis issues

Software requirement specification

Requirements process Requirements determination Requirements Anticipation Requirements Investigation Requirements Specification

Testing

Testing Information flow Data flow Testing Loop Testing System Testing Recovery Testing Security Testing

Coding and Interface Forms

References Future Enhancement

AppendixReferences

Page 2: Project Report Course Registration System

Introduction

With this changing world we also have to change ourselves according to the

current requirements of the market, there was no proper medium available for the people

to get information about the world so that they could update theirseleves besides news

paper, but today various medium area there such as television, radio and now a days IT.

IT has changed the people's idea about information. People can get information about any

thing within few seconds. These medium are the software which are developed to store

information about any particular area. Here, the software CR will help the student to get

the information about a particular course and then they can easily register them self in a

particular course. The management of the institution can easily see the records of the

students and course and fees.

Page 3: Project Report Course Registration System

CANDIDATE’S DECLARATION

I hereby that the project entitled “ATM System” Submitted by fulfillment of

the requirement for the award of degree of bachelor in computer application of C.C.S. University, Meerut Is in authentic record of work carried out by me under the Guidance of Mr. I also declare that the matter embodied in the project report has not been submitted for the award of any other degree or diploma.

Mr.

Date:

Page 4: Project Report Course Registration System

CERTIFICATE

This is to certify that we are the student of Bhagwant Institute of Technology Muzaffarnagar has done His dissertation work on the topic “Course Registratioin System“ Under my supervision for the award of

BACHELOR IN COMPUTER APPLICATION from C.C.S. UNIVERSITY, MEERUT.

I wish him all success in life.

Mr.

(PROJECT GUIDE) BIT, MEERUT

Page 5: Project Report Course Registration System

Requirement Tool & environment

1.8 GHz or Above128 MB Ram10 GB HDD Windows xp

Front end Visual Basic 6.0

Back EndMs Access

As a front end, visual basic 6.0 support our project environment because:

It have various powerful feature Faster compiler New active x data control object Allow the database integration with wide variety of application system New data support designer New package and development wizard Additional internet capabilities

And as a back end, Microsoft access supports our database requirement

Page 6: Project Report Course Registration System

SDLCSoftware Development Life Cycle

Feasibility Study

A feasibility study is a process of planning to develop a new system or improving an existing one. It includes developing plans for designing the system testing it, introducing it to organization, and maintaining it. A feasibility study not only states that an idea is feasible it includes data gathering, analysis, and design of the overall system process. To success initiate a feasibility study the project leader must accomplish two Tasks:

Clearly defines the objectives of the study. Device an implementation plans so that corporation can allocate the necessary

resources to assist him. Now we have some following type of feasibility. They are as follows:

TECHANICAL FEASIBILITY:-

The proposed project is user friendly as well as easy to operate. It is a menu driven software which a layman can also operate, so it is very easy for the user to know and run the software in 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 requirements like—many work stations are required, how these units are interconnected so that they could operate and communicate smoothly. What speed of input and output should be achieved at particular quality of printing?

ECONOMIC FEASIBILITY:-

Financial benefits arising are more since any already installed hardware can be used and software investments is almost negligible, as the software can be run on any operating system which is already there in the machine. User can be trained to use the system in very less time and cost, thereby increasing the profit. The proposed project is economically feasible. Economic analysis is the most frequently used technique for evaluating the effectiveness of the proposed project more commonly know as cost benefit analysis. The procedure is to determine the benefits and savings that are expected from a proposed project and compare them with the cost.

OPERATIONAL FEASIBILITY:-

Page 7: Project Report Course Registration System

Operational feasibility is mainly related to human organizational and political aspects. Our project is operationally feasible because all type of user can use or work in our project. The main points which are considered in our project to make it operationally feasible are

1- There is sufficient support for the project from the management. The current project is well like and used to the extent that users will not be able to see reasons for a change.

2- The current project have the methods acceptable to the users, there are some facilities in the project that the user may welcome a change that will bring about a more operational and useful system according to there needs.

3- The proposed system does not cause any harm and it will produce better results in any respect or area. The proposed project provides high performance in all areas and will not affect any customer in an undesirable way.

SOCIAL FEASIBILITY:-

The current project is socially feasible because it is acceptable by all the user, the determination examined that the probability of the project is being accepted by the group directly affected by the proposed project change.

SYSTEM ANALYSIS This section overviews systems analysis and design and describe the work of system analysts & the different types of users that participate in the development process.

PROBLEM DEFINATION:-

This is initial and essential step in planning software project before starting work on the project ATM SYSTEM, some questions arises in my mind that what is the actual problem and how could I solve it? What are he characteristics of the entity that I can use to solve the problem? How will the entity and the solution realized? What approach will be used to solve the unclear errors that were made while designing & doing construction of the entity? How wills the entity, we supposed over the long, when correction, adaptation and enhancements are requested by the user? After knowing the actual problem I define some point for the problem definition, I develop a definite statement of the problem to be solve including description of the present situation, problem constraints and a statement of the goals to be achieve, I though a computerized solution strategy for the problem, identification of the function, to be provided by hardware, software and programmer establishing high level acceptance criteria for the system.

Page 8: Project Report Course Registration System

PROBLEM ANALYSIS: -

The basic of problem analysis is to obtain a clear understanding of the needs of users, what exactly is desired from the software analysis leads to the actual specification, analysis involves interviewing the clients & end users. These people & the existing documents about the current mode of operation are the basics source of information for the analysts. Typically analysts research a problem by asking question from users and by reading existing documents. The process of obtaining answers to question that might arise in my mind continues until I felt that all the information has been tainted, as the clients and the users do not understand or know all their needs, because the potential of the new system is often not fully appreciated although I have ensured that the real needs of the clients. And the users are covered by this project because I have played an active role of helping the clients & users to identify their needs by acting as a consultant.

ANALYSIS ISSUES:-

As analysis is the activity that feeds information to the specification activity, it is essential that during analysis a complete and consistent set of specification emerge for the system. For achieving this, the first major problem is to ob4ain the necessary information and that information can be obtained by the people and existing document as they are major source of information besides this, brainstorming between the users and the analyst also reveals the desired properties of the eventual system. During the analysis I have used some fact finding techniques to collect a massive amount of information about the problem fact finding means to learn as much as possible about the system. Fact finding is the formal process of using; sampling, interviews, research, questioners and other techniques, to collect more information about the system requirement and preferences.

SOFTWARE REQUIREMENT SPECIFICATION

The software requirement is dealing with the requirement of the proposed system, that is, the capabilities that the system which is yet to be developed, should have. It is because we are dealing with specifying system that does not exit in any form the manual form of existence does not generally have the same capability as the eventual automated system that the problem of requirement becomes complicated. This happens more in complex application where all the needs many not be know to any set of people during the requirement phase. The problem gets worse because frequently the SRS and the process of requirement analysis and specification give additional ideas to client about what is needed from the system changing requirement is a continuous irritant for software developer and frequently leads to bitterness between the user and developer through may changes come due to the changing needs of the user many of the change request have their origin in incorrect interpretation or

Page 9: Project Report Course Registration System

specification of the requirement these errors come in the SRS largely due to the requirement analysts not performing the task rigorously.

The origin of this project is in the need of a client, who either wants to automate an existing manual system or desires a new project. The proposed system itself is created by the developer. Finally, the completed system will be used by the end user. Thus, three major parties interested in a new project are the client, the user and the developer. Somehow the requirements for the system that will satisfy the needs of the clients and the concern of the user have to be communicated to the developer. The problem is that the client usually does not understand process and the parties involved

in the developed project. A basic purpose of software requirements specification is to bridge this communication gap.SRS is the medium through which the client and user needs are accurately specification; indeed SRS is the basis of software development. A good SRS should satisfy all the parties-something very hard achieve-and involves trade off and persuasion.Another important purpose of developing as SRS is helping the client understand their own need. Those software systems that are not just automating existing manual (system) requirement have to be visualized and created. Even where the primary goal is to automated of a software system, new requirements emerge as the introduction of a software system offers new potential for features, such as providing new services, performing activities in different manner, maintaining the record of new services that are either impossible or infeasible without software system.

In order to satisfy the client which is the basic quality objective of project development, the user has to be made aware of these potential and aided in visualizing and conceptualizing the needs and requirement of his organization.The process of developing an SRS usually helps in this, as it forces the users to think, visualize, interact, and discuss with others to identify the requirement therefore as SRS establish the basis for agreement between the clients and the supplier on what the software service will do. In SRS provides a reference for validation of the final service.That is the SRS helps the client determine if the project meets the requirement without a proper SRS, there is no way a client can determine if the project being delivered is what the ordered is. And there is no way the developer can convince the client that all the requirements have been fulfilled.

Page 10: Project Report Course Registration System

REQUIREMENT PROCESS:-

The requirement process is the sequence of activities that need to be performed in the requirements phase and that ultimate in providing a high- quality document containing the project requirement, where as the process ends in producing an SRS, its starting point depends on whether the project to be developed is a stand- alone project problem only or is one in which project is a component of the system that requires a combination of hardware and software.The requirement process starts when the problem has been identified or a new idea for software arises. Where a system comprising hardware and software is expected to form the solution of the problem at hand the starting point of the project is the requirement specification that are need while maintaining the record of services.The organization of this project is originally in the mind of the user and customers. I have ensured that as far as possible all the requirements of the project are detected and analyzed, clearly specified in the document describing the SRS, and that the SRS if of high quality. In the requirement phase I have faced three basic activities problem or requirements validation. The first aspect, perhaps the hardest and most nebulous that I have deal with understanding the problem, the goal, the constraints etc. During analysis the problem domain and the environment are modeled in efforts to understand the system behavior, constraints on the system, its inputs and outputs etc. The basic purpose of this activity is to obtain a through understanding of what the project needs to provide.The second activity that I have define is the requirement specification which I have focused clearly by specifying the requirement in a document, such as representation, specification language, and tools, are addressed during this activity I have produced large amount of information and

Requirements Determination:

Requirements determination involves studying the current business system to find out how it works and where improvements should be made system studies results in an evolution of how current methods are working and whether adjustments are necessary or possible. These studies consider both manual and computer methods. As we shall see; these are not merely computer studies;A requirement is a feature that must be included in a new system. It may include a way of capturing or processing data, producing information controlling a business activity, or supporting management.The determination of requirements thus entails studying the existing system and collecting details about it to find out what these requirements are it is helpful to my requirements determination through the three major activities of requirements anticipation requirements investigation and requirements specification knowledge with possible redundancies, properly organizing and describing the requirements as an important goal of this project.The final activity is focused on validity that what has specified in the SRS are indeed all the requirements of the project and making sure that the SRS is of good quality. The requirement process terminates with the services of the validated SRS. If the

Page 11: Project Report Course Registration System

objective is to define the overall broad needs of the systems the requirements can be very abstractly stated. Generally the purpose of such requirement is to perform some feasibility analysis or use the requirements for competitive bidding. At the lower level are the requirements where all the behavior are clearly specified such requirements are clearly very details and are suitable for software development it can be seen that the requirements at the lower level can be viewed as specifying the how, when viewed from the higher level of abstraction. Requirements Anticipation: It can be a missed blessing on the one hand experience from previous studies can lead to investigation of areas that would otherwise go unnoticed by an inexperienced analyst. Having the background to know what to ask or which aspect to investigate can be a substantial benefit to the organization. On the other hand, if a bias is introduced or shortcut are taken in conducting the investigation, requirements anticipation is a problem. We will point guidelines for structuring an investigation around basic questions to avoid the undesirable consequence of requirements anticipation.

Requirements anticipation It can be mixed blessing on the one hand, experience from previous studies can lead to investigation of areas that would otherwise go unnoticed by an inexperienced analyst.Having the background to know what to ask or which aspect to investigation can be a substantial benefit to the organization. On the other hand, if a bias is introduced or shortcuts are taken in conducting the investigation, requirements anticipation is a problem.We will point guidelines for structuring an investigation around basic question to avoid the undesirable consequence of requirements anticipation.

Page 12: Project Report Course Registration System

Requirements Investigation:-This activity is at the heart the system analysis. Using a variety of tools and skills, analyst studies the current. System and documents its features for further analysis. Requirements investigation relies on the fact finding techniques and includes methods for documenting and describing system features; the structured analysis strategy for requirements investigation.

Requirements Specification:-

The data produced during the fact finding investigation are analyzed to determine it, the description of features for a new system. This activity has free for interrelated parts:

Analysis of factual data- the data collection during the fact finding study include in data flow and design analysis documentation are examined to determine how well the system is performing and whether it will meet the organization demands.

Identification of the essential requirements features that must be included in a new system, ranging from operational details to performance criteria, are specified.

Selection of requirements fulfillment strategies the methods that will be used to achieve the stated requirements are selected these from basis the system design which follows requirements specification.

Page 13: Project Report Course Registration System

SYSTEM DESIGN

The design activity begins when the requirement document for the software to be developed is available. This may be the SRS for the complete system, as is the case if waterfall model is being followed or the requirements for the next” iteration” if the iterative enhancement is being followed or the requirements for the prototype if the prototyping is being followed. While the requirement specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain design is essentially the bridge between requirement specification and the final solution for satisfying the requirements.The term design is used in two ways. Used as a verb. It represents the process of design. Used as a noun, it represents the result of the design process, which is the design for the system. The goal of the design process is to produced a model or representation of a system, which can be used later to build that system. The produced model is called the design of the system. The design of a system is essentially a blue print or a plan for a solution for the system. Here was consider a system to be a set of components with clearly defined behavior that interacts with each other in a fixed defined manner to produce some behavior or services for its environment manner to produce some behavior or services for its environment. A component of a system can be considered system, with its own component. In a software system, a component is a software module. The design process for software system often has two levels .At the first level the focus is on deciding which modules are needed for the system, the specification of these modules, and how the modules should be interconnected. This is what is called the design or top design. In the second level, the internal design of the modules, or how the specification of the module can be satisfied, is decided. This design level is often called detailed design or logic design. Detailed design essentially expands the system design to contain a more detailed description of the processing logic and data structure so that the design is sufficiently complete for coding. Because the detailed design is an extension of the system design, the system design controls the major structural character tics of the system.The system design has a major impact on the testability and modifiability of a system, and it impacts its efficiency. Much of design effort for designing software is spent creating the system design.A design methodology is a systematic approach to creating a design by applying of a set of techniques and guidelines. Most design mythologies essentially offer a set of guidelines that can be used by the developer to design a system. These techniques are not formalized and do not reduced the design activity to a sequence of steps that can be followed by the designer.The input to the design phase is the specification for the system to be designed. Hence a reasonable entry criteria can be that the specification are stable and have been approved , hopping that the approval mechanism will ensure that the specification are complete, consistent, unambiguous, etc. the output of the top level design phase is the architectural design or the system design for software system to be built. This can be produced with or with out using a design methodology. Reasonable exit criteria for the phase could be that

Page 14: Project Report Course Registration System

the design has been verified against the input specification and has been evaluated approved for quality.A design can be object – oriented or function – oriented. In function – oriented design, the design consists of module definition, with each module supporting a functional abstraction. In object – oriented design, the modules in the design represent data abstraction (these abstractions are discussed in more detail later).In a function – oriented design approach, a system is viewed as transformation function, transforming the inputs to the desired outputs.The purpose of the design phase is to specified the component for this transformation function, so that each component is also a transformation function. hence, the basic output of the system design phase, when a function oriented design approach is being followed, is the definition of all the major data structures in the system , all the ,major modules of the system , and how the modules interact with each other.

OBJECTIVES IN DESIGNING:-

Requirement is translated into design specification. What does the system analysts intend to achieve when design an information system? This section describes the objective of system design and explores the nature of the design, as wall as the explicitly result expected.

System design involves first logical design and then physical construction of the system. When analysts formulate a logical design, they write the detailed section for the system; they describe its features the output, input files and database, and procedures all in a manner that meets project requirement.

The statement of this feature is turned the design specification of the system. The logical design of an information system is like the engineering blueprint of an automobile, it shows the major features (such as the engine, transmission and passenger area) and how they are related to one another (where components interconnect or how far apart the doors will be).The reports and the outputs of the analysts are like the engineers design component. Data and procedures link each together to produce a working system. Physical construction the activity following logical design, produce program software files and a working system. Design specification instructs programmers about what the system should do. The programmers in turn write the programs that accept input from users, process data, produce the report, and store data in the files. The physical design for the sample service of this project introduce above consist of programs steps, written in a programming language. These steps revise record of quantities on hand by using transaction data, print the reports and store the data. The analysts specify the algorithm for changing the stock quantities. During physical construction, programmers write the program instruction to compute the change and produce the result.

Page 15: Project Report Course Registration System

The components of an information system described during requirement analysis are the focal point in system design. Analysis must design the following elements.

Data flow – the movement of data into, around, and out of the system. Data stores – temporary or permanent collection of data. Processes –activities to accept, manipulate, and deliver data and

information, may be manual or computer based. Procedures – methods and routines for using the information system to

achieve the intend results. Controls – standards and guidelines for determining whether activities are

occurring in the anticipated or accepted manner, that is, “under control” also specifies actions to take when problems or unexpected circumstances are detected. May include the reporting of exception or procedures for correcting problems.

Roles – the responsibilities of all persons include with the new system, including end – users, computers operators and support personnel. Span the full spectrum of system components, including input of data to distribution of output or results roles are often stated in the procedures.

Design-Oriented design:Object oriented approaches are getting a lot of attention these days. Many claims have made in support of object –oriented approaches. One main claimed advantages of using object orient aches is that an object oriented model closely represents the problem domain , which makes it easier to produces and understand design

Page 16: Project Report Course Registration System

Testing

In a software development project, errors can be injected at any stage during development. For each phase, we have discussed different techniques for detecting and eliminating errors that originate in that phase. Software testing is an important element of software quality assurance and represents the ultimate review of specification, design and coding. The development software involves a series of services activities where opportunities for injection of human fallibilities are enormous. Errors may being to occur an every inception of the process where the objective may be erroneously have imperfectly specified. Because if human in ability to performed and communicate with perfection, software development is accompanied by a quality assurance activity. Testing presents an interesting anomaly for the software engineer.Earlier in the software process, the developer attempts to build software from an abstract concept to a tangible implementation. Now comes testing, the developer creates a series of test cases that are intended to” Demolish” the software that has been build. In fact testing is the in step in the software developing process that could be viewed as destructive rather than constructive. During testing, the program to be tested is executed with a set of test cases, and the output of the program for the test eases is evaluated to determine if the program is performing as expected. Due to this approach, dynamic testing can only ascertain the presence of errors in the program; the exact nature of the errors is not usually decided by testing. Testing forms step in determining the errors in program. Clearly, the success of testing in revealing errors in programs depends critically on the test cases.

Testing Information Flow:

In this test process to class inputs were taken they are; software configuration that includes software requirements specification design specification and source code.Test configuration- that includes a test plan and procedures, testing tools and test cases their expected results.The test is conducted and all results are evaluated I, e, the test results are compared with the expected results and concluded that software quality and reliability and acceptable.

Condition Testing:

Condition testing is a test case design method that exercises the logical condition contained in a program module. A simple condition is a Boolean variable or a relational expression, possibly preceded with one NOT operator. A relational expression takes the form E 1 (Relational Operator) E 2.Here E 1 and E2 Arithmetic expression. Data flow testing:

Page 17: Project Report Course Registration System

The data flow testing methods selects tests paths of a program according to the location of definitions and uses of variables in the programs. Data flow testing strategies are useful for selecting test paths of a program containing nested if and loop statements. For Data flow- based criteria, a definition used graph for the program is first constructed from the control flow graph of the program. A statement in a node in the flow graph representing a block of code has variable occurrences in it. Loop Testing:-Loops are cornerstone for the vast majority of all algorithms implemented in software. And yet be often paying them little heed while conducting testing. Loop testing is a white box testing technique that focuses exclusively on the validity look constructs.

Four different classes of loop tests are defined:a. simple loopb. concatenated loopc. nested loopd. unstructured loop

System Testing:System testing series of different tests whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose, all the work should verify that all system elements have been properly integrated and perform allocated functions. Recovery Testing:This is a system testing that force to fail in a variety of ways and verifies that recovery is prop4erly performed. If recovery is automatic re- initialization, checking pointing mechanisms, data recovery, and restart each evaluated for correctness. If recovery requires human intervention, the mean time to repair evicted to determine whether it is within acceptable limits.

SECURITY TESTING:-During this testing, the tester plays the role of the individual who desires to penetrate the system. The tester may attempts to acquire password through external clerical means and may attack the system with custom software designed to break down and defenses that have been constructed.The tester may also over view the system there by denying service to others and may purposely cause system errors to the penetrate during recovery and may browse through insecure data, hopping to the find the key to system entry.

Page 18: Project Report Course Registration System

MaintenanceOnce the software is delivered and deployed, it enters the maintenance phase. All systems need maintenance, but for other systems it is largely due to problems that are introduced due to aging, software needs to be maintained not because some of its components wear out and need to be replaced, but because there are often some residual errors remaining in the system that must be removed as they discovered. It is commonly believed that the state of the art today is such that almost all software that is developed as residual errors, or bugs, in them. Many of these surface only after the system has been in operation some times or a long time. These errors, once discovered need to be removed, leading to the software getting changed. This is sometimes called corrective maintenance. Even without bugs, project frequently under goes change the main reason is that project often must be upgraded and enhanced to include more features and provide more services. This also requires modification of the project. It has been argued that once a project system is deployed, the environment in which it operates changes.Hence, the needs that initiated the project development also change to reflect the needs of the new environment. The changed project than changes the environment, which intense requires further change. Maintenance due to this phenomenon is sometime called adaptive maintenance. Though maintenance is not considered a part of project development it is an extremely important activity in the life of the software project. Thus, maintenance involves understanding the effects of changed, because often during development, the needs of the maintainers are not kept in mind, few support documents are produced during development to help the maintainer the complexity of the maintenance task, coupled with the neglect of maintenance concerns during development, makes maintenance the most costly activity in the life of software service. The development of the project starts with the requirements documents, which is also used to determine eventually whether or not the delivered project is acceptable. It is therefore important that the requirement specification contains no errors and specifies the client’s requirements correctly. It is extremely desirable to detect errors in the requirements before the design the development of the software begin. Let us consider the type of the errors that typically occur in a SRS system Requirement Specification). Many different types of errors are possible, in the requirement specification phase. But the most common errors that occurs can be classified as four types : Omission, Inconsistency, Incorrect fact, and Ambiguity. Input design are aimed at reducing the chance of mistakes or errors during data entry. However an analyst must always assume that errors will occur. They must be found during input and corrected prior to storing or processing the data. Infect, erroneous data are frequently forgotten about until someone using a report based on those data questions their accuracy and validity.The general term given to methods aimed at detecting errors in input is INPUT VALIDATION. Three main categories of methods are concerned in this project for checking the validity. These methods are, checking the transactions, checking. The transaction data and modifying the transaction data.Checking the transaction:-

Page 19: Project Report Course Registration System

First and foremost, it is essential to iderify any transaction that are not valid, that is not acceptable. Transaction can be invalid because they are incomplete, unauthorized or even out of order. The main point which are considered in checking the validity of the transaction in the project are.Batch control :-In batch environment, the occurrence of a trasactoinAnd the time data about them are processed. As the proposed project is concerned about keeping the record of all kinds of this project collection. So, there is no consideration that how much delay is about the concerned service and sometimes the delay is acceptable to the users.When transaction are accumulated and not processed as they are occurring, there are very few chances that some entries will be misplaced, forgotten or simply over looked because keeping record of the CD’s and cassettes is a daily in a and in the proposed system separate tables are considered for keeping the records of the each service.

Transaction validation :-Sometime, user often attempt to process data in unaccepted ways, eater accidentally or intentionally. So in the concerned project several validation procedures are specified that test the acceptability of transaction.

Sequence test:-Sequence tests use codes in the data, serial numbers to test for either of the two different conditions ,depending on the characteristics of the application . in some system, the order of transaction in an important when processing to the services of the collection important to ensure that each service is processed in the order in which it arrived.If the sequence of services record of any service is mistakenly processed before the repot of other service that actually occurred first. There is little point in accepting input that is missing some items of data, since the result is storage of incomplete and erroneous information therefore input validation checks on each transaction should be made to ensure that all essential data are included. Completeness tests are one more way of validating the transaction in the concerned project. To ensure it is accurate and acceptable before any data is accepted into the system for further processing or storage.

CHECKING THE TRANSATION DATA :-Even valid transition can contain invalid data. Therefore, analyst should be sure to specify methods for validating the data when developing input procedure. In the proposed project there are some data validation methods which are considered for checking the transaction data. Existence Test :-Some data fields in transactions are designed to not be left empty or blank. Existence

tests examine those essential fields to determine that they contain data.

Page 20: Project Report Course Registration System

limit and Range Tests :- these tests verify the reasonableness of the transaction data (they can also be used to

verify theresult of processing).Limits tests validate either the maximum or minimum amount acceptable for an item.

Range tests validate both maximum and minimum values.Combination tests:-Combination tests validate that several data items jointly have acceptable values that is; the value for one element of the data determines whether other data values are correct.Modifying the transaction of data:-A third way of validating data involves modifying the data themselves. In the proposed project some methods are describe as automatic correction of errors and self checking digits on key field in modifying the transaction of data.Automatic correction:-Some times analyst specification that programs be written to correct errors in the data. This input validation methods is used to misnames

Page 21: Project Report Course Registration System

Planning and Scheduling

The planning is very important in every aspect of development work. Good manager carefully monitor developments at various phases. Improper planning leads to failure of the project. Software project plan can be viewed as the following1. within the organization:

How to implement the project? What are various constraints)? What is market strategy?

2. With respect to the customer: Weekly or timely meetings with the customer with presentation on status reports. Customer feedback is also taken and further modifications and developments are

done. Project milestones are also presented to the customer.

After making an in depth analysis of the problems and considering the various

requirements the project is planned to be complete in one and a half month. For completing the project waterfall model is selected. The waterfall model has four phases namely requirement analysis, design, coding, testing and maintenance. Thus different activities and the milestones in the system according to the waterfall model are following Activities

Requirement Gathering: In this phase all the requirements for developing the software are arranged and analyzed. This phase will require problem definition, requirement specification, software and hardware requirements etc.

Design: After analyzing the requirements the system is designed. This phase includes logical design, physical design, database design and the interface design of the system.

Coding: After designing the system the software is to be coded in any specific language for this purpose visual basic is chosen as the desired front end.

Testing: After coding the system various test cases are to be developed so that the system can be thoroughly tested and any default in the system will be reduced. For this purpose unit testing is planned to be use.

Maintenance: after going through above phases the system will be changed according to the feed back of different user. After that the system will be modified or updated Finally the system will be put into work.

Page 22: Project Report Course Registration System

Milestone

1. Start Of The Project : 10th March 20112. Requirement Gathering : 20th March 20113. Design : 5th Apr 20114. Test Cases : 10th Apr 20115. Coding : 12th Apr 20116. Testing : 15th Apr 20017. Build : 5th May 2001

Gantt Chart For The System To Be Developed

The below chart explains the tasks vs. the time they will take to complete

Tasks 20 March 5 Apr 10 Apr 15 Apr 20 Apr

Req.

Analysis

Design

Test Cases

Coding

Testing

Build

Page 23: Project Report Course Registration System

Software and Hardware Requirements

For software development very first and essential requirement is the availability of software and hardware.

The software “COURSE REGISTRATION SOFTWARE” requires the following software and hardware for its successful implementation.

SOFTWARE REQUIREMENTS

Configurations of the project Windows - 9x/ 2000/ XP Operating System Visual Basic 6.0 (Professional edition) Oracle 8+ (structured query language 8)

Here Visual Basic will be used as front end software and Oracle 8 will be used as backend (to store database)

HARDWARE REQUIREMENTS

IBM Compatible PC 128 MB RAM For Installing Oracle And Visual Basic 10 GB Of Hard Disk Monochrome 15" Monitor Writable CD ROM For Backup 132 Character 80 Cps Printer

These are the minimum requirement for working on this project, higher the hardware and software configuration will give the best quality of software.

REFERENCES

An Introduction to Database System, Bipin C.Desai, Gelgotia Publication. Software Engineering, Rogers Pressman Black Dreamtech Oracle 8i of BPB Publication

Page 24: Project Report Course Registration System
Page 25: Project Report Course Registration System
Page 26: Project Report Course Registration System
Page 27: Project Report Course Registration System
Page 28: Project Report Course Registration System
Page 29: Project Report Course Registration System
Page 30: Project Report Course Registration System
Page 31: Project Report Course Registration System
Page 32: Project Report Course Registration System
Page 33: Project Report Course Registration System
Page 34: Project Report Course Registration System
Page 35: Project Report Course Registration System
Page 36: Project Report Course Registration System
Page 37: Project Report Course Registration System
Page 38: Project Report Course Registration System
Page 39: Project Report Course Registration System
Page 40: Project Report Course Registration System
Page 41: Project Report Course Registration System
Page 42: Project Report Course Registration System
Page 43: Project Report Course Registration System

CODING OF FIRST FORM

Private Sub Timer1_Timer()

If ProgressBar1.Value < 100 Then

ProgressBar1.Value = ProgressBar1.Value + 5

End If

If ProgressBar1.Value = 100 Then

main.Show

Unload Me

End If

End Sub

Page 44: Project Report Course Registration System

CODING OF MODULE FILE

Public rs As New ADODB.RecordsetPublic con As New ADODB.Connection

Page 45: Project Report Course Registration System

CODING OF MDI FORM

Private Sub Command1_Click()Set rs = con.Execute("SELECT * FROM A WHERE ID='" & Combo1.Text & "'")Set DataReport1.DataSource = rsDataReport1.ShowEnd Sub

Private Sub Form_Load()con.Open "PROVIDER=MSDAORA.1;USER ID=SCOTT;PASSWORD=TIGER"End Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Private Sub Label1_Click()EndEnd Sub

Private Sub mnuaddition_Click()courseadd.ShowEnd Sub

Private Sub mnuadmission_Click()studentadd.ShowEnd Sub

Private Sub mnuall_Click()Set rs = con.Execute("select * from student")Set all_student_report.DataSource = rsall_student_report.ShowEnd Sub

Private Sub mnuallcourse_Click()Set rs = con.Execute("select * from course")Set all_course_detail.DataSource = rsall_course_detail.ShowEnd Sub

Private Sub mnucwise_Click()coursewise_detail.ShowEnd Sub

Page 46: Project Report Course Registration System

Private Sub mnudeleteuser_Click()userdel.ShowEnd Sub

Private Sub mnudeletion_Click()coursedelete.ShowEnd Sub

Private Sub mnudeletion1_Click(Index As Integer)studentdel.ShowEnd Sub

Private Sub mnufeedeposit_Click()FEE.ShowEnd Sub

Private Sub mnufdep_Click()fee_deposit.ShowEnd Sub

Private Sub mnumodification_Click()coursemodify.ShowEnd Sub

Private Sub mnumodification1_Click()studentmodify.ShowEnd Sub

Private Sub mnunewuser_Click()createuser.ShowEnd Sub

Private Sub mnupassword_Click()changepass.ShowEnd Sub

Private Sub mnupcourse_Click()particular_course_detail.ShowEnd Sub

Private Sub mnupstudent_Click()particular_student_detail.ShowEnd Sub

Page 47: Project Report Course Registration System

CODING OF STUDENT REGISTRATION FORM

Private Sub Combo1_Click()Set rs = con.Execute("SELECT * FROM COURSE")Text7.Text = rs.Fields("ELIGIBILITY")End Sub

Private Sub Command1_Click()Dim dob As StringDim mstatus As StringDim gen As StringDim FEE As StringIf Text9.Text = Text10.Text ThenIf Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Or Text8.Text = "" Or Text9.Text = "" Or Combo1.Text = "" Or Combo2.Text = "" Or (Option1 = False And Option2 = False) Or (Option3 = False And Option4 = False And Option5 = False) Or (Option6 = False And Option7 = False) ThenMsgBox "SOME INFORMATION MISSING"Elsedob = Format(DTPicker1.Value, "dd-MMM-yy")If Option1 = True Thengen = "Male"Elsegen = "Female"End IfIf Option3 = True Thenmstatus = "Unmarried"ElseIf Option4 = True Thenmstatus = "Married"Elsemstatus = "Divorced"End IfIf Option6 = True ThenFEE = "Check/dd"ElseFEE = "cash"End IfSet rs = con.Execute("insert into student values('" & Text1.Text & "','" & Text2.Text & "','" & Text3.Text & "','" & dob & "','" & Text4.Text & "','" & Text5.Text & "','" & Text6.Text & "','" & mstatus & "','" & gen & "','" & Combo1.Text & "','" & Combo2.Text & "')")Set rs = con.Execute("insert into student_USER values('" & Text1.Text & "','" & Text2.Text & "','" & Text8.Text & "','" & Text9.Text & "')")MsgBox "SUCCESS"Combo1.Text = ""

Page 48: Project Report Course Registration System

Combo1.Text = ""Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""Text6.Text = ""Text7.Text = ""Text8.Text = ""Text9.Text = ""Text10.Text = ""End IfElseMsgBox "PASSWORDS DONT MATCH"End IfEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select MAX(en) from student")If rs.Fields(0) <> 0 Thene = rs.Fields(0) + 1Elsee = 101End IfText1.Text = eSet rs = con.Execute("SELECT COURSE_NAME FROM COURSE")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Page 49: Project Report Course Registration System

Private Sub Text2_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End If

End Sub

Private Sub Text3_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text4_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Page 50: Project Report Course Registration System

CODING OF MODIFICATION OF A STUDENT

Private Sub Combo1_Click()Set rs = con.Execute("select * from student")Text1.Text = rs.Fields("name")Text2.Text = rs.Fields("fname")DTPicker1.Value = rs.Fields("dob")Text3.Text = rs.Fields("ph_no")Text4.Text = rs.Fields("email")Text5.Text = rs.Fields("address")Text6.Text = rs.Fields("mstatus")Text7.Text = rs.Fields("gender")Combo2.Text = rs.Fields("course")Text8.Text = rs.Fields("qualification")End Sub

Private Sub Command1_Click()Dim dob As Stringdob = Format(DTPicker1.Value, "dd-MMM-yy")If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Or Text8.Text = "" Or Combo2.Text = "" ThenMsgBox "SOME INFORMATION MISSING"ElseSet rs = con.Execute("UPDATE STUDENT SET NAME='" & Text1.Text & "',FNAME='" & Text2.Text & "',DOB='" & dob & "',PH_NO='" & Text3.Text & "',EMAIL='" & Text4.Text & "',ADDRESS='" & Text5.Text & "',MSTATUS='" & Text6.Text & "',GENDER='" & Text7.Text & "',COURSE='" & Combo2.Text & "',QUALIFICATION='" & Text8.Text & "' where en='" & Combo1.Text & "'")MsgBox "SUCCESS"Combo1.Text = ""Combo1.Text = ""Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""Text6.Text = ""Text7.Text = ""Text8.Text = ""End IfEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Page 51: Project Report Course Registration System

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select en from student")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Private Sub Text1_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text2_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text3_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text6_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElse

Page 52: Project Report Course Registration System

KEYASCII = 0End IfEnd Sub

Private Sub Text7_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Page 53: Project Report Course Registration System

CODING OF DELETION OF STUDENT

Private Sub Combo1_Click()Set rs = con.Execute("select * from student")Text1.Text = rs.Fields("name")Text2.Text = rs.Fields("fname")Text3.Text = rs.Fields("dob")Text4.Text = rs.Fields("ph_no")Text5.Text = rs.Fields("email")Text6.Text = rs.Fields("address")Text7.Text = rs.Fields("mstatus")Text8.Text = rs.Fields("gender")Text9.Text = rs.Fields("course")Text10.Text = rs.Fields("qualification")End Sub

Private Sub Command1_Click()Set rs = con.Execute("DELETE FROM STUDENT WHERE EN='" & Combo1.Text & "'")Set rs = con.Execute("DELETE FROM STUDENT_USER WHERE EN='" & Combo1.Text & "'")MsgBox "SUCCESS"Combo1.Text = ""Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""Text6.Text = ""Text7.Text = ""Text8.Text = ""Text9.Text = ""Text10.Text = ""End Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select en from student")

Page 54: Project Report Course Registration System

rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Page 55: Project Report Course Registration System

CODING OF ADDITION OF A COURSE

Private Sub Command1_Click()If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Combo1.Text = "" Or Combo2.Text = "" Or Combo3.Text = "" Or Combo4.Text = "" ThenMsgBox "SOME INFORMATION MISSING"ElseSet rs = con.Execute("INSERT INTO COURSE VALUES('" & Text1.Text & "','" & Text2.Text & "','" & Combo1.Text & "','" & Text4.Text & "','" & Combo2.Text & "','" & Combo3.Text & "','" & Combo4.Text & "','" & Combo5.Text & "')")MsgBox "SUCCESS"Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Combo1.Text = ""Combo2.Text = ""Combo3.Text = ""Combo4.Text = ""Combo5.Text = ""End IfEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select MAX(cid) from course")If rs.Fields(0) <> 0 Thene = rs.Fields(0) + 1Elsee = 1101End IfText1.Text = eCombo1.AddItem "1"Combo1.AddItem "2"Combo1.AddItem "3"Combo1.AddItem "4"Combo1.AddItem "5"Combo1.AddItem "6"

Page 56: Project Report Course Registration System

Combo1.AddItem "7"Combo1.AddItem "8"Combo2.AddItem "1"Combo2.AddItem "2"Combo2.AddItem "3"Combo2.AddItem "4"Combo3.AddItem "3"Combo3.AddItem "4"Combo3.AddItem "5"Combo3.AddItem "6"End Sub

Private Sub COMBO2_GotFocus()Text4.Text = Text3.Text * Combo1.TextEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Private Sub Text2_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text3_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Page 57: Project Report Course Registration System

CODDING OF MODIFICATION OF A COURSE

Private Sub Combo1_Click()Dim FEE As IntegerDim SEM As IntegerSet rs = con.Execute("select * from course where cid='" & Combo1.Text & "'")Text1.Text = rs.Fields("COURSE_NAME")Text2.Text = rs.Fields("SEMESTER")Text3.Text = rs.Fields("FEE")Text4.Text = rs.Fields("MIN_DURATION")Text5.Text = rs.Fields("MAX_DURATION")Text6.Text = rs.Fields("RECOGNISED_BY")Text7.Text = rs.Fields("ELIGIBILITY")End Sub

Private Sub Command1_Click()If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" ThenMsgBox "SOME INFORMATION MISSING"ElseSet rs = con.Execute("UPDATE COURSE SET COURSE_NAME='" & Text1.Text & "',SEMESTER='" & Text2.Text & "',FEE='" & Text3.Text & "',MIN_DURATION='" & Text4.Text & "',MAX_DURATION='" & Text5.Text & "',RECOGNISED_BY='" & Text6.Text & "' WHERE CID='" & Combo1.Text & "'")MsgBox "SUCCESS"Combo1.Text = ""Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""Text6.Text = ""Text7.Text = ""End IfEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Page 58: Project Report Course Registration System

Private Sub Form_Load()Set rs = con.Execute("select cid from course")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Private Sub Text1_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text2_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text3_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text4_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text5_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("0") And KEYASCII <= Asc("9") Or KEYASCII = 8 Then

Page 59: Project Report Course Registration System

ElseKEYASCII = 0End IfEnd Sub

Private Sub Text6_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Private Sub Text7_KeyPress(KEYASCII As Integer)If KEYASCII >= Asc("A") And KEYASCII <= Asc("Z") Or KEYASCII >= Asc("a") And KEYASCII <= Asc("z") Or KEYASCII = 8 ThenElseKEYASCII = 0End IfEnd Sub

Page 60: Project Report Course Registration System

CODING OF DELETION OF A COURSE

Private Sub Combo1_Click()Set rs = con.Execute("select * from course where cid='" & Combo1.Text & "'")Text1.Text = rs.Fields("COURSE_NAME")Text2.Text = rs.Fields("SEMESTER")Text3.Text = rs.Fields("FEE")Text4.Text = rs.Fields("MIN_DURATION")Text5.Text = rs.Fields("MAX_DURATION")Text6.Text = rs.Fields("RECOGNISED_BY")Text7.Text = rs.Fields("ELIGIBILITY")End Sub

Private Sub Command1_Click()Set rs = con.Execute("DELETE FROM COURSE WHERE CID='" & Combo1.Text & "'")MsgBox "SUCCESS"Combo1.Text = ""Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""Text6.Text = ""Text7.Text = ""End Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select cid from course")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeight

Page 61: Project Report Course Registration System

Image1.Width = main.ScaleWidthEnd Sub

Page 62: Project Report Course Registration System

CODING OF FEE DEPOSIT

Private Sub Combo1_Click()Set rs = con.Execute("select * from student")Text1.Text = rs.Fields("name")Text2.Text = rs.Fields("course")Text3.Text = DateEnd Sub

Private Sub Command1_Click()Dim dt As StringIf Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Combo1.Text = "" Or Combo2.Text = "" ThenMsgBox "Some Information Missing"Elsedt = Format(Text3.Text, "dd-MMM-yy")Set rs = con.Execute("insert into fee values('" & Combo1.Text & "','" & Text1.Text & "','" & Text2.Text & "','" & Combo2.Text & "','" & dt & "','" & Text4.Text & "')")MsgBox "success"End IfText1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""End Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Command3_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select en from student")While rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendCombo2.AddItem "1"Combo2.AddItem "2"Combo2.AddItem "3"Combo2.AddItem "4"Combo2.AddItem "5"

Page 63: Project Report Course Registration System

Combo2.AddItem "6"End Sub

Page 64: Project Report Course Registration System

CODING TO SHOW OF A PARTICULAR COURSE DETAIL REPORT

Private Sub Combo1_Click()Set rs = con.Execute("select * from course where cid='" & Combo1.Text & "'")Text1.Text = rs.Fields("COURSE_NAME")End Sub

Private Sub Command1_Click()Set rs = con.Execute("select * from course where cid='" & Combo1.Text & "'")Set particular_course_report.DataSource = rsparticular_course_report.ShowEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select cid from course")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Page 65: Project Report Course Registration System

CODING TO SHOW OF A PARTICULAR STUDENT DETAIL REPORT

Private Sub Combo1_Click()Set rs = con.Execute("select * from student where en='" & Combo1.Text & "'")Text1.Text = rs.Fields("NAME")End Sub

Private Sub Command1_Click()Set rs = con.Execute("select * from student where en='" & Combo1.Text & "'")Set particular_student_report.DataSource = rsparticular_student_report.ShowEnd Sub

Private Sub Command2_Click()Unload MeEnd Sub

Private Sub Form_Load()Set rs = con.Execute("select en from student")rs.MoveFirstWhile rs.EOF <> TrueCombo1.AddItem rs.Fields(0)rs.MoveNextWendEnd Sub

Private Sub Form_Resize()Image1.Height = main.ScaleHeightImage1.Width = main.ScaleWidthEnd Sub

Page 66: Project Report Course Registration System

CODDING OF ALL COURSE DETAIL REPORT

Private Sub DataReport_Initialize()all_course_detail.Sections("section1").Controls("text1").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text1").DataField = "cid"all_course_detail.Sections("section1").Controls("text2").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text2").DataField = "course_name"all_course_detail.Sections("section1").Controls("text3").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text3").DataField = "semester"all_course_detail.Sections("section1").Controls("text4").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text4").DataField = "fee"all_course_detail.Sections("section1").Controls("text5").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text5").DataField = "min_duration"all_course_detail.Sections("section1").Controls("text6").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text6").DataField = "max_duration"all_course_detail.Sections("section1").Controls("text7").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text7").DataField = "recognised_by"all_course_detail.Sections("section1").Controls("text8").DataMember = all_course_detail.DataMemberall_course_detail.Sections("section1").Controls("text8").DataField = "eligibility"End Sub

Page 67: Project Report Course Registration System

CODDING OF ALL STUDENT’S DETAIL REPORT

Private Sub DataReport_Initialize()all_student_report.Sections("section1").Controls("text1").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text1").DataField = "en"all_student_report.Sections("section1").Controls("text2").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text2").DataField = "name"all_student_report.Sections("section1").Controls("text3").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text3").DataField = "fname"all_student_report.Sections("section1").Controls("text4").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text4").DataField = "dob"all_student_report.Sections("section1").Controls("text5").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text5").DataField = "ph_no"all_student_report.Sections("section1").Controls("text6").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text6").DataField = "email"all_student_report.Sections("section1").Controls("text7").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text7").DataField = "address"all_student_report.Sections("section1").Controls("text8").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text8").DataField = "mstatus"all_student_report.Sections("section1").Controls("text9").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text9").DataField = "gender"all_student_report.Sections("section1").Controls("text10").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text10").DataField = "course"all_student_report.Sections("section1").Controls("text11").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text11").DataField = "qualification"End Sub

Page 68: Project Report Course Registration System

CODDING OF ALL STUDENT’S DETAIL REPORT (COURSEWISE)

Private Sub DataReport_Initialize()all_student_report.Sections("section1").Controls("text1").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text1").DataField = "en"all_student_report.Sections("section1").Controls("text2").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text2").DataField = "name"all_student_report.Sections("section1").Controls("text3").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text3").DataField = "fname"all_student_report.Sections("section1").Controls("text4").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text4").DataField = "dob"all_student_report.Sections("section1").Controls("text5").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text5").DataField = "ph_no"all_student_report.Sections("section1").Controls("text6").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text6").DataField = "email"all_student_report.Sections("section1").Controls("text7").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text7").DataField = "address"all_student_report.Sections("section1").Controls("text8").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text8").DataField = "mstatus"all_student_report.Sections("section1").Controls("text9").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text9").DataField = "gender"all_student_report.Sections("section1").Controls("text10").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text10").DataField = "course"all_student_report.Sections("section1").Controls("text11").DataMember = all_student_report.DataMemberall_student_report.Sections("section1").Controls("text11").DataField = "qualification"End Sub

Page 69: Project Report Course Registration System

CODDING OF A PARTICULAR STUDENT’S DETAIL REPORT

Private Sub DataReport_Initialize()DataReport1.Sections("section1").Controls("text1").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text1").DataField = "en"DataReport1.Sections("section1").Controls("text2").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text2").DataField = "name"DataReport1.Sections("section1").Controls("text3").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text3").DataField = "fname"DataReport1.Sections("section1").Controls("text4").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text4").DataField = "dob"DataReport1.Sections("section1").Controls("text5").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text5").DataField = "ph_no"DataReport1.Sections("section1").Controls("text6").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text6").DataField = "email"DataReport1.Sections("section1").Controls("text7").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text7").DataField = "address"DataReport1.Sections("section1").Controls("text8").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text8").DataField = "mstatus"DataReport1.Sections("section1").Controls("text9").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text9").DataField = "gender"DataReport1.Sections("section1").Controls("text10").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text10").DataField = "course"DataReport1.Sections("section1").Controls("text11").DataMember = DataReport1.DataMemberDataReport1.Sections("section1").Controls("text11").DataField = "qualification"End Sub

Page 70: Project Report Course Registration System

CODDING OF A PARTICULAR COURSE DETAIL REPORT

Private Sub DataReport_Initialize()particular_course_report.Sections("section1").Controls("text1").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text1").DataField = "cid"particular_course_report.Sections("section1").Controls("text2").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text2").DataField = "course_name"particular_course_report.Sections("section1").Controls("text3").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text3").DataField = "semester"particular_course_report.Sections("section1").Controls("text4").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text4").DataField = "fee"particular_course_report.Sections("section1").Controls("text5").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text5").DataField = "min_duration"particular_course_report.Sections("section1").Controls("text6").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text6").DataField = "max_duration"particular_course_report.Sections("section1").Controls("text7").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text7").DataField = "recognised_by"particular_course_report.Sections("section1").Controls("text8").DataMember = particular_course_report.DataMemberparticular_course_report.Sections("section1").Controls("text8").DataField = "eligibility"End Sub