SIM Module Architecture

Project Overview

Signator Investors is a broker dealer supporting a national network of affiliated Firms and Financial Advisors.   Signator Investors is a business unit within John Hancock, with the Firms independently owned (not by John Hancock) and the Financial Advisors are employees of those Firms and not John Hancock.

The intended users of SIM are Financial Advisors that are typically out on appointments with their clients and rarely spend the day in their office.

Some Advisors are tech savvy, but most of them are challenged when it comes to technology.  They prefer to call the help desk than do things for themselves.  For example  50% of the calls to our help desk are for password resets to a website where they have the capability to change the password themselves by answering a security question.

Financial Advisor and field staff smartphones/tablets are their personal devices and are not owned by Signator Investors.

The purpose of this project is to build such an app which includes admin web interface and mobile user app.

Competition Task Overview

For this challenge, we need to come up with a full design / architecture for the project covering both backend and frontend (admin web app and mobile client).

This includes:

• 1. Design the database schema for SQL Server 2012 and provide ERD
• 2. Design the data model and RESTful web services. Authentication must be done as described in the forum.
• 3. Design the admin HTML5 implementation (specifically, we just need to know which functions from which pages will be calling which APIs)
• 4. Design the mobile app (Ionic) implementation (specifically, we just need to know which functions from which pages will be calling which APIs)
• 5. Provide detailed assembly specs for the developers
• 6. The design must cover all business requirements and all pages from the prototype (both admin and mobile)
• 7. The design must take authorization into consideration, only users with correct roles can access admin console
• 8. The design must addresses video/audio content hosting. Please design and document the strategy for managing video/audio content and serving it to the mobile client (the content will be uploaded via the admin web app)
• 9. Design solution for content History management (archiving of old content, but ability to see all content every displayed historically in the database)
• 10. Final application must support HTTPs, make sure this is properly covered in ADS / assembly specs
• 11. The destination of the services / backend will be on Azure environment and probably, architects must keep this in mind and not do things that prohibit the application from running in such an environment
• 12. When deployed on Azure, we may deploy it with load-balancing, the architecture must work with load balancing without further code modification

Open Source Library

Apache v2 and MIT libraries are generally ok, for others please get our approval first.

TC Components

No TC components.

Technology Overview

• SQL Server 2012
• Windows Server / Azure
• C# / .NET
• RESTful services
• Angular.js
• Ionic
• HTML5
• HTTPS connectivity from the browser to the server

Documentation Provided

Register to download all documents from challenge forum.

Final Submission Guidelines