Instructor Contact Information

Carl Stucke http://www3.cis.gsu.edu/cstucke/

Email Address: cstucke@gsu.edu (always the quickest way to reach me)

Course Website: TBA

Phone: 404-413-7379 office

Office: Room 906, 35 Broad Street (RCB Building)

Office Hours: TBA and in-person or online by appointment

Acknowledgement: The instructor is grateful to James Brown, Melody Moore, and John Sergo for their many years of leadership in the conduct of this course and for the use of their course materials.

This document is subject to change during the conduct of this course.

Students are invited to contact the instructor assistance with class work. The best, quickest way for doing this is via email (cstucke@gsu.edu ).

Prerequisites: All required BA and CIS 3000-level courses. Students must be CIS Majors at Georgia State University and must have completed certain course requirements at Georgia State.

Course Description:
This course provides an opportunity for students to apply the knowledge and skills acquired in the core courses to larger and more complex problems and to gain experience in working in teams.

Detailed Course Description:
This course provides an opportunity for students to apply the knowledge and skills acquired from previous course work on a full-scale systems development project for a client organization (external or internal). Student teams will conduct a feasibility analysis, develop project plans and system requirements specifications for the client. They will design a new system, develop and test a prototype of the resulting software, develop implementation plans and implement the prototype in the client environment. Upon completion of the course, students will present both oral and written reports on their project. Course grades will include the client organization's evaluations, and the input of each student team member, as well as the instructor's evaluation.

Method of Instruction Text Policies Grades TOP Project Guidelines

Course Objectives:
This course is designed to provide the student experience in working with a client organization to perform systems analysis and design from the initial request through a final design and prototype. In doing this, the student will demonstrate his/her ability to :

Students will be grouped into teams and assigned a project for a client organization. There will be interim project milestones and deliverables during the course to ensure that each project is progressing on schedule. On each due date, each team will submit a written report of the total project to date, and give a class presentation that updates the class on their progress.

After obtaining client requirements for their project, each student team will arrange a presentation of their requirements definition for their client, to make sure the team has a correct and complete understanding of the client's intentions and expectations. (See "Reality Check".)

At the end of the course, and after approval by the Course Director, each team will arrange a final presentation for their client, in which they will present their research (and prototype, if applicable) and appropriate documentation. On the Final Exam date or a scheduled class day, each team will give a complete presentation of their project before the class, the course Director, and invited faculty. Please see Project Guidelines for more details.

All other class time will be spent working in teams, meeting on-site with the client organization, or discussing the project with the course Director. It is a course requirement that each student be available for client meetings during business hours as required.

Departmental General Class Policies

Student work submitted in fulfillment of course requirements and any student activity recorded is deemed to be granted in the public domain (copyright-free) for the purposes of use as instructional or research material or for examples of student work in future courses.

Students are expected to attend all classes and group meetings, except when precluded by emergencies, religious holidays or bona fide extenuating circumstances.

Students who, for non-academic reasons beyond their control, are unable to meet the full requirements of the course should notify the instructor. Incompletes may be given if a student has ONE AND ONLY ONE outstanding assignment.

A “W” grade will be assigned if a student withdraws before mid-semester while maintaining a passing grade. Withdrawals after the mid-semester date will result in a grade of “WF”. Refer to GSU catalog or Registrar’s office for details.

Spirited class participation is encouraged and informed discussion in class is expected. This requires completing readings and assignments before class.

Unless specifically stated by the instructor, all exams and assignments are to be completed by the student alone.

Within group collaboration is allowed on project work. Collaboration between project groups will be considered cheating unless specifically allowed by an instructor.

Work copied from the Internet without a proper reference will be considered plagiarism and is subject to disciplinary action as delineated in the Student Handbook.

Any non-authorized collaboration will be considered cheating and the student(s) involved will have an Academic Dishonesty charge completed by the instructor and placed on file in the Dean’s office and the CIS Department. All instructors regardless of the type of assignment will apply this Academic Dishonesty policy equally to all students. See excerpt from the Student Handbook below:

Academic Honesty

(Abstracted from GSU’s Student Handbook Student Code of Conduct “Policy on Academic Honesty and Procedures for Resolving Matters of Academic Honesty” - http://www2.gsu.edu/~wwwdos/codeofconduct_conpol.html )

As members of the academic community, students are expected to recognize and uphold standards of intellectual and academic integrity. The University assumes as a basic and minimum standard of conduct in academic matters that students be honest and that they submit for credit only the products of their own efforts. Both the ideals of scholarship and the need for fairness require that all dishonest work be rejected as a basis for academic credit. They also require that students refrain from any and all forms of dishonorable or unethical conduct related to their academic work.

Students are expected to discuss with faculty the expectations regarding course assignments and standards of conduct. Here are some examples and definitions that clarify the standards by which academic honesty and academically honorable conduct are judged at GSU.

Plagiarism. Plagiarism is presenting another person’s work as one’s own. Plagiarism includes any paraphrasing or summarizing of the works of another person without acknowledgment, including the submitting of another student’s work as one’s own. Plagiarism frequently involves a failure to acknowledge in the text, notes, or footnotes the quotation of the paragraphs, sentences, or even a few phrases written or spoken by someone else. The submission of research or completed papers or projects by someone else is plagiarism, as is the unacknowledged use of research sources gathered by someone else when that use is specifically forbidden by the faculty member. Failure to indicate the extent and nature of one’s reliance on other sources is also a form of plagiarism. Failure to indicate the extent and nature of one’s reliance on other sources is also a form of plagiarism. Any work, in whole or part, taken from the internet or other computer based resource without properly referencing the source (for example, the URL) is considered plagiarism. A complete reference is required in order that all parties may locate and view the original source. Finally, there may be forms of plagiarism that are unique to an individual discipline or course, examples of which should be provided in advance by the faculty member. The student is responsible for understanding the legitimate use of sources, the appropriate ways of acknowledging academic, scholarly or creative indebtedness, and the consequences of violating this responsibility.

Cheating on Examinations. Cheating on examinations involves giving or receiving unauthorized help before, during, or after an examination. Examples of unauthorized help include the use of notes, texts, or “crib sheets” during an examination (unless specifically approved by the faculty member), or sharing information with another student during an examination (unless specifically approved by the faculty member). Other examples include intentionally allowing another student to view one’s own examination and collaboration before or after an examination if such collaboration is specifically forbidden by the faculty member.

Unauthorized Collaboration. Submission for academic credit of a work product, or a part thereof, represented as its being one’s own effort, which has been developed in substantial collaboration with assistance from another person or source, or computer honesty. It is also a violation of academic honesty knowingly to provide such assistance. Collaborative work specifically authorized by a faculty member is allowed.

Legal Requirements: Some project assignments may require legal agreements with the respective clients, and some projects may not require legal agreements. In cases where legal agreements are necessary, legal documents are available for student use. All students are expected to be familiar with the terms of the legal requirement documents furnished by the University.

All student work presented for course credit will identify the sources of information used, and any sources quoted verbatim will be further identified by including the material in quotations. Any material included in work submitted that is copied from other sources without giving credit for the source will result in a grade of F for the course.

Text:

Textbooks for CIS3300 and CIS3310 should be retained for reference in this course. Each student team will be expected to obtain a copy and read each of the following:

To earn a project grade of "C" a student team must successfully complete the following minimum requirements, which shall be demonstrated in both written reports and oral presentations to the complete satisfaction of the faculty and the client, plus excellent relations with the client throughout the duration of the project:

To earn a project grade of "A", a student team must successfully accomplish all the above, plus provide more functionality and better documentation than the minimum expected by the sponsor, the course Director and the faculty, plus excellent relations with the sponsor throughout the duration of the project.

Individual student grades will be allocated according to their contribution to their team's project, but in no event will a student get a grade higher than the project grade earned by the team.

    Deliverables:

    Software Projects: Prototype 50%, Reports 25%, Presentations 25 %
    Other project types: Documentation 50%, Presentations 50%

    Inputs: Course Director 50%, Project Sponsor 25%, Teammates 25%

CAUTION: Student are expected to conduct themselves in a manner that best exemplifies students in the University, the CIS Department, and CIS 4980.