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;
62 Cards in this Set
- Front
- Back
|
Legacy system |
an old system that is fast approaching or beyond the end of it's useful life within an organization |
|
|
Conversion |
the process of transferring information from a legacy system to a new system |
|
|
Software customization |
modifies software to meet specific user or business requirements |
|
|
off-the-shelf application software |
supports general business processes and does not require any specific software customization to meet the organization's needs |
|
|
Systems development life cycle (SDLC) |
The overall process for developing information systems |
|
|
Phase 1: Planning |
establishes high-level plan of the intended project and determines project goals |
|
|
Change agent |
person or event that is a catalyst for implementing major changes for a system to meet business changes |
|
|
Project |
temporary activity a company undertakes to create a unique product, service or result |
|
|
Project management |
the application of knowledge, skills, tools and techniques to project actives to meet project requirements |
|
|
Project manager |
An individual who is an expert at project planning and management, defines and developed the project plan, and tracks the plan to ensure it's completed on time and budget |
|
|
Project scope |
describes business need and justification, requirements, and current boundaries for the project |
|
|
Project plan |
formal, approved document that manages and controls the entire project |
|
|
Phase 2: Analysis |
analyzes its end-user business requirements and refines project goals into defined functions and operations of the intended system |
|
|
Business requirements |
specific business requests the system must meet to be successful. (Business requirements drive entire system development) |
|
|
Requirements management |
process of managing changes to the business requires throughout the project |
|
|
Requirements definition document |
prioritizes all business requirements by order of importance |
|
|
Sign-offs |
Users' actual signatures indicating they approve all of the business requirements |
|
|
Phase 3: Design |
Establishes descriptions of the desired features and operations of the system, including screen layouts, business rules, process diagrams, pseudo code and other documentation |
|
|
Phase 4: Development |
Takes all detailed design documents and transforms them into the actual system |
|
|
Software entineering |
Disciplined approach for constructing information systems through the use of common methods, techniques or tools |
|
|
Computer-aided software engineering (CASE) |
tools that provide automated support for the development of the system |
|
|
Control Objects for Information and Related technology (COBIT) |
set of best practices that help an organization to maximize benefits of an information system |
|
|
Scripting language |
programming method that provides interactive modules |
|
|
Object-oriented languages |
Data and corresponding processes into objects |
|
|
Forth-generation languages (4FL) |
programming languages that look similar to human languages |
|
|
Testing phase |
brings all project pieces together into special testing environment to eliminate errors an bugs to ensure system meets all business requirements |
|
|
Bugs |
Defects in a code of an information system |
|
|
Test conditions |
Steps the system must perform along with the expected result of each step |
|
|
Phase 6: Implementation |
Organization place system into production so users can perform actual business operations with it |
|
|
User documentation |
Highlights how to use the system and how to troubleshoot issues |
|
|
Online training |
Where employees complete training on their own time via Internet or CD |
|
|
Workshop Training |
held in a classroom lead by an instructor |
|
|
Help desk |
Group of people who respond to users' questions |
|
|
Maintenance phase |
Organization performs changes, corrections, additions an upgrades to ensure system continues to meet business goals |
|
|
Corrective maintenance |
Makes system changes to repair design flaws |
|
|
Preventive maintenance |
makes system changes to reduce chance of future system fail |
|
|
Methodology |
set of policies, procedures, standards, processes, practices, tools, techniques, and tasks that people apply to technical and management challenges |
|
|
Waterfall methodology |
A sequence of phases in which the output of each phase becomes the input for the next |
|
|
Prototyping |
Modern design approach where designers and system users use an iterative approach to building the system |
|
|
Discover prototyping |
builds a small-sclae representation or working model of the system to ensure it meets all the suer and business requiremens |
|
|
Iterative development |
Series of small projects |
|
|
Agile methodoloyg |
aims for customer satisfaction through early and continuous deliver of useful software components developed by an iterative process using the bare minimum requirements |
|
|
Rapid application development (RAD) methodology |
extensive user involvement in the rapid an evolutional construction of working prototypes of a system to accelerate system developing process |
|
|
Extreme Programming (XP) methodology |
Breaks project into four phases, and developers cannot continue to the next phase until the previous phase is complete |
|
|
Rational unified process (RUP) methodology |
owned by IBM, provides framework for breaking down the development of software into four "gates" |
|
|
Gate one: inception |
ensures all stakeholders have shared understanding of the proposed system and what it will do |
|
|
Gate two: elaboration |
expands on agreed details, including ability to provide architecture to support and buildit |
|
|
Gate three: construction |
Includes building and developing the product |
|
|
Gate four: transition |
questions address ownership of system and training of key personnel |
|
|
Scrum methodology |
small teams to produce small pieces of software using series of "sprints" |
|
|
Tangible benefits |
easy to quantify and typically measure to determine the success or failure of a project |
|
|
Feasability |
measure of tangible and intangible benefits of an information system |
|
|
Triple contraint |
time, cost, scope |
|
|
Kill switch |
trigger that enables a project manager to close the project before completion |
|
|
PERT (program evaluation and review technique) chart |
graphical network model that depicts projects tasks and relationships between them |
|
|
Dependency |
logical relationship that exists between the project tasks, or between project task and milestone |
|
|
Critical path |
estimates shortest path through project ensuring all critical tasks are completed from start to finish |
|
|
Gantt chart |
Bar chart that lists project tasks and project's time frame |
|
|
In-Sourcing (in-house development) |
professional expertise within an organization to develop and maintain it's information technology systems |
|
|
outsourcing |
arrangement by which one organization provides service for another organization that chooses not to perform them in-house |
|
|
Onshore outsourcing vs Nearshore outsourcing vs Offshore outsourcing |
Onshore: within the same country Nearshore: boarder sharing countries Offshore: geographically far away |
|
|
Two challenges of outsourcing |
Length of contract Threat to competitive advantage Loss of confidentiality |
