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;
83 Cards in this Set
- Front
- Back
|
Data Modelling |
Creating a layout of information fields to organize data |
|
|
External Data Model |
Depiction of the database from viewpoints of individual user groups. |
|
|
Conceptual Data Model |
How basic concepts are defined and related with one another. |
|
|
Logical Data Model |
Shows layout of data, size and type of data and how objects relate to one another. |
|
|
Physical Data Model |
Technical details of implementation |
|
|
Entity - Relationship Diagram |
Relationship between database entries. |
|
|
Entity |
Collection or sets of things e.g. Students, orders, opportunities etc. |
|
|
Primary Key |
A unique identifier. ex. a student id. |
|
|
Foreign Key |
A field installed in an entity that refers to a primary key field. |
|
|
Cardinality |
The number of instances in one entity which are associated with ones in another |
|
|
Characteristics of primary key |
1. Unique 2. Mandatory 3. Only one primary key per entity |
|
|
Unique - primary key |
no duplicates allowed (ex. student id) |
|
|
Mandatory - primary key |
Must have a value |
|
|
Only one primary key per entity? |
Can only be one primary key |
|
|
Derived Attributes? |
Value can be determined from other attribute values. e.g age --> calculated from date of birth |
|
|
IT FlowChart |
1. Interests 2. Research 3. Finding Options 4. Applying and Studying 5. Getting Basic Experience 6. Networking |
|
|
Executive Duties |
1. Initiatives to support business 2. Bridge between technology and business 3. Budgeting, long term planning 4. Managing people 5. Assigning duties |
|
|
Manager Duties |
1. Manage day to day management 2. Project management 3. Risk management 4. Tactical thinking 5. Time management 6. Staff management |
|
|
Administrators Duties |
1. Monitor key hardware and software 2. Action problems 3. Create reports on issues 4. Ensure service level agreements are met 5. Fix issues and upgrades |
|
|
Analyst Duties |
1. Document and gather needs from users 2. Report on status of project 3. Test applications |
|
|
Developer Duties |
1. Translate requests filtered through analysts into working application |
|
|
Support Duties |
1. Fixing issues 2. Training users in applications 3. Help with applications |
|
|
MCSD? |
Microsoft certified software designer |
|
|
CISSP |
Certified Information Systems security professionals |
|
|
Knowledge Management |
Identifying, capturing, evaluating, receiving and sharing all of an enterprises information assets |
|
|
Data |
Raw facts that describe a particular phenomenon |
|
|
Information |
Data that have a particular meaning within a specific context |
|
|
Knowledge |
A meaningful organization of information, expressing an understanding of a subject and potential for action. |
|
|
Knowledge management names? |
1. Information management 2. Data management 3. Intellectual capital |
|
|
Objective of knowledge management? |
1. manage 2. share 3. Knowledge assets that help meet strategic and tactical requirements |
|
|
Organization culture? |
The organizational culture influences the way people interact, the resistance they have to certain changes and the way they share knowledge |
|
|
Enterprise Resource Planning |
- Ensuring that all pieces of an organization talk to each other - Facilitates flow of information between different business units |
|
|
Politics |
The long - term support to implement and sustain initiatives |
|
|
Emerging Technology Lifecycle |
1. Technology trigger 2. Peak of inflated expectations 3. Trough of disillusionment 4. Slope of enlightenment 5. Plateau of productivity |
|
|
Frameworks |
Managing information to industry standards |
|
|
ISO 9000 |
Quality management - Make sure your products and services meet customers needs |
|
|
ISO 45001 |
Occupational Health and Safety |
|
|
ISO 26000 |
Social Responsibility |
|
|
ISO 31000 |
Risk Management |
|
|
ISO Standards |
Frameworks that provide requirements, guidelines or characteristics that are used to ensure that products are fit for their purpose. |
|
|
Balanced Scorecard |
1. Used to align business activities to vision and strategies of the organization 2. Improve internal and external communications 3. Monitor organization performance against strategic goals. |
|
|
ITIL |
Information Technology Infrastructure Library |
|
|
COBIT |
Bridging gap between technical issues, business units and control requirements |
|
|
ISO/IEC 38500 |
1. Responsibility 2. Strategy 3. Acquisition 4. Performance 5. Conformance 6. Human Behaviour |
|
|
ISO/IEC 27002 |
Provides best practise recommendations on information security management |
|
|
Balanced Scorecard: Views an organization from four perspectives |
1. Financial 2. Internal 3. Customer 4. Organizational |
|
|
Balance Scorecard - Information Technology Scorecard |
1. Strategic Value 2. Innovative Value 3. Internal Customer Value 4. External Customer Value |
|
|
Goals of ITIL |
1. Business service provider, rather than back end support. 2. Best practises to align IT actions and expenses to business needs and change them as the business grows |
|
|
7 Improvement Practises for ITIL |
1. What should you measure? 2. What can be measured? 3. Gather data 4. Process data 5. Analyze data 6. Present Information 7. Implement Corrective Action |
|
|
COBIT 5 Processes |
1. Align 2. Build 3. Deliver 4. Monitor |
|
|
Metrics |
Numbers that tell you information about ..... 1. How a process is functioning 2. Process for suggesting improvement |
|
|
Efficiency |
Doing something in the right way so that it takes the least time, and money and fewest errors |
|
|
Effectiveness |
Doing the right thing |
|
|
Business Analysis? |
Practise of enabling change: 1. Defining needs and recommending solutions 2. Articulate needs, design solutions that can deliver value. |
|
|
Business Analysis Activities |
1. Analyze current state of organization 2. Define the future state of the organization 3. Requirements analysis and design definition of future state 4. Prioritize and approve requirements 5. Asses risks 6. Solution Evaluation 7. Planning and monitoring |
|
|
Data Flow Diagramming |
1. What a business entity does
2. To what standard a process should be completed 3. How success of business processes can be determined |
|
|
Activity Diagrams |
Follows flow of information in a systematic approach. Identifies different roles |
|
|
Data Dictionary |
Describes the contents, format and structure of a database and relationship between elements. |
|
|
When is a data dictionary beneficial? |
When trying to create mash-up with different systems accessing and interacting with a common database. |
|
|
Data Modelling |
Using text and symbols to describe the way data needs to flow. |
|
|
UML Diagrams |
Visualize interactions between people and systems |
|
|
Software Design |
The process of implentating software systems to one or more sets of problems |
|
|
SDLC |
Software Development Lifecycle |
|
|
SDLC Phases |
1. Requirement 2. Design 3. Implemetation 4. Testing 5. Evolution |
|
|
Cons to Waterfall Method |
1. Scope changes 2. As project proceeds, the initial design may need to be changed as systems are used |
|
|
Agile Software Development uses |
1. Promotes adaptive plans 2. Evolutionary Development 3. Early Delivery 4. Continuous Improvement |
|
|
Pros of Agile Software Development |
Changes are made from real - world results |
|
|
Cons of Agile Software Development |
1. Poor design can result in band aid fixes 2. More difficult with large systems 3. Less control of development 4. Less Documentation 5. Skilled developers |
|
|
software as a Service |
A software distribution model in which a third - party hosts applications and makes them available to customers over the internet |
|
|
Pros of Software as a Service |
1. No capital investment 2. No infrastructure needed 3. No expertise in back end system needed 4. Predictable costs 5. No maintenance fees |
|
|
Waterfall Methodology |
1. Planning 2. Analysis 3. Design 4. Development 5. Testing 6. Implementation 7. Maintenance |
|
|
Three primary activities of the planning phase for waterfall method |
1. Define system to be developed 2. Set the scope 3. Develop project plan |
|
|
Analysis: Waterfall Method |
1. Gather business requirements 2. Prioritize requirements |
|
|
Design: Waterfall Method |
1. Technical architecture: Hardware, software, and telecommunications equipment 2. System Models: Sample screens and reports |
|
|
Development: Waterfall Method |
The development phase takes the details of the design documents and changes them into an actual working system |
|
|
What are the two primary development activities for the waterfall method? |
1. Technical architecture 2. Database Programs |
|
|
Testing: Waterfall method |
- Verifies that the system works and meets all of the business requirements. |
|
|
Two primary activities for test plan under the waterfall method |
1. Creating the test plan 2. Doing the tests |
|
|
What are the three kinds of testing that need to be done under the waterfall method? |
1. Unit Testing 2. System Testing 3. Integration Testing 4. User Acceptance Testing |
|
|
Implementation Phase: Waterfall |
The system is distributed to users who begin to use it in their daily activities |
|
|
Two main implementation activities under the waterfall method? |
1. Writing detailed user documentation on how to use new training system 2. Training users either on - line or in workshops |
|
|
Maintenance Phase: Waterfall Method |
New systems are monitored and supported (ongoing) to meet business goals |
|
|
Two primary maintenance activities (Waterfall method) |
1. Setting up help desks so users questions can be answered 2. Providing a support environment so that system corrections are identified, assessed and implemented. |
