20 Oct Write a self-contained program in Visual C#. The subject and scope of the project are deliberately open ended to allow individuals to work on a project they find interesting and challeng
write a self-contained program in Visual C#. The subject and scope of the project are deliberately open ended to allow individuals to work on a project they find interesting and challenging.
Part-1: Program
Working alone, write a self-contained program in Visual C#. The subject and scope of the project are deliberately open ended to allow individuals to work on a project they find interesting and challenging. Some students will have something they really want to have the opportunity to program for class credit. This is your opportunity to program something related to your personal interests, hobbies, area of study, etc. If you want more guidance in choosing a project. Here are some things to think about:
· Games
· Tools .
· Storytelling
· Simulation
· Art
Part-2: Requirements:
Use these ingredients of effective programs at least once in your project:
• iteration (e.g. Use loops to do something repeatedly instead of manually doing the same thing repeatedly.)
• conditionals (e.g. If something happens, react one way; otherwise, react differently.)
• abstraction (e.g. Use a custom function to define a command that you reuse in multiple parts of your program.)
Part-3:Grading:
Your program must run. If your program crashes, you will receive a 0 point. This may sound extreme, but a program that doesn’t run is worthless, regardless of how much effort you’ve put into it. Almost all programming classes will hold you to this standard. To protect yourself, use incremental development. Only change one thing at a time, make sure the program works, then save your program with a new version number before making any new changes. This will keep you from finding yourself in the situation in which you break your program and can’t fix it by adding 1 more feature. You’ll just be able to go back a version to get something that works and submit the older version instead. Your logic must be sound. Your program should work as advertised. If it runs but it doesn’t do what it’s supposed to, you will get a lower logic score. If it runs properly most of the time, you will get a good logic score. If you go the extra mile and add extra safeguards so that it always works sensibly, even if the user uses it incorrectly, you can get a perfect logic score. You must use good style. Whenever you can simplify your program by using functions, loops, and conditionals, you should do so. You must document your code. Your program should be thoroughly commented.
· At the beginning of your program, explain what it does and provide a copyright notice with the year and your name.
· The first line of each function definition should explain what the function does.
· Before any block of code, explains what the block does.
· Explain any other lines of code whose function isn’t immediately obvious.
You must use sensible variable names. Your variable names should clearly communicate what the variable does. It’s ok to use a variable like x if you are dealing with an (x; y) coordinate system for drawing. It would be ok to use a if you were implementing the pythagorean theorem, because it’s standard to write c2 = a2 + b2 and it would be very clear what a was in the context of that equation. It would be confusing, however, to use x or a for something that isn’t somehow x-related or a-related. For instance, you wouldn’t want to use x if you were calculating the total price; you’d want to use something like totalPrice instead of an arbitrary letter. This makes your program more readable and it makes you less likely to make mistakes by mixing up similar arbitrarily named variables. Your program must be of an appropriate scope.
