I am working on a project that is responsible for creating a "job" which is one or more "work" Is made up of DAL through a database that is created for job and work column values, which are determined according to the business rules.
The way it is presently present, it is becoming complex and burdens, because business rules say that it requires access to many databases. Our system has to decide whether to make any jobs And / or how it can be established.
Before there is a need to be required to submit a list of jobs to keep things entangled and it can be used in a variety of ways (as a referenced assembly, through window service, or web service Through this).
Here are some things that do it:
- Generating job costs
- To give an account and / or a job to the user
- Execute an event for job submission progress tracking
- Merge data from outside, user-defined list (.csv, .xls, ect.)
- Copy files from a local drive to a network accessible drive (if necessary)
My question is: Which is the best way to create te Rthaon or design patterns are as possible as it manageable and simple?
It seems that the violation of the square again I would suggest that out of the bullet points given above Each has their own separate class of classes. In this manner you can implement it, where your main class represents the abstraction of its high level of what the system is doing.
Comments
Post a Comment