Process Improvement

110 Items

Sort by Date | Title

Pat O'Toole's Dos and Don'ts of Process Improvement: Don’t Maintain a Low Profile Aug 23, 2002 When using the CMMI's continuous representation, organizational behavior is characterized within each Process Area (PA) by one of six Capability Levels: Incomplete (0); Performed (1); Managed (2); Defined (3); Quantitatively Managed (4); or Optimizing (5). Learn how CMMI's Capability Levels are used to assess organizational process improvement.

Pat O'Toole's Dos and Don'ts of Process Improvement: DON’T: Attend Industry Conferences Sep 13, 2002 Conferences offer one of the best ways to find out how other people have addressed the same day-to-day problems your organization faces. Learn how to be "actively engaged" to exploit every valuable opportunity to gain new insights to benefit your organization.

Pat O'Toole's Dos and Don'ts of Process Improvement: Don't Carry Old Baggage on a New Journey Aug 16, 2002 The CMMI's continuous representation has taken most of us out of our comfort zones because it's new. Learn how this method differs from the staged model approach and why "different" may be better.

Performance and Load-Testing of Axis with Various Web Services Styles Jul 16, 2004 Rajal Shah and Naresh Apte evaluate the performance and load-testing characteristics of various styles of web services with Axis.

Process Improvement via Organizational Change, Part 1 - What Doesn't Work Jan 4, 2008 Learn the three things that are missing from the basic toolkit of most change initiatives.

Quality By Design, Part 1: Avoiding Rotten Code 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.

Quality Last: Why We Make Poor Software Oct 14, 2009 Aaron Erickson discusses why your Statement of Work probably guarantees low software quality.

Quality of Service Design Overview Dec 17, 2004 This chapter provides an overview of the QoS design and deployment process. This process requires business-level objectives of the QoS implementation to be defined clearly and for the service-level requirements of applications to be assigned preferential or deferential treatment so that they can be analyzed.

Quality of Service for Internet Multimedia: a General Mapping Framework Oct 17, 2003 Continuous media applications have exceptionally stringent QoS requirements, and QoS for multimedia will remain a challenge well into the future. In this chapter from Quality of Service for Internet Multimedia, the authors present a futuristic QoS mapping framework.

Quality of Service, Part 1 of 2: Elements of Enterprise QoS for Voice Over IP Oct 8, 2004 In the first article of a two-part series, network management specialist Stephen Morris discusses the increasingly critical area of enterprise QoS for IP-based voice service or voice-over-IP (VoIP).

Quality of Service, Part 2 of 2: Managing Enterprise QoS Oct 15, 2004 In the conclusion of his two-part series on quality of service (QoS), network management specialist Stephen Morris discusses the issues of enterprise QoS management.

Real Process Improvement: Getting What You Need Aug 16, 2002 For processes to improve anything, they must be used and useful. Learn how good process improvement efforts are tied to business goals and problems, and most importantly actually improve processes.

Robert C. Martin’s Clean Code Tip of the Week #1: An Accidental Doppelgänger in Ruby 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 #12: Eliminate Boolean Arguments Aug 25, 2009 We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this twelfth tip in the series, the crew learns that Boolean arguments loudly declare that the function does more than one thing. They are confusing and should be eliminated.

Robert C. Martin's Clean Code Tip of the Week #10: Avoid Too Many Arguments Jul 6, 2009 We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this tenth tip in the series, the crew learns that functions should have a small number of arguments.

Robert C. Martin's Clean Code Tip of the Week #11: Output Arguments are Counterintuitive Jul 28, 2009 We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this eleventh tip in the series, the crew learns that if your function must change the state of something, have it change the state of the object it is called on.

Robert C. Martin's Clean Code Tip of the Week #2: The Inverse Scope Law of Function Names 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 #4: Avoid Obsolete Comments 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 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.

<< < Prev Page 2 3 4 5 6 Next >