A4.1 demonstrate the ability to identify and correct syntax, logic, and run-time errors in computer programs;
A4.2 use workplace and professional conventions (e.g., naming, indenting, commenting) correctly to write programs and internal documentation;
A4.3 demonstrate the ability to interpret error messages displayed by programming tools (e.g., compiler, debugging tool), at different times during the software development process (e.g., writing, compilation, testing) ;
A4.4 use a tracing technique to understand program flow and to identify and correct logic and run-time errors in computer programs; A4.5 demonstrate the ability to validate a program using a full range of test cases.
A4.5 demonstrate the ability to validate a program using a full range of test cases.
B1.2 demonstrate the ability to solve problems independently and as part of a team;
B3.3 design algorithms to detect, intercept, and handle exceptions (e.g., division by zero, roots of negatives).
B4.1 describe the phases (i.e., problem definition, analysis, design, writing code, testing, implementation, maintenance), milestones (e.g., date of completion of program specification), and products (e.g., specification, flow chart, program, documentation, bug reports) of a software development life cycle;
A boolean expression is the heart of decision making and gives your program the ability to adapt when it needs to!
Here is a list of problems that MUST be solved using some kind of decision structure. Choose a problem that no one else has picked and enter it into the spreadsheet. Do not wait until the last minute. Also, you cannot do a problem that we have already done in class.
If you are not sure on any part of the problem, just ask me and I will give you additional information.
complete the assignment section in Hãpara Workspace for this day
if Hãpara is not working, make a copy of this document
move it to your IMH-ICS folder for this course
See the rubric for more information.