Term
Define information systems analysis and design. |
|
Definition
System analysis and design is the complex organizational process whereby computer-based information systems are developed and operated. |
|
|
Term
Discuss the modern approach to system analysis and design that combines both process and data views of systems. |
|
Definition
Process orientation:
- Focuses on what the system is suppose to do.
- Provides a less stable design because business processes change faster than do the data an organization uses.
- Data files are designed for specific applications.
- Leads to much uncontrolled data redundancy.
Data orientation:
- Focuses on the data the system needs to operate.
- Data files are designed for the whole enterprise
- Application independence
|
|
|
Term
Describe the role of the systems analyst in information systems development. |
|
Definition
Systems analysts act as the liaisons between business users on one hand and technical personnel on the other. The must posses analytical, technical, managerial, and interpersonal skills to succeed. |
|
|
Term
Describe three types of information systems: TPS(Transaction Processing Systems), MIS (Management Information Systems), and DSS (Decision Support System). |
|
Definition
TPS automate the handling of data about business activities such as customer purchase transactions; MIS convert data from a TPS into meaninful information such as a sales summary report; and DSS access data and model to support organizational decision making such as comparing alternative investment options. |
|
|
Term
Describe the information systems development life cycle (SDLC). |
|
Definition
SDLC includes four major phases:
- Systems planning and selection: analysts make detailed road maps of the system development project.
- Systems analysis: analysts work to solve the business problem being studied.
- Systems design: the solution to the problem is built.
- Systems implementation and operation: the system is given to users and kept running.
|
|
|
Term
List alternatives to the SDLC, including a description of the role fo computer-aided software engineering (CASE) tools in systems development. |
|
Definition
The alternative frameworks are:
- Prototyping: analysts build a working model of the system.
- Joint Application Design (JAD): analysts and users meet to solve problems and design system.
- Participatory Design: the emphasis is on the user community.
- Agile Mythologies: focus on adaptive rather than predictive mythologies, on people rather than roles, and on continuous adaption, depending on the situation.
- CASE: represents the use of IT to assist in the systems development process. They include diagramming tools, screen and report design tools and other specialty tools. CASE tools help programmers and analysts do their jobs efficiently and effectively by automating routine tasks.
|
|
|
Term
Agile Methodologies (p.24) |
|
Definition
Agile Methodologies focus on adaptive rather than predictive methodologies, focus on people rather than roles, and a self-adaptive process. |
|
|
Term
Application Software (p.4) |
|
Definition
Also called a system, is designed to support a specific organizational function or process, such as inventory management, payroll, or market analysis. |
|
|
Term
|
Definition
A system has a boundary, within which all of its components are contained and which establishes the limits of a system, separating it from other systems. Components within the boundary can be changed, whereas systems outside the boundary cannot be changed. |
|
|
Term
|
Definition
The extent to which a system performs a single function. |
|
|
Term
|
Definition
Either an irreducible part or an aggregate of parts, also called a subsystem. |
|
|
Term
Computer-aided Software Engineering (CASE) (p.21) |
|
Definition
Refers to automated software tools used by systems analysts to develop information systems. |
|
|
Term
|
Definition
The limit (in terms of capacity, speed, or capabilities) to what a system can do and how it can achieve its purpose within its environment. |
|
|
Term
Interrelated Components (p.7) |
|
Definition
The function of one component is somehow tied to the function of others. |
|
|
Term
Joint Application Design (JAD) (p.22) |
|
Definition
To structure the requirements determination phase of analysis and the review that occurs as part of the design. Users, managers, and system developers are brought together to agree on system requirements and design details. |
|
|
Term
|
Definition
The system's reason for existing. |
|
|
Term
Rapid Application Development (RAD) (p.22) |
|
Definition
To delay producing detailed system design documents until after the user requirements are clear. The prototype serves as the working description of the needs. RAD involves gaining user acceptance of the interface and developing key system capabilities as quickly as possible. |
|
|
Term
|
Definition
An integrated and standard database for providing product and tool integration and has been a key factor in enabling CASE to manage large, more complex projects more easily and to seamlessly integrate data across various tools and products. |
|
|
Term
|
Definition
An interrelated set of business procedures (or components) used within one business unit, working together for some purpose. |
|
|
Term
|
Definition
SDLC phase where the analyst thoroughly studies the organization's current procedures and the information systems used to perform tasks such as general ledge, shipping, order entry, machine scheduling, and payroll. |
|
|
Term
|
Definition
The primary role of a systems analyst is to study the problems and needs of an organization in order to determine how people, methods, and information technology can best be combined to bring about improvements in the organization. A systems analyst helps system users and other business managers define their requirements for new or enhanced information services. |
|
|
Term
|
Definition
Phase 3 of the SDLC where analysts convert the description of the recommended alternative solution into logical and then physical system specifications. |
|
|
Term
Systems Development Life Cycle (SDLC) (p.15) |
|
Definition
Common methodology for systems development in many organizations. It marks the phases or steps of information systems development. The steps include (1) planning and selection, (2) analysis, (3) design, and (4) implementation and operation. |
|
|
Term
Systems Development Methodology (p.15) |
|
Definition
Standard set of steps used by organizations to develop and support their information systems. |
|
|
Term
Systems Implementation and Operation (p.18) |
|
Definition
Final phase of SLDC. During systems implementation and operation, you turn system specifications into a working system that is tested and then put in use. Implementation includes coding, testing, and installation. During operation, programmers make the changes that users ask for and modify the system to reflect changing business conditions. There changes are necessary to keep the system running and useful. |
|
|
Term
Systems Planning and Selection (p.17) |
|
Definition
Systems planning and selection has two activities. First someone identifies the need for a new or enhanced system. The second part is to investigate the system and determine the proposed system's scope. |
|
|
Term
|
Definition
A planned undertaking of a series of related activities to reach an objective that has a beginning and an end. |
|
|
Term
|
Definition
A short (typically one page), high-level document prepared for the customer that describes what the project will deliver and outlines many of the key elements of the project. Often includes: project title and date of authorization, project manager name and contact information, customer name and contact information, project start and completion dates, key stakeholders, project roles, and responsibilities, project objectives and description, key assumptions or approach, and signature section for key stakeholders. |
|
|
Term
Project Initiation (p.53) |
|
Definition
Project manager performs several activities that assess the size, scope, and complexity of the project, and establishes procedures to support subsequent activities. Activities include: establishing the project initiation team, establishing a relationship with the customer, establishing the project initiation plan, establishing management procedures, establishing the project management environment and project workbook, and developing the project charter. |
|
|
Term
Project Management (p.52) |
|
Definition
Project management process involves four phases: initiating, planning, executing, and closing down the project. |
|
|
Term
|
Definition
A systems analyst with a diverse set of skills- management, leadership, technical, conflict management, and customer relationship - who is responsible for initiating, planning, executing, and closing down the project. |
|
|
Term
|
Definition
A repository of all project correspondence, inputs, outputs, deliverables, procedures, and standards established by the project team. |
|
|
Term
Application Service Provider (p.36) |
|
Definition
Third-party providers that host applications where users pay on a per-use basis or they license the software, typically month to month. The provider buys, installs, maintains, and upgrades the applications. |
|
|
Term
Enterprise Resource Planning (ERP) System (p.35) |
|
Definition
ERP software solutions consist of a series of integrated modules. Each module supports an individual traditional business function, such as accounting, distribution, manufacturing, and human resources. The modules are integrated to focus on business processes rather than on business functional areas. |
|
|
Term
Managed Service Provider(MSP) (p.36) |
|
Definition
An MSP can offer customized applications and also include business processes, engineering, security, and maintenance. MSP customers can pay based on a monthly charge or a per user basis and like ASPs, MSPs can provide services from outside a company's network. |
|
|
Term
|
Definition
When another organization develops or runs a computer application for your organization. It includes a spectrum of working arrangements. |
|
|
Term
Request for Proposal(RFP) (p.40) |
|
Definition
An RFP will ask the vendor to propose hardware and system software that will meet the requirements of your new system. |
|
|
Term
|
Definition
The use of previously written software resources in new applications. |
|
|
Term
|
Definition
Constructive Cost Model uses parameters that were derived from prior projects of differing complexity. COCOMO uses these different parameters to predict human resource requirements for basic, intermediate, and complex systems. |
|
|
Term
|
Definition
Refers to a sequence of task activities whose order and durations directly affect the completion date of a project. The critical path represents the shortest time in which a project can be completed. Any activity in the critical path that is delayed in completion delays the entire project. |
|
|
Term
Critical Path Scheduling (p.70) |
|
Definition
A technique such as a network diagram used for controlling resources. |
|
|
Term
|
Definition
|
|
Term
|
Definition
Study to determine whether the information system makes sense for the organization from an economic and operational standpoint. |
|
|
Term
|
Definition
A graphical representation of a project that shows each task as a horizontal bar whose length is proportional to its time for completion. |
|
|
Term
|
Definition
A graphical depiction of project tasks and their interrelationships. |
|
|
Term
PERT(Program Evaluation Review Technique) (p.70) |
|
Definition
Technique that uses optimistic, pessimistic, and realistic time estimates to calculate to calculate the expected time for a particular task. |
|
|
Term
|
Definition
To bring the project to an end. |
|
|
Term
|
Definition
Puts the baseline project plan into action. It occurs primarily during the analysis, design, and implementation phases. |
|
|
Term
|
Definition
Involves defining clear, discrete activities and the work needed to complete each activity within a single project. |
|
|
Term
|
Definition
Any person, group of people, piece of equipment, or material used in accomplishing an activity. |
|
|
Term
|
Definition
|
|
Term
Work Breakdown Structure(WBS (p.58) |
|
Definition
|
|