tim50-lecture12-handouts-x2

tim50-lecture12-handouts-x2 - TIM 50 - Business Information...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
1 TIM 50 - Business Information Systems Lecture 12 Instructor: Terry Allen UC Santa Cruz 11/2/2011 Announcements Database Lab available You will need to attend one session to do the database assignment Tutorial will also be available, run by TAs Assignment 3 posted later this week DUE next Monday, 11/14 For next time read: Messerschmitt Ch. 7
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Modularity and Layering Application Architecture Design The most important step to reduce/control complexity Hardest to change Influences everything that follows Conceptualization What is it you are trying to do? Example Concept: Small HHC for flight attendants. HHC tells flight attendants which passengers are higher priority. Who paid the highest fares Who has been a more valuable customer in past (e.g. frequent flyer points) Flight attendant discriminates based on this Free drinks, meals, and pillows to valued customers
Background image of page 2
3 Example Concept: Architecture What is the complexity of such a problem? How do you begin to architect a solution for a problem like this? Follow the principle that says: Break it into modules! What is a “good” architecture?
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Architecture Airline Dataserver HEADQUARTERS HHC HHC Server Airline Intranet Wireless Link Each Tier is decomposed into modules HHC Architecture When a module is composed of sub-modules, the architecture is hierarchical . HHC Application Palm OS Networking Infrastructure User Interface Coordination With HHC Server Data Management
Background image of page 4
5 HHC Architecture We are using a layered architecture as well. Allows reuse of previously built infrastructure. HHC Application Palm OS Networking Infrastructure User Interface Communication With HHC Server data management Some aspects of software complexity 1) The number of elements (or participants) increases system's complexity increases 2) The problem domain is complex 3) A lot of constraints 4) Every case must be foreseen 5) Continuous vs discrete, cannot exhaustively check every case 6) Team effort 7) Integration of different parts
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Properties of Modularity (idea: divide into smaller parts and deal with each part separately) Functionality Hierarchy Separation of concerns “Easier to code for one goal than ten goals” Interoperability Reusability Student Talks Wai-Son Wong
Background image of page 6
7 A simple interface: from within our HHC Server Architecure HHC Application Windows OS Networking Infrastructure Computation of key statistics Communication
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 23

tim50-lecture12-handouts-x2 - TIM 50 - Business Information...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online