Deliver C# code for a a simple workflow and case management component with DB storage

Deliver C# code for a a simple workflow and case management component with DB storage The code must be maintainable, demonstrating good up-to-date competence in agile OO design with a good level of BDD style unit testing. Outline Requirements My client wants a simple workflow management component, which will work as part of a larger system. It must allow us to: * easily define a workflow as a state-machine. As easily as for example [login to view URL] (We welcome and prefer the use of existing, well-supported, open source solutions such as stateless or alternative as a part of your solution). * Understand these features of a UML 2 state machine: states, transitions, actions (entry, exit, do and transition actions), triggers, guard conditions, hierarchical states. * define and persist workflows by name; retrieve a workflow by name from the database; and apply it to objects (the objects in question will represent insurance related claim cases handled in a call centre) to track the progress of cases through a workflow. * track the process of thousands of cases through the workflow defined. The initial 3 or 4 workflows will involve around 20 or 30 states and transitions per workflow. * store the states of the cases in a database. (The database will be in use for several years). * retrieve the entire history of a case's passage through the workflow so far including dates. * associate actions with a state. When a trigger is fires which makes a case move into a state with a defined action, the component show respond by returning a list of the actions associated with the state, and creating entries in a tasklist table in the database so that we can see that the case requires certain actions to be followed up. * retrieve past and present actions for a case * record started and finished dates for actions and query completed and outstanding actions. * query cases, states and actions generally by case id, states, past and present actions, date ranges etc. Technical Constraints The source code must be in C#, and compile and run on both .Net 3.5 and on .Net 4.0. It must build to produce a single component (e.g. a dll and its dependent dlls). It will be used both by a command line executable But Most Importantly in an Asp.Net application hosted on IIS 7/8 My client uses: MS Sql Server 2008; Castle Windsor for dependency injection; NUnit and Moq for testing; and [login to view URL] for DB access. Please use these technologies in preference to alternatives. Given a SQL 2008 database with 10,000 cases on a 2GHz Core 2 Duo server with 4GB memory, we would expect the component to comfortably handle 3 transactions per second sustained at peak; and to be able to run most queries against all cases and actions in less than 5 seconds. Database changes must be scripted and include rollback scripts. I can provide some assistance with this if needed. Unit Testing Requirements I will assist you significantly to turn the requirements into more detailed BDD style "When ... Then ... Should ... (Given ...)" statements which you should implement as NUnit tests. Since no UI is involved I expect 90% or better test coverage. Examples will be something like: "When I ask for the current state of a case, given that the case has started on a workflow, I should get back the current state of the case" "When I ask for the history of a case by passing its Id to the system, it should return an object listing its current state, the states the case has been through in date order, a list of completed actions for the case in date order and a list of outstanding actions for the case, given that the case has previously" Working process I will provide a repository on BitBucket where you can check in. Because the code using the component which you are writing is being developed simultaneously by me, you must check in work so far at intervals no longer than a couple of days.