Information Requirement Analysis

Identify Problems, Opportunities, and objectives

• 1st step in the 7 phase of SDLC

• This stage is critical to the success of the rest of the project

• (1 Answer) will be brought up by organizational members that need to be address

• Seizing (2 Answer) allow the business gain competitive advantage or set an industry standard

• Identifying (3 Answer) and reaching it by addressing specific (1 Answer)or (2 Answer)

• Output: Feasibility Report

  • containing a problem definition and summarizing the objectives

Determining Information Requirement

• 2nd step in the 7 phase of SDLC

• Tools : interviewing, sampling and investigating hard data, questionnaires, observation

• Striving to understand what information users need to perform their jobs

• Information Analyst (IA) specialize on this

• Need to know the details of current system function :

  • WHO (the people who are involved)

  • WHAT (the business activity)

  • WHERE (the environment in which the work takes place)

  • WHEN (the timing)

  • HOW (how the current procedures are performed)

• Business Process Reengineering (BPR)

  • help in framing an approach for rethinking the business in a creative way.

Analyzing System Needs

• 3rd step in the 7 phase of SDLC

• Tools: Data Flow Diagram (DFD)

• analyzes the structured decisions made

  • (conditions, condition alternatives, actions and action rules can be determined)

• Prepares a system proposal

  • (summary of initial research, cost benefit analysis, recommendation etc.)

Designing the Recommended System

• 4th step in the 7 phase of SDLC

• the analyst designs accurate data entry procedures so that data going into the information system are correct.

• Devising the user interface and output

• Ex. GUIs that use a mouse or touch screen on screen menus

           Keyboard (to type in questions and

                           answers)

• designing files or databases

• Design controls and backup procedures to protect the system and data

• To produce program specification packets for programmer

  • (should contain input and output layouts, file specifications, and processing details)

• Design system flowchart

Developing and Documenting Software

• 5th step in the 7 phase of SDLC

• The analyst works with programmers to develop any original software that is needed

• Communicate to the programmer what needs to be programmed

• Works with uses to develop effective documentation for software, including procedure manuals, on-line helps, webs sites (FAQs)

• Documentation tells user how to use software problems occur.

Testing the Maintaining the System

• 6th step in the 7 phase of SDLC

• It is much less costly to catch problems before the system is signed over to users

• Testing is completed by programmer alone, or system analysts in conjunction with programmers

• Much of the programmer’s routine work consists of maintenance and businesses spend a great deal of money on maintenance

Implementing and Evaluating the System

• 7th step in the 7 phase of SDLC

• last phase of system development which the analyst help implement the IS

• Involves training users to handle the system

• This process includes converting files from old formats to new ones, or building a database, installing equipment, brining the new system into production

Feasibility Study

• used to gather broad data for the members of management that in turn enables them to make a decision on whether to proceed with a system study

• Data of (answer) can be gathered through interviews

  • (to know the problem or opportunity being suggested)

• Identifies the important risks associated with the project that must be addressed if the project is approved

• Assess the operational, technical, and economic merits of the proposed project

Technical Feasibility

• part of the 3 types of feasibility study

• Add on to present system

• Technology available to meet users needs

• assesses whether the current technical resources are sufficient for the new system

• If they are not available, can they be upgraded to provide the level of technology necessary for the new system

• Refers to the technical resources needed to develop, purchase, install, or operate the system

• Analysis of technical risks like familiarity with the application or technology, project size, and compatibility

Economic Feasibility

• part of the 3 types of feasibility study

• determines whether the time and money are available to develop the system

  • Systems analysts’ time

  • Cost of system study

  • Cost of employee’s time for study

  • Estimated cost of hardware

  • Cost of packaged software or software development

• Includes the purchase of:

  • New equipment

  • Hardware

  • Software

• Means that the projected benefits of the proposed system outweigh the estimated costs, which includes ongoing support and maintenance costs, as well as acquisition costs

• Costs:

  • Development Cost

  • Operational Cost

  • Tangible Benefits

  • Intangible Benefits

Operational Feasibility

• part of the 3 types of feasibility study

• determines if the human resources are available to operate the system once it has been installed

  • Whether the system will operate when installed

  • Whether the system will be used

• Means that the proposed system will be used effectively after it has been developed

• A measure of the user’s attitude towards the system and how well the solution will work in the organization

• Users that do not want a new system may prevent it from becoming operationally feasible. Furthermore, if users have a difficulty with a system, it will not produce the expected benefits

Schedule Feasibility

• not part of the 3 types of feasibility study

• it is added by sir (i think)

Planning

includes all the activities required to select a system analysis team, assign numbers of the team to appropriate projects, estimate the time required to complete each task, and schedule the project so that tasks are completed in timely fashion.

Control

• means using feedback to monitor the project, including comparing the plan for the project with its actual evolution

• means taking appropriate action to expedite or reschedule activities to finish on time while motivating team members to complete the job

Project Feasibility

is a decision to be made not by the system analyst but instead by management.

• Decisions

  • based on feasibility data

  • expertly and professionally gathered and presented by the analyst.

Analysis

Design

Implementation

the 3 major activities in planning a project

Activities in Analysis Phase

• Data Gathering

• Data Flow and Decision Analysis

• Proposal Preparation

Activities in Design Phase

• Data entry design

• input design

• output design

• data organization

Activities in Implementation Phase

• Implementation

• Evaluation

Gantt Chart

• Used in Project Scheduling

• is an easy way to schedule tasks. 

• a chart on which bars represents each tasks or activity.

• The length of which bar represents the relative length of the task.

Program Evaluation and Review Techniques - Critical Path Method

• PERT-CPM

• A program (project) is represented by a network of nodes and arrows that are then evaluated to determine the critical activities, improve the schedule if necessary, and review progress once the project is undertaken.

Activity Planning

• it includes:

  • Selecting a systems analysis team

  • Estimating time required to complete each task

  • Scheduling the project

• Two tools for project planning and control are

  • Gantt charts

  • PERT diagrams

Estimating Time

• Project is broken down into phases

• Further broken down into tasks or activities

• Finally broken down into steps or even smaller units

• Estimate time for each task or activity

• May use a most likely, pessimistic, and optimistic estimates for time

Team Management

• Teams often have two leaders:

  • One who leads members to accomplish tasks

  • One concerned with social relationships

• The systems analyst must manage

  • Team members

  • Their activities

  • Their time, and resources