Skip to Content.
Sympa Menu

patterns-discussion - Re: [patterns-discussion] pattern to apply to centralized reporting

patterns-discussion AT lists.cs.illinois.edu

Subject: General talk about software patterns

List archive

Re: [patterns-discussion] pattern to apply to centralized reporting


Chronological Thread 
  • From: "Ralph Johnson" <johnson AT cs.uiuc.edu>
  • To: "Reza Razavipour" <rrazavipour AT stbernard.com>
  • Cc: patterns-discussion AT cs.uiuc.edu
  • Subject: Re: [patterns-discussion] pattern to apply to centralized reporting
  • Date: Thu, 20 Apr 2006 05:30:47 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references; b=iR+xXPEhvr1vsHckkl1hLn6g804pdB+OBf0ijGTvY9hoCMQkItEAfvaQi+yI2kMAFhJn6rAcE5XTwWm2KjdNUJ/T8Xw1yaikot6hznPlIr1hj7qE3TCMpb4y5gd/wdOYCu/O7PSn8/s1mRYU5oO1fY8yOq22Mx/bc8lJeZQh0BE=
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/patterns-discussion>
  • List-id: General talk about software patterns <patterns-discussion.cs.uiuc.edu>

There isn't enough information here for us to give you much concrete help.  For example, can this system inport and export data?  Then perhaps the best way is to export the data from each machine and inport it all into one machine.  On the other hand, perhaps the database is fairly easy to access.  This would be true if they used Access or SQL Server, but not if the "database" were a custom package.  If the database were easy to access, you could write a script that extracts data from one of the databases and puts it in a public place.  You could then run that script on each machine.  You'd write another script that would read the data from each machine and put it all in the database of a single machine, which could then run a report on the consolidated data.  Alternatively, you might make a web interface to the database and let the central machine fetch the data.
 
Noneof these solutions are very elegant.  There are lots of things that could go wrong with them.  A full client server system would be more elegant, but it would require writing a lot of software.  My guess is that part of the requirements that you didn't state is that your boss wants you to reuse the old software as much as possible and to get the whole thing done with as little work as possible.  But maybe I am misinterpreting the situation, and this is not a package that you bought, but a package that your company sells, and they want to redesign the whole thing.  If that is the case, my advice is all wrong.
 
There are many options, and you didn't give enough information for us to know which ones are possible or not possible.  For example, how good a programmer are you?  Do you have source for the system?  How much data is collected each day?  How soon does this have to be done?  How long is this system going to be continued to be used?  E-mail is a very inefficient way to find this out.  There are many options, and there is no one place you can go do learn them.  Figuring out the best choice is basically learning software architecture.  I suggest you find a local software architect that you can talk to.
 
-Ralph Johnson
 
On 4/19/06, Reza Razavipour <rrazavipour AT stbernard.com> wrote:
To all,

I have a software that runs on Windows, it has reporting built in, from a database. So customers buy this and install on their workstations. The problem is that each workstation can report on their own data only. I need to come up with an architecture for a central reporter to allow for a consolidated report of all these workstations aggregated data.

Anyone can tel where to go to learn about my options.

Thanks,

Reza





Archive powered by MHonArc 2.6.16.

Top of Page