JUN 23, 2004 1:00am ET

Related Links

10 Sustainability Predictions for 2011
February 23, 2011
A Letter to Future Employees: Embrace Analytics
February 3, 2011
A Hunger for Risk
January 6, 2011

Web Seminars

Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014
Integrating Relational Database Data with NoSQL Database Data
October 23, 2014

Do Business Rules Fit the Systems Development Life Cycle?


The systems development life cycle has been around for as long as computerized applications have been built and is all too familiar to most practitioners. Although it can be articulated in a number of ways, it basically consists of defining the requirements of an application, then analyzing the business problem domain, then designing an application, then building it, then testing and debugging it, and then running the application in production. There are a number of variations on this theme, such as a final obsolescence phase or iterative building, testing and debugging steps. A major problem, however, is that the systems development life cycle looks very hit-and-miss if you compare it to other engineering activities such as building bridges or aircraft. Bridge builders and aircraft designers certainly look at requirements and do design work, but they create detailed specifications that are used to build things in a way that never seems to happen in software development. In fact, the way in which we do software development never rises to the level of true "engineering" despite new methodologies that seem to come along every couple of years. These methodologies often promise that they will supplant the traditional systems development life cycle, but always seem to end up just being variations on it. There are legitimate grounds to ask if the business rules approach is just another variation to dealing with business logic, or if it really does not fit with the systems development life cycle. We may have to wait a while to get the definitive answer, but there is evidence that the business rules approach does not fit the systems development life cycle.

Hand-Crafted Code

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Filed under:


Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
Please note you must now log in with your email address and password.