100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Previously searched by you
Previously searched by you
logo
Summary INFO1004 Block 2 R70,00
Add to cart
Quickly navigate to
Preview
  2.  
  3. University Of The Witwatersrand (wits)
  4.  
  5. Fundamentals in Information Systems (INFO1004)

Summary

Summary INFO1004 Block 2
 10 views  0 purchase

A complete and in-depth summary of the content covered in INFO1004 Block 2. These notes include all the important information in a colourful and succinct manner. They assisted me in scoring high marks in all test, exams and assignments and I hope they will do the same for you.

Preview 3 out of 18  pages

Document information

  • October 18, 2023
  • 18
  • 2023/2024
  • Summary

Subjects

Written for

All documents for this subject (2)

Seller

avatar-seller
Norma2003

Content preview

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

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying this summary from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller Norma2003. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy this summary for R70,00. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

56326 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy summaries for 14 years now

Start selling
R70,00
  • (0)
Add to cart
Added