Project Links |
Bid 2 - Programming Analysis Tool
| |||||||||||
|
1.0 Project Preferences
| |||||||||||
|
2.0 Qualifications and Tradeoffs
2.1 Strengths and Qualifications | |||||||||||
|
Control4 is our team leader's current place of employment and as such he has daily access to an informational resource. He also understands basic Control4 functionality and has done some C4 system programming.
| |||||||||||
|
2.2 Tradeoffs, constraints, and special considerations
| |||||||||||
|
Not all members of the team have experience in C#, the programming language that would be best for this project.
| |||||||||||
|
3.0 Programming Analysis Tool (Casey Anderson of Control4 Corp., Draper, Utah)
3.1 Approach | |||||||||||
|
Define a minimum required feature set for the tool
Select language/dev environment (probably C#/VS2005) Identify development milestones Break out tasks for each milestone and assign to team members based on skills | |||||||||||
|
3.2 Implementation Considerations
| |||||||||||
|
For consistency, we would like to have access to standard
Control4 graphics and possibly the source code of an
existing Control4 application to use as a starting point.
We may need to set up a basic C4 system that is accessible
to all team members to use during the development process.
Ideally, the location of this system would be somewhere on
campus.
| |||||||||||