|
Client expectations
The client can expect the following from the students:
- A careful study of the requirements.
- A design that meets those requirements.
- A tested and well documented system that performs as specified.
In return, the student can expect the following from the client:
- Weekly meetings.
- Feedback on draft documentation.
- Attendance at the project presentations.
The client must understand that a semester is a very short period of time to complete a substantial system. In previous years, about half of all CS 5150 projects have resulted in systems that have gone into production. However, the client has often found it necessary to continue work after the semester to add extra functionality. Sometimes, members of the project team have continued work the following semester, as an independent project.
Business considerations
A number of business considerations surround any practical software product. As part of the Feasibility Study and Plan, every project must describe how it will handle these considerations.
- For your software to interface with other programs, the client may provide access to trade secret or other proprietary information. In this case you may be asked to sign a non-disclosure agreement.
- As Cornell students you own the copyright in the software that you create. However, the client needs to be able to use your software and to use it as a basis for future work. You must either agree to transfer the copyright to the client or to provide the client with an unrestricted license to use it.
- It is just possible that a project may develop concepts that could be patented. This is a complex area, with implications for the project team, the university, and the client. The client may require a statement that covers this possibility.
- Some projects may be for companies in which members of the Cornell faculty or staff are principals. In such situations, the university's policy on conflicts of interest must be observed.
|
