Software Development Resources

As part of our mission to advance the art and science of commercial software engineering, Construx provides an array of software development resources. Our focus is on supporting time tested, proven software development best practices across the full spectrum of software development activities.

10 Most Important Ideas in Software Development

As software engineering approaches its 40th birthday, do we know which software development ideas matter most? In this talk, award-winning author Steve McConnell identifies 10 of the most powerful ideas in software engineering. McConnell explains how the 10 ideas form the foundation for effective software development, and he shows how practices ranging from the waterfall model to extreme...

Architecture Checklist

The checklist covers design at the architecture level. The term element is used in this document to mean any sub-system, component, module or other design element the architecture covers.

Blended Learning for Software Professionals

Instructor led technical training continues to provide the highest quality training experience, but advances in online eLearning are narrowing the quality gap between Instructor Led Training and eLearning. The choice of training modalities does not have to be an 

Bridging the Product Introduction Gap

New software and hardware technologies are driving product innovation at an unprecedented rate. Companies that thrive in this new era will adopt practices that foster product management and product development collaboration to blend new technology alternatives with sound market insight.

Code Complete 2: Modern Realities of Software Construction

For more than 10 years, Code Complete has been a computing-industry best seller. The past decade has seen the emergence of object-oriented programming, the Internet, the CMM, offshore outsourcing, Java, Visual Basic, and the Agile movement as well as staggering advances in computing power and numerous other developments.

Design Checklist

This checklist captures common elements that should be present in all design artifacts including documents, diagrams, prototype models, etc. Some items refer to the design of the system as a whole, and others can be applied individually to separate parts of a design. 

Design For Change

Design For Change refers to employing design structures, techniques, practices, idioms and patterns that allow a software system behavior to be more easily modified in the future.

General Design Checklist

This checklist captures common elements that should be present in all design artifacts including documents, diagrams, prototype models, etc. Some items refer to the design of a system as a whole, and others can be applied individually to separate parts of a design.

High Level Software Design Checklist

This checklist covers high level design issues. The term component is used to refer to high level design elements that may include objects,components,modules,packages,sub-systems,etc.See CxStand_Design for a discussion of different design levels in CxOne.

Low Level Software Design Checklist

This checklist covers low level designs. For this checklist, a “unit” describes the low level element you are working on; it could be a module, class, script, webpage, form, report, etc. See CxStand_Design for a discussion of different design levels in CxOne.