domain driven design - Help applying DDD to dynamic form application -
domain driven design - Help applying DDD to dynamic form application -
i designing application display dynamically-generated forms user come in values form fields , submit values persistence. form represents employee evaluation.
one utilize case allows administrator (from hr) define form fields. should able create new form, add/remove fields form , mark form 'deleted'.
the sec utilize case when manager views form , enters values form fields specific employee. should able save values @ time , recall saved values when viewing form 1 time again same employee.
finally, when manager satisfied values they've entered employee, can 'submit' form info persists flattened info data warehouse reporting purposes. when done, 'working' re-create of info removed form display empty next time view employee.
i not concerned front-end @ point , working on back-end service application sits between client , info store. application must provide course-grained interface of behavior required.
my question how many aggregate roots have (and that, how many repositories, etc)? separate form definition form info though need both when displaying form user?
i see 2 main entities, 'employeeevaluationschema' , 'employeeevaluation'. 'employeeevaluationschema' entity have collection of 'fielddefinition' value objects contain properties define field, basic beingness name of field. 'employeeevaluation' entity have collection of 'fieldvalue' value objects contain values each field definition. in simplest case, have field name , value property. next, 'employeeevaluation' have reference 'employeeevaluationschema' specify definition particular evaluation based on. can used enforce form definition in each evaluation. have 2 repositories - 1 each entity. if utilize orm such nhibernate, when retrieve 'employeeevaluation' entity, associated 'employeeevaluationschema' retrieved though there dedicated repository it.
domain-driven-design
Comments
Post a Comment