Term Project - Software
The project must contain a strong research component directly related
to the topics covered in the course (i.e., software visualization).
In many cases the development of a prototype software system to
test and/or demonstrate
your concept will form a large part of the project. Other
involve the investigation of specific visualization techniques for a
problem, an in-depth survey to achieve a specific research goal,
of existing taxonomies that describe aspects of software visualization,
A project proposal is required and must be completed before midterm
(see schedule for specific date). Topics will arise from in
class discussion and students can meet with me to formalize ideas and
topics. Of course, the student must become familiar with the
general topic of software visualization, via the first 3-4 weeks of
course, before any concrete project topics can be defined.
- The format of the
final project report will be in IEEE 2 column proceedings format (with one change - citations will
- Length should be
approximately 10 pages
- Citations must be
complete, accurate, and meet typical ACM/IEEE standards and guidelines
- I have a MS Word
(dot) for IEEE 2 Column. The styles are defined with examples and
instructuions. See IEEE-2Column-Template under http://www.sdml.info/library/library%20and%20styles/
- I highly recommend
a bibliography/citation tool.
- The tool I use is Endnote
. They have a free trial version. This is a plugin to
that makes doing the references and bibliography much
simpler. The full version from the bookstore is around $100
for KSU students.
- KSU has an
agreement with RefWorks.
All KSU students and staff can use this service for free. This is
a tool much like Endnote but is served online. There are plugin's
for MSWord and other tools. For instructions see the KSU Library (see
"What's new" on the left)
- If you use LaTeX
then you'll want to use BibTex.
- There is an
library for my research Lab under the above address - sdml_library.enl
- I have also
citation and bib formats, the ens files. I would suggest using
AuthorYear.ens or MultiAuthorYear.ens for your reports.
- Visualization of Version Control information (i.e., change
histories) For example visualize what
types of changes occurred to what files and when (could use sv3D)
- Visualization of source code clones – for detecting and/or
- Visualizing refactorings
- Visualizing patterns
- Physical-view to logical-view coordination as needed. Maps classes to files to support project
refactorings, for example.
- Visualizing merging and differencing (e.g., a MS Word “track
changes” for source code)
- Graph layout with respect to UML class diagrams and
architectural importance (e.g., control, boundary, entity, or patterns)
- VR and software visualization (IMSOvision style
- Survey/study of SE tasks supported by software visualization
- Document/Table lens or fisheye for source code viewing
- Alternative views of source code. Examples:
literate programming, table view of
classes, class browser, etc.
- 3D UML
- Use eye-tracking equipment (Dr. Khan’s) to assess a software
- A visualization tool to support source code walkthroughs or