Thursday, 7 January 2010

Use Case Diagram

This is one of my Use Case Diagrams.
It is currently showing the way in which the agent would interact with the system in order to compose a statement of account before sending it through to the vendor's solicitor. statement of account is just a fancy phrase for asking for the commission charges.

Wednesday, 6 January 2010

Title Page

well.... i wonder what we can do for that?

do we include a logo, images or do we make it look like a promotion of Sellit Quick and Soon or make it look funky or very professional??

hmmm...

Tuesday, 5 January 2010

ONE OF MY ACTIVITY DIAGRAMS

i thought i should maybe include one of my activity diagrams in my blogs.

this activity diagram shows the workflow of buying and negotiating of a property. i really think that this is how an activity diagram should be.


Event Table: how many events?

before i started i thought that i would find it hard to think-up the relevant events to address in the events table. after a while of careful thought and understanding i seem to have bombarded my mind with the amount of events that could be included.

i have decided to call it off at 13 events as they are the most relevant cases.

Event Table: 'Source' column

i have realised that the 'Source' column on the event table will be mainly the agent because the agent is the only individual using the system unless it is used on the internet by the buyer or vendor.

or does the source refer to where the information is coming from instead of who is entering it into the system?

Sunday, 3 January 2010

Final states within an activity diagram

I have come to realisation that within an activity diagram it should be possible that there are 2 (or more than one) final states.

This is because the client (agency) has noted that the vendor or the buyer can pull out the transaction or process throughout most of the case study.

therefore there should be a final state where the vendor or buyer has changed their decision to buy or sell.

isn't that how it should be?

Monday, 7 December 2009

Don't be Fooled

A LOT OF PEOPLE SEEM TO THINK THAT EVERY LITTLE TINY ACTIVITY NEEDS AN ACTIVITY DIAGRAM...

I JUST WANT TO NOTE THAT REMEMBER THE DIAGRAMS ARE SUPPOSED TO BE FOR PRESENTATIONAL PURPOSES...SO LONG AS U CAN UNDERSTAND THEM AND PRESENT THEM WELL ENOUGH THEN YOUR ACTIVITY DIAGRAM IS CORRECT.

THIS MEAN YOU DO NOT NEED TO CREATE AN ACTIVITY DIAGRAM FOR VERY SMALL ACTIVITIES, HOWEVER YOU CAN INCORPORATE THE LITTLE ACTIVITIES WITHIN THE DIAGRAM FOR THE BIGGER ACTIVITIES. IT ONLY MAKES SENSE TO DO IT THAT WAY BECAUSE BIGGER ACTIVITIES WILL ALWAYS DEPEND ON SMALLER ACTIVITIES WITHIN THEM.