BUS 270

1
BUS 270

• System Development Process

2
SYSTEMS

• THE WORD SYSTEM DOES NOT NECESSARILY MEAN
  COMPUTERS
• SYSTEM EXAMPLES
• WATER SYSTEM
• ELECTRONIC SYSTEM
• PHONE SYSTEM

3
SYSTEM DEFINED

• A SYSTEM IS ANY COLLECTION OF UNITS THAT PERFORMS
  AN ESTABLISHED FUNCTION
• THEY HAVE BEEN AROUND FOR A LONG TIME
• AS HAS THE SYSTEM APPROACH

A REGULARLY INTERACTING GROUP OF PARTS WHICH FORM
A UNIFIED WHOLE
4
SYSTEM APPROACH

• BOOK
• RECOGNIZE AND DEFINE PROBLEM
• DEVELOP AND EVALUATE ALTERNATIVES
• SELECT SOLUTION
• DESIGN
• IMPLEMENT

5
Once establish what doing then

• 9 step process
• Understand Problem
• Define structure
• Code
• Key
• Compile
• Debug
• Execute
• Test
• Document

6
Isolation

• These processes however have a fault
• They do not look at the big picture when
  designing an individual component
• This produces systems that cannot share with one
  another
• And prevents becoming a communicated enterprise.

7
Federation

• An enterprise system is comprised of a collection
  of many sub systems
• For a large business they may reside on differing
  platforms.
• For a small business they could reside on one

8
System break out example

• On my PC I have the following
• Design systems (Smartdraw)
• Money systems (Turbo Tax, MS Money)
• Communication systems (Outlook, QVT)
• Office systems (MS office)
• Sound systems (Real player)
• Etc.

9
Need

• What is lacking in the design approach is
• A guiding architecture or blueprint
• Which will allow sub systems to be designed
  knowing how they are to be interconnected.

10
Macro to Micro
It starts Tops Down
11
From wants
With the identification of what you want on the
desk of the user - what sort of computing
capability do you want
12
And then
It goes to the specifics of Where you will
provide that capability
13
The steps or components

• What you will compute Architecture
• Where you will compute Engineering
• How you will compute Technical skills like
  using office 2000

14
How to design a sub systemMicro to Macro

• With an architecture in place you can now design
  a sub system that fits
• First determine what family the new system
  belongs in
• EUC
• KS
• Processing
• eCom
• Etc.

15
By looking at the diagram
Developing KS What elements do you need
User interface
Connection and data feeds from other systems
KS software
16
Micro to Macro

• Next what system package do you need
• Software Pre made or special design or
  combination
• Hardware PCs, Mid-rang, host
• And what connectivity
• GAN
• WAN
• LAN

17
Mindful of what computing power you want to
deliver
18
What you Really want

• Its not the individual design of each system that
  gives you power A payroll system for example
• But rather the enabling for people to
• Discover
• Communicate
• And Create
• Brand new products, services and methods
• This will give you a strategic advantage (Bank
  study example again)

19
Its this
20
Not these

• UNDERSTAND PROBLEM
• DEFINE STRUCTURE
• CODE
• KEY
• DEBUG
• COMPILE
• EXECUTE
• TEST
• DOCUMENT

• RECOGNIZE AND DEFINE PROBLEM
• DEVELOP AND EVALUATE ALTERNATIVES
• SELECT SOLUTION
• DESIGN
• IMPLEMENT

21
Although you still need to useDevelopment
process Modified for Enterprise Architecture

• Process outline
• RECOGNIZE AND DEFINE PROBLEM
• DEVELOP AND EVALUATE ALTERNATIVES
• SELECT SOLUTION
• DESIGN
• IMPLEMENT

• With Architectural template
• STILL DO
• HAVE STANDARD
• HAVE STANDARD
• HAVE STANDARD
• STILL SAME

22
What you really want

• Is to re-do your strategy
• So instead of something like
• 1billion Customers by 2012
• We want
• Be the best possible bank
• And Our business and IT strategies should reflect
  How we do that

Get this
Do This
23
By empowering
24
Combining IS models
25
Determining an Architecture
26
And a Specific Design
27
The Empowered Enterprise

• Develop a Concept
• What to deliver EII
• Where to deliver Models
• Then How to deliver
• Architecture
• And Design

28
BUS 270

• System Development Process

29
The system development Life cycle

• SYSTEM APPROACH
• RECOGNIZE AND DEFINE PROBLEM
• DEVELOP AND EVALUATE ALTERNATIVES
• SELECT SOLUTION
• DESIGN
• IMPLEMENT

• DEVELOPMENT LIFE CYCLE
• INVESTIGATE
• ANALYSIS
• DESIGN
• IMPLEMENT
• MAINTAIN

30
Step 1

• Receive Request
• What do you want
• Why do you want it

31
Step 2

• Investigate Can we do this - the feasibility
  study
• Organizational Meets organizations objective
• Economic Cost/Benefit
• Technical Is it possible?
• Operational Will it be used?

32
Issues

• Cost/Benefit Issues
• Tangible versus intangible
• Tracking real saves
• Hawthorne Effect

33
Step 3 Analysis

• In depth study of user needs to develop
  functional requirements
• The delivery goals of the new system
• Look at
• Current processes
• Current systems
• User involved!!!!!!!!!!!!!

34
Design

• Prototyping
• Good for interfaces
• User involved
• Structured design
• Back office
• DP

35
Note

• Prototyping is referred to as RAD
• RAD, more correctly is the use of development
  tools, visual languages and CASE techniques

36
Design

• Interface
• Data
• Process
• And yes user you care!!

37
Implementation

• Parallel
• Pilot
• Phased
• Plunge

38
Maintenance

• Must keep functioning
• And modify to reflect current situation
• Example Payroll tax deductions - Tax Cut

39
End User development

• Specialized/Customized
• Follow same rules
• IT sets environment, user develops custom
  application
• It also takes care of production systems
• Like payment processing

40
Change control

• Don't want to put system down when you install
• Test
• Develop case
• User checks output
• And review
• Then sign off

41
Dont forget

• User documentation
• Developer documentation
• Training

42
Evaluate

• Did it do what you want
• CaptKrash method score and rank
• Can also do to evaluate vendor software
• Finally may want to look at make versus buy