• Post Reply Bookmark Topic Watch Topic
  • New Topic

Project Module Structure problem  RSS feed

umesh aum
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am not sure if this is the right place to ask this question

I need your valuable suggestions regarding an E-Commerce project structure..Below is a brief summery of the requirement
We need to develop an application with one store front (i mean user interface) and one kinda back-office from where we can control all the aspects with the respect to the store front.
Platform on which this application need to be developed is J2EE.
Its also quite possible that in future we may also need to develop another interface to run/control or admin various other things all related to this application.my question is about the application structure as how we should organize all these modules?
Here is what currently in our minds
1) We can simply create a web-application and than can create a folder structure as per the requirements as i described above
e.g we can create two module/package storefront and back-office and can put all Action/BO/DAO and other objects under this tree and same is the case with the second Interface.

but i can see a potential problem in the above structure that these two Interface become coupled to each other,any change in the storefront will force to deploy the application as a whole vice-versa

Please provide your valuable suggestions/feedback how best we can organize these Interface so that even they have a solid relation with each other but on the same time they can be develop and exist independently..

Thanks in advance

Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!