Chapter 5 Flashcards
People who ultimately benefit from project
Stakeholders
People who will interact with the system regularly
Users
Professional who specializes in analyzing and designing business systems
Systems analysts
Responsible for modifying or developing programs to satisfy user requirements
Programmer
Systems development initiatives (3)
1.Arise from all levels of an organization
2.Can be planned or unplanned
3. Merger and acquisition
Play pivotal role in organization’s continued operations and goal attainment
Mission-critical systems
Factors essential to success of a functional area of an organization
Critical success factors (CSFs)
Traditional Systems Development Life Cycle Stages
- System investigation
- System analysis
- System design
- System implementation
- System maintenance and review
Identifies problems and opportunities and considers them in light of business goals
System investigation
Studies existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement
System analysis
Defines how the information system will do what it must do to obtain the problem’s solution
System design
Creates or acquires various system components detailed in systems design, assembles them, and places new or modified system into operation
System implementation
Ensures the system operates as intended
Modifies the system so that it continues to meet changing business needs
System maintenance and review
Detailed description of what is to be done
Project schedule
Critical date for completion of a major part of the project
Project milestone
Date that the entire project is to be completed and operational
Project deadline
Activities that, if delayed, would delay the entire project
Critical path
Combines logic of systems development life cycle with power of object-oriented modeling and programming
Object-Oriented Systems Development
Feasibility Analysis assesses:
-Technical feasibility
-Economic feasibility
-Legal feasibility
-Operational feasibility
-Schedule feasibility
advantages of traditional system development life cycle
- Formal review at end of each phase allows maximum management control
- Creates considerable system documentation
- produces many intermediate products that can be reviewed to see whether they meet the users needs and conform to standards.
disadvantages of traditional system development life cycle
- documentation is expensive and time consuming to create
- often, user needs go unstated or are misunderstood
