Implementing bussiness logic with a large number of business rules and processes
We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.
Implementing bussiness logic with a large number of business rules and processes
We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.
Implementing bussiness logic with a large number of business rules and processes
We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.
Implementing bussiness logic with a large number of business rules and processes
We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.
Implementing bussiness logic with a large number of business rules and processes
We are currently working on a project that heavily relies on a database.
Among many tables the main focus is on table “data” which is linked to another table “data_type” as many-to-one, which is then linked to table “data_operation” as one-to-many.
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
Describe business logic with diagrams
I am currently developing a web application for my thesis.I was asked by my professor to make diagrams to describe the business logic.
Since I don’t have a prior experience, I am pretty confused with all the terminology.
I managed to clarify,I think, what business rules and business logic are, but I can’t find out how you describe the business logic. Is it something particular or is it something more general? Do I need to learn UML? Does the fact that I use MVC affects the way I’ll describe it?