Hi,
I am looking for a good software design book. Could you please
recommend one?
I am looking for a book that would provide the (human) language and
the methodology to write specifications for software projects.
It might seem that c.l.l is not the correct place to ask, but I can't
think of a better place.
Thanks in advance!
--
Kamen
Kamen TOMOV <·····@evrocom.net> writes:
> I am looking for a good software design book. Could you please
> recommend one?
>
> I am looking for a book that would provide the (human) language and
> the methodology to write specifications for software projects.
>
> It might seem that c.l.l is not the correct place to ask, but I can't
> think of a better place.
Indeed, on the lisp planet, we take a more 'experimental' approach to
software specification: we start at the REPL writing some forms, see
how it goes, and build upon that. The initial specification of the
software project is somewhat like: make a smarter spam filter. The
real software project specification document wanted by the PHB and
coworkers come at the end. If you're like me, you generate the
specifications from the lisp sources. Then you go to holidays while
the cowokers implement it anew in C++ ;-)
But serriously, one way not too bad to make specifications is
described in the OO methodologies, things like use cases, etc. And OO
diagrams look nice in specification documents. So any good OO
methodology book should do.
--
__Pascal Bourguignon__ http://www.informatimago.com/
WARNING: This product warps space and time in its vicinity.
On �������, ��� 18 2006, Pascal Bourguignon wrote:
> Indeed, on the lisp planet, we take a more 'experimental' approach
> to software specification: we start at the REPL writing some forms,
> see how it goes, and build upon that. The initial specification of
> the software project is somewhat like: make a smarter spam filter.
Starting from the code definitely has some advantages and perhaps we
(on the Lisp planet) can sometimes afford it. So I see your point. But
I will also need the knowledge on how to put all that in some common
form using the proper terminolodgy.
> The real software project specification document wanted by the PHB
> and coworkers come at the end.
... or the customer.
> If you're like me, you generate the specifications from the lisp
> sources. Then you go to holidays while the cowokers implement it
> anew in C++ ;-)
Yeah on some forgotten island, like our ancestor - Mac :-)
> But serriously, one way not too bad to make specifications is
> described in the OO methodologies, things like use cases, etc. And
> OO diagrams look nice in specification documents. So any good OO
> methodology book should do.
OK, so can anybody direct me to a good one - preferably Lisp oriented
and good for the purpose of writing specifications with actors, roles,
use-cases, process modeling, etc..
Thanks,
--
Kamen
Kamen TOMOV <·····@evrocom.net> writes:
> OK, so can anybody direct me to a good one - preferably Lisp oriented
> and good for the purpose of writing specifications with actors, roles,
> use-cases, process modeling, etc..
The classic UML book is The Unified Modeling Language User Guide by
Grady Booch, James Rumbaugh, Ivar Jacobson - not Lisp oriented though.
--
vedm
Kamen TOMOV wrote:
> OK, so can anybody direct me to a good one - preferably Lisp oriented
> and good for the purpose of writing specifications with actors, roles,
> use-cases, process modeling, etc..
I can recommend Martin Fowler's "UML Distilled". It's a rather thin
book, but manages to present the essentials and gets you going very
quickly. Afterwards, you can decide to delve deeper into specific issues
using other material.
I would also recommend to take a look at "agile methodologies" - IMHO,
they fit the "Lisp way" better. For example, I can recommend "Agile
Software Development" by Alistair Cockburn and "Planning Extreme
Programming" by Kent Beck and Martin Fowler.
Pascal
--
My website: http://p-cos.net
Closer to MOP & ContextL:
http://common-lisp.net/project/closer/