It Fund Report

8/11/2019 It Fund Report

http://slidepdf.com/reader/full/it-fund-report 1/41

INFORMAT

SYST

DEVELOPMENT APROGRAMM

LANGUA• SYSTEM D

• PROGRAMMING LANGUAGE AND PROGRAM DEVELO

• PROGRAM D





INFORMATION SYSTEM

• An Information System (IS) is a collection of hardware, software, data,

and procedures that work together to produce quality information.

•

An information system supports daily, short-term, long-range activitiesusers.



SYSTEM DEVELOPMENT LIFE

CYCLE SDLCSystem development activities often are grouped into larger categories cphases. This collection of phases sometimes is called the SYSTEM

DEVELOPMENT LIFE CYCLE (SDLC). Many SDLC contain five phases:

1. Planning

2. Analysis

3. Design

4. Implementation

5. Operation, Support, and Security



1. Planning-()Review/prioritize project

request()Allocate resources

()Form project developmentteam

2. Analysis-() Conduct Preliminary

investigation()Study current system

()Determine user requireme()Recommend Solution

3. Design-()Acquire hardware andsoftware, if necessary

()Develop details ofsystem

4. Implementation-()Develop programs

()Install and test newsystems

()Train Users()Convert to new system

5. Operation, Support, andSecurity-

()Perform maintenanceactivities

()Monitor systemperformance

()Assess system security





PROJECT MANAGEMENT

Project management is the process of planning, scheduling, and then conthe activities during system development. The goal of project manageme

deliver an acceptable system to the user in an agreed-upon time frame, w

maintaining costs.

In smaller organizations or projects, one person manages the entire projelarger projects, the project management activities are separated between

project manager and a project leader.

• Project Leader – manages and controls the budget and schedule of the

project

• Project Manager – controls the activities during system development





PROJECT MANAGEMENT TOOL

Project leader can use Project Management Software to assist them in pl

scheduling and controlling development projects:

• Gantt Chart

• Pert Chart



GANTT CHART

• A Gantt Chart, developed by Henry L. Gantt, is a bar chart th

uses horizontal bars to show project phases or activities. A

horizontal axis across the top or bottom of the char representime.



GANTT CHART



PERT CHART

• A tool used for planning and scheduling large, complex projects is the P

chart. A PERT chart, short for PROGRAM EVALUATIONS AND REVIEW

TECHNIQUE chart, analyzes the time required to complete a task and

identifies the minimum time required for an entire management.



PERT CHART



FEASIBILITY ASSESSMENT

Feasibility is a measure of how suitable the development of a system will

organization. A project that is feasible at one point during system develop

might become infeasible at a later point. Thus, systems analysts frequent

evaluate feasibility during the system development project.



FOUR TESTS TO EVALUATE

FEASIBILITY ARE• Operational Feasibility: Measures how well the proposed information s

will work. Will the users like the new system? Will they use it? Will it m

their requirements? Is it secure?

• Schedule Feasibility: Measures whether the established deadlines for t

project are reasonable. If a deadline is not reasonable, the project lead

might make a new schedule.• Technical Feasibility: Measures whether the organization has or can ob

the hardware, software, and people needed to deliver and then suppo

proposed information system.

• Economic Feasibility: Measures whether the lifetime benefits of the pr

information system will be greater than its lifetime costs.





DATA AND INFORMATION GATHERING

TECHNIQUES

System analysts and other IT professionals use several techniques to gather data and

information. They review documentation, observe, survey, interview, conduct joint-app

design sessions and research.

• Review Documentation – provides information about the organization such as its op

weaknesses and strengths.

• Observe - observing people helps system analyst understand exactly how they perfo

task.

• Survey – To obtain data and information from a large number of people, system anal

distribute surveys.

• Interview – the interview is the most important data and information gathering tech

the system analyst. It allows the system analyst to clarify response and probe during

face feedback.



DATA AND INFORMATION GATHERING

TECHNIQUES

• JAD Sessions – instead of a single one-on-one interview, analysts often use the joint

application design session to gather information.

• Research – Newspapers, computer magazines, reference books, trade shows, the We

vendors, and consultants are excellent sources of information. These sources can pro

systems analyst with information such as the latest hardware and software products

explanations of new processes and procedures.



WHAT INITIATES SYSTEM

DEVELOPMENT?

A user may request a new or modified information system for a variety o

reasons. The most obvious reason is to correct a problem such as an inco

calculation or a security breach. Another reason is to improve the inform

system.

Upon completion of the preliminary investigation, the system analyst wri

feasibility report. This report presents the team’s findings to the steering

committee.



WHAT INITIATES SYSTEM

DEVELOPMENT?In some cases, the project team may recommend not to continue the project. If the proteam recommends continuing and the steering committee approves this recommendat

detailed analysis begins.

• Detailed Analysis

• The System Proposal

• Testing and Evaluating Vendor Proposal

• Making a Decision

• Detailed Design

• Prototyping

• Case tools

• Quality Review Techniques



DETAILED ANALYSIS

Detailed analysis involves three major activities:

• 1. study how the current system works

• 2. determine the users’ wants, needs, and requirements

• 3. recommend a solution



THE SYSTEM PROPOSAL

After the systems analyst has studied the current system and determined

user requirements, the next step is to communicate possible solutions fo

project in a system proposal.

The system analyst presents the system proposal to the steering committthe steering committee approves the solution, the project enters the des

phase.



TESTING AND EVALUATING VENDOR

PROPOSALS

Evaluating the proposals and then selecting the best one often is a difficu

System analysts use many techniques to test the various software produc

vendors.



MAKING A DECISION

Having rated the proposals, the system analyst presents a recommendati

the steering committee. The recommendation could be to award a contra

vendor or to not make any purchases at this time.



DETAILED DESIGN

The next step is to develop detailed design specifications for the components in the pro

solution. The activities to be performed include developing designs for the databases in

outputs, and programs.

• During database design, the system analyst works closely with the database analyst a

database administrators to identify those data elements that currently exist within th

organization.

• During detailed design of inputs and outputs, the system analyst carefully designs ev

menu screen, and report specified in the requirements.



DETAILED DESIGN

The systems analyst typically develops two types of designs for each input and output: a mockupchart.

• A mockup is a sample of the input or output that contains actual data. The system analyst sho

to users for their approval



DETAILED DESIGN

After users approve the mockup, the systems analyst develops a layout chart for the

programmer.

• A layout chart is more technical and contain programming-like notations. Many

database programs provide tools for technical design.



PROTOTYPING

Many systems analysts today use prototypes during detailed design. A prototype is a wo

model of the proposed system. The systems analyst actually builds a functional for of th

solution during design.

The main advantage of a prototype is users can work with the system before it is complmake sure it meets their needs. As soon as users approve a prototype, system analyst c

implement a solution more quickly than without a prototype





QUALITY REVIEW TECHNIQUES

Many people should review the detailed design specifications before the

given to the programming team. Reviewers should include users, systems

analyst, managers, IT staff, and members of the system development tea

the steering committee decides, the project still is feasible, which usuallycase, the project enters the implementation phase.



IMPLEMENTATION PHASE

The purpose of the implementation phase is to construct, or build, the nmodified system and then deliver it to the users. Members of the system

development team perform four major activities in this phase:

1. Develop programs

2. Install and test the new system

3. Train users

4. Convert to the new system



OPERATION SUPPORT AND

SECURITY PHASE

The purpose of the operation, support and security phase is to provide

ongoing assistance for an information system and its users after the syste

implemented. The support phase consists of three major activities:

1. Perform maintenance activities

2. Monitor system performance

3. Assess system security





PROGRAM DEVELOPMENT

Program development consists of series of steps programmers use to build computer pThe system development life cycle guides information technology professionals through

development of an information system. Likewise, the program development life cycle (P

guides computer programmers through the development of a program. The program

development life cycle consists of six steps:

1. Analyze Requirements

2. Design Solution3. Validate Design

4. Implement Design

5. Test Solution

6. Document Solution



SYSTEM DEVELOPMENT LIFE



SYSTEM DEVELOPMENT LIFECYCLE

1. Planning

2. Analysis

3. Design4.

Implementation

5. Operation,Support, and

Security



CONTROL STRUCTURES

When programmers are required to design the logic of a program, they ty

use control structure to describe the tasks a program is to preform. A con

structure depicts the logical order of a program instructions.

A sequence control structure shows one or more actions following each

order. Actions include inputs and outputs. All actions must be executed, n

can be skipped.

Action 1 Action 2 Action 3



IF THEN ELSE CONTROL

STRUCTURE

When a program evaluates the condition in an if-then-else control structure, it yields one of twopossibilities: true or false.



REPETITION CONTROL STRUCTU

The repetition control structure enables a program to perform one or more actions repeatedly as

certain condition is met. Many programmers refer this construct as a loop.

• Do-while control structure

• Do-until control structure



DO WHILE CONTROL STRUCTURE

A do-while control structure repeats one or more times as long as a speccondition is true. This control structure tests a condition at the beginning

loop.



DO UNTIL CONTROL STRUCTURE

The do-until control structure is similar to the do-while but has two major differences: wit tests the condition and when it stops looping. This program stops looping after it proc

the action that it requires to be done.

Date post:	02-Jun-2018
Category:	Documents
Upload:	johnmauruss
View:	215 times
Download:	0 times

It Fund Report

Documents