Konnect Responsive Ticketing System Backend Implementation

1.0 - CHALLENGE OVERVIEW

 

Welcome to the Responsive Ticketing System Backend Implementation challenge! In this challenge, you will need to build the backend services and the DB model for this application as per the provided architecture.

1.1 - PROJECT OVERVIEW

The client wants to build a simple service desk ticketing system for MSPs (Managed Service Provider). The custom application will be a responsive web application built in .NET.

 

This assembly will provide the the backend services, stored procedures and part of the pages as detailed below for Codes, Regions, Logs and Root Cause.

1.2 - COMPETITION TASK OVERVIEW

A complete list of deliverables can be found in the TopCoder Assembly competition Tutorial at: http://apps.topcoder.com/wiki/display/tc/Assembly+Competition+Tutorials

Note: Extensive implementation notes are provided at method documentation on UML Class Diagrams. Please follow them for implementation.

Note: Please read the whole Application Design Specification first. All the details not mentioned in this specification are provided in that document.

1.2.1    Backend Services

This challenge is responsible for all services listed in the UML diagram. All Services, Controllers, Models, Exceptions - all methods are in scope. Please also see the provided Swagger API definition

1.2.2    Database Model

This challenge is responsible for implementing the provided data model and associated business logic as per the Application Design Specification

1.2.3    Sequence Diagrams

All flows as depicted by sequence diagrams are in scope for this challenge.

 

1.3 - TECHNOLOGY OVERVIEW

-    Windows Server 2008+ / Azure with .NET Framework 4.5 installed

-    SQL Server 2012

-    Microsoft IIS 8.5

-    C# 6.0

-    .NET Framework 4.5.2

-    ASP.NET Web API 2.2

-    HTML5

-    Unity 4.0 http://unity.codeplex.com/

-    Log4net 1.2.15 http://logging.apache.org/log4net/

-    AngularJS 1.5 https://angularjs.org

 

 

1.4 - DOCUMENTATION PROVIDED

Documentation and Applications that will be provided to registered members via forums:

 

1.5 - TESTING

 

Please include unit tests to verify your application successfully meets the requirements of the project.  You should only provide functional tests for service classes - there is no need to test the entity and exception classes or no need to provide failure tests for service classes.

 

Final Submission Guidelines

- Completed code for the application backend (see architecture documentation and section 1.2 of this challenge spec above)
- A complete and detailed deployment documented explaining how to deploy the application including configuration information
- Please provide a demo video of your submission (unlisted video on Youtube/ mp4/ swf file)
- Unit tests to verify your application successfully meets the requirements of the project.