JISC CETIS 2010 Day 1 Parallel Subverting & Integrating Corporate Systems

Get Started. It's Free
or sign up with your email address
Rocket clouds
JISC CETIS 2010 Day 1 Parallel Subverting & Integrating Corporate Systems by Mind Map: JISC CETIS 2010 Day 1 Parallel Subverting & Integrating Corporate Systems

1. Intro

1.1. Sharepoint

1.1.1. 78% HEIs using

1.1.1.1. document mgt

1.1.1.2. collaboration

1.1.1.3. targeting information

1.1.1.4. improving/automating cross institutional processes

1.1.2. why have a VLE if you have sharepoint?

1.1.2.1. why have sharepoint if you have a standards based, distributed, repository backed VLE?

1.1.2.2. or a standards based process driven web service delivered platform?

1.1.2.2.1. unicorn!

1.1.2.3. so portal v best of breed

1.2. JISC Programmes

1.2.1. curriculum design

1.2.2. DVLE

1.2.3. FSD

1.2.4. XCRI

2. Fantasy Curriculum Management System

2.1. Requirements

2.1.1. Scope/Definition

2.1.1.1. Just Course Catalogue

2.1.1.1.1. Core Data

2.1.1.1.2. Enriched Data

2.1.1.2. Course Delivery?

2.1.1.2.1. Course Selection

2.1.1.3. Big Picture = Big System

2.1.2. Different Audiences

2.1.2.1. Student

2.1.2.1.1. Informed Choices

2.1.2.2. Teachers

2.1.2.3. Employers

2.1.3. Learning Outcomes

2.1.4. Rules

2.1.4.1. Extensions not Exceptions

2.1.5. Lifecycle

2.1.6. Data Entry/Modification

2.1.7. Open Data

2.1.7.1. Persistence

2.1.7.2. Versioning

2.1.7.3. Course Ontology

2.1.8. Workflow

2.1.8.1. Agile

2.1.9. Analytics

2.1.10. Costing

2.1.10.1. Would know how much a course costs!!!!

2.1.10.2. Sensitive data

2.1.10.3. Most difficult area

2.1.10.4. Different pricing for different models (combination/delivery)

2.1.10.4.1. Costs

2.1.10.4.2. Loss leaders

2.1.10.4.3. Price point choices

2.2. Key (System) Players

2.2.1. Student Record System

2.2.2. Timetabling

2.2.3. Room Booking

2.2.4. Finance

2.2.5. VLE

2.2.6. Content Repositories

2.3. Interoperability

2.3.1. Seamless!

3. Southampton Learning Environment

3.1. what

3.1.1. central services hub

3.1.1.1. learning

3.1.1.2. teaching

3.1.1.3. living

3.1.1.4. appropriate to university role

3.1.2. vehicle for reviewing and aligning processes

3.1.3. flexible systems

3.1.4. single login

3.2. why

3.2.1. student experience

3.2.2. staff experience

3.2.3. employability

3.2.4. efficiencies

3.2.5. scale

3.2.6. teaching space problem

3.3. architecture

3.3.1. corporate systems

3.3.2. student facing applications

3.3.3. RDF layer (or some form of open data)

3.3.3.1. web services?

3.3.4. portal front

3.3.4.1. Sharepoint

3.4. system groupings

3.4.1. communications

3.4.2. fee payment/records

3.4.3. infrastructure

3.4.4. cloud services

3.4.5. push

3.4.6. resources

3.4.7. learning services

3.5. rich learning environment

3.5.1. personal space

3.5.2. institutional space

3.5.3. support space

3.5.4. social space

3.5.5. good for learning (external resources)

3.6. AGILE development

3.6.1. POCs

3.6.1.1. potential quick wins

3.6.1.2. personalised timetable

3.6.1.3. option selection

3.6.1.4. booking rooms for group work

3.6.1.5. well me what bus I need to get to my lecture on time

3.6.1.6. tutee information and progress

3.6.2. done

3.6.2.1. research portal

3.6.2.1.1. grant bids

3.6.2.1.2. projects

3.6.2.1.3. groups

3.6.2.1.4. academic CV generation

4. Strathclyde

4.1. DRIVER: Reorganisation and Reviews

4.1.1. Aspirations

4.1.1.1. Remove steps

4.1.1.2. Remove repetition

4.1.1.3. Single Source Data

4.1.1.4. Simplify Access to Data

4.1.2. Homegrown corporate systems

4.1.2.1. 1 Oracle Database: 4000 tables

4.1.3. Course and Class Approvals

4.1.3.1. Process Modelling

4.1.3.1.1. Information not Data

4.1.3.1.2. Decision Points not Timings or Criteria

4.1.3.1.3. Generalised model

4.1.3.1.4. BPMN

4.2. Architecture and Technologies

4.2.1. Presentation Layer

4.2.1.1. Tools

4.2.1.1.1. Sharepoint UI

4.2.1.1.2. jQuery

4.2.1.1.3. AJAX

4.2.1.1.4. ASP.NET

4.2.1.2. ? Why not a BPEL process platform ?

4.2.2. Service Layer

4.2.2.1. Orchestration

4.2.2.2. Service Interfaces

4.2.2.3. Message Types

4.2.3. Business Layer

4.2.3.1. Domain Model

4.2.3.2. Business Entities

4.2.3.3. Business Workflows

4.2.4. Data Access Layer

4.2.4.1. O/R Mapping

4.2.4.2. Service Agents

4.2.5. Data Stores

4.2.5.1. Tools

4.2.5.1.1. SQL Server

4.2.5.1.2. Sharepoint Lists

4.2.5.1.3. Document Libraries

4.2.5.2. Needed due to limits of Sharepoint

4.3. Data

4.3.1. Data structures not the problem

4.3.2. Making information timely and relevant is

4.4. Corporate v Education

4.4.1. Entrepreneurs

4.4.1.1. Control

4.4.1.1.1. is this subverting then?

4.4.2. Innovators

4.4.2.1. Promote

4.5. Standards/Specifications

4.5.1. Driven by external demands

4.5.2. Poor fit internally

4.5.3. No desire to adopt external models for internal apps

5. Staffordshire

5.1. Problems

5.1.1. Point to Point integrations

5.1.2. Reporting/Business Intelligence

5.1.3. External Examiner Appointment Process

5.2. Development

5.2.1. Agile

5.2.2. Continuous Delivery - not releases

6. My Thoughts

6.1. open data layers vs corporate portals and standardisation

6.1.1. published structures/apis

6.1.2. published guidance on standards

6.1.3. encouraging mashups/portlets/applications

6.1.3.1. institutional app store

6.1.3.2. discouraged by sharepoint usage

6.1.4. authentication/privacy

6.1.4.1. OAuth?

6.2. entrepreneurs vs innovators

6.2.1. standard experience/delivery

6.2.2. channel alliance

6.3. Strategy or Skunkworks?

6.3.1. high level support

6.3.2. enterprise architecture

6.3.3. roadmaps

6.3.4. portals

6.4. Process/Architecture v Facts/Rules

6.4.1. what's the best framework

6.4.2. who is building glossaries and rule repositories?

6.4.2.1. not just processes or architectures

6.4.2.2. not just domain models

6.4.2.3. published apis and data standards

6.4.2.4. taxonomies and ontologies

6.4.3. this is what we need to do

6.4.3.1. not this is how we do it

6.4.4. standardise inputs/outcomes

6.4.4.1. not control the bit in the middle

6.4.5. personas and scenarios

6.4.6. facts then rules then processes

6.4.6.1. information/data

6.4.6.2. decisions/rules

6.4.6.3. process/workflow

6.4.6.4. service connectors

6.5. Architecture v Ecologies

6.5.1. data, services and frameworks

6.5.2. not so much on the structure

6.6. mostly standardisation not subversion

6.7. CampusM not EA starting point for SOA

7. MMU

7.1. Barriers

7.1.1. Reasons for Vagueness

7.1.1.1. reasonable behaviour in small units

7.1.2. Change Everything!

7.1.3. Rollover + tinkering

7.2. Not really Sharepoint

7.2.1. Getting the Point of Sharing

7.3. Joined Up Imagination

7.3.1. blend specialist expertise

7.4. Creative Dialogue

7.4.1. scenarios

7.4.2. prototyping

7.4.3. stakeholder walk-through workshops

7.4.4. enterprise architect know how

7.4.4.1. identifiers for integration

7.4.4.2. joining islands

7.5. myMMU

7.5.1. shame corporate systems into developing web services

7.5.2. apis.mmu

7.5.2.1. web service feeds

7.5.3. Sharepoint + Mobile