The user of the system interfaces with a browser on a desktop computer or an application on a mobile device. The middle tier is comprised of JBoss Application Server and Apache’s ServiceMix. I chose JBoss AS to allow for enterprise javabeans to be used along with all of the lovely enterprise features such as remoting, security, transaction management, presistence, messaging, resource pooling, concurrency control, and directory services.

I included a servicemix implementation component to jboss for deploying a webservice to external webservice clients. In addtion, servicemix allows for xmpp implementations along with messaging services over Java Messaging Service (JMS).

For authorization, an OpenID provider is accessed for warehousing usernames and passwords. Having users’ credentials stored by an OpenID provider removes the potential possibility of a security breach regarding usernames and passwords.

Lastly, I selected PostgreSQL for the application’s database layer. I have used PostgreSQL with many projects previously while the zero licensing cost to implement is most ideal.

To continue this development drill, I will next blog activity diagrams from using the potential use cases.

–Corey

As you can see, I’ve defined just three types of Actors: Professionals, References, and Guests. I’ve also defined two external entities, OpenID and a web service. The scenarios listed are a first pass and expect to refactor their associations while adding/removing some. I won’t go into detail here regarding the scenarios, but if you would like to follow the wave and/or offer comments, please feel free to contact me on google wave. My gwave account is corey.leong@googlewave.com.

My next step in this process is to create component, deployment, and behavioural diagrams. I’ll post these also to my blog in the future.

–Corey