Hi,

Has anyone incorporated the use a design patterns when developing software with DMC?

If so, what pattern(s) were used? Were there any patterns that worked better than others?

Thank you in advance.

Tom

could you explain a bit more what you mean here? Are you talking about using the PATTERN function? Or something else.

Hi Clif,

I am referring to design patterns as they are used in software development. We are trying to put into
practice a pattern (if one exists for code developed via the DMC) that we may use as we develop our
ETL processes.

The below listed link on design patterns will give you a better understanding of what I mean by patterns.

http://en.wikipedia.org/wiki/D...rn_(computer_science)

Hi Tom,

The link above did not have the trailing parenthesis in the URL, so it routed to a "deleted page" on wikipedia.

Here is the corrected link:

The below listed link on design patterns will give you a better understanding of what I mean by patterns.

http://en.wikipedia.org/wiki/D...n_(computer_science)


Regards,

Dan at UNO

Thanks Dan.

Very interesting. Altho the DMC is not a programming language it does generate FOCUS code. One could argue that by using DMC to generate Data Flows you are enforcing specific patterns. That said I haven't heard of DataMigrator customers using this methodology.

My two cents on the matter: DMC provides a design pattern for the ETL process. The developer uses DMC's design pattern to create a Data Flow from pre-existing source and target data objects. Existing procedural objects can also be re-used in the Process Flow that wraps and modifies the Data Flow. DMC generates the underlying code based on the design. Every DMC design uses the same pattern - only the specific data and procedural objects change.