Summary INFO1004 Block 2

INFORMATION SYSTEMS
INFO 1004
SUMMARIES: BLOCK 2

,INFORMATION
SYSTEMS INFO1004
BLOCK 2

DEVELOPING INFORMATION
SYSTEMS FRAMING : Our THINKING

·
SYSTEMS ANALYST :
SA &D : STRUCTURED PROCESS THAT IS EMPLOYED IN DEVELOPMENT Of IS

DESIGN TECHNIQUES TO SOLUE REAL WORLD PROBLEMS USING TECHNOLOGY
-

USES SYSTEMS ANALYSIS +




UNDERSTAND REAL WORLD PROBLEMS
-




TECHNICAL EXPERTISE
-




-



RESPONSIBLE FOR LIAISON BETWEEN TECHNOLOGY PEOPLE + BUSINESS PEOPLE

REAL WORLD PROBLEM SOLVER
-




·
SYMPTOM= EVIDENCE Of PROBLEM NOT PROBLEM ITSELF
,
(HIGHLY VISIBLE)
·
SYSTEMS ANALYST WILL FOLLOW CAUSE + EFFECT TRAIL TO GET TO ROOT CAUSE

FINDING COMMON SOURCE Of SEVERAL SYMPTOMS :
ABLE TO IDENTIFY PROBLEM

·
SOLVING PROBLEM WILL ADDRESS MANY SYMPTOMS

PROBLEM PLACE
·
IN INFORMATION SYSTEMS IS EITHER NO SYSTEM IN TO ACCOMPLISH GOAL OR BAD

SYSTEM IN PLACE :. FAILING TO ACCOMPLIS GOAL

ORGANISATIONALISOCIETAL 3 LEVELS OF PROBLEM SOLVING IS
·
REAL WORLD PROBLEMS MAY BE INDIVIDUAL , :.


·
DIFFERENCE BETWEEN ANALYSIS + DESIGN :



-



ANALYSIS =
WHAT


UNDERSTAND/FRAME PROBLEM

DEFINE WHAT SYSTEM MUST DO TO SOLVE PROBLEM ::. DEFINE REQUIREMENTS THAT MUST BE

MET TO SOLUE PROBLEM
-




DESIGN =
HOW

DEFINE HOW SYSTEM WILL ADDRESS PROBLEM : A CONCEPTUAL/LOGICAL SOLUTION

DEFINE HOW VARIOUS COMPONENTS Of SYSTEM WILL WORK TOGETHER TO SOLUE PROBLEM
-


NEITHER ACTIVITIES TRADITIONALLY INVOLVE ANY CODE
·
HOW DO SYSTEMS ANALYSTS APPROACH PROBLEMS :
-


FRAME UNDERSTAND PROBLEM
-


VERIFY THAT PROBLEM ACTUALLY EXISTS

VERIFY THAT BENEFITS PROBLEM OUTWEIGH COST
-


Of SOLVING

REQUIREMENTS FOR SOLVING PROBLEM
-

DEFINE

DEVELOPSET OF POSSIBLE/
-



ALTERNATIVE SOLUTIONS

DECIDE WHICH
-



SOLUTION IS BEST + RECOMMEND IT

-



OVERSEE IMPLEMENTATION Of SOLUTION

REVIEW+MONITOR TO ENSURE DESIRED RESULTS HAVE BEEN
-


ACHIEVED

, 3DLC :
·
SYSTEMS ANALYSTS SOLVE "REAL WORLD "PROBLEMS USING TECHNOLOGY

·
ACHIEVE THIS BY ORGANISING WORK INTO PROJECTS

PROJECT :

PLANNED UNDERTAKING THAT HAS A BEGINNING +END AND PRODUCES A DESIRED

RESULT/PRODUCT

IS PROJECTS CAN BE SMALL/LARGE +VARY IN LENGTH

·
In IS in s sequence : THE SYSTEMS DEVELOPMENT LIFECYCLE
·
SDLC :

PROVIDES HOLISTIC/ SYSTEMATIC IS PROJECTS
-


FRAMEWORK FOR MANAGING
-


Mosi IS PROJECTS USE SOME ADAPTATION/VARIATION/FLAVOUR Of SDLC

2 ALTERNATIVE APPROACHES PREDICTIVE THAT PROJECTS CAN BE PLANNED
-


:
ASSUMES IN

ADVANCE :: LOW UNCERTAINTY ,
COMPLEXITY + RISK

ADAPTIVE :


ASSUMES CANNOT PLAN IN ADVANCE SO MORE

FLEXIBLE APPROACH : HIGH UNCERTAINTY, COMPLEXITY + RISK
·
TRADITIONAL DREDICTIVE SDLC :

I PLANNING
2
ANALYSIS

3
DESIGN PADIS
4
IMPLEMENTATION
5
SUPPORT

·
PLANNING :

DEFINE /FRAME PROBLEM
-


BY FORMULATING PROBLEM STATEMENT

"SCOPE CREED"
-


DETERMINE PROJECT SCOPE TO AVOID

ECONOMIC, OPERATIONAL , TECHNICAL , LEGAL
-


ASSESS + CONFIRM PROJ ECT FEASIBILITY
:


...




PROJECT
-


ALLOCATE RESOURCES TO

-



LAUNCH PROJECT

-


NO CODE

⑧
ANALYSIS :

-


GATHER INFO TO UNDERSTAND PROBLEM DOMAIN :. UNDERSTAND CLIENTS SYSTEMS , PROCESSES, CULTURE ...




-


DEFINE REQUIREMENTS TUROUGH QUESTIONAIRES ,
INTERVIEWS, OBSERVATION ...




-


PRIORITISE REQUIREMENTS
-



VALUATE ALTERNATIVE SOLUTIONS

PRESENT RECOMMENDATIONS
-


CHOOSE A SOLUTION

-


USUALLY NO CODE

·
DESIGN :

-



DATABASE DESIGN

DESIGN
-


USER INTERFACE


PROCESS DESIGN/ENGINEERING
-




-



SOFTWARE SELECTION

-


HARDWARE SELECTION
-


SECURITY CONTROLS

USUALLY NO LODE
-




-"Cloud" IS NOW MAJOR INFLUENCE