Embed Size (px)
Citation preview
Georgia State University CIS Internship Database Project
Produced by
Steve Bean, John Hupp, Archie Otu,
Shanell Overton, Yan Wang
CIS 8040 Spring 2007
Dr. Vijay Vaishnavi
2
Table of Contents MILESTONE 1: Team Formation 3 MILESTONE 2: Project Proposal 4
Project Description 4 Client 4 Statement of Purpose 4 Existing System 4 Examples of Internship System Documents 6 Advantages and Drawbacks of Current System 8 Project Scope 9 Relevant Data 10 Project Plan and Estimated Work Hours 13
MILESTONE 3: Conceptual Design 15 Conceptual Model Diagram 15 Data Domain 16 Relationship Domain 19 MILESTONE 4: Logical Design 20 Logical Model Diagram 20 Data Dictionary 21 System Prototype 27 Quick Reference Guide 27 Forms 29 Reports 34
Business Domain Assumptions 39 Comments 40
Team Meeting Minutes 41
3
MILESTONE 1: Team Formation Team Role List:
• Team Leader – Yan Wang • Documenter – Shanell Overton • TechGuru – John Hupp • Implementation Leader – Archie Otu • Client PoC – John Hupp • Instructor PoC – Steve Bean
Meeting Schedule:
• Monday’s at 6:00 pm at the Lenox Mall Food Court • Other meetings as needed
4
MILESTONE 2: Project Proposal Project Description
The growing need to improve the business process by efficiently managing data is the
primary reason for a system change. IT personnel have been working day and night to
develop an IT system that will eliminate the paper handling of internship information.
Through constant communication between IT personnel and CIS administration, a robust
system will be developed that will historically track the progress of internships and
improve the communication between students, employers, and faculty.
Client
CIS Department:
• Primary Advisors: Dr. Mark Keil, Chairman, Dr. Carl Stucke, Associate Chairman
and
• Internship Coordinator: John Hupp
• General Advisors: Faculty Sponsors, Business Managers, and Students
Statement of Purpose
The purpose of the CIS Internship database system is to maintain the data that is used
and generated to support the CIS Department’s Internship Program for students and
employers and to facilitate the cooperation and sharing of information among students,
faculty sponsors, employers, and CIS administration.
Existing System
The existing Internship System would be replaced by a database system. Although the
process for students, faculty sponsors, and employers would remain much the same, the
presence of a shared database to maintain internship data would significantly improve
the overall operation of the system. A new database system would replace the paper-
based work presently in place, and it would provide reporting, shared access, and
historical analysis that is not available using today’s system.
The current Internship System is entirely paper-based with a web front-end that emails
application data to the Internship Coordinator. The basic student process is as follows:
5
Fill out the on-line http://www2.cis.gsu.edu/cis/internship/Stuappl.aspapplication form
(emailed to Internship Coordinator)
Submit the resume on line (emailed to Internship Coordinator)
Email or submit the copy of an unofficial transcript (get from GoSolar) to verify
the current GPA
Find a employer
The Internship Office and RCB Career Management Office identifies and
posts opportunities with employers who wish interns
The Internship Office selects the student intern applicants who best meet
the internship needs
The student may also assist in identifying companies who wish interns
but there is no guarantee that the student will be selected by the
Internship Office as one of the best qualified candidates for that
company's internship
Obtain a faculty sponsor
The faculty sponsor reviews the internship proposal form and advises
the student concerning credit hours and responsibilities
The faculty sponsor assists the student intern with the position and
reviews status reports, journals, and final internship reports as agreed
upon in the internship proposal
Interview
The student will be contacted directly from the potential employers or the
internship coordinator for the interviews.
Sign internship agreement after being selected (obtain from the internship office)
and approved by faculty sponsor and employer.
Perform internships and maintain journals, status reports, and complete final
reports as agreed in internship proposal.
The employer will fill out the student evaluation form after completing the
internship.
6
Examples of Internship System Documents
The following documents are representative of those used in the current system. A
complete set of forms and reports are available upon request, and these will be analyzed
by the database development team as they build the Internship Database.
Graduate Internship Authorization Form – CIS 8391
Undergraduate Internship Authorization Form – CIS 4970
Student Application Form from website -
http://www2.cis.gsu.edu/cis/internship/Stuappl.asp
Employer Information Form from website (not shown in examples) -
http://www2.cis.gsu.edu/cis/internship/empapp.asp
Internship Proposal Form - CIS 4970
7
REQUEST FOR AUTHORIZATION FOR CIS 83 91
Student
Name:
Phone:
E-Mail:
The student will be contacted at this e -mail address
with the CRN when this internship is approved.
Student #:
Semester :
Credit Hours :
Course: CIS 8391 Field Study , Internship
Reason for student requesting CIS 8391:
I have been offered a full -time internship position by the company called xxx. This company is experiencing business growth. This position is also a great opportunity for me to show my skills
and get more experience about administering the relational databases. With this internship, I am also willing to create a value for my employer in terms of creating better technology solutions to
enable them to improve their competencies.
Descriptions of assignmen t/activity for cour se:
To fulfill the requ irements of the class, I will submit a written report and also a student journal.
Student Journal
1. What work I did for the host company, 2. When I worked (dates & hours),
3. How my work advanced my ability to a chieve my objectives, 4. How my work contributed value to the business,
5. What problems I encountered and my efforts or ideas for resolving them,
6. How was the knowledge acquired in the MS -CIS program helpful for me in resolving problems at work?
Writte n Report
At the end o f the field study experience, I will prepare a written report documenting the learning
experience. The report will contain the following information :
• Page 1: Field Study Company Information. On the first page of the report, I will p rovide the name of the field study company, the name of the department, the name of the supervisor, and the title of the
position held as an intern. I will provide information that will enable the field study coordinator the ability to contact the supervi sor if there are questions about the completion of the field study.
• Page 2: Responsi bilities and Tasks/Projects. I will list the responsibilities and/or tasks and projects fulfilled or completed while working as an intern.
• Page 3: Lessons Learned . I wil l provide a narrative discussion of the lessons learned while working as
an intern
________________________________________
Student Signature Date
By signing this request, I agree to fulfill all requirements for CIS 8391.
_________________________ ________________
Faculty Signature Date
________________________________________
Internship Coordinator Date
_________________________________________
Department Chair Date
Dr Carl Stucke
____ Accept _____ Reject
Email Address:
Evening Phone:
Daytime Phone:
Zip Code:
Address:
Expected Graduation Date:
(mm/ yy):
GPA
Yes NoCompleted Programming Track:
Junior Seni
orClass:
Yes NoCIS Major (required):
Student ID (Last 5 digits of SS#):
First Name:
Last Name:
Student Internship Application Form (Step 1 in applying)
Please fill out this Application FormYou must upload your resume in next step to ensure completion of this
application for an internship.
Email Address:
Evening Phone:
Daytime Phone:
Zip Code:
Address:
Expected Graduation Date:
(mm/ yy):
GPA
Yes NoCompleted Programming Track:
Junior Seni
orClass:
Yes NoCIS Major (required):
Student ID (Last 5 digits of SS#):
First Name:
Last Name:
Email Address:
Evening Phone:
Daytime Phone:
Zip Code:
Address:
Expected Graduation Date:
(mm/ yy):
GPA
Yes NoCompleted Programming Track:
Junior Seni
orClass:
Yes NoCIS Major (required):
Student ID (Last 5 digits of SS#):
First Name:
Last Name:
Student Internship Application Form (Step 1 in applying)
Please fill out this Application FormYou must upload your resume in next step to ensure completion of this
application for an internship.
CIS 4970 Based on Internship —Spring 2005 Student Name: xx
Major: CIS
Year: Senior
Internship Outline and Objectives Company and Internship Information
B G Corporation, an advanced technology company, was formed in March 1995 with the merger of two of the world's premier technology companies, B Corporation and G Corporation.
Headquartered in Bethesda, Maryland, B G employs about 130,000 people worldwide and is principally
engaged in the research, design, development, manufacture and integration of advance d technology systems, products and services.
B G is led by xxx , president and chief executive officer.
CUSTOMER BASE: As a lead systems integrator and information technology company, nearly 80% of B G's business is with the U.S. Department of Defense and the U.S. federal government agencies. In fact, B G is
the largest provider of IT services, systems integration, and training to the U.S. Government. The remaining portion of B G's business is comprised of international government and some commercial sales of our products, services and platforms.
FINANCIAL PERFORMANCE: The Corporation reported 2003 sales of $31.8 billion, a backlog of more than
$75 billion and free cash flow of $1.8 billion.
ORGANIZATION: B G's operating units are organized into broad bus iness areas.
• Aeronautics, with approximately $10.2 billion in 2003 sales, includes tactical aircraft, airlift, and aeronautical
research and development lines of business.
• Electronic Systems, with approximately $8.9 billion in 2003 sales, includes missil es and fire control, naval systems, platform integration, and C4I lines of business.
• Integrated Systems and Solutions, with approximately $3.4 billion in 2003 sales, will leverage our existing and emerging capabilities to address customers' growing needs for highly integrated systems and solutions. As customers move toward a more "network -centric" as opposed to "platform -centric" concept of operations, B G is
focusing its formidable strengths in this arena.
• Space Systems, with approximately $6.0 billion i n 2003 sales, includes space launch, commercial satellites, government satellites, and strategic missiles lines of business.
• Technology Services, with approximately $3.1 billion in 2003 sales, includes federal services, energy programs, government and com mercial IT and aeronautical/aerospace services lines of business.
Objectives:
• Explore/Experience career path opportunities throughout engineering/manufacturing
organizations within B G by participating on day to day basis in problem solving and
communica tion initiatives tied to intern's career path in an effort to improve
process/system efficiency and allow intern exposure to organizational career possibilities.
Achieve the se objectives by carrying out the following activities within the Intern Duties
s hown below :
• Requirements elicitation and documentation;
8
Advantages and Drawbacks of Current System
Currently, the internship records are maintained manually on paper, and problems occur
when people need to review current and prior internship activities. Often records are
missing since there is no centrally managed filing system for student, faculty sponsor,
and employer paperwork. Additionally, reports on internships by employer are not
available, and this information is kept in the memories of those engaged in administering
the program. The lack of shared information and historical data prevents the program
from effectively and efficiently achieving its objectives at the level that it could with a
database system.
Additionally, records are completed inconsistently. As a result, the data available for
each internship is not always the same, and some changes are not carried forward to
other forms and paperwork accurately. In general, the program needs a centralized
means of sharing, protecting, and managing its data in order to reach expected levels of
performance and achievement. With a shared database the Internship Program will be
better able to process, monitor, and analyze its performance and services. Students will
be enrolled and monitored more quickly and orderly. Faculty sponsors will be better
informed and able to submit evaluations. Business employers will be more responsively
managed and positions filled with qualified students.
The program today does a great deal of service to all concerned, the department, the
students, the employers, and the faculty. However, a shared database will provide the
opportunity to achieve higher levels of quality and performance by enabling stakeholders
to gain access to shared and accurate data.
9
Project Scope
The system definition stage is to define the scope and boundary of the database system
and its major user views. The data collected so far is analyzed to define the boundary of
the internship database system as shown below. The central part of the project is to
improve the internship management level in CIS department, which involves employers,
faculties, jobs, students, and administrator. However, the employer end human resource
management, such as employer HR, employer payroll, and student records update work,
such as transcript, courses update will not be considered in the database system. In
addition, the database will only be used for internship management; therefore, the full-
time job position data will not be collected also.
Employer HR
Employer Payroll
Employer AdministratorJob
Faculty
Student
Transcript CoursesFull-Time
Position
System Boundary
10
Relevant Data Below is the list of data that will be stored in the system: 1. Student
a. Student’s information collect the data of basic information of the applicants, which will be obtained from online application form. Last Name: string First Name: string Student ID: string CIS Major: Boolean (Y/N) Class: Boolean (junior/senior) Completed Programming Track: Boolean (Y/N) GPA: Double Interested job category Expected Graduation Date: String Address: string Daytime Phone: string Evening Phone: string Evening Phone: string Email Address: string (multiple values)
b. Student’s internship journal collect the data of journal report written by the student, which will from get from the Weekly Internship Journal form. Student Name: string Internship No: integer Internship Position: string Internship Status: string Date (Week covered by journal entries): string Annotated descriptive list of activities per day: Amount of time devoted to each activity per day: double Total hours worked per the day and week: double
2. Employer
a. Employer Information will be acquired from employer internship request form. Organization Name: string Contact Person: string
First Name Last Name Middle Name
Title: string Physical Address: string Mailing Address: string Phone: string Email Address: string Organization Website Address: string
b. Employer Evaluation of Student will be obtained from the Employer
Evaluation of Student form. Supervisor’s name: Last Name First Name Middle Name Company Name Email Address
11
Summary of main contributions: Quality of work Attitude towards work Technical skills Communication skills Interpersonal skills Ability to learn Judgment Dependability Suggestions for improvement
3. Job Job information will be got from employer internship request form. Internship title: string Resume Submission Deadline: string Number of Internship Opening Internship location:
City State
Company Name: string Available Season Job Category Internship No 4. Faculty Faculty Sponsors Information will be collected when faculty sponsor signed the document. Faculty sponsor’s name First name Last name Telephone: string Position: string Email Address: string 5. Administrator Administrator information will be collected when administrator is assigned to the position and authorized to access to the database. Name Address Title Position Email Telephone Date of Service
Start Date End Date
12
Functions the database will serve The database must allow for the maintenance of all information by the appropriate
persons. It must also allow for searches and the running of standard and ad hoc reports.
The standard reports will be those that are used most frequently or run at specific
intervals, i.e. the first of the month, every week, etc. The ad hoc reports will be created
by the appropriate personnel to suit their needs. The list of standard outputs is not all
inclusive and may be added to or deleted from in the future.
Maintenance
• To maintain (enter, update, and delete) data on students. • To maintain (enter, update, and delete) data on administrators. • To maintain (enter, update, and delete) data on jobs. • To maintain (enter, update, and delete) data on faculty. • To maintain (enter, update, and delete) data on employers.
Searches
• To perform searches on students. • To perform searches on administrators. • To perform searches on jobs. • To perform searches on faculty. • To perform searches on employers.
Reports
• To report on students. • To report on administrators. • To report on jobs. • To report on faculty. • To report on employers.
Standard Outputs
• Listing of all students currently on internships through the CIS department • Listing of all internships and jobs by status by term • All companies that have requested internships • All open jobs and their qualifications • Unfilled requests for interns by date of request • Feedback from companies on interns • Faculty sponsors with no assigned students • All faculty sponsors and internships by term • Employer details and history • Date of most recent internship at a particular company • Number and history of internships at a particular company
13
Project Plan and Estimated Work Hours The estimated cost to complete this project is 370 person-hours to be divided among five
developers. These preliminary estimates are based on an initial project review and the
assigned deliverables. Efforts will be focused on the planning, requirements, and
database design phases of the development cycle, and will exclude actual system
implementation and maintenance; however, a working prototype model will be
developed to demonstrate the database functionality.
14
Dat
a D
omai
n
Entit
y N
ame
Attr
ibut
esD
escr
iptio
nD
ata
Type
& L
engt
h C
onst
rain
tB
usin
ess
Rul
eA
pplic
atio
nst
uden
tID
Uni
quel
y id
entif
ies
the
stud
ent (
Prim
ary
Key
)nv
arch
ar(1
0)ca
n no
t be
null
appl
No
Ass
igne
d in
the
orde
r the
app
licat
ion
is re
ceiv
ed. (
Prim
ary
Key
)nv
arch
ar(3
0)ca
n no
t be
null
date
App
lTh
e da
te th
e ap
plic
atio
n w
as s
ubm
itted
.da
tetim
ere
ques
tSta
rtD
ate
The
date
the
stud
ent w
ould
like
to b
egin
wor
king
date
time
requ
estS
alar
yPer
Hr
The
hour
ly p
ay th
e st
uden
t wou
ld li
ke to
rece
ive
mon
eyre
ques
tWor
kTyp
eTh
e ty
pe o
f wor
k th
e st
uden
t wou
ld li
ke to
do
nvar
char
(50)
appl
Com
men
tA
dditi
onal
com
men
ts o
n th
e ap
plic
atio
nnv
arch
ar(2
00)
Com
pany
com
pany
No
Uni
quel
y id
entif
ies
a co
mpa
ny (P
rimar
y K
ey)
nvar
char
(30)
can
not b
e nu
llA
ssig
ned
in th
e or
der t
he c
ompa
ny
cont
acts
the
CIS
dep
artm
ent.
com
pany
Nam
eTh
e na
me
of th
e co
mpa
nynv
arch
ar(3
0)lin
eOfB
usin
ess
The
com
pany
's m
ain
line
of b
usin
ess
nvar
char
(30)
The
com
pany
's m
ain
line
of
busi
ness
as
is g
ener
ally
un
ders
tood
or a
s pr
ovid
ed b
y th
e co
mpa
ny c
onta
ct.
com
pany
PriC
onta
ctTh
e pr
imar
y co
ntac
t per
son
of th
e co
mpa
nynv
arch
ar(3
0)Th
ere
can
only
be
one
prim
ary
cont
act f
or e
ach
orga
nzia
tion.
com
pany
Wor
kPho
neTh
e w
ork
phon
e nu
mbe
r of t
he c
ompa
ny's
prim
ary
cont
act p
erso
nin
t(10)
com
pany
Mob
ilePh
one
The
mob
ile p
hone
num
ber o
f the
com
pany
's p
rimar
y co
ntac
t per
son
int(1
0)co
mpa
nyFa
xTh
e fa
x nu
mbe
r of t
he c
ompa
ny's
prim
ary
cont
act p
erso
nin
t(10)
prim
aryC
ompa
nyEm
ail
The
prim
ary
emai
l add
ress
of t
he c
ompa
ny's
prim
ary
cont
act p
erso
nnv
arch
ar(3
0)se
cond
aryC
ompa
nyEm
ail
The
seco
ndar
y em
ail a
ddre
ss o
f the
com
pany
's p
rimar
y co
ntac
t per
son
nvar
char
(30)
Coo
rdin
ator
staf
fNo
Uni
quel
y id
entif
ies
a m
embe
r of s
taff
(Prim
ary
Key
)in
tca
n no
t be
null
staf
fFN
ame
Firs
t nam
e of
the
coor
dina
tor
nvar
char
(50)
staf
fLN
ame
Last
nam
e of
the
coor
dina
tor
nvar
char
(50)
staf
fDat
eOfS
ervi
ceTh
e le
ngth
of t
ime
the
coor
dina
tor h
as b
een
in th
is p
ositi
on in
day
s.in
t
staf
fSta
rtD
ate
Coo
rdin
ator
sta
rting
wor
k da
teda
tetim
e
staf
fEnd
Dat
eC
oord
inat
or e
ndin
g w
ork
date
date
time
prim
aryS
taffE
mai
lC
oord
inat
or's
prim
ary
emai
l add
ress
nvar
char
(50)
seco
ndar
ySta
ffEm
ail
Coo
rdin
ator
's s
econ
dary
em
ail a
ddre
ssnv
arch
ar(5
0)st
affA
ddre
ssC
oord
inat
or's
add
ress
nvar
char
(50)
staf
fWor
kPho
neC
oord
inat
or's
wor
k ph
one
num
ber
nvar
char
(20)
staf
fCel
lPho
neC
oord
inat
or's
cel
l pho
ne n
umbe
rnv
arch
ar(2
0)st
affF
axPh
one
Coo
rdin
ator
's fa
x nu
mbe
rnv
arch
ar(2
0)Ev
alua
tionI
tem
eval
Item
No
Uni
quel
y id
entif
ies
the
eval
uatio
n ite
m (P
rimar
y K
ey)
nvar
char
(10)
can
not b
e nu
llev
alTy
peId
entif
ies
the
type
of e
valu
atio
n ite
mnv
arch
ar (5
0)ev
alD
escr
iptio
nA
desc
riptio
n of
the
eval
uatio
n ite
mnv
arch
ar (5
0)
Eval
uatio
nRes
ult
jobN
oU
niqu
ely
iden
tifie
s th
e jo
b (P
rimar
y K
ey)
nvar
char
(10)
can
not b
e nu
ll
An
inte
rnsh
ip c
an n
ot e
xist
with
out
the
exis
tenc
e of
a jo
b nu
mbe
r. O
ne
job
can
have
mul
tiple
set
s of
in
tern
ship
s bu
t onl
y on
e in
tern
ship
ca
n ha
ve o
ne jo
b.in
tern
Sem
este
rS
emes
ter t
he s
tude
nt h
olds
inte
rnsh
ip (P
rimar
y K
ey)
nvar
char
(10)
can
not b
e nu
llev
alD
ate
The
date
the
eval
uatio
n w
as re
ceiv
ed (P
rimar
y K
ey)
date
time
can
not b
e nu
llev
alR
esul
tNo
The
resu
lt of
the
eval
uatio
n (P
rimar
y K
ey)
int
can
not b
e nu
llev
alSc
ore
The
scor
e re
ceiv
ed o
n th
e ev
alua
tion
int
eval
Text
Add
ition
al c
omm
ents
on
the
eval
uatio
nnv
arch
ar(2
00)
Facu
ltySp
onso
rfa
culty
IDU
niqu
ely
iden
tifie
s th
e fa
culty
mem
ber (
Prim
ary
Key
)nv
arch
ar(1
0)ca
n no
t be
null
Stro
ng e
ntity
that
can
sta
nd o
n its
ow
n.
facu
ltyFN
ame
Firs
t nam
e of
facu
lty m
embe
rnv
arch
ar (5
0)
facu
ltyLN
ame
Last
nam
e of
facu
lty m
embe
rnv
arch
ar (5
0)fa
culty
Wor
kPho
neFa
culty
's w
ork
num
ber
nvar
char
(20)
facu
ltyC
ellP
hone
Facu
lty's
cel
l num
ber
nvar
char
(20)
facu
ltyFa
xPho
neFa
culty
's fa
x nu
mbe
rnv
arch
ar(2
0)pr
imar
yFac
ulty
Emai
lP
rimar
y fa
culty
mem
ber's
em
ail a
ddre
ssnv
arch
ar(5
0)se
cond
aryF
acul
tyEm
ail
Sec
onda
ry fa
culty
mem
ber's
em
ail a
ddre
ssnv
arch
ar (5
0)
Dat
a D
omai
n
Entit
y N
ame
Attr
ibut
esD
escr
iptio
nD
ata
Type
& L
engt
h C
onst
rain
tB
usin
ess
Rul
e
Inte
rnsh
ipjo
bNo
Uni
quel
y id
entif
ies
the
job
(Prim
ary
Key
)nv
arch
ar(1
0)ca
n no
t be
null
An
inte
rnsh
ip c
an n
ot e
xist
with
out
the
exis
tenc
e of
a jo
b nu
mbe
r. O
ne
job
can
have
mul
tiple
set
s of
in
tern
ship
s bu
t onl
y on
e in
tern
ship
ca
n ha
ve o
ne jo
b.in
tern
Sem
este
rS
emes
ter t
he s
tude
nt h
olds
inte
rnsh
ip (P
rimar
y K
ey)
nvar
char
(10)
can
not b
e nu
llco
urse
No
The
cour
se n
umbe
r the
stu
dent
is e
nrol
led
in fo
r the
inte
rnsh
ipnv
arch
ar(7
)du
ratio
nOfIn
tern
ship
The
leng
th o
f tim
e th
e st
uden
t is
on th
e in
tern
ship
in d
ays.
int
inte
rnSt
artD
ate
Sta
rting
dat
eda
tetim
eca
n no
t be
null
inte
rnEn
dDat
eE
ndin
g da
teda
tetim
ein
tern
JobO
ffer
Whe
ther
the
inte
rn w
as o
ffere
d a
job
(Y o
r N)
bit
com
men
tIn
tern
ship
com
men
tsnv
arch
ar (2
00)
Inte
rnEv
alua
tion
jobN
oU
niqu
ely
iden
tifie
s a
job
(Prim
ary
Key
)in
tca
n no
t be
null
inte
rnSe
mes
ter
Sem
este
r the
stu
dent
hol
ds in
tern
ship
(Prim
ary
Key
)nv
arch
ar (1
0)ca
n no
t be
null
eval
Dat
eTh
e da
te o
f the
eva
luat
ion
(Prim
ary
Key
)da
tetim
eca
n no
t be
null
eval
uato
rTh
e na
me
of th
e pe
rson
who
com
plet
ed th
e ev
alua
tion
(Prim
ary
Key
)nv
arch
ar(3
0)ca
n no
t be
null
eval
uato
rOrg
The
orga
niza
tion
that
the
pers
on fi
lling
out
the
eval
uatio
n be
long
s to
nvar
char
(30)
Inte
rnsh
ipSt
atus
jobN
oU
niqu
ely
iden
tifie
s a
job
(Prim
ary
Key
)in
tca
n no
t be
null
One
inte
rnsh
ip o
nly
exis
ts o
ne
sem
este
r, an
d ca
n ha
ve d
iffer
ent
stat
us in
the
diffe
rent
tim
e pe
riod.
inte
rnSt
atD
ate
The
date
and
tim
e th
e in
tern
ship
sta
tus
assi
gned
(Prim
ary
Key
)da
tetim
eca
n no
t be
null
sem
este
r, an
d ca
n ha
ve d
iffer
ent
inte
rnSe
mes
ter
The
sem
este
r the
stu
dent
hol
ds th
e in
tern
ship
(Prim
ary
Key
)nv
arch
ar(1
0)ca
n no
t be
null
stat
us in
the
diffe
rent
tim
e pe
riod.
inte
rnSt
atus
Sta
tus
of th
e in
tern
ship
app
licat
ion:
Clo
sed,
Ope
n, o
r Pen
ding
bit
Job
jobN
oU
niqu
ely
iden
tifie
s a
job
(Prim
ary
Key
)in
tca
n no
t be
null
Eve
ry jo
b m
ust b
elon
g to
an
empl
oyer
.jo
bTitl
eJo
b tit
le a
s de
term
ined
by
the
empl
oyer
nvar
char
(50)
jobD
esc
Job
desc
riptio
n as
def
ined
by
the
empl
oyer
nvar
char
(300
)jo
bWee
ksD
urat
ion
Num
ber o
f wee
ks th
e em
ploy
er d
esire
s to
hav
e so
meo
ne w
ork
int
A jo
b us
ually
has
a s
peci
fied
leng
th
expr
esse
d in
wee
ks.
jobD
esire
dSta
rtD
ate
The
date
the
empl
oyer
des
ires
to h
ave
som
eone
sta
rt w
ork
date
time
jobP
ayR
ateP
erH
our
Sta
rting
bas
e ho
urly
pay
rate
for t
he jo
bm
oney
JobC
lass
jobC
lass
No
Uni
quel
y id
entif
ies
a jo
b cl
ass
(Prim
ary
Key
)in
tca
n no
t be
null
Cla
ssifi
catio
n is
the
com
mon
in
dust
ry n
ame
for a
tech
nolo
gy o
r to
ol.
jobC
lass
Des
crib
es th
e ge
nera
l job
cla
ssifi
catio
n, i.
e. p
rogr
amm
ing,
net
wor
king
, da
taba
se a
dmin
, pro
ject
mgt
, PC
sup
port
nvar
char
(50)
Cla
ss is
a s
hort
desc
riptio
n as
de
fined
by
the
coor
dina
tor.
jobC
lass
Des
cD
etai
ls th
e sp
ecifi
c jo
b de
scrip
tion
nvar
char
(300
)C
lass
des
crip
tion
is a
det
aile
d ve
rsio
n of
a c
lass
as
defin
ed b
y th
e co
ordi
nato
r.Jo
bQua
lific
atio
njo
bNo
Uni
quel
y id
entif
ies
a jo
b (P
rimar
y K
ey)
int
can
not b
e nu
llQ
ualif
icat
ions
are
iden
tifie
d jo
b re
late
d sk
ills.
jobQ
ualN
oU
niqu
ely
iden
tifie
s a
job
qual
ifica
tion
(Prim
ary
Key
)in
tca
n no
t be
null
Rec
orde
d in
the
orde
r giv
en.
jobQ
ualS
kill
Des
crib
es th
e ge
nera
l job
ski
ll, i.
e. J
ava,
Cis
co, O
racl
e, M
S O
ffice
, typ
ing,
pu
blic
spe
akin
gnv
arch
ar(2
00)
Qua
lific
atio
n sk
ills
and
deta
iled
desc
riptio
ns a
re re
cord
ed a
s pr
ovid
ed b
y th
e em
ploy
er.
jobQ
ualD
esc
Des
crib
es th
e sp
ecifi
c jo
b qu
alifi
catio
nnv
arch
ar(5
0)P
rovi
ded
by th
e em
ploy
er.
JobS
tatu
sjo
bNo
Uni
quel
y id
entif
ies
a jo
b (P
rimar
y K
ey)
int
can
not b
e nu
ll
One
job
can
have
sev
eral
in
tern
ship
s, a
nd o
ne jo
b ca
n la
st
mor
e th
an o
ne s
emes
ter.
Las
t se
mes
ter o
f the
job
is th
e se
mes
ter
of re
cord
.
jobS
tatD
ate
the
date
and
tim
e th
e jo
b st
atus
ass
igne
d (P
rimar
y K
ey)
date
time
can
not b
e nu
ll
Inte
rnsh
ips,
and
one
job
can
last
m
ore
than
one
sem
este
r. T
he la
st
sem
este
r of t
he jo
b is
the
sem
este
r of
reco
rd.
jobS
tatu
sS
tatu
s of
the
job:
Clo
sed,
Ope
n, o
r Pen
ding
bit
Org
aniz
atio
nor
gNo
Uni
quel
y id
entif
ies
an o
rgan
izat
ion
(Prim
ary
Key
)in
tca
n no
t be
null
Org
aniz
atio
ns a
re d
epar
tmen
ts,
busi
ness
uni
ts, d
ivis
ions
, etc
.or
gNam
eTh
e tit
le o
f the
org
aniz
atio
n as
giv
en b
y th
e co
mpa
nynv
arch
ar(3
0)
Dat
a D
omai
n
Entit
y N
ame
Attr
ibut
esD
escr
iptio
nD
ata
Type
& L
engt
h C
onst
rain
tB
usin
ess
Rul
eor
gSup
vCon
tact
The
prim
ary
cont
act p
erso
n/su
perv
isor
of t
he o
rgan
izat
ion
nvar
char
(30)
Ther
e ca
n on
ly b
e on
e pr
imar
y co
ntac
t/sup
ervi
sor f
or e
ach
orga
nzia
tion.
orgW
orkP
hone
The
wor
k ph
one
num
ber o
f the
org
aniz
atio
n's
prim
ary
cont
act p
erso
nin
t(10)
orgM
obile
Phon
eTh
e m
obile
pho
ne n
umbe
r of t
he o
rgan
izat
ion'
s pr
imar
y co
ntac
t per
son
int(1
0)or
gFax
The
fax
num
ber o
f the
org
aniz
atio
n's
prim
ary
cont
act p
erso
nin
t(10)
prim
aryO
rgEm
ail
The
prim
ary
emai
l add
ress
of t
he o
rgan
izat
ion'
s pr
imar
y co
ntac
t per
son
nvar
char
(30)
seco
ndar
yOrg
Emai
lTh
e se
cond
ary
emai
ll ad
dres
s of
the
orga
niza
tion'
s pr
imar
y co
ntac
t per
son
nvar
char
(30)
orgC
omm
ent
Com
men
ts a
bout
the
orga
niza
tion
nvar
char
(200
)St
uden
tst
uden
tID
Uni
quel
y id
entif
ies
the
stud
ent (
Prim
ary
Key
)nv
arch
ar(1
0)ca
n no
t be
null
Stro
ng e
ntity
that
can
sta
ndst
uden
tFN
ame
Firs
t nam
e of
stu
dent
nvar
char
(50)
on it
s ow
n.st
uden
tLN
ame
Last
nam
e of
stu
dent
nvar
char
(50)
prog
ram
OfS
tudy
Pro
gram
of s
tudy
(i.e
. MB
A/C
IS)
nvar
char
(50)
com
plet
ePro
gram
min
gTra
ckFi
nish
ed p
rogr
amm
ing
track
(Y o
r N)
bit
stud
entG
PAS
tude
nt's
GPA
float
expe
cted
Gra
duat
ionD
ate
Gra
duat
ion
date
date
time
stud
entA
ddre
ssS
tude
nt a
dddr
ess
nvar
char
(100
)st
uden
tHom
ePho
neS
tude
nt's
hom
e nu
mbe
rnv
arch
ar(2
0)st
uden
tWor
kPho
neS
tude
nt's
wor
k nu
mbe
rnv
arch
ar(2
0)st
uden
tCel
lPho
neS
tude
nt's
cel
l num
ber
nvar
char
(20)
stud
entF
axPh
one
Stu
dent
's fa
x nu
mbe
rnv
arch
ar(2
0)pr
imar
yStu
dent
Emai
lP
rimar
y st
uden
t em
ail a
ddre
ssnv
arch
ar(5
0)se
cond
aryS
tude
ntEm
ail
Sec
onda
ry s
tude
nt e
mai
l add
ress
nvar
char
(50)
Relationship Domain
Entity Name Multiplicity Relationship Multiplicity Entity Name Business RulesCompany 1 includes 0..* Organization A company may or may not have
organizations or groups within it (such as departments, divisions, etc.) when it enters into a relationship with CIS, and an organization must belong to a company.
Coordinator 1 establishes 0..* Job Status A coordinator may or may not establish a job status, and a job status belongs to a coordinator.
1 assigns 0..* Internship Status A coordinator may or may not assign an internship status, and an internship status belongs to a coordinator.
Faculty Sponsor 1 responsible for 0..* Internship An internship when it is being initiated may not have a faculty sponsor. However, once initiated a faculty sponsor must be assigned to be responsible for the internship.
Internship 1 receives 0..* Intern Evaluation An internship may or may not receive an intern evaluation since there are no governing policies at this time; however, an evaluation must belong to an intership.
1 is assigned 0..* Internship Status An internship may or may not be assigned a status, and an internship status belongs to an internship.
1 applies for 0..* Application An internship may or maynot have any students submit an application for it.
Job 1 requires 1..* Job Qualification A job must have at least one qualification, and a qualification belongs to only one job.
1 registers 1..* Job Status A job must have at least one status, and a job status belongs to only one job.
1 needs 0..* Internship An internship must belong to a job opportunity from a company, but a job may not have any internships until it is filled.
Job Class 1 identifies 0..* Job A job belongs to only one job class which organizes jobs by kind or class.
Organization 1 has 0..* Job An organization or group within a company may or may not have job openings for internships, and a job must belong to an organization.
Student 1 works on 0..* Internship A student may or may not work on an internship, and an internship belongs to one and only one student.
21
Data Dictionary Application (studentID, applNo, jobNo, internSemester, facultyID, dateAppl, requestStartDate, requestSalaryPerHr, requestWorkType, applComment) Primary Key studentID, applNo Foreign Key studentID reference Student(studentID) Foreign Key jobNo reference Job(jobNo) Foreign Key internSemester reference Internship(internSemester) Foreign Key facultyID reference FacultySponsor(facultyID)
Attributes Data Type & Length studentID nvarchar(10) applNo nvarchar(30) jobNo nvarchar(10) internSemester nvarchar(10) facultyID nvarchar(10) dateAppl datetime requestStartDate datetime requestSalaryPerHr money requestWorkType nvarchar(50) applComment nvarchar(200)
Company (companyNo, companyName, lineOfBusiness, companyPriContact, companyWorkPhone, companyMobilePhone, companyFax, primaryCompanyEmail, secondaryCompanyEmail) Primary Key companyNo Foreign Key None
Attributes Data Type & Length companyNo nvarchar(30) companyName nvarchar(30) lineOfBusiness nvarchar(30) companyPriContact nvarchar(30) companyWorkPhone int(10) companyMobilePhone int(10) companyFax int(10) primaryCompanyEmail nvarchar(30) secondaryCompanyEmail nvarchar(30)
22
Coordinator (staffNo, staffFName, staffLName, staffStartDate, staffEndDate, primaryStaffEmail, secondaryStaffEmail, staffAddress, staffWorkPhone, staffCellPhone, staffFaxPhone) Primary Key staffNo Derived staffDateOfService (staffEndDate – staffStartDate) Attributes Data Type & Length staffNo int staffFName nvarchar(50) staffLName nvarchar(50) staffDateOfService staffStartDate datetime staffEndDate datetime primaryStaffEmail nvarchar(50) secondaryStaffEmail nvarchar(50) staffAddress nvarchar(50) staffWorkPhone nvarchar(20) staffCellPhone nvarchar(20) staffFaxPhone nvarchar(20)
EvaluationItem (evalItemNo, evalType, evalDescription) Primary Key evalItemNo Foreign Key none Attributes Data Type & Length evalItemNo int evalType nvarchar(50) evalDescription nvarchar(300)
EvaluationResult (jobNo, internSemester, evalDate, evalResultNo, evalItemNo, evalScore, evalText) Primary Key jobNo, internSemester, evalDate, evalResultNo Foreign Key jobNo reference Job(jobNo) Foreign Key internSemester reference Internship(internSemester) Foreign Key evalDate reference InternEvaluation(evalDate) Foreign Key evalItemNo reference EvaluationItem(evalItemNo) Attributes Data Type & Length jobNo int internSemester nvarchar (20) evalDate datetime evalResultNo int evalItemNo int evalScore int evalText nvarchar (300)
FacultySponsor (facultyID, facultyFname, facultyLname, facultyWorkPhone, facultyCellPhone, facultyFaxPhone, primaryFacultyEmail, secondaryFacultyEmail) Primary Key facultyID Attributes Data Type & Length
23
facultyID int facultyFName nvarchar(50) facultyLName nvarchar(50) facultyWorkPhone nvarchar(20) facultyCellPhone nvarchar(20) facultyFaxPhone nvarchar(20) primaryFacultyEmail nvarchar(50) secondaryFacultyEmail nvarchar(50)
Internship (jobNo, internSemester, facultyID, studentID, courseNo, durationofInternship, internStartDate, internEndDate, internJobOffer, comment) Primary Key jobNo, internSemester Foreign Key jobNo reference Job(jobNo) Foreign Key facultyID reference Faculty(facultyNo) Foreign Key studentID reference Student(studentID) Derived durationOfInternship (internEndDate – internStartDate) Attributes Data Type & Length jobNo int internSemester nvarchar (20) facultyID int studentID int courseNo int durationofInternship internStartDate datetime inernEndDate datetime internJobOffer bit comment nvarchar(300)
24
InternEvaluation (jobNo, internSemester, evalDate, evaluator, evaluatorOrg, studentID, OrgNo, facultyID) Primary Key jobNo, internSemester, evalDate Foreign Key jobNo reference Job(jobNo) Foreign Key internSemester reference Internshp(internSemester) Foreign Key studentID reference Student(studentID) Foreign Key orgNo reference Organization(orgNo) Foreign Key facultyID reference FacultySponsor(facultyID) Attributes Data Type & Length jobNo int internSemester nvarchar(20) evalDate datetime evaluator nvarchar (50) evaluatorOrg int studentID nvarchar(10) orgNo int facultyID nvarchar(10)
InternshipStatus (jobNo, internStatDate, internSemester, staffNo, internStatus) Primary Key jobNo, internStatDate, internSemester Foreign Key jobNo reference Job(jobNo) Foreign Key internSemester reference Internship(internSemester) Foreign Key staffNo reference Coordinator(staffNo) Attributes Data Type & Length jobNo int internStatDate datetime internSemester nvarchar(10) staffNo int internStatus bit
25
Job (jobNo, orgNo, jobTitle, jobDesc, jobWeeksDuration, jobDesiredStartDate, jobPayRatePerHour, jobClassNo) Primary Key jobNo Foreign Key orgNo reference Organization(orgNo) Foreign Key jobClassNo reference JobClass(jobClassNo) Attributes Data Type & Length jobNo int orgNo int jobTitle nvarchar(50) jobDesc nvarchar(300) jobWeeksDuration int jobDesiredStartDate datetime jobPayRatePerHour money jobClassNo int
JobClass (jobClassNo, jobNo, jobClass, jobClassDesc) Primary Key jobClassNo Foreign Key none Attributes Data Type & Length jobClassNo int jobClass nvarchar(50) jobClassDesc nvarchar(300)
JobStatus (jobNo, jobStatDate, staffNo, jobStatus) Primary Key jobNo, jobStatDate Foreign Key staffNo reference Coordinator(staffNo) Foreign Key jobNo reference Job(jobNo) Attributes Data Type & Length jobNo int jobStatDate datetime staffNo datetime jobStatus bit
JobQualification (jobNo, jobQualNo, jobQualSkill, jobQualDesc) Primary Key jobNo, jobQualNo Foreign Key jobNo reference Job(jobNo) Attributes Data Type & Length jobNo int jobQualNo int jobQualSkill nvarchar(50) jobQualDesc nvarchar(300)
Organization (orgNo, companyNo, orgName, orgSupvContact, orgWorkPhone, orgMobilePhone, orgFax, primaryOrgEmail, secondaryOrgEmail)
26
Primary Key orgNo Foreign Key companyNo reference Company(companyNo) Attributes Data Type & Length orgNo int companyNo int orgName nvarchar(50) orgSupvContact nvarchar(20) orgWorkPhone nvarchar(20) orgMobilePhone nvarchar(20) orgFax nvarchar(20) primaryOrgEmail nvarchar(50) secondaryOrgEmail nvarchar(50) orgComment nvarchar(300)
Student (studentID, studentFName, studentLName, programOfStudy, completeProgrammingTrack, studentGPA, expectedGraduationDate, studentAddress, studentHomePhone, studentWorkPhone, studentCellPhone, studentFaxPhone, primaryStudentEmail, secondaryStudentEmail) Primary Key studentID Attributes Data Type & Length studentID int studentFName nvarchar(50) studentLName nvarchar(50) programOfStudy nvarchar(50) completeProgrammingTrack bit studentGPA float expectedGraduationDate datetime studentAddress nvarchar(100) studentHomePhone nvarchar(20) studentWorkPhone nvarchar(20) studentCellPhone nvarchar(20) studentFaxPhone nvarchar(20) primaryStudentEmail nvarchar(50) secondaryStudentEmail nvarchar(50)
27
System Prototype QUICK REFERNECE GUIDE The following steps are meant as a quick guide to help use the Internship Database. This is not a comprehensive reference, but it provides the basic steps required to setup and enter data and to view the various reports. 1. SETUP
1.1. Startup MS Access and select the Internship Database and open it.
1.2. For initial usage
1.2.1. At the main menu select Job Class and enter the determined
classes of jobs for internships.
1.2.2. At the main menu select Evaluation Item and enter the determined
items for evaluating the internship.
1.2.3. Once these tables are populated, the database is ready for initial
entry of data.
2. Initial Data Entry
2.1. In order to insert data about internships and jobs, some primary data
tables must be entered beforehand. These primary data tables may be
entered in any order, but they must be present before entering related
data tables. For example, a student must be entered before an
application is inserted, and a company with its organization must be
entered before inserting a job.
2.2. At the main menu select Company and Organization and enter the
required data in the provided form.
2.3. At the main menu select Student and enter the required data in the
provided form.
2.4. At the main menu select Faculty and enter the required data in the
provided form.
2.5. At the main menu select Coordinator and enter the required data in the
provided form.
28
2.6. Once these tables are populated, the database is ready for the
insertion of related data such as jobs, internships and intern evaluations.
3. Adding a New Job
3.1. If the Company and Organization are not already in the database, add
them from the main menu.
3.2. At the main menu select Job and enter the job description and its
associated qualifications and job status.
4. Adding a New Internship
4.1. If the Company and Organization are not already in the database, add
them from the main menu.
4.2. If the Student is not already in the database, add him/her from the
main menu.
4.3. Optionally, if known at this time, the Faculty Sponsor may be added to
the database from the main menu.
4.4. At the main menu select Internship and complete the provided form for
the internship and its status.
5. Adding an Intern Evaluation
5.1. The required data tables must be completed for an Internship before
an Intern Evaluation can be inserted. These include the Company and
Organization, the Job, the Faculty Sponsor, and the Student.
5.2. At the main menu select Intern Evaluation and fill out the provided form
for the Intern Evaluation.
6. Standard Reports
6.1. At the main menu, buttons are provided for the primary reports and
may be viewed by selecting the appropriate button for the report.
6.2. Additional queries may be created using SQL as needed.
29
Forms
30
31
32
33
34
Reports 1. Active Internships SELECT S.studentID, s.studentFName, s.studentLName FROM Internship I, Student S, InternshipStatus T WHERE I.studentID=S.studentID AND I.jobNo=T.jobNo AND I.internSemester=T.internSemester AND internStatus='true' GROUP BY S.studentID, s.studentFName, s.studentLName Order By s.studentFName;
2.Internship Master List SELECT j.jobTitle, n.internStatus, i.internSemester, O.jobStatus FROM job j, Internship I, JobStatus O, InternshipStatus N WHERE J.jobNo=I.jobNo AND J.jobNo=o.jobNo AND I.jobNo=n.jobNo ORDER BY n.internStatus, I.internSemester
35
3. Job Master List SELECT j.jobdesiredStartDate, c.companyName, R.orgName, j.jobTitle, O.jobStatus FROM job j, JobStatus O, Company c, Organization R WHERE c.companyNo=R.companyNo AND R.orgNo=j.orgNo AND J.jobNo=o.jobNo ORDER BY j.jobdesiredStartDate ,o.jobStatus
36
4 Job Qualification List SELECT c.companyName, o.orgName, j.jobTitle, Q.jobQualDesc, Q.jobQualSkill, S.jobStatus FROM company c, organization o, job j, jobStatus S, jobQualification Q WHERE c.companyNo=o.companyNo AND o.orgNo=j.orgNo AND j.jobNo=Q.jobNo AND j.jobNo=S.jobNo AND s.jobStatus='true' GROUP BY c.companyName, o.orgName, j.jobTitle, Q.jobQualDesc, Q.jobQualSkill, S.jobStatus ORDER BY c.companyName
5.Open Job List By Date SELECT j.jobdesiredStartDate, c.companyName, R.orgName, j.jobTitle, O.jobStatus FROM job j, JobStatus O, Company c, Organization R WHERE c.companyNo=R.companyNo AND R.orgNo=j.orgNo AND J.jobNo=o.jobNo AND o.jobStatus='true' ORDER BY j.jobdesiredStartDate ,o.jobStatus
37
6.Companies Feedback SELECT c.companyName, o.orgName, j.jobTitle, i.internSemester,e.evalScore, e.evalText FROM company c, organization o, job j, internship I, evaluationResult e WHERE o.orgNo=j.orgNo AND j.jobNo=I.jobNo AND I.internSemester=e.internsemester AND c.companyNo=o.companyNo;
7. Faculty Master List SELECT F.facultyFName, F.facultyLName, s.studentFName, s.studentLName,j.jobTitle, I.internSemester FROM FacultySponsor F, job j, Internship I,student s WHERE F.facultyID=I.facultyID AND I.jobNo=j.jobNo GROUP BY F.facultyFName, F.facultyLName, s.studentFName, s.studentLName,j.jobTitle, I.internSemester *Note: this statement only list the faculty sponsors with internship.
38
8. Internships By Company SELECT c.companyName,o.orgName, j.jobtitle, i.internSemester, s.studentLName, s.studentFName, i.internStartDate, i.internEndDate FROM company c, organization o, job j, internship i, student s WHERE c.companyNo=o.companyNo AND o.orgNo=j.orgNo AND j.jobNo=i.jobNo AND s.studentID=i.studentID GROUP BY c.companyName,o.orgName, j.jobtitle, i.internSemester, s.studentLName, s.studentFName, i.internStartDate, i.internEndDate ORDER BY i.internstartDate DESC;
39
Business Domain Assumptions 1. A job may not have multiple openings within the same time period. A job with
multiple openings is considered by both employers and CIS as two individual job
positions, and they are tracked accordingly. No single job may have two open
positions within the same time period.
2. An internship application is not a single entity in the model, and the application
process is not part of the database design. The application is a form that is
composed of attributes from several entities, and as such it is not modeled as a
separate entity. When a student applies, the appropriate data is entered into the
internship entity and its related entities such as internship status, faculty, student,
and coordinator.
3. An organization is a group of employees within a company who have a job opening.
The organization entity is a generic group and may be a department, a division, or
any group within the company. If a company is so small that it has no subordinate
organizations (a rare occurrence), then the company becomes the organization. The
organization entity denotes where within the company the job occurs and the primary
contact for the job.
4. The evaluation process is not formalized today. The evaluator is the employing
manager for the internship. The organization entity contains data on the supervisor.
The intern evaluation entity contains an attribute to indicate to which organization,
employer or CIS, the evaluator belongs. The evaluator may be either the employer
responsible for the work or the faculty sponsor for the internship. Multiple
evaluations may be submitted for a single instance of an internship. Each instance
includes the evaluator making the evaluation. At this time no standard evaluation
form is used; however, a form is being developed for this purpose with ten evaluation
criteria and scores are recorded in the evaluation entity for that form.
5. Each job is classified by kind in order to group them for access and reporting. By
definition no job may occur within more than one job class. The job class entity is
used to organize the jobs by kind in a simple taxonomy so that jobs may be
accessed in groups by class for student searching and for analysis.
6. Student documents are not maintained in the database nor are they archived at this
time. Student internship documents such as journals are not within the scope of this
40
database. These are submitted to the faculty sponsor for review and are not
archived at this time.
7. The internship entity contains an attribute to denote the course number, and
additional data about the student’s performance, grades, and coursework is kept in
the Banner System. The internship courses are managed separately within the
Banner system. Data about the courses is outside the scope of this database and
would involve privacy issues that would impair the use of this database by
coordinators, students, employers, and faculty.
Comments Items Not Implemented During the Conceptual Design review with the users, the standard reports were revisited
and by agreement modified. The reason for this change was that better understanding
of the database and its purpose was evolving as a result of the design process. Based
upon that new understanding the standard reports needed to be adjusted. The original
requirements included the following items that were revised during the review:
• Listing of all students with a particular status (active, inactive)
• Interview results
• Students with GPAs in a certain range that have not been placed
• Students who have not completed the course requirements (journal, paper)
• Students with GPAs in a certain range
• Students with missing acceptance requirements (transcripts, resume, etc.)
The revised standard output requirements are:
• Listing of all students currently on internships through the CIS department
• Listing of all internships and jobs by status by term
• All companies that have requested internships
• All open jobs and their qualifications
• Unfilled requests for interns by date of request
• Feedback from companies on interns
• Faculty sponsors with no assigned students
• All faculty sponsors and internships by term
• Employer details and history
• Date of most recent internship at a particular company
• Number and history of internships at a particular company
41
Experiences
What We Liked
• Having a real-world client
• Building something that will help the CIS department at GSU
What We Disliked
• Having to work around each other’s schedules in order to meet
• Having to change our design to meet the user’s requirements
• Building the user interface
What We Learned
Over the course of this project, we learned that the client is always right…even when
you disagree. Ultimately, we the designers are not going to be the users of this system.
Although it may be easier to design a system one way, the user’s wants and needs
required us to do things that were more difficult. We also learned that modifications are
a necessity. As we went through the process, we had to make many changes to our
original design. Although it slows the process, it makes the end result better. We
learned that it is best to have a clear understanding of the current process before you
begin. It is easier for everyone to agree on the approach when you all understand the
process the same way.
Team Meeting Minutes January 9, 2007
1. Team member roles were assigned with the following results:
• Team Leader – Yan Wang • Documenter – Shanell Overton • TechGuru – John Hupp • Implementation Leader – Archie Out • Client PoC – John Hupp • Instructor PoC – Steve Bean
42
2. A weekly group meeting time of 7:00 PM on Mondays was agreed upon. The meeting location will be Panera’s in the Perimeter area. John will provide directions to the location.
3. Group member email addresses were shared:
• Yan Wang – [email protected] • Shanell Overton – [email protected] • John Hupp – [email protected] • Archie Otu – [email protected] • Steve Bean – [email protected]
January 23, 2007 4. Due to scheduling conflicts, the team meetings have been moved to Sundays at
2:00pm at the Lenox Mall Food Court. 5. In preparation for Milestone 2, it was decided that the questions be split amongst
the team members:
• Questions 1,2 &3 – John • Question 4 – Yan • Question 5 – Shanell • Question 6 – Steve • Final Compilation – Archie
6. John recommended that everyone review Section 10.4 of the textbook (pp. 321-
340) as a guide for completing the questions for Milestone 2. 7. It was decided that everyone would email their responses to the assigned
questions by Saturday, January 27, 2007 at 10:00 pm so that everyone will have a chance to review the responses before we meet on Sunday.
January 28, 2007
8. Drafts of Milestone 2 were reviewed and discussed. It was decided to follow the
examples given in the Dream Home Case Study for the majority of the sections. John recommended and the team members agreed that short paragraphs should be added to each section.
9. Final sections are due via email by Monday at 11:59 PM.
February 6, 2007
10. It was decided that John would do the ER Diagram for Milestone 3. The Domain
for the entity types will be divided among the remaining group members.
43
11. Meetings have been switched to Thursdays at 7:15 in Aderhold 1st floor.
February 8, 2007
12. A rough ER Diagram was sketched and discussed among all team members. 13. The entity types were defined as:
• Student • Employer • Company • Job • Internship • Faculty Sponsor • Coordinator • Job Status • Internship Status • Job Class • Job Qualifications • Internship Evaluation
14. The domains were assigned as follows:
• Steve: Job, Job Qualifications, Job Class • Archie: Internship, Faculty Sponsor, Student • Shanell: Employer, Company, Internship Evaluation • Yan: Coordinator, Internship Status, Job Status
15. Steve’s Professor from another class has volunteered to assist in any way he
can. Steve will coordinate with him to find out his availability and the group will attempt to meet with him as soon as possible.
16. It was decided that all rough drafts should be emailed out by Thursday, February
15th for review. February 13, 2007
17. Due to the Milestone deadline being pushed back a week, the deadline for the
rough drafts is now Sunday, February 18th at 11:59 PM. 18. Yan cancelled the Thursday meeting so everyone will have time to study for the
Midterm.
February 25, 2007
19. Meeting was held at the Lenox Mall Food Court.
44
20. Discussion regarding entity names resulted in changes to some entities.
21. Discussion and ultimate resolution of attributes occurred.
22. Revisions of conceptual drafts are due by Monday, February 26, 2007 at
11:59PM.
23. John will update the ER diagram to reflect new attributes and entity names.
24. John requested that everyone send their revisions out at soon as possible to allow for the updates.
February 27, 2007
25. Group meeting will be held this Thursday, February 29, 2007 on the lower level
of the Aderhold Building. 26. Discussion will be about the next Milestone for the project..
February 29, 2007
27. Meeting was cancelled due to extreme weather. 28. Discussion will occur via email regarding Milestone 4.
March 6, 2007
29. No meeting due to Spring Break.
March 13, 2007
30. It was decided that John would do the ER Diagram and everyone would do the
logical model for their same entities. 31. Drafts are due by Saturday, March 17th at 11:59 PM. 32. Revisions for Milestone 3 are due Wednesday, March 14th by 11:59 PM.
March 20, 2007
33. It was decided that John would do the majority of the presentation for next week. 34. Shanell will put together the PowerPoint presentation and email to all for
updates/revisions.
45
35. John requested a plain white background and dark blue font for the presentation slides.
36. The group agreed upon 8 slides: cover, purpose, transactions, conceptual ER, Business Rules and assumptions, Logical ER, logical written schema, Q&A.
March 27, 2007
37. John will make the suggested changes to the conceptual and logical models. 38. Each member will write the new relations and also carry forward the attribute
types and lengths for their assigned entities. April 3, 2007
39. Each group member will build up the tables for their assigned entities and bring
them to the next meeting. 40. The next meeting is Monday, April 9, 2007 at 6:00 PM in the Lenox Mall Food
Court. April 9, 2007
41. The tables were discussed and changes were made. 42. The group is having difficulty figuring out how to move the information back and
forth between computers. 43. Steve built the MS SQL database and will email the latest database version and
send updates when there are significant changes. 44. The next group meeting is Friday, April 13, 2007 at 5:00 at the Lenox Food
Court. April 13, 2007
45. Archie sent over the dummy data. 46. All of the tables have been built. The group is having trouble getting the derived
attributes to populate correctly. 47. Steve built the MS Access forms to be used as the user interface. 48. Shanell will do all of the revisions to the previous submissions and handle some
of the written items. 49. All members are to send out what they have learned and what their most
memorable experience was from this project by Monday, April 16. 50. The next group meeting is Monday, April 16, 2007.
April 16, 2007
51. The group tested the database. 52. The dummy data was modified in order to produce better results.
46
53. Some standard reports were combined and others modified at the request of the user.
54. The database is fully operational. 55. Steve corrected attributes in two of the database tables to compute the derived
date values and added auto-numbering functions for the appropriate primary keys.
56. Steve or Yan will try to get it uploaded to the server tonight. 57. The presentation was divided up among the group members as follows:
• Yan – Introduction • John – Purpose, Conceptual and Logical Models • Steve and Shanell – Database Maintenance and Demonstration • Yan and Archie – Reports and Demonstration, Documentation • Steve – Security • Shanell - Summary
