|
The Wonderful World of Software Former STQE magazine Technical Editor Brian Lawrence shares a tale about why a commitment to quality and paying close attention to detail are critical elements in building better software. It’s all about careful planning and anticipating customer behavior. Go with Brian on a stroll through one of the oldest, best-known amusement parks to find out more.
|
|
|
Reference Point: The Software Project Manager's Handbook The Software Project Manager's Handbook is an excellent reference for the experienced or moderately experienced project managers who are looking to expand their "bag of tricks." Use this book as a reference to bone up on a specific topic, or use the case studies and questions to help you design and implement a feasible project plan.
|
|
|
How Do You Build the Right Software Right? Technical Editor Brian Lawrence explains his top-three list of things to do to deliver the right software right: risk-based planning, problem definition and modeling, and congruent leadership.
|
|
|
Making Numbers Count Numbers count—no two ways about it. But any numbers you include in a bug report should also include the appropriate units of measure. In an example from their experience, David Wilson and Leonidas Hepis explain the importance of using consistent terminology and units of measure.
|
|
|
I Think, Therefore I Prototype Prototypes can help you deliver the right software. Here, Technical Editor Brian Lawrence gives examples of prototypes and some guidelines for prototyping.
|
|
|
A Cautionary Tale Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment.
|
|
|
Software Requirements Brian Lawrence and Johanna Rothman recommend Software Requirements by Karl Wiegers, a "readable, practical book about gathering and managing requirements, focused on best practices."
|
|
|
Welcome to Software Testing and Quality Engineering Technical Editor Brian Marick introduces the first issue of STQE magazine. He says the magazine "is for people who get their hands dirty, whether by writing tests, cranking out code, managing others, or--perhaps the hardest task of all--being the internal QA consultant who has no direct authority but must somehow persuade ten projects with impossible deadlines to think strategically."
|
|
|
The Ariane 5: A Smashing Success On June 4, 1996, the maiden flight of the Ariane 5 satellite launcher ended spectacularly after only forty seconds, with bits of the $67 billion vehicle and its payload spread over a fairly large part of French Guiana. The report issued July 19 by the International Inquiry Board noted that the fiery crash was due to a "chain of technical events." The details of that particular chain of events are reviewed here.
|
|
|
What's in a Name? Technical Editor Brian Marick outlines a goal for the magazine and its readers: gradual process improvement, driven by immediate needs.
|
|