Hello

I'm designing a directory listing system with feedback and a quoting engine. The UI and use cases have been written and I’m now starting to work on the ER diagram and module split but I’m undecided on how many different modules I should break this project into. Can anyone offer some advice on this?

For example - The directory listing has two main requirements:

1.      Provide a registered user the ability to create one or more directory listings to advertise their business.

2.      Provide the ability to search on directory listings, view the results then drill into the details on a business.

I could split this across two modules, let’s say a Directory Creation module containing a wizard and a Directory Listing module which contains the search functionality, presents the results summary and allows the user to drill down and view the listing.

I could also apply this model to the feedback and quoting engine, before long there’ll be a lot of modules to manage. This may be the correct approach but I’m not sure. Can anyone provide me some advice or guidelines on the benefits of breaking up pieces of functionality into separate modules or the case to keep them under one roof?

Thanks in advance

Adam

ok i'll have a look at that, thanks.

Adam