Professional Documents
Culture Documents
College Technical Festival Event Organization Application PDF
College Technical Festival Event Organization Application PDF
College Technical Festival Event Organization Application PDF
Ch. 1: Introduction:
1.1Project detail:
1.1.1Definition:
The definition of the project is College Technical Event Scheduling and
Organization. This application leads for the handling and formation of the event and
its schedule.
1.1.2 Project Profile:
1.2 Purpose:
The purpose of making this application is to provide a easiness of finding the event
schedule at one place. The user will find the technical event schedule in one application
rather to visit different web pages. The invention satisfies the foregoing needs and avoids
the drawbacks and limitations and frustrations of the prior art, and provides a better, more
timely and effective process of communication to schedule and coordinate events by
utilizing Internet-based application. The people may get fail to answer the call or would be
unable to check the email so this Application will lead a better communication of the
people about the event.
1.3Project Scope:
The scope of the project includes creating a user interface to Android system as well as
a backend that will emulate some of its behaviour, specifically for testing. Event
management is the application of management to the creation and development of
Technical festivals, events and conference.
The Application generally relates to a system and method to schedule events, and more
particularly, to a system and method for scheduling technical events among entities such
as organization that may have limitations for scheduling, such as geographical
requirements, constraints by timing, conflicts, availability, or other factors.
This Application leads to provide the user especially the student the reliability in
finding the schedule of events at one place rather to go for each of the college websites.
The college will just have to post the event in .pdf file and that will be downloaded by
students. By this Application the matter of time which go in informing each other for the
event will also be solved out.
1.4Objectives:
The people sending mail or message of technical event to other is wasting of time and
memory. To overcome this problem our invention provides a medium where one can get
the schedule of an event by just opening our application with the internet connection and
refreshing it.Another thing our Application provides is all in one characteristic. i.e. all
technical event schedule in just one application.
upcoming events in the database. The other person who will use this application will
be student they will get the details of the upcoming technical events by just logging to
the application and downloading the desired event details.
Product Features
Functionality
The invention satisfies the foregoing needs and avoids the drawbacks and
limitations and frustrations of the prior art, and provides a better, more timely and
effective process of communication to schedule and coordinate events by utilizing
Internet-based application.
This product contains three major Users. First the admin will allow the user for
accessing this application by giving the permission rights and access control.
Second The college login will have a right to see the events listing and they can
post their new schedule of a technical event as well. And third The End User i.e.
Student, they can see the list of the events and schedule of event.
User Classes and Characteristics
Admin
The Admin will have all the access to this product. The Admin will provide the
access permission to the users which are students and Colleges. The admin can also
delete or discard the unwanted events reported as spam. They also manage the
database like deleting the past events.
College
The college admin will be the second admin to this product, but with less access
control. The college admin will be provided the access the database like to add
event in .pdf format and to delete event. The college admin will be logged in using
their id and password provided.
Student
The student are the end-user entity, they will be having the access rights to see
the event schedule by pdf format. And register their new account providing their
basic details.
Other Non-Functional Requirements
Performance Requirements
we thought we would use for refactoring. We alsopondered on a suitable name to give the
project.
The group was then divided that would work on parts of the code. We kept in
touchwith each other and whenever we had difficulties, we asked each other questions. On
someoccasions, we had to pretend we were the customer so as to try to figure out some of
the things thatuser would desire, such as the friendliness of the user interface and ease of
navigation through thesoftware.
Figure 1 GanttChart
Ch. 3: Analysis:
3.1 Technology And Analysis
The technology used here is ANDROID. Android is basically an operating system for
smartphones. But we find now integrated into PDAs, touch pads or televisions, even cars
(trip computer) or netbooks. The OS was created by the start-up of the same name, which
is owned by Google since 2005. Now a day’s people using android as an operating system
in their mobile phones have been increased. So people using android are, much more and
they are familiar with it. Students increase their craze about android phones. The operating
system is based on Linux. Android allows multitasking in the sense that multiple
applications can run simultaneously. The database here used is SQLite. The lighter version
of SQL.
Software and Hardware Requirements
Software Requirements:
Android version 2.3 or above.
Hardware Requirements:
Minimum 128MB RAM
Ch. 4: Design:
4.1E-R Diagram
Entity-Relationship diagram is a detail & logical representation of entities and data
elements for an organization. This technique is used in database that helps in an enterprise
are related to each other. There are 3 types of E-R diagram:
1. one to one :
It is a one to one relationship is an association between 2 entities.
2. one to many:
One-to-many relationship exists when one entity related to one or more entity.
3. Many to many:
It describes entities that may have many relationships among each other.
College Information
(0.0)
College
Student Registration Information Event Organize
College Technical Festival Event Admin
Organization Application
User Acess
Services
Admin
Admin
Fetch Password Database
Get Data
(1.0)
Student Registration Information Event Organize College
Registration
User Access
Services
(2.0) (2.0)
Admin
Fetch data
User information
(1.2)
Login
College Information
College
(2.2)
Update Person_data
Update
Details
Give Details
(2.1)
College Details Get Data
Login
Event Title
(2.3)
Create Event
(2.4)
Event_pdf
Post Event
(2.3)
List of User
Fetch
view
(2.2)
Admin details Fetch Details Person_data
login
Accept
Enter details
Insert
(2.1)
(2.4)
College
Registration registration
College
Receive
(3.1)
(3.2)
Student/
Provide Username Access Person_data Send password
College Forget
Message
password
SYSTEM BOUNDARY
Login
*
*
*
List Of User
*
*
* **
Update Details
*
Top Package::College *
*
*
*
Payment
* *
**
Top Package::Admin
Check Event
*
*
*
Get Schedule
* *
*
*
Top Package::Student
Registration
Delete User
Register College
ADMIN BOUNDARY
Login
Register College
Get Payment
*
*
**
**
Delete User
Top Package::Admin *
View Users
*
Login
Update Details
Payment
*
STUDENT BOUNDARY
Login
Update Details
Check Schedule
*
**
*
**
Registration
*
Strat Application
/ NO / YES
Reenter Add student information
/ NO
Incorrect VALID?
/ YES
Save Data
Registration Sucessful
College Registration:
Strat Application
/ NO
Incorrect VALID?
/ YES
Payment
Enter Details
Login
/ NO
Incorrect VALID?
/ YES
Check Schedule
College Activity:
Enter Details
Login
/ NO
Incorrect VALID?
/ YES
Create Event
Enter Details
Post Event
Admin Activity:
Strat Applicatin
/ NO
valid
/ YES
/ NO
check college request for registration
/ YES
logout
4.5Class Diagram
4.6Sequence Diagram
Student Login Activity College Admin Activity Event Activity Payment Activity Admin Activity
Login Do Login ( )
X X
Generate Event ( )
Notification Event ( )
Event Schedule ( )
Get Schedule ( )
Update Schedule ( )
Logout
Response ( ) Logout ( )
X X X X
Table 2College_login
Field Name Data Type Size Null
Username Varchar 30 Not Null
Password Varchar 30 Not Null
College_name Varchar 50 Not Null
College_no Number 15 Not Null
E-Mail ID Varchar 30 Not Null
3. Student_login:
Table 3Student_login
Field Name Data Type Size Null
Username Varchar 30 Not Null
Password Varchar 30 Not Null
First Name Varchar 30 Not Null
Last name Varchar 30 Not Null
Gender Boolean 2 Not Null
Contact No. Number 12 Not Null
Reg_Type Varchar 10 Not Null
E-Mail ID Varchar 30 Not Null
4. Event_pdf:
Table 4Event_pdf
Field Name Data Type Size Null
Event_id Number 30 Not Null
Event_name Varchar 30 Not Null
Pdf_no Number 30 Not Null
Pdf_size Number 30 Not Null
Pdf_date/time Date/time 8 Not null
5. Event_registerd_information:
Table 5Event_registerd_information
Field Name Data Type Size Null
Event_name Varchar 30 Not Null
Event_id Number 30 Not Null
4.9User Interface
Loading Page: This page is shown at the starting of the application.
Login Page: The below figure shows the login screen/activity of an application.
Student Registration Success: The given figure shows the activity strike to the student
user when the login is successfully done.
College Registration Success: The given figure shows the activity strike to the
College user when the login is successfully done.
Ch.5: Testing:
5.1 Testing Plan
5.1.1 The Testing Process:
We have tested the software process activities such as design, implementation and
requirement engineering because design errors are very costly to repair once system has
been started to operate. Therefore, it is quite obvious to repair them at early stage of the
system. So analysis is the most important process of any project.
5.1.2 Requirement Traceability:
As the most interested portion is whether the system is meeting its requirements or not,
for that testing should be planned so that all requirements are individually tested. We have
to check out that output of certain combinations of inputs gives the desirable results or not.
Your requirement specification gives us the path to get the desirable result.
5.1.3 Tested Modules:
Administrator
Users
Visitors
5.1.4 Testing Schedule:
We have tested each procedure back to back so that errors and omissions can be found
as early as possible. Once the system has been developed fully we tested it on another
machines, which differs in combinations.
5.2 Testing Strategy
A strategy for the software testing integrates software test case design methods into
awell-planned series of steps that result in the successful construction of software. The
strategy provides a road map that describes the steps to be conducted as part of testing.
When these steps are planned and then undertaken, very much efforts, time and resources
are required.
A software testing strategy should be flexible enough to promote a customized testing
approach. At that same time it must be rigid enough to promote reasonable planning and
management tracking as the project progresses.
Testing begins at the component level and works outward towards the
integration of the entire computer based system.
Different testing techniques are appropriate at different points in time.
Testing & Debugging are different activities but debugging must be
accommodated in any testing strategy.
We checked entire project thoroughly so not even a single mistake would be there.
5.3 Test Methods
Testing presents an interesting anomaly for the software engineering activities, the
engineer attempts to build software from an abstract concept to a tangible product. Now
comes testing. The engineer creates a series of test case that are initiated to "demolish" the
software that has been build. Infect, testing is the one step in the software process that
could be viewed (psychologically, at least) as destructive rather than constructive.
Models of Testing:-
There are different Models of testing. On the basis of testing methods there are two
types of testing:
1. Black-box testing.
2. White-box testing
Black-box tests are used to demonstrate that software functions are operational, that
input is properly accepted and output is correctly produced, and that integrity of external
information is maintained.
White-box tests are used to examine the procedural details. It checks the logical paths
by test case. It can also checks the conditions, loops used in the software coding. It checks
that loops are working correctly on defined boundary value.
5.3.1 White-Box Testing:
White-box testing sometimes called glass-box testing, is a test case design method that
users the control structure of the procedural design to drive the test case. Always we are
thinking that there is no necessary to execute or checks the loops and conditions. And so
large number of errors is uncovered. With using white-box testing methods, we have
checked that; all independent paths within a function have been executed at least once, All
logical decisions on their true and false side, A11 loops working correctly at their boundary
values and within their specified conditions.
In our coding we test that all the loops works truly in each module. The one technique
of white-box testing is basis path testing. It contains two parts, one is flow graph notation
and the second is cyclometer complexity. In flow graph notation we are checking logical
control of flow. By using cyclometer complexity we find complexity of our project
structure.
5.3.2 Black-Box Testing:
Black-box testing focuses on the functional requirements of the software. That is black-
box testing enables the software engineer to drive sets of input conditions that will fully
exercise all functional Requirements for the program. Black-box testing is not an
alternative to white-box testing techniques. Rather, it is a complementary approach that is
likely to uncover a different class of errors than white-box methods.
We use in our coding to find errors in the following categories:
Incorrect or missing functions
Interface errors
Errors in database
Performance errors
Initialization and termination errors.
Unlike white-box testing, which is performed earlier in the testing process, black-box
testing tends to be applied during later stages of testing. Because black-box testing
purposely disregards control structure, attention is focused on the information domain.
By applying black-box techniques, we derive a set of test cases that satisfy following
criteria test cases that reduce, by a count that is greater than one, the number of additional
test cases must be designed to achieve reasonable testing.
Level 1 - Build Acceptance Tests
Other related test cases ensure that adopters received the proper Development
Release Document plus other build related information (drop point, etc.). The objective
is to determine if further testing is possible. If any Level 1 test case fails, the build is
returned to developers un-tested.
Future Enhancement:
Registration Services:
The future needs of providing registration for the specific event will be provided. This
provides students not to interact with the college for registration, but they can directly
register their names in any event.
Email Services:
When the user is registered they will get the confirmation mail to their registered mail.
This service will make sure to the Student that they are successfully registered to the event.