0% found this document useful (0 votes)
69 views

Final Presentation 3

The document describes a database project for HSFL, an organization that aims to develop small spacecraft from Hawaii. The project involves developing a database system to: 1) Monitor available equipment; 2) Store employee and project information; 3) Enable HSFL to perform queries and create reports. The methodology uses Rapid Application Development with 7 steps: requirements analysis, conceptual design, DBMS selection, logical design, physical design, prototype, and evaluation. The logical design includes 4 entities and 3 relationships in 3rd normal form. The physical design involves query tuning, indexing, views, and storage level decisions.

Uploaded by

api-393028141
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
69 views

Final Presentation 3

The document describes a database project for HSFL, an organization that aims to develop small spacecraft from Hawaii. The project involves developing a database system to: 1) Monitor available equipment; 2) Store employee and project information; 3) Enable HSFL to perform queries and create reports. The methodology uses Rapid Application Development with 7 steps: requirements analysis, conceptual design, DBMS selection, logical design, physical design, prototype, and evaluation. The logical design includes 4 entities and 3 relationships in 3rd normal form. The physical design involves query tuning, indexing, views, and storage level decisions.

Uploaded by

api-393028141
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 76

1

HSFL
Database System Project
Query Queens +2
Tse Yu Chiu (Frank), Kaden Kawakami, Lauren Kirkwood,
Jacki Suminaga and Kara Tanaka
2

INTRODUCTION METHODOLOGY RESULTS

• •

• •

• •
3
4

HSFL aims to:


● Develop, launch, and operate small spacecraft from the Hawaiian Islands to accelerate the validation of new
space technologies

● Provide workforce training in all aspects of unmanned space missions

● Build synergistic collaborations among educational, governmental, and corporate institutions interested in
space exploration

● Engineering of microsatellites ● Workforce Development


● Management of equipment & employee information ● Creation of reports to lobby for project funding
5

THE PROBLEM:
Manual entry results in data that is: ○ Cannot perform ad hoc ○ Don’t know what equipment is
○ Improperly filed queries available to build satellites
○ Missing ○ Cannot create accurate ○ Wasted time
○ Redundant reports ○ Reduced funding for projects
6

To develop a database system that helps HSFL achieve its goals of


creating microsatellites to explore space and providing internships to students.

- Monitors available - Enable HSFL to perform - Spend more time creating


equipment ad hoc queries satellites
- Send reports to
- Stores employee and - Enable HSFL to create NASA/government to
project information personalized reports obtain more funds
7
7 Steps to Success

Rapid Application Development


The major benefit of the RAD methodology is that it is an iterative process. It provides the flexibility
to continually update and improve the requirements throughout the entire life of the project.

1. Requirement Analysis 4. Logical Design


5. Physical Design
6. Prototype

7. Performance
Evaluation
2. Conceptual Design

3. Selection of DBMS
8

Requirements Analysis
9
10

Process 1:
Employee/Intern Management

MAIN FUNCTION:


INFLOWS (forms)


OUTFLOWS


11

Process 2: Reporting

MAIN FUNCTION:

INFLOWS:

OUTFLOWS:




12

MAIN FUNCTION:

INFLOWS:

OUTFLOWS:

13

MAIN FUNCTION:



INFLOWS:

OUTFLOWS:


14

Conceptual Design
15

● 4 Entities
○ Intern
○ Employee
○ Project
○ Equipment

● 3 Relationships
○ Assigned to
○ Use
○ Requires
16

Selection of DBMS
17

FUNCTIONALITY: The DBMS had to be user-friendly and not


complicated to use.

FUNCTIONALITY: The DBMS had to be compatible with an


application coded in PHP.

COST: The DBMS had to be low cost, or free to use.

SIZE: As HSFL is a small size company, the DBMS had to fit with a
moderate level of data.

SELECTION:
Relational Database Management System
18

High
Offering level

Mid

Low

User Compatible Cost Size


Friendly with PHP

ORACLE INGRES MICROSOFT ACCESS IBMDB2


(standard edition)
19

High
Offering level

Mid

Low

User Compatible Cost Size


Friendly with PHP

ORACLE INGRES MICROSOFT ACCESS IBMDB2


(standard edition)
20

Logical Design
21
Logical Design

TOP DOWN APPROACH

ER DIAGRAM Tables:
3rd Normal Form
22

DENORMALIZED

Intern I_user I_fname I_lname I_bdate I_gender I_address Assigned I_user E_user
Semester I_email Gpa Grad_date Funding I_PhysChall I_veteran to
23

DENORMALIZED

Intern I_user I_fname I_lname I_bdate I_gender I_address Assigned I_user E_user
Semester I_email Gpa Grad_date Funding I_PhysChall I_veteran to

Intern I_user I_fname I_lname I_bdate I_gender I_address I_veteran

E_username Semester I_email Gpa Grad_date Funding I_PhysChall


24
Logical Design

Intern I_user I_fname I_lname I_bdate I_gender I_address I_veteran


E_username Semester I_email Gpa Grad_date Funding I_PhysChall

Employee_Ethnicity E_username E_ethnicity Intern_Ethnicity I_username I_ethnicity

Accomplishments I_user Accomplishments Date

Employee E_user E_fname E_lname E_bdate E_gender E_address E_veteran E_PhysChall Active E_email

Uses E_user Enumber E_amount T_number Use_date

Equipment Enumber E_type E_amount E_value E_package E_device Description

Project Pnumber Pname StartDate EndDate E_user Project Requires Pnumber Enumber Amount
25

Physical Design
26

OPTIMIZE Tuned
RETRIEVAL Queries
Index
FROM
SECONDARY Create Storage
STORAGE Views Level
Decisions
27

1. Tuning Queries
SELECT I_user, GROUP_CONCAT(`I_ethnicity` SEPARATOR ', ') AS ALIAS, I_fname, I_lname,
I_bdate, I_gender, I_veteran, I_PhysChall, Semester
FROM intern_ethnicity, intern
WHERE I_username=I_user AND Semester='Spring $value1' AND Semester='Fall $value1'
GROUP BY I_user;

SELECT I_user, GROUP_CONCAT(`I_ethnicity` SEPARATOR ', ') AS ALIAS, I_fname, I_lname,


I_bdate, I_gender, I_veteran, I_PhysChall, Semester
FROM intern_ethnicity, intern
WHERE I_username IN (SELECT I_user
FROM employee
WHERE Semester='Spring $value1' OR Semester='Fall $value1')
GROUP BY I_user;
28

2. Indexing

Equipment Intern
Types: Semester:
Intern I_user I_fname I_lname
Equipment Enumber E_type E_amount
I_bdate E_username Semester I_email
E_value E_package E_device Description Gpa I_gender I_address I_veteran
Grad_date Funding I_PhysChall

Significant amount of data retrieval + Indexing


= Faster Data Retrieval
29

3. Create Views
Intern_Underrepresented_View Employee_Underrepresented_View

Includes: Includes:

IF: IF:

= Pre-joined Tables
= Faster Data Retrieval
30

4. Storage Level Decisions

B TREE

EFFECTIVE
= FILE
ORGANIZATION
HASH INDEXING
31

Prototype

http://localhost/HSFL_Project/login.php
32

Performance Evaluation
33

Black Box White Box


Testing
+ Testing
5 Users
5 Users
USER TESTING: USER TESTING:
Little Experience Knowledgeable

= New remaining feature requirements


34
35

External Database plans


● Give HSFL employees a tutorial on how
to use all capabilities of the database
● Give company full access to database

Internal Database Plans


● Create way for HSFL to add new
types of equipment
● Include suppliers
● Add increased security throughout all
pages
36


Earn more funding for


future projects

Build more microsatellites Mentor more interns


37
38

● Data Dictionary
○ DFD
○ ER

● Selection of DBMS
○ MySql, Oracle, Ingres, Microsoft Access, IBMDB2

● Project Management
○ Agile Methodology
○ GANTT Chart

● Prototype

● Performance Evaluation
○ Survey Results
Back To Appendix

39

Process Main Functions Inflows/Outflows

1.0 Employee INFLOW:


Management ● Retrieve Applications ● Application Form
● Review Applications Change Information Form
OUTFLOW:
● Account Information
● Changed Information

2.0 Reporting ● Create Annual and Semi-Annual Report INFLOWS:


● Create Email lists to the Internal ● Account information
Communication process OUTFLOWS:
● Semi-Annual Report
● Annual Report
● Email Lists
● Project Report

3.0 Workforce INFLOWS:


Development ● Monitor/Track intern progress ● Accomplishments
OUTFLOWS:
● Intern Updates

4.0 Equipment ● Check Equipment INFLOW


Management ● Take Out Equipment ● Request Equipment Report
● Receive Equipment ● Type, user, values, amount
OUTFLOW
● Equipment Report
● Equipment
Back To Appendix

40
Back To Appendix

41
Employee Application

Attribute Data Type Description

E_user Short Text Username of employee

E_Fname Short Text First name of Employee

E_Lname Short Text Last name of Employee

E_Address Short Text The physical mailing address of employee

E_Bdate Date Birth date of employee

E_Gender Short Text “F” or “M”

E_Ethnicities Short Text Asian, Caucasian, Native American, Pacific Islander, Native Hawaiian, African American,

E_Veteran Short Text ““Y” or “N”

E_Physically_challenged Short Text “Y” or “N”

Activw Short Text “Y” or “N”

E_Email Short Text Email Address of Employee


Back To Appendix

42
Intern Application

Attribute Data Type Description

I_user Short Text Username of intern

I_Fname Short Text Intern First Name

I_Lname Short Text Intern Last Name

I_Address Short Text The physical mailing address of intern

I_Bdate Date Birth date of intern

I_Gender Short Text “F” or “M”

I_Ethnicities Short Text Asian, Caucasian, Native American,Native Hawaiian Pacific Islander, African American

E_email Short Text Email of intern

GPA Number GPA of Student within the range of 1.5-4.5

GradDate Date Date of expected graduation

I_Veteran Short Text “Yes” or “No”

I_Physically_challenged Short Text “Yes” or “No”

Semester Short Text Spring *year* or Fall *year*

Funding Float $ Funding

E_User Short Test Mentor’s username


Back To Appendix

43
Back To Appendix

44
Account Info

Attribute Data Type Description

E_user Short Text Username of employee

E_Fname Short Text First name of Employee

E_Lname Short Text Last name of Employee

E_Address Short Text The physical mailing address of employee

E_Bdate Date Birth date of employee

E_Gender Short Text “F” or “M”

E_Ethnicities Short Text Asian, Caucasian, Native American, Pacific Islander, Native Hawaiian, African American,

E_Veteran Short Text ““Y” or “N”

E_Physically_challenged Short Text “Y” or “N”

Activw Short Text “Y” or “N”

E_Email Short Text Email Address of Employee


Back To Appendix

45
Account Info

Attribute Data Type Description

I_user Short Text Username of intern

I_Fname Short Text Intern First Name

I_Lname Short Text Intern Last Name

I_Address Short Text The physical mailing address of intern

I_Bdate Date Birth date of intern

I_Gender Short Text “F” or “M”

I_Ethnicities Short Text Asian, Caucasian, Native American,Native Hawaiian Pacific Islander, African American

E_email Short Text Email of intern

GPA Number GPA of Student within the range of 1.5-4.5

GradDate Date Date of expected graduation

I_Veteran Short Text “Yes” or “No”

I_Physically_challenged Short Text “Yes” or “No”

Semester Short Text Spring *year* or Fall *year*

Funding Float $ Funding

E_User Short Test Mentor’s username


Back To Appendix

46
Annual Report

Attribute Data Type Description

E_Fname Short Text First name of Employee

E_Lname Short Text Last name of Employee

E_Address Short Text The physical mailing address of employee

E_Bdate Date Birth date of employee

E_Gender Short Text “F” or “M”

E_Ethnicities Short Text Asian, Caucasian, Native American, Pacific Islander, Native Hawaiian, African American,

E_Veteran Short Text ““Y” or “N”

E_Physically_challenged Short Text “Y” or “N”

Active Short Text “Y” or “N”

# of Female *Derived Attribute*

% of Female *Derived Attribute*

% of Underrepresented *Derived Attribute*


Back To Appendix

47
Annual Report

Attribute Data Type Description

I_Fname Short Text Intern First Name

I_Lname Short Text Intern Last Name

I_Address Short Text The physical mailing address of intern

I_Bdate Date Birth date of intern

I_Gender Short Text “F” or “M”

I_Ethnicities Short Text Asian, Caucasian, Native American,Native Hawaiian Pacific Islander,
African American

I_Veteran Short Text “Yes” or “No”

I_Physically_challenged Short Text “Yes” or “No”

Semester Short Text Spring *year* or Fall *year*

Funding Float $ Funding

# of Female *Derived Attribute*

% of Female *Derived Attribute*

% of Underrepresented *Derived Attribute*


Back To Appendix

48
Email Lists

Attribute Data Type Description

I_user Short Text Username of intern

I_email Short Text Intern Email

E_user Short Text Username of employee

E_email Short Text Employee email


Back To Appendix

49
Project Report

Attribute Data Type Description

PName Short Text Name of Project

Pnumber Number Specific number for each project

Account Number Specific account for each project

Startdate Date Starting date of the project

Enddate Date Ending date of the project

E_users Short Text Head employee user that are in charge of the project
Back To Appendix

50
Back To Appendix

51

Accomplishments

Attribute Data Type Description

I_user Short Text Intern Username

Accomplishments Long Text Description of major accomplishments

Date Date Date accomplishment inputted

Intern Updates
Attribute Data Type Description

User Short Text User of Intern or Employee User

Accomplishments Long Text Description of major accomplishments

Date Date Date accomplishment inputted

GradDate Date Expected Grad Date

GPA Short Text GPA of intern


Back To Appendix

52
Back To Appendix

53
Equipment Report/Equipment

Attribute Data Type Description

E_number number Number assigned to equipment

Amount Number Number of equipment taking out/adding

Type Short Text Name of equipment

Package Short Text Package description of equipment

Cost Number Cost of equipment

Value Short Text Value of equipment

Description Short Text Description of equipment


Back To Appendix

54
Request Equipment Report

Attribute Data Type Description

Type Short Text Name of equipment

Value Short Text Value of equipment


Back To Appendix

55

● 4 Entities ● 3 Relationships
○ Intern ○ Assigned to
○ Employee ○ Use
○ Project ○ Requires
○ Equipment
Back To Appendix

56
Employee

Attribute Data Type Description

E_user Short Text Username of employee

E_Fname Short Text First name of Employee

E_Lname Short Text Last name of Employee

E_Address Short Text The physical mailing address of employee

E_Bdate Date Birth date of employee

E_Gender Short Text “F” or “M”

E_Ethnicities Short Text Asian, Caucasian, Native American, Pacific Islander, Native Hawaiian, African American,

E_Veteran Short Text ““Y” or “N”

E_Physically_challenged Short Text “Y” or “N”

Active Short Text “Y” or “N”

E_Email Short Text Email Address of Employee

# of Female *Derived Attribute*

% of Female *Derived Attribute*

% of Underrepresented *Derived Attribute*


Back To Appendix

57
Employee

Attribute Data Type Description

E_user Short Text Username of employee

E_Fname Short Text First name of Employee

E_Lname Short Text Last name of Employee

E_Address Short Text The physical mailing address of employee

E_Bdate Date Birth date of employee

E_Gender Short Text “F” or “M”

E_Ethnicities Short Text Asian, Caucasian, Native American, Pacific Islander, Native Hawaiian, African American,

E_Veteran Short Text ““Y” or “N”

E_Physically_challenged Short Text “Y” or “N”

Active Short Text “Y” or “N”

E_Email Short Text Email Address of Employee

# of Female *Derived Attribute*

% of Female *Derived Attribute*

% of Underrepresented *Derived Attribute*


Back To Appendix

58
Intern

Attribute Data Type Description

I_user Short Text Username of intern

I_Fname Short Text Intern First Name

I_Lname Short Text Intern Last Name

I_Address Short Text The physical mailing address of intern

I_Bdate Date Birth date of intern

I_Gender Short Text “F” or “M”

I_Ethnicities Short Text Asian, Caucasian, Native American,Native Hawaiian Pacific Islander,
African American

E_email Short Text Email of intern

GPA Number GPA of Student within the range of 1.5-4.5

GradDate Date Date of expected graduation

I_Veteran Short Text “Yes” or “No”

I_Physically_challenged Short Text “Yes” or “No”


Back To Appendix

59
Intern Cont.

Attribute Data Type Description

Semester Short Text Spring *year* or Fall *year*

Funding Float $ Funding

E_User Short Test Mentor’s username

Accomplishments Long Text Users Accomplishments

# of Female *Derived Attribute*

% of Female *Derived Attribute*

% of Underrepresented *Derived Attribute*


Back To Appendix

60
Project

Attribute Data Type Description

PName Short Text Name of Project

Pnumber Number Specific number for each project

Account Number Specific account for each project

Startdate Date Starting date of the project

Enddate Date Ending date of the project

E_users Short Text Head employee user that are in charge of the project
Back To Appendix

61
Equipment

Attribute Data Type Description

E_number number Number assigned to equipment

Amount Number Number of equipment taking out/adding

Type Short Text Name of equipment

Package Short Text Package description of equipment

Cost Number Cost of equipment

Value Short Text Value of equipment

Description Short Text Description of equipment


Back To Appendix

62
Uses and Requires

Attribute Data Type Description

Tnumber Number Transaction Number

Use Date Float $ Funding

Amount Number Amount taken out

Attribute Data Type Description

Amount Number Amount taken out


Back To Appendix

63

Relational Object Oriented Object Relational

Pros -Data is stored once -A lot of code is already inside -Software to convert data
object oriented data provided
-Modification of data is simpler and -Data model is based on real
storage efficiency can be high world
-Security is better with tables
-Modular, extensive, and
-Adaptable to future changes in the reusable: software productivity
database and maintainability is easier

Cons -Can be expensive to setup and maintain -Not necessary for simple -Speed Performance is
relationships and data lower because of constant
-Structure Limits -More tools and standards are data conversion
made for RDBMS
-New forms of data can be confusing -More Complex -Not a lot of information and
-Isolated databases are common software developed
-Slower programs
Back To Appendix

MySQL 64

● Functionality: supports many program languages


including Python, C++, Java, PHP, etc.
● Works with IX, Linux, OS X, Windows and more
● Size of Database: is great for single, multiple and small
business
● Cost
○ Community edition: Free
○ Standard edition: $2000
○ Cluster: $10,000
○ Enterprise: $5000
Back To Appendix

Oracle 65

● Functionality: supports C, C++, Java, Python and etc.


Works with many platforms

● Size of Database: focuses on more larger companies and


organizations.

● Cost: pay monthly with the three editions (Enterprise,


Standard, and Express)
Back To Appendix

Ingres 66

● Functionality: compatible with AIX, HP-UX, Linux, Solaris,


and Windows.

● Size of Database: is for 1 to over 10 thousand employees.

● Cost: an agreement with the company giving a quote upon


request.
Back To Appendix

Microsoft Access 67

● Functionality: compatible with C, C++, Java, and a few


others
Only works with windows

● Size of Database: small to big companies not


recommended for single users and small groups.

● Cost:Free: 256MB
■ Pays as you use GB and subscription
Back To Appendix

IBM DB2 68

● Functionality: C++, C, Java, PHP, Python and etc


Compatible to Linux, Window, Solaris and z/OS. Very
scalable
● Size Of Database: great for small and large companies

● Cost: pays with each memory add on after 256 and all
appliances needed for the database.
Back To Appendix

69

● Uses short development


cycles called “sprints” to
focus on continuous
improvement

● It is an iterative process
with a people-centric
approach to software
development

● Benefits:
○ Can rapidly identify
and adjust for issues
○ Deliver a better
product, faster
Back To Appendix

70

Agile Manifesto
1. Customer satisfaction is always the highest priority and is achieved through rapid and continuous delivery.
2. Changing environments are embraced at any stage of the process to provide the customer with a competitive
advantage.
3. A product or service is delivered with higher frequency.
4. Stakeholders and developers collaborate closely on a daily basis.
5. All stakeholders and team members remain motivated for optimal project outcomes, while teams are provided with
all the necessary tools and support, and are trusted to accomplish project goals.
6. Face-to-face meetings are deemed the most efficient and effective format for project success.
7. A final working product is the ultimate measure of success.
8. Sustainable development is accomplished through agile processes whereby development teams and stakeholders
are able to maintain a constant and ongoing pace.
9. Agility is enhanced through a continuous focus on technical excellence and proper design.
10. Simplicity is an essential element.
11. Self-organizing teams are most likely to develop the best architectures and designs and to meet requirements.
12. Regular intervals are used by teams to improve efficiency through fine-tuning behaviors.
Back To Appendix

71
Back To Appendix

72

Employee Side:
Main Webpage Section Purpose Forms Reports

Account -Fill out application -Application Form -Account Information


-Create account -Change information
-Change or update account Information
Equipment -Find, add, and take out equipment -Put in Equipment -Equipment Report
-Add Equipment -Equipment per Project

Reporting -Print annual and semiannual report -Report and Bidding -Semi-annual/Annual Report
statistics Form Statistics
-Allow users to obtain specific data on -Statistics Request -Email List Statistics
previous interns to send customized -Project Report
newsletters
Workforce -Allow Employees to track intern -Track Progress -Log Accomplishments
Development progress
Back To Appendix

73

Intern Side:

Main Webpage Section Purpose Forms Reports

Application Fill out application -Application Form -Account Information


Create account
Accomplishments Monitor accomplishments per user -Accomplishments -Intern Updates
Form

Change Information To change or update information on -Change information


application
Back To Appendix

74

1. Overall, how well does our system meet your needs? :


2. Did it take you more or less time than you expected to find what you were looking for?
A lot less time A little more time
A little less time A lot more time
About what I expected

3. How visually appealing is our website?


4. What did you like about our website?

5. Do you have any comments about how we can improve our website?
Back To Appendix

75

1. Overall, how well does our system meet your needs? :


2. Did it take you more or less time than you expected to find what you were looking for?
A lot less time A little more time
A little less time A lot more time
About what I expected

3. How visually appealing is our website?


4. What did you like about our website?
It a n u t e d p e s . Gen l u r-f i d . It e m f e
ne f H L.

5. Do you have any comments about how we can improve our website?
It o d ic av ca li t u l c ec t h up an
or qu n ro h te.
Back To Appendix

76

1. Overall, how well does our system meet your needs? :


2. Did it take you more or less time than you expected to find what you were looking for?
A lot less time A little more time
A little less time A lot more time
About what I expected

3. How visually appealing is our website?


4. What did you like about our website?
I li t ev de of r a ni l in s t , an s o s i s
to te say r . The c o l of s t i j w H L
ne . Ver n i n .
5. Do you have any comments about how we can improve our website?
The g i l le c, an l em is ya li n va d om
ar .

You might also like