Where to store data types and data size

[Khurshid Akbar]

We need to store information on functional things like which actor is
authorized to add/update certain data items or what should be the type
and size of the data item.
If we store this information in Use Case then they are repeated and have
to be updated in multiple places. Please suggest where acrhitect should
be be storing this type of information so that developer can make use of
it.

[Geert Bellekens]

I think the best way to to model "Business Concepts" as on a CIM level.

You can then create relations between Actors and Business Concepts and store the CRUD details on that relation.

Business Concepts should then be refined into Entities on the PIM level, and database tables on the PSM level.

Or you could leave out the Business Model level, and maintain the relations between Actors and system Entities.

Geert

[Thelonius]

Geert - "CIM" meaning "Conceptual Information Model"? Thanks - Jon

[Geert Bellekens]

Geert - "CIM" meaning "Conceptual Information Model"? Thanks - Jon

CIM as in Computational Independent Model (ref. OMG's MDA)

Geert

[beginner]

We need to store information on functional things like which actor is
authorized to add/update certain data items or what should be the type
and size of the data item.
If we store this information in Use Case then they are repeated and have
to be updated in multiple places. Please suggest where acrhitect should
be be storing this type of information so that developer can make use of
it.

Actually I would attach Business Rules to the Actors. You can create those by using Requirement elements and stereotyping them with <<Business Rule>>. There are probably some profiles which offer this kind of stereotype in a broader context.

b.