the it story begins with…

57
The IT Story Begins With… Jacquard Loom - 1801

Upload: zariel

Post on 19-Jan-2016

35 views

Category:

Documents


0 download

DESCRIPTION

The IT Story Begins With…. Jacquard Loom - 1801. And Continues with…. Difference Engine: 1822-65 (Babbage and Lovelace). And then …. ITR (1889-1914) + CTR (1911-1914) => IBM. +. SDLC. The Systems Development Life Cycle. The Traditional Approach. Ready Fire Aim. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: The IT Story Begins With…

The IT Story Begins With…

Jacquard Loom - 1801

Page 2: The IT Story Begins With…

And Continues with…

Difference Engine: 1822-65 (Babbage and Lovelace)

Page 3: The IT Story Begins With…

And then …

ITR (1889-1914) + CTR (1911-1914) => IBM

+

Page 4: The IT Story Begins With…

Analysis

Operational Support

Planning

Design

Implementation

SDLC

The Systems Development Life Cycle

Page 6: The IT Story Begins With…

There are different approaches to Software Development

• Reverse Engineering

• The Traditional Waterfall Model

• Exploratory Programming

• Boehm’s Spiral Model

• Agile/Extreme Programming

• Pattern Languages

Page 7: The IT Story Begins With…

Reverse EngineeringReverse Engineering

1. Specifications

2. Design

3. Construction

4. Test and Use

1. Test and Use

2. Deconstruction

3. Document Design

4. Formulate Specifications

EngineeringEngineering

Page 8: The IT Story Begins With…

Traditional Waterfall (Our Text)

Analysis

Operational Support

Planning

Design

Implementation

Page 9: The IT Story Begins With…

Planning

If you can keep your head about you

When all around you others are losing theirs

…..then maybe you just don’t understand the problem!

Page 10: The IT Story Begins With…

Planning Activities

• System Request

• Preliminary Investigation– Interviews on needs and practices– Surveys– Collecting forms

• Analysis of the Business Case

• Feasibility Study

Page 11: The IT Story Begins With…

Analysis Activities

• Identify the stakeholders

• Research existing practices

• Research real (vs requested) needs

• Requirements Modelling

• Prepare Design specification

Page 12: The IT Story Begins With…

Design

• Document or Die!

• Use of specific techniques important– Data Flow Diagrams– UML Diagrams/Use-Case– Database Normalization

• Prototype – a quick and dirty demo – not production quality

Page 13: The IT Story Begins With…

Implementation

• Code (according to specifications)

• Test!

• Revise specifications as needed (go back to previous SDLC stages if necessary)

• Installation

Page 14: The IT Story Begins With…

Operational Support

• Training

• Implement security (why wait?)

• Modifications

Page 15: The IT Story Begins With…

Maintenance

Development

Software Development

$90%

$10%

Page 16: The IT Story Begins With…

• Hacking

• Cost effective only forsmall projects

• Useful for solving novel problems

• Risky (high failure rate)

• Fun, but hard to sell to management

Exploratory Programming

Page 17: The IT Story Begins With…

Object Oriented Design

• Model using “real world” Objects

• Analyze with Use/Case Examples

• Model Systems Behaviour with UML

Page 18: The IT Story Begins With…

Spiral Model (Barry Boehm)

Page 19: The IT Story Begins With…

Agile (Extreme) Programming

• Small teams• Developers work very closely with clients• Rapid turnaround of project features• Paretto’s Law: 80% of the job takes 20% of the

effort – to complete the job will take the remaining 80% therefore: most clients will be happy to pay for 80% functionality and balk at the extra cost of the remaining 20% - so don’t do it.

Page 20: The IT Story Begins With…

Pattern Languages

• Applications are likebuildings

• Most projects can bebased on knownarchitectural patterns

• Learning the patterns thatwork helps ensure futuresuccess

Page 21: The IT Story Begins With…

Which Methodology Works?

• Different Techniques fit different situations• The corporate culture is a major factor in

choosing an approach• The method of development is itself a

pattern – learn to follow success.• Don’t be too rigid – you can always fake it!

- A Rational Design Process (and how to fake it),by Prof. David L. Parnas & Paul Clemens, 1985

Page 22: The IT Story Begins With…

Types of Software Systems

• Transaction Processing (TP)• Management Information Systems (MIS)• Knowledge Management Systems• User Productivity Software • Real Time Systems (RTS)• Enterprise Computing• Systems Software and Utilities

• Information Systems Integration

Page 23: The IT Story Begins With…

Transaction Processing

• A. – Atomicity (All or nothing)

• C. – Consistancy (the books balance)

• I. - Isolation (don’t affect each other)

• D. – Durability (permanent record)

Performance Measurement: TPS (Transactions per second)

Page 24: The IT Story Begins With…

MIS

• Text also uses the term “Business Support Systems” – MIS is more common

• MIS does not need to be real time

• Decision Support

• Data Mining/Data Warehouses

TP collects/generates data – MIS summarizes and reports

Page 25: The IT Story Begins With…

Knowledge Management

• Expert Systems– Interview the experts and uncover the rules they use

– usually 20-80 – relatively small #– Applicable to small problem domains, not large– Use of Knowledge Engines, languages such as

Prolog) – Rules + facts => Diagnosis• Fuzzy Logic (ie: Omron, rice cooker example,

OCR)• Content Management

– Silos of information (Ann Rockly)– Ontologies for organizing my meaning

• Search: Altavista; Google; Lucene; HTDig

Page 26: The IT Story Begins With…

User Productivity Software

• Office Suites/Personal Software

• Groupware

Page 27: The IT Story Begins With…

Enterprise Software

• Enterprise Resource Planning (ERP)– SAP– Oracle Financials, PeopleSoft– Walmart’s Inventory System– American Airline: SABRE

• Bet the company type software (Federal Express)

• Integrates essential company functions

Page 28: The IT Story Begins With…

Real Time Systems

• Used in process control, embedded devices

• Specialized operating systems (QNX, Symbian, HP/RTE) or no OS at all

• Issue is guaranteed response time – can’t wait for paging, garbage collection

• Make sure the system is not overloaded (in order to guarantee response time)

• Examples?

Page 29: The IT Story Begins With…

Systems Software & Utilities

• Operating Systems• Device Drivers• Backup Software (ie: Time Machine)• Virus Protection• Programmer’s Tools

– Compilers and Interpreters– IDE’s– Computer Aided Software Engineering (CASE)– Debuggers

• Performance Monitors • Database Engines

Page 30: The IT Story Begins With…

Embedded Devices

Page 31: The IT Story Begins With…

Mashups

Page 32: The IT Story Begins With…
Page 33: The IT Story Begins With…

SystemsSoftware& Utilities

EnterpriseComputing

MISRealTime

KnowledgeManagement

UserProductivity

TransactionProcessing

Software Integration

Page 34: The IT Story Begins With…

Games (How to classify?)

Page 35: The IT Story Begins With…

What is the Market Place?

Page 36: The IT Story Begins With…

Rule of 4 – How IT Companies Make Money

1. Product Sales

2. Maintenance and Support

3. Projects and Consulting

4. Training

Page 37: The IT Story Begins With…

Business to Business (B2B)

• Electronic Data Interchange using XML and agreed upon standard protocols– Banking– Ordering inventory

Page 38: The IT Story Begins With…

Business to Consumer

• Web Based Software– Advertising– Product Information– Home Banking

• Games• Personal Productivity

Tools

Page 39: The IT Story Begins With…

Identifying Stakeholders And Their Needs

• Top Managers

• Middle Managers & Knowledge Workers

• Supervisors and Team Leaders

• Operational Employees

Page 40: The IT Story Begins With…

Information Needs

CEO

Top Managers

Middle Management

Supervisors &Team Leaders

Operational Employees

short term goalsDetailed Info

Long term goalsSummarized Info

Page 41: The IT Story Begins With…

Lets not forget…

• Customers

• Vendors

• Stockholders

• Competitors (Industry Standards that have to be met – companies often need to co-operate with the competition)

Page 42: The IT Story Begins With…

Chapter 2 –Systems Planning

Page 43: The IT Story Begins With…

Strategic Planning

• Mission Statement– Short –briefly describes the core purpose of the

company or project or team– Sets a direction – a “moral compass”

• Principles/Core Values

• Business Plan– Long Term Goals– Mid Term Goals– Short Term Goals

Page 44: The IT Story Begins With…

Strategic Planning Question

In pursuing this project are we supporting our mission statement, principles and goals

If not – why are we doing it?

Should we drop the project?

Should we change how we define ourselves?

Page 45: The IT Story Begins With…

Mission Statements

What is the Mission Statement of

• Toronto’s Police Force

• The Canadian Cancer Society?

• Humber College

Page 46: The IT Story Begins With…

What is your Mission Statement?

Page 47: The IT Story Begins With…

SWOT Analysis

Page 48: The IT Story Begins With…

Feasibility Study

• Economic

• Technical

• Operational

• Scheduling

Page 49: The IT Story Begins With…

Making a Business Case

• Why are we doing this project?

• What is the project about?

• How does this solution address key business issues?

• How much? (ROI) How long? (Payback)

• Will it cause a hit in productivity?

• Risks of going ahead? Of NOT doing it?

Page 50: The IT Story Begins With…

Making a Business Case (2)

• If we don’t know where our goals are – how do we know we’ve arrived. How do we measure success?

Page 51: The IT Story Begins With…

Making the Business Case

What other choices are there? (Missed opportunities?)

Page 52: The IT Story Begins With…

Reasons for System Projects

• Improved Service

• Support for new products and services

• Better performance

• More information

• Stronger Controls (Security)

Improving any of the “Qualities of a Good System”

Page 53: The IT Story Begins With…

Discussion

Collecting the current position of every vehicle in the TTC.

Page 54: The IT Story Begins With…

Internal Factors Affecting Systems Projects

• Strategic Plan

• Management Directives

• User Requests

• The IT department

• The weight of Existing Systems

Page 55: The IT Story Begins With…

External Factors Affecting Systems Projects

• Technology (ie: Office 2007, Vista, Multitouch, Wireless, RFID, the Internet, Web 2.0)

• Suppliers - Radio Freq. ID chips (RFID) – EPOD (Electronic Proof of Delivery, Just In Time Management (JIT)

• Customers: CRM Software (Customer/Supplier Relationship Management)

Page 56: The IT Story Begins With…

More External Factors

• Competitors

• The Economy

• Government

Page 57: The IT Story Begins With…

Cost/Benefit Analysis

• Tangible/Intangible

• Direct/Indirect

• Recurring/Non-Recurring

• Capital

• Overhead

• Supplies

• Personnel