Term
|
Definition
consists of the sets of instructions, often called programs, that are executed by the hardware.
Software is written in languages that can be processed by the computer. |
|
|
Term
|
Definition
| data are stored in a computer in a series of ones and zeros |
|
|
Term
|
Definition
the ones and zeros in which programs/instructions are stored.
Binary code is grouped into larger units of fields, records, and files.
Files can be integrated into a database. |
|
|
Term
| two major types of software |
|
Definition
| systems and application software |
|
|
Term
|
Definition
| performs the fundamental tasks needed to manage computer resources |
|
|
Term
|
Definition
| common type of systems software that negotiates the conversation between the computer's hardware, the application the user is running, and the data that the application is working with. |
|
|
Term
|
Definition
| common type of systems software that performs basic functions not particular to a certain application. |
|
|
Term
|
Definition
| consist of programs that tell the computer what steps the user wants carried out |
|
|
Term
| first-generation (machine) languages |
|
Definition
| written in binary code and therefore understood directly by the computer |
|
|
Term
| third-generation (procedural or programming) languages |
|
Definition
consist of English-like words and phrases that represent multiple machine language instructions, making these languages much easier to learn, but they must be converted to binary through either compilation or interpretation.
3rd generation languages include COBOL, BASIC, C and C++, Java, etc. |
|
|
Term
|
Definition
| whole program converted at once, then executed (like batch processing) |
|
|
Term
|
Definition
| the program is converted and executed one line at a time (like online processing) |
|
|
Term
| Common Business Oriented Language (COBOL) |
|
Definition
| designed in 1959 to be easy to read and maintain, and the standard has been extensively revised and updated over the years. Some COBOL still in use. |
|
|
Term
| Beginner's All-Purpose Symbolic Instruction Code (BASIC) |
|
Definition
| Developed to teach programming but not used in business application processing. Visual BASIC provides a graphical user interface to develop Microsoft Windows applications from code written in BASIC. |
|
|
Term
|
Definition
| high-level, object-oriented programming language developed to write programs embedded in World Wide Web documents. |
|
|
Term
|
Definition
| Java programs that run in a web browser |
|
|
Term
|
Definition
| Java programs that run on a web server |
|
|
Term
| fourth-generation (problem-oriented or nonprocedural) languages |
|
Definition
| permits a nonspecialized user to describe the problem to, and receive guidance from, the computer instead of specifying a procedure. |
|
|
Term
| generalized audit software (GAS)/computer-assisted audit techniques (CAAT) |
|
Definition
| perform calculations, extracting sample items, verifying totals, developing file statistics, and retrieving specified data fields. |
|
|
Term
|
Definition
| authoring software language commonly used to create and link websites. |
|
|
Term
|
Definition
| open standard usable with many programs and platforms; focused on the content of the data. |
|
|
Term
|
Definition
| specification developed for commercial and industrial entities that report in accordance with U.S. GAAP. The SEC allows firms to report using XBRL. |
|
|
Term
|
Definition
| Digital computers store all information in binary format, which makes arithmetic operations and true/false decisions on the lowest level extremely straightforward. |
|
|
Term
|
Definition
| either 0 or 1 (off or on) in binary code. Bits can be strung together to form a binary (base 2) number. |
|
|
Term
|
Definition
| group of bits; byte can signify a character |
|
|
Term
|
Definition
| group of bytes; contains a unit of data about some entity |
|
|
Term
|
Definition
| group of fields; all fields contain information pertaining to an entity |
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
| combination of the first two fields on each record. Essence of a key is that it contains enough information to uniquely identify each record. |
|
|
Term
|
Definition
| allows records to be sorted and managed with much greater efficiency. If all the records are sorted in the order of the key, searching for a particular one becomes much easier. |
|
|
Term
|
Definition
| all records are stored continuously one after the other, as on a reel of magnetic tape; oldest file structure. Search methods extremely limited. |
|
|
Term
| hierarchical/tree database model |
|
Definition
records form branches and leaves extended from a root
Data is stored only once.
Every parent record can have multiple child records, but every child can only have one parent.
Tree structure improves speed and storage efficiency, but harder to add data than with with flat file system because relationships must be maintained. |
|
|
Term
|
Definition
| group of tables built following the principles of relational data structures; allows for easy searching of records |
|
|
Term
| primary purpose of a database system |
|
Definition
| to have a single storage location for each data item. |
|
|
Term
|
Definition
| Every record in a single row and every column containing a value that pertains to that record. |
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
refers to how close a given data element is to being unique
High cardinality- data can only exist once
Normal- not unique to a given table, but has a restricted range of possible values
Low- very small range of values |
|
|
Term
|
Definition
| for a record to be entered in a given table, there must already be a record in some other tables |
|
|
Term
| database management system (DBMS) |
|
Definition
| integrated set of software tools superimposed on the data files that helps maintain the integrity of the underlying database |
|
|
Term
|
Definition
DBMS make the maintenance of vast relational databases practical.
W/out the sophisticated capabilities of DBMS, enforcing relational database rules would be difficult.
DBMS allows programmers and designers to work independently of the physical and logical structure of the database.
W/ a DBMS, the physical structure of the database can be completely altered w/out having to change any of the programs using the data items. Thus, different users may define their own data views (called subschemas). |
|
|
Term
|
Definition
| those in the IT function responsible for dealing with the DBMS |
|
|
Term
|
Definition
| consists of the layouts of the tables and the constraints on entering new records. The DBMS automates the enforcing of the schema. |
|
|
Term
|
Definition
| data view as designed by a particular user, since the physical structure of the database can be completely altered w/out having to change any of the programs using the data items. |
|
|
Term
|
Definition
| allows the user to specify how the tables will look and what kinds of data elements they will hold |
|
|
Term
| data manipulation language |
|
Definition
| allows the DBMS retrieves, adds, deletes, or modifies records and data elements |
|
|
Term
| structured query language (SQL) |
|
Definition
| SQL uses both DDL and DML. |
|
|
Term
|
Definition
| contains the physical and logical characteristics of every data element in a database; contains the size, format, usage, meaning, and ownership of all data elements, as well as what persons, programs, reports, and functions use the data elements |
|
|
Term
|
Definition
| database stored in 2+ physical sites. |
|
|
Term
| replication/snapshot database |
|
Definition
| DBMS duplicates the entire database and sends it to multiple locations; changes are periodically copied and similarly distributed |
|
|
Term
| fragmentation/partitioning method |
|
Definition
| specific records are stored where they are most needed |
|
|
Term
| organization needs assessment (ONA) |
|
Definition
| detailed process of study and evaluation of how information systems can be deployed to help the organization meet its goals |
|
|
Term
|
Definition
Determine whether current systems support organizational goals
Determine needs unmet by current systems
Determine capacity of current systems to accommodate projected growth
Propose path for information systems deployment to achieve organizational goals within budgetary constraints |
|
|
Term
|
Definition
| flow of actions performed on goods and/or information to accomplish a discrete objective. Integrated systems are now the norm. |
|
|
Term
| business process reengineering |
|
Definition
| requires a complete rethinking of how business functions are performed to provide value to customers. Normally occurs when processes are automated or when an integrated system is acquired. |
|
|
Term
| business process design participants |
|
Definition
Business processing functioning affects all stakeholders in the business, so input from each group should be considered.
End users are generally the drivers of a new or redesigned process. |
|
|
Term
| IT steering committee & members |
|
Definition
B/c IT pervades every aspect of operations in a modern organization, the IT steering committee must study each request and approve or deny it.
Members include the CIO, head of systems development, and executive management from each division. |
|
|
Term
| What happens when the IT steering committee approves a new process? |
|
Definition
Once a new process is approved, a project team is assembled, comprised of representation from the end users who requested it and the IT personnel who will design and build the software components that will support it.
Upper management supports process design.
If the new process or system crosses org. boundaries, external parties are participants. |
|
|
Term
| most important process for IT |
|
Definition
| creating requirements, especially when building, planning, and managing |
|
|
Term
| Who must approve progress on the new business process? |
|
Definition
| both IT management and the end users at the end of each stage. This requirement for ongoing review and approval of the project is a type of implementation control. |
|
|
Term
| Systems Development Life Cycle (SDLC) |
|
Definition
| Traditional methodology applied to the development of large, highly structured application systems. |
|
|
Term
|
Definition
| Plan (need for new system recognized), analyze (definition), design, build/buy (development), implementation, deploy (maintenance). |
|
|
Term
|
Definition
A proposal for a new system is submitted to the IT steering committee, describing the need for application and the business functions that it will affect.
Feasibility studies
Steering committee gives the go-ahead. |
|
|
Term
|
Definition
| consists of mapping the flow and storage of the data elements that will be used by the new system and the new program module that will constitute the new system |
|
|
Term
|
Definition
| structured flowcharts are commonly used in this step; used in logical design |
|
|
Term
|
Definition
| planning the specific interactions of the new program code and data elements with the hardware platform on which the new system will operate. |
|
|
Term
|
Definition
determines how an application should be designed to best serve the users' needs; often works w/applications programmers;
heavily involved in the logical and physical design processes. |
|
|
Term
|
Definition
| actual program code and database structures that will be used in the new system are written. |
|
|
Term
|
Definition
| most crucial step of the development process; test data is used in testing. |
|
|
Term
| user acceptance testing & beginning of implementation |
|
Definition
final step before placing the system in live operation.
Once the user department is satisfied with the new system, they acknowledge formal acceptance and implementation begins. |
|
|
Term
| four strategies for implementation |
|
Definition
| parallel operation, cutover conversion, pilot conversion, phased conversion |
|
|
Term
|
Definition
the old and new systems both are run at full capacity for a given period
Safest, but most expensive and time-consuming. |
|
|
Term
|
Definition
old system shut down and new one takes over at once
Riskiest, but least expensive and time-consuming. |
|
|
Term
|
Definition
one branch, department, or division at a time is fully converted to the new system.
Experienced gained from one section, but the conversion time is extended. |
|
|
Term
|
Definition
under this strategy, one function of the new system at a time is placed in operation
Advantage of this strategy is allowing the users to learn one part of the system at a time. |
|
|
Term
| most critical parts of implementation |
|
Definition
| training and documentation |
|
|
Term
|
Definition
| consists of more than just operations manuals, but also layouts of the program code and database structures must also be available for the programmers. |
|
|
Term
| systems follow-up/post-audit evaluation |
|
Definition
| subsequent review of the efficiency and effectiveness of the system after it has operated for a substantial time. |
|
|
Term
|
Definition
| important after fully implemented and post-audit evaluation is complete. |
|
|
Term
|
Definition
creating a working model of the system requested, demonstrating it for the user, obtaining feedback, and making changes to the underlying code.
Repeats through several iterations until user is satisfied with functionality. |
|
|
Term
| computer-aided software engineering (CASE) |
|
Definition
applies the computer to software design and development
Provides capacity to maintain on the computer all of system documentation to develop input and output screens and generate program code (automate coding process). |
|
|
Term
|
Definition
| relevant controls modified as systems maintenance (managing changes) occurs |
|
|
Term
|
Definition
| copy of an approved change saved in a test area of the computer, not to the production version |
|
|
Term
| database administrators (DBAs) |
|
Definition
| responsible for developing and maintaining the organization's databases and for establishing controls to protect their integrity |
|
|
Term
|
Definition
| maintains the devices that interconnect the organization's computers, as well as its connections to other networks |
|
|
Term
|
Definition
| content of organization's website; works closely with programmers and network technicians |
|
|
Term
| computer (console) technicians |
|
Definition
| responsible for the moment-to-moment running of servers and mainframes |
|
|
Term
|
Definition
maintain control over and accountability for documentation, programs, and data storage media.
Should have no programming knowledge. |
|
|
Term
|
Definition
| maintain and fine-tune the operating systems on servers and mainframes. |
|
|
Term
|
Definition
| core software that performs input, output and storage (transformation is done by application software) |
|
|
Term
|
Definition
| design, write, test, and document computer programs according to specifications provide by the end users |
|
|
Term
|
Definition
| log problems reported by users, resolves minor difficulties, and forwards tougher problems to the DBA or the webmaster. |
|
|
Term
| information security (IS) |
|
Definition
| distinct function w/in IT; ensure that employees can only access to programs and data elements appropriate for their job duties. |
|
|
Term
|
Definition
| responsible for information security policy (to be used for organizational purposes only). |
|
|
Term
| Who are responsible for designing, building, and maintaining the organization's applications? |
|
Definition
| systems analysts and applications programmers |
|
|
Term
|
Definition
| responsible only for the smooth running of servers and mainframes, so they should not have access to change applications programs. |
|
|
Term
|
Definition
| extremely valuable asset and not easily replaceable. |
|
|
Term
|
Definition
| determine how the organization's data should be stored and what relationships among the data best achieve the business objectives. |
|
|
Term
| Every database is a unique combination of the... |
|
Definition
schema- relationships among the data
software- database management system
hardware- equipment on which the database is stored
DBA should have no access to the application programs that process the data. |
|
|
Term
|
Definition
| end users; should never be able to access the underlying code |
|
|
Term
|
Definition
|
|
