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, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,17c02346e2b592d9,start X-Google-Attributes: gid103376,public From: mjsilva@my-deja.com Subject: Software design and development methods? Date: 2000/10/10 Message-ID: <8rvov4$imr$1@nnrp1.deja.com>#1/1 X-Deja-AN: 679824899 X-Http-Proxy: 1.1 x55.deja.com:80 (Squid/1.1.22) for client 206.169.137.75 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Tue Oct 10 18:59:53 2000 GMT X-MyDeja-Info: XMYDJUIDmjsilva Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) Date: 2000-10-10T00:00:00+00:00 List-Id: 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 Sent via Deja.com http://www.deja.com/ Before you buy.