From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,17c02346e2b592d9 X-Google-Attributes: gid103376,public From: Jerry Petrey Subject: Re: Software design and development methods? Date: 2000/10/10 Message-ID: <39E37364.1330E41C@west.raytheon.com>#1/1 X-Deja-AN: 679852334 Content-Transfer-Encoding: 7bit References: <8rvov4$imr$1@nnrp1.deja.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: news@ext.ray.com X-Trace: bos-service2.ext.raytheon.com 971207527 138.126.254.210 (Tue, 10 Oct 2000 15:52:07 EDT) Organization: Raytheon Company MIME-Version: 1.0 NNTP-Posting-Date: Tue, 10 Oct 2000 15:52:07 EDT Newsgroups: comp.lang.ada Date: 2000-10-10T00:00:00+00:00 List-Id: mjsilva@my-deja.com wrote: > > This isn't really an Ada question, but I think I'm likely to get more > good info and less nonsense asking it here than in almost any other > group. My question is how does an individual, or a small company with > limited resources, improve the software design and development process > beyond an ad-hoc collection of self-discovered "methodologies". What, > for example, are the -right- ways to do a requirements analysis, create > a functional specification and come up with a program framework? What > is the right way to create a test plan? > > The goal is to come up with a consistent way to develop "better" > (including but not limited to more reliable) software, including > embedded applications, quicker. These applications are not in the > safety-critical arena, BTW. > > Any and all guidance is greatly appreciated! > > Mike > mjsilva@jps.net >From what I've seen, most 'big' companies haven't figured this out yet, although, on paper, they claim to have. In any case, a good start would be reading the book "The Capability Maturity Model : Guidelines for Improving the Software Process (Sei Series in Software Engineering)", ISBN: 0201546647 . Also look at "Software Process Improvement : Practical Guidelines for Business Success (Sei Series in Software Engineering)", ISBN: 020117782X , "Managing the Software Process", ISBN: 0201180952 , "A Discipline for Software Engineering (Sei Series in Software Engineering)", ISBN: 0201546108 and "Managing Risk: Methods for Software Systems Development (SEI Series in Software Engineering)", ISBN: 0201255928 . Hope this helps. Jerry -- ----------------------------------------------------------------------------- -- Jerry Petrey -- Senior Principal Systems Engineer - Member Team Ada & Team Forth -- Raytheon Missile Systems -- NOTE: please remove NOSPAM in email address to reply -----------------------------------------------------------------------------