| [901] | 1 | <html>
|
|---|
| 2 | <BODY BACKGROUND="../icons/backg.jpg">
|
|---|
| 3 | <BR>
|
|---|
| 4 | <H1 ALIGN="CENTER"> <IMG SRC="http://cern.ch/geant4/images/g4_small.gif" ALT="GEANT4"> </H1>
|
|---|
| 5 | <H1 ALIGN="CENTER">Object Oriented</H1>
|
|---|
| 6 | <H1 ALIGN="CENTER">Analysis and Design</H1>
|
|---|
| 7 | <p>
|
|---|
| 8 | <p>Geant4 exploits advanced software engineering techniques based on the Booch/UML
|
|---|
| 9 | Object Oriented Methodology and follows the evolution of the ESA Software Engineering
|
|---|
| 10 | Standards for the development process. The "spiral" (iterative) approach has
|
|---|
| 11 | been adopted; <A HREF="URD.pdf">User Requirements</A> were collected in the initial phase and Problem
|
|---|
| 12 | Domain Decomposition, Object Oriented Methods and CASE tools have been employed
|
|---|
| 13 | for the Analysis and Design, giving a clear <a href="class_category_diagram/architecture.html">hierarchical
|
|---|
| 14 | structure</a> of sub-domains linked by a uni-directional flow of dependencies.
|
|---|
| 15 | This leads to a software product which is modular and flexible (a toolkit) and
|
|---|
| 16 | in which the physics implementation is transparent and open to the user validation
|
|---|
| 17 | of the physics predictions. It allows the user to understand, customise
|
|---|
| 18 | and extend the toolkit in all the domains; at the same time the modular architecture
|
|---|
| 19 | allows the user to load only needed components.
|
|---|
| 20 | <h2 align="left">Analysis Documents</h2>
|
|---|
| 21 | <ul>
|
|---|
| 22 | <li><A HREF="analysis/class_diags/index.html">Class diagrams</A>
|
|---|
| 23 | <li><A HREF="analysis/class_spec/index.html">Class specifications</A>
|
|---|
| 24 | <li><A HREF="analysis/scen_diagrams/index.html">Scenario diagrams</A>
|
|---|
| 25 | </ul>
|
|---|
| 26 | <h2 align="left">Design Documents</h2>
|
|---|
| 27 | <ul>
|
|---|
| 28 | <li>Class category diagram
|
|---|
| 29 | <ul>
|
|---|
| 30 | <li><a href="class_category_diagram/architecture.html">Architecture</a>
|
|---|
| 31 | (also available as <a href="class_category_diagram/architecture.ps">Postscript</a>)
|
|---|
| 32 | </li>
|
|---|
| 33 | <li><a href="class_category_diagram/detailed.ps">Details</a> including sub-categories
|
|---|
| 34 | (only as Postscript) </li>
|
|---|
| 35 | </ul>
|
|---|
| 36 | </li>
|
|---|
| 37 | <LI><A HREF="design/class_diags/index.html">Class diagrams</A>
|
|---|
| 38 | <LI><A HREF="design/class_spec/index.html">Class specifications</A>
|
|---|
| 39 | <LI><A HREF="design/scen_diagrams/index.html">Scenario diagrams</A>
|
|---|
| 40 | </ul>
|
|---|
| 41 | <hr>
|
|---|
| 42 | <i>Tuesday, 8 October 2002
|
|---|
| 43 | - <i><a href="http://consult.cern.ch/xwho/people/20341">GC</a>,
|
|---|
| 44 | <a href="http://consult.cern.ch/xwho/people/1342">GF</a></i>
|
|---|
| 45 | </body>
|
|---|
| 46 | </html>
|
|---|
