Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you are nesting 6 levels, you're probably artificially mixing multiple concerns. See below for the 5D model. It looks like you should be using namespace-class-method as the basic navigation model. You are at least mixing code structure with its organisation on disk (files and folders) and the mapping to variants. Smalltalk IDEs like <a href="http://pharo-project.org" rel="nofollow noreferrer">Pharo</a> provide a set of code browsers making navigation easy along a few dimensions, and provide a browser construction kit <a href="http://www.themoosebook.org/book/internals/glamour/" rel="nofollow noreferrer">Glamour</a> to make your own for other navigation dimensions.</p> <p>You'll want to take a look at the work done by Richard Wettel. Something similar to <a href="http://www.inf.usi.ch/phd/wettel/codecity.html" rel="nofollow noreferrer">Codecity</a>. Using OpenGL to create a 3- and 4D (time) display of the development history of a project. It is part of the research in software reengineering <a href="http://www.moosetechnology.org/" rel="nofollow noreferrer">MOOSE</a>.</p> <p>For your research you might want to use the 5 dimensional model for this:</p> <ul> <li>version (wanting to change)</li> <li>status (life cycle: creating, testing, deploying, retiring)</li> <li>view (requirement, code, test, documentation)</li> <li>hierarchy (module, class, method)</li> <li>variant (largely similar, describing the differences, product families)</li> </ul> <p>Most systems only handle a few of these dimensions. To handle all five, you have to describe (fix) your development process. If you do, you can describe the use cases you want to support in your UI. If not, you need a 5-dimensional flexible display engine. That will not be as easy to use.</p> <p>The reference:</p> <p><em>Managing design data: the five dimensions of CAD frameworks, configuration management, and product data management.</em><br> van den Hamer, P. Lepoeter, K.<br> Philips Res., Eindhoven; </p> <p>This paper appears in: <em>Proceedings of the IEEE</em><br> Publication Date: Jan 1996<br> Volume: 84, Issue: 1<br> On page(s): 42-56<br> ISSN: 0018-9219<br> References Cited: 26<br> CODEN: IEEPAD<br> INSPEC Accession Number: 5175049<br> Digital Object Identifier: 10.1109/5.476025<br> Current Version Published: 2002-08-06 </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload