An Object-Oriented Information Architecture for Borland C++ 3.0
Preserved & Archived for wholeo.net
In 1991–1992, as a technical writer in Silicon Valley documenting Borland C++ 3.0, I proposed an innovative approach to technical documentation: rather than presenting software through standard linear hierarchies or manuals, I designed an Object-Oriented Information Architecture that mirrored the language's own concepts of classes, inheritance, encapsulation, and derived subclasses.
At one point I see a call for papers for the Borland Language Conference. I write up a proposal of how to visualize this new information based on stuff I'd like to do in the manual but there's no time.
This week Greg (my boss) has a meeting and gives us new assignments. When he gets to me he says, "I liked your proposal for the conference and I think that's something we need. Make that your job. And redesign the way we present our software environment for all the books." I found my face flooded with pleasure and surprise. He took my idea and saw larger implications for it.
Because this is definitely a highly creative task. I'm thrilled because I'm in a position to really do something creative that could directly impact people's lives and even be history. It's something that doesn't exist, that people need and want...
What I propose is to diagram the system in an object-oriented way, instead of a hierarchical way. And then use that method to diagram templates. Templates is a way of representing data for the computer that is the cutting edge of C++. It was created by AT&T Bell labs as an idea, but Borland is the first company to put it in their product. As far as we know, it's the only or best solution to managing large amounts of data, which is coming up for everyone.
Although the project was created in graphics form in 1992, standard visual modeling languages like UML did not yet exist. The project was reviewed, rejected, and later preserved in personal archives. Today, it stands as a unique historical artifact of early hypermedia design and pre-UML domain modeling.
Click on any diagram below to view the original scan and detailed structural breakdown.
{Wholeo Online} ~ {Trips} ~ {Art} ~ {Silicon Valley}