Hello, I am a student web developer. I am largely comfortable with database design and development, but I struggling with a somewhat peripheral(?) aspect.

In order to create a database system for a business, how does one analyse the process of the latter, with no prior knowledge thereof.

I have looked into UML activity diagrams and IDEF0/IDEF3 for process mapping, but I am curious how it is done in the 'real world'. I have a relatively short report to write on the matter and I am worried that I am going in 'too deep'.

Any advice/direction would be appreciated.

how does one analyse the process of the latter, with no prior knowledge thereof.

You don't! because you will get it wrong.

The only really sensible way is by asking people who are in that particular business who they work. It is no good you making something that is how you think it works or should work

Certainly, you can map the process using diagrams or flow charting, but to know the process take experience.

There are plenty of very public examples of developers getting it wrong even after consultation, usually because they consulted with managers NOT the people who actually do the job!

Chris, I absolutely agree with you, but this is where I am confused.

I have been given an assignment which asks me to create maps of the processes of a business, with a rather shallow case study. I don't have any workers to consult, which would be the first thing I would do in the 'real-world'.
I have also been told just to 'create process maps', without any guidance on which modelling language to use (I didn't even know they existed until I did research into process mapping).

Really I suppose I'm asking:

• Which modelling languages do people actually employ in order to analyse the processes of a business?
• (And) How do I analyse a business that I have no experience or contact with?

You don't have to answer the second question, I'll just make something up with what I have. I am interested in what people reveal for the first one though!

Then as it is a project, which are not really meant to come up with a new and revolutionary paradigm for a real business model.

You choose something to model that you know how to do, which may or not relate to business. projects and assignments are to find out if you understand the principles of creating the project outlines and schemas.

You probably know exactly how to do something that happens every day in companies all over the world.

Finding a supplier for a particular component.

For you to analyse that process you can create an analogue of it that you can follow or perform, it might be something as simple sourcing a supplier for your next t-shirt.

Sure you probably go to your nearest "Gap" store and buy one, but you want to find a specific shirt with particular features, then you document and "map" the process of finding that shirt.

What do you need to know before you decide that a supplier can meet your exacting requirements?
Those questions and the answers you need to get from a possible is the business process.

The items you then need to consider when scaling up from supplying one shirt to supplying thousands then become relatively simple.

Best price, price breaks, delivery scheduling and so on.

I see. Perhaps the whole concept of assignments hasn't sunk in yet; I think I am my own worst enemy at the moment.

Thanks for your advice! I know how to create UML activity diagrams through my own research, so I suppose I will use that technique. As for the business analysis, from what you said I shall keep it straight-forward; which entails telling myself: 'No no no, stop questioning everything so much!! Just write it down you pedantic incarnation of the word ridiculous!!'

'No no no, stop questioning everything so much!! Just write it down you pedantic incarnation of the word ridiculous!!'

Ha! been there, still doing it, still wearing the thirt!

just consider that:
Assignments are a test of understanding not necessarily of knowledge.

Exams are a test of memory rather than of understanding.

Just out of interest I looked-up the difference between 'understand' and 'knowledge' in the Oxford Dictionary:

Knowledge
facts, information, and skills acquired through experience or education; the theoretical or practical understanding of a subject

(I burst out laughing when I read the first part).

Understanding
the ability to understand something; comprehension
(The definition for 'comprehension' in the same as above interestingly)

Huh? Okay, let's look up 'understand' then…

Understand
perceive the intended meaning of

So really by

Assignments are a test of understanding not necessarily of knowledge.

you meant:
Assignments are a test of theoretical understanding (i.e. knowledge of facts and information, not skills).

Wait, how can I theoretically explain how I have practically done something? (Which is what I have been asked to do.)

It's a paradox!

Also, I agree with you on exams!
Now let's look up 'memory' in the dictionary!!

Just kidding! (But really I did).

… Hmm, I'm sure there was something I was supposed to tell myself.

Bugger!!

I've been out-pedanted

Hahaa, I win!!

Thanks for your help by the way Chris!