The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Software Design Industry Standards

I want to know what industry standards are being followed by software companies for software design. I run my own startup and have no idea how the design phase must be handled. When a request for software is received, how to proceed further. Which designs are useful?
R
Tuesday, April 15, 2008
 
 
You _do_ realise how open that question is, don't you?
Troels Knak-Nielsen Send private email
Tuesday, April 15, 2008
 
 
How about using Rational Unified Process (RUP).
http://en.wikipedia.org/wiki/Rational_Unified_Process
Silvercode
Tuesday, April 15, 2008
 
 
Go back in the Joel On Software archives, I think there's an outline of a "light" process back there.

"Heavy" processes include:

DOD-STD-2167 (VERY detailed specification of too many documents)

Mil-Std-498 -- (a MUCH more streamlined follow-on version) -- http://www.pogner.demon.co.uk/mil_498/

The CMMI standard, put out by Carnegie-Mellon University's Software Engineering Institute (SEI).  Here's where CMM levels 1 (whatever) through 5 (the best) come from.

IEEE 12207 (http://en.wikipedia.org/wiki/IEEE_12207) is the follow-on to '498.

In most of these procedures above, quite a lot of "customization" can be done for your particular environment.

My favorite approach is Agile Modeling, by Scott Ambler. http://www.agilemodeling.com/essays/agileModelingRUP.htm

This takes the "heavyweight" UML RUP process, and reduces it to a nice minimum.

And I've really enjoyed Yourdon's "Just enough systems analysis" coverage of the DFD (Chapter 19).
http://www.yourdon.com/jesa/pdf/JESA_cb.pdf
AllanL5
Tuesday, April 15, 2008
 
 
Christopher Wells Send private email
Tuesday, April 15, 2008
 
 
Looks like you can get it here, http://www.yourdon.com/jesa/jesa.php
but requires registration

Found that link from here, http://yourdon.com/strucanalysis/wiki/index.php?title=Introduction

cheers
Chris Hulan Send private email
Tuesday, April 15, 2008
 
 
But the registration is free.

Sorry about that.
AllanL5
Tuesday, April 15, 2008
 
 
"I run my own startup and have no idea how the design phase must be handled. When a request for software is received, how to proceed further. Which designs are useful?"

If I understand your role correctly, it is not you who will actually do the design, but either some service provider, ISV or employess of your company.

IMHO, the best way to deal with it is to stay out of the way and let the designers decide which 'standard' they will use while on the other hand strongly insist to use a standard and stick to it.

In order to do this, you will have to be clear about the following two areas:
- the requirements for the software
- your requrirements for the design in order to steer your business. Think about it that way that the design documentation you will receive will help you to understand  the current status, the tradeoffs and estimations.

In my personal experience (I was part of the RUP steering comittee some ages ago:-) I consider the agile approach, and use cases (some call them user stories) a good start to get into the topic.

Another input to this decision is your market: e.g., if you have customers in the 'DoD market', you should think about using accepted standards of this market.

my some cents,
Volker
Volker Kopetzky Send private email
Wednesday, April 16, 2008
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz