CS 5150
Software Engineering
Fall 2012

Project Suggestion: Tracking greenhouse usage and billing


Tracking greenhouse usage and billing

Client

Dirk P Swart
dps42@cornell.edu

Overview

This project is producing a greenhouse space tracking and billing system for production use at CALS that is expected to last for several years (so a great resume builder). We would love your help to write, test and deliver the code. You will work with a professional software development team on campus who have already started the project, and be involved in the complete development life cycle using Agile development practices and formal project management.

Problem statement

Space in greenhouses needs to be tracked carefully. For example, certain plants need specific treatment regimes, some are pathogenic and others are sensitive. Therefore all space needs to be tracked and monitored so university technicians can know what to do, who owns which plants and what to do in an emergency.

Technical environment

Python and the Pylons framework with an Oracle back end. Users interact with the system over the web. Code is hosted in a Mercurial repository and bugs are tracked with Pivotal Tracker, and project pages are maintained in Confluence. An older space tracking system exists as a reference. The following documents are available as the specification:
  • Data model diagram.
  • Web page mockup list (Note: Mockups will be produced by a designer. You are not expected to do it).
  • Product backlog.
  • System workflow diagram and notes.
  • Client notes.
  • Existing system which is to be replaced.
The deliverable will consist of:
  • greenhouse space request (create new records, update records)
  • growth chamber space request (new records, update records)
  • Billing system ( get an account to charge from the Business center)
    • bill runs quarterly
    • account info may have more than one account
    • different facility type will have different charge rate
  • map system (user can click on the greenhouse location map and get more detail info and the image will enlarge)
  • space attribute database (details about the physical space [greenhouse room or growth chamber])
  • user database (user/PI/Manager/Emergency Contact)

Summary

This project will create production code for Cornell. Because this project is small, well-contained and already fully spec'd out from client expectations down the database tables, we believe it is the correct size to be comfortably completed in the time you have available. You will learn how to function as part of a professional development team, and hopefully have some fun as well. We are committed to weekly meetings, detailed feedback, will attend your presentations and help you come up to speed in our environment, and expect a similar commitment from you. If you are non-responsive or otherwise unprofessional, please don't waste our time.

[ Home ]