1
|
- Week 1
- INFM 718N
- Web-Enabled Databases
|
2
|
- Teaching theater orientation
- Why do this?
- Architecture
- Tools
- Course design
- Term project
|
3
|
- Login
- University password and ID
- Tech support
- Notes
- RTF for Word, Powerpoint for printing
- Video
|
4
|
- Explore one Web-enabled database (7 min)
- Work in 10 teams of 2 people each
- Identify features you like and dislike
- Report to the class (1 minute!)
- Very briefly describe it
- Content, control, presentation, policies
- Say one new thing you like, one that you don’t
|
5
|
|
6
|
- Formal
- To permit automated reasoning
- Necessarily incomplete
- Useful for a purpose
|
7
|
- Data reuse
- Multiple views
- Scalability
- Personalization / access control
|
8
|
- Brittle
- Complex
- Learning, design, implementation, debugging
- Formally modeled
|
9
|
- Web
- Standards: HTTP / (X)HTML / URL
- Software: Server, Browsers
- Database
- Programming languages
- Server-side: PHP, Perl, JSP, ASP.NET
- Client-side: JavaScript, Java
- Data interchange
|
10
|
- WAMP (for PC)
- PHP 5.1.2 + MySQL 5.0.18 + Apache 2.0.55
- GUI tools
- OTAL (Sun Unix)
- PHP 5.0.5 + MySQL 4.1.15 + Apache 2.0
- Text editor/Integrated Dev. Environment
- Eclipse, emacs, notepad, …
|
11
|
- Pair with someone you don’t know
- Briefly interview each other
- Name and what program they are in
- One interesting thing about them
- One thing they want to learn from this class
- Take a 10 minute break
- Introduce them after the break
|
12
|
- Process design
- Algorithm design
- Coding
|
13
|
- Reusing code [run the book’s programs]
- Understanding patterns [read the book]
- Applying patterns [modify programs]
- Coding without patterns [programming]
- Recognizing new patterns
|
14
|
- Functional decomposition
- High-level languages
- Structured programming, object-oriented design
- Patterns
- Design patterns, standard algorithms, code reuse
|
15
|
- http://www.en.wampserver.com/
- Run phpinfo.php
- Error reporting on? M=
ySQL
configured?
- Create a database and user accounts (mysql)
- Run mysql_test.php
|
16
|
- Local vs. server-based display
- HTML as an indirect display mechanism
- “View Source” for debugging
- Procedural vs. Object-Oriented
|
17
|
- Database Design (LBSC 793)
- Java Programming (LBSC 790/INFM 718B)
- Human-Computer Interaction
- Information Retrieval Systems (LBSC 796)
- XML Encoding (LBSC 708Y)
|
18
|
- Weekly class sessions
- Ways of thinking
- Mixed-initiative interaction (questions, teamwork)
- Readings
- Exposure to ideas, details, and references
- Structured exercises
- Points of departure for experiential learning
- Project
- Experiential learning, mastery of details
- Mailing list and optional TA “lab sessions”
- Student-initiated interaction
|
19
|
- Project: 80%
- Team grade: &=
nbsp;
40%
- Your management role: 20%
- Your technical role: 20%
- Homework: 10%
- PHP, MySQL &nb=
sp;
5% each
- Participation: 10%
- Class sessions, mailing list
|
20
|
- Optimally 3-person teams
- You pick ‘em, you live with ‘em!
- Minimum of 2 (severely limits what can be done)
- Max of 4, but only for Ajax teams
- Must solve a real problem for a real client
- No configuration/language limitations
|
21
|
- A 90-second “elevator pitch”
- One interesting and feasible idea
- Plus why they should want you on their team!
- Showing one optional powerpoint slide
- Illustrate your point, don’t say the same words!
- One-page handout (22 copies)
- Your idea in a short paragraph
- Your name, picture and contact information
- A list of your strengths
|
22
|
- Functionality
- Content
- Usability
- Security/Stability
|
23
|
- What was the muddiest point in today’s class?
- Be brief!
- No names!
|