This past weekend I submitted our online application for a new user registered port with IANA. Here is a simple client server model depicting requests and responses.
The protocol, Multiple Listing Service Network (MLSN), will involve online users and applications querying a real estate database of listings.
I'll post more diagrams and information regarding this protocol/port as we draw closer to our application being approved. :)
--Corey
This is a first pass at building a use case model for real estate project management. As you can see on the left side of the system, there are five actors: the project manager, salesperson, administrative assistant, buyer, and the seller. On the right side of the model are three external systems which interface with the model. They are Google Wave, SalesForce, and OpenProj.
The system's use cases are self-explanatory and may need refactoring. Again, this is a first pass. In addition, I'm sure more use cases will rear their heads so I expect the number of use cases to grow.
Feel free to leave comments and suggestions for this model is open for public comment.
--Corey
Continuing from Part 1, this modeled diagram represents components of a concept reputational application. As do most web applications, the system is comprised of three tiers: client, application, and the database layer.
 |
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 a non-profit organization, the gr8c's central purpose is to help the real estate community. One way to help is to create awareness for the global real estate community with a designated day called Global Real Estate Day.
As always, I am open to ideas so please feel free to post comments.
The day will be announced in the coming days.
--Corey
Here's a list of my resolutions for 2010.
I resolve to:
I look forward to accomplishing these goals for 2010.
-- Corey
