Hi Tino, *,
On Tue, Apr 11, 2006 at 01:00:00PM +0200, Tino Rachui - Sun
Germany - Development - Software Engineer wrote:
>
> you just hit a general problem of the specification
process and its
> output. The output of this process namely the
specifications which
> should serve as a working base for development,
testing, user experience
> and documentation are all too often in an
unsatisfactory shape.
Yes.
> The
> main problems are inclompleteness, ambiguity,
inconsistency to name just
> a few. To fix these problems a project has been setup
to address and fix
> such problems in the future see "Improving the
Specification Workflow"
> earlier in this newsgroup for details. As a first
outcome of this
> project an improved specification template has been
introduced. Of
> course this is not sufficient to fix all problems
already but its a
> first step more steps will follow.
I know. That's exaclty the point why I wrote the rant.
Having a template
and guidelines won't help if these aren't used.
> Beside all the technical and process improvements what
is always needed
> is motivation and understanding that specifications
when done properly
> save us a lot of time. Lessons that we all including
the OpenOffice.org
> community member who work at Sun have to learn.
Exaclty.
> As we all make mistakes the best we can do is to gather
early feedback
> and keep learning.
I'm happy to see that people here agree with me.
ciao
Christian
--
NP: Linkin Park - Figure.09
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe specs.openoffice.org
For additional commands, e-mail: dev-help specs.openoffice.org
|