PolyTraceAid
Rickychien (Talk | contribs) |
Rickychien (Talk | contribs) |
||
| Line 30: | Line 30: | ||
==[[PolyTraceAid_Tutorial | Tutorial]]== | ==[[PolyTraceAid_Tutorial | Tutorial]]== | ||
| − | |||
| − | |||
==[[PolyTraceAid_Improvements&Problems | Improvements and Problems]]== | ==[[PolyTraceAid_Improvements&Problems | Improvements and Problems]]== | ||
Revision as of 15:42, 10 July 2014
This Cartoon is cited from Tech Comic [1]
Contents |
Introduction
Welcome to the homepage of PolyTraceAid !!!
PolyTraceAid is an internal program documentation tool developed at
Object-Oriented Technology Lab (OOTL)
Computer Science and Information Engineering
National Central University
ZhongLi, TAIWAN
Programmers:
Supervisor: Yung-Pin Cheng [4]
PolyTraceAid is an authoring tool based on the debugging break points.
In practice, a source-level debugger is a powerful tool for program comprehension because using a debugger allows you to see the output of the program, watch the variables and their value changes during the run, and browse the source code at the same time.
We suggest that an internal program document can be composed from several trace cases in PolyTraceAid.
A trace case is a sequence of break points which can capture a control flow of a program run, typically designed to run an example which can go through the components which an author wants to explain.
A break point in a trace case is called a trace point.
Typically, a trace point is placed at a program statement from which an author expects to explain things. At a trace point, an author may link a document of arbitrary forms.
Multimedia documents such as PowerPoint slides or voice recordings are particularly recommended for this procedure.
