|
> I am trying to see if somebody has architecture like what I > described above, and I would like to know if there are any > gotcha's or problems other than it is incredibly hard to make > it extensible ;-) Aaron, In addition to user interface ideas, you seem quite interested in program architecture. Is that because portions of the user interface would depend on the type of customer, while other portions of the user interface would be common across multiple types of customers? For example, one customer may need to order pizza while another customer may need to order microwaves? The contact information screens may be the same, while the order screens may be different? The controller must know which procedure to call based on data in a repository, rather than having the CSR back out to a menu to choose a different hyperlink? Avoid duplicating program code across multiple modules? Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.