Difference between revisions of "Intro Week 1 JL"
Line 6: | Line 6: | ||
Analyze the problem | Analyze the problem | ||
+ | |||
What are the intended outputs? What are the required inputs? How does the program flow? | What are the intended outputs? What are the required inputs? How does the program flow? | ||
Design the solution | Design the solution | ||
+ | |||
Using flow charts and/or pseudocode, outline the solution. Be sure to use modularity in your design. | Using flow charts and/or pseudocode, outline the solution. Be sure to use modularity in your design. | ||
Code the solution | Code the solution | ||
+ | |||
Based on the outlined solution, write the individual modules, testing each one with a driver and then combining them into your final program. | Based on the outlined solution, write the individual modules, testing each one with a driver and then combining them into your final program. | ||
Build | Build | ||
+ | |||
Using your Integrated Development Environment (IDE), compile the project and/or individual modules. Eliminate syntactical errors. | Using your Integrated Development Environment (IDE), compile the project and/or individual modules. Eliminate syntactical errors. | ||
Test | Test | ||
+ | |||
Run the program to test its logic. Is the output correct under various situations? Use good and bad data entry to prove that the application is user-proof. Does it solve the problem? Does it perform according to the specifications? | Run the program to test its logic. Is the output correct under various situations? Use good and bad data entry to prove that the application is user-proof. Does it solve the problem? Does it perform according to the specifications? | ||
Document | Document | ||
+ | |||
Although documentation should have been done during the above process, be sure that it is complete, for both users and programmers. | Although documentation should have been done during the above process, be sure that it is complete, for both users and programmers. | ||
Update and Enhance | Update and Enhance | ||
+ | |||
Programs have lives of their own. How can this one be improved with age? | Programs have lives of their own. How can this one be improved with age? | ||
Revision as of 21:15, 18 January 2012
Week One
Part I
The Program Development Process
Analyze the problem
What are the intended outputs? What are the required inputs? How does the program flow?
Design the solution
Using flow charts and/or pseudocode, outline the solution. Be sure to use modularity in your design.
Code the solution
Based on the outlined solution, write the individual modules, testing each one with a driver and then combining them into your final program.
Build
Using your Integrated Development Environment (IDE), compile the project and/or individual modules. Eliminate syntactical errors.
Test
Run the program to test its logic. Is the output correct under various situations? Use good and bad data entry to prove that the application is user-proof. Does it solve the problem? Does it perform according to the specifications?
Document
Although documentation should have been done during the above process, be sure that it is complete, for both users and programmers.
Update and Enhance
Programs have lives of their own. How can this one be improved with age?
Part II
Introduce Visual Studio
Part III Hello World Console Program
Programming assignment
• Two Name Hello Write a console program called Hello that asks the user to input his or her first and last name and outputs the message “Hello, firstname lastname”. Use string FName and LName to create the variable. Document. Hint: Output code looks like this: “Hello, “ + FName + “ “ + LName + “.”