Application Architecture: Page

How requirements use cases facilitate the SDLC

Learn software use case processes and techniques that result in better application requirements in this tip. Takeaways include use case diagrams and user acceptance test case examples.

By Betty Leudke • Sept. 9, 2009

How to deliver software with an SDLC iterative model

The phases of iterative SDLCs come together to build better software applications faster, as long as the team avoids some common development and planning mistakes.

By Robin Goldsmith • Aug. 20, 2009

Is BASE a more scalable alternative to ACID transactions?

ACID is used to summarize the basic properties of a transaction in the database sense of the word, not the logical "business" transaction sense. On the other hand BASE is used to summarize the properties many large scale Web sites follow to relax or reduce the strict interpretation of ACID as implemented in most commercial database products.

By Eric Newcomer • Aug. 3, 2009

Expert shows seven ways to improve your project management abilities

Project management offices can benefit when the team has a diverse portfolio of skills. Learn how to become a better project manager by reading these seven suggestions, which range from developing talents and group leaders to better assessing software tools.

By Michelle LaBrosse • July 23, 2009

Differentiating between Functional and Nonfunctional Requirements

Many of the difficulties encountered in defining requirements relate to the functional-nonfunctional distinction. As so often happens, some of those difficulties are things of which people are aware, largely realizing after-the-fact that nonfunctional requirements were missed.

By Robin Goldsmith • June 23, 2009

Defining requirements during software project feasibility analysis

There are at least two key points in a software project when requirements should be defined. One point people often miss is during feasibility analysis, and failure to define requirements at this stage can doom a project.

By Robin Goldsmith • March 17, 2009

What is test granularity?

Test granularity is the level of detail at which your software tests and test cases address your project.

By John Overbaugh • March 6, 2009

How Covad made the switch to a distributed agile development process

Waterfall methodologies weren't working for Covad Communications, so the company switched its process to agile and cut costs while achieving faster project completions.

By Colleen Frye • March 2, 2009

Can traditional project management and agile development coexist?

Are traditional project managers and agile practitioners fundamentally at odds? Or can they live together and even complement each other?

By Colleen Frye • Feb. 18, 2009

How teams transition to agile development methodologies

Organizations usually move to agile development methods for the same reasons -- scope creep, time to market -- but details of the transition can vary from team to team.

By Colleen Frye • Feb. 10, 2009

Web application security testing checklist

Testing your Web application security is something that needs be taken seriously. The best way to be successful is to prepare in advance and know what to look for. Here's an essential elements checklist to help you get the most out of your Web application security testing.

By Kevin Beaver • Feb. 3, 2009

Big Blue dog learns new tricks: How IBM Software Group moved to agile

In this case study, Sue McKinney, vice president of IBM's development transformation, explains how and why the IBM Software Group made the transition to agile.

By Colleen Frye • Jan. 27, 2009

How to avoid requirements creep

Despite all the attention placed on defining requirements, creep continues to plague software projects. Learn how a different approach to requirements can curtail that creep.

By Robin Goldsmith • Jan. 22, 2009

Template for requirements use cases

A user is looking for a template for writing requirements use cases. Robin Goldsmith walks through a few interpretations of this question.

By Robin Goldsmith • Jan. 21, 2009

Making requirements walkthroughs more effective (and fun)

Do you have to twist arms to get people to attend your requirements review sessions? It doesn't have to be this way. Learn how to use a simulation model to get everyone engaged in the walkthrough.

By Tony Higgins, Contributor • Jan. 21, 2009

Formulating test status reports based on daily status criteria

A user requests help deriving the daily status criteria for the test execution of a software project, with status criteria including test execution criteria, test case failure rate and bug rate.

By John Overbaugh • Jan. 19, 2009

Is a requirements freeze in a software project a bad idea?

Learn why imposing a requirements freeze in an application project is usually a misguided idea.

By Robin Goldsmith • Dec. 16, 2008

Integration testing: Is it black box or white box testing?

Integration testing of software systems can be black box or white box testing. Learn how each can be used in this Ask the Expert Q&A with testing expert Mike Kelly.

By Mike Kelly • Nov. 11, 2008

Use cases and SRS for requirements gathering

Before comparing use cases and software requirements specifications, you should know what each is. Requirements expert Robin Goldsmith explains how use cases and SRS work and how to use them for requirements engineering.

By Robin Goldsmith • Oct. 6, 2008

How to match the test environment to the production environment

Testers often find a gulf between test results in a test environment and test results in a production environment. Testing expert John Overbaugh offers strategies for ensuring that test results in different environments match.

By John Overbaugh • Oct. 1, 2008

Running UAT and system testing in parallel

Conducting user acceptance testing and system testing at the same time may or may not be a good choice. Expert Baher Malek discusses the factors that testers need to consider when attempting a parallel UAT process.

Sept. 24, 2008

Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?

Agile software development calls on developers to write clean code, according to Robert "Uncle Bob" Martin. This free chapter introduces the concepts and methods programmers can adopt to write truly clean code.

By Robert C. Martin • Sept. 9, 2008

How to estimate change requests in requirements

Software requirements are often subject to change; using a sound estimation process helps greatly to manage change. Requirements expert Betty Luedke explains, in detail, how to implement good estimation techniques.

By Betty Luedke • Aug. 27, 2008

Use cases: Who writes them, what data do you include?

Typically a business analyst writes the use cases for a software project. But who writes them doesn't matter as much as what is included in them, says expert Robin Goldsmith.

By Robin Goldsmith • Aug. 26, 2008

The scope of user acceptance testing

User acceptance testing is ineffective if testers don't allocate the proper time and resources. Expert Karen N. Johnson explains how to avoid shortchanging UAT.

By Karen Johnson • May 5, 2008