Difference between revisions of "Architecture"
m (→Specifications: Fixed Specifications list.) |
m (Relativated lists to "Architecture" .) |
||
Line 10: | Line 10: | ||
==Analysis== | ==Analysis== | ||
<DPL>category=Analysis</DPL> | <DPL>category=Analysis</DPL> | ||
− | ==Architectural | + | ==Architectural To-Dos== |
− | <DPL>category=Architecture</DPL> | + | <DPL>category=To-Do |
+ | category=Architecture</DPL> | ||
==Efforts== | ==Efforts== | ||
− | <DPL>category=Effort</DPL> | + | <DPL>category=Effort |
+ | category=Architecture</DPL> | ||
==Specifications== | ==Specifications== | ||
<DPL>category=Spec | <DPL>category=Spec | ||
category=Architecture</DPL> | category=Architecture</DPL> | ||
− | |||
==Proposal== | ==Proposal== | ||
− | <DPL>category=Proposal</DPL> | + | <DPL>category=Proposal |
+ | category=Architecture</DPL> |
Revision as of 17:22, 29 January 2007
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
Implementation Modules
<DPL>category=Module</DPL>
Module Tests
<DPL>category=ModuleTest</DPL>
Analysis
<DPL>category=Analysis</DPL>
Architectural To-Dos
<DPL>category=To-Do category=Architecture</DPL>
Efforts
<DPL>category=Effort category=Architecture</DPL>
Specifications
<DPL>category=Spec category=Architecture</DPL>
Proposal
<DPL>category=Proposal category=Architecture</DPL>