Senior Projects

Appearance

Charleston Southern University
Charleston Southern University

Syllabus | CSCI 497 Senior Project Design ​

General Information ​

Department: Computer Science
Course Name: Senior Project Design
Course Number: CSCI 497
Credit Hours: 1
Approved Major Credit: BS in Computer Science, BS in Cybersecurity, and BA in Applied Computing
LAC Requirement: None
Prerequisites: Permission of the instructor

Course Description ​

Senior Project Design is the first of a project-based capstone series for the Computer Science degree program. Students will complete the planning, scheduling, and design of a significant project in the field of Computer Science. Upon completion of CSCI 497 Senior Project Design, the student may progress to CSCI 498 Senior Project Construction.

Course Materials ​

Additional Materials for Learning

  1. Computer with basic audio/video output equipment
  2. Internet access
  3. A GitHub Account

ABET Student Learning Outcomes ​

The following student outcomes are to be supported by this coursework:

  1. An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs.

  2. An ability to communicate effectively with a range of audiences.

  3. Recognize professional responsibilities and make informed judgments in computing practice based on legal and ethical principles.

Grading ​

ObjectiveGrade Weight
Proposal60%
Requirements Specification40%

Objectives and Tasks ​

The student must produce a multi-page proposal document and a software requirements specification.

Course Schedule ​

The deadline to submit the final proposal is noon two weeks before the last day of classes. The proposal is then reviewed by your project advisor and accepted/rejected by the CSCI faculty. Draft proposals are expected to be submitted to the project advisor for review before the final proposal due date.

Proposal ​

The proposal will contain the following information:

  • Student Name 👩👨

  • Degree and Major 💻🔑

  • Project Advisor Name 👵👴

  • Expected Graduation Date 📅🏁

  • Problem Statement 💡
    The problem statement should be one or two concise and formal paragraphs containing the following:

    1. Describe the “ideal” state of affairs.
    2. Explain the problem.
    3. Explain why the problem is important.
    4. Back up your assertions.
    5. Propose your solution (without details).
    6. Explain the benefits of the solution.
    7. Conclude by summarizing the problem and solution as your thesis statement.

    Use this wikiHow article for details.

  • Project Description 📱

  • Proposed Implementation Language(s) 🐍☕🎯

  • Libraries, Packages, Development Kits, etc. to be used in the proposed implementation languages(s) 🔧

  • Additional Software/Equipment Needed 💻🕹️📱

  • Alternative Solutions and Rationale 🔍

  • Personal Motivation 🍰
    Describes how this project will further the student’s knowledge in the field.

  • Outline of Future Research Efforts 📚🚀🧪
    Describes how the student will complete his/her project. What deliverables can be expected?

  • Schedule 📆 ⌚
    A list of expected dates various tasks will be completed and deliverables will be submitted to the faculty advisor for CSCI 498 and 499

Requirements Document ​

The goal of this assignment is to produce a high-quality Software Requirements Specification (SRS) using the Volere approach, with particular emphasis on writing clear, testable requirements with well-defined fit criteria. This document should describe what the system must do and how well it must do it, without prescribing implementation details.

The requirements will be of the appropriate subset of the types listed below. For more details about these types and to help generate requirements ideas, request a free educational copy of the Volere Requirement Specification Template.

Scope and Quantity ​

Your requirements document must contain 20 – 50 total requirements that, taken together, provide a complete and coherent description of the system.

  • Do not inflate the count with trivial or redundant requirements.
  • Each requirement should represent a distinct, necessary stakeholder need.
  • A mix of functional and non-functional requirements is expected.

Requirement Types ​

Your requirements should be drawn from an appropriate subset of the following Volere requirement types. You are not required to use every type, but you should justify the overall balance based on the nature of your system. There will be more functional requirements than any other type.

  1. Functional

  2. Look and Feel

    1. Appearance
    2. Style

  3. Usability

    1. Ease of Use
    2. Personalization and Internationalization
    3. Learning
    4. Understandability and Politeness
    5. Accessibility
    6. Convenience

  4. Performance

    1. Speed and Latency
    2. Safety-Critical
    3. Precision or Accuracy
    4. Reliability and Availability
    5. Robustness or Fault-Tolerance
    6. Capacity
    7. Scalability or Extensibility
    8. Longevity

  5. Maintainability and Support

  6. Security

    1. Access
    2. Integrity
    3. Privacy
    4. Audit (The information must be recorded to allow security checks, e.g., logs)
    5. Immunity

  7. Cultural

Requirement Specification ​

Each requirement will contain at least the following information.

  1. ID Number
    A unique identifier (e.g., FR-01, US-04, SEC-02).

  2. Type
    One of the requirement types listed above.

  3. Description
    A clear, concise statement of what is required.

    • Avoid vague terms such as fast, user-friendly, or secure unless they are clarified by the fit criterion.
    • Avoid describing implementation or design unless explicitly required.

  4. Rationale
    A brief explanation of why this requirement exists.

    • Identify the stakeholder need, business goal, or risk it addresses.

  5. Fit Criterion (Critical)
    A measurable and testable condition that defines how success will be determined.

    • Ask: How would a tester objectively verify that this requirement has been met?

    • Fit criteria may involve thresholds, limits, frequencies, error rates, or test outcomes.

    • If a requirement cannot be tested, it is not yet complete.

  6. Priority
    An indication of importance (e.g., High / Medium / Low, or Must / Should / Could).

  7. Dependencies
    The ID(s) of any other requirement(s) that must be satisfied before this one can be implemented or verified (if applicable).

Quality Expectations ​

High-quality requirements are:

  • Precise – stated clearly, with no unnecessary wording

  • Unambiguous – interpreted the same way by all readers

  • Testable – validated through the fit criterion

  • Describe real needs – traceable to a real stakeholder or system need

  • Solution-independent – focused on what, not how

You should assume that your document will be used by developers, testers, and project managers who were not involved in writing it.

Attendance ​

The student is expected to schedule a meeting with the project advisor within the first full week of the class. During this initial meeting, the attendance policies will be discussed and meeting times will be scheduled between the student and advisor.

Course, Department, and University Policies ​

Academic Integrity and the Honor Code ​

All students are expected to adhere to Charleston Southern University's Academic Integrity Policy and the Computer Science Departmental Guidelines. For example, all work must be original and must not be copied from another student. Failure to follow this guideline will be considered a violation of the code and will be treated accordingly. Students are encouraged to ask their instructor(s) for clarification regarding their academic dishonesty standards.

AI Policy for CSCI 497 ​

Level 1. Use of generative AI is prohibited in this course.

To ensure development and mastery of the concepts and skills in this course, the use of generative artificial intelligence (AI) tools is prohibited. Students who are unsure of this policy or any assignment-specific directions, including whether a given technology is considered AI, should consult the course instructor before using such technology to complete their assignment.

While proper AI use is an important skill that will be emphasized in other courses, AI misuse short-circuits the learning process to give the illusion of proficiency without the necessary depth. It is unethical to take full credit for work created with the help of AI. This principle is the same as using someone else’s idea without citing it.

Review the departmental policies for AI use in Computer Science coursework.

Course Evaluations ​

To pursue our mission of Academic Excellence in a Christian Environment, we must receive feedback from students. The student-feedback survey is online and will be available to students in the second half of the semester. Students are strongly encouraged to complete the short evaluation survey, which is anonymous. Your professor will let you know when the survey is available. The survey will be available through your MyCSU account. We greatly value your opinion!

Student Representatives ​

These are students who are designated by letter to represent the University in official business (e.g., athletic, music, and similar events). If officially scheduled absences cause these students to miss tests, assignments, or similar academic activities, university policy allows these to be made up without penalty. Student Representatives may opt to either make-up tests before departure or supplant missed tests with the final exam grade. Final exams must always be taken before departure to avoid an Incomplete for the course. Scheduled assignments remain subject to the lateness policy and must be turned in before departure to avoid lateness penalties. Student Representatives are responsible for informing the instructor of official absences and to make all appropriate arrangements.

Internet Etiquette ​

Charleston Southern University (CSU) holds students, faculty, and staff to the highest standards of conduct and expects all to demonstrate courteous behaviors and practices in online communications. This policy includes guidelines and recommendations for online communications. Being respectful, thoughtful, meaningful, and ethical are fundamental to good netiquette.

CSU's basic netiquette rules are:

  • Course communications are for internal use only and are considered confidential. Do not forward or quote discussion posts, emails, or other course communications to outside parties.
  • Never share personal login usernames, IDs, or passwords.
  • Do not type in all capital letters. It is perceived online as shouting.
  • Use proper capitalization, grammar, spelling, and punctuation conventions for professional communications.
  • Avoid texting jargon or abbreviations without explanation.
    • Incorrect: "CSU is a wonderful university."
    • Correct: "Charleston Southern University (CSU) is a wonderful university."
  • Be mindful of sending emails. Ensure that content is relevant and pay attention to Reply versus Reply All.
  • BucMail is the only email allowed for course communications. Other platforms (Yahoo, Gmail, etc.) are prohibited.
  • In video conferencing, mute your microphone when not speaking.
  • Differing views are natural and welcome in discussion boards. Be respectful in your comments - even if you disagree or dislike someone's position on a topic.
  • Respect the time and availability of students, faculty, and staff. Emails should be addressed within 24 hours of receipt. Keep in mind that traditional faculty work hours are 8 a.m. - 5 p.m. EST.

Accessibility Services ​

Any student who may need accommodations should review the requirements/procedures on the Accessibility Services website. Once approved to receive accommodations, the student must contact the instructor.

Title IX: Confidentiality and Responsible Employee Statement ​

Charleston Southern University is committed to maintaining a safe learning environment for everyone. In accordance with Title IX of the Education Amendments of 1972, the university prohibits any form of sexual harassment, including quid pro quo harassment, hostile environments, sexual assault, dating/domestic violence, and stalking. This policy applies to all students, employees, and visitors.

Additionally, Title IX prohibits discrimination against students based on pregnancy, childbirth, false pregnancy, termination of pregnancy, or recovery from these conditions. Pregnant or parenting students may receive accommodations to ensure their full participation in educational programs. These adjustments can be arranged through the university’s Title IX Coordinator or their designee.

Under Charleston Southern University’s Title IX Policy, all faculty members, including teaching assistants, are required to report any disclosures of sex or gender-based discrimination or violence to the Title IX Coordinator. The Title IX Coordinator will provide support and resources while maintaining privacy. If you or someone you know needs assistance, please contact the Title IX Coordinator: Shannon Morrison or the deputy Title IX Coordinator Justin Brown. Email: titleix@csuniv.edu

Please visit the CSU Title IX webpage for more information on Title IX procedures, anonymous reporting, or available support. You may complete an incident report using the form on the title-ix website.

See all course, department, and university policies located in Blackboard and the CSU Student Handbook.