projectorg.files.wordpress.com · Web viewI hereby declare that this project work titled “Event...

ACKNOWLEDGEMENT

With Candor and Pleasure I take opportunity to express my sincere thanks and

obligation to my esteemed guide …………. It is because of his able and mature

guidance and co-operation without which it would not have been possible for me to

complete my project.

It is my pleasant duty to thank all the staff member of the computer center who never

hesitated me from time during the project.

Finally, I gratefully acknowledge the support, encouragement & patience of my

family, and as always, nothing in my life would be possible without God, Thank You!

(Student Name)

1

DECLARATION

I hereby declare that this project work titled “Event Management System” is my

original work and no part of it has been submitted for any other degree purpose or

published in any other from till date.

2

Acknowledgment 3

Declaration 4

1. Introduction & Objectives of the Project

1.1 Introduction 8

1.2 Objectives 8

1.3 Advantage 9

1.4 Drawback of Current Manual-System 10

1.5 Proposed System 11

1.6 Need 12

2. System Study

2.1 Preliminary Investigation 19

2.2 System Development Life Cycle 20

3. System Analysis

3.1 Importance of Computerized System 24

3.2 Principle of System Analysis 25

4. System Design

4.1 System Design 28

4.2 Data Modeling 32

3

TABLE OF CONTENT

4.3 E-R Diagram 36

4.4 Context Level DFD 37

4.5 Modules 42

4.6 Report Generation 43

4.7 Tool/Platform, Hardware and Software Requirement Specification 47

4.8 Scheduling 47

5. System Development

5.1 Source Code 50

5.2 Code Efficiency 83

6. Testing

6.1 Testing Phase 85

6.2 Level of Testing 86

6.3 Test Cases 91

7. System Implementation

7.1 Post Implementation Maintenance and Review 98

7.2 Hardware Evaluation Factors 98

7.3 Software Evaluation Factors 99

7.4 Conversion and Training 100

7.5 Training Needs 101

8. Cost Estimation of the Project 102

9. GANTT & PERT CHART 103

10. Security and Validations 106

4

11. Scope of Future Application 108

12. Conclusion 109

13. Bibliography 110

14. Glossary 111

5

1. INTRODUCTION

In present era, the scopes of information technology growing with a very fast .We do

not see any are untouched from this industry. The scope of information technology

has become wider includes: Business and industry. Household Business,

Communication, Education, Entertainment, Science, Medicine, Engineering, Distance

Learning, Weather Forecasting. Carrier Searching and so on.

My project named “Event Management System” is software that store and maintained

all events coordinated in college. It also helpful to print related reports. My project

will help to record the events coordinated by faculties with their Name, Event subject,

date & details in an efficient & effective ways.

In my system we have to make a system by which a user can record all events

coordinated by a particular faculty. In our proposed system some more featured are

added which differs it from the existing system such as security.

1.2 Objectives of the project

The important objectives if this project are following:

1) To provide a graphical user interface to add or delete the information.

2) To provide the same type of easy to feel type interface to update the records.

3) To provide an interface for feeding the suggestion.

4) To store those suggestions in the database.

5) To secure the data of records in very efficient way.

6) To allow the access of data and software to only the people who are

authenticated.

7) Improved processing speed.

8) Enhance capacity to process a greater amount of activity.

9) Providing ability to conducting complex search.

10) Faster retrieval of information.

11) Grater accuracy and consistency.

12) Reducing paper work.

6

13) Reducing cost.

14) Improved arrangement for event coordination.

1.3 Drawbacks of Current Manual- System

At present the system which is not effective and efficient way.

It does not has the security and authenticity. Any user can access that system.

The existing system is not user friendly.

It does not have a menu based control which can make a system move

consistent and user friendly.

It requires on expend hand to work on.

If anyone wants to work on, then it requires a special training for this.

Unnecessary printing is too much costly.

There is no any file management technique used so it lacks it deserve high

speed data access.

No searching of records is two complex and time consuming.

7

Establish the Need Of New System

1. Problem of Reliability: Current system is not reliable. It seems to vary in quality

from one month to the next. Some times it gives good output, but some times the

output is worst.

2. Problem of Accuracy: There are too many mistakes in reports.

3. Problem of timeliness: In the current system the reports and output produced is

mostly late and in most of the cases it is useless because it is not on time.

4. Problem of Validity: The output and reports mostly contains misleading

information. The customer's information is sometimes not valid.

5. Problem of Economy: The current system is very costly. We have to spend lots

of money to keep the system up and going, but still not get the desired results.

6. Problem of Capacity: The current system is suffering from problem of capacity

also. The staff for organization is very less and the workload is too much. Few

peoples cannot handle all the work.

1.5 Proposed System

1. Details: The new proposed system stores and maintains all the faculties events, students, funds, expenses details.

2. Calculations: The new proposed system updates tables and other

information automatically and it is very fast and accurate.

3. Registers: There is no need of keeping and maintaining salary and

information manually. It remembers each and every record and we can get

any report at any time.

8

4. Speed: The new proposed system is very fast with 100% accuracy and saves time.

5. Manpower: The new proposed system needs less manpower. Less people

can do the large work.

6. Efficiency: The new proposed systems complete the work of many people in less time.

7. Past details: The new proposed system contains the details of every past

Event organized.

8. Reduces redundancy: The most important benefit of this system is that it

reduces the redundancy of data within the data.

9. Work load: Reduces the work load of the data store by helping in easy

updates of the products and providing them with the necessary details

together with financial transactions management.

10. Easy statements: Month-end and day-end statement easily taken out without

getting headaches on browsing through the day end statements.

1.6 Need

I have designed the given proposed system in the Visual Basic to automate the

process of Event Management System. This project is useful for the authorities who

keep track of all the Event Management System.

The following steps that give the detailed information of the need of proposed system

are:

Performance: During past several decades, the records are supposed to be

manually handled for all activities. The manual handling of the record is time

consuming and highly prone to error. To improve the performance of the system,

the computerized system is to be undertaken. The computerized project is fully

computerized and user friendly even that any of the members can see the report

and status of their enquiries.

9

Efficiency: The basic need of this project is efficiency. The project should be

efficient so that whenever a new user submits his/her details the project is updated

automatically. This record will be useful for other users instantly.

Control: The complete control of the project is under the hands of authorized

person who has the password to access this project and illegal access is not

supposed to deal with. All the control is under the administrator and the other

members have the rights to just see the records not to change any transaction or

entry.

Security: Security is the main criteria for the proposed system. Since illegal

access may corrupt the database. So security has to be given in this project.

SOFTWARE & HARDWARE REQUIREMENTS

Visual programming tools are complete programming environments. It allows

programmers to build a GUI program using the various on-screen controls such as

buttons, text, menus, boxes etc. These controls are placed on a form and then the

processing details related with each control are filled.

In the business world, competitive strategies have become the order of the day to

improve quality, cut costs and provide a high response customer service base. Most

organizations today need to be market driven and do a lot of value addition to their

products and services. This naturally calls for rational decision making, which

requires information. Information Technology or IT provides that effective channel to

support and implement this strategy. Client/Server is the technology that empowers

the desktop, thus setting a trend for the way successful organizations will use

technology in the next decade.

10

INTRODUCTION OF VISUAL BASIC.NET

Visual Basic .NET is one of the languages that are directed towards meeting the

objectives of the .NET initiative of creating distributed applications.

Visual Basic .NET is a powerful object-oriented language that provides features such

as abstraction, encapsulation, inheritance, and polymorphism.

Features of Visual Basic .NET

Some of the key features of Visual Basic .NET are as follows:

o Inheritance

o Constructors and destructors

o Overloading

o Overriding

o Structured exception handling

o Multithreading

Visual Studio .NET Integrated Development Environment

The Visual Studio .NET Integrated Development Environment (IDE) provides

you with a common interface for developing various kinds of projects for

the .NET Framework.

In Visual Studio .NET, an application can be made up of one or more items,

such as files and folders. To organize these items efficiently, Visual

Studio .NET has provided two types of containers:

o Projects

o Solutions

The various components of the Visual Studio .NET IDE are:

o The Start Page

o Windows Forms Designer

o The Solution Explorer Window

o The Properties Window

11

o Toolbox

o The Output Window

o The Task List Window

o The Server Explorer Window

o The Dynamic Help Window

Navigational Features in Visual Studio .NET IDE

o The Class View Window

o The Code and Text Editor Window

The Visual Studio .NET IDE also provides three navigational features:

o Docking

o Tabbed navigation

o Auto hide

Windows Form Is a representation of any window displayed in an application.

Is used to accept input from a user and display information.

Advantages of the .NET Framework Some advantages of the .NET Framework are:

o Consistent programming model

o Multi-platform applications

o Multi-language integration

o Automatic resource management

o Ease of deployment

Security Evidence-based security (authentication)

Based on user identity and code identity

Configurable policies

Imperative and declarative interfaces

12

INTRODUCTION OF SQL

Structured Query Language, is a computer language designed for the retrieval and

management of data in relational database management systems, database schema

creation and modification, and database object access control management.

SQL has been standardized originally designed as a declarative query and data

manipulation language, variations of SQL have been created by SQL database

management system (DBMS) vendors that add procedural constructs, control-of-flow

statements, user-defined data types, and various other language extensions. With the

release of the SQL: 1999 standard, many such extensions were formally adopted as

part of the SQL language via the SQL Persistent Stored Modules (SQL/PSM) portion

of the standard.

SQL has come under criticism for its lack of cross-platform portability between

vendors, inappropriate handling of missing data , complex three-valued logic system,

and its complex and occasionally ambiguous language grammar and semantics.

Using SQL one can create and maintain data manipulation objects such as table,

views, sequence etc. These data manipulation objects will be created and stroed on the

server's hard disk drive, in a tablespace, to wich the user has been assigned.

Once these data manipulation objects are created, they are used extensively in

commercial applications.

DML, DCL, DDL:

Data manipulation

First, there are the standard Data Manipulation Language (DML) elements. DML is

the subset of the language used to add, update and delete data:

INSERT is used to add rows (formally tuples) to an existing table.

UPDATE is used to modify the values of a set of existing table rows.

13

MERGE is used to combine the data of multiple tables. It is something of a

combination of the INSERT and UPDATE elements. It is defined in the SQL:2003

standard; prior to that, some databases provided similar functionality via different

syntax, sometimes called an "upsert".

DELETE removes zero or more existing rows from a table.

Data control

The third group of SQL keywords is the Data Control Language (DCL). DCL handles

the authorization aspects of data and permits the user to control who has access to see

or manipulate data within the database. Its two main keywords are:

GRANT authorizes one or more users to perform an operation or a set of

operations on an object.

REVOKE removes or restricts the capability of a user to perform an operation

or a set of operations.

Example:

GRANT SELECT, UPDATE ON my_table TO some_user, another_user

Data definition

The second group of keywords is the Data Definition Language (DDL). DDL allows

the user to define new tables and associated elements. Most commercial SQL

databases have proprietary extensions in their DDL, which allow control over

nonstandard features of the database system. The most basic items of DDL are the

CREATE, ALTER, RENAME, TRUNCATE and DROP statements:

CREATE causes an object (a table, for example) to be created within the

database.

DROP causes an existing object within the database to be deleted, usually

irretrievably.

TRUNCATE deletes all data from a table (non-standard, but common SQL

statement).

14

ALTER statement permits the user to modify an existing object in various

ways -- for example, adding a column to an existing table.

Example:

CREATE TABLE my_table (

My_field1 INT,

My_field2 VARCHAR (50),

My_field3 DATE NOT NULL,

PRIMARY KEY (my_field1, my_field2)

);

In addition to the creationof data manipulation objects, the actual manipulation of data

within these objects is done using SQL.

The SQL sentences that are used to create these objects are called DDL's or Data

Defination Language. The SQL sentences used to manipulate data within these

objects are called DML's or Data Manipulation Language. The SQL sentences, which

are used to control the behavior of these objects, are called DCL's or Data Control

Language.

Hence, once access to the SQL*Plus tool is available and SQL syntex is known, the

creation of data stroage and the manipulation of data within the storage system,

required by commercial applications, is possible.

15

2.1 PRELIMINARY INVESTIGATION

System development, a process consisting of two major steps of system analysis and

design, start when management or sometimes system development personnel feel that

a new system or an improvement in the existing system is required. The system

development life cycle is classically thought of as the set of activities that analysts,

designers and users carry out to develop and implement an information system. The

system development life cycle consists of the following activities:

Preliminary investigation

Determination of system requirements

Design of system

Development of software

System testing

Implementation, evaluation, and maintenance

A request to take assistance from information system can be made for many

reasons, but in each case someone in the organization initiates the request is

made, the first system activity the preliminary investigation begins. This activity

has three parts:

1) Request clarification

2) Feasibility study

3) Request approval

Request clarification: Many requests from employees and users in the

organizations are not clearly defined, therefore it becomes necessary that

project request must be examined and clarified properly before considering

systems investigation.

17

2.2 SYSTEM DEVELOPMENT LIFE CYCLE

Systems are created to solve problems. One can think of the systems approach as an

organized way of dealing with a problem. In this dynamic world, the subject System

Analysis and Design (SAD), mainly deals with the software development activities.

DEFINING A SYSTEM:-

A collection of components that work together to realize some objective forms a

system. Basically there are three major components in every system, namely input,

processing and output.

In a system the different components are connected with each other and they are

interdependent. For example, human body represents a complete natural system. We

are also bound by many national systems such as political system, economic system,

educational system and so forth. The objective of the system demands that some

output is produced as a result of processing the suitable inputs.

SYSTEM LIFE CYCLE:-

System life cycle is an organizational process of developing and maintaining

systems. It helps in establishing a system project plan, because it gives overall list of

processes and sub-processes required for developing a system.

System development life cycle means combination of various activities. In other

words we can say that various activities put together are referred as system

development life cycle. In the System Analysis and Design terminology, the system

development life cycle means software development life cycle.

Following are the different phases of software development cycle:

System study

Feasibility study

System analysis

System design

Coding

18

Testing

Implementation

Maintenance

The Different Phases Of Software Development Life Cycle Are Shown Below.

PRELIMINARY INVESTIGATION

DETERMINATION OF REQUIREMENTS

REVIEW RUNNING SYSTEM AND SYSTEM

MAINTENANCE

SYSTEM IMPLEMENTATION

SYSTEM TESTINGDEVELOPMENT OF

SOFTWARE AND CODING

DESIGN OF SYSTEM

DEVELOPMENT OF PROTOTYPE SYSTEM

SYSTEM ANALYSIS50% DESIGN

DESIGN OF SYSTEM 30%

CODING 20%

19

FIG: SHOWING GENERAL LIFE CYCLE PROCESS AND PERCENTAGE OF TIME DEVOTED

A system analysis is a separation of a substance into parts for study and their

implementation and detailed examination.

Before designing any system it is important that the nature of the business and the

way it currently operates are clearly understood. The detailed examination provides

the specific data required during designing in order to ensure that all the client's

requirements are fulfilled. The investigation or the study conducted during the

analysis phase is largely based on the feasibility study. Rather it would not be wrong

to say that the analysis and feasibility phases overlap. High-level analysis begins

during the feasibility study. Though analysis is represented as one phase of the

system development life cycle (SDLC), this is not true. Analysis begins with system

initialization and continues until its maintenance. Even after successful

implementation of the system, analysis may play its role for periodic maintenance

and up gradation of the system.

One of the main causes of project failures is inadequate understanding, and one of

the main causes of inadequate understanding of the requirements is the poor

planning of system analysis.

Analysis requires us to recall the objectives of the project and consider following

three questions:

What type of information is required?

What are the constraints on the investigation?

What are the potential problems that may make the task more

difficult?

20

3.1 IMPORTANCE OF COMPUTERIZED EVENT MANAGEMENT SYSTEM

The system if fully user friendly.

Since it is developed in menu based category which baring an interative

environment.

This is having very easy understandable facilities.

It does not require expert hand-the data entry in the software can be done by

anybody, since it handles any error occurred with a reliable message which

guide even a raw hand to sort out the error.

Paper work is reduced-since there is no unnecessary printing, photo copying of

the document.

Faster access of information- As the system will use as it database, the

information can be accesses quickly and since the system will be run on

standalone machine the retrieval can be done round the clock with greater

Easy to find the installment payment-The system which is working previously

is unable to find anything about to manintain it. But now, in the now system it

will itself maintain it.

Faster processing.

Provides immediate reports.

More availiblity of details.

Security of records.

Time saving

Better planning and control

Better service to all

Analyzing Modeling

Analyzing modeling uses a combination of text and diagram to depict data, function

and behavior requirements. At the core of model, there is a data dictionary. It contains

all the data objects used or produced by the project.

Entity relationship diagram depicts the relation between data objects.

Data flow diagram depicts that how is transformed in the system.

22

It serves both data modeling and functional modeling. Description of each function

lies in process specification(PSPEC).State transition diagram serves behavioral

modeling. The control aspects are contained in control specification (CSP

3.2 PRINCIPLES OF SYSTEM ANALYSIS

Principles:

1. Understand the problem before you begin to create the analysis model.

2. Develop prototypes that enable a user to understand how human machine

interaction will occur.

3. Record the origin of and the reason for every requirement.

4. Use multiple views of requirements like building data, function and behavioral

models.

5. Work to eliminate ambiguity.

A Complete Structure:

The limited time and resources have restricted us to incorporate, in this project, only

the main activities that are performed in news sites, but utmost care has been taken to

make the system efficient and user friendly.

For the optimum use of practical time it is necessary that every session is planned.

Planning of this project will include the following things:

Topic Understanding. Modular Break – Up of the System. Processor Logic for Each Module. Database Requirements.

Topic Understanding:

It is vital that the field of application as introduced in the project may be totally a new

field. So as soon as the project was allocated to me, I carefully went through the

project to identify the requirements of the project.

23

Modular Break –Up of the System:

Identify The Various Modules In The System.

List Them In The Right Hierarchy.

Identify Their Priority Of Development

Description Of The Modules:

24

4.1 SYSTEM DESIGN

The design document that we will develop during this phase is the blueprint of the

software. It describes how the solution to the customer problem is to be built. Since

solution to complex problems isn’t usually found in the first try, iterations are most

likely required. This is true for software design as well. For this reason, any design

strategy, design method, or design language must be flexible and must easily

accommodate changes due to iterations in the design. Any technique or design needs

to support and guide the partitioning process in such a way that the resulting sub-

problems are as independent as possible from each other and can be combined easily

for the solution to the overall problem. Sub-problem independence and easy

combination of their solutions reduces the complexity of the problem. This is the

objective of the partitioning process. Partitioning or decomposition during design

involves three types of decisions: -

Define the boundaries along which to break;

Determine into how money pieces to break; and

Identify the proper level of detail when design should stop and implementation should

start.

Basic design principles that enable the software engineer to navigate the design

process suggest a set of principles for software design, which have been adapted and

extended in the following list:

Free from the suffer from "tunnel vision." A good designer should consider

alternative approaches, judging each based on the requirements of the problem, the

resources available to do the job.

The design should be traceable to the analysis model. Because a single element of the

design model often traces to multiple requirements, it is necessary to have a means for

tracking how requirements have been satisfied by the design model.

26

The design should not repeat the same thing. Systems are constructed using a set of

design patterns, many of which have likely been encountered before. These patterns

should always be chosen as an alternative to reinvention. Time is short and resources

are limited! Design time should be invested in representing truly new ideas and

integrating those patterns that already exist.

The design should "minimize the intellectual distance" between the software and the

problem as it exists in the real world. That is, the structure of the software design

should (whenever possible) mimic the structure of the problem domain.

The design should exhibit uniformity and integration. A design is uniform if it appears

that one person developed the entire thing. Rules of style and format should be

defined for a design team before design work begins. A design is integrated if care is

taken in defining interfaces between design components.

The design activity begins when the requirements document for the software to be

developed is available. This may be the SRS for the complete system, as is the case if

the 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 requirements 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 requirements

specification and the final solution for satisfying the requirements.

The design of a system is essentially a blueprint or a plan for a solution for the

system. We 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. A component of a system can be considered a system,

with its own components. In a software system, a component is a software module.

The design process for software systems, often, has two levels. At the first level, the

focus is on deciding which modules are needed for the system, the specifications of

these modules, and how the modules should be interconnected. This is what is called

27

the system design or top-level design. In the second level, the internal design of the

modules, or how the specifications 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 structures so that the design is sufficiently complete for coding.

Because the detailed design is an extension of system design, the system design

controls the major structural characteristics 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 the design effort for designing software is spent creating the

system design.

The input to the design phase is the specifications for the system to be designed.

Hence, reasonable entry criteria can be that the specifications are stable and have been

approved, hoping that the approval mechanism will ensure that the specifications are

complete, consistent, unambiguous, etc. The output of the top-level design phase is

the architectural design or the system design for the software system to be built. This

can be produced with or without using a design methodology. Reasonable exit criteria

for the phase could be that the design has been verified against the input specifications

and has been evaluated and approved for quality.

A design can be object-oriented or function-oriented. In function-oriented design, the

design consists of module definitions, 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 the function-

oriented methods for design and describe one particular methodology the structured

design methodology in some detail. In a function- oriented design approach, a system

is viewed as a transformation function, transforming the inputs to the desired outputs.

The purpose of the design phase is to specify the components 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.

28

Once the designer is satisfied with the design he has produced, the design is to be

precisely specified in the form of a document. To specify the design, specification

languages are used. Producing the design specification is the ultimate objective of the

design phase. The purpose of this design document is quite different from that of the

design notation. Whereas a design represented using the design notation is largely to

be used by the designer, a design specification has to be so precise and complete that

it can be used as a basis of further development by other programmers. Generally,

design specification uses textual structures, with design notation helping in

understanding

29

4.2 DATA MODELING

Data modeling defines primary data objects, composition of each data object,

and attributes of the object, relationships between each object and other objects

and between objects and the processes.

List of Tables:

Admin Table: To store admin username and password.

Fields Type Constraint DescriptionUsername Char(30) Not Null UsernamePassword Char(30) Not Null Password

Users Table: To store users details. The users are managed by admin.

Fields Type Constraint DescriptionUsername Char(30) Not Null UsernamePassword Char(30) Not Null PasswordEmail Char(30) Not Null Email Id

Students: To store student details

Fields Type Constraint DescriptionReg no. Char(30) Primary Key Registration No.Name Char(30) Not Null NameAddress Char(30) Not Null AddressContact_no Char(30) Not Null Contact NoReg.Amount Number Not Null Registration

AmountTotal Fee Number(5) Not Null Total FeeReg_date Date Not Null Registration DateDescription Char(30) Not Null Description

Faculty: To store faculty details

Fields Type Constraint DescriptionID Char(30) Primary Key IdName Char(30) Not Null NameAddress Char(30) Not Null AddressCity Char(30) Not Null CityState Char(30) Not Null StateSubject Char(30) Not Null SubjectSpecialization Char(30) Not Null SpecializationQualification Char(30) Not Null Qualification

30

Funds: To store funds details.

Fields Type Constraint DescriptionTransaction_Id Char(30) Primary Key TransactionDonor Char(50) Not Null DonorAmount Number(6) Not Null AmountDate_of_deps Date Not Null Date

Expenses: To store details of the expenses for event Management system.

Fields Type Constraint DescriptionExpenses_amount Number(8) Not Null Expenses amountDate_of_withdrawl Date Not Null Date of withdrawlDescription Char(200) Not Null Description

Event: To store event Details

Fields Type Constraint DescriptionEvent_Id Char(30) Primary Key Event IDEvent_Name Char(50) Not Null Event NameSubject Char(50) Not Null SubjectFaculty_name Char(50) Not Null Arranged by

FacultyDate_of_event Date Not Null Date of eventTime Char(30) Not Null Time

31

4.3 ENTITY RELATIONSHIP DIAGRAM (ERD)

Entity – Relationship Diagram: This depicts relationship between data objects. The

attribute of each data objects noted in the entity- relationship diagram can be

described using a data object description. Data flow diagram serves two purposes:

1. To provide an indication of how data are transformed as they move through the

system.

2. To depict the functions that transformation the data flow.

Data Objects: A data object is a representation of almost any composite information

that must be understood by the software. By composite information, we mean

something that has a number of different properties or attributes. A data object

encapsulates data only there is no reference within a data object to operations that act

on the data.

Attributes: Attributes define the properties of a data object and take on one of three

different characteristics. They can be used to:

Name an instance of data object.

Describe the instance.

Make reference to another instance in other table.

Relationships: Data objects are connected to one another in a variety of different

ways. We can define a set of object relationship pairs that define the relevant

relationships.

32

CARDINALITY AND MODALITY:

Cardinality:

The data model must be capable of representing the number of occurrences of objects

in a given relationship. The cardinality of an object relationship pair is

One-T0-One (1:1): An occurrence of object ‘A’ can relate to one

and only one occurrence of object ‘B’ and vice versa.

One-To-Many (1:N): One occurrence of object ‘A’ can relate to

one or may occurrences of object ‘B’ but an occurrence of object

‘B’ can relate to only one occurrence of object ‘A’.

Many-To-Many (M: N): An occurrences of ‘B’ and an occurrence

of ‘B’ can relate to one or many occurrence of ‘A’.

Modality:

The modality of a relationship is zero if there is no explicit need for the relationship to

occur or the relationship is optional. The Modality is one if the occurrence of the

relationship is mandatory.

The object relationship pair can be represented graphically using the Entity

Relationship Diagrams. A set of primary components are identified for the Entity

Relationship Diagram,

1. Attributes,

2. Relationships and

3. Various Type Indicators.

The primary purpose of the Entity Relationship Diagram is to represent data objects

and their relationships.

33

E-R DIAGRAM

34

4.4. DATA FLOW DIAGRAM

CONTEXT LEVEL DFD FOR EVENT MANAGEMENT SYSTEM

35

EVENT

MANAGEMENT

SYSTEM

1.ADMIN

2.STUDENT 3.

FACULTY

4.ADD EVENT

5.BUDGET OF

EVENT

6.EVENT

SCHEDULER

Ist Level DFD for Admin

36

ADMIN

1.1 Accept the user name &

Password

1.2 Validate

the Admin

EVENT MANAGEMENT

SYSTEM

ADMIN

Ist Level DFD For the students

37

STUDENT

2.2 Accept

the student details

2.2 Validate students

EVENT MANAGEMENT

SYSTEM

2.4 update

students

2.4 Update students

2.3 Faculty

Managers Even

STUDENT

FACULTY

EVENTS

Ist Level DFD for the Faculty

38

FACULTY

3.1 Accept

the Faculty Details

3.2Validate Faculty

EVENT MANAGEMENT

SYSTEM

3.3 Faculty manages

the Student &

Events

FACULTY

EVENS

Ist Level DFD For event Management

39

ADMIN

4.1 Accept

the Event Requests

4.2 Validate

the Events

EVENT MANAGEMENT

SYSTEM

4.4 Approved Budget & Expenses

4.3 Coordinate Faculty

4.5 Coordina

te Students

Event

Students

FacultyS

4.5 MODULES

Project Plan, Design & Approach

The proposed project will have its main page and will be mainly divided into partially

dependent and partially independent modules as:

1. LOGIN FORM

2. MDI FORM

3. ENTRY FORM

4. DISPLAY FORM

**These modules are described below**

1. LOGIN MODULE

It is first form that is displayed on the display form if user wants to

edit information into the display form. Here the user has to give his login detail to the

system. It consists of one combo box and one text boxes. When the faculty wants to

edit information in the display form has to give his password. Password will be

hidden to the external viewer.

Along with then the form has two buttons, “OK” and “EXIT”. Clicking on “OK”, the

execution moves forward to the second form.

2. MDI FORM

MDI Form is the form in the execution line. All the other forms in project are linked

together by this from only. Pathways to all the other forms go through this module.

This form consists of two options buttons, that is labeled as “open” and “EXIT”.

Users first have to select one of the options that is desired by user. Clicking on any of

the button takes the user to form according to the option selected .Clicking on “Exit”

ends the execution.

40

3. ENTRY FORM

ENTRY form consists of one combo box, five text boxes in the form,

the users has to give the details of new records to be added. He can specify the

category by combo box and also fill up the text boxes provided under the heading of

software details and hardware details of a particular lab. For the purpose of adding

new record and removing record buttons” NEW”,“DELETE” and are provided.

Clicking on “PREVIOUS” or “NEXT” button in the form all entries in the database

are viewed on and “EXIT” clicking will be send back the user to main login form.

4. SEARCH MODULE

Display form contains a data grid to display the faculty’s even

records. Data Grid contains six records. It also contains two commands “edit” and

“exit”. By edit command we can edit information in the Entry form and by “exit”

clicking will be send back the user to main to MDI Form.

Project can be divide in to the following types:-

The proposed system can be divided into the following modules-

1) Login Module- This module is created for security purpose, so, it is

authentication module in which an user authenticate by username

and password.

2) Faculty Module-This is faculty module that contain complete

infromation of faculties coordinated events.

3) Event Module-This is event module that store complete

information of all events.

41

Input to the project

Login Module- This is first module in the project used as authentication module. This

module takes following input-

User Name

Password

Type

Faculty Module-This module contains information of event coordinator faculties. It

takes the following input.

Faculty Id

Faculty Name

Address

Phone No

Subject

Event Module-this module contain complete information for coordinated event. It

takes the following inputs.

Event Id

Event Name

Event Subject

Faculty Name

Date

Time

Output of the project

42

Login Module: Enter username and password and get MDI form if valid.

Faculty Module: Enter faculty Id and get complete information of faculty such as

name, address, phone no. and subject, if valid.

Event Module: Enter event ID or Event name to get and complete information of

coordinated event such as date, time, name and coordinator name.

43

4.6 Report Generation

Data report provides data access from lot of data source like Access, oracle, Dbase,

Sybase, Paradox and SQL Server.

Data report can public report the window in a variety of formats, data report can be

integrated with visual basic.net.

Data report access data through

1. Direct database file.

2. ODBC

3. Data report Query designer file

4. Data report dictionary file.

Features of data report

Data report is an excellent reporting tool, which can be used to prepare

efficient and professional looking reports writing.

Data reports remains the market leader and defects standard for business and

corporate report writing.

Data report now bundled over 150 leading software packages including

Microsoft back office & visual studio packages together with ERP and

accounting packages from different vendors.

Data report developer interface have been designed to work with most popular

windows development tools.

The following reports will print through Data report

Faculty report- this report contain complete information of faculty that coordinated

the events.

Event report-This report show the complete information about event.

44

4.7 TOOLS / PLATFORM, HARDWARE AND SOFTWARE REQUIREMENT SPECIFICATION

HARDWARE:

Processor : Pentium 2.4 GHz or above

Memory : 256 MB RAM or above

Cache Memory : 128 KB or above

Hard Disk : 3 GB or above [at least 3 MB free space required

Pen Drive : 2 GB

Printer : Laser Printer

SOFTWARE:

Operating System : Windows 95/98, Win NT, Win 2000.

Font-End Tool : VB.NET

Back End Tool : SQL SERVER

4.8 SCHEDULING

Scheduling of a software project does not differ greatly from scheduling of any multi-

task engineering effort. Therefore, generalized project scheduling tools and

techniques can be applied with little modification to software projects.

Program evaluation and review technique (PERT) and critical path method (CPM) are

two project scheduling methods that can be applied to software development. Both

techniques are driven by information already developed in earlier project planning

activities.

45

Estimates of Effort:-

A decomposition of the product function.

The selection of the appropriate process model and task set.

Decomposition of tasks.

Interdependencies among tasks may be defined using a task network. Tasks,

sometimes called the project Work Breakdown Structure (WBS) are defined for the

product as a whole or for individual functions.

Both PERT and CPM provide quantitative tools that allow the software planner to (1)

determine the critical path-the chain of tasks that determines the duration of the

project; (2) establish "most likely" time estimates for individual tasks by applying

statistical models; and (3) calculate "boundary times" that define a time window" for a

particular task.

Boundary time calculations can be very useful in software project scheduling.

Slippage in the design of one function, for example, can retard further development of

other functions. It describes important boundary times that may be discerned from a

PERT or CPM network: (I) the earliest time that a task can begin when preceding

tasks are completed in the shortest possible time, (2) the latest time for task initiation

before the minimum project completion time is delayed, (3) the earliest finish-the sum

of the earliest start and the task duration, (4) the latest finish- the latest start time

added to task duration, and (5) the total float-the amount of surplus time or leeway

allowed in scheduling tasks so that the network critical path maintained on schedule.

Boundary time calculations lead to a determination of critical path and provide the

manager with a quantitative method for evaluating progress as tasks are completed.

Both PERT and CPM have been implemented in a wide variety of automated tools

that are available for the personal computer. Such tools are easy to use and take the

scheduling methods described previously available to every software project manager.

46

5.1 Source Code

Login Form

Imports System.Data.SqlClient

Public Class login Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub ok_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ok.Click Call start() DA = New SqlDataAdapter("SELECT * FROM users where username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "' ", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB)

ROWNO = 0 Dim s1 As String = Trim(DATATAB.Rows(ROWNO)(0).ToString) Dim s2 As String = Trim(DATATAB.Rows(ROWNO)(1).ToString)

If TextBox1.Text = s1 And TextBox2.Text = s2 Then uname = TextBox1.Text uid = TextBox2.Text

Dim obj As New menu obj.Show() Me.Hide() Else MsgBox("invalid Password") TextBox1.Text = "" TextBox2.Text = ""

48

TextBox1.Focus() End If CN.Close()

End Sub

Private Sub TextBox2_Validating(ByVal sender As System.Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles TextBox2.Validating If TextBox2.Text = "" Then MsgBox("Password Should not be blank") TextBox2.Focus() End If If Len(TextBox2.Text) > 8 Then MsgBox("Password should be of maximum 8 character") TextBox2.Text = "" TextBox2.Focus() End If

End Sub

Private Sub TextBox1_Validating1(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles TextBox1.Validating If TextBox1.Text = "" Then MsgBox("UserName Should not be blank") TextBox1.Focus() End If If Len(TextBox1.Text) > 8 Then MsgBox("UserName should be of maximum 8 character") TextBox1.Text = "" TextBox1.Focus() End If End Sub

Private Sub Panel2_Paint(ByVal sender As System.Object, ByVal e As System.Windows.Forms.PaintEventArgs) Handles Panel2.Paint

End Sub

Private Sub login_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End SubEnd Class

49

MDI Form

Imports System.Windows.Forms

Public Class menu

Private Sub AdminToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Student.Click Dim obj As New student obj.MdiParent = Me obj.Show() End Sub

Private Sub AboutCCMSToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Dim obj As New frmAboutus

obj.MdiParent = Me obj.Show() End Sub

Private Sub menu_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub EnterpriseRecordToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Dim obj As New UPDATESTUDENT

50


Private Sub Courses_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Courses.Click Dim obj As New DELSTUDENT obj.MdiParent = Me obj.Show() End Sub

Private Sub AdminToolStripMenuItem_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles AdminToolStripMenuItem.Click Dim obj As New frmmaster


Private Sub CheckStatusToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CheckStatusToolStripMenuItem.Click End End Sub

Private Sub StudentToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles StudentToolStripMenuItem.Click Dim obj As New Enquiry Type = "Student" obj.MdiParent = Me obj.Show() End Sub

Private Sub FacultyToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Dim obj As New Enquiry type = "Faculty" obj.MdiParent = Me obj.Show() End Sub

Private Sub ConfirmAddmissionToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ConfirmAddmissionToolStripMenuItem.Click Dim obj As New eventdet obj.MdiParent = Me obj.Show() End Sub

Private Sub StudentsDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles StudentsDetailsToolStripMenuItem.Click Dim obj As New STUDENT_REPO

obj.MdiParent = Me

51

obj.Show() End Sub

Private Sub FacultyToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Dim obj As New faculty_repo obj.MdiParent = Me obj.Show() End Sub

Private Sub GroupsDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Dim obj As New GROUP_REPO obj.MdiParent = Me obj.Show() End Sub

Private Sub AddDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles AddDetailsToolStripMenuItem.Click End Sub

Private Sub ADDNewEventsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ADDNewEventsToolStripMenuItem.Click Dim obj As New Addevent obj.MdiParent = Me obj.Show() End Sub

Private Sub UpdateDeleteEventsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles UpdateDeleteEventsToolStripMenuItem.Click Dim obj As New delupdate obj.MdiParent = Me obj.Show() End Sub

Private Sub EnquiryDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles EnquiryDetailsToolStripMenuItem.Click Dim obj As New faculty_repo


Private Sub UserManagerToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles UserManagerToolStripMenuItem.Click

End Sub

52

Private Sub FacultyDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles FacultyDetailsToolStripMenuItem.Click Dim obj As New Enquiry obj.MdiParent = Me obj.Show() End Sub

Private Sub CourseDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CourseDetailsToolStripMenuItem.Click Dim obj As New Enquiry obj.MdiParent = Me obj.Show() End Sub

Private Sub AddToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles AddToolStripMenuItem.Click Dim obj As New Funds obj.MdiParent = Me obj.Show() End Sub

Private Sub ExpensesDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ExpensesDetailsToolStripMenuItem.Click Dim obj As New Expenses obj.MdiParent = Me obj.Show() End Sub

Private Sub ExpensesToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ExpensesToolStripMenuItem.Click Dim obj As New Expenses_repo obj.MdiParent = Me obj.Show() End Sub

Private Sub FundDepositedToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles FundDepositedToolStripMenuItem.Click Dim obj As New Funds_repo obj.MdiParent = Me obj.Show() End SubEnd Class

53

Student add details


Public Class student Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub student_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from STUDENT", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB)

da1 = New SqlDataAdapter("select * from course", CN) cm1 = New SqlCommandBuilder(da1) da1.Fill(datatab1) combobox1.datasource = datatab1 ComboBox1.DisplayMember = "course_id"

da2 = New SqlDataAdapter("select * from groupi", CN) cm2 = New SqlCommandBuilder(da2) da2.Fill(datatab2) ComboBox2.DataSource = datatab2 ComboBox2.DisplayMember = "group_id"

TextBox1.Text = "E001" & DATATAB.Rows.Count + 1

CN.Close() ROWNO = 0

54

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox10.Text = "" Or TextBox7.Text = "" Or TextBox11.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1 newrow(0) = TextBox1.Text newrow(1) = TextBox2.Text

newrow(2) = TextBox3.Text newrow(3) = TextBox4.Text


newrow(6) = TextBox7.Text newrow(7) = ComboBox1.Text

newrow(8) = ComboBox2.Text newrow(9) = TextBox10.Text

newrow(10) = TextBox11.Text

DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA INSERTED") TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" 'TextBox8.Text = "" 'TextBox9.Text = "" TextBox10.Text = "" TextBox11.Text = ""

CN.Close() DATATAB.Clear() start() DA = New SqlDataAdapter("select * from STUDENT", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "E001" & DATATAB.Rows.Count + 1

CN.Close() ROWNO = 0

55

End If End If End SubEnd Class

Del student


Public Class DELSTUDENT Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If (MessageBox.Show("Do You want to DELETE this Record from your Database", "DELETE", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then

start() Dim CMD As SqlCommand = New SqlCommand("DELETE FROM STUDENT WHERE REG_NO='" & TextBox1.Text & "'", CN) CMD.ExecuteNonQuery() CN.Close() MsgBox("Record Deleted") TextBox1.Text = ""

End If End Sub

End Class

56

Admin Login


Public Class frmmaster Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub frmmaster_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object, ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles LinkLabel1.LinkClicked Dim obj As New newusers obj.Show() End Sub

Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Call start() DA = New SqlDataAdapter("SELECT * FROM admin where username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "' ", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB)

57


If TextBox1.Text = s1 And TextBox2.Text = s2 Then Panel1.Visible = False Panel2.Visible = True Else MsgBox("invalid Password") TextBox1.Focus() End If CN.Close() End Sub

Private Sub LinkLabel4_LinkClicked(ByVal sender As System.Object, ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles LinkLabel4.LinkClicked Dim obj As New changepass obj.Show() End Sub

End Class

Master login


58

Public Class frmmaster Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub frmmaster_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object, ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles LinkLabel1.LinkClicked Dim obj As New newusers obj.Show() End Sub

Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Call start() DA = New SqlDataAdapter("SELECT * FROM admin where username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "' ", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB)


If TextBox1.Text = s1 And TextBox2.Text = s2 Then Panel1.Visible = False Panel2.Visible = True Else MsgBox("invalid Password") TextBox1.Focus() End If CN.Close() End Sub

Private Sub LinkLabel4_LinkClicked(ByVal sender As System.Object, ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs) Handles LinkLabel4.LinkClicked Dim obj As New changepass obj.Show() End Sub

End Class

59

New user


Public Class newusers Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub ok_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ok.Click If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox1.Text = "" Or TextBox2.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1 newrow(0) = TextBox1.Text newrow(1) = TextBox2.Text

DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA UPDATED") CN.Close() End If End If End Sub

Private Sub newusers_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from users", CN)

60

CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 End Sub

Private Sub SHOWCURRENTRECORD() If rowno = datatab.Rows.Count Then TextBox1.Text = "" TextBox2.Text = ""

Else TextBox1.Text = DATATAB.Rows(ROWNO)(0).ToString TextBox2.Text = DATATAB.Rows(ROWNO)(1).ToString End If End SubEnd Class

61

Change password


Public Class changepass Private Sub conpassword_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles conpassword.Click Panel1.Visible = True Panel1.Location = New System.Drawing.Point(80, 32) Panel2.Visible = False End Sub

Private Sub change_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles change.Click start()

Dim up As New SqlCommand("update users set password='" & TextBox2.Text & "' where username='" & TextBox1.Text & "'", CN) DA.UpdateCommand = up

DA.UpdateCommand.ExecuteNonQuery()

MsgBox("PASSWORD CHANGED") conpassword.Visible = True CN.Close() End Sub

Private Sub ok_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ok.Click start() DA = New SqlDataAdapter("SELECT * FROM users where password='" & TextBox4.Text & "' and username='" & TextBox3.Text & "'", CN) CM = New sqlCommandBuilder(DA) DA.Fill(DATATAB) ROWNO = 0

62

If DATATAB.Rows.Count > 0 Then

Me.Hide() Dim obj As New menu

obj.Show() Else MsgBox("invalid Password") End If CN.Close() End Sub

Private Sub changepass_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("SELECT * FROM users", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() End Sub

End Class

63

Enquiry form


Public Class Enquiry Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Enquiry_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from faculty", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "E001" & DATATAB.Rows.Count + 1 CN.Close() ROWNO = 0 End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox8.Text = "" Or TextBox7.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1 newrow(0) = TextBox1.Text newrow(1) = TextBox2.Text

64




DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA INSERTED") TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" CN.Close() start() DATATAB.Clear() DA = New SqlDataAdapter("select * from ENQUIRY", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "E001" & DATATAB.Rows.Count + 1 CN.Close() ROWNO = 0 End If End If End Sub

Private Sub Label1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Label1.Click

End Sub


End Sub


End Sub


End Sub


End Sub

65


End Sub


End Sub


End Sub


End Sub

Private Sub TextBox8_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox8.TextChanged

End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End SubEnd Class

66

Events details

Imports SystemImports System.Data.SqlClient

Public Class eventdet Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click MsgBox(ComboBox1.Text & ComboBox1.SelectedIndex) Dim s As String = ComboBox1.Text Dim sql As String = "" Select Case ComboBox1.SelectedIndex Case 0 sql = "select * from event where event_id='" & TextBox1.Text & "'" Case 1 sql = "select * from event where event_name='" & TextBox1.Text & "'"

Case 2 sql = "select * from event where event_sub='" & TextBox1.Text & "'"

Case 3 sql = "select * from event where dat='" & TextBox1.Text & "'"

67

End Select DATATAB.Clear()

start() DA = New SqlDataAdapter(sql, CN) CM = New SqlCommandBuilder(DA) DATATAB.Clear() DA.Fill(DATATAB) CN.Close() ROWNO = 0

TextBox7.Text = DATATAB.Rows(ROWNO)(0).ToString TextBox2.Text = DATATAB.Rows(ROWNO)(1).ToString TextBox3.Text = DATATAB.Rows(ROWNO)(2).ToString TextBox4.Text = DATATAB.Rows(ROWNO)(3).ToString TextBox5.Text = DATATAB.Rows(ROWNO)(4).ToString TextBox6.Text = DATATAB.Rows(ROWNO)(5).ToString

End Sub

End Class

Add new events


Public Class Addevent Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

68

If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or TextBox5.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1 newrow(0) = TextBox1.Text newrow(1) = TextBox2.Text


newrow(4) = TextBox5.Text newrow(5) = TextBox6.Text DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA INSERTED") TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = ""

CN.Close() End If End If End Sub

Private Sub Addevent_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load TextBox1.Text = regno

start() DA = New SqlDataAdapter("select * from event", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 End Sub


End Sub


End Sub


End Sub

69


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End Sub


End SubEnd Class

70

Delete update form


Public Class delupdate Dim DATATAB, datatab1, datatab2 As New DataTable


If (MessageBox.Show("Do You want to update this Record", "DELETE", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then

start() Dim CMD As SqlCommand = New SqlCommand("update event set event_name='" & TextBox2.Text & "',event_sub='" & TextBox3.Text & "',fac_name='" & TextBox4.Text & "',dat='" & TextBox5.Text & "',tim='" & TextBox6.Text & "' WHERE event_id='" & TextBox1.Text & "'", CN) CMD.ExecuteNonQuery() CN.Close() MsgBox("Record Deleted") TextBox1.Text = ""

End If

End Sub


71

If (MessageBox.Show("Do You want to DELETE this Record from your Database", "DELETE", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then

start() Dim CMD As SqlCommand = New SqlCommand("DELETE FROM event WHERE event_id='" & TextBox1.Text & "'", CN) CMD.ExecuteNonQuery() CN.Close() MsgBox("Record Deleted") TextBox1.Text = ""

End If End Sub

Private Sub delupdate_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click MsgBox(ComboBox1.Text & ComboBox1.SelectedIndex) Dim s As String = ComboBox1.Text Dim sql As String = "" Select Case ComboBox1.SelectedIndex Case 0 sql = "select * from event where event_id='" & TextBox1.Text & "'" Case 1 sql = "select * from event where event_name='" & TextBox1.Text & "'"

Case 2 sql = "select * from event where event_sub='" & TextBox1.Text & "'"

Case 3 sql = "select * from event where dat='" & TextBox1.Text & "'" End Select DATATAB.Clear()

start() DA = New SqlDataAdapter(sql, CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0

TextBox7.Text = DATATAB.Rows(ROWNO)(0).ToString TextBox2.Text = DATATAB.Rows(ROWNO)(1).ToString TextBox3.Text = DATATAB.Rows(ROWNO)(2).ToString TextBox4.Text = DATATAB.Rows(ROWNO)(3).ToString TextBox5.Text = DATATAB.Rows(ROWNO)(4).ToString TextBox6.Text = DATATAB.Rows(ROWNO)(5).ToString

End SubEnd Class

72

Reports

Student details


Public Class STUDENT_REPO Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub STUDENT_REPO_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from student", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 Dim OBJ As New CrystalReport2

OBJ.SetDataSource(DATATAB) CrystalReportViewer1.ReportSource = OBJ End SubEnd Class

Faculty details

73


Public Class faculty_repo Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub faculty_repo_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from faculty", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 Dim OBJ As New facu

OBJ.SetDataSource(DATATAB) CrystalReportViewer1.ReportSource = OBJ

End SubEnd Class

74

Expenses


Public Class Expenses_repo Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Expenses_repo_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from expenses", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 Dim OBJ As New EXPENSE

OBJ.SetDataSource(DATATAB) CrystalReportViewer1.ReportSource = OBJ End SubEnd Class

75

Fund details


Public Class Funds_repo Dim DATATAB, datatab1, datatab2 As New DataTable

Private Sub Funds_repo_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load start() DA = New SqlDataAdapter("select * from funds", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0 Dim OBJ As New fund

OBJ.SetDataSource(DATATAB) CrystalReportViewer1.ReportSource = OBJ

End SubEnd Class

76

Add fund details


Public Class Funds

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1 newrow(0) = TextBox1.Text newrow(1) = TextBox2.Text


DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA INSERTED") TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = ""

CN.Close() End If

77

End If

DATATAB.Clear()

DATATAB.Clear() start() DA = New SqlDataAdapter("select * from funds", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "T001" & DATATAB.Rows.Count + 1

CN.Close() ROWNO = 0 DA = New SqlDataAdapter("select * from funds", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "T001" & DATATAB.Rows.Count + 1

CN.Close() ROWNO = 0 End Sub

Private Sub Funds_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

DATATAB.Clear() start() DA = New SqlDataAdapter("select * from funds", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) TextBox1.Text = "T001" & DATATAB.Rows.Count + 1

CN.Close() ROWNO = 0 End SubEnd Class

78

Add expenses details


Public Class Expenses

Private Sub Expenses_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

DATATAB.Clear() start() DA = New SqlDataAdapter("select * from expenses", CN) CM = New SqlCommandBuilder(DA) DA.Fill(DATATAB) CN.Close() ROWNO = 0

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If (MessageBox.Show("Do You want to add this Record in your Database", "ADD", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) = DialogResult.Yes) Then If TextBox2.Text = "" Or TextBox3.Text = "" Then MsgBox("FIELD SHOULD NOT BE EMPTY") Else Dim newrow As DataRow = DATATAB.NewRow ROWNO = ROWNO + 1

79


newrow(2) = TextBox3.Text

DATATAB.Rows.InsertAt((newrow), ROWNO) DA.Update(DATATAB) MsgBox("DATA INSERTED") TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = ""

CN.Close() End If End If End SubEnd Class

80

5.2 Code Efficiency

Reviewing of Code efficiency for a module is carried out after the module is

successfully compiled and all the syntax errors eliminated. Code efficiency review is

extremely cost-effective strategies for reduction in coding errors in order to produce

high quality code. Normally, two types of efficiency are carried out on the code of a

module - code optimization and code inspection. The procedure and final objective of

these two efficiency techniques are very different as discussed below.

Optimization of Code

Code optimization is an informal code analysis technique. In this technique, after a

module has been coded, it is successfully compiled and all syntax errors are

eliminated. Some members of the development team are given the code a few days

before the optimization meeting to read and understand the code. Each member

selects some test cases and simulates execution of the code by hand (i.e. trace

execution through each statement and function execution). The main objectives of the

optimization are to discover the algorithmic and logical errors in the code. The

members note down their findings to discuss these in a optimization meeting where

the coder of the module is also present.

Even though a code optimization is an informal analysis technique, several guidelines

have evolved over the years for making this naïve technique more effective and

useful. Of course, these guidelines are based on personal experience, common sense,

and several subjective factors. Therefore are based on personal experience, common

sense, and several subjective factors. Therefore, guidelines should be considered as

examples rather than as rules to be applied dogmatically. Some of these guidelines are

the following:

The team performing the code optimization should not be either too big or too small.

Ideally, it should consist of three to seven members.

81

6.1 TESTING PHASE

One of the purposes of the testing is to validate and verify the system. Verification

means checking the system to ensure that it is doing what the function is supposed to

do and Validation means checking to ensure that system is doing what the user wants

it to do.

No program or system design is perfect; communication between the user and the

designer is not always complete or clear, and time is usually short. The result is errors

and more errors. Theoretically, a newly designed system should have all the pieces in

working order, but in reality, each piece works independently. Now is the time to put

all the pieces into one system and test it to determine whether it meets the user's

requirements. This is the best chance to detect and correct errors before the system is

implemented. The purpose of system testing is to consider all the likely variations to

which it will be subjected and then push the system to its limits. If we implement the

system without proper testing then it might cause the problems.

1. Communication between the user and the designer.

2. The programmer's ability to generate a code that reflects

exactly the system specification.

3. The time frame for the design.

Theoretically, a new designed system should have all the pieces in working order, but

in reality, each piece works independently. Now is the time to put all the pieces into

one system and test it to determine whether it meets the requirements of the user. The

process of system testing and the steps taken to validate and prepare a system for final

implementation are:

83

6.2 LEVELS OF TESTING

The different types of testing are as follows:

1. UNIT TESTING: This is the smallest testable unit of a computer system and is

normally tested using the white box testing. The author of the programs

usually carries out unit tests.

2. INTEGRATION TESTING:

In integration testing, the different units of the system are integrated

together to form the complete system and this type of testing checks the system as

whole to ensure that it is doing what is supposed to do. The testing of an integrated

system can be carried out top-down, bottom-up, or big-bang. In this type of testing,

some parts will be tested with white box testing and some with black box testing

techniques. This type of testing plays very important role in increasing the systems

productivity. We have checked our system by using the integration testing techniques.

3. SYSTEM TESTING:

A part from testing the system to validate the functionality of

software against the requirements, it is also necessary to test the non-functional aspect

of the system. Some examples of non-functional tools include tests to check

performance, data security, usability/user friendliness, volume, load/stress that we

have used in our project to test the various modules.

System testing consists of the following steps:

1. Program(s) testing.

2. String testing.

3. System testing.

4. System documentation.

5. User acceptance testing.

84

4. FIELD TESTING: This is a special type of testing that may be very important in some

projects. Here the system is tested in the actual operational surroundings. The

interfaces with other systems and the real world are checked. This type of testing is

very rarely used. So far our project is concerned; we haven't tested our project using

the field testing.

5. ACCEPTANCE TESTING:

After the developer has completed all rounds of testing and he is

satisfied with the system, then the user takes over and re-tests the system from his

point of view to judge whether it is acceptable according to some previously

identified criteria. This is almost always a tricky situation in the project because of the

inherent conflict between the developer and the user. In this project, it is the job of the

bookstores to check the system that whether the made system fulfills the goals or not.

WHY SYSTEM TESTING? Testing is vital to the success of the system. System testing makes a logical

assumption that if all the parts of the system are correct, the goal will be successfully

achieved. Inadequate testing results in two types of problems:

1. The time lag between the cause and the appearance of the problem.

2. The effect of system errors on the files and records within the system.

ACTIVITY NETWORK FOR SYSTEM TESTING

The test plan entails the following activities:

1. Prepare test plan.

2. Specify conditions for user acceptance testing.

3. Prepare test data for program testing.

4. Prepare test data for transaction path testing.

5. Plan user training.

85

6. Compile/assemble programs.

7. Prepare job performance aids.

8. Prepare operational documents.

PREPARE TEST : A workable test plan must be prepared in accordance with

established design specifications. It includes the following items:

Outputs expected from the system.

Criteria for evaluating outputs.

A volume of test data.

Procedure for using test data.

Personnel and training requirements.

SPECIFY CONDITIONS FOR USER ACCEPTANCE TESTING

Planning for user acceptance testing calls for the analyst and the user to agree on

conditions for the test.

PREPARE TEST DATA FOR PROGRAM TESTING

As each program is coded, test data are prepared and documented to ensure that all

aspects of the program are properly tested.

PREPARE TEST DATA FOR TRANSACTION PATH TESTING

This activity develops the data required for testing every condition and transactions to

be introduced into the system. The path of each transaction from origin to destination

is carefully tested reliable results.

PLAN USER TRAINING

User training is designed to prepare the user for testing and converting the system.

User involvement and training take place parallel with programming for three

reasons:

• The system group has time available to spend on training while the programs

are being written.

• Initiating a user-training program gives the systems group a clearer image of

the user's interest in the new system.

86

• A trained user participates more effectively in system testing.

The training plan is followed by preparation of the user training manual and other text

materials.

COMPILE / ASSEMBLE PROGRAMS

All programs have to be compiled / assembled for testing.

PREPARE JOB PERFORMANCE AIDS

In this activity the materials to be used by personnel to run the system are specified and

scheduled. This includes a display of materials.

PREPARE OPERATIONAL DOCUMENTS

During the test plan stage, all operational documents are finalized including copies of the

operational formats required by the candidate system.

SYSTEMS TESTING

The computer department to ensure that the system functions as specified does this testing.

This testing is important to ensure that a working system is handed over to the user for

acceptance testing.

ACCEPTANCE TESTING

The user to ensure that the system functions, as the user actually wanted performs this

testing. With prototyping techniques, this stage becomes very much a formality to check the

accuracy and completeness of processing. The screen layouts and output should

already have been tested during the prototyping phase.

An error in the program code can remain undetected indefinitely. To prevent this

from happening the code was tested at various levels. To successfully test a system,

each condition, and combinations of conditions had to be tested. Each program was

tested and linked to other programs. This unit of program is tested and linked to

other units and so on until the complete system has been tested.

The purpose of testing is to ensure that each program is fully tested. To do so a test

plan had to be created. The test plan consists of a number of test runs such as the

87

valid paths through the code, and the exception and error handling paths. For each

test run there is a list of conditions tested, the test data used and the result expected.

The test plan was then reviewed to check that each path through the code is tested

correctly. It is the responsibility of the programmer to collect the data that will

produce the required test condition.

88

TEST CASES:-

TEST DATA Specifications

for Event Management System user

form1

Test Date 27.July.2011 Programmer name:Event

Management System

Tested By: Project ID: 11105454

Event_Id

Event_Name

Event_Subject

Date

Time

89

Faculty

Positive Test cases for registration form

T.C ID PRE-CONDITION T.C

DESCRIPTION T.C DATA EXPECTED ACTUAL RESULT

1

User should be on/ Event Management

System/registration? And is on Event_Id Field

Check the functionality of Event_Id field

[email protected]

Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. name are required.

Ok Pass

2




[email protected]


Ok Pass

3




[email protected]


Ok Pass

4




[email protected]

Will accept only letters, spaces, hyphens, and apostrophes.Length

upto 32 characters.name are

required.

Ok Pass

5




[email protected]

Will accept only letters, spaces, hyphens, and apostrophes.Length

upto 32 characters.name are

required.

Ok Pass

6


System/registration? And is on Event_Name Field

Check the functionality of Event_Name

option12456


Ok Pass

90

mailto:[email protected]








7




option

844496 Will accept one.This is required Ok Pass

8


System/registration? And is on Event_Subject Field

Check the functionality of Event_Subject

option9a Lext. Part 3rd Uttam Nagar


Ok Pass

9




option

wz 102 b tilak nagar

Will accept only numeric upto 3 digit . Customer

ID are requiredOk Pass

10




option

a 1 army appartment Will accept all valid dates Ok Pass

11




option

1a L ext. 2nd floor Dwarka Will accept all valid dates Ok Pass

12




option9a Lext. Part 3rd Uttam Nagar

Will accept country.This is required. Ok Pass

13




option

wz 102 b tilak nagar

Will accept the valid postal code of the selected country Ok Pass

14


System/registration? And is on Date Field

Check the functionality of

Date option

1234

Will accept only letters, numbers, underscores,

and one dot (.)Ok pass




Date option1456

Will accept only letters, numbers, underscores,

and one dot (.)Ok pass

18




Date option1589

Will accept 6 to 32 characters.Capitalisation matters. and don't use

your name ID.

Ok Pass

20


System/registration? And is on Time Field

Check the functionality of Time Option

14567


your name or ID.

Ok Pass

91

21




2568


your name or ID.

Ok Pass

23


System/registration? And is on Faculty Field

Check the functionality of Faculty field

19-Jul-11

Will accept any valid email id or blank Ok Pass

24




27-Jul-11

Will accept any valid email id or blank Ok Pass

Negative Test cases for registration form

T.C ID PRE-CONDITION T.C

DESCRIPTION T.C DATA EXPECTED ACTUAL RESULT

1




[email protected]


Invalid Fail

2




[email protected]


Invalid Fail

3




[email protected]

Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.name are required.

Invalid Fail

4




[email protected]


Invalid Fail

5




optionLissa

Allows to select one.This field is

required. Invalid Fail

6




optionDeepjot Kaur

Allows to select a month and enter a valid day

and yearInvalid Fail

92







7




optionGandharn



8




optionKaran Singh



9




option

a 1 army appartment Allows to select a country.This field is

required. Invalid Fail

12




option

1a L ext. 2nd floor Dwarka

Will accept only letters, numbers, underscores, and one dot (.) .The ID

must be available.

Invalid Fail

13




option 9a Lext. Part 3rd Uttam Nagar


must be available.

Invalid Fail

14




optionwz 102 b tilak nagar


must be available.

Invalid Fail

15




Date option

8568


your name or ID.

Invalid Fail

16




Date option

4586


your name or ID.

Invalid Fail




Gate Repair

Will accept any valid email id or blank Invalid Fail

18




Air condition


19




Gate Repair


93

22




28-Jul-11

Either select one from drop list or type one Invalid Fail

23




31-Jul-11

Will accept anything.But not blank Invalid Fail

94

VERIFICATION AND VALIDATION (V&V)

The objectives of verification, validity activities are to assess and improve the quality

of the work products generated during development and modification of the software.

Quality depends upon the various attributes like correctness, completeness,

consistency, reliability, usefulness, usability, efficiency and conformance to

standards.

The terms verification and validation are used synonymously. These are defined as

under: -

Verification: “Are we building the product right?”

Validation: “Are we building the right product?”

Verification activities include proving, testing, and reviews. Validation is the process

of evaluating software at the end of the software development to ensure compliance

with the software requirements. Testing is a common method of validation. Clearly,

for high reliability we need to perform both activities. Together, they are often called

V&V activities.

The major V&V activities for software development are inspection, reviews, and

testing (both static and dynamic). The V&V plan identifies the different V&V tasks

for the different phases and specifies how these tasks contribute to the project V&V

goals. The methods to be used for performing these V&V activities, the

responsibilities and milestones for each of these activities, inputs and outputs for each

V&V task, and criteria for evaluating the outputs are also specified.

The two major V&V approaches are testing and inspections. Testing is an activity that

can be generally performed only on code. It is an important activity and is discussed

in detail in a later chapter. Inspection is a more general activity that can be applied to

any work product, including code. Many of the V&V tasks are such that for them, an

inspection type of activity is the only possible way to perform the tasks (e.g. trace

ability and document evaluation). Due to this, inspections play a significant role in

verification.

95

7.1 System Implementation Maintenance and Review

96

As we know, creating software is one thing and the implementation of the created

software is another. The process of implementing software is much difficult as

compared to the task of creating the project. First we have to implement the software

on a small scale for removing the bugs and other errors in the project and after

removing them we can implement the software on a large scale. Before we think in

terms of implementing the Software on a large basis, we must consider the Hardware

requirements.

Whenever we develop software or project a certain hardware and software is being

used by the programmer for developing the project. The hardware and software to be

used by the programmer for developing the project should be such that it would result

in the development of a project, which would satisfy all the basic needs for which the

project has been created by the programmer. The Hardware should be such that cost

constraints of the Client should also be taken into account without affecting the

performance.

7.2 Hardware Evaluation Factors

When we evaluate computer hardware, we should first investigate specific physical and

performance characteristics for each hardware component to be acquired. These specific

questions must be answered concerning many important factors. These hardware

evaluation factors questions are summarized in the below figure.

Notice that there is much more to evaluating hardware than determining the fastest and

cheapest computing device. For e.g. the question of possible obsolescence must be

addressed by making a technology evaluation. The factor of ergonomics is also very

important. Ergonomics is the science and technology that tries to ensure that computers

and other technologies are "user-friendly", that is safe, comfortable and easy to use.

Connectivity is another important evaluation factor, since so many computer systems

are now interconnected within wide area or local area telecommunications networks.

Hardware Evaluation Factors:-

97

1) Performance

2) Cost

3) Reliability

4) Availability

5) Compatibility

6) Modularity

7) Technology

8) Ergonomics

9) Connectivity

10) Environmental requirements

11) Software

12) Support

7.3 Software Evaluation Factors

Software can be evaluated according to many factors similar to the hardware

evaluation. Thus the factors of performance, cost, reliability, compatibility,

modularity, technology, ergonomics, and support should be used to evaluate

proposed software acquisitions. In addition, however, the software evaluation

factors are summarized in below figure. For e.g. some software packages require too

much memory capacity and are notoriously slow, hard to use, or poorly

documented. They are not a good selection for most end users, even if offered at

attractive prices.

1. EFFICIENCY: is the software a well-written system of computer

instructions that does not use much memory capacity or CPU time?

2. FLEXIBILITY: can it handle its processing assignments easily without

major modifications?

3. SECURITY: does it provide control procedures for errors, malfunctions

and improper use?

4. LANGUAGE: do our computer programmers and users write it in a

programming language that is used?

98

5. DOCUMENTATION: is the s/w well documented? Does it include

helpful user instructions?

6. HARDWARE: does existing hardware have the features required to best

use this software?

7. Other characteristics of hardware such as its performance, what about the

cost, how much is reliable and etc.

7.4 Conversion and Training

An important aspect of is to make sure that the new design is implemented to

establish standards. The term implementation has different meanings, ranging form

the conversion of a basic application to a complete replacement of a computer system.

Implementation is used here to mean the process of converting a new or revise system

into an operational one. Conversion is one aspect of implementation. Conversion

means changing form one system to another. The objective is to put the tested system

into operation while holding costs, risks, and personnel irritation to a minimum. It

involves creating computer-compatible files, training the operation staff, and

installing terminal and hardware. A critical aspect of conversion is not disrupting the

functioning of the organization.

When a new system is used over and old, existing and running one, there are always

compatibility errors. These errors are caused because of the lack of equipment or

personnel to work the new system. Running any specified system at an organization

does require some or other hardware or, in this case, software requirement as well.

Conversion is one aspect of implementation review & software maintenance.

There are three types of implementation:

1. Implementation of a computer system to replace a manual system. The

problems encountered are converting files, training users, creating accurate

files and verifying printouts for integrity.

99

2. Implementation of a new computer system to replace an existing one. This is

usually a difficult conversion. If not properly planned there can be many

problems. Some large computer systems have taken as long as year to convert.

3. Implementation of a modified application to replace an existing one, using the

same computer. This type of conversion is relatively easy to handle, provided

there are no major changes in the files.

7.5 TRAINING NEEDS

Training needs refer to the gaining of knowledge required for running the system.

First of all the system is a computer based system therefore the person should have

good knowledge about computer and its working. He should know how to use

software's on the computer.

For a better usage and working of the software the organization should appoint a

person who has good knowledge of all the required software’s. The organization gets

a person trained through different institutes present in the market. The training should

be as per the above requirements.

100

8. COST ESTIMATION OF THE PROJECT

Cost in a project is due to the requirements for software, hardware, and human

resources. Hardware resources are computer time, terminal time and memory required

for the project. Software resources include the tools and compilers needed during

development. The bulk of cost of software development is due to human resources

needed. Cost estimates are determined in terms of person-months (PM).

Total No. Of Persons Involved In This Project:

1. Administrator

2. Senior Programmer

3. Junior Programmers

4. On line Users.

Since this Project will complete in 4 months

COST ESTIMATE: (Salary of Project Manager + Salary of Senior Programmer + 2 * Salary of Junior Programmer) * 2

101

9. GANTT & PERT CHART

GANT CHART

Gantt charts mainly used to allocate resources to activities. The resources allocated to

activities include staff, hardware, and software. Gantt charts (named after its

developer Henry Gantt) are useful for resource planning. A Gantt chart is special type

of bar chart where each bar represents an activity. The bars are drawn along a

timeline. The length of each bar is proportional to the duration of the time planned for

the corresponding activity.

Gantt chart is a project scheduling technique. Progress can be represented easily in a

Gantt chart, by coloring each milestone when completed. The project will start in the

month of July and end after 4 months at the end of Oct.

System Design

Detailed Design

Coding

Unit Testing

Test Plan

Testing

July Aug Sep Oct

102

Pert Chart

PERT (Project Evaluation and Review Technique) charts consist of a network of

boxes and arrows. The boxes represent activities and the arrows represent task

dependencies.

PERT chart represents the statistical variations in the project estimates assuming a

normal distribution. Thus in a PERT chart instead of making a single estimate for

each task, pessimistic, likely, and optimistic estimates are also made. The boxes of

PERT charts are usually annotated with the pessimistic, likely, and optimistic

estimates for every task. Since all possible completion times between the minimum

and maximum durations for every task have to be considered, there are many critical

paths, depending on the permutations of the estimates for each task. This makes

critical path analysis in PERT charts very complex. A critical path in a PERT chart is

shown by using thicker arrows. The PERT chart representation of the EVENT

Management System problem of Figure A. is shown in Figure B.

Task ES EF LS LF STSpecification Part 0 15 0 15 0Design Database Part 15 60 15 60 0Design GUI Part 15 45 90 120 75Code Database Part 60 165 60 165 0Code GUI Part 45 90 120 165 75Integrate and Test 165 285 165 285 0Write User Manual 15 75 225 285 210

Figure A : Different Tasks for the Event Management System shown in above table.

103

FIGURE B: PERT Chart representation of the Event Management System.

PERT charts are a more sophisticated form of activity chart. In activity diagrams only

the estimated task durations are represented. Since the actual durations might vary

from the estimated durations, the utility of the activity diagrams is limited.

104

DesignDatabase part

40, 45, 60

CodeDatabase part

95,105,120

Specification12, 15, 20

Design GUI part

24, 30, 38

CodeGUI part4538,, 52

IntegratedAnd test

100,120,140 Finish0

Write userManual

50, 60, 70

10. SECURITY AND VALIDATION CHECKS

Software’s Vulnerability to Attack

Software development is not yet a science or a rigorous discipline, and the

development process by and large is not controlled to minimize the vulnerabilities that

attackers exploit.

The security of software is threatened at various points throughout its life cycle, both

by inadvertent and intentional choices and actions taken by “insiders”—individuals

closely affiliated with the organization that is producing, deploying, operating, or

maintaining the software, and thus trusted by that organization—and by “outsiders”

who have no affiliation with the organization. The software’s security can be

threatened.

During its development: A developer may corrupt the software—

intentionally or unintentionally—in ways that will compromise the software’s

dependability and trustworthiness when it is operational.

During its deployment (distribution and installation): If those responsible

for distributing the software fail to tamperproof the software before shipping

or uploading, or transmit it over easily intercepted communications channels,

they leave the software vulnerable to intentional or unintentional corruption.

Similarly, if the software’s installer fails to “lock down” the host platform, or

configures the software insecurely, the software is left vulnerable to access by

attackers.

During its operation: Once COTS and open source software has gone

operational, vulnerabilities may be discovered and publicized; unless security

patches and updates are applied and newer supported versions (from which the

root causes of vulnerabilities have been eliminated) are adopted, such software

will become increasingly vulnerable. Non-commercial software and open

source software (OSS) may also be vulnerable, especially as it may manifest

untrustworthy behaviors over time due to changes in its environment that

stress the software in ways that were not anticipated and simulated during its

testing.

105

During its sustainment: If those responsible for addressing discovered

vulnerabilities in released software fail to issue patches or updates in a timely

manner, or fail to seek out and eliminate the root causes of the vulnerabilities

to prevent their perpetuation in future releases of the software, the software

will become increasingly vulnerable to threats over time. Also, the software’s

maintainer may prove to be a malicious insider, and may embed malicious

code, exploitable flaws, etc., in updated versions of the code.

The Challenge of Building Secure Software:-

1. Dependability: Dependable software executes predictably and operates

correctly under all conditions, including hostile conditions, including when the

software comes under attack or runs on a malicious host.

2. Trustworthiness: Trustworthy software contains few if any vulnerabilities or

weaknesses that can be intentionally exploited to subvert or sabotage the

software’s dependability. In addition, to be considered trustworthy, the

software must contain no malicious logic that causes it to behave in a

malicious manner.

Survivability (also referred to as “Resilience”): Survivable—or resilient—software

is software that is resilient enough to (1) either resist (i.e., protect itself against) or

tolerate (i.e., continue operating dependably in spite of) most known attacks plus as

many novel attacks as possible, and (2) recover as quickly as possible, and with as

little damage as possible, from those attacks that it can neither resist nor tolerate

106

11. SCOPE OF FUTURE APPLICATION

The whole project as we have seen is totally based upon the database maintenance.

This could be the most vital thing that the Indian industry asks for these days. This

phenomenon is not only confined to big industries, but amazingly what that a

common man deals with everyday in his life. This phenomenon starts from a common

man to big industries like railways. Not only has their database had to upgraded very

often. There is no denying the fact that one can say that the company’ progress solely

depends on how fast the database accessing goes on.

Certainly database accessing has given boon to the companies if Indian industries and

will have major role in upcoming of leading industries. Database accessing is what

each firm will ask for in the coming future. Database is what they required in each

field.

Therefore the database is the future of computer industry.

107

12.CONCLUSION

This project is designed to meet the requirements of Event Management in Colleges.

It is developed in Visual Basic.Net, keeping in mind the specifications of the system.

For designing the system we have used simple data flow diagrams.

Overall the project teaches us the essential skills like:

Using system analysis and design techniques like data flow diagram in designing

the system.

Understanding the database handling and query processing

108

13. BIBLIOGRAPHY

1. Visual Basic Jamew Foxall

2. Fundamentals Of Software Engineering Rajib Mall

3. Software Engineering K.K.Aggarwal & Yogesh Singh

4. Visual Basic Projects Tony Martin, Dominic Selly

5. Visual Basic Professional Projects Kuljit Kaur,Pooja Bembey

6. Using SQL-SERVER 2000, Microsoft publication

7. SQL-SERVER 2000 BPB publication

109

14. GLOSSARY

TEXT BOX

A text Box control, sometimes called an edit field or edit control, displays information

entered at design time, entered by the user, or assigned to the control in code at run

time.

BUTTON

Use a Command Button control to begin, interrupt, or end a process. When chosen, a

Command Button appears pushed in and so is sometimes called a push button.

LIST BOX

A List Box control displays a list of items from which the user can select one or more.

If the number of items exceeds the number that can be displayed, a scroll bar is

automatically added to the List Box control.

LABEL

A Label control is a graphical control you can use to display text that a user can’t

change directly.

GROUPBOX

A GROUPBOX control provides an identifiable grouping for controls. You can also

use a Frame to subdivide a form functionally – for example, to separate groups of

Option Button controls.

COMBO BOX

A Combo Box control combines the features of a text box and a list box. This control

allows the user to select an item either by typing text into the combo box, or by

selecting it from the list.

110

TIMER

A Timer control can execute code at regular intervals by causing a Timer event to

occur. The Timer control, invisible to the user, is useful for background processing.

PICTURE BOX

The primary use for the Picture Box control is to display a picture to the user. The

actual picture that is displayed is determined by the picture property. The picture

property contains the file name (and optional path) for the picture file that you wish to

display.

DATA GRID CONTROL

The DATA Grid control displays and operates on tabular data. It allows complete

flexibility to sort, merge, and format tables containing strings and pictures. When

bound to a Data control, MSFlexGrid displays read-only data.

DATE AND TIME PICKER CONTROL

A Date and Time Picker (DTP) Control provides a simple and intuitive interface

through which to exchange data and time information with a user. For example, with a

DTP control you can ask the user to enter a data and then retrieve his or her selection

with ease.

OPTION BUTTON

An Option Button control displays an option that can be turned on or off.

IMAGE CONTROL

Use the Image control to display a graphic. An Image control can display a graphic

from an icon, bitmap or metafile, as well as enhanced metafile, JPEG, or GIF files.

CHECK BOX CONTROL

A Check Box indicates whether a particular condition is on or off. We use check

boxes in an application to give users true/false or yes/no options. Because check

boxes work independently of each other, a user can select any number of check boxes

at the same time.

111

projectorg.files.wordpress.com · Web viewI hereby declare that this project work titled “Event...

Documents

Transcript of projectorg.files.wordpress.com · Web viewI hereby declare that this project work titled “Event...