Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
69 Cards in this Set
- Front
- Back
3 Approaches to Systems Development:
_________-Oriented Approach _________-Oriented Approach __________-Oriented Approach |
Process
Data Object Data |
|
3 Approaches to Systems Development:
_________-Oriented Approach _________-Oriented Approach __________-Oriented Approach |
Process
Data Object Data |
|
Separating Data and Processes that Handle Data
|
Process-Oriented Approach
|
|
Combines data and processes
|
Object-Oriented Approach
|
|
Flat File Based systems
|
Process Oriented Approach
|
|
Relational database based systems
|
Data Oriented Approach
|
|
Object-Oriented Database systems
|
Object-Oriented Approach
|
|
A method used by companies to create and maintain computer-based systems that perform basic business functions
|
Information Systems Analysis & Design
|
|
A ________ approach must be used in order to ensure success
|
structured
|
|
________________, __________________, and __________ are the Three Key Components of an Information System
|
Data
Data Flows Processing Logic |
|
raw facts that describe people, objects and events in an organization
|
Data
|
|
Groups of data that move and flow through the system
|
Data Flows
|
|
Steps that transform data and events that trigger the steps
|
Processing Logic
|
|
Systems that perform and record daily routine transactions necessary for business
|
Transaction Processing Systems (TPS)
|
|
Point of Sales (POS) system in retail store
|
Transaction Processing Systems (TPS)
|
|
Systems that serve planning, control and decision-making through routine summary and reports
Serve managers primarily interested in weekly, monthly and yearly results |
Management Information Systems (MIS)
|
|
Systems that combine data, models and analysis tools for non-routine decision-making
|
Decision-support Systems (DSS)
|
|
Systems that support non-routine decision-making through advanced graphics and communications
|
Executive Support Systems (ESS)
|
|
3 Levels of information systems
|
1. Strategic Level Systems
2. Management Level Systems 3. Operational Level Systems |
|
Phases of the SDLC
|
Planning
Analysis Design Implementation Maintenance |
|
Identify opportunity
Opportunity and problems Analyze the feasibility Technical, economic, and organizational Arrange for the resources Time, cost and people Develop workplan Project management Scope management Deliverables: feasibility analysis and workplan |
Planning (why)
|
|
Study of current procedures and information systems
Gather Requirements Recommend an alternative solution |
Analysis (who, what, when and where)
|
|
system proposal
|
Analysis Deliverable
|
|
system specification
|
Design (how) Deliverable
|
|
Construction
Code and testing Installation Cutover, parallel conversion, and phased parallel conversion Training |
Implementation
|
|
System changed to reflect changing conditions
System obsolescence |
Maintenance
|
|
Advantages of the SDLC
|
Structured
Less changes – less cost |
|
Disadvantages of the SDLC
|
Lacks flexibility to change
Locks in users’ requirements too early Limited user involvement Long development period |
|
Alternative methodology to System Development
|
Rapid Application Development (RAD)
|
|
An iterative process of systems development in which requirements are converted to a working system (a scaled-down version)
|
Prototyping
|
|
Users, Managers and Analysts work together
System requirements are reviewed Structured meetings |
Joint Application Design (JAD)
|
|
Software tools that provide automated support for phases of the systems development process
|
Computer-aided software engineering (CASE) tools
|
|
Used at early phases: diagramming, screen design and generation
|
Upper CASE
|
|
Focus on implementation phase: code and test generator
|
Lower CASE
|
|
Support the entire SDLC
|
Integrated CASE
|
|
An object-oriented systems development methodology
|
Rational Unified Process (RUP)
|
|
4 phases of Rational Unified Process
|
Inception
Elaboration Construction Transistion |
|
define the scope, determine the feasibility and requirement
|
Inception
|
|
analysis and design
|
Elaboration
|
|
software is coded, tested and documented
|
construction
|
|
system is developed and users are trained and supported
|
Transition
|
|
The practice of turning over responsibility for some or all of an organization's information systems applications and operations to an outside firm
|
Outsourcing
|
|
_______ is the leader in software sales and services
|
IBM
|
|
___________ is the leader in prepackaged software production.
|
Microsoft
|
|
Firms like _______ and _______ are leading custom software producers.
|
Accenture, EDS
|
|
systems that integrate individual traditional business functions into modules enabling a single seamless transaction to cut across functional boundaries.
|
Enterprise Resource Planning (ERP)
|
|
_________ is the leading vendor of ERP systems
|
SAP AG
|
|
ex of ERP
|
SAP AG
Oracle/PeopleSoft JD Edwards |
|
an organization that providing software that can be rented by other companies over a Web or a private network, typically on a per-use or license basis
|
Application Service Providers
ex. Microsoft |
|
_______________ may be the most important aspect of systems development.
|
Project management
|
|
A standard form for requesting or proposing systems development work within an organization
|
System Service Request (SSR)
|
|
A study that determines whether a requested system makes economic and operational sense for an organization
|
Feasibility study
|
|
A planned undertaking of related activities to reach an objective that has a beginning and an end
|
Project
|
|
A controlled process of initiating, planning, executing, and closing down a project
|
Project management
|
|
Systems analyst with management and leadership skills responsible for leading project initiation, planning, execution, and closedown
|
Project Manager
|
|
The end product of an SDLC phase
|
Deliverable
|
|
Phases of Project Management Process
|
Phase 1: Initiation
Phase 2: Planning Phase 3: Execution Phase 4: Closedown |
|
Assess size, scope and complexity, and establish procedures.
|
Project Initiation
|
|
Define clear, discrete activities and the work needed to complete each activity
|
Project Planning
|
|
“Contract” between the IS staff and the customer regarding deliverables and time estimates for a system development project
|
Statement of Work (SOW)
|
|
Contains estimates of scope, benefits, schedules, costs, risks, and resource requirements
|
The Baseline Project Plan (BPP)
|
|
Cost-benefit analysis outlining planned expenses and revenues
|
Preliminary Budget
|
|
Division of project into manageable and logically ordered tasks and subtasks
|
Work Breakdown Structure (WBS)
|
|
horizontal bars represent task durations
|
Gantt chart
|
|
boxes and links represent task dependencies
|
Network Diagram
|
|
Plans created in prior phases are put into action.
|
Project Execution
|
|
Bring the project to an end.
|
Project Closedown
|
|
Show task durations.
Show time overlap. Show slack time in duration. |
Gantt charts
|
|
Show task dependencies.
Do not show time overlap, but show parallelism. Show slack time in boxes. |
Network diagrams
|