Re: Business Entity Designs

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I always like Duwamish. I always wondered why they never generated a typed
dataset. Are you following that route as well for your datasets? But, in a
web app, there is no dire need to call for child rows on a parent datarow
when there is no in-memory dataset as in a WinForm app.

IssueVision (windowsforms.net applications section) is a good example of
using delegates to keep different views of a dataset in sync if you want to
check that out for your GUI.

Ron

"DylanM" <DylanM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F1239C3-4B21-40C1-8569-013BEB84B49D@xxxxxxxxxxxxxxxx
> Thanks again...
>
> Sure - i'm still at UML stage since this is going to be a very large
> system
> & I'm trying to cover everything before I write any code (lessons learnt
> from
> past experience!).
>
> Quick summary - the key functionality.
> This is going to be an order system for a retail company. It will
> basically
> allow buyers to select a product from a catalogue system (based on an
> existing in-house developed IBM DB2 solution), then place orders for all
> the
> stores in the company - allocating quantities to each store based on the
> local market strength in the genre of the product.
>
> Tier Roles and Responsibilities (6 assemblies in total)
>
> Client user interaction via GUI
> Invoking remote calls to the Business Façade
> All business and application logic serviced by .NET remote \ COM+
> Assemblies
>
> Business Facade
> Simplified interfaces into the lower level tiers.
> Product System (retrieves product details from catalogue system)
> Order System (allocates order quantities, places orders, uses data from
> Product System)
> etc
>
> Business Rules
> Validates and ensures data integrity
> Accesses data services
> Contains application specific data
>
> Data Access
> Specific extended DataSet classes that represent the underlying data tiers
> Retrieve catalogue product information
> Supply relevant on-hand and sales data
> Interact with DB2 servers for store dial ins & order amendments
> Save orders and quantities in SQL Server database.
>
> Common
> Defines application configuration settings and shapes datasets
>
> Framework
> Low level system functionality, provides a consistent approach on handling
> error scenarios.
> Tracing and logging support, error checking and automatic logging of
> asserts
> and conditional checks.
>
> I'm trying to completely abstract the GUI from the database, it simply has
> to make calls into the Business Facade to accomplish any tasks. The GUI
> only
> references the Facade and the Common assemblies, so any changes in the
> actual
> underlying schema's should only need to be updated in these DLL's.
>
> I'm implementing this in WinForms, but I think they'll be wanting a
> simplified web front end of some sort as well - so this approach should
> allow
> easy future development and extensibility.
>
> I've tried to look at existing systems & examples (hence my Duwamish
> references!) for implementing the best solution.
>
> Any thoughts appreciated - I think I'm getting there now though - my 50
> page
> FSD is a monster, but proving a worthwhile reference!
>
> Thanks
> Dylan
>
>
>
> "RYoung" wrote:
>
>> By the way, can you provide some more info on the logical structure of
>> your
>> application? Mostly the assemblies and what their responsibilities are?
>> I'm
>> just curious on that, it can be a mind-boggling thought experiment at
>> times.
>>
>> - Ron
>>
>


.

Relevant Pages

  • Re: Business Entity Designs
    ... All business and application logic serviced by .NET remote \ COM+ Assemblies ... to make calls into the Business Facade to accomplish any tasks. ... references the Facade and the Common assemblies, so any changes in the actual ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Auto selection
    ... the GUI only. ... Selection/Focus is a part of the UI. ... Btw, with node you mean an business object, right? ... The event that triggers the creation of a folder is the use clicking ...
    (comp.object)
  • Re: Why I prefer inline code to code-behind
    ... An ASP.Net application, like any user application, has a user interface. ... at least an interface tier, a business tier, and possibly a data tier. ... one can use compiled classes in assemblies. ... but separate from the Page components. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Unit testing GUIs
    ... > developing a separate business model and application model. ... it implies having a simpler GUI than you might ... > Now in the final system, all three layers will be sewn together. ... > be defined as adaptors to domain objects and methods. ...
    (comp.object)
  • Re: 3 tier architecture: a lot of questions
    ... here is that your middle layer actually solves some business problem ... and the GUI. ... the RDB access layer. ... Where things get stickier is when the validation data is not yet in the ...
    (comp.object)