Question

Design the application architecture - Plan the application layers

You are designing an application that allows employees to change their human resources (HR) information, such as next of kin and direct deposit information. The requirements state that the application should talk directly to the HR systems’ database. However, at a recent company meeting, the CFO announced that the company will be converting to a new HR system over the next two years. They will take an additional year to move employees to the new system, one department at a time. How will this affect your design?

	You should implement the Repository pattern with the current HR system being the first repository that is built. When the second system comes online, you implement that data access using the same pattern.
	It won’t; the requirements state that the application should talk directly to the HR systems’ database.
	You should ensure your naming convention for the database as clearly as possible so you can rework your data calls with minimal changes.
	You should map the model directly to the database calls, anticipating that you will have to change the model as the new system rolls out.