GIS Architectures, 2'5'2006

1
GIS Architectures, 2.5.2006

• IS Network
• Mobile IS
• Human resources
• Training
• Computing policies
• Security

2
Cell phone generations

• 1G networks (NMT, C-Nets, AMPS, TACS)
• the first analog cellular systems, which started
  early 1980s. There were radio telephone systems
  even before that.
• 2G networks (GSM, cdmaOne, DAMPS)
• the first digital cellular systems launched early
  1990s.
• 2.5G networks (GPRS, cdma2000 1x)
• the enhanced versions of 2G networks with data
  rates up to about 144kbit/s.

http//www.umtsworld.com/umts/faq.htm
3
Cell phone generations

• 3G networks (UMTS FDD and TDD, cdma2000 1x EVDO,
  cdma2000 3x, TD-SCDMA, Arib WCDMA, EDGE, IMT-2000
  DECT)
• the latest cellular networks that have data rates
  384kbit/s and more.
• 4G
• mainly a marketing buzzword at the moment. Some
  basic 4G research is being done, but no
  frequencies have been allocated. The Forth
  Generation could be ready for implementation
  around 2012.

http//www.umtsworld.com/umts/faq.htm
4
Network localization

• Practical localization for cell phones
• Cell phones work in cells which have base
  stations, which (or groups of which) keep track
  of open phones
• base station network is dense because they
  operate on very high radio frequencies, which do
  not reflect easily
• In principle location could be calculated in the
  phone but in practise this is done in separate
  localization servers at base stations

5
Network localization methods

• Several methods which augment the basic cell
  identification method exist
• An example

road
car with one or more cell phones
base station
6
Mobile computing

• Laptops
• wireless network connections via WLAN, GSM, GPRS,
  ... (Internet protocols)
• Cars, Boats,
• PDAs (portable digital assistants)
• wireless network connections via WLAN, GSM, GPRS,
  ... (Internet protocols)
• on person
• Mobile phones
• 2G SMS 2,5G GPRS (WAP) 3G broadband (WAP,
  Internet protocols)

7
HS vieraskynä 13.10.2003Juha Koivisto Hyöty
irti tietojärjestelmistä

• Main cause for failures in implementing an IS is
  not a technical one, but human/organisation
  related one
• lack of commitment in the management
• a lot of time is spent in solving problems and in
  extra work caused by disintegrated ways of working

8
Two different views

• The vendor/consultant
• thinks the problem is a technical one
• has no or little interest in the future of the
  client
• The organisation
• (should) see the problem as one of learning and
  change

9
Possible solution

• (still by Koivisto, Turun yliopiston
  tietojärjestelmälaboratorio)
• Description, Training, Use
• Two descriptions
• How are things done now?
• How things will be done with the new system?
• Recap GIS Design

10
Training

• Training has to be based on the task of the
  employee (not on the IS)
• how things were done before
• how things will be done with the new system
• Implementation of the IS is not over till new
  institutions are in place
• institutions how things are done
• Have faith in the local knowledge
• use local instructors
• local employees are experts on their tasks
• but to a limit

11
Organisation and GIS

• Software hardware people
• Organisational structures
• task structure
• specialization / generalization
• support people, experts
• Communication
• Links to non-GIS and non-spatial

12
Organisations

• Are often large, or have a large network
• interoperability
• institutions
• things change slowly!
• Costs vs. benefits
• Customers, products

13
Human side of system development

• Development
• Implementation
• Use
• Developers (technical problem)
• Implementors (organizational change and learning)
• Users (individual learning process)

time
14
(No Transcript)
15
GIS staff (Harmon and Anderson)

• Viewer
• Spatial data modifier
• Attribute data modifier
• Application developer
• GI database administrator

16
Implementation process

• Description
• how does the new system change existing work
  processes?
• Training
• training should be organised (customized)
  according to the job descriptions people have
• Use
• implementation continues until the use of the new
  system is routine
• implementation has to be monitored

17
Capacity building

• Common term used by development agencies in
  relation to resource management
• Empowering individuals and organisations to
• assess their own information needs
• set their own priorities
• build their own information systems
• Not just provision of hardware, software, and
  training

18
Policies

• General computing policy
• General internet policy
• Electronic mail policy
• Software policy
• Hardware policy
• Support policy
• Backup policy
• Web development policy
• ...

19
What is in the policies?

• Mostly free / mostly forbidden
• free anything not specifically forbidden is
  allowed
• Who is responsible of what?
• Who can/should do what?
• Procedures when acquiring new hardware/software
• General guidelines for new hardware/software
• for example monitor resolution

20
Backup hardware

• Against hardware failures / user mistakes
• Backup vs. Archiving
• Hardware
• Tape drives (DAT, DLT, SDLT, ..)
• largest DAT tape is 72 GB
• Magneto-optical devices (archival)
• optical disk is typically 9 GB but they can be
  used in large jukeboxes
• CDR, DVD

21
Backup policies

• What is stored and how often?
• System software, local customizations, data, user
  files
• Complete backup
• once a month, twice per year
• Incremental backup
• daily
• Note all versions of the files are stored
• How long backups are stored?
• reliability of the media

22
Security

• Secure computing?
• See for example Trusted Computing
• Information security?
• compare Information / system availability
• Integrity of systems and data
• Unauthorized access/changes has not happened
• Secure/logged access/changes
• Trust in the system and in the data
• Damages due to loss of confidentiality

23
Dimensions of security

• Levels of access rights
• type of user
• type of action
• Strength of protection
• security through obscurity
• DO NOT TRUST
• unencrypted passwords/communications
• work against casual user
• secure communications
• encrypted

24
Example SQL rights model

• GRANT SELECT INSERT UPDATE DELETE
  RULE REFERENCES TRIGGER
• ,... ALL PRIVILEGES
• ON TABLE tablename , ...
• TO username GROUP groupname PUBLIC ,
  ...
• GRANT CREATE TEMPORARY TEMP ,...
  ALL PRIVILEGES
• ON DATABASE dbname , ...
• TO username GROUP groupname PUBLIC ,
  ...
• GRANT EXECUTE ALL PRIVILEGES
• ON FUNCTION funcname (type, ...) , ...
• TO username GROUP groupname PUBLIC ,
  ...
• GRANT USAGE ALL PRIVILEGES
• ON LANGUAGE langname , ...
• TO username GROUP groupname PUBLIC ,
  ...
• GRANT CREATE USAGE ,... ALL
  PRIVILEGES
• ON SCHEMA schemaname , ...

To remove rights use the command REVOKE.
25
Internet security

• Firewalls
• packet-filtering (source and dest IP ports)
• stateful inspection (connection awareness)
• application-level (content examination)
• Daemons
• accept connections only from selected addresses
• no holes in the socket interface
• do not allow remote execution of insecure code
• Email attachments and downloads
• need virus protection in client computers

26
Classification of information

• Top secret
• Matters of public safety
• Secret
• Security arrangements, Logs
• Confidential
• Personal information, Communication
• Public

Management, Life cycle (incl. disposal),
Archiving