Google Directory - Computers > Software > Software Engineering



Directory

Directory Help
Search only in ArticlesSearch the Web

Articles

Computers > Software > Software Engineering > Articles

Go to Directory Home

Web Pages

Viewing in Google PageRank order View in alphabetical order

	On the Criteria To Be Used in Decomposing Systems into Modules - http://www.acm.org/classics/may96/ One of the classic articles leading to modern software engineering, by D.L. Parnas.
	Building bug-free O-O software: An introduction to Design by Contract - http://archive.eiffel.com/doc/manuals/technology/contract/page.html Advanced use of assertions for clearer specifications and greater software reliability. By OO guru Bertrand Meyer, creator of Eiffel.
	Seven Steps to Test Automation Success - http://www.io.com/~wazmo/papers/seven_steps.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.
	Medical Devices: The Therac-25 - http://sunnyday.mit.edu/papers/therac.pdf Case study of a well known software error.
	High-Pressure Steam Engines and Computer Software - http://sunnyday.mit.edu/steam.pdf 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.

	Classic Testing Mistakes - http://www.testing.com/writings/classic/mistakes.html The role of testing, Planning the complete testing effort, Personnel issues, The tester at work, Test automation, Code coverage
	Heavy Rotation - http://www.acm.org/ubiquity/views/w_fiefer_2.html For business software, faster-cheaper can be better too.
	Lessons Learned -- Current Problems - http://www.spmn.com/lessons.html Technical and managerial best/worst practices. Based on study of US Department of Defense software projects.
	The Many Dimensions of the Software Process - http://www.acm.org/crossroads/xrds6-4/software.html Explores the importance and purpose of software process and quality.
	Introducing Demeter and its Laws - http://www.cmcrossroads.com/bradapp/docs/demeter-intro.html 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

	Sure It Works, But Is It Beautiful: The Relationship Between Software Aesthetics and Quality - http://www.chc-3.com/pub/beautifulsoftware.htm Some aspects of the relationship between quality and aesthetics (beauty) in software, using architecture analogies.
	Seven Principles Of Software Development - http://c2.com/cgi/wiki?SevenPrinciplesOfSoftwareDevelopment Emphasizes "soft" issues - attitude, approach.
	What Do Users Want? Engineering Usability into Software - http://foruse.com/articles/whatusers.htm User-Centered Design. Simple approaches for delivering smaller, simpler systems that better serve the needs of users.
	Orphans Preferred - http://www.gamasutra.com/features/19991222/mcconnell_01.htm Characteristics of software developers - personality type, demographics, age, education, attitudes.
	Successful Engineering Management: 7 Lessons Learned - http://www.jrothman.com/Papers/usefulmgmtideas.html People management advice for technical people.

	Major Causes of Software Project Failures - http://stsc.hill.af.mil/crosstalk/1998/07/causes.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.
	Nine Steps to Delivering Defect-Free Software - http://www.tenberry.com/errfree/steps.htm By a software developer and consultant with over 30 years experience.
	Principles of Good GUI Design - http://axp16.iie.org.mx/Monitor/v01n03/ar_ihc2.htm Describes the basic rules for all good interfaces - the cardinal dos and don'ts.
	Large Software Systems - Back to Basics - http://stsc.hill.af.mil/crosstalk/2000/06/evans.html John Evans; Crosstalk, June 2000. The importance of software architecture, and related items such as unambiguous requirements and coding standards.
	Classic Mistakes Enumerated - http://www.stevemcconnell.com/rdenum.htm Description of 36 ineffective development practices: people-related, process-related, product-related, technology-related. (Sample chapter from Steve McConnell's book Rapid Development.)

Survival Crib Notes: NASA's Success Checklist - http://www.stevemcconnell.com/sgcrib.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.)

Help build the largest human-edited directory on the web.

Submit a Site - Open Directory Project - Become an Editor