(1)

Project Overview

Philip JohnsonCollaborative Software Development

LaboratoryInformation and Computer Sciences

University of Hawaii

(2)

Who are we? ICS 414 students•Second semester software engineering•Undergrads

ICS 699 students• Independent study•Graduate students

REIS Ph.D. students and professors•Research in energy•Robert, Shanah, Xiangrong, Philip, others?

Community members•HEEP, others?

(3)

Why are we here? To do innovative, groundbreaking research and development in energy and sustainability.

To define requirements and perform technology development experiments for the “Kukui Cup”, a UH Dorm Energy Competition for Fall 2010.

To enhance Hawaii’s consumer-facing energy information through partnership with the Hawaii Energy Efficiency Program.

To develop advanced software engineering skills through participation in ICS 414 and ICS 699.

(4)

414/699 Learning objectives Build upon the software engineering skills you learned last semester:•tools and techniques for group-based project planning, management, design, implementation, testing, quality assurance, version control, configuration management

How to build upon?•Apply to new domain, new programming languages or development environments, external sponsors•Less “spoon feeding”; translate high-level strategic goals into concrete weekly action

(5)

414/699 Evaluation ICS 414/699 attempts to mimic “real world” evaluation in professional settings:•No tests, quicky quizzes, etc.•Weekly individual progress report•Monthly group milestone•Project notebook

Just like in the real world, you must show initiative to succeed in ICS 414/699

(6)

Project structure Multiple subprojects, energy related.

Groups of 2-4 people. The same subproject can be pursued by multiple groups.

There will be four milestones during the semester, every four weeks on Tuesday:•Feb 9, March 9, April 6, May 4

You must complete a subproject and present it on each milestone date.

You can change subprojects after each milestone.

New subprojects can be proposed starting with second milestone.

(7)

414/699 Weekly Meetings There are two required meetings with me per week.

General Meeting•Tuesdays, noon, POST 126•Each group gives 5+ minute update on their accomplishments of past week.•Question asking and answering

Project meeting•POST 307, meeting time TBD•In depth, working meeting about project.

(8)

414/699 Grading You will receive four grades this

semester, one per milestone.

Your grade will be based on:1.Weekly blog posts2.Group organization, group process.3.Application of open source SE

techniques.4.Milestone deliverable5.Project Notebook

(9)

1. Weekly Blog Posts Due every Tuesday by 8am; email me the link at philipmjohnson@gmail.com; do not expect reminders!

Content:•Write for the world, not the professor.•Explain what you as an individual and the group as a whole accomplished.•What problems did you encounter? What are you planning to do about them?•What do you plan to accomplish during the next week?•Provide links to relevent pages, images, etc. as appropriate.•Each post should be grammatically correct, informative, at least one page long, and interesting.

(10)

2. Group Organization; Process

You are expected to establish an effective, transparent group organization and process.

Effective means:•Every one contributes approximately equally, progress is immediate, progress is constant.

Transparent means:•An outsider (i.e. me) can always determine the current state of the project.

Your best bet: Google Project Hosting •SVN holds work products.•Wiki pages holds documentation.•Associated google group holds discussions.• Issue page holds tasks, assignments, status.

(11)

3. Application of Open Source Software Engineering

Techniques Use of a cloud-based open source hosting service (google project hosting).

Produce a working system early and often.

High quality, automated test suite.

Automated build and release.

(12)

4. Milestone Deliverable Each milestone deliverable should be a functioning, “complete” system.•Accomplishes some subset of requirements.•Fully tested, fully documented.•Easy to install and run by end-users.•Easy for new developers to jump in and take over development.

(13)

5. Project Notebook A physical, bound notebook. Each entry dated.

Provides a chronological ordering of:•Meeting notes•Design ideas•Readings notes•etc.

Supports “active learning”, mitigates information overload.

(14)

Subprojects for first milestone

WattDepot apps:•A set of stand-alone webapps for WattDepot.

Google Stoplight Visualization:•General purpose stoplight widget.

Hawaii Energy Efficiency Program apps:•Oahu grid data inside the HEEP website.

Kukui Cup technology prototypes:•Dorm energy competition website.

Kukui Cup competition design:•Content and structure of the competition.

Energy meter design•Hardware and software specs for dorm energy meters.

(15)

WattDepot Apps WattDepot needs a set of individual user interface web apps to:•quickly visualize repository•provide small samples of useful code•Wicket-based

Multiple, standalone apps:•WattDepotVisualizer

-Charts using Google Visualization•WattDepotBrowser

-Interactively inspect a WattDepot respository.

•WattDepotMonitor-Provides real-time updates of a source. -Automatically pushes most recent data.

(16)

QuickTime™ and a decompressor

are needed to see this picture.

(17)

Google Stoplight Visualization Create a new Google visualization called a “stoplight” using Javascript and the Google Visualization API.

Example application: a Google Gadget that provides Oahu grid stoplight visualization by hooking it up to WattDepot.

Ultimate goal is inclusion of this widget in the Google Visualization Gallery.

(18)

QuickTime™ and a decompressor

are needed to see this picture.

(19)

HEEP website The Hawaii Energy Efficiency Program is interested in incorporating Oahu grid data into their website.

You will work with their web design team to add (for example) an Oahu stop light to their web site.

(20)

QuickTime™ and a decompressor

are needed to see this picture.

(21)

Kukui Cup Technology Prototypes

Explore various technology infrastructures for the 2010 Dorm Energy Competition.

Possible technologies: Java/Wicket, Scala/Lift, Drupal, CodeIgniter, etc.

Potential integration with:•Twitter•Google Gadgets•Facebook•SMS•Dorm Kiosk

(22)

Kukui Cup Competition Design

Overall content development for the Kukui Cup.

Research dorm energy competitions and behavioral change methods.

Apply community-based social marketing principles.

Research and develop content for website:•Commitments, Social Norms, •Energy literacy development•Rules for contest•Point system

Create mockup of all content using Balsamiq.

(23)

QuickTime™ and a decompressor

are needed to see this picture.

(24)

QuickTime™ and a decompressor

are needed to see this picture.

(25)

Energy Meter Design Work with Prof. Xiangrong Zhou of EE on the design of energy meters for dorm use.

Issues:•Research possible COTS meters. •ACme meter design/implementation.•Requirements: 10 second sampling, multiple meters per dorm (floor?), internet access, WattDepot storage capable.

(26)

QuickTime™ and a decompressor

are needed to see this picture.

(27)

Next steps Fill out form, rank order all projects you would be willing to work on.•At least two projects.

Indicate people you would like to work with.

I will post assignments to the mailing list before Thursday.

Come to POST 126 Thursday •start work in your groups.•schedule weekly meeting time with me