This is the final post in a four (4) part series exploring ConcourseConnect.  The first three parts can be read here: Introducing ConcourseConnect to Team Elements Users, Major Functional Changes to Team Elements in making ConcourseConnect, and ConcourseConnect: Improving Upon the Team Elements Core Modules.

Now for the technical overview...

Team Elements is a web application, based on the Enterprise Edition of the Java Platform, and is designed to be portable and scalable.  Early Team Elements work introduced an MVC framework for separating the visual appearance of the application and the underlying business rules.  The MVC implementation allows for security constraints for all web requests, and over the years various components have been added to share database resources, integrate a rules engine, and perform background scheduling.  Those are all great things for modern web applications.

So what could be better?  Well, it depends on who you ask.  At Concursive, we evaluated many options, but in the end, the need to drastically increase flexibility of the application, without sacrificing simplicity, performance and scalability, won hands down.  We also wanted a better user experience.

So how did we do that?

This is the third post in a four (4) part series exploring ConcourseConnect.  Part 1 can be read here: Introducing ConcourseConnect to Team Elements Users.  Part 2 can be read here: Major Functional Changes to Team Elements in making ConcourseConnect.

ConcourseConnect improves upon several of Team Elements' modules and adds many more... here's a rundown of all the modules...

This is the second post in a four (4) part series exploring ConcourseConnect.  Part 1 can be read here: Introducing ConcourseConnect to Team Elements Users.

Concursive Corporation recently announced a new product called ConcourseConnect, which is built on the Team Elements platform.  Since as of this writing, the free version of ConcourseConnect is yet to be publicly released, I'll explore the various improvements by focusing on fundamental differences, major functional changes, overall functionality and technological changes.  Some of the information is subject to change, so for the most part I'll focus on high-level features that shouldn't.

ConcourseConnect is being touted as a business social software networking platform.  As a testament to the Team Elements platform, building out a social networking application took the developers about 6 months.  That was after a lot of product management responsibilities which helped orchestrate the desired capabilities.  The ongoing plan is to review the ConcourseConnect code base and contribute back to the Team Elements project.  Future blogs will discuss the direction of Team Elements, migration to ConcourseConnect for those that want to, and any other fundamental changes.  Some of you may find that moving to ConcourseConnect is more desirable given the feature set, others may want to stick with the project management capabilities of Team Elements.  

Now on to the fundamental differences...