Path: utzoo!attcan!uunet!ogicse!pdxgate!eecs!warren From: warren@eecs.cs.pdx.edu (Warren Harrison) Newsgroups: comp.software-eng Subject: Re: Identifying high quality software development efforts Message-ID: <645@pdxgate.UUCP> Date: 12 Nov 90 16:35:28 GMT References: <1965@shodha.enet.dec.com> Sender: news@pdxgate.UUCP Reply-To: warren@eecs.UUCP (Warren Harrison) Distribution: na Organization: Portland State University, Portland, OR Lines: 32 In article <1965@shodha.enet.dec.com> marks@ssdevo.enet.dec.com (Randy Marks) writes: > >In article <534@pdxgate.UUCP>, warren@eecs.cs.pdx.edu (Warren Harrison) writes... >>As I said, this is just a guess, but the AEL metric is mentioned many times >>in a mongraph entitled Japanese Software Engineering which is a collection >>of papers by Japanese Software Engineering figures. > >Are these papers in Japanese or English? Can somebody provide additional >info. so that I might have our library obtain copies for me? The papers are in a collection entitled "Japanese Perspectives in Software Engineering", edited by Yoshihiro Matsumoto and Yutaka Ohno, published by Addison Wesley, ISBN 0 201 41629 8. After checking, I find my acronym was incorrect - it's EASL (equivalent assembler source lines). Specific numbers mentioned in the papers was (for 1985) 1.6K EASL/month, not including reused code, 3.1K if you include reused code. The SOftware Engineering text by Schach (ISBN 0 256 08515 3, Irwin Publishers) cites an expansion factor of 4 for EASL which translates into about 400 lines of new "high level" code a month. As I said in my earlier posting, I'm not sure if the other numbers from Japan we always hear are EASL or actual high level lines of code, but in the Addison Wesley collection, manyof the authors specify their data in terms of EASL. Warren ========================================================================== Warren Harrison warren@cs.pdx.edu Department of Computer Science 503/725-3108 Portland State University