Quantcast
Channel: patterns & practices: Prism
Viewing all articles
Browse latest Browse all 1878

New Post: WPF PRISM modular design

$
0
0

Hi folks

I'm working on an application, have started down the PRISM modular path using Unity for DI and Entity Framework Code First approach for entity/model creation and use. My question is related to modular design concept and where parts fit.

My application is for managing patients in small health care practices. 

I have created a WPF application with Shell window, UnityBootsrapper; also a Client module with a structure of:

  • Views  containing Usercontrols for displaying/capturing input
  • ViewModels containg logic for views
  • Interfaces I currently have nothing in these but are there for dependency injection
  • Model contains my entity structures
  • Data holds my Client dataContext and initializer

The application will allow a client/patient to be entered. A client can have many referrals from different sources and a referral can have many appointments. 

At present my model folder has all the entities I have identified so far for my application but these are not all client specific as I have a referral entity which I believe should be contained in a Referral module? as well as Appointment specific entities that I think should be in an Appointment module. Where would you place all your entities? Also I am about to start creating a referral module, seeing as a Referral must have a Client, how would my referral module be aware of client/patient data, would the Client module have a Search method returning a client that the referral module can call upon?

I've gotten in a bit of a muddle with how architecture should look and how modules would interact with each other?

Thanks for any help.


Viewing all articles
Browse latest Browse all 1878

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>