Term
|
Definition
| In systems development the result of each phase is a |
|
|
Term
|
Definition
| Early working version of an information system. |
|
|
Term
|
Definition
| IBM internet-based systems development system |
|
|
Term
|
Definition
| Design that can expand to meet new business requirements |
|
|
Term
|
Definition
| Analysis method that tests variables before making a decision |
|
|
Term
|
Definition
| Manages the hardware components |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Common way to describe businesses who depend on the internet |
|
|
Term
| Systems analysis and design |
|
Definition
| Step-by-Step process for developing information systems |
|
|
Term
|
Definition
| Provide job-related information support to users |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Combines Technology, people and data into a system |
|
|
Term
|
Definition
| used to represent a company's operations and information needs |
|
|
Term
|
Definition
| System designed for use by a specific business or industry |
|
|
Term
|
Definition
| set of beliefs and attitudes that define a company |
|
|
Term
|
Definition
| plan that defines the company's overall mission and goals |
|
|
Term
|
Definition
| physical layer of an information system |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Team who plan, develop, and maintain information systems. |
|
|
Term
|
Definition
| describes the information that a system must provide |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Microsoft Internet-Based systems development solution is (dot) |
|
|
Term
|
Definition
| people who interact with an information system |
|
|
Term
|
Definition
| collection of similar objects |
|
|
Term
|
Definition
| defining the specific boundaries of a project |
|
|
Term
|
Definition
| process of controlling risks to minimize their impact |
|
|
Term
|
Definition
| inventory system to provide the right product on time |
|
|
Term
|
Definition
| an example would be "budget increase was turned down" |
|
|
Term
|
Definition
| steps used to accomplish the company's mission |
|
|
Term
|
Definition
| method of obtaining information from a large group of users |
|
|
Term
|
Definition
| a proposed system used effectively once developed |
|
|
Term
|
Definition
| report section where to attach supporting information |
|
|
Term
|
Definition
| an event that could affect a project negatively |
|
|
Term
|
Definition
| refers to the technical resources needed for the new system |
|
|
Term
|
Definition
| reasons or justifications for a proposal |
|
|
Term
|
Definition
| coding the data to keep it safe from unauthorized users |
|
|
Term
|
Definition
| constraint due to an outside force |
|
|
Term
|
Definition
| constraint that must be met as soon as a system is developed |
|
|
Term
|
Definition
| a company may break down a goal into shorter term - |
|
|
Term
|
Definition
| report featuring anticipated benefits |
|
|
Term
| preliminary investigation |
|
Definition
| a systems request is studied and an action recommended |
|
|
Term
|
Definition
| report section featuring results of preliminary investigation |
|
|
Term
|
Definition
| Examines strengths, weaknesses, opportunities and threats |
|
|
Term
|
Definition
| describes a company for its stakeholders |
|
|
Term
|
Definition
| an example would be "aggressive new Web competition" |
|
|
Term
|
Definition
| Ability to identify a person by retina scan |
|
|
Term
|
Definition
| Process of identifying long-term goals and strategies |
|
|
Term
|
Definition
| constraint due to a requirement within |
|
|
Term
|
Definition
| represents the chance that the risk will happen |
|
|
Term
|
Definition
| Widely-used tool for visualizing and prioritizing issues |
|
|
Term
|
Definition
| Widely-used tool for visualizing and prioritizing issues |
|
|
Term
|
Definition
| when is absolutely essential to meet a constraint |
|
|
Term
|
Definition
| Constraint needed at some future time |
|
|
Term
|
Definition
| Another term for questionnaire |
|
|
Term
|
Definition
| controls that safeguard and protect the system |
|
|
Term
|
Definition
| feature that must be included in the system |
|
|
Term
|
Definition
| system characteristics such as speed and volume |
|
|
Term
|
Definition
| physical location visit used to observe system in use |
|
|
Term
|
Definition
| vertical bar that shows distribution sampling results |
|
|
Term
|
Definition
| changeover to a new system phase |
|
|
Term
|
Definition
| system documentation to help understand system |
|
|
Term
|
Definition
| document containing standardized questions |
|
|
Term
|
Definition
|
|
Term
|
Definition
| when people have more influence than job title indicates |
|
|
Term
|
Definition
| Visually represents interaction between user and system |
|
|
Term
|
Definition
| shows the timing of interactions between objects |
|
|
Term
|
Definition
| questions that suggest or favor a particular reply |
|
|
Term
|
Definition
| includes word processing and spreadsheet programs |
|
|
Term
|
Definition
| fact-finding technique to obtain information |
|
|
Term
| unified modeling language |
|
Definition
| method of documenting software system design |
|
|
Term
|
Definition
| logical rules that transform data into valuable information |
|
|
Term
|
Definition
| process of collecting a variety of document samples |
|
|
Term
|
Definition
| ability to expand to meet new needs and volumes |
|
|
Term
|
Definition
| questions that limit or restrict response |
|
|
Term
|
Definition
| program and application development phase |
|
|
Term
|
Definition
| a "use case diagram" where user has specific role |
|
|
Term
|
Definition
| electronic or printed information produced by system |
|
|
Term
|
Definition
| planned meeting to obtain information from a person |
|
|
Term
|
Definition
| necessary data that enters the system |
|
|
