md703: computer information systems n goals n logistics n teams and projects n class organization n...

MD703: Computer Information Systems Goals Logistics Teams and Projects Class Organization Technical Topic: Application

Development Case Analysis Strategy

Goals

1)“Management understanding” of key technical principles, ideas and products (via “tech talks”)

2)Management of IT resources and staff (via text chapters)

3)Experiences in implementing IT projects (via text cases)

4)Presentation Experience

Classes are divided between the 1st three topics

Logistics

Schedule “Assessment” Web Page Text Office Hours Project Teams Case Discussions

Project Topics

RFID Web Services/SOA Sarbanes-Oxley Blade Servers, Virtual Computing SPAM Issue & Management WiFi/Mobile computing/IM Teleconferencing IPv6 VoIP XML

Application Development Principles System Development Life Cycle

– Steps– Methods

Application Hosting Environment– Functional Tiers– Infrastructure Levels

Phases of technology Assimilation

Application Development Life Cycle

Analysis

Design

Build/Buy Monitor

Implement

Methods for Applying SDLC

Classic Model– Static environment– Minimal unknowns

Rapid Application Design– Delivery in stages– Fast to Production

Prototyping– Focus on presentation, not process– Customer-based apps

Analysis Basics

Focus on business need, not technology Entity-relationship Diagrams for data Dataflow diagrams for logic Define Scope Define Success

Design Basics

Focus on the solution, “blueprint” Considers environmental factors

– Enterprise standards– Staff talents, availability

Data-centric: Normalization Process-centric: Flowchart / Pseudo-code Combining the two: Objects

Build / Buy Issues

Current move to “buy and integrate” Build only where control, differentiation are

key All applications must coordinate upwards and

to peer applications Trade off of ability to maintain versus control

over maintenance Exception handling is 80% of work “Workflow” is often the major issue

Implementation Issues

Process Changes Training, reward mechanism Business process change must accompany

technology change Data lifespan includes creation,

operational use, analytical use, archiving

Monitor / Measurement

Baseline Statistics Aggregate “good news”, detail “bad

news” Compare to Analysis goals Basis for upgrade, acceptance

Tiers

Presentation Logic Storage

Network

Client Server

“4-Tier” Model

Web ServerClient

(Browser)

ApplicationServer

DBMS Storage

“Jolt”

Application Development EnvironmentNetwork

Servers

Operating System/Subsystems

Common System Utilities

Common Business Code

Application Specific Code

Phases of Technology Assimilation Identify

– What technical abilities are required? Learn

– How do they work? Control

– How will we use them? Distribute

– Commit to the new technology!

Chapter 1 Review

Management evolution to “governance”

Organizational Use of IS

Evolution of the service provided

Evolution of the IT mechanics

Case Analysis Strategy

Scope– Data vs Process

Strategy vs Tactics– What has to be done vs how

Efficiency vs Flexibility– Parallels investment strategies

Excellence vs Satisficing– Elasticity of return

Adherence to phases of “technology assimilation”– Is IT incorporated into business practices

Scope Discussion

What are the weaknesses of providing technical solutions:– Overly centralized– Overly distributed

– Provide an example to match each observation.