Home

{{CS-000}} Course Wiki

Welcome to the {{CS-000}} Course Wiki! Select the wiki page that best matches the information or help you need.

Common Course Resources

• Tech Stack — Learn how to setup and use the languages, platforms, frameworks, course IDE (Integrated Development Environment), and other development tools used in the course.

• Industry Standards — Find the required coding, pseudocode, diagram, documentation, and file-organization conventions.

• Best Practices — Review recommended professional approaches, including the SDLC (Software Development Life Cycle), testing, documentation, and version control.

Industry Standards

The Industry Standards page explains the required conventions used throughout the course.

These standards are based on formal standards, published style guides, and widely used professional conventions. Some have been adapted for an academic environment so that students can learn and apply them consistently.

Course standards may address:

• Source-code style
• File and folder organization
• Naming conventions
• Pseudocode
• Flowcharts and other diagrams
• Documentation
• Testing
• Git and GitHub use

A style guide defines conventions for writing and formatting work consistently. When a course standard is included in an assignment or rubric, treat it as a requirement.

Best Practices

The Best Practices page presents recommended approaches for planning, developing, testing, documenting, and improving your work.

A best practice is an approach that professionals commonly use because it generally improves quality, reliability, readability, security, or maintainability. A best practice becomes an assignment requirement when it is included in the task instructions or rubric.

This page may include guidance about the SDLC (Software Development Life Cycle). The SDLC is a structured process for planning, analyzing, designing, developing, testing, deploying, and maintaining software.

Best practices may also include:

• Breaking large problems into smaller steps
• Developing and testing incrementally
• Using clear names and simple logic
• Saving and committing work regularly
• Reviewing requirements before submission
• Documenting design decisions
• Asking for help early

Help and Support

Use the appropriate support resource based on the type of help you need.

Academic Support

Use Academic Support for help with:

• Course concepts
• Assignment requirements
• Programming logic
• Pseudocode and diagrams
• Debugging approaches
• Study skills and tutoring

Academic support can help you understand and apply course concepts, but it should not complete graded work for you.

Technical Support

Use Technical Support for problems involving:

• Account access
• Course software installation
• Codio or virtual-lab access
• Git or GitHub configuration
• Files, permissions, or operating-system issues
• Development tools that will not open or run

When requesting help, include the course and task number, the exact error message, what you expected to happen, what happened instead, and what you have already tried. Do not share passwords, authentication codes, private keys, or other sensitive information.