dc.contributor |
Graduate Program in Computer Engineering. |
|
dc.contributor.advisor |
Akın, H. Levent. |
|
dc.contributor.author |
Şekerci, M. Erdal. |
|
dc.date.accessioned |
2023-03-16T10:06:14Z |
|
dc.date.available |
2023-03-16T10:06:14Z |
|
dc.date.issued |
2007. |
|
dc.identifier.other |
CMPE 2007 S45 |
|
dc.identifier.uri |
http://digitalarchive.boun.edu.tr/handle/123456789/12500 |
|
dc.description.abstract |
In software system development, the most important issue is to build a system that satisfies the requirements and works correctly. But even if a software system works correctly, this does not show that its source code is well-written. The source code may contain unnecessary codes, may have undetected bugs, or may not conform to the required coding standards or rules. This will make the code dirty and unreadable making it very difficult for other people (except the writer) to understand, update or analyze the source code. The motivation for this thesis underlies in this issue. The idea is to analyze a given source code and check it according to user defined flexible checker rules and coding standards (conventions). This could be useful in checking source codes in a variety of areas such as student projects in programming courses and deciding how good the source codes were written according to the defined rules of the checker. |
|
dc.format.extent |
30cm. |
|
dc.publisher |
Thesis (M.S.)-Bogazici University. Institute for Graduate Studies in Science and Engineering, 2007. |
|
dc.relation |
Includes appendices. |
|
dc.relation |
Includes appendices. |
|
dc.subject.lcsh |
Source code (Computer science) |
|
dc.title |
Flexible code checker |
|
dc.format.pages |
xiii, 116 leaves; |
|