[Modeling-cvs] ProjectModeling/Modeling/doc/HomePage status.tex,NONE,1.1

[<sbi...@us...>]

Update of /cvsroot/modeling/ProjectModeling/Modeling/doc/HomePage
In directory sc8-pr-cvs1:/tmp/cvs-serv2828/doc/HomePage

Added Files:
	status.tex 
Log Message:
Added Project's status page

--- NEW FILE: status.tex ---
\documentclass{article}

\title{Project's status}
\author{S\'ebastien Bigaret}
%\authoraddress{Email: \email{sbi...@us...}}
\date{\today}
\begin{document}
\input{www/menu-inline-begin}
\maketitle

\begin{description}
\item[Example of projects using the framework]

Even if the framework is still in a beta stage (see below), it is already used
in two applications that has been put in production since november 2002.

\begin{enumerate}
\item a python-gtk-based app. for bookshops' stock and sales management.
  \begin{itemize}
    \item mono-threaded application
    \item involved a team of 4 persons for 5 months w/ intensive use of the
      framework
    \item database size:  about xxx Mo.
    \item about XXX transactions per day,
    \item number of entities in the model: XXX
  \end{itemize}


\item a zope-based web app. dedicated to the supervision of doctors in
  duty for the french emergency services
  \begin{itemize}
    \item Multi-threaded environment (Zope-2.6.1), dev. 2 man-months
    \item model: 10 entities,
    \item database size: 27500 rows, about 2Mo,
    \item about 8800 transactions per day.
  \end{itemize}
\end{enumerate}

Both of these projects make a heavy use of qualifiers (fetch), custom
validation logic, inheritance and nested EditingContext.

We'd be happy to hear about your own projects and deployment experience.

\item[Development status: Beta]

While the framework is stable and used in production, we maintain it in
``beta'' status because of the following reasons.

\begin{itemize}

\item To our knowledge, some particular features have not been used extensively
  (apart in the unittests). This concerns: EditingContext.autoInsertion();
  ``manual'' management of many-to-many relationships.

\item There is a lack of functionalities for the sessioning mechanisms , see
  the following sections in the User's Guide for details:
  \begin{itemize}
    \item \begin{rawhtml}<a href="UserGuide/framework-integration-shared-ec.html">6.3.1 Sharing an EditingContext between sessions</a>\end{rawhtml}

    \item \begin{rawhtml}<a href="UserGuide/framework-integration-sessioning-ec.html">6.3.2 Sessioning</a>\end{rawhtml}
  \end{itemize}

\item there are still important missing features:
  \begin{itemize}

    \item database locking policy: neither the optimistic locking nor the
          pessimistic one is available. This means that the framework cannot
          safely handle a situation where another independent process modifies
          the database.

    \item Automatic many-to-many relationship is not supported yet

    \item It is not possible yet to specify that the framework should hold no
          more than a given number of objects.

  \end{itemize}

\end{itemize}

\item[Notes on the pre-0.9 series]

It's been some time since we're stuck in the pre-0.9 series. The reason is
that we once thought that the steps required to reach v0.9 would be easily
passed. But this was too much optimistic; in particular, we still need to
complete the \code{PyModel} dev. branch (where models can be expressed in
pure python rather than xml) and find a better name for the framework before
we reach 0.9. Until then, the pre-0.9 series continues.

\end{description}
%% end
\input{www/menu-inline-end}
\end{document}