Wims paper (1)


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Wims paper (1)

  1. 1. Toward a Shared Vocabulary for Systems Engineering Paola Di Maio, University of Strathclyde/ISTCS.org WIMS11, Norway 25-27 May 2011
  2. 2. CONTENTS <ul><ul><li>About this paper, what's new? </li></ul></ul><ul><ul><li>How did it all start </li></ul></ul><ul><ul><li>Worldview </li></ul></ul><ul><ul><li>About Systems Engineering </li></ul></ul><ul><ul><li>The trigger: wikification </li></ul></ul><ul><ul><li>Entanglement </li></ul></ul><ul><ul><li>Mixed Method Approach </li></ul></ul><ul><ul><li>Text extraction </li></ul></ul><ul><ul><li>integrating Dimensions </li></ul></ul><ul><ul><li>The proposed architecture </li></ul></ul><ul><ul><li>Future work </li></ul></ul>WIMS11, Norway 25-27 May 2011
  3. 3.   Whats new? <ul><li>Shared vocabularies are not new but it is surprising to find that </li></ul><ul><li>a) in real world situation not many people use them </li></ul><ul><li>b) not many people outside the SW community know about them </li></ul><ul><li>c) some efforts started in 2009, when I joined INCOSE </li></ul><ul><li>This paper introduces: </li></ul><ul><li>- SEBOK and related challenges </li></ul><ul><li>- An integrated, socio-technical perspective </li></ul><ul><li>(exctracting the vocabulary is just a beginning) </li></ul><ul><li>- Novel worldwiew and approach </li></ul>WIMS11, Norway 25-27 May 2011
  4. 4. SYSTEMIC PROBLEMS <ul><ul><li>  ARE INHERENTLY NON-QUANTIFIABLE </li></ul></ul><ul><ul><li>  CONTAIN GENUINE UNCERTAINTIES </li></ul></ul><ul><ul><li>  CANNOT BE CAUSALLY MODELLED OR SIMULATED </li></ul></ul><ul><ul><li>  REQUIRE A JUDGMENTAL APPROACH </li></ul></ul><ul><ul><li>  TECHNICALLY FLAWLESS SYSTEM, FAIL DUE TO HUMAN AND SOCIAL FACTORS </li></ul></ul>WIMS11, Norway 25-27 May 2011
  5. 5. HOW DID IT ALL START <ul><li>Joined INCOSE in 2009, presented a paper at EUSEC2010 </li></ul><ul><li>Meet Art Pyster from Stevenson, invited to join SEBOK effort </li></ul><ul><li>SEBOK is at a critical turning point to move to WIKI </li></ul><ul><li>Involved in effort, and discussing approaches toward semantic wiki </li></ul><ul><li>See 'challenges to wikification' for more details </li></ul><ul><li>  </li></ul>WIMS11, Norway 25-27 May 2011
  6. 6. WORLDVIEW (EPISTEMOLOGICAL PARADIGM)   <ul><li>Postpositivism  quantitative determination reductionism knowledge can never be found empirical observation and measurement (scientific method) theory verification cause-and-effect deductive 19th century writers Conte and Locke  </li></ul><ul><li>Constructivism  qualitative understanding multiple participant meanings (humans) social and historical construction theory generation open-ended questioning inductive </li></ul><ul><li>Advocacy and Participatory   qualitative (can lead to quantitative) political empowerment issue oriented collaborative change-oriented focus on marginalized or disenfranchised Marx, Marcuse </li></ul><ul><li>Pragmatic   consequences of actions problem-centered pluralistic real-world practice oriented                                              </li></ul><ul><li>                                                                                    (Creswell) </li></ul><ul><li>TRANSFORMATIVE   Delivers systemic change </li></ul><ul><li>SYSTEMIC   Tackles issues as a whole, takes the integrated perspective </li></ul>WIMS11, Norway 25-27 May 2011
  8. 8. ABOUT Systems Engineering <ul><li>T he discipline of systems engineering (SE) has been recognized for 50 years as essential to the development of complex systems. [...] SE is still treated primarily as heuristics learned by each practitioner during the personal experimentation of a career. The heuristics known by each  differ, as shown by the fractured development of SE “standards” and SE certification. [...] As a result of this heuristic understanding of the discipline, it has been nearly impossible to quantify the value of SE to programs. [Sheard 2000] [...] The differences in understanding, however, just as typically result in disagreement over the level and formality of the practices to include. [Shenhar 1997] </li></ul>WIMS11, Norway 25-27 May 2011
  9. 9. Image Source: wikipedia
  10. 10. KNOWLEDGE SHARING   WIMS11, Norway 25-27 May 2011 Source: P. Di Maio
  11. 11. WIKIFICATION, CHALLENGES  1 <ul><li>Provide justification for what is essentially a cultural change from a ‘closed world’ perspective, to the open dynamic world,’  </li></ul><ul><li>Many implications. </li></ul><ul><li>it reflects in the logic of the technical system being implemented, and in the organisational  and management setup of development practices and documentation itself.  </li></ul>WIMS11, Norway 25-27 May 2011
  12. 12. WIKIFICATION, CHALLENGES 2 <ul><li>What's the best way to migrate the content from hard coded documents to a SMWiki environment? </li></ul><ul><li>What kind of structure should the wiki provide to enable meaningful representation of the content? </li></ul><ul><li>What model of governance is suitable for a distributed multiauthors team that would allow both max flexibility to encourage contributions, and that would also support sufficient validation  for the  quality of the contribution? </li></ul>WIMS11, Norway 25-27 May 2011
  13. 13. ENTANGLEMENT/CIRCULARITY <ul><li>Loading the corpus to a wiki requires some decision  in relation to the ‘structure’ which means,  how to best organise the corpus depends on how the corpus structure is defined.  </li></ul><ul><li>Subsequent ongoing edits and editorial changes  to body of knowledge after it has been opened up on the wiki, will be determined by what editorial process is in place. The editorial process in turn depends on what governance model is chose .These interdependencies between various steps are what we refer to as ‘entanglement’  </li></ul><ul><li>Solving the entanglement can be done by  </li></ul><ul><li>a) identifying and mapping all the key factors and  their dependencies  </li></ul><ul><li>b)  constructing a the project schedule and a plan build around them, in what is essentially a very ‘agile’ style. </li></ul>
  15. 15. ENTANGLEMENT 2
  17. 17. Automated Text Extraction Approach (ATX)   STEPS :   - Parsed Chap 2 using different generic tools (Opencalais, Alchemy)  - Compared the output with the glossary created manually by  the editors with the output of ATX OVERVIEW OF RESULTS - ATX yields more granular results and in some cases provides some categories (structure) to the terms RECOMMENDATIONs - Editors of the glossary could take into account additional granularity and categorization structure.  - New ad hoc categories for SE could be created.  - Categories could serve as metadata and could be encoded using SKOS or other suitable supporting  schema MORE INFO: http://tinyurl.com/2vwq5wh    
  18. 18. Morphological Analysis <ul><ul><li>From classical Greek (morphe) :and means shape or form </li></ul></ul><ul><ul><li>Morphology is the study of the shape and arrangement of parts of an object, and how these parts &quot;conform&quot; to create a whole or Gestalt. </li></ul></ul><ul><ul><li>The &quot;objects&quot; in question can be physical objects (e.g. an organism, an anatomy, a geography or an ecology) or mental objects (e.g. word forms, concepts or systems ofideas). </li></ul></ul><ul><li>A methodological framework for creating models of systems and processes, which cannot be meaningfully quantified </li></ul><ul><ul><li>Extended typology analysis was invented as early as the 1930’s by Fritz Zwicky, professor of astronomy at the California Institute of Technology – the famous Caltech in Pasadena </li></ul></ul><ul><li>http://www.swemorph.com/pdf/it-webart.pdf </li></ul>
  19. 19. <ul><li>What is MA used for? </li></ul><ul><li>- Complex issue which is not well formulated or defined; (”wicked </li></ul><ul><li>problem”) </li></ul><ul><li>- Well formulated/defined issue, but with no single solution (different </li></ul><ul><li>solutions depending on…) </li></ul><ul><li>- Well defined problem with aspecific solution which can be </li></ul><ul><li>worked out. </li></ul><ul><ul><li>Mess </li></ul></ul><ul><ul><li>Problem </li></ul></ul><ul><ul><li>Puzzle </li></ul></ul><ul><li>(Russell Ackoff: Redesigning the Future, 1974; Michael Pidd: Tools for Thinking, 1996.) </li></ul>
  20. 21. PROCESS <ul><li>in answering the question: What's the best way to migrate  content from a hardcoded document to a SMWiki environment, and then to maintain the future updates?  </li></ul><ul><li>1. to upload the working version of a Body of Knowledge  to  a wiki after it has been finalized. This can be done as a single step, or a series of steps, for example one chapter at the time. (SINGLE STEP, FEW TEAM MEMBERS) </li></ul><ul><li>2. to allow users to make ongoing edits and changes throughout the life of the BOK    In our description, a process consists of  a series of dynamic steps (as opposed to a model, which is a static representation’). The following processes are required to deploy a body of knowledge to a wiki:  (EDITORIAL PROCESS, ALL AUTHORS) </li></ul>
  21. 22. STRUCTURE <ul><li>“ What kind of content structure should the wiki provide to enable meaningful representation of the content?” </li></ul><ul><li>It may be useful  to define further 'structure' . It is envisaged that a minimum of two levels of structure can be easily inferred from the hard version of the corpus </li></ul><ul><li>1.content structure,  for example a TOK (Table of Contents), including chapters, topics and/or subtopics, can be considered as a first level of content structure, </li></ul><ul><li>2. 'semantic' structure , essentially  what a semantic wiki environment supports –  refers to the allocation to each term (glossary entry) of a value and properties (is a concept , or is it a relation, either, or both, for example) as well as some lexical definitions for each term (a description of the meaning). </li></ul>
  22. 23. GOVERNANCE <ul><li>A governance model (gm) = 'who' does 'what' (possibly also 'when' and 'how').  </li></ul><ul><li>  characteristics of the technological environments influence and shape directly the governance model. The GM required for a  large distributed project would necessarily have to take into account the 'virtual' and 'distributed' nature of the team. A governance model can  be built by establishing </li></ul><ul><li>a) what tasks constitute the editorial process  </li></ul><ul><li>b)what roles (team members and other users) have what permissions (what tasks in the editorial process can carry out). </li></ul><ul><li>c) what sequence/priorities/rules should be applied to the execution of the tasks that. A workflow can then be built, and tags (metadata) can be derived/associated with the content at different stages of the process.  </li></ul>
  23. 24. INTEGRATING DIMENSIONS (D. Bedford)  www.dtic.mil/mlw/2004/presentations/ Bedford . ppt   
  24. 25. The proposed architecture outline
  25. 26. EVALUATION <ul><li>- GOLD STANDARD (Grefstette) Compare and integrate the manual glossary with the ATX glossary </li></ul><ul><li>- Heuristic evaluation, competence questions </li></ul><ul><li>- Possible integrated evaluation of various factors, including 'cost' (people hours, cognitive load etc) may need to be developed </li></ul>
  26. 27. <ul><li>Coverage/ Scope </li></ul><ul><li>Is the vocabulary capable of representing all of the concepts used in the chapter? </li></ul><ul><li>Does the vocabulary have the terms necessary to represent the full range of issues? </li></ul><ul><li>Does the vocabulary encompass the terminology used to describe the various procedures? </li></ul><ul><li>Does the vocabulary use terms that are commonly used by SE? </li></ul><ul><li>Specificity </li></ul><ul><li>Is the vocabulary specific enough to accurately represent the many aspects of SE reality? </li></ul><ul><li>Does the vocabulary capture information in sufficient detail? </li></ul><ul><li>Structure </li></ul><ul><li>Are the vocabulary hierarchies logical and complete? </li></ul><ul><li>Are the meanings of terms clearly defined? </li></ul><ul><li>Does the vocabulary contain redundant terms? </li></ul><ul><li>Are there explicit rules for combining terms, or for combining terms and qualifiers? </li></ul><ul><li>Does the vocabulary allow for multiple classification of terms, that is, can terms appear in more than one hierarchy? </li></ul><ul><li>Maintenance </li></ul><ul><li>Does the vocabulary have ongoing institutional support? </li></ul><ul><li>Does the institution or body that developed the vocabulary have stable funding? </li></ul><ul><li>Useability </li></ul><ul><li>Is the vocabulary mapped to other vocabularies used in the practice? </li></ul><ul><li>Does the vocabulary meet the needs of a range of end users? </li></ul><ul><li>Does the user interface facilitate optimal use of the vocabulary with minimal training? </li></ul>
  27. 28. CONCLUSIONS <ul><li>This paper presents a socio-technical view of the challenges associated with developing and implementing and managing a shared vocabulary for SEBOK, and analyses various aspects of the problem space using innovative worldview and integrating various analysis and knowledge representation techniques. </li></ul><ul><li>It proposes an integrated ' emergent' architecture to combine vocabulary creation and management, with other aspects of the wikifcation task, including synchronizing the vocabulary development to the structuring of the SEBOK and the governance of the process. </li></ul>
  28. 29. FUTURE WORK <ul><li>Currently the SEBOK team is moving to a wiki, semantic wikification is going to be in a subsequent phase,  </li></ul><ul><li>The proposed architecture is intended to serve as guidance to capture emergence, and will have to be tested, refined and modified according to usage </li></ul><ul><li>A fully fledged text extraction exercise could result in a 'gazeteer for the systems engineering lexicon' to support text extraction  in the SE domain, using open source tools like GATE </li></ul>
  29. 31. Thanks <ul><li>This research is supported by EPRSC Grant EP/D505461/1. </li></ul><ul><li>Thanks to  University of Strathclyde (Alex Duffy), for funding and academic freedom </li></ul>
  30. 32. <ul><li>Get in touch  </li></ul><ul><li>[email_address] </li></ul>