Software Development & Management

197 Items

Sort by Date | Title

Prologue: Software Architectures and Documentation: By Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Paulo Merson, Robert Nord, Judith Stafford; Nov 11, 2010; This prologue to Documenting Software Architectures: Views and Beyond, 2nd Edition begins with short overviews of software architecture and architecture documentation and then discusses architecture views, architecture styles and rules for sound documentation.

Publish and Subscribe Using C++ and the Observer Pattern: By Stephen B. Morris; May 27, 2005; Separation of concerns is increasingly on the programmer's radar. Given the growing range of data access products and platforms, it is now essential to separate data producers from data consumers. The observer pattern provides a simple but powerful model for achieving this crucial design goal.

Quality By Design, Part 1: Avoiding Rotten Code: By Pete McBreen; May 31, 2002; We all have to face the fact that some software stinks; it doesn't work right or it just plain feels wrong. Fixing these problems is simple, but may not be easy. We have to understand the nature of software development and make sure that we allow ourselves enough time to do a good job.

Rebecca Wirfs-Brock on the 15th Anniversary of Design Patterns: By Rebecca Wirfs-Brock; Oct 30, 2009; Rebecca Wirfs-Brock shares her thoughts about Design Patterns: Elements of Reusable Object-Oriented Software on the 15th anniversary of its publication.

Robert C. Martin’s Clean Code Tip of the Week #1: An Accidental Doppelgänger in Ruby: By Robert C. Martin; Jan 7, 2009; Robert C. Martin investigates an interesting dilemma: if the implementation of two functions is identical, yet their intent is completely different, is it still duplicate code?

Robert C. Martin's Clean Code Tip of the Week #2: The Inverse Scope Law of Function Names: By Robert C. Martin; Jan 21, 2009; The longer the scope of a function, the shorter its name should be.

Robert C. Martin's Clean Code Tip of the Week #3: Avoid Inappropriate Information: By Robert C. Martin; Jan 28, 2009; In this third tip of the series, programmers discuss how to avoid inappropriate information.

Robert C. Martin's Clean Code Tip of the Week #4: Avoid Obsolete Comments: By Robert C. Martin; Feb 11, 2009; A comment that has gotten old, irrelevant, and incorrect is obsolete. Obsolete comments tend to migrate away from the code they once described and become floating islands of irrelevance and misdirection.

Robert C. Martin's Clean Code Tip of the Week #5: Avoid Redundant Comments: By Robert C. Martin; Feb 18, 2009; In this fifth tip in the series, the programmers discuss redundant comments, which describes something that adequately describes itself.

Robert C. Martin's Clean Code Tip of the Week #6: Avoid Poorly Written Comments: By Robert C. Martin; Feb 27, 2009; We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this sixth tip in the series, the crewmen try to interpret a poorly worded comment.

Russ Olsen on the 15th Anniversary of Design Patterns: By Russ Olsen; Nov 16, 2009; Russ Olsen shares his thoughts about Design Patterns on the 15th anniversary of its publication.

Saving Money with Legacy Data: By Stephen B. Morris; Mar 11, 2005; Migrating legacy source code is a time-consuming and complicated business. The same is often true for the migration of legacy data, but there are some useful techniques that can reduce the cost. In this article, network management software specialist Stephen Morris discusses the migration (or upgrading) of legacy data into XML format. This process proves to be surprisingly straightforward and low in cost.

Scrum with XP: By Kane Mar, Ken Schwaber; Mar 22, 2002; Ken Schwaber and Kane Mar argue that Scrum can be combined with XP engineering practices to generate a significant impact on the productivity of a project team. This article details a project in which this theory was put to work successfully.

Secure By Design? Techniques and Frameworks You Need to Know for Secure Application Development: By Randy Nash; Dec 19, 2012; What do you know about developing secure robust software? Randy Nash discusses several available techniques and frameworks for secure application development.

Setting Up a Private Docker Registry: By Christopher Negus; Jan 19, 2016; This chapter from Docker Containers: Build and Deploy with Kubernetes, Flannel, Cockpit, and Atomic explains how to create a private Docker registry in Fedora or Ubuntu, use the docker-registry package, use the registry container image, and understand the Docker image namespace.

Sneaking It In: Getting Customers and Developers to Go Agile: By Ken Schwaber; Mar 15, 2002; Ken Schwaber describes some strategies for getting customers and developers to accept and implement agile processes - even piecemeal, if necessary.

Software [In]security: A Software Security Framework: Working Towards a Realistic Maturity Model: By Gary McGraw, Brian Chess; Oct 15, 2008; Gary McGraw and Brian Chess introduce a software security framework (SSF) to help understand and plan a software security initiative.

Software [In]security: Attack Categories and History Prediction: By Gary McGraw; Aug 25, 2009; Software security expert Gary McGraw describes how to divide attacks into four categories — and predict the attacks of tomorrow.

Software [In]security: Balancing All the Breaking with some Building: By Gary McGraw; Aug 30, 2011; Security expert Gary McGraw argues that the software security industry is favoring offense at the expense of defense, and that more proactive defense is needed.