Password Manager Web API

Create a client/server data management application that meets the following criteria:

• Has fully separated client and server-side logical layers.
• Manages at least two entities (in our example these are semesters and courses).
• For this, the data should be stored in a static class.
• Users should be able to perform standard CRUD operations on each entity: create, read, update, and delete.
  • Create should allow the user to specify information that is then used to populate the properties of an entity
  • Read should allow the user to get a list of entities that are currently stored in the static class on load or when the relevant UI is shown.
  • Update should allow the user to see the properties of a given entity, modify them, and then save the updated properties back to the appropriate property of the static class.
  • Delete should allow the user to remove an entity from the appropriate property of the static class and that entity should no longer appear when the list is read from the class.

Additional Notes:

• The client side code can be written as a console, WPF, SPA, or web application. Any widely used front-end technology is fine.
• You MUST write a RESTful API for the server-side code with C# WebAPI.
• Examples of applications you could build are those that manage:
  • Course/Instructor reviews
  • Movie/Music reviews
  • Financial information (bills, accounts, payments, etc)
  • Course notes by semester/subject and class
  • Any data in an area of interest

You will improve the data management application you built by introducing a true persistence component. The requirements are that:

• Data that was previously stored in a static class must now be stored in persistent storage (I.e., a file system, a database, etc).
  • That is, when the project is stopped and then started again from VS, data that was added/deleted in a previous session should have the appropriate state.
• There must be an EC layer that provides persistence-related business logic separate from the WebAPI communication layer of server-side code
• The persistence component must synchronize identifiers.