hi Arie,
I replied to one of your threads earlier, and again.. there is no "cookbook" - you need to find out what works best for your team considering the landscape and tools you can actually use.
considering UI5 development, case you want multiple developers to be working in parallel on the same code-base, I would advise you to have a development environment locally to each developer (a web-container, SAP does have a skinned version of Oracle's Orion called Web IDE which I have been using) while keeping the code centralized in a repository - probably a git repository.
about Componentisation, you can read more at SAPUI5 SDK - Demo Kit - there was no need in things I've done in the past for such, but it seems you can even have components in different contexts and you can request and load them as long CORS is not in the way.
the next obvious step is to have automated deployment tools, and you can use the same "automation" the SAP Web IDE uses, in some nightly script to pull files from git and deploy using one of the rest services under /adt ICF node (you can have a read on SREST package in ABAP, it reminds a distant bastard brother of JAX-RS 1.0) - case you are deploying into XS engine, I'm sure there are similar endpoints for such - so just re-use what SAP developed in your own custom script (give curl a try if you are running it as a shell script).
last, you confused me a bit on your "iView" reference.. but if I understood:
when you want to use "real" web-components, I suggest you wrap your UI5 artifacts either in Polymer or X-Tags - this will enable you to have real "web components" in a way that you could easily embed a whole UI5 application inside a "div" of another UI5 application, without styles and javascript clashes.
I can already tell it works quite well; I was able to embed a whole UI5 application using Personas 3 (which is pretty much an UI5 application itself) - this is possibly a good way if applications needs to be part of each other in isolation (or not totally as you still can dispatch event thru them using postMessage for inter-communication, as long they are on the same domain).
and explaining my suggestion above: usually people would wrap a whole application within an iView with URL isolation method, but of course, when you want a nice mesh-up of applications the iView concept of the Portal does not work well - for obvious reasons... if this is not the usage you mention with your iView related comment, then maybe I did not understand at all what you said there.
Hope somehow this info helps,
Dan.