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?

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?

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.

Events?

External event- an event that occurs outside the system, usually initiated by an external agent or actor.
• Agent (actor) or organisational unit that supplies/receives data from the system
• Customer- order/return
• Must be defined clearly by its name (event name). Description should include the action that the external agent wants to pursue
e.g.) customer places an order – this title of an event describes the external agent (customer in this case) and the action that the customer wants to take (place an order for product).


Temporal event- an event that occurs as a result of reaching a point in time
• Generated by system automatically
e.g.) payroll or store statistics reports (end of day stats/footfall etc.)
• No agent/actor required to make demands, system generates outputs when they are needed periodically
e.g.) internal outputs needed include....management reports, operational reports, internal statements and documents
external outputs needed...statements, status reports, bills, reminders and quotes


State event- an event that occurs when something happens inside the system that triggers the need for processing. Also called internal events.
e.g.) stock falls below minimum stock level (reorder level) so the system initiates prompt to reorder or reorders automatically

Using Predictive approach to SDLC:

Project planning – to plan a schedule and obtain relevant approval in order to go ahead with the proposed project.

Analysis- to understand the processing requirements as well as the needs of the business .
Design- to define the solution system based the requirements and the relevant decisions from the analysis section.

Implementation- to construct a prototype and test it to ensure the system operates as it should and nothing is missed out. Users and the necessary personnel need to be trained to use the system.

Support- to keep the system updated and in optimum functionality and to keep it running to improve the user’s experience.