Project Bid Proposal 2

Version 1.0

Date: Friday Jan 14, 2005

Product: Home Automation System Web Interface

Team Silent Mission

Jenny Greenwood, Shannon Whitaker, Brittney Brown, Zack Douglas




Table of Contents

   1.0 Project Preferences

   2.0 Qualifications and Tradeoffs
      2.1 Strengths and Qualifications
      2.2 Trade-offs, Constraints, Special Conditions

   3.0 Project Name
      3.1 Approach
      3.2 Implementation Considerations


1.0 Project Preferences

  Jenny Shannon Brittney Zack Total
Control4 0 4 3 3 10


2.0 Qualifications & Tradeoffs

   2.1 Strengths and Qualifications

     All team members are competent in C++, HTML, HTTP, XML and socket
     programming, and have experience with C# .NET also.  Our group has
     prior experience with developing applications for the internet.

   2.2 Trade-offs, Constraints, and Special Considerations

     We all are experienced in using the internet and web applications. 
     We also obviously all have lights in our home that get left on, so we
     understand the demand for this type of product.

3.0 Project Name - Home Automation System Web Interface

   3.1 Approach

     The system has three major components, the ability to use it with
     a web browser, the ability to use it on a cell phone, and the ability
     to use it on a PDA.  These three implementations will require different
     code and structure.  We feel the best approach to developing these would
     be work on each component for all implementations at once.  For example,
     the main menu for the browser, phone and PDA would be developed at the
     same time.  We feel by approaching the system in this manner, we will
     be sure that all three implementations have the same functionality, 
     look and feel. 

   3.2 Implementation Considerations

     The system will be implemented like most web applications.  The basic interface
    will all be in HTML of course.  The html could then call a CGI wrapper
    that would call C++ programs on the server.  The results would then be
    returned in HTML format and sent back out to the user.  The C++ scripts
    could be made to be standard for all implementations, and just vary what
    sort of HTML is returned.  For example, the same C++ program could return
    code that would be suitable for a browser, or it could return code that
    is suitable for a PDA, based on information that is passed to it.