Top : Computers : Software : Software Engineering :
Articles
Websites
One of the classic articles leading to modern software engineering, by D.L. Parnas.
http://www.acm.org/classics/may96/
Technical and managerial best/worst practices. Based on study of US Department of Defense software projects.
http://www.spmn.com/lessons.html
Explores the importance and purpose of software process and quality.
http://www.acm.org/crossroads/xrds6-4/software.html
The advantages of scripting languages - typeless data, smaller code size, greater reuse, higher productivity. By TCL creator John Ousterhout.
http://dev.scriptics.com/doc/scripting.html
The role of testing, Planning the complete testing effort, Personnel issues, The tester at work, Test automation, Code coverage
http://www.testing.com/writings/classic/mistakes.html
Emphasizes "soft" issues - attitude, approach.
http://c2.com/cgi/wiki?SevenPrinciplesOfSoftwareDevelopment
Describes the basic rules for all good interfaces - the cardinal dos and don'ts.
http://axp16.iie.org.mx/Monitor/v01n03/ar_ihc2.htm
Characteristics of software developers - personality type, demographics, age, education, attitudes.
http://www.gamasutra.com/features/19991222/mcconnell_01.htm
People management advice for technical people.
http://www.jrothman.com/Papers/usefulmgmtideas.html
By a software developer and consultant with over 30 years experience.
http://www.tenberry.com/errfree/steps.htm
For business software, faster-cheaper can be better too.
http://www.acm.org/ubiquity/views/w_fiefer_2.html
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.
http://sunnyday.mit.edu/steam.pdf
Case study of a well known software error.
http://sunnyday.mit.edu/papers/therac.pdf
Index to articles written by members of Jerry Weinberg's SEM Group.
http://www.geraldmweinberg.com/R...ach_Reading.html/SEM.essays.html
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.
http://www.io.com/~wazmo/papers/seven_steps.html
Offers various resources - including news, articles, forum and job board.
http://www.software-engineer.org/
Some aspects of the relationship between quality and aesthetics (beauty) in software, using architecture analogies.
http://www.chc-3.com/pub/beautifulsoftware.htm
User-Centered Design. Simple approaches for delivering smaller, simpler systems that better serve the needs of users.
http://foruse.com/articles/whatusers.htm
John Evans; Crosstalk, June 2000. The importance of software architecture, and related items such as unambiguous requirements and coding standards.
http://stsc.hill.af.mil/crosstalk/2000/06/evans.html
Margaret Kulpa; Crosstalk, September 1998. Common misconceptions concerning software process improvement and the Software CMM.
http://stsc.hill.af.mil/crosstalk/1998/09/kulpa.asp
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.
http://stsc.hill.af.mil/crosstalk/1998/07/causes.asp
An overview of some simple principles to attain success designing and implementing new projects
http://www.unidata.ucar.edu/staff/wier/design.html
Recapturing, exploring and celebrating the Art of Computer Programming.
http://www.reciprocality.org/Reciprocality/r0/
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
site exerpt
Introducing Demeter and its Laws If you hang around any of the object-oriented mailing lists, chat groups, or Usenet newgroups, you'll notice that the name Demeter keeps popping up every few months or so on a regular basis. Usually it is in the form of...Advanced use of assertions for clearer specifications and greater software reliability. By OO guru Bertrand Meyer, creator of Eiffel.
http://archive.eiffel.com/doc/ma...ls/technology/contract/page.html
Description of 36 ineffective development practices: people-related, process-related, product-related, technology-related. (Sample chapter from Steve McConnell's book Rapid Development.)
http://www.stevemcconnell.com/rdenum.htm
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.)
http://www.stevemcconnell.com/sgcrib.htm
CIOs reveal the projects that did not kill them and made them stronger.
http://www.cio.com/archive/120198/turk.html