Debugging A Small Application Essay
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Debugging A Small Application Essay
Assessment item 4
Asg 4 – Debugging
Value: 20%
Due date: 13-Oct-2017
Return date: 03-Nov-2017
Submission method options
Alternative submission method
Task
Assignment 4 revolves around debugging a small application. This is an individual assignment.
You will be provided with some code which contains several known bugs. The source code and initial bug reports will be made available in the Resources section of the subject’s Interact site.
Your task is to replicate, simplify, trace, and eliminate these bugs using best practice debugging techniques. Your debugging effort should take place within a version control system using appropriately sized, commented, and timely commits.
Please note that the focus in this assignment is on the process and techniques applied, not the complexity of the code. It is recognised that the process applied is ‘way over the top’ for the size of problem addressed.
Tasks
- Replication.
- For each of the reported bugs, generate a test case in UAT format that will reliably reproduce the buggy behaviour.
- Commit the test case documentation to version control.
- Simplification.
- For each of the reported bugs, produce a simplified and automated test that reliably reproduces the bug.
- Commit the test code demonstrating the bug to version control.
- Record output from your test, demonstrating the buggy behaviour.
- Tracing.
- For each of the reported bugs, trace back through the programs dependences from the point of failure to find the origin of the bug. Use a sequence of hypotheses and tests to support this search, and document this sequence in a debugging log.
- For each of the reported bugs, demonstrate that before the identified origin, variable values are ‘sane’ and that after the origin, at least one value is ‘infected’.
- Record screen shots demonstrating the origin of the bug.
- Resolution.
- For each of the reported bugs, correct the bug.
- Commit the corrected code to version control.
- Record output listings from your automated test demonstrating that the buggy behaviour has been eliminated.
- Carry out the user test case with the specified data and show that the buggy behaviour has been eliminated.
Submit:
- A word processed file containing:
- The URL for repository used for your debugging effort. Make sure you commit both at the start of the debugging process, once you have developed an automated test demonstrating each bug, and after you have resolved each bug.
Include a directory at the top of the file indicating where in your repository the files related to each debugging effort can be found.
- For each bug:
- The user tests (in UAT format) that demonstrate the bug. (specifying expected buggy output)
- Output from your automated test demonstrating the buggy behaviour.
iii. A debugging log recording the succession of hypotheses, tests, and results of those tests that you used to trace the origin of each bug.
- ‘Before’ and ‘after’ screen shots identifying the origin of the bug. (show variable values)
- Output from the automated test demonstrating correct operation after resolution of each bug.
- Test results from the user test you specified for each bug demonstrating correct operation.
Presentation
There are two aspects to the presentation of this assignment.
The first is a word processed file submitted through TURNITIN which contains:
- the URL for the version control repository where all code development and tests for the debugging assignment can be found.
- for each bug:
- the user test case for each bug
- the output from the automated test demonstrating the buggy behaviour
- your debugging log showing the sequence of hypotheses and tests leading to identification of the origin of the bug
- screen shots demonstrating the transition from sane to infected at the origin
- output showing resolution of the bug
The second aspect of the assignment is presented as a functional code repository containing the complete development history and code for the assignment. You should clearly comment the update which represents the point at which you submit the assignment.
It is critical that you do not delete the repository until after you have received your mark for thre assignment.
RUBRIC
Excellent Quality
95-100%
Introduction 45-41 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Literature Support
91-84 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Methodology
58-53 points
Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met.
Average Score
50-85%
40-38 points
More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided.
83-76 points
Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration.
52-49 points
Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met.
Poor Quality
0-45%
37-1 points
The background and/or significance are missing. No search history information is provided.
75-1 points
Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration.
48-1 points
There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow Debugging A Small Application Essay