Advanced System Analysis Exam 1 Systems analysis and design

Risk

(1) An event that could affect the project negatively; (2) the impact of an attack multiplied by the likelihood of a vulnerability being exploited.

sequence diagram

A UML diagram that shows the timing of transactions between objects as they occur during system execution.

empowerment

A business practice that places more responsibility and accountability throughout all levels of an organization.

help desk

A centralized resource staffed by IT professionals that provides users with the support they need to do their jobs. A help desk has three main objectives: to show people how to use system resources more effectively, to provide answers to technical or operational questions, and to make users more productive by teaching them how to meet their own information needs.

Scalability

A characteristic of a system, implying that the system can be expanded, modified, or downsized easily to meet the rapidly changing needs of a business enterprise.

system requirement

A characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users.

B2C (business-to-consumer)

A commercial exchange (e.g., products or services) between businesses and consumers conducted over the Internet.

B2B (business-to-business)

A commercial exchange (e.g., products or services) between businesses, typically enabled by the Internet or electronic means.

histogram

A common tool for showing the distribution of questionnaire or sampling results. It takes the form of a vertical bar chart.

service-oriented

A company that primarily offers information or services, or sells goods produced by others.

management information systems (MIS)

A computer-based information system used in business planning, control, decision making, and problem solving.

Certification

A credential an individual earns by demonstrating a certain level of knowledge and skill on a standardized test.

business profile

A definition of a company's overall functions, processes, organization, products, services, customers, suppliers, competitors, constraints, and future direction.

spiral model

A development model with a series of iterations, or revisions, based on user feedback.

survey

A document containing a number of standard questions that can be sent to many individuals. Also called a questionnaire.

questionnaire

A document containing a number of standard questions that can be sent to many individuals. Also called a survey.

mission statement

A document or statement that describes the company for its stakeholders and briefly states the company's overall purpose, products, services, and values.

system requirements document

A document that contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management. It is the end product of the systems analysis phase.

system design specification

A document that presents the complete design for the new information system, along with detailed costs, staffing, and scheduling for completing the next SDLC phase, systems implementation. Also called the technical design specification or the detailed design specification.

brainstorming

A fact-finding technique for gaining information through the use of a small group discussion of a specific problem, opportunity, or issue.

observation

A fact-finding technique where an analyst sees a system in action. Observation allows the verification of statements made in interviews.

business model

A graphical representation of business functions that consist of business processes, such as sales, accounting, and purchasing.

business process model (BPM)

A graphical representation of one or more business processes.

unstructured brainstorming

A group discussion where any participant can speak at any time.

structured brainstorming

A group discussion where each participant speaks when it is his or her turn, or passes.

systems review committee

A group of key managers and users responsible for evaluating systems requests. The term computer resources committee is sometimes also used.

computer resources committee

A group of key managers and users responsible for evaluating systems requests. The term systems review committee is also used.

server farm

A large concentration of servers working together

biometric device

A mechanism used to uniquely identify a person by a retina scan or by mapping a facial pattern.

Zachman Framework for Enterprise Architecture

A model that asks the traditional fact-finding questions in a systems development context.

total cost of ownership (TCO)

A number used in assessing costs, which includes ongoing support and maintenance costs, as well as acquisition costs.

case for action

A part of the preliminary investigation report to management that summarizes project requests and makes specific recommendations.

requirements planning phase

A phase that combines elements of the systems planning and systems analysis phases of the SDLC.

construction phase

A phase that focuses on program and application development tasks similar to the SDLC.

cutover phase

A phase that resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training.

Hawthorne Effect

A phenomenon where employees who know they are being observed are more productive.

interview

A planned meeting during which information is obtained from another person.

deliverable

A polished, final product, suitable for its intended use. End products or deliverables often coincide with the completion of each SDLC phase.

joint application development (JAD)

A popular systems development technique that uses a group of users, managers and IT professionals that work together to gather information, discuss business needs, and define the new system requirements.

knowledge base

A popular systems development technique that uses a group of users, managers, and IT professionals that work together to gather information, discuss business needs, and define the new system requirements.

Scrum

A popular technique for agile project management. Derived from a rugby term. In Scrum, team members play specific roles and interact in intense sessions.

risk response plan

A proactive effort to anticipate a risk and describe an action plan to deal with it. An effective risk response plan can reduce the overall impact by triggering a timely and appropriate action.

enterprise resource planning (ERP)

A process that establishes an enterprise-wide strategy for IT resources. ERP defines a specific architecture, including standards for data, processing, network, and user interface design.

electronic data interchange (EDI)

A process that involves the computer-to-computer transfer of data between companies.

Modeling

A process that produces a graphical representation of a concept or process that systems developers can analyze, test, and modify.

sampling

A process where an analyst collects examples of actual documents, which could include records, reports, or various forms.

encryption

A process where data is coded (converted into unreadable characters) so that only those with the required authorization can access the data (usually via decoding software).

schedule feasibility

A project can be implemented in an acceptable time frame.

constraint

A requirement or a condition that the system must satisfy or an outcome that the system must achieve.

systematic sample

A sample that occurs at a predetermined periodicity. For example, every tenth customer record might be selected as a systematic sample for review.

random sample

A selection taken in a random, unplanned manner. For example, a random sample might be a sample that selects any 20 customers.

stratified sample

A set metric is collected across functional areas. For example, a certain percentage of transactions from every work shift, or five customers from each of four zip codes, could be a stratified sample.

corporate culture

A set of beliefs, rules, traditions, values, and attitudes that define a company and influence its way of doing business.

project scope

A specific determination of a project's boundaries or extent.

business process modeling notation (BPMN)

A standard set of shapes and symbols used to represent events, processes, and workflows in computer-based modeling tools.

fact-finding

A step in the requirements modeling process that involves gathering facts about a systems project using techniques such as interviews, documentation review, observation, questionnaires, sampling, and research.

electronic proof of delivery (EPOD)

A supplier uses RFID tags on each crate, case, or shipping unit to create a digital shipping list to verify receipt of goods.

Operational feasibility

A system that that will be used effectively after it has been developed.

adaptive methods

A systems development method that typically uses a spiral development model, which builds on a series of iterations, to make adapting to changes easier for all stakeholders.

rapid application development (RAD)

A team-based technique that speeds up information systems development and produces a functioning information system. RAD is similar in concept to joint application development (JAD), but goes further by including all phases of the System Development Life Cycle (SDLC).

computer-aided software engineering

A technique that uses powerful programs called CASE tools to provide an overall framework for systems development. The tools support a wide variety of design methodologies, including structured analysis and object-oriented analysis.

fill-in form

A template used to collect data on the Internet or a company intranet.

class

A term used in object-oriented modeling to indicate a collection of similar objects.

personal information manager (PIM)

A tool that helps manage tasks and schedules. Many handheld devices also include this function.

scatter diagram

A tool used by system analysts to graphically show the correlation between two variables. Also called XY chart.

XY Diagram

A tool used by system analysts to graphically show the correlation between two variables. Also called a scatter diagram

functional decomposition diagram (FDD)

A top-down representation of business functions and processes. Also called a structure chart.

supply chain

A traditional systems development technique that uses phases to plan, analyze, design, implement, and support an information system. Processes and data are treated as separate components.

site visit

A trip to a physical location to observe a system in use at another location.

Pareto chart

A vertical bar graph named for a nineteenth-century economist. The bars, which represent various causes of a problem, are arranged in descending order, so the team can focus on the most important causes.

use case diagram

A visual representation that represents the interaction between users and the information system in UML.

Unified Modeling Language (UML)

A widely used method of visualizing and documenting software systems design. UML uses object-oriented design concepts, but it is independent of any specific programming language and can be used to describe business processes and requirements generally.

Economic feasibility

Achieved if the projected benefits of the proposed system outweigh the estimated costs involved in acquiring, installing, and operating it.

systems development life cycle (SDLC)

Activities and functions that systems developers typically perform, regardless of how those activities and functions fit into a particular methodology. The SDLC model includes five phases: 1. Systems planning, 2. Systems analysis, 3. Systems design, 4. Systems implementation, and 5. Systems support and security.

iterative

An adaptive method typically uses a spiral development model, which builds on a series of iterations.

fishbone diagram

An analysis tool that represents the possible causes of a problem as a graphical outline. Also called Ishikawa diagram.

prototype

An early, rapidly constructed working version of the proposed information system.

bring your own device (BYOD)

An equipment management model where employees are in charge of their devices (e.g., computers, tablets, smartphones) at work, not the IT department. This includes device selection and setup, program installation and updating, and network connectivity (including security).

SWOT analysis

An examination of a company's strengths (S), weaknesses (W), opportunities (O), and threats (T).

actor

An external entity with a specific role. In a use case model, actors are used to model interaction with the system.

Research

An important fact-finding technique that include the review of journals, periodicals, and books to obtain background information, technical material, and news about industry trends and developments.

preliminary investigation

An initial analysis to clearly identify the nature and scope of the business opportunity or problem. Also called a feasibility study.

feasibility study

An initial investigation to clearly identify the nature and scope of the business opportunity or problem. Also called a preliminary investigation.

Informal structures

An organization based on interpersonal relationships, which can develop from previous work assignments, physical proximity, unofficial procedures, or personal relationships.

user productivity systems

Application that provides employees of all levels a wide array of tools to improve job performance. Examples include email, word processing, graphics, and company intranets.

Productivity software

Applications such as word processing, spreadsheet, database management, and presentation graphics programs.

Range-of-response questions

Closed-ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scale.

Product-oriented

Companies that manufacture computers, routers, or microchips.

systems support and security phase

During the systems support and security phase of the SDLC, the IT staff maintains, enhances, and protects the system.

Output

Electronic or printed information produced by an information system.

Qualitative risk analysis

Evaluating risk by estimating the probability that it will occur and the degree of impact.

quantitative risk analysis

Evaluating risk in terms of the actual impact in terms of dollars, time, project scope, or quality.

Tangible cost

Expense that has a specific dollar value. Examples include employee salaries and hardware purchases.

Brooks' Law

Frederick Brooks, an IBM engineer, observed that adding more manpower to a late software project only makes it later.

data flow diagram (DFD)

Graphical representation of the system, showing it stores, processes, and transforms data into useful information.

Security

Hardware, software, and procedural controls that safeguard and protect a system and its data from internal or external threats.

business rules

How a system handles data and produces useful information. Business rules, also called business logic, reflect the operational requirements of the business. Examples include adding the proper amount of sales tax to invoices, calculating customer balances and finance charges, and determining whether a customer is eligible for a volume-based discount.

swim lanes

In a business process diagram, the overall diagram is called a pool, and the designated customer areas are called swim lanes.

properties

In object-oriented (O-O) analysis, characteristics that objects inherit from their class or possess on their own.

objects

In object-oriented analysis or programming, an object represents a real person, place, event, or transaction.

user design phase

In this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.

Enterprise computing

Information systems that support company-wide data management requirements, such as airline reservations or credit card billing systems.

ecommerce

Internet-based commerce

Systems analysis and design

Is a step-by-step process for developing high-quality information systems

intangible cost

Item that is difficult to measure in dollar terms, such as employee dissatisfaction.

customer relationship management (CRM)

Many companies implement systems to integrate all customer-related events and transactions including marketing, sales, and customer service activities.

Input

Necessary data that enters a system, either manually or in an automated manner.

Transaction processing (TP) systems

Operational system used to process day-to-day recurring business transactions, such as customer billing.

stakeholders

People who have an interest in an information system

CASE tool

Powerful software used in computer-aided systems (or software) engineering (CASE) to help systems analysts develop and maintain information systems.

Business support systems

Provide job-related information support to users at all levels of a company.

Open-ended questions

Queries that allows for a range of answers. They encourage spontaneous and unstructured responses, and are useful in understanding a larger process.

Closed-ended questions

Queries that limit or restrict the range of responses. Used in the interview process when specific information or fact verification is desired.

leading questions

Queries that suggests or favors a particular reply.

Business Case

Refers to the reasons, or justification, for a proposal.

Groupware

Software that runs in the cloud or on a company intranet that enables users to share data, collaborate on projects, and work in teams, and may offer features in addition to basic email capability, such as calendars, task lists, schedules, contact lists, and document management. Also called workgroup software.

Performance

System characteristics such as speed, volume, capacity, availability, and reliability.

agile methods

Systems development method that attempts to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements. Related to adaptive method.

technical support

Technical support is necessary to support the wide variety of IT systems and users. It includes six main functions: application development, systems support, user support, database administration, network administration, and web support. These functions overlap considerably and often have different names in different companies.

electronic product code (EPC)

Technology that uses RFID tags to identify and monitor the movement of each individual product, from the factory floor to the retail checkout counter.

radio frequency identification (RFID)

Technology that uses high-frequency radio waves to track physical objects.

scalable

The ability of a system to expand to meet new business requirements and volumes.

critical thinking skills

The ability to compare, classify, evaluate, recognize patterns, analyze cause and effect, and apply logic. Such skills are valued in the IT industry.

engaged listening

The ability to really concentrate on what someone is saying, and avoid the temptation to hear what is expected. Also includes noticing non-verbal communication.

object-oriented (O-O) analysis

The act of understanding an information system by identifying things called objects. An object represents a real person, place, event, or transaction. Object-oriented analysis is a popular approach that sees a system from the viewpoint of the objects themselves as they function and interact with the system.

just-in-time (JIT)

The exchange or delivery of information when and where it is needed. For example, just-in-time inventory systems rely on computer-to-computer data exchange to minimize unnecessary inventory.

systems planning phase

The first phase of the SDLC.

systems implementation phase

The fourth phase of SDLC. During this phase the new system is constructed, programs are written, tested, and documented, and the system is installed.

strategic plans

The long-range plan that defines the corporate mission and goals. Typically defined by top management, with input from all levels.

pool

The overall diagram In business process modeling notation (BPMN).

project creep

The process by which projects with very general scope definitions expand gradually, without specific authorization.

Strategic planning

The process of identifying long-term organizational goals, strategies, and resource.

Risk Management

The process of identifying, evaluating, tracking, and controlling risks to minimize their impact.

Project management

The process of planning, scheduling, monitoring, controlling, and reporting upon the development of an information system.

systems analysis phase

The second SDLC phase. The purpose of this phase is to build a logical model of the new system.

systems design phase

The third SDLC phase. The purpose of systems design is to create a blueprint for the new system that will satisfy all documented requirements, whether the system is being developed in-house or purchased as a package.

waterfall model

The traditional model of software development. A graph that depicts the result of each SDLC phase flowing down into the next phase.

requirements modeling

Used in the systems planning phase of the SDLC. It involves using various fact-finding techniques, such as interviews, surveys, observation, and sampling, to describe the current system and identify the requirements for the new system.

critical success factor

Vital objective that must be achieved for the enterprise to fulfill its mission.

Technical feasibility

When an organization has the resources to develop or purchase, install, and operate the system.

legacy systems

When planning an information system, a company must consider how a new system will interface with older systems

discretionary project

Where management has a choice in implementing a project, they are called discretionary. For example, creating a new report for a user is an example of a discretionary project.

nondiscretionary project

Where management has no choice in implementing a project, it is called nondiscretionary. For example, adding a report required by a new federal law.

information system

combines technology, people, and data to provide support for business functions such as order processing, inventory control, human resources, accounting, and many more.

data

consists of basic facts that are the system's raw material

Hardware

consists of everything in the physical layer of the information system

Application software

consists of programs that support day-to-day business functions and provide users with the information they need

Processes

describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results

systems request

formal request to the IT department that describes problems or desired changes in an information system or business process.

enterprise applications

include order processing systems, payroll systems, and company communications networks.

users

inside and outside the company who will interact with the system, and IT staff members, such as systems analysts, programmers, and network administrators who develop and support the system.

system

is a set of related components that produces specific results

horizontal system

is a system, such as an inventory or payroll application, that can be adapted for use in many different types of companies

systems analyst

is a valued member of the IT department team who helps plan, develop, and maintain information systems

Information

is data that has been transformed into output that is valuable to users.

vertical system

is designed to meet the unique requirements of a specific business or industry, such as an online retailer, a medical practice, or an auto dealership.

mission-critical system

is one that is vital to a company's operations.

System software

manages the hardware components, which can include a single computer or a global network with many thousands of clients.

risk management plan

ncludes a review of the project's scope, stakeholders, budget, schedule, and any other internal or external factors that might affect the project. The plan should define project roles and responsibilities, risk management methods and procedures, categories of risks, and contingency plans.

Moore's Law

predicted that the number of transistors on an integrated circuit chip would double about every 24 months

Process

refers to the logical rules that are applied to transform the data into meaningful information.

Software

refers to the programs that control the hardware and produce the desired information or results