Business analysis - system vs business processes in flowchart

Hi,

I would like to differenciate between system processess / business processes as well as processes take place as a result of user interaction with the system.

Creating a busineess and system only flowchart, I think placing any processes such as user interaction with the system is incorrect. for example:

A user goes to a web site, select a relationship type from radio buttons and then select A from a list box and then select B from an other list box. Then click the Add button to create a relationship between A and B.

In the flowchart the process should NOT be as:


select Relationship Type  ------ X  ----->  select A ----->  select B ----> Add relationship
                                        ------ Y   ------> do something else

I am not sure what type of process flow is called above?


On the other hand I think the correct flowchart should be:

Relationship Type   ------- X  ---------------> Create relationship  
                               ------- Y  ----------------> do something else

And this is the system process.

Am I correct?

Thanks
shmzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kdebugsCommented:
Hi shmz,

I suggest that you get yourself a book called UML in 24 hours. It's an excellent starting point into uml diagramming.

The paragraph that describes the action is called a "use case."

In this case, since there are no decision points it would be a pretty linear "activity diagram" (that's just a fancy, more uml-ish name for a flowchart).

From top to bottom, it would be:

Start
  |
Select from radio buttons
  |
Select from list "A"
  |
Select from list "B"
  |
Click the "Add" button
  |
End

Now, here is what I think MOST important when it comes to design: do whatever works for you and your team. Just because you know uml and are able to throw sofisticated-sounding terms all over the room, doesn't mean you must model every single transaction with 6 different diagrams.

I'm not sure I understood correctly what you're really asking here, but your use-cases are what will let a lay-person understand what your system does (and maybe write end-user documentation for it), and your flowcharts will help a programmer implement it (those would be my starting points). Then, keep in mind that a single flowchart can take care of a large number of use cases.

Alex
0
shmzAuthor Commented:
Hi Alex,

The system and business processes I am trying to identify and place in my flowchart are used purly for system/business 'ANALYSIS' purposes. It is not used by the programmer.

Hence I think your suggested approch would not help with analysing a system and for example finding gaps within a system....

however thanks for your input.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kdebugsCommented:
Like I said, I didn't understand what you were asking, exactly.
0
shmzAuthor Commented:
no answer provided
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Visio

From novice to tech pro — start learning today.