ࡱ> n+0B捪4E2&PNG  IHDRi~+sBITOPLTE̙3f3ffff33f33̙f3̙̙̙f̙3̙ffff333̙̙f3̙f3ffff3f3333ffff3ffffffff3fff3ff33f3f333f333f3f3ff3f33f3333f33333333ffff33f3333:BZtRNS֊obKGDHIDATx[ { p,A*-'-I`æگ E3G+[ Ijc i+$FHG[ s;o@zrJv& H qLߎ3\r? $`Ӹs0äHJ+\\wFIlX`w;1yf3gpcv?{hMwGg4M0͒%%0Aiv{DRR^!ht}IEI-k$A^f&(%b?w(oA&+OQ1cNna} ?nx#yr}^Hq fqAo[+񯌩Ӹa욦gvLޏN ZuB]^Q#c[=]h2%E ltMZ H)78oM󼭔E 0:JsT{=W8(8o|Pyے FzXng/!%|֘#p6굆T84 :wآt>_`2ԺUNxº J@ﭜ@%!uϩ;U67 @ 8 [H#J rN32@/XD~척Fl )SO%>ct, 4^hdףUȅZ} olnu٩"ahV[)@)pɴG#)9@ '\>RWdh#R\uMfԿ@DSe'Ўe| 5R:j N@ (:F Tpdv:>2R7ؤK@>Gהʎ^yل-HII1BBqؤ@R-WvҏP9 ;mO>7CnK8q\".,'TY"^ˣJ[x9);tAPu6"\N k k5:2Ej'u]3;];<%D%,D%;H>8g+Fq 7L$GKo8Q%ľ10A#&j6-u`n'M$Hz;IYN 1m ND@f֐W\Gzn\.lc1/d88c_2Pv֐P3*9a'y&y'}{O{ox}}HE՟PqÏƇlŃvW$>^'9Hrc%*Lu]ֿS]= v!HtCL$/q%\?FF M BhO{E,2~:\"nf8|eOǒx H:R;|0,}{ֹ>W.~cLnv5x*>"^oIAjtNBR vR\qvbg67dחH۞vIA 'W[^n@CIC#热ZiiSFVZ?sb Q/W؊S"FYv gI5I(d('|6[e4b)&4F춲 1 Yu]1ʕfp)I*a0BW)wh8#aڱth-A~EvQ׉z:-H%ĖlM[Z 'D 4n EJ$g0EzT)c 8>Lk :˽w[ޫG@‰Q 8K *lȰr:lK0\fds%, Ke OJVI-ќpkes'fb:|/#]\:,fӂGx2H=}&p[["Xt^mp"њ傥I 5ZY+iS +ۡJkX ]___PPT9 / 0z? -O =Y3.A Systems Model for the Field of Informatics //d A. J. Cowling@ Structure of PresentationlBackground A model for the structure of the SE curriculum General systems theory applied to Informatics Hierarchical curriculum models The Proposed Three-Dimensional Model The products dimension The process dimension The people dimension relationships with products and processes Evaluation and Conclusions Comparison with the Great Principles model Conclusions. }%B*8 }%B*   8 ,The SE CurriculumA Multi-Dimensional Model Three main dimensions: products, processes and people 1 Products defined in terms of levels of abstraction of components 2 Processes defined in terms of relationships to people: individuals, groups and markets Also introduced a further dimension: balance of theory and practice. Application to SE Described its relationships with other disciplines: Computer Engineering, Computer Science, Information Systems % 4<7A7 %    4<-General Systems TheoryThe British Computer Society The UK Professional Body for Information Systems Engineering; Accredits degree programmes in this whole area: viz Computer Science, Computer Engineering, Software Engineering, Information Systems, Information Technology, Artificial Intelligence, etc Hence covers the whole of Informatics; Accreditation criteria need to be applicable throughout. The Artefacts Being Studied For all programmes the products are information systems; Different programmes focus on different aspects of these systems; General Systems Theory is applicable to all of them; It defines key aspects that must be covered in all programmes.na2a.Hierarchical Curriculum ModelsUsual Structure Curriculum for a discipline consists of knowledge areas; Knowledge areas consist of knowledge units; Knowledge units consist of topics; Topics may have attributes: core or optional, levels on Bloom s taxonomy, etc. Limitations Different disciplines may need different views of the same knowledge area 3: different structures of units, or emphases; Within a discipline, relationships between different areas or units are not easily represented.3 M,`3 J    , `  Unifying These ApproachesAFocus: Knowledge Structures and Relationships Approach: A Three-Dimensional Model Places Informatics knowledge areas in a space; Key dimensions for this space: Products, Processes and People Each dimension has a hierarchical sub-structure: For products, from general systems theory; For processes, from activities and the information they use; For people, from organisational structures. Omission The balance of theory and practice is not included as a dimension: this would be desirable, to link theory to applications, but the structure for such a dimension is not clear.T/%N1 Cn/%N 1    #  4   "  Cn>"The Products Dimension 1Hierarchical Structure Root levels (nearest the origin) derived from core computing concepts; Layered to match levels of abstraction; Leaf levels derived from application domains of computing. Aspects of the Levels All levels relate to kinds of information systems; Aspects of the root levels come from General Systems Theory: systems are structured from sub-systems by some paradigm, systems have a purpose (ie processing and storage of information), systems have a boundary, across which they communicate, internal sub-systems must communicate to achieve purpose; Aspects of the leaf levels all involve different kinds of abstract software components interacting.tpdpd!The Products Dimension 2 "The Processes Dimension 1Two Structures for Processes Abstract, in terms of sequences of activities that produce models; Concrete, in terms of plans, resources and their control.&}}#The Processes Dimension 2Combining These Structures% The People DimensionLevels of Organisational Structure The opposite way round to the usual organisational hierarchy; root level (nearest the origin)  individuals, middle levels  different sizes of teams, outermost level  organisations or business units. Structures Within Levels Each level will have a variety of purposes; These will lead to different application domains. Roles of People Reflected in relationships with product and process dimensions: as users of products, as developers working within processes.#>_@>#>_      ( Combining the DimensionszForming a Knowledge Space Any topic can therefore be located in the space by: which abstraction level of products it refers to, which aspect of systems theory it covers, or which application domain, which abstraction level of processes it refers to, what size group of people it relates to. Example Database normalisation (a topic in CS, CE, SE, IS and IT); Irrespective of programme, this is concerned with: the storage aspect of the software components level, for domains involving information with an ER structure, the design activity that involves manipulating ER models, the business of the organisation requiring the database.4n4n 0The Great Principles Model 16Also Multi-Dimensional Two main dimensions: principles and practice. The Principles Dimension Has two elements: mechanics and design; Both focus on laws: for  what and  how . Mechanics corresponds to the general properties of systems cf the five windows: automation, coordination, computation, recollection (storage), and communication; Design corresponds to how two elements are brought together: the characteristic properties for specific products, and the relationships between components that produce these. The Practice Dimension Identifies generic activities that underpin processes: innovating, engineering, modelling, validation, programming, applying.Z0ZZZgZ=ZsZZZ7ZGZ0g= s 7G3The Great Principles Model 2mStructuring The Space Identifies two components: applications and core technologies. Applications and Domains Concerned with why people need computing; Correspond to the application domains for products, and their relationships with people. Core Technologies Currently 30 of these: from algorithms to workflow; Capture key common features of domains; The principles and practices capture how this happens. Correspond to areas within the knowledge space: some mainly focus on lower level products (databases, compilers, networks, operating systems, etc), others on kinds of applications (graphics, robots, vision, etc).Z@ZZZZZZ@ 9 Evaluation|Application of the Model to the Whole Field All informatics disciplines involve products: which are information systems, so general systems theory is applicable to them; All informatics disciplines involve processes: historically some have not given them much attention, but to prepare students adequately for careers they should! maybe this part of the Great Principles model is weak; All informatics disciplines involve people, either as users, developers or both. Does the Model Cover The Whole Field? The above suggests that it does; The acid test will be mapping current curriculum models into it: one example topic is not enough!,.P/R&b!,.P/R &  b!* ConclusionsoA Model for the Whole Field of Informatics The structure of the model has been defined; It reflects fundamental principles: eg the application of general systems theory to products; Its structure allows it to capture relationships between topics: in a more general fashion than conventional hierarchical curriculum models. Restricted to Knowledge Structures It does not capture the balance of theory and practice; Hence, it ignores some distinctions between disciplines. Future Work To map existing curriculum models into this model: ie to place actual topics in this space; To include the balance of theory and practice.+Q:AL#r 3)/+Q:AL #  r 3)/,|V=!The End- Thanks for your attention!! Any Questions?R$.  ` ̙33` ` ff3333f` 333MMM` f` f` 3>?" dd@ ?" dd@n  @̙ ` n?" dd@   @@``PP    @ ` ` p@@ ZR (    6DV "  T Click to edit Master title style! !$  0X "p  RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  0] "`  iInf. Edu. Europe 2006  0Da "`   y9University of Sheffield Department of Computer Science$:9  00 " : 2 lB   6DԔ"  p   C JA2\\U2\ajc\crest_white.gif"ilB  @ 6DԔ"``   C JA2\\U2\ajc\crest_white.gif"IH  0޽h ? ̙33 ExtSlides0 zr@ (     0h-P P   P P*    0JP    P R*  d  c $ ?  P  0MP  @ P RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  6P `P  P P*    6UP `  P R*  H  0޽h ? ̙33 P8(    0P P    >*   0\P    P @*   6LP `P  P >*   6*P `  P @* H  0޽h ? ̙33 ~ (  l  C L4P  l  C h[p0    0L : 2   0u0 P z8Department of Computer Science University of Sheffield &9(8r  C JA2\\U2\ajc\crest_white.gifP`  H  0޽h ? ̙334  0\(  ! M x  c $[     c $[p<$0  H  0޽h ? ̙33~   (  r  S 4     S V` <$0  N  0M`  p$D0<4___PPT9 vA. J. Cowling, A Framework for Developing the SE Curriculum, Proc. International Workshop on SE Education, Sorrento, 1994, pp 111  118. A. J. Cowling, A Multi-Dimensional Model of the SE Curriculum, Proc 11th CSEE&T, Atlanta, 1998, pp 44  55.Z 2,^.  $ @`H  0޽h ? ̙33(  P(  r  S 8     S Tp<$0  H  0޽h ? ̙33  "(  r  S d      S T/ <$0  Z  0d8P  ,$D0 N3. A. J. Cowling, Teaching Data Structures and Algorithms in a Software Engineering Degree: Some Experience with Java, Proc 14th CSEE&T, Charlotte, 2001, pp 247  257.F 2cb  ( @`H  0޽h ? ̙33(  pP(  pr p S     p S <$0  H p 0޽h ? ̙33(  P(  r  S      S  0<$0  H  0޽h ? ̙33al  kk0t}k(  tr t S     jz 1 t 1,$D0T ny Ct# 1K t N`+Cy eLevel of Abstraction 4# " r Bt BnyT ny Et# 1K t N4%y eStructuring Paradigm 4# " r Dt BnyT 6y Gt# 1 K t N+ y [ Processing 4  # " r Ft B6yT 6= y It#  1 K  t N0a y XStorage 4 # " r Ht B6= yT = y Kt#  1`K  t N5h y gInternal Communication 4# " r Jt B= yT  y Mt# `1K  t N@;! y gExternal Communication 4# " r Lt B yT yn Ot# K1  t N(+yC ZAnalogue Circuits ,# " r Nt BynT ny Qt# K1  t NWy S Modulation , # " r Pt BnyT y6 St# K 1 t N\y  VGate circuits , # " r Rt By6T 6y=  Ut#  K 1 t Naay  Q Feedback , # " r Tt B6y= T = y  Wt#  K`1 t N,gh y  YAnalogue signals ,# " r Vt B= y T  y Yt# `K1 t Nl! y YAnalogue signals ,# " r Xt B yT n [t# 1K t Nq+C YDigital Circuits ,# " r Zt BnT n ]t# 1K t N4w Q Clocking , # " r \t BnT 6 _t# 1 K t N|  uCombinatoric logic ,# "  r ^t B6T 6=  at#  1 K t N$a  YSequential logic ,# " r `t B6= T =   ct#  1`K t N|h   XDigital signals ,# " r bt B=  T   et# `1K t NԌ!  aPhysical layer protocols ,# " r dt B T nq  gt# Ke t N,+Cq  [Digital Components ,# " r ft Bnq T nq  it# Ke t Nq  ZMicro-programming ,# " r ht Bnq T 6q  kt# K e t Nܜ q  S Processors , # " r jt B6q T 6= q  mt#  K e t N4a q  Q Memories , # " r lt B6= q T =  q  ot#  K`e t NXh  q  NBuses ,# " r nt B=  q T  q  qt# `Ke t NP! q  \MAC layer protocols ,# " r pt B q T q n]  st# e t N+q C]  E Computers # r rt Bq n] T nq ]  ut# e t N( q ]  MAssembly language # r tt Bnq ] T q 6]  wt# e   t N̺q ]  `Interrupt handling, etc ,# " r vt Bq 6] T 6q = ]  yt#  e  !t Nܿaq  ]  WVirtual memory ,# " r xt B6q = ] T = q ]  {t#  e` "t Nh q ]  YDevice level I/O ,# " r zt B= q ] T  q ]  }t# `e #t Nl! q ]  gLink & network layer protocols , # " r |t B q ] T ] n t# 2  $t NP+] C T OS Services , # " r ~t B] nT n]  t# 2  %t N\]  _Imperative programming ,# " r t Bn] T ] 6 t#  2  &t Nh]  NProcess management # r t B] 6T 6] =  t#   2  't N8a]   WFiling systems ,# " r t B6] = T = ]  t#  `2  (t Nh ]  ZBuffer management ,# " r t B= ] T  ]  t# `2  )t N\! ]  bTransport layer protocols ,# " r t B ] T n t# 2   *t N+C ]Programming Concepts ,# " r t BnT n t# 2   +t N$ ^Programming paradigms ,# " r t BnT 6 t# 2    ,t N   sTranslators, VMs ,# "  r t B6T 6=  t#  2   -t N` a  T Data typing , # " r t B6= T =   t#  2 `  .t N h   U Data streams , # " r t B=  T   t# `2   /t N !  `Session layer protocols ,# " r t B T n t#    0t N=`+C aProgramming Abstractions ,# " r t BnT n t#    1t NB` _ADTs ,# "  r t BnT 6 t#    2t N0G`  _Procedures and methods ,# " r t B6T 6=  t#    3t N`a  XData structures ,# " r t B6= T =   t#   `  4t N8&`h   \GUIs, event streams ,# " r t B=  T   t# `   5t N+`!  dApplication layer protocols ,# " r t B T n  t#    6t N0`+C  MAPIs ,# " r t Bn T n  t#    7t N5`  \Software components ,# " r t Bn T 6  t#    8t Tm`   N "  r t B6 T 6=  t#   9t N(r`a  N "  r t B6= T =   t#  `  :t Nt`h   N "  r t B=  T    t# `   ;t N`!   N "  r t B  T  n t#   t NDzP   L Domain - &  #  r t B 6T 6 =  t#   ?t N~Pa   W specific 2 # " r t B6 = T =   t#  ` @t NPh   [ abstractions 2 # " r t B=  T   t# `  At NP!  N "  r t B H t 0޽h ? ̙33J  @"x b(  xr x S @    x S (`<$0  z ( x (,$D0  x 3 M Mspecify   x C PjJh S Methodologies   x C PjJ0p  P Activities     x C DPjJ  P Sequencing     x C  BPjJ0 p  LModels    x C DPjJP ( O Notations   TB  x c $Doh TB xB c $DoPh x 3 PP   P manipulate   TB x c $DoP P  x 3 PP0   Iuse  TB x c $DoP PP l  H  "x H ,$D0 x C 4PjJ  TProcess Models   x C PjJ` P  ^Objectives & Constraints   x C pPjJ @P  _Schedule & Work Breakdown   x C PjJ p P H  O Resources    x 3 P0 X  Jneed   x 3 P x Jneed  TB xB c $Do0  TB x c $Do TB x c $Do P p fB  xB 6Do@ ` H x 0޽h ? ̙33|   !| (  |r | S     | S $+<$0  < z ` !| `,$D0 | 3 8`   P manipulate    | 3 4 8  Iuse   | 3    Mspecify    | C 謖jJX  S Methodologies    | C jJ p  O Processes     | C  0jJ`   WActivity Sequence    | C |jJ `   `Objectives & Constraints    | C 0{jJ`  _Schedule & Work Breakdown   | C jJ   LModels   | C ԶjJ(  O Notations   TB | c $Do (TB | c $Do   | 3 ๖ @   Jneed  TB | c $Do  ` TB | c $Dop p` TB |B c $Do` ZB |B s *DjJ ZB |B s *DjJ    | C jJ p  O Resources    | 3 `   Jneed  TB | c $Do  TB | c $Do 0  | 3   H  Nallocate   TB | c $Do  H | 0޽h ? ̙33(  P(  r  S       S p<$ 0  H  0޽h ? ̙334  \(  x  c $     c $|p<$0  H  0޽h ? ̙33(  P(  r  S S     S 8<$0  H  0޽h ? ̙33(  P(  r  S P  P   S Pp<$0 P H  0޽h ? ̙33(  P(  r  S @!P  P   S Pp<$0 P H  0޽h ? ̙33(  pP(  r  S P  P   S .P00<$ 0 P H  0޽h ? ̙33  `0(  x  c $4P0  P x  c $Pp P H  0޽h ? ̙33___PPT10i.,)`0+D=' = @B +r00:OfE R @jae3% (9*P(K"UZ\0u39= 5c  >Oh+'0@J hp( 4@ ` l xETranslating Diagrams: A New Approach to Introducing Formal Methods oajcQF:\Documents and Settings\ajc\Application Data\Microsoft\Templates\ExtSlides.potaajc74Microsoft PowerPointing@@@ ~GHg  N$& &&#TNPP2OMi & TNPP &&TNPP    --- !-----y8H-- w@, ww0- @"Arialw@2 ww0- .%2 z A Systems Model for  & $  . .-2 the Field of Informatics      &  .--)-- @"Arialw@, ww0- .2 t A. J. Cowling   .--Q  -- --o9--  .62 ,Department of Computer Science        . .+2 b3University of Sheffield         .&7.C~i8(i~???????????????C~i8(i~=Y3333f3333f3333333f33333f33ff3f3333333f3fffff33f3ff3f3f3ff3ffffffff3ffff3ffff3ffff̙33f3f3ffff3f̙3f̙3f̙33̙3̙f̙̙̙3f3G<77777777777777 $ 777LKGLLL=F<773$ 777 7 G $#6<@PKQXLXXLXL78XT78XXXLMWXP<6$ 68 LXXX7 7&@;<@PP76 E7XL L X2=7LK X 7L <7PQ;@$#77 L L7 7 '*?;'$ K$ W =KX 7X7 UX 7 XLL K$6P;:59:>HNHHH&#44N   4#4544#459C:#&#::9H95#145#47K 2="545"444549###:4551445 7 =3 L7Q3 "4#1$"5# "#7##4 !T 3Q 8  7 L3L3 !7"56RXTL76$$6#6667LWXX70 7!L!!L 7!7LL 7K!W7 "1"6XXRXXXXXWRXLFXXXXXXXXQXX<4W%7L 7X 7 73 7G G<3L!77"57XXWXXXXXXXXL7XXXXXXXWXXX7" <L!L77L 7! 77W7K!9H  ::>4VNI"4V:VN4HNVHNI45VN5::# #"4#4N4#4NHH5I9H4#4N"1###  ##4549HHH:NHH#HNH9IH95H#"&   9545"45HNVN45""459  491H5HH#H5H    44NH5   D4#H "5HV"5  :NH5  44 4HH 5" NNC"9H# 455"44 "H5"9NS  #V45NVH:1 HNHHNNHOHH 19HVN54N  HN5  9I4 494NH 5NH   5NV4  9HHNH5HINH9 4VN4  HN5 4V"V #HH HH  #V4VH  9N  4I4H9 4    N:V  HHH4 4NHH IH5  "I      &--"System 0-&TNPP &՜.+,0    >On-screen ShowUniversity of Sheffield Times New RomanArial Wingdings ExtSlides/A Systems Model for the Field of Informatics Structure of PresentationThe SE CurriculumGeneral Systems TheoryHierarchical Curriculum ModelsUnifying These ApproachesThe Products Dimension 1The Products Dimension 2The Processes Dimension 1The Processes Dimension 2The People DimensionCombining the DimensionsThe Great Principles Model 1The Great Principles Model 2 Evaluation ConclusionsThe End  Fonts UsedDesign Template Slide Titles_fajcajc  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root EntrydO)Pictures3Current UserSummaryInformation(pJPowerPoint Document( DocumentSummaryInformation8Root EntrydO)`C%L@Pictures3Current User/SummaryInformation(pJ_f KarenKaren