Corey.Leong.Name

Tagged: diagram RSS

• 

  coreyleong 7:46 pm on 2010/01/05 Permalink | Reply
  Tags: diagram, google wave, model, openproj, project management, real estate (5), salesforce, uml (2), use case   

  RealPM Model Use Case Diagram 

  

  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

  coreyleong, and Kelley Martin are discussing. Toggle Comments

   
  • 

    Kelley Martin 7:54 am on 2010/01/06 Permalink | Reply

    couple things I am thinking at this point to possibly add is:
    1. more responsibility for admin assistant: as far as logging activity with buyers and sellers, AND communicating with sellers regarding getting feedback, and information, scheduling for buyers, etc
    2. buyers and sellers more vested in their portion of the project……. they have to want this to happen and need to be contributing a bit as well, there are things that they provide and their involvement.

  • 

    coreyleong 8:16 am on 2010/01/06 Permalink | Reply

    I see something I missed. The project manager needs to update the project wave in gw. We need to add an include or extend from ‘Manage Project’ to the google wave actor. Revision number two will include this.

  Reply Click here to cancel reply.

  Name (required)

  Email (required)

  Web Site

  Notify me of follow-up comments via email.

  Notify me of new posts via email.

   
• 

  coreyleong 12:48 am on 2010/01/05 Permalink | Reply
  Tags: component, deployment, diagram, GR8C (3), realrep, reputation (2), uml (2)   

  Building The Perfect Reputational Beast, Part 2 

  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