Combining MVVM, ORM, and some hardware interfaces

I am trying to plan the architecture of a robot controller application to be written in WPF. Since this MVVM is the actual template for WPF, and overall much more sexy, I decided to use it as a base layout.

The application will have several controllers that access the equipment outside the domainmodel, which represents the database and utility classes. And to access the database, I intend to use the repository (as a general idea, I want to use Ayedes IRepository), and then Linq2sql or EF4 for actual access.

The application will also have its own scripting engine for custom scripts.

But I'm not sure if I should consider access to hardware controllers and the scripting engine to be part of or under a domain model or something that was directly accessed from the controller level.

I tried to compose what I think is the right way to do this. But I'm not at all sure that this is the right way, so I would like to get some tips and advice on this, and how I can do it better.

http://dl.dropbox.com/u/1744224/Upload/Drawing7.png

+3
source share
2 answers

, ( ), .

, TDD, UML-...

+1

, . , MVVM MVVMC MVC:)

, . -, .

, . , , .

, , DI/IoC, , .

:)

http://dl.dropbox.com/u/1744224/Upload/Drawing7b.png

0

Source: https://habr.com/ru/post/1763577/


All Articles