Term
| Phased approach to building an information system (the “Waterfall Model”) |
|
Definition
Planning Phase
Analysis Phase
Design Phase
Implementation Phase
Operation, Support, and Security Phase |
|
|
Term
|
Definition
| Triggered by a project request |
|
|
Term
|
Definition
Preliminary Investigation
Detailed Analysis
System Proposal |
|
|
Term
| Analysis Phase: Preliminary Investigation |
|
Definition
Documentation review
Observation
Surveys
Interviews
Focus groups
Research |
|
|
Term
| Analysis Phase: Feasibility |
|
Definition
Feasibility Assessment Criteria
Operational – how well will the system work?
Schedule – are deadlines reasonable?
Technical – can resources be obtained?
Economic – cost/benefit over lifetime of system |
|
|
Term
| Analysis Phase: Detailed Analysis |
|
Definition
Logical Design
No specific hardware or software
3 major activities:
How does the current system work?
What are the requirements?
Recommend a solution: system proposal |
|
|
Term
| Analysis Phase: System Proposal |
|
Definition
Assess solution choices
Packaged software
Custom software
Pros:
may provide a better fit
(meet requirements more closely)
provide professional development opportunities for staff
Cons:
more time to develop
more $$$
Outsourced
In-house |
|
|
Term
| Design Phase: Hardware and Software Acquisition |
|
Definition
Identifying Technical Specifications
Soliciting Vendor Proposals
Request for Information (RFI)
Request for Proposal (RFP)
Request for Quote (RFQ)
Testing and Evaluating Vendor Proposals
References, Demonstrations, Benchmarks
Making a Decision |
|
|
Term
| Design Phase: Detailed Design |
|
Definition
Databases
User Interface
Inputs
Data entry
Forms
Menus
Validation
Outputs
Reports
Displays |
|
|
Term
|
Definition
Construct new system and deliver to users
Program development (custom software)Write/modify programs based on design specification
Installation and Testing
Training
System Conversion |
|
|
Term
|
Definition
Unit tests: individual components work by themselves
System tests: components work together
Integration tests: system works with other systems/software
Acceptance test: end users verify “live data” operation |
|
|
Term
| Implementation Phase: System Conversion Strategies |
|
Definition
irect: “cold turkey”, stop using old system, start using new
Pro: No transition costs
Con: Risky
Parallel: both systems used
Pro: New system problems easier to fix
Con: Costs of running two systems
Phased: different groups start using new system at different times
Pilot: one group starts using new system, others convert after pilot group approval |
|
|
Term
| Operation, Support, and Security Phase |
|
Definition
Maintain System
Bug fixes and system enhancements
Monitor Performance
Efficiency and stability
Assess Security
Computer security plan
Balance risk management vs. ease of use |
|
|
Term
| Program Development Life Cycle (PDLC |
|
Definition
Analysis
Design
Design Validation
Design Implementation
Testing
Documentation |
|
|
Term
| Programming Languages and Program Development Tools |
|
Definition
Computer program
Series of instructions which direct a computer to perform tasks
Programmer, Developer, Software Engineer
Programming language
Set of words, abbreviations, symbols
Communicate instructions to computers
Several hundred exist
Low-level, high level languages
Program development tools
Integrated Development Environment |
|
|
Term
| Low-Level Programming Languages |
|
Definition
Machine-dependent (runs on one type of computer)
One language instruction = one machine instruction
Tedious and time-consuming
Assembly language
“2GL”
Source program
(Source code) |
|
|
Term
| High-Level Programming Languages |
|
Definition
Machine-independent (runs on different types of computers)
One (“English-like”) language instruction = multiple machine instructions
Compiler converts source into machine language
Checks for errors during compilation
Program runs after compilation
Interpreter reads and converts one language instruction at a time (“on the fly”)
Procedural Languages |
|
|
Term
|
Definition
|
|
