Building IT Systems

SUKAMTO

Building IT System

03/18/15
1

Introduction
When an organization develops a new IT system,
it goes through much the same process as building a home; this process called the system
development life cycle (SDLC).
After determining that a problem or opportunity
exists and gathering the necessary requirements
or characteristic of the new system, an organization may choose to lets its own IT specialist
design and build the new system or hire another
organization or independent consultant to do it.
Building IT System

03/18/15
2

Building IT Systems
The System Development Life Cycle (SDLC)
The process an organization goes through to
develop an IT system.
* Why your organization want your involvement
* Why organization undertake the SDLC

In-House SDLC
When organizations use
their own IT specialist to
develop an IT system.

Outsourcing
When organizations hire
someone else to develop
an IT system.
Building IT System

Helpful SDLC Tools

* Prototyping
* Data Flow Diagramming
* Computer-Assisted
Software Engineering
(CASE) tools.
03/18/15
3

Why Organization Want Your

Involvement
The success of the system development
process which will have an impact on the
success of the organization, depends on
the active participation of many people.
People who participate during the system
development process include IT
specialist, users, and customers.
Building IT System

03/18/15
4

Why Organization Want Your

Involvement
As an employee of an organization, you will
potentially wear many hats (perform different tasks) during the system development
process. This may include being:
A business process expert.
A manager of the people
A liaison to the customer
A quality control analyst
Building IT System

03/18/15
5

Why Organization Undertake

the SDLC
Organization today develop systems to
take advantage of IT.
These advantages include performing
task more efficiently and effectively and
providing new products or services
(innovation)

Building IT System

03/18/15
6

The need of System

Development Life Cycle
To convert manual system to an automated
system
Totally overhaul an existing system
Make changes to an existing system
Make minor revision to an existing system
Invent a new system
Building IT System

03/18/15
7

The In-House System

Development Life Cycle
The in-house SDLC is a set of six stages
that an organization goes through to
develop an IT system.
During theses six stages, the
organization relies on its own IT staff to
carry out the necessary tasks.

Building IT System

03/18/15
8

The Six Stages of The InHouse SDLC

Define the problem/opportunity
Gather requirements for new system
Design the new system
Develop the new system
Implement the new system
Maintain the new system
Building IT System

03/18/15
9

SDLC

The In-House
SDLC

Stage 1:
Define the problem/opportunity

No

Continue

Stop

Yes
Stage 2:
Gather requirements for the new system

No

Continue

Stop

Yes
Stage 3:
Design the new system

No

Continue

Stop

Yes
Stage 4:
Develop the new system
Stage 5:
Implement the new system

Building IT System

Stage 6:
Maintain the new system

03/18/15
10

Stage 1:
Define the
Problem/
Opportunity

Function
* Recognize that a problem
or opportunity exists
* Gather the project
development team
* Assess the initial feasibility
* Develop a plan for
proceeding

End Documents
* Problem/opportunity definition
* Initial feasibility review and recomendation
* Project Plan

Building IT System

03/18/15
11

Stage 2: Gather
Requirements for
the New System

Functions
* Focus on logical requirements
* Determine how processes work
* Determine changes that need to
be made
* Determine how processes should
work

End Documents

Building IT System

* Description of the current system

* Description of the changes
* Description of the propoised system
* Description of the input, processing, and
output requirements.

03/18/15
12

Function

Stage 3:
Design the
New System

* Konvert logical system requirements

into a technical system design
* Generate alternative system design
* Evaluate alternative system design
* Choose system design

End Documents
* Technical system design
* Screen and report formats
* File and database layout
* Processing requirements (software)
* Hardware requirements
* List of people to develop the system

Building IT System

03/18/15
13

Function

Stage 4:
Develop the
New System

* Konvert the technical system design

into an IT system
* Programming and testing
* Implement file and database layout
* Build reports and screens

End Documents
* Software
* Software documentation
* File and database documentation
* Detailed description of the hardware
Building IT System

03/18/15
14

Stage 5: Implementing the

New System
The implementing stage involves actually
installing the hardware and software,
training users, and using the new system.
The most important things is converting
from the old to the new way.
Converting from the old to the new way
can be achieved in many ways: parallel,
plunge, piecemeal, and pilot.
Building IT System

03/18/15
15

Parallel Conversion
Using both the old and new system until
the project development team determines
that the new system works correctly.
Probably the most expensive (it may
require some people to perform the same
task two different way), but its also the
safest.
Building IT System

03/18/15
16

Plunge Conversion
Totally discarding the old system and
immediately begin using the new system
Although this method is fast and
inexpensive, its the riskiest if the new
system doesnt work.

Building IT System

03/18/15
17

Piecemeal Conversion
Piecemeal conversion occurs when one
portion of the new system is implemented
and verified before other portion are
implemented.
For example, if an organization were
implementing a new accounting system, it
may choose to implement the payroll
portion before implementing the inventory,
accounts receivable, and accounts payable
portion.
Building IT System

03/18/15
18

Piloting
Only one portion of the users start using
the new system until it is verified.
After that, the remaining users convert to
the new system.

Building IT System

03/18/15
19

Stage 6: Maintain the New

System
During this stage, member of the project
team monitor the system to make sure it
continues to work correctly and makes
changes as the need arises.

Building IT System

03/18/15
20

Outsourcing The Request for

Proposal Process
Outsourcing occurs when an organization
decides to let someone else take over and
develop, operate, and/or maintain part or its
operation.
For SDLC or IT system, many organization
hire consultants to assist during requirements
gathering and design, contract programmer for
the development (programming and testing) of
software, to implement a new system, train
user, and maintain the hardware and software.
Building IT System

03/18/15
21

The Considerations
Besides being a cost-effective
mechanism, the real logic behind
outsourcing is to focus management
effort and resources on the firms priority
areas of business.

Building IT System

03/18/15
22

A Request For Proposal (RFP)

RFP is a document that outlines the necessary
requirements for a new system and solicits bids from
other organization or individuals (generally referred to
as vendor)
A good RFP provides a description of the organization
and future changes in the organization (for example,
the number of students in the year 2003)
The RFP defines the problem/opportunity and provide
a complete description of how the current system
works and the logical requirements for the new
system.
Building IT System

03/18/15
23

RFP
Process

The New SDLC

Stage 1:
Define the problem/opportunity

No

Continue

Stop

Yes
Stage 2:
Gather requirements for the new system

No
Continue

Stop
Yes

Stage 3:
Generate Request For Proposal (RFP)

Stage 4:
Evaluate RFP returns

No

Continue

Stop

Yes
Stage 5:
Choose a vendor
Stage 6:
Implement the new system

Building IT System

Stage 7:
Maintain the new system

03/18/15
24

Characteristic of a Good RFP

Organizational background described
Future projections outlined
Complete problem/opportunity defined
Requirements listed and ranked
Evaluation criteria completely detailed
Contact person specified
Deadline for RFP returns stated
Timetable for project completion included
Concise
Thorough
Building IT System

03/18/15
25

Why is Software Development

so Difficult and Take So Long?
Incomplete or ambiguous requirement
specifications during requirements gathering.
Lack of user and customer involvement
throughout the SDLC.
Requirement changes over the course of
time.
Computer are simpleminded
One error means big failure.
Building IT System

03/18/15
26

Prototyping
A prototype is a simulation or
experimental model of a proposed
system or product.
Prototyping is the process of developing
a simulation or experimental model.
Prototyping can be used as a tool within
the SDLC or it can be used as a
replacement for SDLC.
Building IT System

03/18/15
27

The Prototyping Process

Identifying basic requirements
Developing the initial prototype.
User reviewing
Revising and enhancing the prototype

Building IT System

03/18/15
28

The Prototyping Process

Protoryping
Process

Use the prototype

as a technical
blueprint for the
finel system

Step 1:
Identify basic requirements

Gather basic but not all

requirements from the
users

Step 2:
Develop initial prototype

Preliminary process of
building mostly user
interface

Step 3:
User reviewing

Done by at least two

users and the project
development team

Yes

Continue

No

Building IT System

Step 4:
Revise and
enhance the
prototype

Make sugested
changes (revised) and
add new requirements
(enhance)

03/18/15
29

The Advantages and Disadvantages of

Prototyping
Advantages

Disadvantages

1.

Encourages active user

participation

1.

Leads users to believe the

final system will follow shortly

2.

Gives users a feel for the new

system

2.

Leads to a gloss-over effect

3.

Gives no indication of likely

performance under
operational conditions

3.

Becomes a blueprint for the final

system

4.

Helps resolve discrepancies

among users

5.

Aids in determining technical

feasibility

6.

Helps sell the idea of a

proposed system
Building IT System

03/18/15
30

Data Flow Diagramming

A data flow diagram (DFD) is a graphical
tool that shows the process that act on
data and information as they flow through
a system.
Data flow diagramming incorporates a
top-down decomposition approach to
modeling the processes within a system.
Building IT System

03/18/15
31

Context-Level Diagram
Distributor

CD Mail-Order
System

Customer

Building IT System

03/18/15
32

Second-Level DFD
C u s to m e r

A d v e r t is e m e n t

C u s to m e r
O rd e r

P ro c e s s
c u s to m e r
o rd e r
1 .0

O rd e r
B ill

C u s to m e r
O rd e r

C u s to m e r
A d d re s s
C r e d it
S ta tu s

C D
In fo

N ew
c a t a lo g
in f o

C a t a lo g
D is t r ib u t o r

C a t a lo g
P aym ent
In f o r m a tio n

C D O rd e r
B ill

C u s to m e r

Enaough
In v e n to r y
I n f o r m a t io n

Pay
d is t r ib u t o r
fo r o rd e r
6 .0

C D
I n f o r m a tio n

In v e n to r y

In v e n to ry
R e d u c t io n

P ro c e s s
in c o m in g
c a t a lo g
4 .0

P ro d u c e
a d v e r tis e m e n t
3 .0

D is t r ib u t o r
In fo

In v e n to ry
Level

D is t r ib u t o r

P ro c e s s
c u s to m e r
o rd e r
1 .0

D is t r ib u t o r
A d d re s s

O rd e r C D
fro m
d is tr ib u to r
5 .0

C u s to m e r
P u rc h a s e
P u rc h a s e

Building IT System

C D
O rd e r

03/18/15
33

Computer-Assisted Software
Engineering Tools
CASE tools are software tools that automate
some portion of the SDLC.
CASE tools can help perform tasks within the
SDLC such as identifying the problem or
opportunity, gathering requirements,
generating sample screen and reports,
generating a technical blueprint from the
requirements, an providing documentation.
Building IT System

03/18/15
34

Documentation Production
CASE tools generate a lot of documentation such
as description of how process work, data
dictionaries for databases, data flow diagrams,
and software documentation.
Software documentation becomes important if
changes have to be made in the future.
The documentation that CASE tools produce
becomes a knowledge repository that will be
very beneficial in the future.
Building IT System

03/18/15
35

Changing the Design, not the

Software
If changes do occur,you use CASE tools
to change the technical design and then
simply regenerate the software.
This greatly reduces the amount of time it
takes to do maintenance.

Building IT System

03/18/15
36

Reverse Engineering
Reverse engineering is the process of
building design documents (the system
technical blueprint) from software.
Many CASE tools will allow you to use
existing software and reverse the
process to automatically build design
documents.
Building IT System

03/18/15
37

Producing Correct Software

CASE tools use the technical blueprint to
produce software.
Not only do they produce software fast
(sometimes 1,500 lines per minute), they
also produce correct software.
Correct software doesnt have to be
tested to see if it works; it only has to be
tested to see if it meets the processing
requirements.
Building IT System

03/18/15
38