Successfully reported this slideshow.

Design Intent Ontology presented at WOP2015

1

Share

Loading in …3
×
1 of 13
1 of 13

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Design Intent Ontology presented at WOP2015

  1. 1. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern   h7p://purl.org/dio   Monika  Solanki   University  of  Oxford,  UK   monika.solanki@cs.ox.ac.uk   h7p://www.monikasolanki.uk   WOP2015  at  ISWC2015  
  2. 2. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern   MoMvaMon   •  Most  current  approaches  for  design   documenta<on  focus  on  the  “what”  and  “not”  on   the  “why”.   •  CollaboraMve  design  à  communica<on  intensive   à  need  to  preserve  design  decision  ra<onales     for  posterity.   •  Legacy  methodologies  lack  the   conceptualisa<ons  needed  to  relate  designed   arMfacts  to  their  origina<ng  requirements.  
  3. 3. Source:  Wikipedia   A  specifica<on  of  an  object,  manifested  by  an   agent,  intended  to  accomplish  goals,  in  a   par<cular  environment,  using  a  set  of  primi<ve   components,  sa<sfying  a  set  of  requirements,   subject  to  constraints   What  is  a  Design?  
  4. 4. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern   Intent   DIO  provides  a  minimalisMc  abstrac<on  and   defines  conceptual,  generic  en<<es  for  the   modelling  of  seman<cally  enriched  knowledge   required  to  capture  the  intents  or  raMonale   behind  the  design  of  an  arMfact.  The  pa7ern   can  be  specialised  to  define  domain  specific   design  intents.  
  5. 5. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern     Typical  Competency  QuesMons     •  What  are  the  solu<on  choices  for  a  design  goal?   •  Which  requirements  are  being  fulfilled  by   the    accepted  design  solu<on?   •  What  are  the  jus<fica<ons  for  a  proposed  solu<on?   •  What  are  the  arguments  against  a  proposed  solu<on?   •  What  is  the  status  of  a  design  issue?   •  Which  agents  have  supported  a  solu<on?  
  6. 6. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern   ConceptualisaMon    
  7. 7. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern  
  8. 8. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern   AxiomaMsaMon    
  9. 9. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern     Pa7ern  specialisaMon:  SoTware  Design  Intent    
  10. 10. Capturing  Design  Intents   DIO:  A  content  ontology  design  pa7ern     Pa7ern  instanMaMon:  JIRA  issues    
  11. 11. Monika  Solanki   University  of  Oxford,  UK   monika.solanki@cs.ox.ac.uk   h7p://www.monikasolanki.uk  

×