operational feasibility - process of 7.

REVIEW RESULTS OF
determining how a system will be INVESTIGATION WITH STEERING
accepted by people and how well it will TEAM
meet various system performance - purpose is to gain their input and counsel
expectations. - After the project review, the steering
team might:
schedule feasibility - The process
 agree with the recommendations of
of determining whether the project can
the system development team
be completed within a desired time
 suggest a change in project focus to
frame.
concentrate more directly on meeting
a specific company objective
6. PREPARE DRAFT OF
INVESTIGATION REPORT  decide that the project not feasible
and thus cancel the effort.
system investigation report: A - This input is used to finalize the system
summary of the results of the system investigation report.
investigation, with a recommendation of
a course of action: if they will continue on
to system analysis, modify the project
in some manner and perhaps repeat the
system investigation, or drop the
project altogether.
After a project has completed the
investigation phase and been approved for
further study, the next step is to answer
the question, “What must the information
system do to solve the problem or
capitalize on the opportunity?”
SYSTEM ANALYSIS
- focuses on gathering data on the existing
system, determining the requirements for
the new system, considering alternatives
within identified constraints, and
investigating the feasibility of alternative
solutions.
Steps:
1. Identify and Recruit Team Leader and
Team Members
- there is some personnel turnover when a
project moves from the system
investigation phase to the system analysis
phase.
- Some players may no longer be available
to participate in the project, and new
members with a different set of skills and
knowledge may be required
2. Develop Budget and Schedule for
System Analysis Activities
- After the participants in the system
analysis phase are determined, the team
develops a list of specific objectives and
activities required to complete the
system analysis
3. Study Existing System
- to identify its strengths and weaknesses
and examine current inputs, outputs,
processes, security and controls, and
system performance.
4. Develop Prioritized Set of
Requirements
- to determine user, stakeholder, and
organizational needs for the new or
modified system
- As requirements are identified, an - This report is a more complete and
attempt is made to prioritize each one by detailed version of the system
using three categories: investigation report
● Critical
● Medium priority 7. Review Results of System Analysis
● Low priority with Steering Team
- System requirements are like puzzles - again, review will happen with the
they must be checked for consistency so steering team with a recommendation to
that they all fit together. stop, revise, or go forward with the system
development project.
5. Perform Feasibility Analysis
- The feasibility analysis conducted during
the investigation phase is repeated but
the analysis here can be more in-depth
because more is known about the system
and its requirements as well as the costs
and benefits of the various options

6. Prepare Draft of System Analysis

Report
- System analysis concludes with a formal
system analysis report summarizing
the findings of this phase of the project.
System Design
- purpose is to answer the question,
“How will the information system solve
this problem?”
- creates a complete set of technical
specifications that can be used to
construct the information system.
- Again, note that many of the steps
were performed in the investigation
and system analysis phase but are
now repeated with more current and
complete information.
Steps:
1. Identify and recruit team leader and
team members.
2. Develop schedule and budget for
system design activities.
3. Design user interface
- User interface design integrates
concepts and methods from computer
science, graphics design, and psychology
to build interfaces that are accessible,
easy to use, and efficient
4. Design System Security and Controls
- designers must develop specific system
security and controls for all aspects of the
information system, including hardware,
software, database systems,
telecommunications, and Internet
operations
5. Design Disaster Recovery Plan
- disaster recovery plan: A documented
process to recover an organization’s
business information system assets
including hardware, software, data,
networks, and facilities in the event of a
disaster.
- focuses on technology recovery and
identifies the people or the teams
responsible to take action in the event of a
disaster
6. Design Database
- database provides a user view of data
and makes it possible to add and
modify data, store and retrieve data,
manipulate the data, and generate reports CONSTRUCTION
- One of the steps in designing a database - here, what we do in system design will
involves “telling” the database be converted into an operational system
management system (DBMS) the logical by acquiring and installing hardware and
and physical structure of the data and the software, coding and testing software
relationships among the data for each programs, creating and loading data into
user. databases, and performing initial program
- Another important step in designing the testing.
database is to establish a data dictionary,
a detailed description of all data used in Steps:
the database. 1. Code software components.
- Software code must be written according
again to defined design specifications so that the
5. Perform Feasibility Analysis system meets user and business needs
6. Prepare Draft of System Design and operates in the manner the user
Report expects
7. Review Results of System design - An organization also needs useful
with Steering Team software documentation to accompany the
software code. Technical documentation
includes written details that computer
operators follow to execute the program
and that analysts and programmers use to
solve problems or modify the program.
- User documentation is developed for the
people who use the system. This type of
documentation shows how the program
can and should be used to perform user
tasks.

2. Create and load data.

- making sure that all files and databases
are populated and ready to be used with
the new information system.

3. Perform unit testing.

- Testing of individual components of code
(subroutines, modules, and programs) to
verify that each unit performs as designed