CIS: Chapter 17

Bugs

Defects in the code of an information system

Project scope

Describes the business need and the justification requirements, and current boundaries for the project

Workshop training

Held in a classroom environment and led by an instructor

User documentation

Highlights how to use the system and how to troubleshoot issues or problems

Data flow diagram (DFD)

Illustrates the movement of information between external entities and the processes and data stores within the system

Software customization

Modifies software to meet specific user or business requirements

Off-the-shelf application software

Supports general business processes and does not require any specific software customization to meet the organizations needs.

GUI screen design

The ability to model the information system screens for an entire system using icons, buttons, menus, and submenus

Project management

The application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations form a project

Software engineering

A disciplined approach for constructing information systems through the use of common methods, techniques, or tools

Data models

A formal way to express data relationships to a database management system (DBMS)

Prject plan

A formal, approved document that mages and controls project execution

Help desk

A group of people who respond to internal system user questions

Change agent

A person or event that is the catalyst for implementing major changes for a system to meet business changes

Scripting language

A programming method that provides for interactive modules to a website

Joint application development (JAD)

A session where employees meet, sometimes for several days, to define or review the business requirements for the system

Control objectives for information and related technologies (COBIT)

A set of best practices that helps an organization to maximize the benefits of an information system, while at the same time establishing appropriate controls to ensure minimum erros

Brainstorming

A technique for generating ideas by encouraging participants to offer as many ideas as possible in a short period of time without any analysis until all the ideas have been exhausted

Project

A temporary endeavor undertaken to create a unique product or service

Project manager

An individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure all key project milestones are completed on time.

Legacy System

An old system that is fast approaching or beyond the end of its useful life within an organization

Analysis phase

Analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system

test conditions

The detailed steps the system must preform along with the expected results of each step

Graphical user interface (GUI)

The interface to an information system

Maintenance phase

The organization preforms changes, corrections, additions, and upgrades to ensure the system continues to meet business goals

System development life cycle (SDLC)

The overall process for developing information systems from planning and analysis through implementation and maintence

Project Management Institution (PMI)

develops procedures and concepts necessary to support the profession of project management. It defines a project

System Reports

-Internal report: presents data that are distributed inside the organization and intended for employees within an organization. -Detailed internal report:Presents information with little or no filtering restrictions of the data -Summary internal report: Organizes and categorizes data for managerial perusal. -Exception reporting: Highlights situations occurring outside of the normal operating range for a condition or standard -Information system control report: Ensures the reliability of information, consisting of policies and their physical implementation, access restrictions, or record keeping of actions and transactions. -Information systems audit report: Assesses a company's information system to determine necessary changes and help ensure the information system's availability, confidentiality, and integrity -Post implementation report: Presents a formal report or audit of a project after its up and running

Different forms of System Testing

-Alpha testing: Asses if the entire system meets the design requirements of the users -Development Testing: Test the system to ensure it is bug-free -Integration Testing: Verify that separate systems can work together, passing data back and forth correctly -System Testing: Verify that the units or pieces of code function correctly when integrated -User acceptance testing (UAT): Determine if the system satisfies the user and business requirements -Unit Testing: Test individual units or pieces of code for a system

System Implementation Methods

-Parallel: Uses both the legacy system and new system until all users verify that the new system functions correctly -Plunge: Discards the legacy system and immediately migrates all users to the new system -Pilot: Assigns a small group of people to use the new system until it is verified that it works correctly; then the remaining users migrate to new system -Phased: Installs the new system in phases until it is verified that it works correctly

The SDLC and its associated activities

-Planning -Analysis -Design -Development -Testing -Implementation -Maintenance

Entity relationship diagram

Document the relationship between entities in a database environment.

Testing phase

Involves bringing all the project pieces together into a special testing environment to test for error, bugs, and interoperability and verify that the system meets all of the business requirements defined in the analysis phase

Design phase

Involves describing the desired features and operations of the system including screen layout, business rules, process diagrams, pseudo code, and other documentation.

Planning phase

Involves establishing a high-level plan of the intended project and determining project goals

Process modeling

Involves graphically representing the process that capture, manipulate, store, and distribute information between a system and its environment

Implementation phase

Involves placing the system into production so users can begin to perform actual business operations with the system

Development phase

Involving taking all of the detailed design documents from the design phase and transforming them into the actual system

orientated languages

Languages that group data and corresponding processes into objects

Preventive maintenance

Makes system changes to reduce the chance of future system failure

Corrective maintenance

Makes system changes to repair design flaws, coding errors, or implementation issues

Requirements defined document

Prioritizes all of the business requirements by oder of importance to the company

Fourth0generation language (4GL)

Programming languages that look similar to human languages

Online training

Runs over the internet or on a CD or DVD, and employees complete the training on their own time at their own pace

Computer-aided software engineering (CASE)

Tools are software suites that automate systems analysis, design, and development

Requirements management

The process of managing changes to the business requirements throughout the project

Conversion

The process of transferring information from a legacy system to a new system

Business requirements

The specific business requests the system must meet to be successful, so the analysis phase is critical because business requirements drive the entire systems development effort

Sign-off

The system users' actual signatures indicting they approve all of the business requirements