Architecture

To-Dos Modules <DPL>category=Module count=2</DPL> ... Analysis <DPL>category=Analysis count=2</DPL> ... Efforts <DPL>category=Effort category=Architecture count=2</DPL> ... Specifications <DPL>category=spec category=Architecture count=2</DPL> ... Proposals <DPL>category=Proposal category=Architecture count=2</DPL> ... Visions <DPL>category=Vision category=Architecture count=2</DPL> ...

As most of you know, OOo is a complex and big software system. Many lines of code are implemented in various programming languages, including BASIC, C, C++, Java, and more (perl, make, ANT, ...), if one counts the build system or tests as being part of OOo. Obviously, it is necessary to follow some kinds of guidance, rules, principles or constraints, to make it work seemingly and to make it understandable. Wikipedia gives a good understanding, of what a Software Architecture can or should be.

OpenOffice.org Software Architecture