Chapter 4 Design -...

Introduction Architectural Design Application Architectures Object-Oriented Design Interface Design

Chapter 4 — Design

May 13, 2009

Chapter 4 — Design 1/72

Outline

1 Introduction

2 Architectural DesignSystem OrganizationDistributed Systems Architecture

3 Application ArchitecturesTypes of AAs

4 Object-Oriented DesignObject-Oriented Design Process

5 Interface Design

Introduction

Logical organization of software

UML modelsketches, drawings, notes

creative process: no real “method”learn from previous design experiences

Introduction

Logical organization of softwareUML model

sketches, drawings, notes

Introduction

Logical organization of softwareUML modelsketches, drawings, notes

Introduction

creative process: no real “method”

learn from previous design experiences

Introduction

In This Chapter

Learn about software design perspectives and ideas

Architecture: abstract formulas and patternsSpecific Issues: common to most software designs

object-oriented designuser-interface design

In This Chapter

Learn about software design perspectives and ideasArchitecture: abstract formulas and patterns

Specific Issues: common to most software designsobject-oriented designuser-interface design

In This Chapter

Learn about software design perspectives and ideasArchitecture: abstract formulas and patternsSpecific Issues: common to most software designs

In This Chapter

Learn about software design perspectives and ideasArchitecture: abstract formulas and patternsSpecific Issues: common to most software designs

Introduction Architectural Design Application Architectures Object-Oriented Design Interface DesignSystem Organization Distributed Systems Architecture

Outline

1 Introduction

5 Interface Design

Introduction

System is composed of sub-systems

Architectural Design:identify sub-systemsframework for sub-system control and communication

affects performance, robustness, availability, maintainability

Introduction

System is composed of sub-systemsArchitectural Design:

identify sub-systemsframework for sub-system control and communication

Introduction

System is composed of sub-systemsArchitectural Design:

identify sub-systemsframework for sub-system control and communication

Outline

1 Introduction

5 Interface Design

Organization

Reflects basic strategy for the structure

Common organization styles:repositoryclient-serverlayered

Organization

Reflects basic strategy for the structureCommon organization styles:

repositoryclient-serverlayered

Repository Model

If large amounts of data: central, shared repository or DB

otherwise: DBs for each subsystem

Advantages / Disadvantages:efficient for sharing (all sub-systems must agree on data model)backup, security, access control are centralized (agreement)

Repository Model

If large amounts of data: central, shared repository or DBotherwise: DBs for each subsystem

Repository Model

Advantages / Disadvantages:

efficient for sharing (all sub-systems must agree on data model)backup, security, access control are centralized (agreement)

Repository Model

Advantages / Disadvantages:efficient for sharing (all sub-systems must agree on data model)

backup, security, access control are centralized (agreement)

Repository Model

Client-Server Architecture Model

System as a set of services

Components:servers: offer services.

e.g., web, print, file, compile

clients: consumer servicesnetwork: connects the two

not always necessary if not distributed

Clients must know name, services of available serverse.g., DNSnot vice-versa

Clients access services using RPC with a request-reply protocole.g., http protocol for WWW

Client waits for a reply

System as a set of servicesComponents:

servers: offer services.e.g., web, print, file, compile

servers: offer services.

e.g., web, print, file, compile

clients: consumer services

network: connects the twonot always necessary if not distributed

Clients must know name, services of available servers

e.g., DNSnot vice-versa

Clients must know name, services of available serverse.g., DNS

not vice-versa

Clients access services using RPC with a request-reply protocol

e.g., http protocol for WWW

Client-Server Achitecture Model

E.g.: Video and Photo Library system’s architecture

Advantages:

Distributed architecture: processing, storagemake changes transparently

Best used if using shared data modelotherwise may need to translate for each sub-systemXML can be used, but slow

Advantages:Distributed architecture: processing, storage

make changes transparently

Advantages:Distributed architecture: processing, storagemake changes transparently

Best used if using shared data model

otherwise may need to translate for each sub-systemXML can be used, but slow

Best used if using shared data modelotherwise may need to translate for each sub-system

XML can be used, but slow

Layered Architecture Model

Organize sub-systems in layers

Also “abstract machine model”Each layer ≈ an abstract machineContrast this with client-server model

hierarchy vs. network

Advantages:supports incremental developmentlocalize machine dependence in lower layers

Disadvantages:may have to “punch through” from top to bottomperformance may suffer

Organize sub-systems in layersAlso “abstract machine model”

Each layer ≈ an abstract machineContrast this with client-server model

Organize sub-systems in layersAlso “abstract machine model”Each layer ≈ an abstract machine

Contrast this with client-server modelhierarchy vs. network

Organize sub-systems in layersAlso “abstract machine model”Each layer ≈ an abstract machineContrast this with client-server model

Advantages:

supports incremental developmentlocalize machine dependence in lower layers

Advantages:supports incremental development

localize machine dependence in lower layers

Disadvantages:

may have to “punch through” from top to bottomperformance may suffer

Disadvantages:may have to “punch through” from top to bottom

performance may suffer

Figure: Version Control System

Reference architectures

Represents architecture for a particular domain

several systems will share the architectureCan be resued

Not for direct implementationcommunicate domain conceptsevaluate possible architectures

Represents architecture for a particular domainseveral systems will share the architecture

Can be resued

Represents architecture for a particular domainseveral systems will share the architectureCan be resued

Not for direct implementation

communicate domain conceptsevaluate possible architectures

Not for direct implementationcommunicate domain concepts

evaluate possible architectures

Example Reference Architecture

Figure: The OSI Reference Architecture for Computer Networks

Outline

1 Introduction

5 Interface Design

Introduction

Information processing is distributed over several computers

Advantages:Resource sharingOpennessConcurrencyScalabilityFault Tolerance

Disadvantages:ComplexitySecurityManageabilityUnpredictability

Introduction

Information processing is distributed over several computersAdvantages:

Resource sharingOpennessConcurrencyScalabilityFault Tolerance

Introduction

Resource sharing

OpennessConcurrencyScalabilityFault Tolerance

Introduction

Resource sharingOpenness

ConcurrencyScalabilityFault Tolerance

Introduction

Resource sharingOpennessConcurrency

ScalabilityFault Tolerance

Introduction

Resource sharingOpennessConcurrencyScalability

Fault Tolerance

Introduction

Disadvantages:

ComplexitySecurityManageabilityUnpredictability

Introduction

Disadvantages:Complexity

SecurityManageabilityUnpredictability

Introduction

Disadvantages:ComplexitySecurity

ManageabilityUnpredictability

Introduction

Disadvantages:ComplexitySecurityManageability

Unpredictability

Introduction

Multi-processor Architecture

Figure: A multiprocessor traffic control system

Client-Server Architecture (CSA)

Difference between server process and server computer

CSA Example

Figure: A client-server system

CSA Example

Figure: Computers in a client-server network

How to CSA-ize Your System

Distribute some/all of the MVC layers

Two-tier CSA

Simplest CSA: a server(s) and clients

Thin and flat client models

Two-tier CSA

Simplest CSA: a server(s) and clientsThin and flat client models

Three-tier CSA

Each MVC layer on a separate computer

Other Distributed Architectures

Peer-to-peer

centralizedsemi-centralized

Service-oriented Architecture (e.g., web services)web beyond browsersstandards (based on XML)

SOAPWSDLUDDI

Peer-to-peercentralized

semi-centralized

SOAPWSDLUDDI

Peer-to-peercentralizedsemi-centralized

SOAPWSDLUDDI

Service-oriented Architecture (e.g., web services)

web beyond browsersstandards (based on XML)

SOAPWSDLUDDI

Service-oriented Architecture (e.g., web services)web beyond browsers

standards (based on XML)SOAPWSDLUDDI

SOAPWSDLUDDI

Introduction Architectural Design Application Architectures Object-Oriented Design Interface DesignTypes of AAs

Outline

1 Introduction

5 Interface Design

Introduction

Look at system architecture from application’s perspective

previous perspective: control, distribution, structure

Issues to common to applications of a certain kind

Introduction

Look at system architecture from application’s perspectiveprevious perspective: control, distribution, structure

Introduction

Look at system architecture from application’s perspectiveprevious perspective: control, distribution, structure

Use of AA

As s/w developer, AAs are useful asstarting point for design process

design checklistorganize team-specific workassessing components for reuse

Use of AA

As s/w developer, AAs are useful asstarting point for design processdesign checklist

organize team-specific workassessing components for reuse

Use of AA

As s/w developer, AAs are useful asstarting point for design processdesign checklistorganize team-specific work

assessing components for reuse

Use of AA

As s/w developer, AAs are useful asstarting point for design processdesign checklistorganize team-specific workassessing components for reuse

Outline

1 Introduction

5 Interface Design

Data-Processing Systems

Batch-processing of data

input and output: sizable databases / data stores

Figure: Model of data-processing applications

Do not need to save state across transactions∴, function-oriented rather than OO

Batch-processing of datainput and output: sizable databases / data stores

Do not need to save state across transactions

∴, function-oriented rather than OO

Data-Flow Diagrams

DFDs are useful to describe data-processing applications

Figure: DFD for a payroll system

Transaction-Processing Systems

Process user requests for DB read / update

Could be event-driven (interactive) or procedural(non-interactive)E.g.: medical records software, ATM

Figure: Layered architecture of a transaction processing system

Process user requests for DB read / updateCould be event-driven (interactive) or procedural(non-interactive)

E.g.: medical records software, ATM

Process user requests for DB read / updateCould be event-driven (interactive) or procedural(non-interactive)E.g.: medical records software, ATM

Event Processing Systems

Respond to user or system events

e.g. of such events?

Figure: Architecture of Event-driven system

Respond to user or system eventse.g. of such events?

Introduction Architectural Design Application Architectures Object-Oriented Design Interface DesignObject-Oriented Design Process

Outline

1 Introduction

5 Interface Design

Introduction

Object-oriented system: interacting objects that maintain their ownstate and provide operations on those states

Object-oriented design: system designing with object classes andwith relationships between these classes

classes are related to problemstate representation is privatesystem is easy to modify→ objects (classes) since they areindependentobjects are reusable

Introduction

Object-oriented system: interacting objects that maintain their ownstate and provide operations on those statesObject-oriented design: system designing with object classes andwith relationships between these classes

classes are related to problem

state representation is privatesystem is easy to modify→ objects (classes) since they areindependentobjects are reusable

Introduction

classes are related to problemstate representation is private

system is easy to modify→ objects (classes) since they areindependentobjects are reusable

Introduction

classes are related to problemstate representation is privatesystem is easy to modify→ objects (classes) since they areindependentobjects are reusable

Objects and classes

Object: entity{state, operations}

state provides object informationoperations provide services to other objectsObjects created from a class: definition of template

Objects and classes

Object: entity{state, operations}state provides object information

operations provide services to other objectsObjects created from a class: definition of template

Objects and classes

Object: entity{state, operations}state provides object informationoperations provide services to other objects

Objects created from a class: definition of template

Objects and classes

Object: entity{state, operations}state provides object informationoperations provide services to other objectsObjects created from a class: definition of template

An Employee object class (UML)

Example Class Hierarchy (Generalization)

Association Model

Concurrent Objects

Objects execute concurrently

However, service requests are proceduralThreads allow for full concurrency even with service requests

Concurrent Objects

Objects execute concurrentlyHowever, service requests are procedural

Threads allow for full concurrency even with service requests

Concurrent Objects

Objects execute concurrentlyHowever, service requests are proceduralThreads allow for full concurrency even with service requests

Outline

1 Introduction

5 Interface Design

The Process

Steps in the process:Understand context and useDesign system architectureIdentify main objectsDesign system modelsSpecify object interfaces

Usually an iterative, interleaved process

The Process

Example: a weather mapping system

Basics

System descriptiongenerates weather maps from data collected from several sourcescollect and integrate data into an archiveuse archive and digitized map to display/print weather map

Use Case and Context

Context: how the system is connected in its environmentUse case: ways in which system can be used

Use-cases for weather station

Compltete System Architecture

Layered architecture: each step only depends on previous step

Compltete System Architecture

Layered architecture: each step only depends on previous step

Subsystems in the Architecture

System Architecture of Weather Station

Decomposing the system

Weather Station architecture:

Decomposing the systemWeather Station architecture:

Object Identification

Figure out what objects (classes) for each system/susbsystem

Use application domain knowledge for attributes and servicesFor the weather station subsystem:

Figure out what objects (classes) for each system/susbsystemUse application domain knowledge for attributes and services

For the weather station subsystem:

Figure out what objects (classes) for each system/susbsystemUse application domain knowledge for attributes and servicesFor the weather station subsystem:

Design Models

Graphical model of system to be implemented

Helps you to program your classes laterBridge between requirements and implementation

can create conflicts for level of detail

create several models with varying detailor choose certain level of detail in single model

Design Models

Graphical model of system to be implementedHelps you to program your classes laterBridge between requirements and implementation

Design Models

create several models with varying detail

or choose certain level of detail in single model

Design Models

Static and Dynamic models

Static Models

describe system structure with classes and relationshipsrelationships: generalization, used/used-by, composition

Dynamic Modelsshow interactions between system objects (not classes)service requests, state chages

Static Modelsdescribe system structure with classes and relationships

relationships: generalization, used/used-by, compositionDynamic Models

show interactions between system objects (not classes)service requests, state chages

Static Modelsdescribe system structure with classes and relationshipsrelationships: generalization, used/used-by, composition

Dynamic Models

show interactions between system objects (not classes)service requests, state chages

Dynamic Modelsshow interactions between system objects (not classes)

service requests, state chages

UML for Modeling

12 types of graphical models to document the static and dynamicsystem design

Subsystem models: show logical grouping of classes insub-systems

show as packagesstatic models

Sequence models: show sequence of object interactionsUML sequence or collaboration diagram.dynamic models

State machine models: show state changes for individual objectsevents and responsesstate chart diagramsdynamic models

Other model types in UML: use case, object models, generalization,etc.

UML for Modeling

12 types of graphical models to document the static and dynamicsystem designSubsystem models: show logical grouping of classes insub-systems

UML for Modeling

show as packages

static models

UML for Modeling

Sequence models: show sequence of object interactions

UML sequence or collaboration diagram.dynamic models

UML for Modeling

Sequence models: show sequence of object interactionsUML sequence or collaboration diagram.

dynamic models

UML for Modeling

State machine models: show state changes for individual objects

events and responsesstate chart diagramsdynamic models

UML for Modeling

State machine models: show state changes for individual objectsevents and responses

state chart diagramsdynamic models

UML for Modeling

State machine models: show state changes for individual objectsevents and responsesstate chart diagrams

dynamic models

UML for Modeling

Subsystem Models

Objects in weather station package:

Figure: Weather station packages

Subsystem Models

simple associations as well

sub-system model + class model = describe logical groupingusually relate to Java packages/libraries

Subsystem Models

simple associations as wellsub-system model + class model = describe logical grouping

usually relate to Java packages/libraries

Subsystem Models

simple associations as wellsub-system model + class model = describe logical groupingusually relate to Java packages/libraries

Sequence Diagrams

Document interactions

For each interaction: sequence of object interactions

Figure: Sequence of operations in data collection

Sequence Diagrams

Document interactionsFor each interaction: sequence of object interactions

Sequence Diagrams

Document interactionsFor each interaction: sequence of object interactions

Sequence Diagrams

Objects shown horizontally, time vertically

Labeled arrows show atomic interactions between objectsrepresent messagesnot data flows

thin rectangles: when the object is the controlling objectin a hierarchy, control is not relinquished until original object isreplied to

Sequence Diagrams also for single objects

Sequence Diagrams

Objects shown horizontally, time verticallyLabeled arrows show atomic interactions between objects

represent messagesnot data flows

Sequence Diagrams

thin rectangles: when the object is the controlling object

in a hierarchy, control is not relinquished until original object isreplied to

Sequence Diagrams

State Diagrams

For important objects: show their lifetimes and event responses

Figure: State diagram for weather station

States can be helpful when implementing the class

State Diagrams

Object-Interface Specification

Only the interface

not implementation or data itemsno internal details (private methos etc.)

helps concurrent developmentmore maintainable than full specification of classesTwo approaches:

each interface is a class in Javadeclare interfaces separately from classes

use interface and let classes implement an interface

Simply use Java (or another OO PL) to define interfaces

Only the interfacenot implementation or data items

no internal details (private methos etc.)

Only the interfacenot implementation or data itemsno internal details (private methos etc.)

helps concurrent development

more maintainable than full specification of classesTwo approaches:

helps concurrent developmentmore maintainable than full specification of classes

Two approaches:each interface is a class in Javadeclare interfaces separately from classes

each interface is a class in Java

declare interfaces separately from classesuse interface and let classes implement an interface

Design Evolution

OO approach allows for easy changes to design

state representation does not affect interfaceobjects are loosely coupled⇒ easy to introduce new ones

E.g.: add pollution-monitoring to weather stationintroduce Air quality class at Weather Data leveladd reportAirQuality() operation to WeatherStationadd classes for pollution monitoring

Design Evolution

OO approach allows for easy changes to designstate representation does not affect interface

objects are loosely coupled⇒ easy to introduce new ones

Design Evolution

OO approach allows for easy changes to designstate representation does not affect interfaceobjects are loosely coupled⇒ easy to introduce new ones

Design Evolution

E.g.: add pollution-monitoring to weather station

introduce Air quality class at Weather Data leveladd reportAirQuality() operation to WeatherStationadd classes for pollution monitoring

Design Evolution

E.g.: add pollution-monitoring to weather stationintroduce Air quality class at Weather Data level

add reportAirQuality() operation to WeatherStationadd classes for pollution monitoring

Design Evolution

E.g.: add pollution-monitoring to weather stationintroduce Air quality class at Weather Data leveladd reportAirQuality() operation to WeatherStation

add classes for pollution monitoring

Design Evolution

Outline

1 Introduction

5 Interface Design

Introduction

“Design interface with user’s experience and interaction inmind”

Field of Human Computer InteractionExamples:

Command line interfaceXHTML/CSSSwingsometimes combined with hardware design

Software developer == Interface designer

Introduction

“Design interface with user’s experience and interaction inmind”Field of Human Computer Interaction

Examples:Command line interfaceXHTML/CSSSwingsometimes combined with hardware design

Introduction

“Design interface with user’s experience and interaction inmind”Field of Human Computer InteractionExamples:

Introduction

Good user experience is crucial to product success

User errors are often a result of bad interface design

Introduction

Good user experience is crucial to product successUser errors are often a result of bad interface design

Introduction

Good user experience is crucial to product successUser errors are often a result of bad interface design

Introduction

Bad interface leads tofrustration

inaccessible / difficult to use featuresmistakes

Some (random) guides:make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)balance meaning with action (icons in any app, Reason, !Office2010)understand and aid human memory (!16tone, !SonicMood)don’t terrorize user with errors (http://adobegripes.tumblr.com)work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Bad interface leads tofrustrationinaccessible / difficult to use features

mistakes

Introduction

Bad interface leads tofrustrationinaccessible / difficult to use featuresmistakes

Introduction

Some (random) guides:

make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)balance meaning with action (icons in any app, Reason, !Office2010)understand and aid human memory (!16tone, !SonicMood)don’t terrorize user with errors (http://adobegripes.tumblr.com)work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Some (random) guides:make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)

balance meaning with action (icons in any app, Reason, !Office2010)understand and aid human memory (!16tone, !SonicMood)don’t terrorize user with errors (http://adobegripes.tumblr.com)work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Some (random) guides:make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)balance meaning with action (icons in any app, Reason, !Office2010)

understand and aid human memory (!16tone, !SonicMood)don’t terrorize user with errors (http://adobegripes.tumblr.com)work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Some (random) guides:make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)balance meaning with action (icons in any app, Reason, !Office2010)understand and aid human memory (!16tone, !SonicMood)

don’t terrorize user with errors (http://adobegripes.tumblr.com)work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Some (random) guides:make user interaction simple and efficient (Quicksilver, TaDa List,Ubiquity, !gpsGuide, !Password-engine)balance meaning with action (icons in any app, Reason, !Office2010)understand and aid human memory (!16tone, !SonicMood)don’t terrorize user with errors (http://adobegripes.tumblr.com)

work with user’s capabilities (accessibility, Frenzic, Mac toolbar,!Any (old) Linux GUI interface)

Introduction

Formal principles

User familiarity

ConsistencyMinimal surpriseRecoverabilityUser guidanceUser diversity

Formal principles

User familiarityConsistency

Minimal surpriseRecoverabilityUser guidanceUser diversity

Formal principles

User familiarityConsistencyMinimal surprise

RecoverabilityUser guidanceUser diversity

Formal principles

User familiarityConsistencyMinimal surpriseRecoverability

User guidanceUser diversity

Formal principles

User familiarityConsistencyMinimal surpriseRecoverabilityUser guidance

User diversity

Formal principles

User familiarityConsistencyMinimal surpriseRecoverabilityUser guidanceUser diversity

Issues of Interface Design

Answer two questions:How should user interact with system?How should information be presented to user?

User Interaction

Advanced from interfaces designed for experts

Current interaction styles:direct manipulationmenu selectionform fill-incommand languagenatural language

User Interaction

Advanced from interfaces designed for expertsCurrent interaction styles:

direct manipulationmenu selectionform fill-incommand languagenatural language

User Interaction

direct manipulation

menu selectionform fill-incommand languagenatural language

User Interaction

direct manipulationmenu selection

form fill-incommand languagenatural language

User Interaction

direct manipulationmenu selectionform fill-in

command languagenatural language

User Interaction

direct manipulationmenu selectionform fill-incommand language

natural language

User Interaction

Comaprisons of Interface Styles

Figure: Interaction Styles Merits/Demerits

Interaction Issues

single application may have mixed styles

e.g., Linux: direct manipulation, menu selection, commandlanguage

Web interfacesmostly forms baseddirect manipulation ?command language ?

Interaction Issues

single application may have mixed stylese.g., Linux: direct manipulation, menu selection, commandlanguage

Interaction Issues

Web interfaces

mostly forms baseddirect manipulation ?command language ?

Interaction Issues

Web interfacesmostly forms based

direct manipulation ?command language ?

Interaction Issues

Web interfacesmostly forms baseddirect manipulation ?

command language ?

Interaction Issues

Information Presentation

Use the MVC approach for focusing on UI

Kinds of presentation elements depend on many factors:precise vs relationships (tables/text/graphs, sparklines)speed of change in values (tables/graphs, animation)

Visualizations for large, changing, interactive datamolecule models, network graphs

Color usage:few (4-5)system change == color changedisplay anomalies, similaritiesconsistencyeye strain (red-on-blue)

Use the MVC approach for focusing on UIKinds of presentation elements depend on many factors:

precise vs relationships (tables/text/graphs, sparklines)speed of change in values (tables/graphs, animation)

precise vs relationships (tables/text/graphs, sparklines)

speed of change in values (tables/graphs, animation)

Visualizations for large, changing, interactive data

molecule models, network graphs

Color usage:

few (4-5)system change == color changedisplay anomalies, similaritiesconsistencyeye strain (red-on-blue)

Color usage:few (4-5)

system change == color changedisplay anomalies, similaritiesconsistencyeye strain (red-on-blue)

Color usage:few (4-5)system change == color change

display anomalies, similaritiesconsistencyeye strain (red-on-blue)

Color usage:few (4-5)system change == color changedisplay anomalies, similarities

consistencyeye strain (red-on-blue)

Color usage:few (4-5)system change == color changedisplay anomalies, similaritiesconsistency

eye strain (red-on-blue)

UI Design Process

3-step process

User analysis, System prototyping, Interface evaluation

UI Design Process

3-step process

UI Design Process

3-step process

Chapter 4 Design -...

Documents

Transcript of Chapter 4 Design -...

Early Social and Emotional Communication of ASD Infants ...local.psy.miami.edu/faculty/dmessinger/c_c/rsrcs... · social or communicative functioning as indicated by family history

AN849 Basic PICmicro Oscillator Designapplication-notes.digchip.com/022/22-19194.pdf · nant oscillator circuit, as used with the Microchip PIC-micro family of devices. The output

A state feedback input constrained control design for a 4 ......Problem statementLPV Control in the presence of input saturationController designApplication of LPV approach to the

users.manchester.eduusers.manchester.edu/Student/Kstaton/ProfWeb/statonkl… · Web viewto the tune of "You Are My Sunshine") ... “I wonder what this community helper does to

users.manchester.eduusers.manchester.edu/Facstaff/JPOsborne/BCA_Science_Majors.pdf · 'Microbe-Human Interactions Biogeography Equine Biology .Animal Behavior Ecology and Environmental

Adoptive Gay Father Families: Parent Child Relationships ...local.psy.miami.edu/faculty/dmessinger/c_c/rsrcs/... · father families possess the additional nontraditional feature of

users.manchester.eduusers.manchester.edu/Student/Kstaton/ProfWeb/statonkl… · Web viewDuring the first phase, the researcher obtained an Education Evaluation, Case Conference

4-Braudel, Eating and Drinking - users.manchester.eduusers.manchester.edu/FacStaff/SSNaragon/Kant/LP/Readings/04-Braudel... · Braudel, “Eating and Drinking” 1 of 11 EATING AND

users.manchester.eduusers.manchester.edu/student/DNave/Profweb/ESS 301... · Web viewK-6 P.E. Standards 3-18. ... stunts and tumbling routine). ... and each time the teacher says

introduction to infant developmentlocal.psy.miami.edu/.../c_c/rsrcs/rdgs/intervention/gaines.intervention.chapter.pdfintroduction to infant development Edited by Alan Slater University

Fear conditioning and extinction across development ...local.psy.miami.edu/faculty/dmessinger/c_c/rsrcs/rdgs/...conditioning and extinction across development: Evidence from human

users.manchester.eduusers.manchester.edu/Student/arbigjohny/ProfWeb/BigJo… · Web viewThe Simpsons. Spiderman. The Wizard of Oz. Historical Figures. Anastasia. Richard Byrd. Cleopatra.

Student Academic Proﬁle - users.manchester.eduusers.manchester.edu/Facstaff/SSNaragon/Online/100-FYS-F17/Misc/... · Student Academic Profile My Week OCTOBER 2016 ... PHIL-2ts B

users.manchester.eduusers.manchester.edu/student/nashort/Profweb/Civil W… · Web viewusers.manchester.edu

users.manchester.eduusers.manchester.edu/Student/drwhitaker/Profweb/Interdi… · Web viewPages 38-41 are subject areas and lesson plan activities for each. ... After children develop

users.manchester.eduusers.manchester.edu/Student/kmconrad/ProfWeb/unit … · Web viewCauses of Development: War . Lesson Plan #1. by . Karla Conrad. Lesson: Mean Median and Mode

Video and Image Processing Example Designapplication-notes.digchip.com/038/38-21081.pdf · Video Output to an External Video Interface. The connection to the external video interface

users.manchester.eduusers.manchester.edu/student/bajones/ProfWeb... · Web viewLaminate all cards and the instruction sheet ... When the music stops, they go to the wall that ...

users.manchester.eduusers.manchester.edu/.../ClarkSM327FinalUnitPlan.docx · Web view1.6.4 Identify and demonstrate appropriate listening behavior ... I have a special surprise

users.manchester.eduusers.manchester.edu/student/dsneill/ProfWeb/NeillDS32… · Web viewDanielle Neill . EDUC 327 ... the use of Indiana steel mills to ... This book provides a