Articles Software Engineering Software

Articles

• - 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.
  
• - Offers various resources - including news, articles, forum and job board.
  
• - Description of 36 ineffective development practices: people-related, process-related, product-related, technology-related. (Sample chapter from Steve McConnell's book Rapid Development.)
  
• - By a software developer and consultant with over 30 years experience.
  
• - Margaret Kulpa; Crosstalk, September 1998. Common misconceptions concerning software process improvement and the Software CMM.
  
• - Characteristics of software developers - personality type, demographics, age, education, attitudes.
  
• - The role of testing, Planning the complete testing effort, Personnel issues, The tester at work, Test automation, Code coverage
  
• - Index to articles written by members of Jerry Weinberg's SEM Group.
  
• - People management advice for technical people.
  
• - The advantages of scripting languages - typeless data, smaller code size, greater reuse, higher productivity. By TCL creator John Ousterhout.
  
• - Emphasizes "soft" issues - attitude, approach.
  
• - Some aspects of the relationship between quality and aesthetics (beauty) in software, using architecture analogies.
  
• - 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.)
  
• - Advanced use of assertions for clearer specifications and greater software reliability. By OO guru Bertrand Meyer, creator of Eiffel.
  
• - Technical and managerial best/worst practices. Based on study of US Department of Defense software projects.
  
• - User-Centered Design. Simple approaches for delivering smaller, simpler systems that better serve the needs of users.
  
• - For business software, faster-cheaper can be better too.
  
• - 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
  
• - Explores the importance and purpose of software process and quality.
  
• - CIOs reveal the projects that did not kill them and made them stronger.
  
• - 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.
  
• - 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.
  
• - Describes the basic rules for all good interfaces - the cardinal dos and don'ts.
  
• - Case study of a well known software error.
  
• - An overview of some simple principles to attain success designing and implementing new projects
  
• - John Evans; Crosstalk, June 2000. The importance of software architecture, and related items such as unambiguous requirements and coding standards.
  
• - One of the classic articles leading to modern software engineering, by D.L. Parnas.
  
• - Recapturing, exploring and celebrating the Art of Computer Programming.
  
  

Copyright © 1995-2007 Internet Advertising Solutions, Inc.
Copyright Notice | Privacy Policy | Site Map | APR