design specifications

Hi, all

I was wondering if someone could guide me in the right direction about doing a formal design specification. Unlike CAD software project people use UML or other graphical tools to share information among different developers.
Is their a better way to do it while doing ACAD project using VB.net.
I just finished a project which had about 50-60 classes in it and i was only devloper, I was begining to loose the track however it was managed however the next project is a massive one with classes in hundreds.

Could someone please let me know if something is available in the market to manage the classes or it has to be done using paper & pencil.

TIA
Irfan

 

Hi,

In simple terms, why not use Excel as a Database to manage them?

We do this with Help files, inclusive of using numbers as a percent of the
work on an item completed and colour coding of various features to suit our
needs.

--


Laurie Comerford
CADApps
www.cadapps.com.au

doing a formal design specification. Unlike CAD software project people use
UML or other graphical tools to share information among different
developers.

only devloper, I was begining to loose the track however it was managed
however the next project is a massive one with classes in hundreds.

to manage the classes or it has to be done using paper & pencil.

 

Irfan,

We're using similar approach (infrastructure design): ACAD // XML/UML //
RationalRose // Oracle 9i or GIS Design Server...

There's a neat little thingy called FDO Classes (aka Feature Classes)
implemented in Autodesk Map 3D 2005. Built-in driver "talks to" Oracle 9i
and FDO AGDS Cartridge (aka GIS Design Server Client). IBM's Rational Rose
is our primary object modeller/documenter - offers a complete visual design
and development environments that targets .NET-based systems.

Regards,
Maksim Sestic

doing a formal design specification. Unlike CAD software project people use
UML or other graphical tools to share information among different
developers.

only devloper, I was begining to loose the track however it was managed
however the next project is a massive one with classes in hundreds.

to manage the classes or it has to be done using paper & pencil.

 

In real OOP (as opposed to what VB calls 'OOP'), we model object
and data relationships graphically, and that's mainly because the
number of class and data relationships in a project can become
overwhelming, making it extremely difficult to visualize the entire
project or architecture at the conceptual level.

I generally do class diagrams for any project with at least a dozen
or so major classes in it, because it makes it easier to visualize the
entire design and the relationships between different elements.

I don't see how Excel would be useful for this.