DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
Agenda <ul><li>DEAR Metamodel </li></ul><ul><ul><li>What information is in DEAR?  </li></ul></ul><ul><ul><li>What is the R...
Quick Start <ul><li>Go to DEAR Home page </li></ul><ul><ul><li>http://www.doi.gov/ocio/architecture/dear </li></ul></ul><u...
Recall Intent of DOI Enterprise Architecture <ul><li>Enterprise Architecture is about  business transformation </li></ul><...
DEAR and its guidance was established by following Policy <ul><li>Policy was created in 2004 and revised in 2006 </li></ul...
System Wizard Overview User context defines which systems you can see and/or edit BFA is used directly on a System Constra...
Quick – Getting Started <ul><li>Go to DEAR Home page </li></ul><ul><ul><li>http://www.doi.gov/ocio/architecture/ </li></ul...
The DEAR Metamodel <ul><li>Metamodel is to DEAR as an outline is to a white paper </li></ul><ul><ul><li>It is a Metadata L...
Parts of the Metamodel DEAR has 8 domains 5 FEA models +  3 sub-architectures PRM = Performance Reference Model BRM = Busi...
We started in the center which was more manageable, and currently detailing out broader as each blueprint progresses Exten...
DEAR information management understands where   <- System Architecture Federal Point of View Department  Point of View Bur...
Data Collection:  Macro Info-Relationship TRM - 1000 BRM - 1000 PRM/ABC - 300 Systems –  700 Investments DRM 13k 4000 450 ...
Lab - Learn the detail behind the DEAR Data model <ul><li>Review the DEAR Metamodel and Glossary </li></ul><ul><li>From th...
System Architecture Touch Points <ul><li>Investment </li></ul>Business Reference Model (BRM) System Architecture  PRM Serv...
Relating Architecture... <ul><li>System Architecture Touch Points </li></ul><ul><li>System Architecture Domain </li></ul><...
DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
Maintaining information via the “System Wizard” <ul><li>http://dear.nbc.gov </li></ul><ul><li>Login: </li></ul><ul><ul><li...
The wizard is a method for loading the data, but not for collecting or validating entry <ul><li>Think: Collect, Load, QA <...
Review the Guidance and see the following tasks <ul><li>Maintaining System Inventory </li></ul><ul><ul><li>Add a system </...
Lab <ul><li>Login </li></ul><ul><li>Open System Wizard </li></ul><ul><li>Expand existing system </li></ul><ul><ul><li>Expa...
When are Privacy Attributes required to be loaded and where <ul><li>All boundaries require Privacy Attribution </li></ul><...
Edit Privacy <ul><li>Set Preliminary PIA Completion Date </li></ul><ul><li>Set Reasons </li></ul><ul><ul><li>Calculation <...
Lab <ul><li>Describe new system with reference models </li></ul><ul><li>Expand Investment </li></ul><ul><ul><li>Edit PRM <...
DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
<ul><ul><li>Business modeling </li></ul></ul><ul><ul><li>Data modeling </li></ul></ul><ul><ul><li>Standards supported and ...
Business Modeling highlights supported in DEAR <ul><li>Business process modeling </li></ul><ul><li>Object-oriented and com...
System Architect and DOORS for Project Requirements synchronization
Data Modeling Highlights <ul><li>Relational data modeling </li></ul><ul><li>Structured analysis and design </li></ul><ul><...
General Modeling Highlights <ul><li>Supports a number of modeling notations and methodologies, including models of the exi...
Telelogic and Popkin Technology System Architect/Telelogic TAU System Architect Telelogic TAU System Architect Telelogic D...
Using System Architect Supports web publishing with HTML, also links to Microsoft Word 97, 2000, 2002 Documentation Suppor...
Lab <ul><li>View the models in DEAR </li></ul><ul><ul><li>DEAR Templates for models are provided in MBT Guidance </li></ul...
Conclusion: Support MBT; Support IAWG DEAR Metamodel System Wizard Business and Data Modeling
Upcoming SlideShare
Loading in …5
×

DEAR Regular User Training

818 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
818
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Investment System Architecture Business Reference Model (BRM) Performance Reference Model (PRM) Technical Reference Model (TRM) Service Reference Model (SRM) Data Reference Model (DRM) Deployment Architecture
  • DEAR Regular User Training

    1. 1. DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
    2. 2. Agenda <ul><li>DEAR Metamodel </li></ul><ul><ul><li>What information is in DEAR? </li></ul></ul><ul><ul><li>What is the Reference Architecture? </li></ul></ul><ul><li>DEAR System Architecture </li></ul><ul><ul><li>How can I detail my system? </li></ul></ul><ul><li>DEAR Data and Business Modeling </li></ul><ul><ul><li>Basics of Modeling in System Architect </li></ul></ul><ul><li>Summary </li></ul>15 minutes 15 minutes 60 minutes 60 minutes Lunch 15 minutes 60 minutes 15 minutes 30 minutes
    3. 3. Quick Start <ul><li>Go to DEAR Home page </li></ul><ul><ul><li>http://www.doi.gov/ocio/architecture/dear </li></ul></ul><ul><li>Navigate to the “DEAR Policy” page </li></ul><ul><li>We will navigate </li></ul><ul><ul><li>the DEAR policy </li></ul></ul><ul><ul><li>the Task Guidance </li></ul></ul><ul><ul><li>Detailed Task instructions </li></ul></ul>
    4. 4. Recall Intent of DOI Enterprise Architecture <ul><li>Enterprise Architecture is about business transformation </li></ul><ul><li>As architects, we are a service provider that helps business organizations become more effective and efficient. </li></ul><ul><li>We must deliver a high quality service that is of value to our customers if we intend to be successful. </li></ul><ul><li>Our EA Information must be valid and accurate </li></ul><ul><ul><li>Inventory </li></ul></ul><ul><ul><li>Integrate Inventory </li></ul></ul><ul><ul><li>Reference Models </li></ul></ul><ul><ul><li>MBT Modeling </li></ul></ul>
    5. 5. DEAR and its guidance was established by following Policy <ul><li>Policy was created in 2004 and revised in 2006 </li></ul><ul><li>DEAR has been updated with each policy revision </li></ul><ul><li>DEAR Guidance gets updated including </li></ul><ul><ul><li>Step Guidance </li></ul></ul><ul><ul><li>For Each step, the following is provided online </li></ul></ul><ul><ul><ul><li>Collection Templates </li></ul></ul></ul><ul><ul><ul><li>Wizard Tutorials </li></ul></ul></ul><ul><ul><ul><li>Quality Assurance Reports </li></ul></ul></ul><ul><ul><ul><li>As well as, </li></ul></ul></ul><ul><ul><ul><ul><li>FAQs, Step Summary, relationship to MBT, and Training Links </li></ul></ul></ul></ul><ul><ul><li>This follows the Collect, Load, and QA process for each Step/Task </li></ul></ul>
    6. 6. System Wizard Overview User context defines which systems you can see and/or edit BFA is used directly on a System Constrained to your Active Group
    7. 7. Quick – Getting Started <ul><li>Go to DEAR Home page </li></ul><ul><ul><li>http://www.doi.gov/ocio/architecture/ </li></ul></ul><ul><li>From the Home Page, on the bottom, navigate to “Reference Models” </li></ul><ul><li>Navigate to the Metamodel Glossary section </li></ul>
    8. 8. The DEAR Metamodel <ul><li>Metamodel is to DEAR as an outline is to a white paper </li></ul><ul><ul><li>It is a Metadata Logical Data Model </li></ul></ul><ul><ul><ul><li>DEAR captures metadata about an enterprise </li></ul></ul></ul><ul><ul><ul><li>The model is the database schema it is organized in. </li></ul></ul></ul><ul><li>Worth noting, the physical implementation is captured not in Data Dictionary Language, but in a Metadata language custom to the COTS product DEAR is based on called “userprops” (short for “user properties”) </li></ul><ul><li>Metamodel was designed with input from: </li></ul><ul><ul><li>Multiple bureaus (i.e. BLM, MMS-OMM, NPS, USGS, DOI EA Gov. Teams) </li></ul></ul><ul><ul><li>Multiple agencies (i.e. USDA Forest Service, OMB, FISMA, NIST, DOE) </li></ul></ul><ul><ul><li>Multiple Domain Data Stewards (i.e. CPIC, Security, Privacy, EA, Sub-Architecture Areas, Workforce Planning, etc.) </li></ul></ul>
    9. 9. Parts of the Metamodel DEAR has 8 domains 5 FEA models + 3 sub-architectures PRM = Performance Reference Model BRM = Business Reference Model SRM = Service Component Reference Model TRM = Technical Reference Model DRM = Data Reference Model
    10. 10. We started in the center which was more manageable, and currently detailing out broader as each blueprint progresses Extended Bureau Models Core DOI Models System Centric Models <ul><li>Systems </li></ul><ul><li>Relationships to Reference Models </li></ul><ul><li>Relationships to Organizations & People </li></ul><ul><li>FEA RMs </li></ul><ul><li>PRM </li></ul><ul><li>BRM </li></ul><ul><li>SRM </li></ul><ul><li>TRM </li></ul><ul><li>DRM </li></ul><ul><li>DOI </li></ul><ul><li>DOI PRM </li></ul><ul><li>DOI BRM </li></ul><ul><li>DOI SRM </li></ul><ul><li>DOI TRM </li></ul><ul><li>DOI DRM </li></ul><ul><li>DOI Tracked Systems </li></ul><ul><li>Bureau </li></ul><ul><li>Bureau PRM </li></ul><ul><li>Bureau BRM </li></ul><ul><li>Bureau SRM </li></ul><ul><li>Bureau TRM </li></ul><ul><li>Bureau DRM </li></ul><ul><li>Bureau </li></ul><ul><li>Activity Models </li></ul><ul><li>Process Models </li></ul><ul><li>Data Extensions </li></ul>
    11. 11. DEAR information management understands where <- System Architecture Federal Point of View Department Point of View Bureau-Specific Point of View Agency Point of View DEAR eCPIC D E P T A G E N C Y O M B Bureau/ Blueprint Modeling Information Assurance Documents OMB FEA Consolidated Reference Models DOI Strategic Plan ABC System System SOR
    12. 12. Data Collection: Macro Info-Relationship TRM - 1000 BRM - 1000 PRM/ABC - 300 Systems – 700 Investments DRM 13k 4000 450 1800 1400 1050 8000 250 15K+ 7300 SRM
    13. 13. Lab - Learn the detail behind the DEAR Data model <ul><li>Review the DEAR Metamodel and Glossary </li></ul><ul><li>From the Department EA web site or DEAR web site, go to the reference models page. </li></ul><ul><li>Open the metamodel view </li></ul><ul><li>Pick a Popular View </li></ul><ul><li>Navigates similar to the panel reports </li></ul><ul><li>Click on an object/entity </li></ul><ul><li>Review metadata </li></ul><ul><li>Click on an attribute </li></ul><ul><li>Review metadata </li></ul>DEAR Touch Points DRM SRM TRM BRM PRM Deployment Architecture System Architecture Investment Architecture
    14. 14. System Architecture Touch Points <ul><li>Investment </li></ul>Business Reference Model (BRM) System Architecture PRM Service Reference Model (SRM) Technical Reference Model (TRM) Performance Reference Model (PRM) Deployment Architecture Data Reference Model (DRM) BRM DRM SRM TRM INV SA DA                             = 1 st level touch point between domains   
    15. 15. Relating Architecture... <ul><li>System Architecture Touch Points </li></ul><ul><li>System Architecture Domain </li></ul><ul><li>How do I edit this? </li></ul><ul><ul><li>System Wizard Demo </li></ul></ul><ul><li>Key System Architecture Domain Touch Points </li></ul><ul><ul><li>System & PRM </li></ul></ul><ul><ul><li>System & BRM </li></ul></ul><ul><ul><li>System & DRM </li></ul></ul><ul><ul><li>System & SRM </li></ul></ul><ul><ul><li>System & TRM </li></ul></ul><ul><ul><li>System & Deployment Architecture </li></ul></ul><ul><li>Concluding Observations </li></ul>DRM SRM TRM BRM PRM Deployment Architecture System Architecture Investment Architecture
    16. 16. DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
    17. 17. Maintaining information via the “System Wizard” <ul><li>http://dear.nbc.gov </li></ul><ul><li>Login: </li></ul><ul><ul><li>Requires Citrix plug-in </li></ul></ul><ul><ul><li>Automatically installed one-time (if admin privileges) </li></ul></ul><ul><li>Login with DEAR ID </li></ul><ul><ul><li>User: Train## (1-20) </li></ul></ul><ul><ul><li>Password: Provided by Instructor </li></ul></ul><ul><li>Training encyclopedia will automatically open </li></ul><ul><ul><li>In real login, the DEAR Work in Progress encyclopedia will open </li></ul></ul><ul><li>Once logged in, go to </li></ul><ul><ul><li>Tools Menu, select System Wizard </li></ul></ul>
    18. 18. The wizard is a method for loading the data, but not for collecting or validating entry <ul><li>Think: Collect, Load, QA </li></ul><ul><li>Collect : DEAR Guidance is provided from the DEAR home page </li></ul><ul><ul><li>Steps </li></ul></ul><ul><ul><ul><li>Tasks </li></ul></ul></ul><ul><ul><ul><ul><li>Description, Template, Tutorial page, Report page, as well as FAQ (future updates) </li></ul></ul></ul></ul><ul><li>Load using the Wizard </li></ul><ul><li>QA with your interviewee using the reports provided to close the task </li></ul>
    19. 19. Review the Guidance and see the following tasks <ul><li>Maintaining System Inventory </li></ul><ul><ul><li>Add a system </li></ul></ul><ul><ul><li>Edit a system </li></ul></ul><ul><ul><li>Model System Hierarchy </li></ul></ul><ul><li>Describe with Reference Models </li></ul><ul><ul><li>Relate Investment to PRM </li></ul></ul><ul><ul><li>Relate Sub-system to BRM </li></ul></ul><ul><ul><li>Relate Sub-system to DRM Information Class or Entity </li></ul></ul><ul><ul><li>Relate Component to SRM </li></ul></ul><ul><ul><li>Relate Component to TRM </li></ul></ul>
    20. 20. Lab <ul><li>Login </li></ul><ul><li>Open System Wizard </li></ul><ul><li>Expand existing system </li></ul><ul><ul><li>Expand sub-system </li></ul></ul><ul><ul><ul><li>Expand component instance </li></ul></ul></ul><ul><ul><ul><ul><li>Expand component </li></ul></ul></ul></ul><ul><li>Add a new system </li></ul><ul><ul><li>Name with initials+number+system </li></ul></ul><ul><ul><ul><li>Expand all levels </li></ul></ul></ul><ul><li>Save then </li></ul><ul><ul><li>Edit system attributes </li></ul></ul><ul><ul><ul><li>Edit Privacy attributes </li></ul></ul></ul><ul><ul><li>Add a subsystem </li></ul></ul><ul><ul><li>Add a component </li></ul></ul>
    21. 21. When are Privacy Attributes required to be loaded and where <ul><li>All boundaries require Privacy Attribution </li></ul><ul><ul><li>If no PIA Required, only the first few fields showing on the screen are required (Preliminary PIA Date completed, and first 4 questions </li></ul></ul><ul><ul><li>If PIA Required, complete all fields based on Full PIA as required </li></ul></ul><ul><li>If Boundaries have multiple member systems, the same information must be populated at the system level </li></ul><ul><li>The Privacy Officer must provide the information to the Bureau IT Security Manager for Boundaries and to the Architect for Systems </li></ul><ul><ul><li>A privacy Office may gain access to edit boundaries directly if coordinated with the Bureau IT Security Managers </li></ul></ul>
    22. 22. Edit Privacy <ul><li>Set Preliminary PIA Completion Date </li></ul><ul><li>Set Reasons </li></ul><ul><ul><li>Calculation </li></ul></ul><ul><li>If Required: </li></ul><ul><ul><li>Set Completion Date </li></ul></ul><ul><ul><ul><li>Annually </li></ul></ul></ul><ul><ul><li>Retrieved by Name attributes </li></ul></ul><ul><ul><li>Records Notice Info </li></ul></ul><ul><ul><li>Online Form Info </li></ul></ul><ul><ul><li>OMB Required Fields </li></ul></ul>
    23. 23. Lab <ul><li>Describe new system with reference models </li></ul><ul><li>Expand Investment </li></ul><ul><ul><li>Edit PRM </li></ul></ul><ul><ul><ul><li>Link to Outcome under Recreation </li></ul></ul></ul><ul><li>Expand Subsystem </li></ul><ul><ul><li>Edit BRM </li></ul></ul><ul><ul><ul><li>Search on recreation </li></ul></ul></ul><ul><ul><ul><li>Link and add “Mapping Details” using dropdown </li></ul></ul></ul><ul><ul><li>Edit DRM </li></ul></ul><ul><ul><ul><li>Search on facility </li></ul></ul></ul><ul><li>Expand Component </li></ul><ul><ul><li>Edit SRM </li></ul></ul><ul><ul><ul><li>Search on Map </li></ul></ul></ul><ul><ul><li>Edit TRM </li></ul></ul><ul><ul><ul><li>Search on multiple technologies – think of multiple layers or just use the taxonomy </li></ul></ul></ul>
    24. 24. DEAR Training: Regular User DEAR Metamodel System Wizard Business and Data Modeling
    25. 25. <ul><ul><li>Business modeling </li></ul></ul><ul><ul><li>Data modeling </li></ul></ul><ul><ul><li>Standards supported and discuss [draft] Policy </li></ul></ul><ul><ul><li>Uploading/briding from other modeling tools </li></ul></ul><ul><ul><li>Using models with solution architecture teams </li></ul></ul><ul><ul><li>Models that are supported in DEAR guided via MBT </li></ul></ul>Section Agenda
    26. 26. Business Modeling highlights supported in DEAR <ul><li>Business process modeling </li></ul><ul><li>Object-oriented and component modeling with UML </li></ul><ul><li>Knowledge capture – some of the previous Enterprise Architecture processes (CoolBiz) and application data (collected application architecture interfaces) can be captured and placed into the Telelogic tool </li></ul><ul><li>Supports a wide range diagram types / methods (UML, BPMN, IDEF, others) </li></ul><ul><li>Can manage and enforce the complete lifecycle of information according to defined processes </li></ul><ul><li>Business Rule Versioning NOT supported </li></ul><ul><li>Provide support the Business process re-engineering effort. </li></ul><ul><li>Requirements tracking can now be integrated with SA v11 and DOORS </li></ul>
    27. 27. System Architect and DOORS for Project Requirements synchronization
    28. 28. Data Modeling Highlights <ul><li>Relational data modeling </li></ul><ul><li>Structured analysis and design </li></ul><ul><li>Single tool used by Burea EA to conduct process, data, application, and technology modeling (Replaces CoolBiz, ERwin, and Visio) </li></ul><ul><li>Transformation rules can be appropriately captured and maintained in specialized objects in the SA encyclopedia. Currently the tool supports a “minispec” data type, which is intended to document the behavior of a data process. </li></ul><ul><li>Developers can view data relationships to determine the impact of proposed changes. This information is also available as a report. </li></ul><ul><li>Schemas for existing applications can be scanned in from databases or from DDL. </li></ul><ul><li>ERwin files can be imported using the MetaIntegration bridge product. Reverse engineering of existing databases brings in all relevant metadata, including data types, table constraints, database triggers, etc. </li></ul><ul><li>Can integrate architecture data which is currently performed using a myriad of tools across multiple non-integrated and incompatible data stores. </li></ul>
    29. 29. General Modeling Highlights <ul><li>Supports a number of modeling notations and methodologies, including models of the existing application portfolio and network architecture. </li></ul><ul><li>Extensive number of existing connectors to modeling tools </li></ul><ul><li>have many out-of-the-box translators </li></ul><ul><li>uses XML and an open API to link with existing modeling tools </li></ul><ul><li>Lower the cost associated with the management of architectural data and generated work products. </li></ul><ul><li>FEAF, Zachman, TOGAF, and DoDAF framework support </li></ul><ul><li>Create an 'extended symbol graphics library' of general symbol shapes which can be used in any diagrams. </li></ul><ul><li>Ability to share model artifacts using third party translators such as Meta Integration Model Bridge product (MIMB) and and standard such as XMI and IDL </li></ul><ul><li>Lower the cost associated with analysis of the architectural data. </li></ul>
    30. 30. Telelogic and Popkin Technology System Architect/Telelogic TAU System Architect Telelogic TAU System Architect Telelogic DOORS Telelogic SYNERGY
    31. 31. Using System Architect Supports web publishing with HTML, also links to Microsoft Word 97, 2000, 2002 Documentation Support for generating languages from OO diagrams (includes reverse code engineering options for C++ and Java). Languages include C++, Java, Visual Basic Object-Oriented (OO) language support Reverse data engineering into, and schema generation out of, physical data models, using AS400, Oracle, SQL Server, dBASE, OS/2, SYBASE10, DB2, Paradox, Teradata, INFORMIX, Progress, WATCOM, Ingres, RDB, XDB, InterBase, SQLBase, Microsoft Access, SQL Anywhere Data modeling database support XML diagram – generation of BizTalk and DTD Extensible Markup Language (XML) UML, OMT (Coad/Yourdon, Booch 94, Shlaer/Mellor) Object Oriented Analysis & Design Entity relation models, physical data models. Data modeling Gane and Sarson, Ward/Mellor, SSADM, Yourdon/DeMarco. Structured systems analysis and design IDEF0 function modeling, IDEF3 process flows, IDEF1X data models, *BPMN (support for v0.9 of BPMN, generation of BPML and BPEL4WS) Business Process Re-engineering (BPR) use these tools For this kind of work
    32. 32. Lab <ul><li>View the models in DEAR </li></ul><ul><ul><li>DEAR Templates for models are provided in MBT Guidance </li></ul></ul><ul><ul><li>DEAR Guidance points to the place in the MBT for which type of templates </li></ul></ul><ul><li>Open MBT guidance </li></ul><ul><ul><li>Open Step 3 or 4 Summary </li></ul></ul><ul><ul><ul><li>Open word document </li></ul></ul></ul><ul><ul><ul><ul><li>Review document to template section </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Open Value Chain (#3) or System Interface (#4) </li></ul></ul></ul></ul></ul><ul><ul><li>By following templates, diagrams created offline in Visio templates can be imported </li></ul></ul><ul><ul><ul><li>Diagrams created following industry standard in any tool can be bridged to DEAR tool </li></ul></ul></ul>
    33. 33. Conclusion: Support MBT; Support IAWG DEAR Metamodel System Wizard Business and Data Modeling

    ×