1/103
Looks like no tags are added yet.
Conversion
Process of transferring information from a legacy system to a new system
Legacy system
Old system that is fast approaching or beyond the end of its useful life within an organization
Systems development life cycle (SDLC)
Overall process for developing information systems, from planning and analysis through implementation and maintenance
Planning phase
Establishes a high level plan of the intended project and determines project goals
Brainstorming
Technique for generating ideas by encouraging participants to offer as many ideas as possible without immediate analysis
Change agent
Person or event that is the 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
Application of knowledge, skills, tools, and techniques to project activities to meet project requirements
Project plan
Formal, approved document that manages and controls the entire project
Project manager
Individual expert in project planning and management who defines, develops, and tracks the project plan
Project scope
Describes the business need, problem to solve, justification, requirements, and current boundaries for the project
Analysis phase
The firm analyzes end user business requirements and refines project goals into defined functions and operations
Business requirements
Specific business requests that the system must meet to be successful
Requirements management
Process of managing changes to the business requirements throughout the project
Requirements definition document
Prioritizes all of the business requirements by order of importance to the company
Sign off
Users' actual signatures indicating they approve all of the business requirements
Process modeling
Involves graphically representing processes that capture, manipulate, store, and distribute information
Data flow diagram (DFD)
Illustrates the movement of information between external entities and the processes and data stores within a system
Design phase
Establishes descriptions of desired features and operations of the system, including screen layouts, business rules, and pseudocode
Figma
Cloud based design and prototyping tool that allows users to create, collaborate, and iterate on digital designs in real time
Development phase
Transforms all detailed design documents from the design phase into the actual physical system
Coders
People who write the programs that operate computers
Software engineering
Disciplined approach for constructing information systems through common methods, techniques, or tools
Programming language
Unique set of keywords along with special syntax for organizing program instructions
Fourth generation languages
Programming languages that look similar to human languages
Low code and no code
Software development approaches that aim to simplify creating applications by reducing manual coding
Technical review (peer review)
Meeting where an independent team of experts provides in depth analysis of project results
Testing phase
Brings project pieces together into a testing environment to eliminate errors and verify business requirements
Bugs
Defects in the code of an information system
Test conditions
Details the steps the system must perform along with the expected result of each step
Alpha testing
Assesses if the entire system meets the design requirements of the users
Development testing
Tests the system to ensure it is bug free
Integration testing
Verifies that separate systems can work together, passing data back and forth correctly
System testing
Verifies that units or pieces of code function correctly when integrated
User acceptance testing (UAT)
Determines if the system satisfies the user and business requirements
Unit testing
Tests individual units or pieces of code for a system
Implementation phase
Organization places the system into production so users can perform actual business operations
Parallel implementation
Uses both legacy and new systems until all users verify that the new system functions correctly
Plunge implementation
Discards the legacy system and immediately migrates all users to the new system
Pilot implementation
Assigns a small group to use the new system until verified, then migrates remaining users
Phased implementation
Installs the new system in phases by department until verified
Online training
Runs over the internet and employees complete it on their own time at their own pace
Workshop training
Held in a classroom environment and led by an instructor
Help desk
Group of people who respond to users' questions
User documentation
Created for users to highlight how to use the system and troubleshoot issues
Maintenance phase
Organization performs changes, corrections, additions, and upgrades to ensure system continues to meet goals
Corrective maintenance
Makes system changes to repair design flaws, coding errors, or implementation issues
Preventive maintenance
Makes system changes to reduce the chance of future system failure
Internal report
Presents data distributed inside the organization intended for employees
Detailed internal report
Presents information with little or no filtering or restrictions of the data
Summary internal report
Organizes and categorizes data for managerial perusal
Exception report
Highlights situations occurring outside of the normal operating range for a condition or standard
Information system control report
Ensures reliability of information via policies, physical implementation, access restrictions, or record keeping
Information system audit report
Assesses a company's information system to determine necessary changes and ensure availability, confidentiality, and integrity
Post implementation report
Presents a formal report or audit of a project after it is up and running
Methodology
Set of policies, procedures, standards, processes, practices, tools, and tasks applied to technical challenges
Waterfall methodology
Sequence of phases in which output of each phase becomes input for the next; inflexible and expensive
Prototyping
Modern design approach by which designers and users use an iterative approach in building the system
Iterative development
Consists of a series of tiny projects
Agile methodology
Aims for customer satisfaction through early and continuous delivery of useful software components using iterative process
Minimum viable product (MVP)
Version of a product developed with the minimum features required to meet core needs
Rapid application development (RAD)
Emphasizes extensive user involvement in the rapid construction of working prototypes
Extreme programming (XP)
Breaks a project into four phases where developers cannot continue until the previous phase is complete
Scrum methodology
Uses small teams to produce small pieces of software using 30 day sprints
RUP methodology
Framework owned by IBM for breaking down software development into four gates
Tangible benefits
Easy to quantify and typically measured to determine project success
Intangible benefits
Difficult to quantify or measure, such as improved decision making or morale
Feasibility
Measure of the tangible and intangible benefits of an information system
Economic feasibility
Measures the cost effectiveness of a project
Operational feasibility
Measures how well a solution meets identified system requirements to solve problems
Schedule feasibility
Measures the project time frame to ensure timely completion
Technical feasibility
Measures the practicality of a technical solution and resource availability
Political feasibility
Measures how well the solution will be accepted in a given organization
Legal feasibility
Measures how well a solution can be implemented within existing legal and contractual obligations
Program management
Managing a group of related projects designed to achieve a common strategic objective
Portfolio management
Focuses on managing a collection of projects, programs, and other initiatives within an organization
Communication plan
Defines the how, what, when, and who regarding project information flow to stakeholders
Executive sponsor
Person or group who provides the financial resources for the project
Project assumption
Factors considered to be true, real, or certain without proof or demonstration
Project constraint
Specific factors that can limit options, including budget, delivery dates, and available resources
Project deliverable
Any measurable, tangible, verifiable outcome or item produced to complete a project
Project management office (PMO)
Internal department that oversees all organizational projects and educates on techniques
Project milestone
Represents key dates when a certain group of activities must be performed
Project objectives
Quantifiable criteria that must be met for a project to be considered a success
Project requirements document
Defines specifications for the product of the project and is key for controlling scope
Project scope statement
Links the project to the organization's overall business goals
Project stakeholder
Individuals and organizations actively involved in the project or whose interests are affected
Responsibility matrix
Defines project roles and indicates what responsibilities are associated with each role
Status report
Periodic reviews of actual performance versus expected performance
Project charter
Concise written description of the project's intended work
Kill switch
Trigger that enables a project manager to close a project before completion
PERT chart
Graphical network model that depicts a project's tasks and the relationships between them
Critical path
Series of activities that determine the earliest time by which a project can be completed with least slack
Critical path analysis
Project diagramming method used to predict total project duration
Slack
Amount of time an activity may be delayed without delaying a succeeding activity or project finish date
Scope creep
Tendency to permit changes that exceed a project's scope and wreak havoc on schedule and budget
Gantt chart
Simple bar chart listing project tasks vertically against time frame horizontally
Dependency
Logical relationship that exists between project tasks or between a task and a milestone
Work breakdown structure (WBS)
Plan that breaks down a project's goals into the many deliverables required
In sourcing
Uses professional expertise within an organization to develop and maintain IT systems