I am working on a project that is responsible for creating a “task” consisting of one or more “tasks” that are stored in the database via DAL. The task and task columns are made up of values defined in accordance with business rules.
The class, as it exists now, becomes complicated and cumbersome, because business rules require it to have access to many databases in our system in order to decide whether it is possible to create a task and / or how to configure it.
To complicate matters even further, you must submit a list of tasks, and you must invoke it in various ways (as a reference assembly through a Windows service or through a web service).
Here are some examples of what he does:
- Generate cost estimate
- Take the account and / or user to whom the task is assigned
- Display an event to track the progress of a task
- Combine data from an external, custom list (.csv, .xls, ect.)
- Copy files from a local disk to network access (if necessary)
My question is: what are the best practices or design patterns to make this as manageable and simple as possible?
source
share