Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 201 views

    System Design

    Uploaded by

    Hitesh Dabas
    System design bridges the gap between understanding problems and implementing solutions. It takes inputs like requirements and current systems analysis and produces outputs like data schemas, program structures, and prototypes. The document then describes logical design focusing on abstract data flows and user needs, and physical design detailing input/output processes and user interfaces. Architectural design defines the system architecture and relationships between development modules.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    System Design

    Uploaded by

    Hitesh Dabas
    201 views2 pages
    System design bridges the gap between understanding problems and implementing solutions. It takes inputs like requirements and current systems analysis and produces outputs like data schemas, program structures, and prototypes. The document then describes logical design focusing on abstract data flows and user needs, and physical design detailing input/output processes and user interfaces. Architectural design defines the system architecture and relationships between development modules.

    Original Title

    System design.docx

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    System design bridges the gap between understanding problems and implementing solutions. It takes inputs like requirements and current systems analysis and produces outputs like data schemas, program structures, and prototypes. The document then describes logical design focusing on abstract data flows and user needs, and physical design detailing input/output processes and user interfaces. Architectural design defines the system architecture and relationships between development modules.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    201 views2 pages

    System Design

    Uploaded by

    Hitesh Dabas
    System design bridges the gap between understanding problems and implementing solutions. It takes inputs like requirements and current systems analysis and produces outputs like data schemas, program structures, and prototypes. The document then describes logical design focusing on abstract data flows and user needs, and physical design detailing input/output processes and user interfaces. Architectural design defines the system architecture and relationships between development modules.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    INFORMATION SYSTEM MANAGEMENT

    System design

    System design is the phase that bridges the gap between problem domain and
    the existing system in a manageable way. This phase focuses on the solution
    domain, i.e. “how to implement?”
    It is the phase where the SRS document is converted into a format that can be
    implemented and decides how the system will operate.
    In this phase, the complex activity of system development is divided into several
    smaller sub-activities, which coordinate with each other to achieve the main
    objective of system development

    Inputs to System Design


    System design takes the following inputs −
     Statement of work
     Requirement determination plan
     Current situation analysis
     Proposed system requirements including a conceptual data model,
    modified DFDs, and Metadata (data about data).

    Outputs for System Design


    System design gives the following outputs −
     Infrastructure and organizational changes for the proposed system.
     A data schema, often a relational schema.
     Metadata to define the tables/files and columns/data-items.
     A function hierarchy diagram or web page map that graphically describes
    the program structure.
     Actual or pseudocode for each module in the program.
     A prototype for the proposed system.

    Logical Design
    Logical design pertains to an abstract representation of the data flow, inputs, and
    outputs of the system. It describes the inputs (sources), outputs (destinations),

    1
    INFORMATION SYSTEM MANAGEMENT

    databases (data stores), procedures (data flows) all in a format that meets the user
    requirements.
    While preparing the logical design of a system, the system analyst specifies the
    user needs at level of detail that virtually determines the information flow into
    and out of the system and the required data sources. Data flow diagram, E-R
    diagram modeling are used.
    Physical Design
    Physical design relates to the actual input and output processes of the system. It
    focuses on how data is entered into a system, verified, processed, and displayed
    as output.
    It produces the working system by defining the design specification that specifies
    exactly what the candidate system does. It is concerned with user interface
    design, process design, and data design.
    It consists of the following steps −
     Specifying the input/output media, designing the database, and specifying
    backup procedures.
     Planning system implementation.
     Devising a test and implementation plan, and specifying any new hardware
    and software.
     Updating costs, benefits, conversion dates, and system constraints.
    Architectural Design
    It is also known as high level design that focuses on the design of system
    architecture. It describes the structure and behavior of the system. It defines the
    structure and relationship between various modules of system development
    process.

    Entity Relationship Diagram:

    You might also like