Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
No where I’ve red actually explain what goes on the top versus the side of a crud matrix?
For example here, why is “Product”, “Order”, “Item”, “Payment” and “ERP Order” along the top? Why is “add product” on the side? What is the rule being used? Is it that the functions you are planning to implement are on the side and the data store you get it from is on the top?
It doesn’t really matter and there is no single standard way to do it. It depends on context, personally I usually put the (Create, Read, Update, Delete) activities along the top and the domain object (or tables) down the side. However another common format is to place the scenarios/usecases down the side, the domain objects along the top and the crud activity in the box. The key thing is to ask your self why you are doing the CRUD matrix. To analyse the problem, clarify your understanding, record progress, demonstrate test coverage, convey information to a third party. Then decide which format is most appropriate for that objective. Don’t get hung up on form, get hung up on objective.