Re: Application design & architecture

Trevor,
 
TenFold sounds like a system of generically built state tables! 
I was going to say that if configuration is required then a system to
reconfigure it is needed.  More complex but less maintenance for the IT
department if done well.  Rules in this case are in the tables.  And the
data?  Query data, or anything through SOA?  Interesting!  Sign me up for
the training!!
 
bill
 

----- Original Message ----- 
From: Trevor Perry <mailto:tperry@xxxxxxxxxxxxxxxxxxxxx>  
To: Midrange Systems Technical  <mailto:midrange-l@xxxxxxxxxxxx> Discussion 
Sent: Monday, May 08, 2006 5:05 PM
Subject: Re: Application design & architecture


Bill, 

Yes - intent is key. Which is going to be different for every company, and 
every suite of applications. And, it will be different when new applications

are added to the mix. A great SOArchitecture would allow flexibility to 
cater for these. 

As for rules, business rules are often in our application code. Some 
development tools - Lansa, for example - have a repository of business 
rules. So, file vs. program would be dictated by the tool you wish to use. 
Here is an interesting example of a company that thinks applications can be 
built without code: http://www.sdtimes.com/article/story-20060501-06.html
<http://www.sdtimes.com/article/story-20060501-06.html>  . 
I wonder where the rules are? 

Trevor 


----- Original Message ----- 
From: "Bill Meecham" 
Subject: Re: Application design & architecture 


> Trevor, 
> 
> Thanks! 
> I think you're saying that decisions regarding granularity can be done 
> based 
> on system intent.  I support a wide variety of dissimilar systems that 
> have 
> intersecting data requirements.  Those intersections change so the 
> temptation is to make the components as grainy as possible but then you 
> have 
> a potential performance issue.  It's a balancing act that usually gets 
> determined by the urgency of the request...unfortunately. 
> 
> Eventually there are patterns that you see in building components that 
> become a guideline but there are always those stinking exceptions....of 
> course with smaller, more distributed pieces to worry about the new 
> concern 
> is the impact you'll have over the system instead of on a particular 
> program...but that's because global rule changes can be made once instead 
> of 
> potentially hundreds of times. 
> 
> The next question is if those rules belong in files or programs.  I used 
> to 
> think files but finally, after arguing for them 
> http://c2.com/cgi/wiki?WelcomeVisitors
<http://c2.com/cgi/wiki?WelcomeVisitors>  
> <http://c2.com/cgi/wiki?WelcomeVisitors
<http://c2.com/cgi/wiki?WelcomeVisitors> > , I think that too depends on the

> application. 
> 
> (time to head home) 
> bill