| |
System Title |
| |
|
CCR Server 1.0 & CCR Client 1.0 |
| |
|
|
| |
Mission Statement |
| |
|
To create a reliable system that meets customer expectations and requirements, remains flexible, manages multiple trains on a system without collisions, and is well documented and easy to use. |
| |
|
|
| |
Problem Statement and Purpose |
| |
|
A new system needs to be created to handle multiple devices and trains based off of requirements listed above. This system needs to prevent collisions and allow users with no prior DCC or computer experience to operate these trains. Multiple interfaces need to be created to assist wtih this function and multiple ideas need to be brought in. Documentation and flexibility for future use are also important factors. |
| |
|
|
| |
Constraints |
| |
|
> Start Date (Schedule):
- Analysis and Design: January 25 - February 26
- Coding and Implementation: March 1 - Finish
> Deadlines:
- Test applications should be up by early April 2010 with official release by late April 2010
> Budget Constraints:
- Cost of project will be close to $0 as it should be utilizing old hardware and resources. My time is also considered free.
> Technology Constraints:
- All technology has to be what the college currently has and is dependent on devices currently available for testing. |
| |
|
|
| |
Specific Objectives |
| |
|
Create a reliable system that allows multiple devices to connect to the track and control trains. This needs to prevent collisions and also be easy to use. |
| |
|
|
| |
Method of Evaluation |
| |
|
This system will be evaluated on what features are likely to be implemented, whether or not the system is feasible to be used by anyone, whether or not it fulfills requirements, whether it is flexible for future growth, and how well it is documented. CS faculty and peer input will work on final evaluations. |
| |
|
|
| |
Feasibility Study |
| |
|
Operational feasibility – operational feasibility for this is good as labor and work on it is free and this is to bring awareness to CS work. This system should resolve some issues that the old one was having and open it up to a new realm where multiple people can use this.
Technical feasibility – the hardware and software resources that the college has appear to be sufficient to meet the requirements of this system. There appears to be room on servers to store this and my personal website can be used for documentation. All that is really needed is the user to have Framework 3.5 installed on their computer and the appropriate .exe to run.
Economic feasibility – the benefits of adding this system do appear to outweigh the costs as this project will be done for free. Ongoing support and maintenance should also be somewhat low as it should be well documented for others to assist and users will have rights to manage system. As it should be saving time and spreading word of CS projects, this is another great benefit that is just utilizing previous hardware.
Schedule feasibility – the feasibility of this project being completed in this short time appears to be realistic. As this is utilizing previous work and elaborating on it, it should just be a matter of getting into this new design and figuring out how to connect multiple devices. However, older systems do not have any logic to prevent collisions and many things will need to be fixed before completion. |
| |
|
|
| |
|
^ Back to Top |
