| 1 |
|
\appendix |
| 2 |
< |
\chapter{\label{chapt:appendix}APPENDIX} |
| 2 |
> |
\chapter{\label{chapt:oopse}Object-Oriented Parallel Simulation Engine (OOPSE)} |
| 3 |
|
|
| 4 |
|
Designing object-oriented software is hard, and designing reusable |
| 5 |
|
object-oriented scientific software is even harder. Absence of |
| 6 |
|
applying modern software development practices is the bottleneck of |
| 7 |
< |
Scientific Computing community\cite{Wilson}. For instance, in the |
| 8 |
< |
last 20 years , there are quite a few MD packages that were |
| 7 |
> |
Scientific Computing community\cite{Wilson2006}. For instance, in |
| 8 |
> |
the last 20 years , there are quite a few MD packages that were |
| 9 |
|
developed to solve common MD problems and perform robust simulations |
| 10 |
|
. However, many of the codes are legacy programs that are either |
| 11 |
|
poorly organized or extremely complex. Usually, these packages were |
| 15 |
|
most MD programs also suffer from missing design and implement |
| 16 |
|
documents which is crucial to the maintenance and extensibility. |
| 17 |
|
|
| 18 |
+ |
\section{\label{appendixSection:architecture }Architecture} |
| 19 |
+ |
|
| 20 |
+ |
\begin{figure} |
| 21 |
+ |
\centering |
| 22 |
+ |
\includegraphics[width=3in]{architecture.eps} |
| 23 |
+ |
\caption[The architecture of {\sc oopse}-3.0] {The architecture |
| 24 |
+ |
of{\sc oopse}-3.0.} \label{appendixFig:architecture} |
| 25 |
+ |
\end{figure} |
| 26 |
+ |
|
| 27 |
|
\section{\label{appendixSection:desginPattern}Design Pattern} |
| 28 |
|
|
| 29 |
|
Design patterns are optimal solutions to commonly-occurring problems |
