The Very Simple Example ####################### The name "very simple" is rather misleading. The problem is very simple, but the example has been expanded to illustrate many of the core features of the Business Object Model ================= Scenario Overview ================= The scenario is illustrated below. .. figure:: /objects/images/VSE_scenario.png :scale: 100% Very Simple Example The aim is to compute the deflection of a beam. The key features are: * Geometrical shape (planar surface) * Hollow beam, defined by Thickness * Beam length * Billet chosen from catalogue of fixed sizes * Machining time derived from differences in volumes of beam and billet * Material provides density property for Mass * Billet properties provide Youngs Modulus E (impacted by billet roll direction etc) * Deflection of cantilever under evenly distributed weight of beam * Range derived from inner area (I.e. fuel volume) ==================================== The Associative Model Networks [AMN] ==================================== The following are illustrations of the networks for the example ================= Beam Geometry AMN ================= The first stage is to create the geometry for the example. It is may appear to be overly complex for the simple problem, but this is to enable illustrations of other areas. The first image shows the network and the .. figure:: /objects/images/vse_shell_solid_amn.png :scale: 100% AMn for the Geometry (ShellSolid) .. rst-class:: expand -------------------------------------------------- Representation using Business Object Model classes -------------------------------------------------- This shows a study with a concept that is managing the AMN. The ModelInstances and KeyValueInstance belong to the AMN. The AMN is actually a combination of the Geometry and the Spreadsheet deflection. .. figure:: /objects/images/vse_ea_beam_geometry_amn.png :scale: 100% Associative Model Network for the Beam Geometry The instances in the above diagram each have a corresponding type. The types are themselves in a Collaborative Model Template [CMT] which is shown in the second image. .. figure:: /objects/images/vse_ea_beam_geometry_cmt.png :scale: 100% Collaborative Model Template for the Beam Geometry .. note:: There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class. ============== Deflection AMN ============== There are then two alternative ways to compute the deflection. The first is using a simple formula in a spreadsheet. This has several assumptions, or limitations, in that it is only applicable for prismatic shapes. The second approach is by using an Finite Element analysis. This can work on any solid shape, and it is probably over-kill for this example so can be used to illustrate a poor "utility" rating. .. figure:: /objects/images/vse_xls_defln.png :scale: 100% AMN for Deflection computed using a formula in a spreadsheet .. rst-class:: expand -------------------------------------------------- Representation using Business Object Model classes -------------------------------------------------- This shows a study with a concept that is managing the AMN. The ModelInstances and KeyValueInstance belong to the AMN. The AMN is actually a combination of the Geometry and the Spreadsheet deflection. .. figure:: /objects/images/vse_xls_defln_with_MT.png :scale: 100% The schematic illustration of the deflection network but also including the types .. figure:: /objects/images/vse_ea_beam_geometry_amn.png :scale: 100% Associative Model Network for the Beam Geometry The instances in the above diagram each has a corresponding type. The types are themselves in a Collaborative Model Template [CMT] which is shown in the second image. .. figure:: /objects/images/vse_ea_xls_defln_cmt.png :scale: 100% Collaborative Model Template for the Deflection computed using a formula in a spreadsheet .. note:: There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class. .. figure:: /objects/images/vse_fe_defln.png :scale: 100% AMN for Deflection computed using Finite Element Analysis .. rst-class:: expand -------------------------------------------------- Representation using Business Object Model classes -------------------------------------------------- The example does not contain a single network that contains all the elements of the Finite Element Deflection analysis, because this is part of the second study which builds on the first study. Therefore only the Collaborative Model Template is shown here. .. figure:: /objects/images/vse_ea_fe_defln_cmt.png :scale: 100% Collaborative Model Template for the Deflection computed using Finite Element Analysis .. note:: There are classes between the instances and types rather than direct relationships. This is because the link between needs to be referenced when the data flows are identified, therefore the link cannot be a simple relationship and must be a class. ================= Manufacturing AMN ================= Finally there is a stage that brings in some manufacturing issues. Here the scenario is, that depending on the size of the beam, different billet sizes have to be used, and these have different material properties (Youngs modulus) due to the roll characteristics of the forging process .. figure:: /objects/images/vse_manuf_amn.png :scale: 100% AMN for the manufacturing models ============ Combined AMN ============ These stages can be combined into a single picture, which are illustrated below using either the spreadsheet, or the Finite Element method of calculating the deflection. .. figure:: /objects/images/vse_xls_combined_amn.png :scale: 100% Combined AMN for the Geometry, manufacturing and spreadsheet deflection .. figure:: /objects/images/vse_fe_combined_amn.png :scale: 100% Combined AMN for the Geometry, manufacturing and FE deflection ==================================== Links and images used in other pages ==================================== ----------------------------- Requirements and Verification ----------------------------- See |Requirements and Verification| .. figure:: /objects/images/vse_ea_study_with_requirements.png :scale: 100% Study objectives as requirements .. figure:: /objects/images/vse_ea_uncertainty.png :scale: 100% Two AMNs with uncertainty values .. figure:: /objects/images/vse_ea_requirement_verification.png :scale: 100% Requirement Verification ---------------- Study Management ---------------- See |Study Management| .. figure:: /objects/images/vse_ea_2x_study.png :scale: 100% Two studies ------------------------------------ AssociativeModelNetwork and workflow ------------------------------------ See |AssociativeModelNetwork| and workflow .. figure:: /objects/images/vse_xls_defln_amn.png :scale: 100% Part of an AMN surrounding a single element .. figure:: /objects/images/vse_xls_defln_workflow.png :scale: 100% Workflow view for the same element .. figure:: /objects/images/vse_ea_just_defln_from_amn1.png :scale: 100% Part of an Associative Model Network concerned with on model .. figure:: /objects/images/vse_ea_just_defln_workflow_from_amn1.png :scale: 100% Data flow view for the same model ----------------- Method Definition ----------------- See |Method Definition| .. figure:: /objects/images/vse_simple_deflection_method_resources.png :scale: 100% Named resources for a method .. figure:: /objects/images/vse_simple_deflection_method_io.png :scale: 100% Equivalent using Business Object Classes .. figure:: /objects/images/vse_simple_deflection_method_inputs.png :scale: 100% Method inputs with names .. figure:: /objects/images/vse_fe_deflection_method_io.png :scale: 100% Different sets of inputs for a method .. figure:: /objects/images/vse_simple_deflection_method_output.png :scale: 100% Method output (method is 'applicable' for Model type) .. figure:: /objects/images/vse_simple_deflection_method_domain_of_validity_ppt.png :scale: 100% .. figure:: /objects/images/vse_simple_deflection_method_domain_of_validity.png :scale: 100% Limitations on inputs .. figure:: /objects/images/vse_fe_deflection_method_sensitivity.png :scale: 100% Duration and Propagation sensitivities on inputs and outputs ---------------- Methods DataFlow ---------------- See |Methods DataFlow| .. figure:: /objects/images/vse_ea_xls_defln_cmt.png :scale: 100% BeamDefn using simple models and methods .. figure:: /objects/images/vse_ea_fe_defln_cmt.png :scale: 100% BeamDefn using FE based models and methods .. figure:: /objects/images/vse_simple_defln_method_cmt_dataflow_and_derivedFrom.png :scale: 100% DataFlows connecting elements in the CMT .. figure:: /objects/images/vse_simple_defln_method_cmt_dataflow.png :scale: 100% Showing just the elements that show the flow of data through the method .. figure:: /objects/images/vse_ea_beam_geometry_amn.png :scale: 100% AMN to create the Deflection using the formulaic method .. figure:: /objects/images/vse_ea_just_defln_from_amn1.png :scale: 100% Area of the AMN relating to the Beam Deflection .. figure:: /objects/images/vse_ea_amn_with_defn_method_dataflow.png :scale: 100% DataFlows connecting elements in the AMN to the method inputs .. figure:: /objects/images/vse_ea_just_defln_workflow_from_amn1.png :scale: 100% Showing just the elements that show the flow of data through the method ------------- Quality Gates ------------- See Quality Gates .. figure:: /objects/images/vse_ea_QualityReportsAndGates_Types.png :scale: 100% View of classes associated with a Quality Gate Type .. figure:: /objects/images/vse_ea_QualityReportsAndGates_Instances.png :scale: 100% View of classes associated with a Quality Gate Instance .. figure:: /objects/images/vse_ea_QualityGates_and_planned_meetings.png :scale: 100% View of classes for a planned meeting for a Quality Gate .. figure:: /objects/images/vse_ea_QualityGates_and_actual_meeting.png :scale: 100% View of classes for a actual meeting for a Quality Gate .. figure:: /objects/images/vse_ea_Argumentation.png :scale: 100% ----------------------- Templates and Instances ----------------------- See |Templates and Instances| .. figure:: /objects/images/vse_ea_MethodologyLibrary.png :scale: 100% Methodology Library of VerySimpleExample in EA .. figure:: /objects/images/vse_ea_programme_lib_study.png :scale: 100% Programme that deploys a Methodology Library, and manages Studies .. figure:: /objects/images/vse_MT_KVT_inheritance_and_doc.png :scale: 100% Documentation for the definition of Model Types and Key Value Types, including inheritance -------------------------------- Collaborative Process Management -------------------------------- See |Collaborative Process Management| .. figure:: /objects/images/vse_ea_AMN_with_Defn_method_Activities.png :scale: 100% Process Management for Study, Associative Model network and Model Instance .. figure:: /objects/images/vse_ea_Study2_Activities.png :scale: 100% Series of Process Management objects with triggers ------------------ Security and Trust ------------------ See |Security and Trust| .. figure:: /objects/images/vse_ea_st_team_of_trust.png :scale: 100% Contract for ID certification within a Team of Trust .. figure:: /objects/images/vse_ea_st_collaboration_contract.png :scale: 100% Contracts for the collaboration .. figure:: /objects/images/vse_ea_st_assignment.png :scale: 100% Assignment of Information Rights and Security Classifications --------------- Value Modelling --------------- See |Value Modelling| * 1a. Stakeholder expectations are captured and validated .. figure:: /objects/images/vse_vm_ea_e_expectations.png :scale: 100% Expressed Expectations are captured using classes * 1b. Stakeholder expectations are validated .. figure:: /objects/images/vse_vm_ea_v_expectations.png :scale: 100% Expressed Expectations are Validated using classes * 2. Stakeholder needs identified, analysed .. figure:: /objects/images/vse_vm_ea_needs_analysis.png :scale: 100% Stakeholder needs are identified * 3. Value Creation strategy for analysed and rank-weighted Needs .. figure:: /objects/images/vse_vm_ea_needs_rankweight.png :scale: 100% Stakeholder needs are rank-weighted in context with value drivers * 4. Quantified Objective Hierarchies with targets for analysed and rank-weighted Needs .. figure:: /objects/images/vse_vm_ea_QuantifiedObjectives.png :scale: 100% Quantified Objectives and Targets assigned to Needs and Value Drivers * 5. Value Creation strategy for analysed and rank-weighted Quantified Objectives .. figure:: /objects/images/vse_vm_ea_QuantifiedObjectives_rw.png :scale: 100% VCS with Rank-Weighted Needs fulfilled by Rank-Weighted Quantified Objectives with Targets * 6. Value Models developed * 7. Requirements established based on rank-weighted quantified objectives .. figure:: /objects/images/vse_vm_ea_Requirements.png :scale: 100% Requirements traced to Quantified Objective and Value Creation Strategy .. sectionauthor:: |Judith Crockford| .. include:: /objects/documents/main/Keywords.rst