What This Document Is
This guidance provides a set of standards and best practices specifically tailored for students undertaking application development projects using Visual Basic within the ITE-370 course at the University of South Alabama. It outlines expectations regarding code quality, documentation, and project submission procedures. Think of it as a comprehensive style guide designed to ensure consistency and professionalism in your programming work. It’s geared towards helping students produce maintainable, understandable, and correctly functioning applications.
Why This Document Matters
This resource is essential for any student enrolled in ITE-370 who is working on Visual Basic programming assignments. Following these guidelines will significantly improve your grade by demonstrating a commitment to professional software development practices. It’s particularly useful when you’re unsure about specific formatting requirements, commenting standards, or acceptable components to use in your projects. Refer to this guidance throughout the entire development lifecycle – from initial planning to final submission – to avoid common pitfalls and ensure your work meets the instructor’s expectations.
Common Limitations or Challenges
This guidance focuses on *how* to approach Visual Basic programming within the context of this course, but it doesn’t provide in-depth tutorials on the Visual Basic language itself. It assumes a foundational understanding of VB concepts and syntax. It also doesn’t offer specific solutions to programming problems or detailed explanations of algorithms; rather, it sets the framework for *how* you should implement those solutions. It’s a set of rules and recommendations, not a substitute for learning the language.
What This Document Provides
* Detailed expectations for code commenting and programming style.
* Guidelines for naming conventions for variables and objects.
* Instructions regarding permitted components and external resources.
* Specific requirements for project submission, including acceptable media and file organization.
* Information on avoiding penalties related to project loss or viruses.
* Recommendations for improving code readability and maintainability.
* Standards for identifying your work and ensuring proper attribution.
* Clarification on required printed materials for project turn-in.
