Standards - Page 1 C# Suggested Standards to accompany the Project Evaluation Sheet 1. Project Performance a) Project works according to specifications. • Your project must follow the requirements outlined in the textbook assignment as well as any additional requirements assigned by your instructor. b) Output is accurate. • It is not enough to just produce output (displayed or printed). Your output must be complete and 100 percent accurate. c) Logic is efficient. • Use the most efficient logic that the textbook or your instructor has covered. Examples: Declare and use appropriate variables for calculations. Use switch rather than if……else when appropriate. d) Meets all requirements. • Follow any special rules and requirements of your instructor. 2. Disk Storage a) Folder name and file names match those listed above. • Fill in the top of the Project Evaluation Sheet, including the name of the folder where the project exists and the name of the .sln file for the project. The names you enter must exactly match those found on the diskette, including correct spelling and punctuation. b) Folder contains all necessary project files (no extra files). • A folder on diskette was created specifically for this project. The folder must contain all of the project’s files. Files unrelated to the project should be moved or deleted. c) Project runs as submitted. • Make sure that the project compiles and runs correctly from the diskette that you submit. Problems can occur when any of the project’s files are not stored in the project’s folder. If your project cannot locate a required file - your project will not run! • Test the project; make sure to test it on a computer other than the one on which you wrote it. 3. User Interface a) Professional appearance. • Designing the user interface is a critical component in the project’s construction. Anything that will appear on the screen for the user (forms, message boxes, etc.) must be presented in a professional format. The screen design should be easy to understand and “comfortable” for the user. • Use correct spelling and punctuation. • Name the form and change the Text property. The Text property appears in the form’s title bar. • Set the location on the screen for your form to appear. • Make sure that any text on the form displays completely, during both design time and run-time. b) Follows Windows standards. • Follow industry standards in relation to color, size, and placement of controls. (Refer to Chapter 2, “Designing the User Interface.”) c) Keyboard access keys (& in Caption, one button set as default, another as cancel). • Use keyboard access for all buttons and menus. For some assignments, you will also be required to include access keys for text boxes, radio buttons, and check boxes. • Follow industry standards whenever possible; use the X of Exit, and the S of Save. • Do not give two controls the same access key. • Set one command button as the default button (it will respond when the user presses the Enter key), and set one command button as the cancel button (it will respond when the user presses the ESC key). Be aware that some users are accustomed to pressing the Enter key instead of using the Tab key to jump to the next field. d) Tab order is correct. • Make sure the focus is on the correct object when a form displays. The tab order must proceed correctly when the user presses the Tab key.Standards - Page 2 4. External documentation a) Professional presentation. • The folder, label, and printout must be neat. The entire project must look professional. • Use a folder with three prongs. Fasten the pages into the folder. • Write your name and the project number on a label on the front of the folder. This information must be visible without opening the folder. • Include a Project Evaluation Sheet, with the student information completed, as the first page in your folder. • Use divider tabs to separate the contents of the folder. Label the divided sections in the folder as listed below, and in this order: Note: These requirements are for each form in the project. 1) Interface Plan------ Sketch of the interface showing object names and what they will display. 2) Properties Plan---- List the properties and settings for each object on the form. The list should contain three columns: Object Name, Property, Setting. 3) Code Plan ---------- Pseudocode or flowchart for each event procedure. 4) Form Image-------- Graphical version of the form printed (press the PrintScreen button on the keyboard and paste the screen capture into a word processor) 5) Code----------------- Source listing printed from File/Print. 6) Printer Output ----- Output produced from statements located in an event procedure ---------------------------- (if required by project – Printing is discussed in Chapter 7). NOTE: Requirements may vary, depending on instructor preference. • Your disk must be securely attached to the folder. (You can create a disk pocket on the inside back cover of the folder.) b) Folder: outside label, evaluation sheet, divider tabs, and disk securely attached. c) Printout of all forms, form text, and code. 5. Standards and conventions a) Object names. • Do not keep the default names assigned by .NET , such as Command1 and Label3. The exception to this rule is for labels that never change during project execution. These labels usually hold items such as titles, instructions, and labels for other controls. • Use good, consistent names for objects. • Begin object names with the correct prefix, in lowercase. (Refer to Chapter 1, “Naming Rules and Conventions for Objects.”) • Object names with multiple words should have the first character of each word capitalized. Examples: lblSalesTax and txtLastName. • Do not name your objects with numbers. • Object names must begin with a letter. The name can contain letters, digits, and underscores. An object name cannot include a space or punctuation mark. • As a general rule, don't abbreviate. If you wish to abbreviate very long names, you may do so. But use long enough names to be easily understandable and be consistent. b) Identifiers for Variables and Named Constants. • Follow the textbook's standards and conventions when naming (identifying) your variables and constants. (Refer to Chapter 3, “Naming Conventions.”) • Variables: