Saturday, July 13, 2013

Rule Triggers

Example of a "rule trigger" (which I believe muddies code when placed inline, which is why we need standard rules engines?)

Being a member of "Halloween Sale" does not mean that the item is always on sale. The "rule trigger" should also take into account the date. Example:
  HALLOWEEN = 18   // See example tables above
  if memberOf(item,HALLOWEEN) and month(today()) = "October" then
    item.price = item.price * 0.9
  end if
http://www.geocities.com/tablizer/sets1.htm

Tuesday, July 9, 2013

Software Requirements

Requirements gathering -- Collecting user, operational, and platform requirements. User requirements express who the business users are and what they need to do with the system. Operational requirements address the system and network management and maintenance. Platform requirements detail the desired infrastructure components.
Note: So there's more counted as "requirements" than just user requests...
link

Sunday, June 30, 2013

Web Development Process

"Scripting elements that are used to prototype solutions should migrate into tag libraries as part of the development process" -- on JSP scripting elements versus tag libraries. link

Wednesday, June 12, 2013

Denormalization

On the fallacy of it: http://www.dbdebunk.com/2013/03/normal-forms-dependent-on-dependencies.html
Shows the need to recognize Functional Dependencies even in time-based records such as invoices.

Tuesday, June 11, 2013

First Normal Form


The classic discussion point is "OK, so you have phone1, phone2 and phone3, so what happens if one customer has 4 phones?". If your design is vulnerable to such a point then it is not in 1NF. – Greenstone Walker May 6 at 1:52

Wednesday, May 8, 2013

Where to Handle ASP.NET Exceptions

Unless some special exception is expected, you wouldn't want to handle general exceptions in the page code. Exception handling belongs in Global.asax
 http://www.codeproject.com/Articles/241066/How-to-Validate-ASP-NET-Web-Forms-Using-Business-R