Models, models and models...

Now, reaching the 3rd step of planning phase, I'll be using an E-R Model to visualise the data requirements.

Re-analysing the activity diagram and front-end layout, I summarised the data requirements as follows.

My First Draft

Further polishing it...

My Second Draft

Does this look good?

You might be wondering why there's this boxed-up part that is excluded from the rest. That is because, it isn't possible for me to have the database of the bank in real life!

I know this is just a prototype, but I want to make it as realistic as possible.

Just a historical background on this idea,

I initially wanted to integrate PayLah into this system. I was planning to use it as a third party software to help make the transaction possible despite it being a prototype. (I wanted it to be as practical as possible.)

However, upon further analysis, this became an issue. The stall owners will receive their payment via PayLah, but without knowing who made the order. Thus, it became impossible for the system to notify the user who had made the order. We have to some how integrate Paylah into the system and not treat it separately. This idea was scrapped away eventually.

A possible solution for this is to register as a bank developer, which will give me access to real-life APIs. But, I won't be implementing this for this prototyping project.