Benton Bovée

Based on Basel Committee report of January 2013.

This figure is my depiction of information essential for anyone unemployed in Virginia.

The U.S. DoD has realized limited success at enabling creation of multiple architectural description master data and models via the DoDAF. Based on partially federated EA models successfully created for two DoD HQ organizations, ASA(ALT) SoSE and SAF(AQXI), this paper presents findings, recommendations, and proposes a meaningful, constructive, and proven way forward for DoDAF.

The value of any Enterprise Information Architecture (EIA) is assess-able in terms of its utilization to enable change management throughout the System Development Life Cycle (SDLC). The presented framework depicts generic concerns at the intersection of natural human thought processes and business perspectives; features differentiating it from other EIA frameworks are:
• Enabling comprehensive trace-ability for any organization endeavor to effect change management;
• Leveraging natural… Show more

The value of any Enterprise Information Architecture (EIA) is assess-able in terms of its utilization to enable change management throughout the System Development Life Cycle (SDLC). The presented framework depicts generic concerns at the intersection of natural human thought processes and business perspectives; features differentiating it from other EIA frameworks are:
• Enabling comprehensive trace-ability for any organization endeavor to effect change management;
• Leveraging natural human thought processes patterns in any SDLC;
• Basing business perspectives on National Institutes of Standards and Technology (NIST) perspectives;
• Augmenting NIST perspectives with analytical/architectural perspective; and
• “Five Ws” concerns are at intersections of aforementioned subjects and perspectives (instead of assuming concerns are identical from different perspectives).
The original link (http://www.ucmss.com/cr/main/papersNew/papersAll/IKE4145.pdf) no longer works. Show less

This paper in response to an open Request for Information (RFI) for the next version of the Semantics of Business Vocabulary and Rules (SBVR) standard. Contents introduce perceived inconsistencies and incomplete coverage of core ideas. Similar to the UML publication process, once they considered and incorporated approved ideas, they archived the publication it to accommodate RFI responses for the next standard version.

This presentation covered the classification, identification, specification, scope and applicability of business rules (BR) and their development and BR management (BRM). I accompanied the preceding with the status of related BRM standards and their holistic coverage, primarily relative to the ZIFA.
Many research findings shared implied that two dimensions of concerns and viewpoints are necessary but an insufficient number (i.e., what is a "What" may not be data, and it may not be a… Show more

This presentation covered the classification, identification, specification, scope and applicability of business rules (BR) and their development and BR management (BRM). I accompanied the preceding with the status of related BRM standards and their holistic coverage, primarily relative to the ZIFA.
Many research findings shared implied that two dimensions of concerns and viewpoints are necessary but an insufficient number (i.e., what is a "What" may not be data, and it may not be a "what" from each perspective; one persons' "What" may be another persons' "How"). I presented some 3-D and 4-D models using triangular and rectangular pyramids respectively.
I gave this presentation during half of a monthly meeting. Show less

I identified the unique Use Case relation concepts from UML versions 0.8, 0.91, 1.0, 1.1, 1.2 and 1.3, mapped them to each other, and proposed a new set incorporating all those ideas in a more simple intuitive notation set.

This paper was in response to an open RFI which the OMG issued for UML version 1.4. Once they considered my ideas and incorporated those they accepted (most of them; most likely since others independently submitted corroborating ideas), and published that version… Show more

I identified the unique Use Case relation concepts from UML versions 0.8, 0.91, 1.0, 1.1, 1.2 and 1.3, mapped them to each other, and proposed a new set incorporating all those ideas in a more simple intuitive notation set.

This paper was in response to an open RFI which the OMG issued for UML version 1.4. Once they considered my ideas and incorporated those they accepted (most of them; most likely since others independently submitted corroborating ideas), and published that version, they archived the paper so they'd only show the RFI responses for the next version. Show less