My client has an existing Microsoft Access application, that we would now like to move to the Web. It has about 150 tables and numerous forms and reports, of course.
Full details of the workings and logic of the current software will be provided.
We would like to start with the basic master data. If things go well, we can continue other modules with the selected vendor. This Module is comparatively simple. Other phases are more demanding.
So what we need is
1) We have a table of products (items that can be procured)
2) These products have categorised details about them. For example Main Features, Standards, Installation Requirements, Warranty. These will be used later for comparing or evaluating items.
Not all items have the same details. For example, a computer may have installation requirements, while some medicine does not.
Please see attached file for a rough idea.
3) These products are in cascading Product Groups.
For example, Group 300000 has under it Groups 310000, 320000, 330000 etc
Group 320000 has 321000, 322000, 323000 etc
321000 has 321100, 321200 etc
4) We will also store a table of suppliers and their details (address etc)
5) Each supplier can be linked to multiple items that they can supply
6) When looking at Products, we can see which Supplier supplies which Products, and possibly select some suppliers for further interaction.
7) We can group Products together so that they are procured together (for example a computer, a keyboard and a mouse)
8) We will need a login system with at least two levels of users: Operator and Manager
9) Reports, of course
10) There may be some refinement of these details, but probably not much.
Subsequent modules will probably require more than one developer working at a time, so we will be inclined towards selecting a team, rather than an individual developer, though we are not closing individual developers out. So if you do have a team, please mention it.