Developing and Integrating a Web Application

crosbyBusiness Need

Crosby initially needed a corporate website developed that would be an information source for investors and potential investors alike. Their requirements included a flexible design that would grow with the company and its needs, be easily updated and managed and would provide easy access to information that investors required to make informed decisions about investment opportunities.

During the discussions about the website, Crosby identified additional needs for a web application that would be used to update the daily NAV value and provide historical information about past values. They also needed another web application that would be used to email investors and subscribers daily NAV information, monthly reports and announcements related to the company and its funds. The email application would need to have multiple functionalities including import/export email addresses, mailing list management and automatic email functionality.

Our Solution

The team at emagine began by developing an architecture for the website based on the information and content that would be presented. This architecture would be the basis for the design and how visitor interactions would be handled. Once the site design was approved by the Crosby management, content and documents were added and web pages created. When all the pages were ready, the site was deployed to our test site so that Crosby management could review and provide feedback while the web applications were developed.

Concurrently, our development team started work on the web applications that Crosby required. Understanding that the most web friendly and flexible database is mySQL, we tailored our development around it. Starting with the NAV application, our development team prepared a requirements document that detailed all the functionalities that would be available in the application and used by our development team to build the application.

The application was designed to work on the backend with a secure login that would allow access to only approved users of the application. Once the user was logged into the application they would have a number of actions available to them. The user would be able to update the NAV by selecting the date and adding the NAV values for the selected fund. They would also be able to import or export the entire contents of the database in either a CSV or text file so that it could easily be moved or backed up. Lastly, the user would be able to delete information from the database in case any error was made during data entry.

The NAV Management application was integrated into the main Crosby website in 2 locations. First, the daily NAV information was displayed on each page of the website so that investors were constantly aware of the value of their investment. Secondly, the application was integrated into the historical NAV section of the website so that visitors and investors would be able to select dates and retrieve relevant data from the database to display on screen.

The second application was the Subscriber Email application that would allow Crosby to email confirmed subscribers with information, documents and NAV information. This application worked very similar to the NAV Management application in terms of base functionality, so its development was fast-tracked with similar code. This application was integrated into the main Crosby website so that visitors would be able to register to receive information directly to their email.

Once all functionalities were tested and approved, the Crosby website was moved to the live Crosby domain so that the site could be retested and taken live.

Leave a reply