IEEE Std 830-1998 -Software Requirements Specifications

Posted by Craig Brown

Team





I thought I should call your attention to International standard IEEE 830-1998.  It's a standard for software requirements specifications.

IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications

IEEE have created standards on a range of engineering disciplines from networking to nuclear power.

A summary of it's contents is here where you can also buy a copy.  Anyone read it?  How close is it to the IIBA's BABOK approach?

Is requirements management an engineering discipline?  Some think so, other disagree.

Opinions?

(picture by Exolucere, CC @ Flickr)

 

Labels: ,

2 Comments:

  1. Janet Rolsma said...
    1:44 AM  
    In my opinion, anything that requires planning requires requirements management. I know there is a very formal means to manage requirements in the engineering discipline. I know that as BAs and PMs we are trying to come up with something formal that works.

    I think that if you aren't managing requirements, you are asking to fail.
    Craig Brown said...
    9:13 PM  
    Yep. I am with you 100% on that one.

Post a Comment



Subscribe to: Post Comments (Atom)