Big Smokes Cigar - assumptions about the Catalog and the Order

Hi to everybody,
I would know your opinion about the assumption that a database for the Catalog(category + products) already exists. There is no mention of this in requirements. It is possible also that it is provided by a subsystem.
Furthermore, also if not required by assignement, we don't know where the data order will be store after the end of the transaction.

Regards,

Andrea

I think you'd be on very shaky ground assuming away a huge part of the assignment.

It's your call but I'd assume a blank sheet of paper with the exception of the existing systems mentioned in the requirements. Think about it - if the requirements take the time to mention integration with existing systems such as inventory, they'd probably mention something as huge as an existing subsystem serving up catalogue data.

At the end of the day you can make all the assumptions you like; just don't go making more work for yourself than is necessary.

Stick to fulfilling the requirements you've been given.

Thank you Jonathan,
most probably it is as you say, if there was a Catalog subsystem would be mentioned. It's more credible a database,we can accept this assumption, so our system could use JPA entities to retrieve data. My doubt is on a specific issue:since it is not indicated anything about the source of this catalog, may be our system should provide a DAO interface for the underlying storage. Someone is in agreement with this possibility?
Regards

I agree. Its given that Inventory system is an existing system and it has to go hand to hand with Catalog system. So we can make safe assumption that catalog system is also an existing system.

-R. Roy