Course Description: Application of computer programming and system development concepts, principles, and practices to a comprehensive system. The student will analyze, design, document, and deliver a final presentation of a realistic system of moderate complexity. Students may propose their own project or select from projects assigned by the instructor. Proposed projects must be approved by the instructor. Students are expected to work individually, although group projects may be allowed on a case-by-case basis. Class meetings will include lectures on software design & engineering, presentations, walk-throughs, structured reviews, and other activities and exercises that will provide the information and structure needed to complete the project in one semester. Students that are completing an internship of equal sophistication should enroll in CS A495.
The course is designed to certify technical competency by all graduating seniors. All CS students will be expected to develop the ability to synthesize and integrate systems analysis, systems design, programming and business and information systems concepts, principles and practices in the development of computer-based information systems. The students will develop the ability to apply technical, managerial, communications and interpersonal skills to a realistic, moderately complex system development project. While the instructor of record is the primary supervisor, other faculty may provide input as warranted (e.g., provide direction in their area of expertise). This course is also used for CS Program assessment; the goal of assessment is to measure how well the program is meeting its intended goals. One mechanism for assessment is an ETS Field Test that will be required by all students. The other is your project deliverables. They will be evaluated by other faculty members but only your instructor is responsible for assigning your course grade.
This semester the course has also been selected for a pilot assessment for GER Integrative Capstone courses. You will be required to complete a survey regarding the GER assessment outcomes.
Homework Assignments: The assignments in this class represent milestones toward the completion of your project. This includes the following:
In addition, you must complete the CS Field Test.
Questions: If you have any questions, feel free to come in to my office. In general, I have an open door policy -- if I am available in my office, you are welcome to come by. An even better way to reach me is through email. I check my email frequently and you should receive a response quickly. Email is preferred over telephone and you will probably receive a faster response since I don't check voicemail very frequently. You can also contact me online via ICQ, AIM, or MSN Messenger (see contact info on the home page). I'm often up late and will be glad to answer questions if I'm available!
Exams: There are no exams in this course.
Resources: If you require a dedicated computer to complete your project (e.g. a server or notebook) then one can be provided for you, on a first-come first-serve basis.
Grading: Grading for this course is letter grade. The grading breakdown is shown below.
An incomplete or deferred grade will only be given for a valid excuse (e.g. medical reasons, death in the family, etc.). If you are unable to complete your project in the semester simply because you got too busy, then you will you receive an F or DF grade and must re-take the course in the future. This means that you should choose your project carefully to ensure that the scope of the work may be completed in a semester.
Cheating: Students are expected to uphold the UAA standard of conduct relating to academic dishonesty outlined in the UAA catalog and student handbook. Cheating is not tolerated and constitutes grounds for dismissal. For this class, it is permissible and encouraged to assist classmates in general discussions of how to complete your projects. It is not permissible to copy another's work (or portions of it) and represent it as your own. Note that this does not preclude you from using publicly available libraries or subcomponents in the completion of your project, but you should note authorship where appropriate.