EXPLORING

INFORMATION
SYSTEM
DEVELOPMENT AND
PROGRAMMING
LANGUAGE
SYSTEM DEVELOPMENT
PROGRAMMING LANGUAGE AND PROGRAM DEVELOPMENT TOOLS
PROGRAM DEVELOPMENT

SYSTEM DEVELOPMENT
A System is a set of components that interact to achieve a common goal.
Businesses use many types of systems:
Billing System allows a company to send invoices and receive payments
from customer through a payroll system, employees receive paychecks.
Manufacturing System produces the good that customers order.
Inventory System keeps track of the items in a warehouse
Information System
INFORMATION SYSTEM
An Information System (IS) is a collection of hardware, software, data, people,
and procedures that work together to produce quality information.
An information system supports daily, short-term, long-range activities of
users.
SYSTEM DEVELOPMENT LIFE
CYCLE SDLC
System development activities often are grouped into larger categories called
phases. 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 development
team
2. Analysis-
() Conduct Preliminary
investigation
()Study current system
()Determine user requirement
()Recommend Solution
3. Design-
()Acquire hardware and
software, if necessary
()Develop details of
system
4. Implementation-
()Develop programs
()Install and test new
systems
()Train Users
()Convert to new system
5. Operation, Support, and
Security-
()Perform maintenance
activities
()Monitor system
performance
()Assess system security
WHO PARTICIPATES IN SYSTEM
DEVELOPMENT?
System development should involve representatives from each department in which proposed system will be used.
This includes both nontechnical users and IT professionals. During system development, the System Analyst will
meet and work on these people:
Steering Committee Members
Application and System Programmers
Vendors
Web Master and Web Developers
Security Specialists
Network Admins/Data Communications Analyst
Data Warehousing Specialist
Database Admins and Database Analyst
Users
Managers
Other Systems Analyst
PROJECT MANAGEMENT
Project management is the process of planning, scheduling, and then controlling
the activities during system development. The goal of project management is to
deliver an acceptable system to the user in an agreed-upon time frame, while
maintaining costs.

In smaller organizations or projects, one person manages the entire project. For
larger projects, the project management activities are separated between a
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
TO PLAN AND SCHEDULE A PROJECT
EFFECTIVELY, THE PROJECT LEADER IDENTIFIES
THE FOLLOWING ELEMENTS FOR THE PROJECT
Goal, objectives, and expectations of the project, collectively called the scope.
Required activities
Time estimates for each activity
Cost estimates for each activity
Order of activities
Activities that can take place at the same time

PROJECT MANAGEMENT TOOLS
Project leader can use Project Management Software to assist them in planning,
scheduling and controlling development projects:
Gantt Chart
Pert Chart
GANTT CHART
A Gantt Chart, developed by Henry L. Gantt, is a bar chart that
uses horizontal bars to show project phases or activities. A
horizontal axis across the top or bottom of the char represents
time.
GANTT CHART
PERT CHART
A tool used for planning and scheduling large, complex projects is the PERT
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 be the
organization. A project that is feasible at one point during system development
might become infeasible at a later point. Thus, systems analysts frequently re-
evaluate feasibility during the system development project.
FOUR TESTS TO EVALUATE
FEASIBILITY ARE
Operational Feasibility: Measures how well the proposed information system
will work. Will the users like the new system? Will they use it? Will it meet
their requirements? Is it secure?
Schedule Feasibility: Measures whether the established deadlines for the
project are reasonable. If a deadline is not reasonable, the project leader
might make a new schedule.
Technical Feasibility: Measures whether the organization has or can obtain
the hardware, software, and people needed to deliver and then support the
proposed information system.
Economic Feasibility: Measures whether the lifetime benefits of the proposed
information system will be greater than its lifetime costs.
DOCUMENTATION
During system development, project member produce much documentation.
Documentation is the collection and summarization of data and information. It
includes reports, diagrams, programs, or any other information generated
during system development.

It is important that all documentation be well written, thorough, consistent, and
understandable.
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-application
design sessions and research.
Review Documentation provides information about the organization such as its operations,
weaknesses and strengths.
Observe - observing people helps system analyst understand exactly how they perform a
task.
Survey To obtain data and information from a large number of people, system analyst
distribute surveys.
Interview the interview is the most important data and information gathering technique for
the system analyst. It allows the system analyst to clarify response and probe during face-to-
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 Web,
vendors, and consultants are excellent sources of information. These sources can provide the
systems analyst with information such as the latest hardware and software products and
explanations of new processes and procedures.
WHAT INITIATES SYSTEM
DEVELOPMENT?
A user may request a new or modified information system for a variety of
reasons. The most obvious reason is to correct a problem such as an incorrect
calculation or a security breach. Another reason is to improve the information
system.

Upon completion of the preliminary investigation, the system analyst writes the
feasibility report. This report presents the teams findings to the steering
committee.
WHAT INITIATES SYSTEM
DEVELOPMENT?
In some cases, the project team may recommend not to continue the project. If the project
team recommends continuing and the steering committee approves this recommendation, then
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 all
user requirements, the next step is to communicate possible solutions for the
project in a system proposal.

The system analyst presents the system proposal to the steering committee. If
the steering committee approves the solution, the project enters the design
phase.
TESTING AND EVALUATING VENDOR
PROPOSALS
Evaluating the proposals and then selecting the best one often is a difficult task.
System analysts use many techniques to test the various software products from
vendors.
MAKING A DECISION
Having rated the proposals, the system analyst presents a recommendation to
the steering committee. The recommendation could be to award a contract to a
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 proposed
solution. The activities to be performed include developing designs for the databases inputs,
outputs, and programs.
During database design, the system analyst works closely with the database analyst and
database administrators to identify those data elements that currently exist within the
organization.
During detailed design of inputs and outputs, the system analyst carefully designs every
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 mockup and a layout
chart.
A mockup is a sample of the input or output that contains actual data. The system analyst shows mockup
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 working
model of the proposed system. The systems analyst actually builds a functional for of the
solution during design.

The main advantage of a prototype is users can work with the system before it is completed to
make sure it meets their needs. As soon as users approve a prototype, system analyst can
implement a solution more quickly than without a prototype
CASE TOOLS
Many system analyst use computer software to assist during system development.
Computer-aided software engineering (CASE) software tools are designed to support one or
more activities of system development
QUALITY REVIEW TECHNIQUES
Many people should review the detailed design specifications before they are
given to the programming team. Reviewers should include users, systems
analyst, managers, IT staff, and members of the system development team. If
the steering committee decides, the project still is feasible, which usually is the
case, the project enters the implementation phase.
IMPLEMENTATION PHASE
The purpose of the implementation phase is to construct, or build, the new or
modified 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 system is
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 programs.
The system development life cycle guides information technology professionals through the
development of an information system. Likewise, the program development life cycle (PDLC)
guides computer programmers through the development of a program. The program
development life cycle consists of six steps:
1. Analyze Requirements
2. Design Solution
3. Validate Design
4. Implement Design
5. Test Solution
6. Document Solution
PROGRAM DEVELOPMENT LIFE
CYCLE
1. Analyze
Requirements
2. Design
Solutions
3. Validate
design
4. Implement
Design
5. Test
Solution
6. Document
Solution
SYSTEM DEVELOPMENT LIFE
CYCLE
1. Planning
2. Analysis
3. Design
4.
Implementation
5. Operation,
Support, and
Security
CONTROL STRUCTURES
When programmers are required to design the logic of a program, they typically
use control structure to describe the tasks a program is to preform. A control
structure depicts the logical order of a program instructions.
A sequence control structure shows one or more actions following each other in
order. Actions include inputs and outputs. All actions must be executed, none
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 two
possibilities: true or false.
REPETITION CONTROL STRUCTURE
The repetition control structure enables a program to perform one or more actions repeatedly as long as a
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 specified
condition is true. This control structure tests a condition at the beginning of the
loop.
DO UNTIL CONTROL STRUCTURE
The do-until control structure is similar to the do-while but has two major differences: where
it tests the condition and when it stops looping. This program stops looping after it processes
the action that it requires to be done.