Task 1

Implement Ticket management application that provides different abilities for users (Venue manager [1], event manager [2], authorized user [3] and anonymous [4]); User can have multiple roles (1 – 4). All user roles can act as anonymous user; User roles:

• 1. Anonymous:
  • a. View all published events and theirs tickets availability;
  • b. Register and login into system;
• 2. User:
  • a. Purchase tickets;
  • b. See purchase history;
  • c. See cart;
• 3. Event manager:
  • a. CRUD operations on event entity;
• 4. Venue manager:
  • a. Manage users;
  • b. Setup venue;

Figure 1 – DB Schema:

Figure 2 - Venue map:

Requirements:

• 1. Use .NET Framework 4.7.2 and ADO.NET for development;
• 2. Ability to create Venues:
  • a. Venue consists of layouts; Layout is set of Areas. Area consists of seats (fig. 2);
• 3. Ability to create Events;
• 4. Create solution with 4 class libraries projects.

  • a. 1-st - Data Access layer with classes and interfaces that allows to manipulate core entities using ADO.NET. Use Repository pattern to give access for all entities. Only repository interfaces and domain entities classes should be public. You should Create, Delete and Update Event via store procedure.

  • b. 2-nd - Business logic layer should reference to DAL and proxy all calls with validation logic.

      i. Validation: adding business logic validation, for example: check that we do not create event for the same venue in the same time. That we don't create event in the past.
    
      ii. Event: event can't be created without any seats;
    
      iii. Venue: unique name;
    
      iv. Layout: layout name should me unique in venue;
    
      v. Area: area description should be unique in layout;
    
      vi. Seat: row and number should be unique for area;
    

  • c. 3-rd - Create unit test project (should test validation logic on business logic). Include positive and negative use cases. It should work multiple times in any order (be independent and repeatable);

  • d. 4-th - create unit test project with integration tests. Integration tests should cover event management API (create event, update event and delete event); Test data should include at least: one venue, two layouts, at least one layout should have two areas, each area should have 5+ seats;