Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
236 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
Application Architecture
|
A specification of the technologies to be used to implement information systems
|
Serves as an outline for detailed design, construction, and implementation
|
|
|
Physical Data Flow Diagram
|
A process model used to communicate the technical implementation characteristics of an information system
|
Serve as a technical blueprint; similar to DFDs
|
|
|
Choices of Implementation Methods
|
Purchased application; System or utility program; Existing application from a program library; A program to be written
|
Ways to implement a process using digital means
|
|
|
Distributed System
|
A system in which components are distributed across multiple locations and computer networks
|
Much more efficient, divides up work and processing power
|
|
|
Centralized System
|
A system in which all components are hosted by a central, multiuser computer
|
Outdated and very inefficient
|
|
|
Types of Distributed System Architecture
|
File Server Architecture; Client/Server Architecture; Internet-Based Architecture
|
|
|
|
Layers of an Information System Application
|
Presentation (Presentation + Presentation Logic); Application/Business Logic; Data (Data Manipulation + Data)
|
|
|
|
Presentation Layer
|
Actual user interface; the presentation of inputs and outputs to the user
|
|
|
|
Presentation Logic Layer
|
Any processing that must be done to generate the presentation
|
Example: editing input data, formatting output data
|
|
|
Application Logic Layer
|
Includes all the logic and processing required to support the actual business application and rules
|
Example: credit checking, calculations, data analysis, etc.
|
|
|
Data Manipulation Layer
|
Includes all the commands and logic required to store and retrieve data to and from the database
|
|
|
|
Data Layer
|
The actual stored data in the database
|
|
|
|
Structure of File Server Solution
|
Data is stored on file server; Data manipulation, application logic, and presentation logic are all executed on the client
|
|
|
|
Structure of Distributed Presentation (2-Tier)
|
Data is stored and manipulated on the database server; Application logic is executed on the server; Presentation logic is executed on the client
|
|
|
|
Structure of Distributed Data (2-Tier)
|
Data is stored and manipulated on the database server; Application logic and presentation logic are executed on the client
|
|
|
|
Structure of Distributed Data and Application (N-Tier)
|
Data is stored and manipulated on the database server; Application logic is executed on the application server; Presentation logic is executed on the client
|
|
|
|
Structure of Network/Internet-Based Solution
|
Data is stored and manipulated on the database server; Application logic is executed on the application server; Presentation logic is distributed from the web server
|
|
|
|
Types of Client/Server Solutions
|
Distributed Presentation (2-Tier), Distributed Data (2-Tier), Distributed Data and Application (N-Tier)
|
|
|
|
Local Area Network (LAN)
|
A set of client computers connected over a relatively short distance to one or more servers
|
Example: a room or section of a building; a department
|
|
|
File Server System
|
A LAN in which a server hosts the data of an information system
|
|
|
|
Client/Server System
|
A distributed computing solution in which the presentation, presentation logic, application logic, data manipulation, and data layers are distributed between client PCs and one or more servers
|
|
|
|
Thin Client
|
A personal computer that does not have to be very powerful
|
Example: a dumb terminal
|
|
|
Fat Client
|
A personal computer, notebook computer, or workstation that is typically powerful
|
Most personal computers today are considered this
|
|
|
Database Server
|
A server that hosts one or more databases
|
|
|
|
Transaction Server
|
A server that hosts services which ensure that all database updates for a transaction succeed or fail as a whole
|
|
|
|
Application Server
|
A server that hosts application logic and services for an information system
|
|
|
|
Messaging/Groupware Server
|
A server that hosts services for groupware
|
|
|
|
Web Server
|
A server that hosts Internet or intranet Web sites
|
|
|
|
Distributed Presentation
|
A client/server system in which presentation and presentation logic are shifted from the server to reside on the client
|
|
|
|
Distributed Data
|
A client/server system in which the data and data manipulation layers are placed on servers and other layers are placed on clients. Also called two-tiered client/server computing
|
|
|
|
Distributed Data and Application
|
A client/server system in which the data and manipulation layers are placed on their own server(s), the application logic is placed on its own server, and the presentation logic and presentation are placed on the clients. Also called three-tiered/n-tiered client/server computing
|
|
|
|
Partitioning (Application)
|
The act of determining how to best distribute or duplicate application components across a network
|
|
|
|
Network Computing System
|
A multitiered solution in which the presentation and presentation logic layers are implemented in client-side Web browsers using content downloaded from a Web server
|
|
|
|
intranet
|
A server that uses Internet technology to integrate desktop, work group, and enterprise computing
|
|
|
|
Distributed Relational Database Management System (RDBMS)
|
Software that implements distributed relational databases
|
|
|
|
Data Partitioning
|
Distributes rows and columns to specific database servers with little or no duplication between servers
|
Useful for when different places need to access different data
|
|
|
Vertical Partitioning
|
Different columns of a table are assigned to different database servers
|
|
|
|
Horizontal Partitioning
|
Different rows of a table are assigned to different database servers
|
|
|
|
Data Replication
|
Duplicates some or all tables on more than one database server
|
Good for when different places need to access the same data
|
|
|
Batch Processing
|
In which transactions of data are grouped into batches for periodic processing
|
Is technically not obsolete, but is slipping out of favor
|
|
|
Online Processing
|
In which transactions are processed individually and automatically
|
More systems are leaning toward this type of immediate transaction processing
|
|
|
Remote Batch Processing
|
A combination of batch processing and online processing that combine the best traits of both
|
|
|
|
Electronic Data Interchange (EDI)
|
The standardized electronic flow of business transactions or data between businesses
|
A transaction standard that could eliminate dependence on paper documents
|
|
|
Middleware
|
Utility software that enables communication between different processors in a system
|
The “slash” in client/server
|
|
|
Classes of Middleware
|
Presentation Middleware, Application Middleware, Database Middleware
|
|
|
|
Software Development Environment (SDE)
|
A language and tool kit for constructing information system applications
|
|
|
|
Clean Layering
|
A design strategy that requires that presentation, application, and data layers be physically separated
|
|
|
|
Design Unit
|
A self-contained collection of processes, data stores, and data stores that share similar design attributes
|
|
|
|
File
|
A collection of similar records
|
Predecessor to tables
|
|
|
Database
|
A collection of interrelated files
|
A collection of tables
|
|
|
Field
|
The smallest unit of meaningful data to be stored in a file or database
|
Physical implementation of a data attribute
|
|
|
Types of Fields
|
Primary Keys, Secondary Keys, Foreign Keys, Descriptive Fields
|
Different types of fields one might find in a table
|
|
|
Primary Key
|
A field or group of fields that uniquely identifies a record
|
Example: Employee ID, Student ID
|
|
|
Secondary Key
|
A field that identifies a single record or a subset of related records
|
Does not have to uniquely identify the record
|
|
|
Foreign Key
|
A field that points to records in a different file in the database
|
Indicator of a relationship
|
|
|
Descriptive Field
|
A nonkey field
|
Anything else
|
|
|
Record
|
A collection of fields arranged in a predetermined format
|
|
|
|
Blocking Factor
|
The number of logical records included in a single read or write operation
|
|
|
|
Table
|
The relational database equivalent of a file
|
|
|
|
Master File
|
A table containing records that are relatively permanent
|
|
|
|
Transaction File
|
A table containing records that describe business events
|
|
|
|
Document File
|
A table containing historical data
|
|
|
|
Archival File
|
A table containing master and transaction file records that have been deleted from online storage
|
|
|
|
Table Look-Up File
|
A table containing relatively static data that can be shared
|
|
|
|
Audit File
|
A table containing records of updates to other files
|
|
|
|
Data Architecture
|
A definition of how files and databases are to be developed
|
|
|
|
Operational Database
|
A database that supports day-to-day operations and transactions for an information system
|
Also called “transactional database”
|
|
|
Data Warehouse
|
A database that stores data extracted from operational databases
|
|
|
|
Data Administrator
|
A database specialist responsible for data planning, definition, architecture, and management
|
|
|
|
Database Administrator
|
A specialist responsible for database technology, design, construction, security, backup/recovery, and performance tuning
|
|
|
|
Database Architecture
|
The database technology used to support data architecture
|
|
|
|
Database Management System (DBMS)
|
Special software used to create, access, control, and manage a database
|
|
|
|
Data Definition Language (DDL)
|
A language used by a DBMS to define a database or a view of a database
|
|
|
|
Data Manipulation Language (DML)
|
A DBMS language used to create, read, update, and delete records
|
|
|
|
Database Engine
|
Core of the DBMS, interacts with the data directly and responds appropriately to specific CRUD commands
|
|
|
|
Relational Database
|
A database that implements data as a series of two-dimensional tables that are related via foreign keys
|
|
|
|
SQL
|
The DML and DDL of most relational databases
|
|
|
|
Trigger
|
A program embedded within a table and is automatically invoked by updates to another table
|
|
|
|
Stored Procedure
|
A program embedded in a table that can be called from an application program
|
|
|
|
Qualities of a Good Data Model
|
Simple, Essentially Nonredundant, Flexible and Adaptable to Future Needs
|
|
|
|
Database Schema
|
A model or blueprint representing the technical implementation of a database
|
|
|
|
Hungarian Notation
|
A set of naming conventions that names each object without spaces, dashes, and underscores and gives each object a prefix that defines all similar objects
|
|
|
|
Types of Data Integrity
|
Key Integrity, Domain Integrity, Referential Integrity
|
|
|
|
Key Integrity
|
Every table should have a non-NULL primary key
|
|
|
|
Domain Integrity
|
No field should take on a value that is outside the range of legal values
|
|
|
|
Referential Integrity
|
The assurance that a foreign-key value in one table has a matching primary-key value in the related table
|
|
|
|
Deletion Rules of Referential Integrity
|
No Restriction; Delete:Cascade; Delete:Restrict; Delete:Set null
|
|
|
|
No Restriction
|
Any record in the table may be deleted without regard to any records in any other tables
|
|
|
|
Delete:Cascade
|
A deletion of a record in the table must be automatically followed by the deletion of matching records in a related table
|
|
|
|
Delete:Restrict
|
A deletion of a record in the table must be disallowed until any matching records are deleted from a related table
|
|
|
|
Delete:Set null
|
A deletion of a record in the table must be automatically followed by setting any matching keys in a related table to the value NULL
|
|
|
|
Role Name
|
A foreign key name that reflects the purpose it serves in the table; ensures that foreign key names are nonredundant across tables
|
|
|
|
Internal Output
|
An output for system owners and users within an organization
|
Support either day-to-day operations or management monitoring and decision-making
|
|
|
Detailed Report
|
An internal output that presents information with little or no filtering
|
Report with everything
|
|
|
Summary Report
|
An internal output that categorizes information for managers
|
Get to the good stuff
|
|
|
Exception Report
|
An internal output that filters data to present information that reports exceptions to some condition or standard
|
Errors, or certain types of data
|
|
|
External Output
|
An output that leaves the organization
|
Intended for customers, suppliers, etc.
|
|
|
Turnaround Output
|
An external output that may reenter the system as input
|
Paper bills; forms
|
|
|
Tabular Output
|
An output that presents information as columns of text and numbers
|
A “traditional” report
|
|
|
Zoned Output
|
An output that presents text and numbers in designated areas of a form or screen
|
Divides report into sections
|
|
|
Graphic Output
|
An output that uses a pictoral chart to convey information
|
Often more effective than just text
|
|
|
Multimedia
|
Any information presented in a format other than traditional numbers, codes, and words
|
Example: video, audio, pictures
|
|
|
Line Chart
|
Shows one or more series of data over a period of time. Useful for summarizing and showing data at regular intervals
|
|
|
|
Area Chart
|
Similar to line chart, except that the focus is on the area under the line
|
|
|
|
Bar Chart
|
Useful for comparing series or categories of data. Each bar represents one series or category
|
|
|
|
Column Chart
|
Vertical bar chart
|
|
|
|
Pie Chart
|
Shows the relationship of parts to a whole; useful for summarizing percentages
|
|
|
|
Donut Chart
|
Similar to pie chart, except can show multiple categories of data
|
|
|
|
Radar Chart
|
Useful for comparing different aspect of more than one series/category of data. Each data series is represented as a geometric shape around a central point. Multiple series are overlaid so that they can be compared
|
|
|
|
Scatter Chart
|
Useful for showing the relationship between two or more series/categories of data measured at uneven intervals of time
|
|
|
|
Output Design Guidelines
|
Should be simple to read and interpret; Timing is important; Distribution/Access must be sufficient to assist all relevant users; Must be acceptable to relevant users
|
|
|
|
Output Design Process
|
Identify system outputs and review logical requirements; Specify physical output requirements; Design any preprinted forms; Design, validate, and test outputs
|
|
|
|
Page Size
|
Standard (8.5'' x 11'') or Legal (8.5'' by 14'')
|
|
|
|
Page Orientation
|
Portrait or Landscape; Portrait is preferred in most situations
|
|
|
|
Page Headings
|
Should appear on every page and include a recognizable title, date/time, and page numbers
|
|
|
|
Report Legends
|
An explanation of codes or abbreviations used in the report; Can be implemented as a page footer, a pop-up dialog box, or a footnote on the first page
|
|
|
|
Column Headings
|
Should be short and descriptive; avoid abbreviations (unless there is a legend)
|
|
|
|
Heading Alignments
|
Either left justified, right justified, or centered; whichever works best for the users/current situation
|
|
|
|
Column Spacing
|
As a rule of thumb, use 3-5 spaces between each header
|
|
|
|
Row Headings
|
Find a consistent way to sort the rows
|
|
|
|
Formatting
|
Convert user input/stored data into readable output
|
|
|
|
Control Breaks
|
Used to separate groups; usually have an accumulated total for each group
|
|
|
|
End of Report
|
Should be clearly indicated to let the user know that he/she is finished reading
|
|
|
|
Screen Size
|
Should consider the “lowest common denominator”--the worst possible resolution a user can have
|
|
|
|
Scrolling
|
If possible, freeze important headings at the top of the screen
|
|
|
|
Navigation
|
Always give users a sense of where they are in the report and give the ability to navigate between screens/sections of the report
|
|
|
|
Partitioning (Output)
|
Zones are forms within forms; Frames are pages within pages; used to separate relevant groups of data
|
|
|
|
Information Hiding
|
Used to hide information until it is requested by the user; useful for giving a summary report the option to be expanded
|
|
|
|
Highlighting
|
Useful for calling users' attention to important/erroneous data, but can be a distraction if overused
|
|
|
|
Printing
|
Always give the user the option to create a hard copy of the report
|
|
|
|
Data Capture
|
The identification and acquisition of new data
|
|
|
|
Source Document
|
A form used to record data about a transaction
|
|
|
|
Data Entry
|
The process of translating data into a computer-readable format
|
|
|
|
Keyboard
|
Most common data entry method, but is also the most prone to user errors
|
|
|
|
Mouse
|
A pointing device used in conjunction with graphical user interfaces
|
|
|
|
Point-of-Sale (PoS)
|
Terminals that capture data at the time of sale; quickly replacing older cash registers
|
|
|
|
Examples of Automatic Data Capture (ADC)
|
Optical Mark, Magnetic Ink, Electromagnetic Transmission, Smart Cards, Biometric
|
|
|
|
Types of Optical Recognition
|
Optical Mark Recognition, Optical Character Recognition, Bar Coding
|
|
|
|
Electromagnetic Transmission
|
Based on the use of radio frequency to identify physical objects; involves attaching a tag that contains identifying memory and an antenna to the physical object that is to be tracked
|
|
|
|
Smart Cards
|
Similar to, but slightly thicker than, a credit card; contains a microprocessor, memory circuits, and a battery
|
|
|
|
Biometric ADC
|
Based on unique and identifying human characteristics or traits; these unique traits are used to identify the specific individual; most widely used in security systems
|
|
|
|
General Principles for Input Design
|
Capture only variable data; Do not capture data that can be calculated/stored; Use codes for appropriate attributes
|
|
|
|
General Principles for User-Friendliness
|
Include instructions for completing the form; Sequence form fields so they can be read left-to-right; Use metaphoric design
|
|
|
|
Metaphoric Design
|
A design guideline that encourages the digital form to resemble a source document that is familiar to the user
|
|
|
|
Methods for Input Validation
|
Existence Checks, Data-Type Checks, Domain Checks, Combination Checks, Self-Checking Digits, Format Checks
|
|
|
|
Existence Checks
|
Determine whether all required fields on the input have actually been entered
|
|
|
|
Data-Type Checks
|
Ensure that the correct type of data has been input
|
|
|
|
Domain Checks
|
Determine whether the input data for each field falls within the legitimate set/range of values for that field
|
|
|
|
Combination Checks
|
Determine whether a known relationship between two fields is valid (such as the relationship between car make and car model)
|
|
|
|
Self-Checking Digit / Check Digit
|
A digit that is appended at the end of an inputted primary key to determine whether or not it is valid
|
|
|
|
Format Checks
|
Compare data entered against its known formatting requirements
|
|
|
|
Repository-Based Programming
|
An IDE that is directly connected to the system database
|
|
|
|
Text Box
|
The most common control for input; a rectangular-shaped box usually accompanied by a caption that allows the user to enter single or multiple lines of text
|
|
|
|
Radio Button
|
A control for selecting only one item from a small set of defined choices; consists of a small circle and a description of the value choice
|
|
|
|
Check Box
|
A control that allows the user to provide a yes/no value. If the value is “yes,” the square box contains a “check” mark. If the value is “no,” the square box is empty.
|
|
|
|
List Box
|
A control that requires the user to select a value from a list of possible choices; if there is a large number of choices, a vertical scrollbar is included
|
|
|
|
Drop-Down List
|
A control similar to a list box, except most of the values are hidden from the user and only a “default value” is visible until the user unhides the full list; this control is preferred over a list box because it conserves screen space
|
|
|
|
Combination “Combo” Box
|
A control that combines the capabilities of a text box and a list box; a drop-down list that allows the user to directly enter the chosen value instead of choosing from the list
|
|
|
|
Spin Box
|
A control that allows the user to either enter data directly or click on the scrolling buttons to “spin” through a sequential list of values
|
|
|
|
Button
|
Technically not an input control, but allows the user to submit data, cancel a transaction, move among forms, etc.
|
|
|
|
Drop-Down Calendar
|
A control where clicking on the drop-down button creates a clickable calendar useful for date fields
|
|
|
|
Slider
|
A control that allows the user to select a numeric value without using text; a graphical version of the spin box
|
|
|
|
Masked Edit
|
A control that automatically formats the text input to the programmer's desired standard
|
|
|
|
Ellipsis
|
A control that allows the user to click on a button in order for a larger dialog box to appear for data entry; often used for a field that requires several parts
|
|
|
|
Hyperlink
|
Clickable text that directs the user to either a website or another form
|
|
|
|
Check List Box
|
A tool for grouping several related check boxes
|
|
|
|
Check Tree List Box
|
A control that allows check box items to be organized in a hierarchical manner
|
|
|
|
Input Design Process
|
Identify system inputs and review logical requirements; Select appropriate GUI controls; Design, validate, and test inputs using some combination of layout tools and prototyping; Design the source document if necessary
|
|
|
|
Memo Box
|
Another word for a multiple-line text box
|
|
|
|
Image Box
|
An advanced GUI control that allows an image to be stored and displayed on the form
|
|
|
|
Expert User
|
An experienced computer user
|
|
|
|
Novice User
|
An inexperienced or casual computer user
|
|
|
|
Commandments of User Interface Design
|
Understand your users and their tasks; Involve the user in interface design; Test the system on actual users; Practice iterative design
|
|
|
|
Dialogue
|
The overall flow of screens and messages for an application
|
|
|
|
Platform Independence
|
The strategy of designing applications specifically for one or two web browsers instead of for multiple operating systems
|
|
|
|
Terminal
|
A non-PC machine that merely displays data and information transmitted from a remote computer, usually a mainframe
|
|
|
|
Paging
|
Displaying a complete screen of characters at a time
|
|
|
|
Scrolling
|
Displaying information up and down a screen, one line at a time
|
|
|
|
Function Keys
|
A series of special keyboard keys used to program special operations
|
|
|
|
Menu-Driven Strategy
|
A dialogue strategy that requires that the user select an action from a menu of choices
|
|
|
|
Types of Instruction Set/Command Language Syntaxes
|
Language-Based; Mnemonic; Natural Language
|
|
|
|
Language-Based Syntax
|
Built around a widely accepted command language, such as SQL, that can be used by the user to invoke actions
|
|
|
|
Mnemonic Syntax
|
Built around commands defined for custom information system applications, ideally commands that are meaningful to the user
|
|
|
|
Natural Language Syntax
|
Allows users to enter questions and commands in their native language
|
|
|
|
Help Wizard
|
Guides the users through complex processes by presenting a sequence of dialog boxes that require user input and system feedback
|
|
|
|
Agent
|
Reusable software object that can operate across different applications and networks
|
|
|
|
User Interface Design Process
|
Chart the user interface dialogue; Prototype the dialogue and user interface; Obtain user feedback; If necessary, return to step 1 or 2
|
|
|
|
State Transition Diagram
|
A tool used to depict the sequence and variation of screens that can occur when the system user sits at the terminal
|
|
|
|
Object-Oriented Design
|
An approach used to specify the software solution in terms of collaborating objects, their attributes, and their methods
|
|
|
|
Entity Class
|
An object class that contains business-related information and implements the analysis classes
|
|
|
|
Interface Class
|
An object class that provides the means by which an actor can interface with the system, sometimes called a “boundary class”; Examples include a window, dialogue box, or screen
|
|
|
|
Responsibilities of an Interface Class
|
Translate the user input into information the system can understand and use to process the business event; Take data pertaining to a business event and translate the data for appropriate presentation to the user
|
|
|
|
Control Class
|
An object class that contains application logic; coordinate messages between interface classes and entity classes and the sequences in which the messages occur
|
|
|
|
Persistence Class
|
An object class that provides functionality to read and write persistent (those that continue to exist beyond when the system is running) attributes in a database; makes entity classes more reusable
|
|
|
|
System Class
|
An object class that handles operating system-specific functionality
|
|
|
|
Dependency Relationship
|
Models the association between two classes in two instances: to indicate that when a change occurs in one class, it may affect the other class; and to indicate the association between a persistent class and a transient class; illustrated with a dashed arrow line
|
|
|
|
Navigability
|
Association between classes are bidirectional; however, messages can be sent from one class to another in only one direction as well
|
|
|
|
Visibility
|
The level of access an external object has to an attribute or method
|
|
|
|
Three Levels of Visibility
|
Public (+); Protected (#); Private (-)
|
|
|
|
Public Attributes/Methods
|
Attributes can be accessed and methods can be invoked by any other methods in any other class
|
|
|
|
Protected Attributes/Methods
|
Attributes can be accessed and methods can be invoked by any method in the class in which the attribute/method is defined or in subclasses of that class
|
|
|
|
Private Attributes/Methods
|
Attributes can be accessed and methods can be invoked by any method in the class in which the attribute/method is defined
|
|
|
|
Method
|
The software logic that is executed in response to a message
|
|
|
|
Object Responsibility
|
The obligation that an object has to provide a service when requested and thus collaborate with other objects to satisfy the request when required
|
|
|
|
Process of Object-Oriented Design
|
Refine the use-case model to reflect the implementation environment; Model class interactions, behaviors, and states that support the use-case scenario; Update the class diagram to reflect the implementation environment
|
|
|
|
Process of Refining the Use-Case Model
|
Transform “Analysis” use cases to “Design” use cases; Update the use-case model diagram and other documentation to reflect any new use cases
|
|
|
|
Process of Modeling Class Interactions/Behaviors/States
|
Identify and classify use-case design classes; Identify class attributes; Identify class behaviors and responsibilities; Model Object States
|
|
|
|
Class Responsibility Collaboration (CRC) Card
|
A popular tool for identifying which behaviors should be associated with which class, and for identifying collaboration among classes
|
|
|
|
Sequence Diagram
|
A UML diagram that models the logic of a use case by depicting the interaction of messages between objects in time sequence
|
|
|
|
Object State
|
A condition of the object at one point in its lifetime
|
|
|
|
State Transition Event
|
An occurrence that triggers a change in an object's state through the updating of one or more of its attributes' values
|
|
|
|
State Machine Diagram
|
A UML diagram that depicts the combination of states that an object can assume during its lifetime, the events that trigger transitions between states, and the rules governing the objects' transition. Also called a statechart diagram or state transition diagram
|
|
|
|
Role-Playing
|
The act of simulating object behavior and collaboration by acting out an object's behaviors and responsibilities
|
|
|
|
Design Class Diagram
|
A diagram that depicts classes that respond to software components that are used to build the software application
|
|
|
|
Systems Construction
|
The development, installation, and testing of system components
|
|
|
|
Systems Implementation
|
The installation and delivery of the entire system into production
|
|
|
|
Tasks of the Construction Phase
|
Build and Test Networks; Build and Test Databases; Install and Test Software Packages; Write and Test New Programs
|
|
|
|
Unpopulated Database Structure
|
The database structure is implemented, but data has not been loaded
|
|
|
|
First Task Specific to the Applications Programmer
|
Install and Test New Software Packages
|
|
|
|
Chief Programming Teams Strategy
|
Strategy that breaks programmers up into teams, led by the chief programmer
|
|
|
|
Levels of Testing
|
Stub, Unit/Program, and Systems
|
|
|
|
Stub Testing
|
Testing performed on a subset of a program
|
|
|
|
Unit/Program Test
|
A test performed on an entire program
|
|
|
|
Systems Test
|
A test performed on the entire system
|
|
|
|
Tasks of the Implementation Phase
|
Conduct Final System Test; Prepare Conversion Plan; Install Databases; Train System Users; Convert to New System
|
|
|
|
Common Installation Strategies
|
Abrupt Cut-Over; Parallel Conversion; Location Conversion; Staged Conversion
|
|
|
|
Abrupt Cut-Over
|
On a specific date, the old system will be terminated and the new system will be placed into operation
|
|
|
|
Parallel Conversion
|
The new and old systems will be operated at the same time for a specific period
|
|
|
|
Location Conversion
|
The system is converted at one geographic location, and will spread to the others if successful
|
|
|
|
Staged Conversion
|
Each version of the system is converted as it is developed
|
|
|
|
Systems Acceptance Test
|
A test performed on the final system wherein users conduct verification, validation, and audit tests
|
|
|
|
Verification Testing
|
Runs the system in a simulated environment using simulated data; also called “alpha testing”
|
|
|
|
Validation Testing
|
Runs the system in a live environment using real data; also called “beta testing”
|
|
|
|
Items Tested During Beta Testing
|
Systems Performance; Peak Workload Processing Performance; Human Engineering Test; Methods and Procedures Test; Backup and Recovery Testing
|
|
|
|
Audit Testing
|
A test performed to ensure that the system is free of errors and is ready to be put into operation
|
|
|
|
Most Common Medium of Computer Output |
Paper |
|
