ASME MBE-1–2022 pdf download
ASME MBE-1–2022 pdf download.Model-Based Enterprise: Framework.
7.1 Stakeholders A stakeholder shall have an interest in a system of interest through a contextual concern. The stakeholder shall take responsibility and perform roles. A stakeholder may have more than one contextual concern, which shall be addressed by the stakeholder’s interest in a system of interest. Astakeholdermaybe an individual, group, ororganization thatholds contextual concern within a system ofinterest. A contextual concern shall be any interest in the system by one or more stakeholders and shall be contextualized by a viewpointthroughthe stakeholder’s role(see para. 7.3). Acontextual concernshall pertainto anyinfluence ofasystemin its environment. A stakeholder shall take one or more responsibilities and perform one or more roles. A stakeholder’s responsibility shall be defined by requirements for which the stakeholder is accountable as the primary cause, motive, or agent ofan activity.Astakeholder’sroleshallbedefinedbythefunctionalrequirementsoftheactorsandactivitiesofadomain,which have one or more viewpoints. All functional roles of an organization (e.g., engineer, manager, technologist, operator, analyst) should be encapsulated and accounted for by the stakeholder block of the MBE Framework. 7.2 Systems of Interest Asystemofinterestshall provide aboundaryforacontextualconcern. Asystemofinterestshall define whatis internal versus external ofa domain. The stakeholder’s interestin the system ofinterestshall conform to one ormore viewpoints and account for the activities, lifecycle phases, roles, responsibilities, and resources for a specific domain in which a stakeholder has a contextual concern. A system of interest shall be defined in one of the following domains (see Figure 7.2-1): conceive: the activities of imagining, specifying, planning, and innovating an MBE’s products and services. design:theactivitiesofdescribing,defining,developing,testing,analyzing,andvalidatinganMBE’sproductsandservices. 7.3 Viewpoints Aviewpointshallprovide the perspective to which astakeholder’s contextual concernshall conform. Aviewpointshall reconcile a stakeholder’s role and contextual concern for the stakeholder’s interest in a system ofinterest. A viewpoint shall be an architecture viewpoint as defined by ISO/IEC/IEEE 42010:2011: “[a] work product establishing the conven- tions for the construction, interpretation, and use ofarchitecture views to frame specific system concerns.”A viewpoint shall set the boundaries for the perspective that a stakeholder has when performing a role. Aviewpointshallbedefinedinoneofthefollowingviews, whicharerepresentedbytheinternalblockdiagram(IBD) in Figure 7.3-1: business: the perspective and context for a stakeholder that is focused on external-facing concerns (e.g., marketing) related to the business functions of a system of interest.
customer: the perspective and contextfora stakeholderthatis focused on concerns related to the customerfunctions ofa system of interest. engineering:theperspectiveandcontextforastakeholderthatisfocusedonconcernsrelatedtotheengineeringfunctions of a system of interest. legal:theperspectiveandcontextforastakeholderthatis focusedonconcerns relatedto thelegalfunctions ofasystemof interest. management: the perspective and context for a stakeholder that is focused on internal-facing concerns (e.g., human resources) related to the management functions of a system of interest. operations:theperspectiveandcontextforastakeholderthatisfocusedonconcernsrelatedtotheoperationsfunctionsof a system of interest. supplier: the perspective and context for a stakeholder that is focused on concerns related to the supplier functions ofa system of interest. 7.4 Resources Resources shalldefine themodels, capabilities, andartifacts usedbyastakeholderwithintheboundaries ofasystemof interest. Astakeholderwith a contextual concern mayuse one ormore ofthe followingresources, which are represented by the IBD in Figure 7.4-1. (a) Model. Amodel shallbe arepresentationthatis physical (e.g., tangible), descriptive (e.g., logical), oranalytical (e.g., mathematical).Themodelshallrepresentareal-worldobject,system,entity,phenomenon,orprocess.Themodelshallbe purpose built and defined within the boundaries of the stakeholder’s contextual concern.
