Академический Документы
Профессиональный Документы
Культура Документы
ITM 480-H
Patrick Walker
THE UNIVERSITY OF TAMPA
1
ITM 408-H
Patrick Walker
Database Project
December 5th, 2017
Scenario 3
SYSTEM REQUEST 8
Business Need 8
Functionality and Data Requirement 9
General Objective 9
Specific Objectives 9
Expected Value 10
Tangible Benefits 10
Intangible Benefits 10
Special Issue or Constraints 11
Description of System Objectives, Scope, and Boundaries 12
Mission Statement 12
System Objectives 12
Routine Transactions 13
Queries and Reports 13
Scope and Boundaries 15
Conceptual Design 16
International Conference on Information Systems Database Business Rules 16
Logical Data Model 25
Data Dictionary 26
Implementation SQL Server Database 32
Create Statements SQL Script 32
Insert Statements SQL Script 40
Select Statements SQL Script 64
SQL Report Table 67
2
Scenario
Management Information Systems Conference
There are many academic conferences that take place every year. Usually, these conferences are
discipline-specific attracting scholars and practitioners from a particular discipline to the event.
Management Information Systems has several conferences as well, with International Conference on
Information Systems (ICIS) being the most prestigious gathering of IS academics and research-oriented IS
practitioners in the world. Every year in December, researchers from various universities and
organizations around the world get together to share their latest work regarding IS and its impacts in
business.
Several months before the conference, ICIS invites scholars and practitioners worldwide to participate in
the conference program by issuing a call for research papers. Papers can be classified according to broad
topic areas or tracks. Submitted papers are sent out for review by other scholars and accepted papers are
published in the proceedings if presented by at least one author at the conference. Selection criteria to
present at this conference are competitive, as ICIS is the premier conference in the IS field. ICIS receives
about 1000 submissions, but only 20% of the submitted papers make it through the review process and
are accepted for presentation.
In the past, the organizing committee handled the paper submission and review process using an Excel
spreadsheet. This approach led to duplication of effort over the years and has complicated conference
planning and reporting. For example, not tying together data on paper submissions with conference
registration made program planning challenging because it was not easy to determine which authors
were going to attend the conference. Having data in multiple formats and locations also made the
compilation of after the conference reports very tedious. Now the conference organizers would like to
automate the submission, review and registration process in order to make paper submission and
program planning easier. Several interviews with the past conference chairs and organizing committee
members were conducted to gather the information needs and requirements for this application that are
described below.
ICIS issues a call for papers to be presented at the annual meeting. Authors submit papers to the
conference. Each paper submission must indicate the track to which the paper is submitted. Each paper
can only be submitted to one track and a listing and description of ICIS 2017 tracks is available at
http://icis2017.aisnet.org/submissions/tracks/. The database needs to keep track of all different tracks ICIS
offers as well as a description of each track. Note that a track can have multiple papers submitted. Each
track has at least one track chair, but may have two or three track chairs. A paper can be single-authored,
or can have multiple authors. Often, the authors of a single paper are from different universities or
organizations. Once received, every paper is assigned a unique ID. Additionally, for every paper the
system needs to keep track of the following information:
date the paper was submitted to the conference,
the papers title,
authors information (last and first name, middle initial, name of the institution, address, country, and
email)
track to which the paper is submitted
up to five different keywords (words or short phrases that describe the paper)
an abstract, which summarizes key points and is less than 100 words
3
the decision (e.g. whether the paper was accepted or rejected
In order to increase chances of acceptance to this prestigious conference, an author may submit multiple
papers. In addition, authors are also assigned to review papers submitted to ICIS based on their expertise.
This process is described in the next section.
When papers are received by the conference, they are sent out to be reviewed by two or three reviewers.
Each reviewer is assigned a unique ID. Both the authors of the papers that submitted to the conference
and other scholars in the IS community can be asked to review. Some reviewers receive several papers to
be reviewed. The following information is maintained for each reviewer:
First and last name, middle initial
Email
Position
Institution
Field in which doctorate degree was completed
Tracks for which they can review
Furthermore, the date a review has been assigned and a date the review has been completed need to be
stored for each paper reviewed by each reviewer. Finally, for every paper reviewers assessment of the
paper on four dimensions (conceptual significance, practical significance, conduct of research, and
presentation of research) needs to be recorded using the following values: excellent, very good, good,
average, fair, poor, and not acceptable. The reviewers are also asked to submit their overall decision
regarding a paper, which can be accept, accept with minor revisions, or reject. Comments about a paper
are also recorded. Author notifications of the decision to accept or reject are sent by email. The conference
organizing committee also would like to be able to generate a report listing reviewers and the papers that
they reviewed together with the review decision similar to the example provided below:
Paper presentations
All papers which are accepted to ICIS are assigned to a session. A session is the official forum in which
the papers will be presented. Each session has a unique code, the date the session is scheduled, the room
the session will be held in together with the start time and end time of each session. Each session will
accommodate multiple paper presentations (usually three), so each presentation will be scheduled for a
certain time slot during the session (i.e. first or second or third presentation in a particular session).
Sessions are chaired by one of the authors or another conference attendee. The session chair introduces
4
each paper and keeps track of the time for each presentation. Any of the conference attendees (authors,
officers or volunteers) can be assigned to chair a conference session. Note that any session must only
show one attendee as chair (although an attendee can chair multiple such sessions, if needed). Papers can
only be presented by their authors. A paper may have more than one presenter if it is co-authored.
Papers that are not presented will not be published in the proceedings. It is therefore necessary to record
if a paper was presented and who presented it. A sample conference schedule for ICIS 2016:
https://icis2016.sched.com/mobile/#page:page-schedule
Conference Registration
ICIS is the largest academic conference on Information Systems and usually attracts around 1,000
attendees. At least one of the authors of every paper is expected to register for the conference to present
the paper. However, many other academics and practitioners attend the conference to learn about the
latest trends in IS research. For all attendees, the database should keep track of their full name, gender,
occupation (e.g. Ph.D. student, Professor, Chief Information Officer, etc.), affiliation (institution or
organization) and corresponding address and contact information (phone and email). The database
should also keep track of the membership status for all attendees (whether the attendee is also a member
of the Association for Information Systems AIS. ICIS requires all attendees to have an active AIS
membership at the time of the conference). Some conference attendees are officers for ICIS. They serve
various administrative roles such as Chair, VP of Communications, VP of Operations and such. For these
officers (which are also conference attendees), the database should also record the office held together
with a start and end date of the appointment. Please note that it is possible for an individual attendee to
serve as a conference officer, an author and a volunteer. Finally, for each attendee the data and type of
registration should also be recorded. Keep in mind each attendee selects only one type of registration and
that the same registration rate may be selected by various attendees.
Conference fees vary according to the type of registration and participants status. Conference attendees
can also purchase tickets for their guests to attend conference social activities, such as lunches and
dinners. The names of guests are recorded so that name tags can be created. A sample of conference
registration fees for ICIS 2017 is available at http://icis2017.aisnet.org/register/ and is similar to what is
listed below.
Registration Options Early Regular On-site
by Oct. 21 Oct. 22-Dec. Dec. 1 and
1 later
Current AIS Academic Member $590 $640 $690
Current AIS Doctoral Student Member $365 $415 $465
Current AIS Professional Member $899 $949 $999
Doctoral Student Consortium
$365
(Requires invitation & includes the Full Conference)
Guest Full Package Ticket ADULT
(Includes badge, conference meals [2 lunches & 3
breakfast], Welcome Reception, Social Event and $150 $170
conference-provided refreshment breaks for your guest i.e.
your family member or colleague)
Guest Full Package Ticket -CHILD (ages 7-13)
(Includes badge, conference meals [2 lunches & 3
breakfast], Welcome Reception, Social Event and $75
conference-provided refreshment breaks for your guest.
5
Guest Full Package Ticket -YOUTH (ages 14-18)
(Includes badge, conference meals [2 lunches & 3
breakfast], Welcome Reception, Social Event and $100
conference-provided refreshment breaks for your guest.
Guest Welcome Reception Ticket
(additional ticket for your family member or colleague) $50 $70
Registration is not considered complete until payment has been received and processed. Payments can be
made by credit card, money order or check. A payment can cover the registration fees for multiple
conference participants (e.g. a check from a university for several professors or doctoral students). For
each conference participant, the payment amount and method of payment are recorded.
Upon arrival, each conference participant receives a packet with a name tag, conference materials and a
conference receipt indicating the type of registration and cost, attendees affiliation, optional events and
their costs, total amount due, amount of payment received and balance. The system must be able to
generate such receipts at the conference for on-site registrations.
Conference participants who cancel their registration in writing by the posted deadlines are entitled to a
refund. The amount is refunded in full less $25 administrative fee for cancelations received by the
October 21. The amount is refunded in full less $50 administrative fee for cancelations received between
October 22 November 30. Cancellation requests received on December 1st or later will not be eligible to
receive a refund; the registrant will be liable for the full conference registration fee.
Volunteers
Another important constituency of ICIS is the volunteers group. ICIS could not be organized without
their help. Volunteers are conference attendees who volunteer their time to help with the organizing ICIS.
They are also available for the duration of ICIS to perform various tasks such as showing the other
attendees to the session rooms, chair sessions, etc. Volunteers have certain time preferences in terms of
the day of the week they are available to work and the time (start date and end date) they can help out. It
is important the database keeps track of these time preferences. Some volunteers may have multiple time
preferences while other may have none.
Sponsors
ICIS officers work with various organizations that act as sponsors for ICIS. Among others, Microsoft, IBM
and Cisco are regular sponsors of ICIS. Such sponsors contribute important amounts of money to ICIS.
The company name, address and contact information (address, phone and email) and contact person
(name) and must be stored for all sponsors. In addition, the system should also store the amount
contributed by each sponsor. Each sponsor may work with various ICIS officers in order to arrange the
sponsorship.
6
Report requirements
To facilitate conference planning and evaluation, the following reports are needed:
7/
SYSTEM REQUEST
Date: December 4th, 2017
Project Name: Management Information System Conference: SQL Database Project
Project Sponsor: Dr. Natasha Veltri
Name: Patrick Walker
Department: Administration
Organization: International Conference on Information Systems (ICIS)
Phone/E-mail: patrick.walker@spartans.ut.edu
Business Need
International Conference on Information Systems (ICIS) is the most prestigious gathering of
Information Systems academics and research-oriented practitioners in the world that takes place
every year in December. Researchers from numerous universities and other organizations across
the globe get together to discuss their latest findings with regards to the Information System field
and their impact in the business environment. ICIS and its organizing committee is currently
handling both the paper submissions and reviewing process using an Excel spreadsheet. The
conference organizers would now like to automate the submission, review, and registration
process so as to facilitate the paper submission and program planning. The current process
employed by ICIS requires months of tedious preparation. The International Conference on
Information Systems organizing committee expect this program to significantly improve the
quality and efficiency of the entire process.
After several interviews were conducted with the past conference chairs and organizing
committee members the following conclusions were noted:
The current system is tedious, labor intensive, and lengthy.
The current system is inefficient in recording submissions and planning the conference.
The current system is unable to standardize the submitted items.
The current system is inefficient at managing post-conference reporting.
The current system is prone to a higher risk of human error.
/69 8
Functionality and Data Requirement
General Objective
Listed underneath are the overall requirements the new system will address. The program will:
Automate and diminish error margins in the submission, review, registration process.
Increase the quality and efficiency of the submission process.
Increase the quality and efficiency of the program planning.
Increase the quality and efficiency of the reporting process.
Incorporate into a sole location all of the data collected to improve overall efficiency.
Specific Objectives
Listed underneath are the specific requirements the new system will need to meet.
Papers Submission
Record submission information (title, date submitted, authors information, etc.).
Keep track of the track to which the paper is submitted.
Identify the paper through keywords.
Describe the papers focus.
Display the decision related to the paper.
Paper Review
Record the review information (reviewer, conference track, date, decision, etc.).
Keep track of the assessments, comments and other relevant information.
Paper Presentation
Record the presentation information (date, room, time, etc.)
Keep track of the chairs presiding the presentation, and the papers presented.
Conference Registration
Record the information relative to the demographics (Memberships, Age, etc.).
Keep track of the registration throughout the entire process.
Volunteers
Keep track of the volunteers personal information and relative assignments.
Sponsors
Record the information relative to the sponsors (Name, address, contacts, etc.)
Keep track of the contributions made by the sponsors.
/69 9
Expected Value
The implementation of the SQL database will provide the following tangible and intangible
benefits to the International Conference on Information Systems.
Tangible Benefits
Increased Efficiency
After implementing the SQL database, International Conference on Information Systems will
have an automated program to run the registration process, ease the review process, and
significantly facility the reporting process. Additionally, the automation will greatly improve
the conference organizers administrative and executive processes for their program planning.
Decreased Human Error
The implementation of the SQL database will provide the organizers, volunteers, and other
stakeholders with the necessary tools to prevent and therefore greatly reduce the margins
for human errors. The data automation will decrease the possibility of mis-typing during and
between the processes. It will further assist in preventing any undesired duplicates, etc.
Decreased Operating Costs
The database implementation will significantly diminish the amount wasted into date entry
and re-entry for the multiple processes. While it reduces the amount of time allocated to
these tasks, it allows the personnel to work on other, more important and relevant,
assignments. The enhanced allocation of the conferences labor force will have a significant
positive impact on its operating expenses and its bottom line.
Intangible Benefits
Enhanced User Experience
The implementation of the SQL Database will allow authors to directly submit their papers to
the conference. It will provide an easier access to reviews. It will simplify the way individuals
can post comments about papers. The new database will provide the conference organizers
with a toolset capable of keeping track of attendance, revenues from tickets entry, revenues
from meal ticket, diverse paper related information, etc.
/69 10
Enhanced Work Force Moral
The new system will suppress the tedious and demoralizing work related to data entries. The
automation process will therefore provide a boost to the work force and volunteers moral in
addition to increasing the amount of time allocable to other tasks.
Facilitate Future Conferences Planning
The SQL Database will allow the International Conference on Information to build powerful
reports to publish paper submissions, reviews, comments, organizations, etc. and help the
conference organizers improve the conference experience year over year. The paper report
could for instance provide the organizers with insights such as paper acceptance rate,
percentages of papers presented by fields of study, etc.
Implementing an automated database system will significantly improve the efficiency of the
paper submission process, the reporting process, and planning all the details of the conference
for both the participants and organizers.
System Objectives
The database system for International Conference on Information Systems will have the ability
to record, update, and search data associated with the different participants, the papers, the
registrations, the payments, and the sessions. Specifically, the database must be able to allow
authors to submit their papers to the conference, allow participants to register themselves as
attendees and pay the due fees, manage the organizers inquires, track the venues and times of
the session, track the review status of a paper, and track all information related to the other
interveners at the conference.
The system will work as an organized structure which will account for all the information referring
to International Conference on Information Systems. The new system will be capable to handle
all the tasks the manual system with spreadsheets was able to manage but it will do it
automatically and in a significantly more efficient way. The system will allow individuals to
register and complete payments to attend the conference. It will allow the organizers to carefully
plan and organize the sessions and presentations using time slots and locations. Additionally, the
new system will track the review process of each paper alongside the comments and
recommendations retained. Furthermore, the database will allow the organizers to keep track of
all interveners such as the officers, chairs, volunteers, and guests. Ultimately, the new system
/69 12
will enhance the user experience by enabling the users to easily to access a powerful yet simple
keyword search system.
Organizers will have the possibility to easily track information on past conferences, payment
transactions, authors submissions, and paper reviews. The database will be allowing the users to
insert, update, and delete data. Furthermore, a major benefit of the database system will be that
the organizers will no longer need to tediously manually insert, move, and search for the
information they are looking for. Hence, due to the automation process, the users will be able to
get access to the conferences content more efficiently and effectively. Overall, the
implementation of the new database system will significant facilitate the organization of the
conference and the post-conference reporting process to improve the quality and participants
experience for the following editions.
Routine Transactions
The routine transactions are the recurring events that the system will collect and update to the
database. These transactions include but are not limited to:
Maintain (insert, update, delete) persons data.
Maintain (insert, update, delete) papers data.
Maintain (insert, update, delete) information relative to track, sessions, and presentations.
Maintain (insert, update, delete) info relative to registration and payment transactions.
/69 14
Scope and Boundaries
The database is designed to answer all the requirements of ICIS and do all the tasks the manual
method through spreadsheets was able to produce, but much more efficiently. The system will
let International Conference on Information System insert, update, and delete information
related to the individuals taking part to the conference, to the papers and its review process, to
the tracks and session with the presentation slots incorporated within the later one. However, in
spite of the new database capability to complete many different requests and tasks, it has a
certain amount of set boundaries and restrictions. The system cannot directly handle payment
transactions since it does not have the programs necessary to handle such tasks. The new system
is also unable to directly send emails to users as it is not properly connected to an email account
and its subsequent servers. Hence, the organizers will need to create a mailing process that can
be linked to the database to forward information to stakeholders by email. The system will be
unable to be access remotely because it will be solely available on one device. The organizers
would need to connect it to an internet server if they would like to access it from a location other
than where the main computer is located. The system will be unable to satisfy accounting
requirements since it only keep a record of the transactions. The system will be unable to receive
information coming directly from stakeholders other than the organizers maintaining the
database at the moment.
/69 15
Conceptual Design
International Conference on Information Systems Database Business Rules
Business Rule #1
A person can be zero to one author, each author can be one and only one person.
Business Rule #2
An author can present zero to many presentations, each presentation can be presented by one
and only one author.
/69 16
Business Rule #3
An author can write one or more paper, each paper can be written by one or many authors.
Business Rule #4
A person can comment zero or more paper, each paper can be commented zero or many persons.
/69 17
Business Rule #5
A paper can be described by one or more keyword, each keyword can describe one or more
paper.
Business Rule #6
A person can be zero to one reviewer, each reviewer can be one and only one person.
/69 18
Business Rule #7
A reviewer can reviewer one or more paper, each paper is reviewed by one to many reviewers.
Business Rule #8
A reviewer can be employed by one to many conference track, each conference track can employ
one to many reviewers.
/69 19
Business Rule #9
A conference track is hosted by one and only one conference, each conference hosts one to many
conference tracks.
/69 20
Business Rule #11
A guest can acquire zero to many guest meal tickets, each guest meal ticket can be acquired by
one and only one guest.
/69 21
Business Rule #13
A person can be zero to one volunteer, each volunteer can be one and only one person.
/69 22
Business Rule #15
A person can be zero to one attendee, each attendee can be one and only one person.
/69 23
Business Rule #17
An institution can make zero to many payments, each payment can be made by zero to one
institution.
/69 24
Business Rule #19
An attendee has one and only one membership status, each membership status can have one to
many attendees.
/69 25
Business Rule #21
A registration can record one to many attendees, each attendee can have one and only one
registration.
/69 26
Business Rule #23
A person can be zero to one officer, each officer can be one and only one person.
/69 27
Business Rule #25
A sponsor can refer as contact zero to many persons, each person can be zero to one sponsors
contact.
/69 28
/69 29
Business Rule #27
A session can have zero to many presentations, each presentation can be presented at one and
only one session.
/69 30
/69 31
Business Rule #29
A conference track presents one to many papers, each paper can be presented to one and only
one conference track.
/69 32
Logical Data Model
25/
Data Dictionary
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
26/
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
Guest (23)
/69 27
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
PaperKeyword (31)
PaperKeyword_ID Paper Keyword ID CHAR(8) 99999999 00000001-99999999 Yes PK
-922337203685477.5808-
Payment_Amount Payment Amount MONEY 99999999.9999 Yes
922337203685477.5807
/69 28
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
/69 29
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
-922337203685477.5808-
SponsorContribution_Amount Sponsor Contribution as an Amount MONEY 99999999.9999 Yes
922337203685477.5807
SponsorOfficer (29)
/69 30
Table Name (ERD#) Attribute Name Content Type Format Range Required PK or FK FK Reference Table
/69 31
Implementation SQL Server Database
Create Statements SQL Script
/*Create project database First (Alone)*/
CREATE DATABASE Database_ICIS
/*Conference (28)*/
CREATE TABLE Conference(
Conference_ID CHAR(8) UNIQUE NOT NULL,
Conference_StrtDate DATE NOT NULL,
Conference_EndDate DATE NOT NULL,
Conference_Description VARCHAR(MAX) NOT NULL,
PRIMARY KEY(Conference_ID)
);
/*ConferenceTrack (27)*/
CREATE TABLE ConferenceTrack(
ConferenceTrack_ID CHAR(8) UNIQUE NOT NULL,
Track_Descritpion VARCHAR(MAX) NOT NULL,
Track_TopicOfInterest VARCHAR(MAX) NOT NULL,
Conference_ID CHAR(8) NOT NULL,
PRIMARY KEY(ConferenceTrack_ID),
FOREIGN KEY(Conference_ID) REFERENCES Conference(Conference_ID)
ON UPDATE CASCADE
);
/*Person (14)*/
CREATE TABLE Person(
Person_ID CHAR(8) UNIQUE NOT NULL,
Person_LName VARCHAR(30) NOT NULL,
Person_FName VARCHAR(30) NOT NULL,
Person_MName VARCHAR(30) NOT NULL,
Person_Gender CHAR(1) NOT NULL,
Person_Street VARCHAR(MAX) NOT NULL,
Person_City VARCHAR(30) NOT NULL,
Person_State CHAR(2) NOT NULL,
Person_Country VARCHAR(30) NOT NULL,
Person_Zip CHAR(5) NOT NULL,
Person_AreaCode CHAR(3) NOT NULL,
Person_Phone CHAR(7) NOT NULL,
Person_Email VARCHAR(MAX) NOT NULL,
PRIMARY KEY(Person_ID)
);
32/
/*Paper (16)*/
CREATE TABLE Paper(
Paper_ID CHAR(8) UNIQUE NOT NULL,
ConferenceTrack_ID CHAR(8) NOT NULL,
Paper_Title VARCHAR(100) NOT NULL,
Paper_Abstract VARCHAR(MAX) NOT NULL,
Paper_SubmissionDate DATE NOT NULL,
PRIMARY KEY(Paper_ID),
FOREIGN KEY(ConferenceTrack_ID) REFERENCES
ConferenceTrack(ConferenceTrack_ID)
ON UPDATE CASCADE
);
/*Session (1)*/
CREATE TABLE Session(
Session_ID CHAR(8) UNIQUE NOT NULL,
ConferenceTrack_ID CHAR(8) NOT NULL,
Session_Room CHAR(5) NOT NULL,
Session_StrtTime TIME NOT NULL,
Session_EndTime TIME NOT NULL,
Session_Date DATE NOT NULL,
PRIMARY KEY(Session_ID),
FOREIGN KEY(ConferenceTrack_ID) REFERENCES
ConferenceTrack(ConferenceTrack_ID)
ON UPDATE CASCADE
);
/*Sponsor (3)*/
CREATE TABLE Sponsor(
Sponsor_ID CHAR(8) UNIQUE NOT NULL,
Contact_ID CHAR(8) UNIQUE NOT NULL,
Company_Name VARCHAR(MAX) NOT NULL,
Company_Street VARCHAR(30) NOT NULL,
Company_City VARCHAR(30) NOT NULL,
Company_State CHAR(2) NOT NULL,
Company_Zip VARCHAR(10) NOT NULL,
Company_Country VARCHAR(30) NOT NULL,
PRIMARY KEY(Sponsor_ID),
FOREIGN KEY(Contact_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/*Author (7)*/
CREATE TABLE Author(
Author_ID CHAR(8) UNIQUE NOT NULL,
PRIMARY KEY(Author_ID),
FOREIGN KEY(Author_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/69 33
/*Presentation (5)*/
CREATE TABLE Presentation(
Presentation_ID CHAR(8) UNIQUE NOT NULL,
Session_ID CHAR(8) NOT NULL,
Paper_ID CHAR(8) NOT NULL,
Presentation_StrtTime TIME NOT NULL,
Presentation_EndTime TIME NOT NULL,
PRIMARY KEY(Presentation_ID),
FOREIGN KEY(Session_ID) REFERENCES Session(Session_ID),
FOREIGN KEY(Paper_ID) REFERENCES Paper(Paper_ID)
ON UPDATE CASCADE
);
/*AuthorPresentation (4)*/
CREATE TABLE AuthorPresentation(
AuthorPresentation_ID CHAR(8) UNIQUE NOT NULL,
Author_ID CHAR(8) NOT NULL,
Presentation_ID CHAR(8) NOT NULL,
PRIMARY KEY(AuthorPresentation_ID),
FOREIGN KEY(Author_ID) REFERENCES Author(Author_ID),
FOREIGN KEY(Presentation_ID) REFERENCES Presentation(Presentation_ID)
ON UPDATE CASCADE
);
/*PaperAuthor (6)*/
CREATE TABLE PaperAuthor(
PaperAuthor_ID CHAR(8) UNIQUE NOT NULL,
Author_ID CHAR(8) NOT NULL,
Paper_ID CHAR(8) NOT NULL,
PaperAuthor_Order INTEGER NOT NULL,
PRIMARY KEY(PaperAuthor_ID),
FOREIGN KEY(Author_ID) REFERENCES Author(Author_ID),
FOREIGN KEY(Paper_ID) REFERENCES Paper(Paper_ID)
ON UPDATE CASCADE
);
/*SessionChair (8)*/
CREATE TABLE SessionChair(
SessionChair_ID CHAR(8) UNIQUE NOT NULL,
Session_ID CHAR(8) NOT NULL,
Chair_ID CHAR(8) NOT NULL,
PRIMARY KEY(SessionChair_ID),
FOREIGN KEY(Session_ID) REFERENCES Session(Session_ID),
FOREIGN KEY(Chair_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/69 34
/*RegistrationFee (21)*/
CREATE TABLE RegistrationFee(
RegistrationFee_ID CHAR(8) UNIQUE NOT NULL,
RegistrationFee_Type VARCHAR(100) NOT NULL,
RegistrationFee_Option VARCHAR(10),
RegistrationFee_AgeGroup VARCHAR(10),
PRIMARY KEY(RegistrationFee_ID)
);
/*Registration (22)*/
CREATE TABLE Registration(
Registration_ID CHAR(8) UNIQUE NOT NULL,
Conference_ID CHAR(8) NOT NULL,
PRIMARY KEY(Registration_ID),
FOREIGN KEY(Conference_ID) REFERENCES Conference(Conference_ID)
ON UPDATE CASCADE
);
/*Institution (9)*/
CREATE TABLE Institution(
Institution_ID CHAR(8) UNIQUE NOT NULL,
Institution_Name VARCHAR(30) NOT NULL,
PRIMARY KEY(Institution_ID)
);
/*MembershipStatus (11)*/
CREATE TABLE MembershipStatus(
Membership_ID CHAR(8) UNIQUE NOT NULL,
Membership_Type VARCHAR(30) NOT NULL,
Membership_Expiration DATE,
Membership_Renewal DATE,
PRIMARY KEY(Membership_ID)
);
/*Attendee (12)*/
CREATE TABLE Attendee(
Attendee_ID CHAR(8) UNIQUE NOT NULL,
Attendee_Occupation VARCHAR(30) NOT NULL,
Institution_ID CHAR(8) NOT NULL,
Membership_ID CHAR(8) NOT NULL,
Registration_ID CHAR(8) NOT NULL,
RegistrationFee_ID CHAR(8) NOT NULL,
PRIMARY KEY(Attendee_ID),
FOREIGN KEY(Institution_ID) REFERENCES Institution(Institution_ID),
FOREIGN KEY(Attendee_ID) REFERENCES Person(Person_ID),
FOREIGN KEY(Membership_ID) REFERENCES MembershipStatus(Membership_ID),
FOREIGN KEY(Registration_ID) REFERENCES Registration(Registration_ID),
FOREIGN KEY(RegistrationFee_ID) REFERENCES
RegistrationFee(RegistrationFee_ID)
ON UPDATE CASCADE
);
/69 35
/*Payment (2)*/
CREATE TABLE Payment(
Payment_ID CHAR(8) UNIQUE NOT NULL,
Payment_Type VARCHAR(10) NOT NULL,
Payment_Amount MONEY NOT NULL,
Institution_ID CHAR(8) NULL,
Attendee_ID CHAR(8) NULL,
PRIMARY KEY(Payment_ID),
FOREIGN KEY(Institution_ID) REFERENCES Institution(Institution_ID),
FOREIGN KEY(Attendee_ID) REFERENCES Attendee(Attendee_ID)
ON UPDATE CASCADE
);
/*Officer (10)*/
CREATE TABLE Officer(
Officer_ID CHAR(8) UNIQUE NOT NULL,
Officer_AdmRole VARCHAR(30) NOT NULL,
Officer_AdmStrtDate DATE NOT NULL,
Officer_AdmEndDate DATE,
PRIMARY KEY(Officer_ID),
FOREIGN KEY(Officer_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/*VolunteerHoursSlot (20)*/
CREATE TABLE VolunteerHoursSlot(
VolunteerHoursSlot_ID CHAR(8) UNIQUE NOT NULL,
VolunteerHours_Strt TIME NOT NULL,
VolunteerHours_End TIME NOT NULL,
VolunteerHours_Date DATE NOT NULL,
PRIMARY KEY(VolunteerHoursSlot_ID)
);
/*Volunteer (13)*/
CREATE TABLE Volunteer(
Volunteer_ID CHAR(8) UNIQUE NOT NULL,
PRIMARY KEY(Volunteer_ID),
FOREIGN KEY(Volunteer_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/*Comment (15)*/
CREATE TABLE Comment(
Comment_ID CHAR(8) UNIQUE NOT NULL,
Paper_ID CHAR(8) NOT NULL,
Person_ID CHAR(8) NOT NULL,
Comment_Object VARCHAR(30) NOT NULL,
Comment_Core VARCHAR(MAX) NOT NULL,
PRIMARY KEY(Comment_ID),
FOREIGN KEY(Paper_ID) REFERENCES Paper(Paper_ID),
FOREIGN KEY(Person_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE );
/69 36
/*Reviewer (18)*/
CREATE TABLE Reviewer(
Reviewer_ID CHAR(8) UNIQUE NOT NULL,
Reviewer_PhDField VARCHAR(30) NOT NULL,
PRIMARY KEY(Reviewer_ID),
FOREIGN KEY(Reviewer_ID ) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/*PaperReview (17)*/
CREATE TABLE PaperReview(
PaperReview_ID CHAR(8) UNIQUE NOT NULL,
Reviewer_ID CHAR(8) NOT NULL,
Paper_ID CHAR(8) NOT NULL,
PaperReview_ConceptualSignificance VARCHAR(30) NOT NULL,
PaperReview_PracticalSignificance VARCHAR(30) NOT NULL,
PaperReview_ConductOfResearch VARCHAR(30) NOT NULL,
PresentationOfResearch VARCHAR(30) NOT NULL,
PaperReview_DateAssigned DATE NOT NULL,
PaperReview_DateComplete DATE,
PaperReview_Decision VARCHAR(10),
PRIMARY KEY(PaperReview_ID),
FOREIGN KEY(Reviewer_ID) REFERENCES Reviewer(Reviewer_ID),
FOREIGN KEY(Paper_ID) REFERENCES Paper(Paper_ID)
ON UPDATE CASCADE
);
/*VolunteerTime (19)*/
CREATE TABLE VolunteerTime(
VolunteerTime_ID CHAR(8) UNIQUE NOT NULL,
Volunteer_ID CHAR (8) NOT NULL,
VolunteerHoursSlot_ID CHAR(8) NOT NULL,
PRIMARY KEY(VolunteerTime_ID),
FOREIGN KEY(Volunteer_ID) REFERENCES Volunteer(Volunteer_ID),
FOREIGN KEY(VolunteerHoursSlot_ID) REFERENCES
VolunteerHoursSlot(VolunteerHoursSlot_ID)
ON UPDATE CASCADE
);
/*Guest (23)*/
CREATE TABLE Guest(
Guest_ID CHAR(8) UNIQUE NOT NULL,
PRIMARY KEY(Guest_ID),
FOREIGN KEY(Guest_ID) REFERENCES Person(Person_ID)
ON UPDATE CASCADE
);
/69 37
/*GuestMealTicket (24)*/
CREATE TABLE GuestMealTicket(
GuestMealTicket_ID CHAR(8) UNIQUE NOT NULL,
Guest_ID CHAR(8) NOT NULL,
GuestMealTicket_Type VARCHAR(10) NOT NULL,
PRIMARY KEY(GuestMealTicket_ID),
FOREIGN KEY(Guest_ID) REFERENCES Guest(Guest_ID)
ON UPDATE CASCADE
);
/*TrackReviewer (25)*/
CREATE TABLE TrackReviewer(
TrackReviewer_ID CHAR(8) UNIQUE NOT NULL,
Reviewer_ID CHAR(8) NOT NULL,
ConferenceTrack_ID CHAR(8) NOT NULL,
PRIMARY KEY(TrackReviewer_ID),
FOREIGN KEY(Reviewer_ID) REFERENCES Reviewer(Reviewer_ID),
FOREIGN KEY(ConferenceTrack_ID) REFERENCES
ConferenceTrack(ConferenceTrack_ID)
ON UPDATE CASCADE
);
/*TrackChair (26)*/
CREATE TABLE TrackChair(
TrackChair_ID CHAR(8) UNIQUE NOT NULL,
Person_ID CHAR(8) NOT NULL,
ConferenceTrack_ID CHAR(8) NOT NULL,
PRIMARY KEY(TrackChair_ID),
FOREIGN KEY(Person_ID) REFERENCES Person(Person_ID),
FOREIGN KEY(ConferenceTrack_ID) REFERENCES
ConferenceTrack(ConferenceTrack_ID)
ON UPDATE CASCADE
);
/*SponsorOfficer (29)*/
CREATE TABLE SponsorOfficer(
SponsorOfficer_ID CHAR(8) UNIQUE NOT NULL,
Sponsor_ID CHAR(8) NOT NULL,
Officer_ID CHAR(8) NOT NULL,
PRIMARY KEY(SponsorOfficer_ID),
FOREIGN KEY(Sponsor_ID) REFERENCES Sponsor(Sponsor_ID),
FOREIGN KEY(Officer_ID) REFERENCES Officer(Officer_ID)
ON UPDATE CASCADE
);
/*Keyword (30)*/
CREATE TABLE Keyword(
Keyword_ID CHAR(8) UNIQUE NOT NULL,
Keyword CHAR(30) NOT NULL,
PRIMARY KEY(Keyword_ID)
);
/69 38
/*PaperKeyword (31)*/
CREATE TABLE PaperKeyword(
PaperKeyword_ID CHAR(8) UNIQUE NOT NULL,
Paper_ID CHAR(8) NOT NULL,
Keyword_ID CHAR(8) NOT NULL,
PRIMARY KEY(PaperKeyword_ID),
FOREIGN KEY(Paper_ID) REFERENCES Paper(Paper_ID),
FOREIGN KEY(Keyword_ID) REFERENCES Keyword(Keyword_ID)
ON UPDATE CASCADE
);
/*SponsorContribution (32)*/
CREATE TABLE SponsorContribution(
SponsorContribution_ID CHAR(8) UNIQUE NOT NULL,
Sponsor_ID CHAR(8) NOT NULL,
SponsorContribution_Amount MONEY NOT NULL,
PRIMARY KEY(SponsorContribution_ID),
FOREIGN KEY(Sponsor_ID) REFERENCES Sponsor(Sponsor_ID)
ON UPDATE CASCADE);
/69 39
Insert Statements SQL Script
USE Database_ICIS
/*Conference (28)
INSERT INTO Conference
VALUES(Conference_ID, Conference_StrtDate, Conference_EndDate,
Conference_Description);*/
/*ConferenceTrack (27)
INSERT INTO ConferenceTrack
VALUES(ConferenceTrack_ID, Track_Name, Track_Description, Conference_ID);*/
/*Person (14)
INSERT INTO Person
VALUES(Person_ID, Person_LName, Person_FName, Person_MName, Person_Gender,
Person_Street, Person_City, Person_State,
Person_Zip, Person_Country, Person_AreaCode, Person_Phone, Person_Email);*/
/69 41
INSERT INTO Person
VALUES('14000006','Alonzo','Maria','C','F','0494 45th
Ave','Tampa','FL','USA','33601', '813','2330922','MAlonzo@gmail.com');
/69 42
INSERT INTO Person
VALUES('14000019', 'Croft', 'Laura', 'E', 'F', '712 Ocean Ave', 'Los
Angles', 'CA', 'USA', '90210', '415', '4693697', 'Lcroft@yahoo.com');
/69 43
INSERT INTO Person
VALUES('14000032', 'Solarsky', 'Adam', 'Q', 'M', '5837 2nd St', 'Phoenix',
'AZ', 'USA', '86312', '480', '7893266', 'Hammer@gmail.com');
/*Paper (16)
INSERT INTO Paper
VALUES(Paper_ID, ConferenceTrack_ID, Paper_Title, Paper_Abstract,
Paper_SubmissionDate);*/
/69 44
INSERT INTO Paper
VALUES('16000002','27000001','Breaking Through the Economic Barriers of
Anesthesia MIS','Anesthesia information management systems (AIMS) are being
increasingly used to assist the delivery and documentation of anesthesia services
in the United States. The major benefits of AIMS cited in the literature are the
ability to (1) reduce costs, (2) facilitate quality assurance and quality
improvement processes, (3) increase the accuracy and completeness of the
anesthesia record, and (4) improve adherence to recommended guidelines. The major
drawback, especially for rural hospitals, is the cost. This article identifies 2
of the main elements of AIMS that exist in information technology and data
systems already present in a hospital. In this project, the medication dispensing
system was used to achieve a 70% reduction in drug costs, and a simple electronic
database was created, which detected adverse events that were missed with the
legacy quality assurance system. There was no additional cost to the hospital to
realize these benefits because this project utilized technologies and data
systems already in place and staff time was part of the normal workload. This
project showed that it is possible to achieve 2 of the major benefits of an AIMS
without the major cost of purchasing one.','10/01/2016')
/69 45
INSERT INTO Paper
VALUES('16000004','27000002','Application of Agent Methodology in
Healthcare Information Systems.','This paper presents a case study to describe
the features and the phases of the two agent methodologies. The Gaia methodology
for agent oriented analysis and design, Tropos is a detailed agent oriented
software engineering methodology to explore each methodologys ability to present
solutions for small problems. Also we provide an attempt to discover whether the
methodology is in fact understandable and usable. In addition we were collecting
and taking notes of the advantages and weaknesses of these methodologies during
the study analysis for each methodology and the relationships among their models.
The Guardian Angle: Patient-Centered Health Information System (GA: PCHIS) is the
personal system to help track, manage, and interpret the subjects health history,
and give advice to both patient and provider is used as the case study throughout
the paper.','11/01/2017')
/69 46
INSERT INTO Paper
VALUES('16000006','27000003','The role of GIS in Digital Earth
education.','A growing number of educators worldwide have become convinced that
geotechnologies - including geographic information systems (GIS), global
positioning systems (GPS), and remote sensing - are key technologies to prepare
students to be tomorrows decision makers. Grappling with local, regional, and
global issues of the 21st century requires people who think spatially and who can
use geotechnologies. Some educators teach geotechnologies as a discipline,
emphasising skills. Other educators use geotechnologies as a tool to teach
content, such as geography, history, environmental studies, Earth Science,
biology, mathematics, economics and other disciplines. Issues such as traffic,
population growth, urban sprawl, energy, water, crime, human health, biodiversity
and sustainable agriculture are growing in complexity, exist at every scale and
increasingly affect peoples everyday lives. Each of these issues has a spatial
component. Drivers for geotechnology education include educational content
standards, constructivism, the school-to-career movement, active learning,
citizenship education, authentic practice and assessment, interdisciplinary
education, community connections and a sustained, increasing demand for GIS
professionals. Digital Earth is an ideal framework for contextualising domains of
inquiry. The Digital Earth community can have a significant impact on the growth
of geotechnologies in education, and conversely, the growth of geotechnologies in
education and society can foster the forward movement of Earth systems concepts.
','12/01/2017')
/*Session (1)
INSERT INTO Session
VALUES(Session_ID, ConferenceTrack_ID, Session_Room, Session_StrtTime,
Session_EndTime, Session_Date); */
/*Sponsor (3)
INSERT INTO Sponsor
VALUES(Sponsor_ID, Contact_ID, Company_Name, Company_Street, Company_City,
Company_State, Company_Zip, Company_Country);*/
/*Author (7)
INSERT INTO Author
VALUES(Author_ID);*/
/*Presentation (5)
INSERT INTO Presentation
VALUES(Presentation_ID, Session_ID, Paper_ID, Presentation_StrtTime,
Presentation_EndTime);*/
/69 48
/*AuthorPresentation (4)
INSERT INTO AuthorPresentation
VALUES(AuthorPresentation_ID, Author_ID, Presentation_ID);*/
/*PaperAuthor (6)
INSERT INTO PaperAuthor
VALUES(PaperAuthor_ID,Author_ID,Paper_ID,PaperAuthorOrder);*/
/*SessionChair (8)
INSERT INTO SessionChair
VALUES(SessionChair_ID, Session_ID, Chair_ID);*/
/*RegistrationFee (21)
INSERT INTO RegistrationFee
VALUES(RegistrationFee_Id, RegistrationFee_Type, RegistrationFee_Option,
RegistrationFee_AgeGroup);*/
/*Registration (22)
INSERT INTO Registration
VALUES(Registration_ID, Conference_ID);*/
/69 51
/*Institution (9)
INSERT INTO Institution
VALUES(Institution_ID, Institution_Name);*/
/*MembershipStatus (11)
INSERT INTO MembershipStatus
VALUES(Membership_ID, Membership_Type, Membership_Expiration,
Membership_Renewal);*/
/*Attendee (12)
INSERT INTO Attendee
VALUES(Attendee_ID, Attendee_Occupation, Institution_ID, Membership_ID,
Registration_ID, Registration_Fee_ID);*/
/69 53
VALUES('14000018','Professional','09000006','11000003','22000001','2100000
8')
/69 54
INSERT INTO Attendee
VALUES('14000034','Academic','09000003','11000001','22000001','21000002')
/*Payment (2)
INSERT INTO Payment
VALUES(Payment_ID, Payment_Type, Payment_Amount, Institution_ID, Attendee_ID);*/
/*Officer (10)
INSERT INTO Officer
VALUES(Officer_ID, Officer_AdmRole, Officer_AdmStrtDate, Officer_AdmEndDate*/
/*VolunteerHoursSlot (20)
INSERT INTO VolunteerHoursSlot
VALUES(VolunteerHoursSlot_ID, VolunteerHours_StrT, VolunteerHours_End,
VolunteerHours_Date);*/
/*Volunteer (13)
INSERT INTO Volunteer
VALUES(Volunteer_ID);*/
/*Comment (15)
INSERT INTO Comment
VALUES(Comment_ID, Paper_ID, Person_ID, Comment_Object, Comment_Core);*/
/*Reviewer (18)
INSERT INTO Reviewer
VALUES(Reviewer_ID, Reviewer_PhDField);*/
/69 57
/*PaperReview (17)
INSERT INTO PaperReview
VALUES(PaperReview_ID, Reviewer_ID, Paper_ID, PaperReview_ConceptualSignificance,
PaperReview_PracticalSignificance, PaperReview_ConductOfResearch,
PaperRewview_PresentationOFResearch, PaperReview_Dateassigned,
PaperReview_DateComplete, PaperReview_Decision);*/
/69 58
/*VolunteerTime (19)
INSERT INTO VolunteerTime
VALUES(VolunteerTime_ID, Volunteer_ID, VolunteerHoursSlot_ID);*/
/*Guest (23)
INSERT INTO Guest
VALUES(Guest_ID);*/
/*GuestMealTicket (24)
INSERT INTO GuestMealTicket
VALUES(GuestMealTicket_ID, Guest_ID, GuestMealTicket_Type);*/
/69 59
/*TrackReviewer (25)
INSERT INTO TrackReviewer
VALUES(TrackReviewer_ID, ReviewerID, ConferenceTrack_ID);*/
/*TrackChair (26)
INSERT INTO TrackChair
VALUES(TrackChair_ID, Person_ID, ConferenceTrack_ID);*/
/69 60
/*SponsorOfficer (29)
INSERT INTO SponsorOfficer
VALUES(SponsorOfficer_ID, Sponsor_ID, Officer_ID*/
/*Keyword (30)
INSERT INTO Keyword
VALUES(Keyword_ID, Keyword);*/
/*PaperKeyword (31)
INSERT INTO PaperKeyword
VALUES(PaperKeyword_ID, Paper_ID, Keyword_ID);*/
/69 62
INSERT INTO PaperKeyword
VALUES('31000015','16000005','30000010')
/*SponsorContribution (32)
INSERT INTO SponsorContribution
VALUES(SponsorContribution_ID,Sponsor_ID,SponsorContribution_Amount)*/
/69 63
Select Statements SQL Script
USE Database_ICIS
/69 65
/*Detailed revenue report that lists the payment of each participant grouped by
type of registration and sorted alphabetically by name and category*/
SELECT RegistrationFee_Option, Institution_Name, Person_LName,
SUM(Payment_Amount) AS Revenue
FROM Attendee
JOIN Institution
ON Attendee.Institution_ID = Institution.Institution_ID
JOIN Payment
ON Payment.Attendee_ID = Attendee.Attendee_ID
JOIN Person
ON Person.Person_ID = Attendee.Attendee_ID
JOIN RegistrationFee
ON RegistrationFee.RegistrationFee_ID = Person.RegistrationFee_ID
GROUP BY RegistrationFee_Option, Institution_Name, Person_LName
ORDER BY Person_LName, RegistrationFee_Option;
/*Listing of all volunteers who were working on the second day of the
conference.*/
SELECT Person_LName, Person_FName
FROM Volunteer
JOIN Person
ON Volunteer.Volunteer_ID = Person.Person_ID
JOIN VolunteerTime
ON Volunteer.Volunteer_ID = VolunteerTime.Volunteer_ID
WHERE VolunteerHoursSlot_ID = '20000006';
/*Listing of officers working for each sponsor ordered by sponsor company name*/
SELECT Company_Name, Person_LName
FROM Sponsor
JOIN SponsorOfficer
ON SponsorOfficer.Sponsor_ID = Sponsor.Sponsor_ID
JOIN Person
ON Person.Person_ID = Sponsor.Contact_ID
ORDER BY Company_Name;
/69 66
SQL Report Table
Report Requirements Script Results Table/Fields
67/
/69 68
Report Requirements Script Results Table/Fields
SELECT AVG(SponsorContribution_Amount) AS
14 Summary showing the average sponsor contribution AvgSponsorContribution 3500000 SponsorCoontribution > SponsorContribution_Amount
FROM SponsorContribution;
/69 70