Chapter 10: Building Successful Information Systems Flashcards
Why do Business Information Systems often fail (5)
- incomplete requirements
- failure to include all members
- lack of clarity
- lack of communication
- unrelated goals and expectations etc
System Development Life Cycle SDLC Phases (5)
- Planning
- Requirements gathering and analysis
- Decision
- Implementation
- Maintenance
System Development Life Cycle 1. Planning
define internal/external problems of organization
analyst or team assess current and future needs of organization: Planning 4 W’s
why is it designed
who will be using it
when will it be operational
what are its capabilities
Planning - Task Force Formation Team (who is on it)
representatives from different departments, systems analyst, stakeholders, and top management
Internal users
external users
employee use system regularly
customers, contractors, suppliers, partners
Boundary Spanning Roles (2)
- Link internal resources and external info sources
- speak languages of technology and business
Feasibility studies
measure of beneficial/practical of new IS 4 Org
Feasibility studies 5 dimensions ETOSL
Economic
Technical
operational
scheduling
legal
Tangible Costs
quantifiable costs relating to identifiable source
Intangible Costs
unquantifiable costs related to identity source
Tangible Benefit example
Intangible Benefit example
Benefits quantified in terms of money
difficult to identify and quantify in terms of dollar amounts
Feasibility studies - technical
technology used in the system, is it available and feasible
Feasibility studies - operational
how well new IST solution will work,resistance? support?
Feasibility studies - scheduling
system schedule for implementation and progression, deadlines, potential set backs or losses
Feasibility studies - legal
legal issues, restrictions, political consequences , conflicts with government
Requirements Gathering Analysis
Gathering requirements via interviews, surveys, observations, brainstroming
Output of analysis
requirements doc, data flow, flowchart, conceptual models
Phase 3: Decision
Analyst choose solution most realistic and yields highest payoff
Output of Phase 3:
document with exact specifications for implementation
Phase 4: Implementation
Solution from paper to action
Implementation Tasks for IS (4-6)
employment, schedule, plan and design, code/test, security measure and safeguard
Request for Proposal / Information
document with specifications on equipment, supplies, services, vendors
Critical Path
longest path to complete the project
Gantt Chart for implementation
Implementation by month timeline and category
Phase 5: Maintenance
Information Systems is in operation, review, enhance, modify and test.
collect performance data and if meet expectations
Service Oriented Architecture
software and system development methodology focuses on development and reuse of small self contained codes to meet software needs
High Modularity Required
Reusable Blocks of Codes
Agile Methodologies
communication and feedback
Rapid Application Development
continuous interaction between user involvement and design
Rapid Application Development Process cycle rddt
repeat, design, development, and test
Extreme Programming
project in smaller functions and developed in step by step functions
blocked steps
next phase or step cannot occur till previous step completed
pair programming
find error before entire program written
Agile and task divison
able to move quickly and easily
short phases of work and frequent reassessment and adaptation
Agile methods drawbacks
bugs accumulate, team members change, requirements change
