Flashcard Set Preview
| Side A | Side B | ||
| 1 |
Organized collection of logically related data
|
Database
|
|
| 2 |
stored representations of meaningful objects and events
|
Data
|
|
| 3 |
2 types of Data.
|
>structured>unstructured
|
|
| 4 |
what type of data are numbers, text and dates?
|
Structured
|
|
| 5 |
what type of data are images, videos and documents
|
unstructured
|
|
| 6 |
what does UML stand for?
|
Unfinished Modelling Languages
|
|
| 7 |
helps users understand data
|
context
|
|
| 8 |
turn data into useful information that managers can use for decision making and interpretation
|
graphical display
|
|
| 9 |
Descriptions of the properties or characteristics of the data, including data types, field...
|
Metadata
|
|
| 10 |
5 Disadvantages of File Processing
|
>Program-data dependence>Duplication of Data/ data redundancy>Limited Data Sharing>Lengthy...
|
|
| 11 |
disadvantage of file processing where All programs maintain metadata for each file they use
|
Program-data dependence
|
|
| 12 |
disadvantage of file processing where different systems/programs have seperate copies of the...
|
duplication of data/data redudancy
|
|
| 13 |
disadvantage of file processing where there is no centralized control of data
|
Limited Data sharing
|
|
| 14 |
disadvantage of file processing where programmers must design their own file formats
|
Lengthy development time
|
|
| 15 |
Disadvantage of file processing where 80% of information systems budget is used.
|
Excessive program Maintenance
|
|
| 16 |
5 Problems with data dependency
|
>Each application programmer must maintain his/her own data>each application program...
|
|
| 17 |
Problems with duplication of data/ data redundancy
|
>waste of space to have duplicate data>causes more maintenance headaches>The biggest...
|
|
| 18 |
Solution to file processing disadvatages.
|
Database Approach
|
|
| 19 |
3 database approaches
|
>Central repository of shared data>data is managed by controlling agent>stored in...
|
|
| 20 |
What does the database approach require?
|
Database Management System(DBMS)
|
|
| 21 |
what does DBMS stand for?
|
database management system.
|
|
| 22 |
a software system that is used to create, maintain and provide controlled access to user databases.
|
Database management system
|
|
| 23 |
manages data resources like an operating system manages hardware resources
|
Database management system
|
|
| 24 |
contains employee, order, inventory, pricing and customer data.
|
Central database
|
|
| 25 |
10 Advanatages of the Database Approach
|
>Program-data independence>Planned data redudancy>Improved data consistency>Improved...
|
|
| 26 |
costs and risks of the database approach
|
>New, specialized personnel>Installation and management cost and complexity>conversion...
|
|
| 27 |
Elemets of the database approach
|
>Data Models>Relational Databases>Use of Internet Technology>Database Applications
|
|
| 28 |
Graphical system capturing nature and relationship of data
|
Data mdels
|
|
| 29 |
High-level entities and relationships for the organization
|
Enterprise data model
|
|
| 30 |
more detailed view, matching data structure in database or data warehouse
|
Project Data Model
|
|
| 31 |
2 typs of data models
|
>Enterprise Data Model>Project Data Model
|
|
| 32 |
Database technology involving tables(relations) representing entities and primary/ foreign...
|
Relational Database
|
|
| 33 |
Networks and telecommunications , distributed database , client server and 3-tier...
|
Use of Internet Technology
|
|
| 34 |
Application programs used to perform database activities(create, read, update and delete) for...
|
Database application
|
|
| 35 |
Components of teh Database Environment
|
>CASE tools>Repository>Database management System (DBMS)>Database>Application...
|
|
| 36 |
Computer-aided software engineering
|
Case tools
|
|
| 37 |
what does CASE stand for
|
Computer-aided Software Engineering
|
|
| 38 |
Centralized storehouse of metadata
|
Repository
|
|
| 39 |
Software for managing the database
|
Database Management System(DBMS)
|
|
| 40 |
Software using the data
|
Application Programs
|
|
| 41 |
Text and graphical displays to users
|
User Interface
|
|
| 42 |
Personnel responsible for maintaining the database
|
Data/database Administrators
|
|
| 43 |
personnel responsible for designing database and software
|
System Developers
|
|
| 44 |
People who use the applications and databases
|
End Users
|
|
| 45 |
The range of database applications
|
>personal Database> workgroup databases>departmental/ divisional databases>Enterprise...
|
|
| 46 |
2 tparts of Enterprise Database Applications
|
>Enterprise Resource Planning (ERP)>Data Warehouse
|
|
| 47 |
Integrate all enterprise functions(manufacturing, finance, sales , marketing , inventory ,...
|
Enterprise Resource Planning(ERP)
|
|
| 48 |
Integrated decision support system derived from various operational database
|
Data Warehouse
|
|
| 49 |
First step in database development
|
Enterprise Data Model
|
|
| 50 |
Specifies scope and general content
|
Enterprise Data model
|
|
| 51 |
Overall picture of organizational data at high level of abstraction
|
Enterprise Data model
|
|
| 52 |
Has Entity-relationship diagram, description of entity types, relationships between...
|
Enterprise data model
|
|
| 53 |
describes the high-level entities in an organization and the relationship between these.
|
Enterprise data model
|
|
| 54 |
what does ISA stand for?
|
Information System Architecture (ISA)
|
|
| 55 |
Conceptual blueprint for organization's desired information system structure
|
Inforamtion System Architecture (ISA)
|
|
| 56 |
The Inforamation Systems Architecture (ISA) consists of ;
|
>Data>Processes>Data Network>People>Events and points in time> reasons for...
|
|
| 57 |
(e.g. Enterprise Datamodel- simplified ER diagram)
|
Data
|
|
| 58 |
data flow diagrams, process decomposition, etc.
|
processes
|
|
| 59 |
topology diagram
|
data network
|
|
| 60 |
people management using project management tools(Gantt charts, etc.)
|
People
|
|
| 61 |
(when processes are performed)
|
Events and points in time
|
|
| 62 |
(e.g., decision tables)
|
reasons for events and rules
|
|
| 63 |
A data-oriented methodology to create and maintain information systems
|
Information Engineering
|
|
| 64 |
A generic Information Systems planning methodology for obtaining a broad understanding...
|
Top-down Planning
|
|
| 65 |
four steps to Top-down planning:
|
>Planning>analysis>Design>Implementation
|
|
| 66 |
Purpose of Information Systems Planning;
|
to align information technology with an organization's business strategies.
|
|
| 67 |
3 steps in Information Systems planning:
|
> Identify Strategic planning factors>Identify corporate planning objects>Develop...
|
|
| 68 |
what we hope to accomplish
|
Organization goals
|
|
| 69 |
what must work in order for us to survive
|
Critical success factors
|
|
| 70 |
weakness we now have
|
Problem areas
|
|
| 71 |
Identify strategic Planning factors;
|
>organization goals>Critical success factors>Problem areas
|
|
| 72 |
Identify corporate planning objects
|
> organizational units> organizational locations>business functions>entity...
|
|
| 73 |
departments
|
Organizational units
|
|
| 74 |
groups of business processes
|
Business fuctions
|
|
| 75 |
the things we are trying to model for the database
|
Entity types
|
|
| 76 |
application programs
|
Information Systems
|
|
| 77 |
Interactive process breaking system description into finer and finer detail
|
Functional decomposition
|
|
| 78 |
Describes interrelationships between planning objects
|
Planning matrixes
|
|
| 79 |
breaking large tasks into smaller tasks in a hierarchical structure chart
|
Decomposition
|
|
| 80 |
Describes relationships between planning objects in the organization
|
Planning Martixes
|
|
| 81 |
6 types of matrixes;
|
>unit-to-function>location-to-function
>Supporting function-to-data entity
>function-to-data...
|
|
| 82 |
what does SDLC stand for?
|
System Development Life Cycel
|
|
| 83 |
-Detailed, well-planned development process- time-consuming but comprehensive-long dveleopment...
|
System Development Life Cycle (SDLC)
|
|
| 84 |
-Rapid Application Development(RAD)-Cursory attempt at conceptual data modeling-Define Database...
|
Prototyping
|
|
| 85 |
What does RAD stand for?
|
Rapid Application Development
|
|
| 86 |
2 approaches to database and IS development
|
> SDLC>Prototyping
|
|
| 87 |
SDLC
|
planning<>analysis<>logical design<> physical design<> implementation...
|
|
| 88 |
purpose of planning:
|
Preliminary understanding
|
|
| 89 |
deliverable of planning:
|
request of study
|
|
| 90 |
database activity of planning:
|
enterprise modeling and early conceptual data modeling.
|
|
| 91 |
purpose of analysis:
|
Thorough requirements analysis and structuring.
|
|
| 92 |
deliverable of analysis:
|
fuctional system specifications
|
|
| 93 |
database activity of analysis:
|
Thorough and integrated conceptual data modeling.
|
|
| 94 |
purpose of logical design:
|
Information requirements elicitation and structure
|
|
| 95 |
deliverable of logical design:
|
detailed design specifications
|
|
| 96 |
database activity of logical design:
|
Logical database design(transactions, forms displays, views, data integrity and...
|
|
| 97 |
purpose of Physical Design:
|
Develop technology and organizational specifications.
|
|
| 98 |
deliverable of Physical Design:
|
Program/data structures, technology purchases, organization redesigns
|
|
| 99 |
database activity of Physical Design
|
Physical Database design(define database to DBMS, physical data organization, database processing...
|
|
| 100 |
purpose of implementation:
|
Programming, testing, training, installation, documenting
|
|
| 101 |
deliverable of implementation:
|
Operational programs, documentation, training materials
|
|
| 102 |
database activity of implementation:
|
database implementation, including coded programs, documentation, installation and conversion
|
|
| 103 |
Purpose of Maintenance
|
monitor, repair , enhance
|
|
| 104 |
deliverable of maintenance
|
periodic audits
|
|
| 105 |
database activity of maintenance:
|
database maintenance, performance analysis, and tuning, error corrections
|
|
| 106 |
Prototying database methodology:
|
>identify problem>develop initial prototype>implement and use prototype>if inefficient;...
|
|
| 107 |
steps in Conceptual data modelling
|
>Analyze requirements>Develop preliminary data model
|
|
| 108 |
steps in Logical database design
|
>analyze requirements in detail>Integrate database views into conceptual data...
|
|
| 109 |
steps in Physical database design and definition
|
>define new database contents to DBMS>decide on physical organization for new data>design...
|
|
| 110 |
steps in database implementation:
|
>code database processing>install new database contents, usually from existing data sources
|
|
| 111 |
steps on database maintenance:
|
>analyze database to ensure it meets application needs>fix errors in database
|
|
| 112 |
steps in database maintenance when converting prototype to operational system.
|
>tune database for improved performance>fix errors in database
|
|
| 113 |
software tools providing automated support for systems development
|
Computer-aided software engineering (CASE)
|
|
| 114 |
three database features of computer-aided software engineering:
|
>Data modelling>code generation>repositories
|
|
| 115 |
drawing entity relationship diagrams
|
data modeling
|
|
| 116 |
SQL code for table creation
|
Code generation
|
|
| 117 |
knowledge base of enterpprise information
|
Repositories
|
|
| 118 |
Model components that can be purchased, customize, and assembled into full-scale data models
|
Packaged Data models
|
|
| 119 |
Advantages of Packaged Data Models
|
>Reduced development time>higher model quality and reliability
|
|
| 120 |
Two types of packaged data models:
|
>universal data models>industry-specific data models
|
|
| 121 |
a planned undertaking of related activities to reach an objective that has a beginning and...
|
Project
|
|
| 122 |
Managing Projects Involves use of review points for:
|
>Validation of satisfactory progress>step back from detail to overall view>Renew...
|
|
| 123 |
Review of systems development project after each development phase with rejustification after...
|
Incremental Commitement
|
|
| 124 |
People Involved in Managing Projects:
|
>Business Analyst>System Analyst>Database Analyst and data Modelers>users>programmers>database...
|
|
| 125 |
Database Schemas
|
> Internal Schema> conceptual Schema>External Schema
|
|
| 126 |
Schema concerned with Physical structures
|
Internal Schema
|
|
| 127 |
Schema concerned with E-R Models
|
Conceptual Schema
|
|
| 128 |
>User views>subsets of conceptual schema>can be determine from business- function/data...
|
External Schema
|
|
| 129 |
is the underlying design and implementation
|
Internal Schema
|
|
| 130 |
AIP, AIR, order processing, inventory control, and so forth; access and connectivity to DBMS...
|
Application/Web server
|
|
| 131 |
contains all organizational data or summaries of data on department servers.
|
Transaction Database
|
|
| 132 |
work with both management and users to analyze the business situation and develop detailed...
|
Business Analysts
|
|
| 133 |
May perform business analyst activities but also specify computer systems requirements and...
|
System Analysts
|
|
| 134 |
Concentrate on determining the requirements and design for the database component...
|
Database Analysts and data modelers
|
|
| 135 |
Provide assessment of their information needs and monitor that the developed system meets their...
|
Users
|
|
| 136 |
Design and write computer programs that have commands to maintain adn access data...
|
Programmers
|
|
| 137 |
Establish standards for data in business units, striving to attain optimum data location, currency...
|
Database Architects
|
|
| 138 |
have responsibility for existing and future databases and ensure consistency and integrity...
|
Data administrators
|
|
| 139 |
oversee assigned projects, including team composition, analysis, deign, implementation and...
|
project managers
|
|
| 140 |
for example, networking, operating systems, testing , data warehousing and documentation
|
Other technical experts
|
|
| 141 |
schema for the user views
|
External Schema
|
|
| 142 |
integrates external schemata
|
Conceptual Schema
|
|
| 143 |
schema that defines physical storage structures
|
Internal Schema
|
No comments yet! Be the first to add a comment below!
Please login to post comments.
After login, we will forward you back to this flashcard.