Hanndouts - PowerPoint PPT Presentation

About This Presentation
Title:

Hanndouts

Description:

best ppt for sad – PowerPoint PPT presentation

Number of Views:8
Slides: 61
Provided by: mnbvcxz2
Category:
Tags: hanndout | system

less

Transcript and Presenter's Notes

Title: Hanndouts


1
Paper Coder CSCC-25
System Analysis and Design
DCS-JMI Jan 2019
1
2
Learning Objectives
  • System Philosophy System Thinking
  • To provide you with the understanding and new
    ways of looking at information in the world in
    order to solve business problems
  • To learn methods for analyzing designing
    systems to solve problems using technology.
  • SAD deals with planning the development of IS
    through understanding and specifying in detail
    what a system should do and how the components
    of the system should be implemented and work
    together.

2
3
Global Village
IPDET
4
What is a system?
Unit - I
5
What is a system?
  • System

INPUT
OUTPUT
PROCESS
FEEDBACK
6
What is a system?
  • A collection of inter-related parts
  • which act as a whole
  • towards a common goal
  • e.g.. The library system

7
What is a System?
  • A collection of parts that work together to
    achieve a goal/task
  • Examples
  • Solar system
  • Digestive systems
  • Public transport system
  • Central heating system
  • Computer system
  • Information system
  • A set of objects and relationships among the
    objects viewed as a whole and designed to
    achieve a purpose

8
System
  • A system is an interrelated set of business
    procedures used within one business unit working
    together for a purpose
  • A system has nine characteristics
  • A system exists within an environment
  • A boundary separates a system from its
    environment

9
Characteristics of a System
  1. Components
  2. Interrelated Components
  3. Boundary
  4. Purpose
  5. Environment
  6. Interfaces
  7. Constraints
  8. Input
  9. Output

1.14
10
1.10
11
Systems Thinking Advantages
  • Allows you to think about an organization, a
    process, a program, etc. at a higher, more
    abstract level
  • Reveals problems that are obscured by physical
    details
  • Abstractions are easier to manipulate
  • Promotes creativity

12
Why System Failed/Abandon?
  • When analysts tried to build wonderful systems
    without understanding organization (User Req.)
  • Primarily goal
  • ..to create value for the organization.
  • Systems analyst - a key person (among
    stakeholders) analyzing the business
    problems/issues, identifying opportunities for
    improvement, and designing IS accordingly (to
    implement these ideas).
  • It is important to understand and develop through
    practice the skills needed to successfully
    design and implement new application/IS .

13
(No Transcript)
14
INFORMATION SYSTEMS
INFORMATION SYSTEMS
MANAGEMENT
15
What Is an IS?
  • System a collection of elements and procedures
    that interact (coordinate cooperate) in order
    to accomplish a mutual common goal.
  • IS a collection of people, hardware, software,
    data, and procedures that interact to generate
    information to support the users of an
    organization.

16
WHAT IS INORMATION SYSTEM ?
ENVIRONMENT Customers Suppliers
ORGANIZATION INFORMATION SYSTEM OUTPUT FEEDBACK
INPUT
PROCESS
Regulatory Stockholders Competitors Agencies
17
The System Process
input input input
output output output
Feeback and Control Loop
The System's Environment (constantly changing)
18
System properties
  • Systems can be seen, organized, and described in
    different ways
  • Systems within systems
  • Open systems
  • Have interaction with the outside world
  • React to and accommodate changes in their
    environments
  • Synergy - elements work together beneficially

19
System features
  • Purpose
  • Processes
  • Data
  • Structure/Organisation
  • Context

20
APPROACHES TO INFO SYSTEMS
TECHNICAL APPROACHES
COMPUTER SCIENCE
MANAGEMENT SCIENCE
MIS
SOCIOLOGY
POLITICAL SCIENCE
PSYCHOLOGY
BEHAVIORAL APPROACHES
21
Information Systems Projects Main Reasons
21
22
22
23
Participants in Systems Development
23
24
Lets have Some .
Thought Provoking !!
Questions?
24
25
Questioning???
25
26
Why Questioning?
26
27
Some Critical Questions
  • What should we develop?
  • When should we develop?

Based on goals strategic Direction OF
Organization.
  • Who will be responsible for the development?
  • For whom, we should develop?
  • How should we proceed?
  • ..Methodology ??
  • ..SSAD

28
Stakeholders Their Perspectives
28
29
Steering committee
User 1
I nformation technology vendors
User 2
Systems analyst
Applications programmers
User N
Network administrator
M anagement/ system owner
Database administrator
I nterface design expert
30
Systems Analysts Diverse Roles
  • Three major roles
  • consultant (outsider)
  • supporting expert (insider)
  • agent of change (shaker)
  • Skills of a Systems Analyst
  • Analytical
  • Technical
  • Management
  • Interpersonal

31
Qualities of Systems Analyst
  • Problem solver
  • Communicator
  • Translator
  • Facilitator
  • Strong personal and professional ethics
  • Self-disciplined and self-motivated

32
  • The force behind the effective functioning of
    any organization.?

32
33
The force behind the effective functioning of
any organization is a system.
34
3 Level Pyramid Model (Management Triangle)
Based on the type of decisions taken at different
levels in the organization
35
Management Triangle
5 level pyramid model based on the processing
requirement of different levels in the
organization
36
Business plus IT-Solution Focus
Analysis Design
Plan
Implementation
IT-Solution Focus
Business Focus
Rigorous
37
What is Methodology?
38
What Is a Methodology?
  • A Formalized Approach or series of steps
  • Writing code without a well-thought-out system
    request may work for small programs, but rarely
    works for large ones.
  • Structured Design
  • Projects move methodically from one step to the
    next step..Generally, a step is finished before
    the next one begins.

39
Systems Development Life Cycle
Systems Investigation Product Feasibility Study
Systems Investigation Product Feasibility Study
Systems Analysis Product Functional Requirements Systems Design Product System Specifications Systems Implementation Product Operational System Systems Analysis Product Functional Requirements Systems Design Product System Specifications Systems Implementation Product Operational System
Systems Maintenance Product Improved System
Systems Maintenance Product Improved System
Understand Business Problem or Opportunity
SDLC
Develop an Information System Solution
Implement Information System Solution
Traditional Approach
40
(No Transcript)
41
SDLC -Phases
1-41
42
Most Significant Step/Phase in SDLC
...Quite Challenging Factors/Aspects
42
43
Most Significant Step/Phase in SDLC
...Quite Challenging Factors/Aspects
  • Problem Identification
  • ..Outline Specific / Exact Problem Area
  • Preliminary Investigation
  • Whether it makes to launch the Project.
  • See if it is worthy of further study (detailed)
  • Understanding User Requiremnts/Concerns
  • ..What are the exact User Requirements?
  • Outline Domain (Scope/Boundary)

43
44
Why ?
  • Such a Situation or Scenario ??
  • Challenging Complex or Difficult Task ??

44
45
(No Transcript)
46
Special Professional Traits
What are Those?
  • Special Traits Required to tackle Such a Complex
    Situation or Scenario
  • . What are Those Traits?

46
47
Preliminary Investigation
  • Identify Problem Areas
  • (Outline The Domain).
  • The purpose of PI
  • Ensure whether it makes sense to launch project
  • Define evaluate problem at hand- (Quickly)
  • See if it is worthy of further study (detailed)
  • Suggest some possible courses of
    actions/alternatives (if there is/are any)

48
Preliminary Investigation
  • What will be the Output of PI?

48
49
Preliminary Investigation
  • Feasibility Report
  • Yes !!!
  • Can Go For System Analysis
  • .Detailed System Study

49
50
What is System Analysis?
51
What is System Analysis?
  • The dissection of a system into its component
    pieces for purposes of studying how those
    component pieces interact and work. Formal
    Definition.
  • Systems analysis is done for the purpose of
    subsequently performing a systems synthesis.
  • What is Systems synthesis?

52
What is System Synthesis ?
  • Systems synthesis is the re-assembly of a
    systems component pieces back into a whole
    system hopefully an improved system (Updated
    Version).

53
What is System Analysis ?
  • Survey and Planning of the system and project,
  • Study and Analysis of the existing business and
    IS, and
  • Definition of Business Requirements and
    Priorities for a new or improved system.
  • ..Leads to Logical design.
  • Systems analysis is driven by business concerns,
    specifically, those of system users (end users).

54
Systems Analysis
  • Two Objectives/Tasks -
  • What are Those Specific Objectives?

55
Systems Analysis
  • Two Objectives/Tasks -
  • First Objective Data collection
  • Information gathering about how work is
    done/performed in application area/domain.
  • To ascertain what Information Users Need.
  • What Exactly are The User Requirements?

56
Systems Analysis
  • Two Objectives/Tasks -
  • 2. Second Objective Data Analysis
  • Data Analysis Tools
  • DFD, Decision Tables/Trees and Checklists
  • Documentation includes any instruments used in
    the data/information gathering stage, as well as
    resulting diagrams, Tables, Trees, checklists,
    etc.

57
The Project
  • Moves systematically through phases where each
    phase has a standard set of outputs
  • Produces project deliverables
  • Uses deliverables in implementation
  • Results in actual information system
  • Uses gradual refinement

58
Project Phases
  • Planning
  • Why build the system?
  • Analysis
  • Who, what, when, where will the system be?
  • Design
  • How will the system work?
  • Implementation
  • System delivery

59
Processes and Deliverables
Process Product
Planning
Project Plan
Analysis
System Proposal
Design
System Specification
New System Maintenance Plan
Implementation
60
Underlying Principles
  1. Get the owners and users involved
  2. Use a problem-solving approach
  3. Establish phases and activities
  4. Establish standards for consistent development
    and documentation
  5. Justify systems as capital investments
  6. Dont be afraid to cancel or revise
  7. Divide and conquer
  8. Design systems for growth and change

60
Write a Comment
User Comments (0)
About PowerShow.com