CHAPTER 4: Flashcards
Planning System and System Request (22 cards)
System Planning Phase 2 Activities
The systems planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will create it.
Project Initiation (Project Identification)
Preliminary Investigation (Feasibility Study)
When should the Project Initiation
begin??
when someone in the organization identifies that a need to improve an existing system or new system is needed to improve business operation
how did the ideas for the Project Initiation
come?
Most of the ideas come from outside the IT department, such as marketing, accounting and ect…, come as form of system request
what is a system request?
A formal way of asking for assistance from the information systems department
System Request Might propose:x
enhancements for an existing system,
the correction of problems
the development of an entire new information system
Systems Request Forms 6
Streamlines the request process
Ensures consistency
Easy to understand
Includes clear instructions
Indicates what supporting documents are needed
Most companies use online system request forms that users submitted electronically
why large companies use Systems Review Committee
Most large companies use a systems review committee to evaluate systems request
Disadvantages of Systems Review Committee
Action on requests must wait until the committee meets
Members might favor projects requested by their own departments
Internal political differences could delay important decisions
Reason for System Request
Improve service
Better performance
more information
stringer control
reduce cost
Factors affecting System Request internal
Top management executives
user control
IT department
Existing System
Factors affecting System Request external
Software and hardware vendors
technology
suppliers
customers
competitors
the economy
government
Problem Statement
After understanding the project initiation, the system analyst has to defines the problems and objectives of the system.
These will form the foundation of determining what needs to be accomplished by the system
what is the preliminary Investigation
A systems analyst conducts a preliminary investigation to study the systems request and recommend specific action
what is the purpose of Preliminary Investigation
gather enough information to determine if the information or problems specified in the systems request warrant
What information does an analyst gather during the preliminary investigation?
The analyst gather facts about the problem or opportunity, project scope and constraints, project benefits and estimated development time and cost.
however, the end of this step the report to the management
Defining Project Objectives
After the objectives are stated, the relative importance of the issues or objectives must be determined.
The identification of the most critical objectives is best done by users
Project Objectives
Problem Statements or issues are followed by a series of objectives, or goals, that match the issues point by point. Issues are the current situation; objectives are the desired situation.
The objectives may be very specific or worded using a general statement.
A constraint can involve hardware, software, time, policy, law, or cost. For example:
The system must operate with existing hardware, that is a constraint that affects potential solutions.
The order entry system must accept input from 15 remote sites.
The human resources information system must produce statistics on hiring practices.
The new Web site must be operating by March 1.
what is Determining the project scope
defining the specific boundaries, or extent, of the project
Boundaries of the preliminary investigation.
examples of the project scope Very general
Payroll is not being produced accurately.
The project scope is to modify the accounts receivable system.
examples of the project scope Very specific:
Overtime pay is not being calculated correctly for production workers on the second shift at the Yorktown plant.
The project scope is to allow customers to inquire online about account balances and recent transactions.
Keys to project success
Satisfy business requirements
Meet users’ needs
Stay within budget
Be completed on time
Some reasons for project failure 11
Unclear requirements, targets, or scope
Shortcuts or sloppy work
Poor design choices
Insufficient testing or test procedures
Lack of software change control
Changes in culture, funding or objectives
Unrealistic cost estimates
Poor monitoring and control of progress
Inadequate reaction to early signs of problems
Failure to recognize activity independencies
Personality conflicts and employee turnover
