PSU Guest Lecture: Database Programming

Database Programming or Application Design with Databases or The Guest Lecture Dr. Shen Asked Me To Do Matthew Batchelder Web Application Engineer ITS

Ye Olde Overview

My Background

My Project Background

Application Design Process

Analysis

Language Selection

Database Design

Interface Design

Development

The Sweet Stuff

Industry

Where it was

Where it is

Where its going

Stuff I’ve Learned

Suggestions

Me

Background

PSU Graduate (PSC, actually)

PSU ITS

Help Desk

PHP/Java Programmer

Registrar PL/SQL Programmer

“ Web Application Engineer”

Database Design

Front-end Design

Javascript

PHP

PL/SQL

I’m a Blogger ( BorkWeb )

Project Background

As a Student

Database Class

Senior Project

On the Side (I’m a Geek)

Star Wars (Emperor’s Hammer)

Uber-Geeks Site

Random Database Projects

As an Employee

Lots of Misc. Apps

On the Side (I’m still a Geek)

BorkWeb

Uber-Geeks Site

MasterWish

Random Database Projects

Analysis

If you are beginning an application, there is undoubtedly a problem/inefficiency that needs a solution.

Compile a list of application needs

Build process maps: Map out

Uses of the application

Data flows

Analyze to root out inefficiencies

Choosing Your Language

Use what is appropriate

Weigh:

Your development capabilities

Time constraints

Language suitability

Thus far, I’ve opted for PHP in most cases

Database Design

This is the application’s foundation

Know your data

The Whiteboard is your friend

Interface Design

Storyboard

The Whiteboard is still your friend

Oh, and paper too

Graphics/Colors/Document Structure

It is extremely important to know what your application should look like!

Development

Develop in chunks

Database Abstraction

PHP: ADOdb & Pear

Modularization

OO is where its at

Templatization

SmartyTemplates & XTemplates

The Sweet Stuff

Javascript

XHR

The Industry

Industry

Where it was

Desktop Applications

Full featured

Updates difficult

Web-based Interfaces

Limited features

Well, Java Applets or ActiveX helped on the feature front…but both came with their own set of problems

Updates a cinch

Or…semi-cinch depending on your language of choice

Industry

Where it is

Desktop Applications

Full featured

Updates difficult

Web-based Applications

Full featured

Updates a cinch

Or…semi-cinch depending on your language of choice

Why the change?

Web 2.0 & AJAX & Ajax

Industry

Where its going

Who the *bleep* knows?

Keep an eye on

Ajax

Web 2.0

Collaboration

RSS & Remixability

Usability

Accessibility

Stuff I’ve Learned

Do your own thing

If you run into an issue search for the answer online…

ask friends and/or instructors for answers only as a last resort …when you’re at a job…chances are, no one knows the answer near you. Get used to it.

Brainstorm DB Design on Paper

When you have an idea, jot it down on paper or the whiteboard then leave it. Come back later and look at it again, you’ll be sure to find inefficiencies.

Stuff I’ve Learned (cont.)

Design your Database…don’t just build it

Its one thing to accomplish a task…it’s a completely different thing to do it correctly – Where “correctly” means:

Re-usable

Sustainable

Versatile

I find it useful to throw a design on the board and critique it aloud and (if possible) with another designer in the room.

Ideas can be bounced back and forth and inefficiencies found before any coding has been done

Design your Interface…don’t just build it

A solid set of mockups saves time and code. Scratch it down on paper before coding. Get a general idea about how your pages should contain and manipulate your data.

Suggestions