Hello Dr. Douglass,

I assume that this is the most appropriate sub-forum in your site for asking questions on modeling the running an organization (i.e., things ‘higher’ than the work of designing the product (the actual operational system)). Namely, how the ‘organization’ goes about designing its product, requirements collection, product management and project management, IT support for management – and much else besides.

My questions, from the most specific to most general:

Question 1: I assume this what is these days termed enterprise architecture?

Question 2: What term is appropriate to use for the flow of information between these three teams: (i) the requirements and analysis team, (ii) the design team, and (iii) the safety analysis team? In one of my work emails I have used the term “business flow”. How correct is that?

Question 3: I have seen various graphic X-layered diagrams describing companies/organizations, e.g., Four-layered: (e.g., Business (top), Function, Information, Data). I have noticed also the Zachman Framework, from which various layered models were derived. I have also noticed Caminao’s Pagoda framework.

But I am not clear whether the intention of these layered models is: (A) to model the operational system -or- (B) to model the company/organization. Seems to me you need both, i.e., you use the same layering concept: one instance of an X layered model for the operational system, and a separate instance of the X layered to model the company/organization. I have never seen this written explicitly, but that’s what seems to me. Your opinion?

I have just completed modeling the top-level design of our company’s product in sysML/UML. Now there is a need to move up a level.

Thanks in advance.

Avraham