Term
| Systems analysis and design |
|
Definition
| Using an organized sequence of activities to study a problem or opportunity using systems thinking. |
|
|
Term
|
Definition
| Trying to recognize systems and the new interrelationships and components of systems in any situation. |
|
|
Term
|
Definition
| Evaluating the success of a solution after it has been implemented. |
|
|
Term
|
Definition
| Your evaluation shows that benefits outweigh costs for a proposed system. |
|
|
Term
|
Definition
| The costs of acquiring computer hardware, software, and specialists. |
|
|
Term
|
Definition
| Loss of customer goodwill cause by errors in a new system. |
|
|
Term
|
Definition
| Increase in profits caused by a new system. |
|
|
Term
|
Definition
| Improved employee morale caused by efficiency and effectiveness of a new system. |
|
|
Term
|
Definition
| A multi-step process to conceive, design, and implement an information system. |
|
|
Term
|
Definition
| A diagram or blueprint of a system that shows what it does without regard to how it does it. |
|
|
Term
|
Definition
| Determines the organizational, economic, technical, and operational feasibility of a proposed information system. |
|
|
Term
|
Definition
| The goal of this feasibility analysis category is to determine whether the proposed system will provide positive economic benefits. |
|
|
Term
|
Definition
| Reliable hardware and software available to implement a proposed system. |
|
|
Term
| Legal/political feasibility |
|
Definition
| Determining whether or not any copyright or patent infringements may exist as the result of a new system. |
|
|
Term
| Human factors feasibility |
|
Definition
| Do we have the right people to operate the new system? |
|
|
Term
|
Definition
| Studying in detail the information needs of users and any information systems presently used and then developing a system to correct a problem or improve operations. |
|
|
Term
|
Definition
| A detailed description of user information needs and the input, processing, output, storage, and control capabilities required to meet those needs. |
|
|
Term
|
Definition
| Systems design should focus on developing user-friendly input and output methods for a system. |
|
|
Term
|
Definition
| A detailed description of the hardware, software, people, network, and data resources and information products required by a proposed system. |
|
|
Term
| Systems development life cycle |
|
Definition
| Acquiring hardware and software, testing and documenting a proposed system, and training people to use it. |
|
|
Term
|
Definition
| Making improvements to an operational system. |
|
|
Term
|
Definition
| An interactive and iterative process of developing and refining information system prototypes. |
|
|
Term
|
Definition
| Managers and business specialists can develop their own e-business applications. |
|
|
Term
|
Definition
| Correcting, converting, filtering, consolidating, and organizing data when replacing an old system. |
|
|
Term
|
Definition
| Operate in parallel with the old system, use a test site, switch in stages, or cut over immediately to a new system. |
|
|
Term
|
Definition
| Checking whether hardware and software work properly for end users. |
|
|
Term
|
Definition
| A user manual communicates the design and operating procedures of a system. |
|
|
Term
| Post-implementation review |
|
Definition
| Keeping an IS project on time and within its budget would be a major goal. |
|
|
