Articles (Software Engineering)

Articles Sites:

Sure It Works, But Is It Beautiful: The Relationship Between Software Aesthetics and Quality Sure It Works, But Is It Beautiful: The Relationship Between Software Aesthetics and Quality: Some aspects of the relationship between quality and aesthetics (beauty) in software, using architecture analogies. (Articles) http://www.chc-3.com/pub/beautifulsoftware.htm What Do Users Want? Engineering Usability into Software What Do Users Want? Engineering Usability into Software: User-Centered Design. Simple approaches for delivering smaller, simpler systems that better serve the needs of users. (Articles) http://foruse.com/articles/whatusers.htm Nine Steps to Delivering Defect-Free Software Nine Steps to Delivering Defect-Free Software: By a software developer and consultant with over 30 years experience. (Articles) http://www.tenberry.com/errfree/steps.htm To Hell and Back To Hell and Back: CIOs reveal the projects that did not kill them and made them stronger. (Articles) http://www.cio.com/archive/120198/turk.html Major Causes of Software Project Failures Major Causes of Software Project Failures: Lorin J. May; Crosstalk, July 1998. Based on interviews with software consultants and practitioners who were asked to provide "autopsies" of failed projects with which they have been acquainted. (Articles) http://stsc.hill.af.mil/crosstalk/1998/07/causes.asp Successful Engineering Management: 7 Lessons Learned Successful Engineering Management: 7 Lessons Learned: People management advice for technical people. (Articles) http://www.jrothman.com/Papers/usefulmgmtideas.html On the Criteria To Be Used in Decomposing Systems into Modules On the Criteria To Be Used in Decomposing Systems into Modules: One of the classic articles leading to modern software engineering, by D.L. Parnas. (Articles) http://www.acm.org/classics/may96/ Lessons Learned -- Current Problems Lessons Learned -- Current Problems: Technical and managerial best/worst practices. Based on study of US Department of Defense software projects. (Articles) http://www.spmn.com/lessons.html Heavy Rotation Heavy Rotation: For business software, faster-cheaper can be better too. (Articles) http://www.acm.org/ubiquity/views/w_fiefer_2.html Orphans Preferred Orphans Preferred: Characteristics of software developers - personality type, demographics, age, education, attitudes. (Articles) http://www.gamasutra.com/features/19991222/mcconnell_01.htm Classic Testing Mistakes Classic Testing Mistakes: The role of testing, Planning the complete testing effort, Personnel issues, The tester at work, Test automation, Code coverage (Articles) http://www.testing.com/writings/classic/mistakes.html The Therac-25 Accidents The Therac-25 Accidents: Case study of a well known software error. (Articles) http://sunnyday.mit.edu/papers/therac.pdf Survival Crib Notes: NASA's Success Checklist Survival Crib Notes: NASA's Success Checklist: 9 Dos and 8 Don'ts for software project success, from NASA's Goddard Space Flight Center. (Sample chapter from Steve McConnell's book Software Project Survival Guide.) (Articles) http://www.stevemcconnell.com/sgcrib.htm Community for Software Engineers Community for Software Engineers: Offers various resources - including news, articles, forum and job board. (Articles) http://www.software-engineer.org/ Ten Things Your Mother Never Told You About the Capability Maturity Model Ten Things Your Mother Never Told You About the Capability Maturity Model: Margaret Kulpa; Crosstalk, September 1998. Common misconceptions concerning software process improvement and the Software CMM. (Articles) http://stsc.hill.af.mil/crosstalk/1998/09/kulpa.asp High-Pressure Steam Engines and Computer Software High-Pressure Steam Engines and Computer Software: Software safety. Parallels between the early development of high-pressure steam engines and software engineering that we can apply to the use of computers in complex systems. (Articles) http://sunnyday.mit.edu/steam.pdf The Many Dimensions of the Software Process The Many Dimensions of the Software Process: Explores the importance and purpose of software process and quality. (Articles) http://www.acm.org/crossroads/xrds6-4/software.html Designing and Managing Successful Projects Designing and Managing Successful Projects: An overview of some simple principles to attain success designing and implementing new projects (Articles) http://www.unidata.ucar.edu/staff/wier/design.html Building bug-free O-O software: An introduction to Design by Contract (TM) Building bug-free O-O software: An introduction to Design by Contract (TM): Advanced use of assertions for clearer specifications and greater software reliability. By OO guru Bertrand Meyer, creator of Eiffel. (Articles) http://archive.eiffel.com/doc/manuals/technology/contract/page.html Seven Principles Of Software Development Seven Principles Of Software Development: Emphasizes "soft" issues - attitude, approach. (Articles) http://c2.com/cgi/wiki?SevenPrinciplesOfSoftwareDevelopment Essays on System Effectiveness Management Essays on System Effectiveness Management: Index to articles written by members of Jerry Weinberg's SEM Group. (Articles) http://www.geraldmweinberg.com/ReadingStuff/Each_Reading.html/SEM.essays.html Scripting: Higher Level Programming for the 21st Century Scripting: Higher Level Programming for the 21st Century: The advantages of scripting languages - typeless data, smaller code size, greater reuse, higher productivity. By TCL creator John Ousterhout. (Articles) http://dev.scriptics.com/doc/scripting.html Large Software Systems - Back to Basics Large Software Systems - Back to Basics: John Evans; Crosstalk, June 2000. The importance of software architecture, and related items such as unambiguous requirements and coding standards. (Articles) http://stsc.hill.af.mil/crosstalk/2000/06/evans.html Principles of Good GUI Design Principles of Good GUI Design: Describes the basic rules for all good interfaces - the cardinal dos and don'ts. (Articles) http://axp16.iie.org.mx/Monitor/v01n03/ar_ihc2.htm Classic Mistakes Enumerated Classic Mistakes Enumerated: Description of 36 ineffective development practices: people-related, process-related, product-related, technology-related. (Sample chapter from Steve McConnell's book Rapid Development.) (Articles) http://www.stevemcconnell.com/rdenum.htm The Programmers' Stone The Programmers' Stone: Recapturing, exploring and celebrating the Art of Computer Programming. (Articles) http://www.reciprocality.org/Reciprocality/r0/ Introducing Demeter and its Laws Introducing Demeter and its Laws: Adaptive Programming - specifying the connections between objects as loosely as possible. Makes programs more flexible, more resilient to change, and more adaptable to varying configurations of classes within a given domain (Articles) http://www.cmcrossroads.com/bradapp/docs/demeter-intro.html Seven Steps to Test Automation Success Seven Steps to Test Automation Success: This paper presents seven key steps: improve the testing process, define requirements, prove the concept, champion product testability, design for sustainability, plan for deployment, and face the challenges of success. (Articles) http://www.io.com/~wazmo/papers/seven_steps.html