Challenging the System-level of RA

[GoogleCodeExporter]

Software and Version
********************
Reference Architecture

Reason for change
*****************
Up to today almost all of our applications only have one BC defined in the 
System. This leads to extra complexity in our source code where have the System 
at the top and one BC generally named core_bc. One reason to this could be that 
this part of the RA isn't well documented and/or the developers are missing 
knowledge of how to use it. Another reason could be that the way we build 
applications to day doesn't match the architecture and the System-level becomes 
useless.

My suggestion is either improve the documentation and the developers 
knowledge/competence of exactly how this part of the RA should be used or 
remove the System-level and make BC the top level component. 

Impacts
*******
- Improve/Rewrite documentation
- In case of keeping the System-level I suggest a smaller workshop on how to 
setup a project by the RA 
- In case of removing the System-level a rewrite of the javg-maven-plugin is 
needed.


Does this replace some existing, already approved, software
***********************************************************
N/A

Earlier experiences of the suggested software
*********************************************
N/A

Original issue reported on code.google.com by aaspl...@gmail.com on 18 Aug 2011 at 6:33