Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 2 System Analysis, Steps, Tangible value-quantifies and measured…

- - - - Technical-extent to which system can be successfully designed,developed and installed by expertise
        
        Software &Hardware
        
        time required for average transactions
        
        idle time of the network
        
        total volume capacity of system
        
        size of memory provided
      - Operational-how well system ultimately will be accepted by its users and incorporated into current operations
        
        Determines if human resources are available to operate system after installed it
      - Schedule
        
        Can company/IT team control factors affect schedule feasibility
        
        Has management establish jadual waktu tegas dlm projek
        
        What conditions must be satisfies during development of system
      - Economic (cost benefit analysis)
        
        Analyst and analyst team time
        
        Business employee time
        
        Software
        
        Hardware
        
        Software development
        
        Tangible Benefits-advantage measurable mount up to organization
        Example increase speed of processing
        access to information on more timely basis
  - - - Problems Definition-The things must be accomplished along with the possible solutions and constraints that limit development system
        
        3)Determine-relative importance of issues or objectives
        
        4)Identify-which objectives are most critical
        
        1)Find-find number of points that included in one issue (from iv,observe,document analysis
        
        2)State-state the objective
    - - System Request-Document that describes business reasons for build system
        
        Business requirements-New or enhance business capability (PROVIDE ONLINE ACCESS TO INFO)
        
        Business value-benefits that system will create the organization (INCREASE 3% IN SALES)
        
        Business need-related reason initiate system (INCREASE SALES)
        
        Special issues or constraints-issues that pertain to approval commitee decisio (MANDATED DEADLINE )
        
        Project Sponsor-Person who initiates the projectand who serves as primary point of contact (IT MANAGER)
- - - - General design for the whole system is performed
      - Project then is divided into subprojectstaht can be design and implemented in parallel
      - Adv-reduce time required to deliver system
      - Disadv-if subprojects are not completely independent,design decisions in one subprojects may affect another
    - - Pay more attention to testing
      - Each level of testing is clearly linked to part of analysis or design phase
        -helping to ensure high quality test effectiveness
      - STRENGTHS-Simple and straightforward
        -Quality improves through the empasis on testing
        -Include Quality assurance expertise early in project
      - WEAKNESS-Rigid
        DIficult to use in dynamic business environment
    - - Dificult to go backward
      - poor for unclear user requirements
      - Sequentially from one phase to
        another
      - Adv-identify requirements long before programming begins
        Limit changes to the requirements as gthe project
      - Disadv-design must be completely specified before programming start
    - - Preliminary version of system
        
        Preliminary version of the system to users
      - PATIENT with the repeated new versions
      - Breaks overall project into series of versionsdeveloped sequentially
      - STRENGTHS
        
        Users get system to use quickly
        
        users identify additional needs for later versions
      - WEAKNESS
        
        Users faced with incomplete system
        
        users must be patient and wait for fully functional system