The document discusses data warehousing and business intelligence. It provides an overview of data warehouses, their components like the ETL process, data marts and OLAP. It also discusses the steps to create a data warehouse like understanding business needs, data modeling, ETL development and testing. Business intelligence is defined as using organizational capabilities to generate knowledge and opportunities.
WordPress in the enterprise - can it work?DMWMartin
WordPress can be used in enterprise environments when more than one person takes responsibility for core competencies like development, maintenance, support, security and governance. Some challenges for WordPress in enterprise include integration, skills gaps, multiple teams, open source trust, and security. Enablers include single sign-on, agile teams, slower upgrades, external support and third party products. Ongoing issues involve shifting costs from the platform to building core competencies while maintaining flexibility, and balancing flexibility with enterprise demands for control. Bridging this gap may involve separate security patches, trusted repositories, and supporting legacy releases similar to Ubuntu's approach.
This document provides a menu for a restaurant. It lists options for starters, salads, main courses, kids meals, desserts, coffee, tea, and drinks. Starters include bruschetta, dumplings, and spring rolls. Salads include caesar, chicken, and prawn salads. Main courses range from lasagna and linguini to seafood, lamb shank, and steak. Kids meals, desserts like tiramisu, and beverage options are also outlined. The menu provides a wide variety of food and drink choices.
Publishing content is like speaking in a crowded room — if no one can hear you your content isn’t doing any good.
Are you struggling to get your audience to take action? Do you want to improve your outreach strategy? If you are, check out these 20 tips to boost your public engagement and increase your digital ROI.
Need for efficient water infrastructure and its impact on water resources man...Mazen Alqadi
This document discusses the need for efficient water infrastructure and its impact on water resource management. It notes that population and economic growth are increasing water demand and leading to water stress situations. Efficient water infrastructure and technology advances can help alleviate this. The document advocates adopting a holistic water resource management approach using three pillars: policies, institutions, and infrastructure. Developing sustainable water and wastewater infrastructure through committed involvement of all stakeholders, including governments, regulators, administrators, operators, and NGOs, is key to managing available resources and demand. An equitable water tariff is also needed to encourage conservation and ensure sustainability.
WordPress in the enterprise - can it work?DMWMartin
WordPress can be used in enterprise environments when more than one person takes responsibility for core competencies like development, maintenance, support, security and governance. Some challenges for WordPress in enterprise include integration, skills gaps, multiple teams, open source trust, and security. Enablers include single sign-on, agile teams, slower upgrades, external support and third party products. Ongoing issues involve shifting costs from the platform to building core competencies while maintaining flexibility, and balancing flexibility with enterprise demands for control. Bridging this gap may involve separate security patches, trusted repositories, and supporting legacy releases similar to Ubuntu's approach.
This document provides a menu for a restaurant. It lists options for starters, salads, main courses, kids meals, desserts, coffee, tea, and drinks. Starters include bruschetta, dumplings, and spring rolls. Salads include caesar, chicken, and prawn salads. Main courses range from lasagna and linguini to seafood, lamb shank, and steak. Kids meals, desserts like tiramisu, and beverage options are also outlined. The menu provides a wide variety of food and drink choices.
Publishing content is like speaking in a crowded room — if no one can hear you your content isn’t doing any good.
Are you struggling to get your audience to take action? Do you want to improve your outreach strategy? If you are, check out these 20 tips to boost your public engagement and increase your digital ROI.
Need for efficient water infrastructure and its impact on water resources man...Mazen Alqadi
This document discusses the need for efficient water infrastructure and its impact on water resource management. It notes that population and economic growth are increasing water demand and leading to water stress situations. Efficient water infrastructure and technology advances can help alleviate this. The document advocates adopting a holistic water resource management approach using three pillars: policies, institutions, and infrastructure. Developing sustainable water and wastewater infrastructure through committed involvement of all stakeholders, including governments, regulators, administrators, operators, and NGOs, is key to managing available resources and demand. An equitable water tariff is also needed to encourage conservation and ensure sustainability.
The document discusses branding in advertising and music. It provides examples of how Cadbury and Coca-Cola use branding in their advertisements to convey emotional connections to their brands rather than directly promoting their products. Music branding is also examined, with One Republic used as an example of maintaining a consistent brand image across their music videos and album covers through elements like color schemes, imagery and themes. The document then proposes a brand image of "Quirky, Timeless, Unique" for a fictional music artist and analyzes how this brand would be conveyed through elements in a music video, album artwork and promotional materials.
El documento habla sobre las actividades de limpieza y cuidado del jardín de la escuela San José de Luruaco por parte de los niños de transición. Los niños ayudarán a limpiar el jardín, abonarlo y cuidarlo para mantenerlo en buenas condiciones.
Bibliografía:
B-Learning utilizando software libre,
una alternativa viable en Educación Superior
Julio César GONZÁLEZ MARIÑO
Universidad Autónoma de Tamaulipas. Mexico
LMS 2.0 - Tools for the Next Gen of LearnersTeamie
The document discusses the evolution of learning management systems (LMS) from LMS 1.0 to LMS 2.0. LMS 1.0 tools had low usage and usability, expensive customizations, and a non-intuitive user interface. However, the changing landscape with social media, mobile devices, and learning/workplace trends requires LMS 2.0 to be more social, collaborative, engage users with open/user-generated content, and facilitate learning anywhere on any device through the cloud. Key characteristics of LMS 2.0 include social communities, discovery/subscriptions, personalized learning, gamification, and cloud/mobile delivery to drive a more engaged and effective learning experience.
Dokumen tersebut membahas tentang regular expressions dan bahasa formal. Terdapat tiga operator utama pada regular expressions yaitu union, concatenation, dan closure. Regular expressions dapat digunakan untuk mendefinisikan bahasa formal dengan menggunakan konstanta, variabel, dan operator tersebut secara rekursif. Prioritas operator pada regular expressions adalah closure, concatenation, dan union.
This document discusses the difference between using "is" and "are" in sentences. "Is" is used when referring to one object or person, while "are" is used when referring to multiple objects or persons. Examples are provided showing the correct use of "is" and "are" based on whether the subject is singular or plural.
In this webinar, Richard Fong, Technical Solution Consultant with GovDelivery, will explain what an API is and why it’s so essential to the new federal Digital Government roadmap. He’ll provide insight into GovDelivery’s API, which helps automate previously manual processes so you can save time and resources on routine tasks. Richard will also share some exciting government success stories that illustrate how easily and successfully government agencies can leverage APIs to drive efficiency and engagement.
The document provides an overview of the Bible, including:
- It is divided into the Old Testament and New Testament
- The Old Testament contains the Pentateuch, Historical Books, Wisdom Books, and Prophetic Books
- The New Testament contains the Gospels, Acts of the Apostles, Pauline Letters, General Epistles, and Revelation
- There are differences in the contents of the Catholic and Protestant Bibles, with the Catholic version containing additional books.
La ecología estudia las interacciones entre organismos y su ambiente, determinando la distribución y abundancia de poblaciones biológicas. Es la síntesis de las ciencias naturales y conecta las ciencias naturales con las sociales. Los principios ecológicos son fundamentales para el desarrollo humano pero el crecimiento económico indefinido no es compatible con la conservación de la naturaleza. El gasto militar mundial supera en gran medida la inversión en conservación ambiental.
Stearns County Sheriff's Office was able to increase their crime prevention tips by 522% over the previous year. See what engagement strategies worked for Stearns County Sheriff's Office.
Best Practices in making Learning Social & FunTeamie
The document discusses best practices for building social learning networks. It outlines 5 key practices: 1) Build learning communities for ongoing learning discussions, 2) Create shared and collaborative multimedia content, 3) Share and build experiences through peer learning, 4) Reward participation through gamification, and 5) Facilitate collaborative learning rather than solely teaching. The key is that social and collaborative learning drives engagement better than formal education alone. Technology can enable the delivery of social learning experiences.
Laporan ini membahas pembuatan aplikasi pengelola gambar dengan Java Desktop. Aplikasi ini menggunakan komponen Swing, AWT Image, dan FileChooser untuk memilih dan mengelola gambar. Komponen-komponen tersebut dirancang khusus untuk pengelolaan gambar. Aplikasi ini mampu memilih, menampilkan, dan mengubah ukuran gambar.
This document discusses how elevated economic policy uncertainty since 2008 has increased equity risk premiums, diminished opportunities for stock picking, and favored defensive stocks over cyclical stocks. The author argues that economic policy uncertainty is highly correlated with these market factors and is the main driver of financial markets currently. However, the author believes economic policy uncertainty may have peaked globally and is poised to decline, which would have positive implications for equities, risk assets, and stock picking opportunities. If policy uncertainty declines, it could lower equity risk premiums and widen the stock picking opportunity set by making individual stocks' performances less correlated with the overall market.
The document provides an overview of relational database concepts and the Oracle database implementation. It describes the life cycle development phases, theoretical and conceptual aspects of relational databases, and how SQL is used with Oracle's RDBMS and ORDBMS. It also covers basic SQL statements like SELECT and restrictions, data types, database objects, SQL statements, operators, and comparisons that can be used with SQL.
SQL Server 2000 provides database functionality including tables, indexes, queries, and stored procedures. It allows for structured storage and retrieval of data. Key objects in SQL Server include databases, tables, indexes, and queries. Databases can be designed in normal forms to avoid data duplication and inconsistencies.
The document discusses branding in advertising and music. It provides examples of how Cadbury and Coca-Cola use branding in their advertisements to convey emotional connections to their brands rather than directly promoting their products. Music branding is also examined, with One Republic used as an example of maintaining a consistent brand image across their music videos and album covers through elements like color schemes, imagery and themes. The document then proposes a brand image of "Quirky, Timeless, Unique" for a fictional music artist and analyzes how this brand would be conveyed through elements in a music video, album artwork and promotional materials.
El documento habla sobre las actividades de limpieza y cuidado del jardín de la escuela San José de Luruaco por parte de los niños de transición. Los niños ayudarán a limpiar el jardín, abonarlo y cuidarlo para mantenerlo en buenas condiciones.
Bibliografía:
B-Learning utilizando software libre,
una alternativa viable en Educación Superior
Julio César GONZÁLEZ MARIÑO
Universidad Autónoma de Tamaulipas. Mexico
LMS 2.0 - Tools for the Next Gen of LearnersTeamie
The document discusses the evolution of learning management systems (LMS) from LMS 1.0 to LMS 2.0. LMS 1.0 tools had low usage and usability, expensive customizations, and a non-intuitive user interface. However, the changing landscape with social media, mobile devices, and learning/workplace trends requires LMS 2.0 to be more social, collaborative, engage users with open/user-generated content, and facilitate learning anywhere on any device through the cloud. Key characteristics of LMS 2.0 include social communities, discovery/subscriptions, personalized learning, gamification, and cloud/mobile delivery to drive a more engaged and effective learning experience.
Dokumen tersebut membahas tentang regular expressions dan bahasa formal. Terdapat tiga operator utama pada regular expressions yaitu union, concatenation, dan closure. Regular expressions dapat digunakan untuk mendefinisikan bahasa formal dengan menggunakan konstanta, variabel, dan operator tersebut secara rekursif. Prioritas operator pada regular expressions adalah closure, concatenation, dan union.
This document discusses the difference between using "is" and "are" in sentences. "Is" is used when referring to one object or person, while "are" is used when referring to multiple objects or persons. Examples are provided showing the correct use of "is" and "are" based on whether the subject is singular or plural.
In this webinar, Richard Fong, Technical Solution Consultant with GovDelivery, will explain what an API is and why it’s so essential to the new federal Digital Government roadmap. He’ll provide insight into GovDelivery’s API, which helps automate previously manual processes so you can save time and resources on routine tasks. Richard will also share some exciting government success stories that illustrate how easily and successfully government agencies can leverage APIs to drive efficiency and engagement.
The document provides an overview of the Bible, including:
- It is divided into the Old Testament and New Testament
- The Old Testament contains the Pentateuch, Historical Books, Wisdom Books, and Prophetic Books
- The New Testament contains the Gospels, Acts of the Apostles, Pauline Letters, General Epistles, and Revelation
- There are differences in the contents of the Catholic and Protestant Bibles, with the Catholic version containing additional books.
La ecología estudia las interacciones entre organismos y su ambiente, determinando la distribución y abundancia de poblaciones biológicas. Es la síntesis de las ciencias naturales y conecta las ciencias naturales con las sociales. Los principios ecológicos son fundamentales para el desarrollo humano pero el crecimiento económico indefinido no es compatible con la conservación de la naturaleza. El gasto militar mundial supera en gran medida la inversión en conservación ambiental.
Stearns County Sheriff's Office was able to increase their crime prevention tips by 522% over the previous year. See what engagement strategies worked for Stearns County Sheriff's Office.
Best Practices in making Learning Social & FunTeamie
The document discusses best practices for building social learning networks. It outlines 5 key practices: 1) Build learning communities for ongoing learning discussions, 2) Create shared and collaborative multimedia content, 3) Share and build experiences through peer learning, 4) Reward participation through gamification, and 5) Facilitate collaborative learning rather than solely teaching. The key is that social and collaborative learning drives engagement better than formal education alone. Technology can enable the delivery of social learning experiences.
Laporan ini membahas pembuatan aplikasi pengelola gambar dengan Java Desktop. Aplikasi ini menggunakan komponen Swing, AWT Image, dan FileChooser untuk memilih dan mengelola gambar. Komponen-komponen tersebut dirancang khusus untuk pengelolaan gambar. Aplikasi ini mampu memilih, menampilkan, dan mengubah ukuran gambar.
This document discusses how elevated economic policy uncertainty since 2008 has increased equity risk premiums, diminished opportunities for stock picking, and favored defensive stocks over cyclical stocks. The author argues that economic policy uncertainty is highly correlated with these market factors and is the main driver of financial markets currently. However, the author believes economic policy uncertainty may have peaked globally and is poised to decline, which would have positive implications for equities, risk assets, and stock picking opportunities. If policy uncertainty declines, it could lower equity risk premiums and widen the stock picking opportunity set by making individual stocks' performances less correlated with the overall market.
The document provides an overview of relational database concepts and the Oracle database implementation. It describes the life cycle development phases, theoretical and conceptual aspects of relational databases, and how SQL is used with Oracle's RDBMS and ORDBMS. It also covers basic SQL statements like SELECT and restrictions, data types, database objects, SQL statements, operators, and comparisons that can be used with SQL.
SQL Server 2000 provides database functionality including tables, indexes, queries, and stored procedures. It allows for structured storage and retrieval of data. Key objects in SQL Server include databases, tables, indexes, and queries. Databases can be designed in normal forms to avoid data duplication and inconsistencies.
This document provides an overview of key concepts for relational database design and maintenance. It discusses proper database design, relational database terminology, normalization techniques to eliminate data anomalies like insertion, deletion, and modification anomalies. The document also covers different table types, identifying primary keys, data dependencies, and strategies for enforcing referential integrity. Additional topics include lookup fields, indexes, different join types, and techniques for maintaining database performance and documentation.
The document discusses key concepts in relational database design and maintenance. It covers topics like proper database design, relational database terminology, characteristics of relational databases, building a relational database by designing tables and joining them, identifying different table types, primary keys, data dependencies, normalization to eliminate anomalies, and maintaining referential integrity between tables. The document uses examples to illustrate concepts like well-structured relations, different normal forms, lookup fields, composite primary keys, indexes, and join types between tables.
The document discusses data modeling and entity relationship diagrams. It defines data modeling as the process of defining and analyzing data requirements to support business processes. It describes the different types of data models including conceptual, logical, and physical models. It also explains the key components of entity relationship diagrams including entities, attributes, relationships, cardinality, and notation. The document provides an example of using an ERD to model a scenario involving departments, supervisors, employees, and projects.
The document discusses database design, including the goals of database design such as data availability, reliability, currency, consistency and flexibility. It describes the key components of database design - entities, attributes, and relationships. Entities are things about which data is gathered, attributes are properties of entities, and relationships describe how entities relate to each other. The document also covers logical data modeling, normalization, and the three forms of normalization - first, second and third normal form. The goal of normalization is to organize data to eliminate redundancy and inconsistent dependency.
The document discusses database design, including the goals of database design such as data availability, reliability, currency, consistency and flexibility. It describes the key components of database design - entities, attributes, and relationships. Entities are things about which data is gathered, attributes are properties of entities, and relationships describe how entities relate to each other. The document also covers logical data modeling, normalization, and the three forms of normalization - first, second and third normal form. The goal of normalization is to organize data to eliminate redundancy and inconsistent dependency.
The document discusses the relational database model and relational query languages. It describes the relational model as being over 35 years old but still the foundation of modern database systems. It is used by major commercial databases and provides a simple yet expressive model through query languages like SQL. The document defines key concepts like relations, attributes, tuples, domains, schemas, instances, and NULL values. It also covers topics like keys, views, and updating views in relational databases.
This document provides an overview of data mining. It defines data mining as the extraction of interesting patterns from large datasets. The document outlines different types of data mining tasks such as classification, clustering, and association rule mining. It also discusses motivations for data mining from both commercial and scientific perspectives, and provides examples of data mining applications.
The document provides an overview of the three-level ANSI-SPARC architecture for relational database management systems (RDBMS). It describes the external, conceptual, and internal levels of the architecture and how they provide logical and physical data independence. Keys such as primary keys, foreign keys, and alternate keys are also discussed as they relate to the relational data structure and ensuring data integrity across tables.
The document discusses IT6701 - Information Management, which covers topics such as database modeling, management and development, information governance, and information architecture. It describes objectives, units, database design, data modeling, entity relationship models, normalization, Java database connectivity, stored procedures, and big data technologies including Hadoop, HDFS, MapReduce, Hive and enhancements.
Michael Joseph is giving a presentation on database normalization. He begins by explaining the importance of properly structuring data across database tables and the problems that can arise from poor database design, such as redundancy, inaccuracy, and consistency issues. He then describes database normalization as a process that organizes data to minimize redundancy by decomposing relations and isolating data in separate, well-defined tables connected through relationships. Different levels of normalization are discussed, with third normal form being sufficient for most applications. Examples are provided to illustrate how normalization progresses from first to third normal form. Potential issues with highly normalized databases are also outlined.
This document provides an introduction to database management systems (DBMS) and MySQL. It defines a database as a collection of organized information that can be quickly accessed by a computer program. A DBMS helps create and manage databases, similar to how MS Word helps create documents. The document discusses the entity-relationship model and how entities are represented as tables with attributes as columns. It provides examples of creating tables, adding primary keys, and linking tables with foreign keys. It also explains the three types of SQL statements - DDL for defining the database structure, DML for managing data, and DCL for controlling access. Specific DDL, DML, and DCL commands are defined along with syntax examples.
This document provides an overview of database theory concepts that are important for understanding how Siebel Enterprise Applications interact with databases. It discusses database tables, keys, normalization, joins, links, and indices. Normalization is important for minimizing data duplication and defining relationships between tables. Many-to-many relationships require intersection tables. An understanding of these database concepts is essential for configuring Siebel's interaction with the underlying database.
The document provides an overview of data modeling and conceptual data modeling. It discusses key concepts in data modeling including entity relationship diagrams, attributes, domains, entity types, weak vs strong entities, and entity sets. It explains how data modeling follows analysis and documents business rules and policies to design a conceptual model of the database and relationships between data. The conceptual model is represented using an ERD.
Page 1 of 27 Tony LoCoco ITCO333 – Unit 2 August 2.docxalfred4lewis58146
Page 1 of 27
Tony LoCoco
ITCO333 – Unit 2
August 29, 2013
REQUIREM ENT S
• This database must contain examples of one
• I will compare your Unit 1 ERD with the Unit 2 database diagram. If there are differences, explain why.
• Present your SQL statements in the order in which they were executed.
• Put your database diagram at the top of your document (see my sample).
Each of your t
sample data (p
REL AT IONS HIP S
Relationship
Type
Entity #1 Entity #2
one-to-one (1:1) Advisors Employees
one-to-many (1:M) Employees Departments
one-to-many (1:M) Advisors Students
This database must contain examples of one-to-one, one-to-many and many-to-many relationships.
I will compare your Unit 1 ERD with the Unit 2 database diagram. If there are differences, explain why.
Present your SQL statements in the order in which they were executed.
Put your database diagram at the top of your document (see my sample).
tables must contain at least eight records of
per the assignment requirements).
Entity #2 Description / Justification
Employees An Advisor is an Employee with additional data
attributes. An Employee may or may not be an Advisor.
Departments A Department may have 0, 1 or many Employees
Employee is assigned to just one Department.
An Advisor may be assigned to 0, 1 or many Students and
a Student is assigned to just one Advisor.
many relationships.
I will compare your Unit 1 ERD with the Unit 2 database diagram. If there are differences, explain why.
An Advisor is an Employee with additional data
attributes. An Employee may or may not be an Advisor.
many Employees and an
An Advisor may be assigned to 0, 1 or many Students and
Page 2 of 27
many-to-many
(M:N)
Students Courses A Student be take 0 , 1 or many Courses and a Course can
contain 0, 1 or many Students.
Relational Databases can not support many-to-many
relationships. These M:N must be broken down into two
one-to-many relationships with a bridge entity
connecting the M:N entities. In this case, Student_Courses
is that bridge entity.
Page 3 of 27
D AT ABASE D IAGR AM
Page 4 of 27
UNIT 1 ERD
Emloyees
PK Employee_ID
Last_Name
First_Name
Birth_Date
Employment_Start_Date
Hourly_Pay
FK1 Department_ID
Manager_ID
Departments
PK Department_ID
Department_Name
Students
PK Student_ID
Last_Name
First_Name
Birth_Date
Enroll_Date
Status_Code
Total_Hours
FK1,FK2 Advisor_ID
Advisors
PK,FK1 Employee_ID
Certification_Level
Courses
PK Course_ID
Course_Code
Course_Name
Credit_Hours
Sessions
PK Session_ID
Session_Name
Session_Start_Date
Student_Courses
PK,FK1 Session_ID
PK,FK3 Course_ID
PK,FK2 Student_ID
Earned_Grade
Page 5 of 27
SQL D D L T O CREAT E D AT ABASE
USE [master]
GO
CREATE DATABASE ITCO333Database
GO
Page 6 of 27
CREAT E T ABL ES, F IEL D S , P RIM ARY K EY S & FOREIGN K EY / CREAT E D M L
USE .
The document discusses database normalization. It begins by defining normalization and describing its purpose in eliminating data redundancy and anomalies. The document then covers various normal forms including 1st normal form (1NF), 2nd normal form (2NF), 3rd normal form (3NF) and Boyce-Codd normal form (BCNF). It also defines key concepts like functional dependencies, full dependencies, partial dependencies and transitive dependencies. Examples are provided to illustrate the normalization process and how relations can be decomposed to remove anomalies through normalization.
The document provides an introduction to databases, including key concepts such as the three levels of viewing a database (data storage, database management system, and database applications). It discusses database types, normalization forms, common terminology like SQL, CRUD, and ACID. Examples of typical database architectures and applications are presented. The advantages of normalization for reducing redundancy and improving integrity are covered, along with some disadvantages like increased complexity and reduced efficiency for some queries.
This document provides an introduction to relational databases and SQL. It discusses key concepts such as:
- Relational databases contain multiple tables that are linked together through primary and foreign keys. This allows normalization of data to reduce redundancy.
- SQL is the standard language used to interact with relational database management systems. SQL can be used to query, manipulate, and define data.
- Common SQL statements include SELECT to query data, INSERT to add new records, UPDATE to modify existing records, and DELETE to remove records.
- Proper database design principles like normalization help ensure data integrity and optimize database performance by eliminating redundant or inconsistent data.
Similar to Data Warehousing and BI - Recruitment POV (20)
Cloud Strategies for Financial Firms : Migrating one step at a timeSuvradeep Rudra
A very few financial firms are currently using cloud computing for their core applications, different hosting architectures provided by IaaS cloud providers and new avenues in the community and hybrid cloud space, will drive more firms to move their core applications to the cloud. In fact, core solutions, such as batch processes running throughout the day, analytics and reporting applications, are perfect candidates.
The idea behind a design patterns is to learn about it's strengths and weaknesses. And more importantly, understand where and how to use a particular design correctly, so as to use its strengths properly and overcome its weaknesses.
In today's competitive market, many organizations are unaware of the quantity of poor-quality data in their systems. Some organizations assume that their data is of adequate quality, although they have conducted no metrical or statistical analysis to support the assumption. Others know that their performance is hampered by poor-quality data, but they cannot measure the problem.
This document discusses the differences between business intelligence (BI) and business analytics. BI involves monitoring and tracking metrics through reports and dashboards, while business analytics takes the analysis further by correlating metrics, understanding trends, and using statistical algorithms to predict outcomes. The document then provides details on building strategies around BI and analytics, including identifying problems, understanding current systems, creating a roadmap, categorizing problems as operational, tactical, or strategic, prioritizing metrics, assessing readiness, establishing benchmarks, monitoring performance, and citing additional resources.
When Jim Messina arrived as Obama's campaign manager in 2011, he mandated decisions be based on data. The campaign collected over 80 data points on voters and used analytics to build profiles. They tested strategies through computer simulations run daily. Based on analysis, they targeted fundraising, ads, volunteers and messages. This data-driven approach helped Obama identify and mobilize supporters, raising $1 billion and re-electing the president in 2012.
Overview ppdm data_architecture_in_oil and gas_ industrySuvradeep Rudra
The PPDM Association develops data modeling standards for the oil and gas industry. It maintains the PPDM data model, which currently covers 53 subject areas across 1238 tables. The PPDM seeks to standardize data sharing across industry members and provides a roundtable process for experts to collaborate on useful, business-driven standards. The PPDM data model follows SQL conventions and can be implemented on common database platforms. It defines structured relationships and naming conventions to organize oil and gas exploration, production, and other operational data.
A column-oriented DBMS is a database management system (DBMS) that stores its content by column rather than by row. This has advantages for data warehouses and library catalogues where aggregates are computed over large numbers of similar data items.
Hadoop provides a solution for overcoming traditional limitations of data storage and computation by leveraging inexpensive commodity hardware and allowing for easy linear scalability. It enables organizations to unlock value from big data by making large amounts of information transparent and usable at high frequencies. This allows for more precise customer segmentation, improved product development, and data-driven management decisions. However, challenges remain around privacy, security, access to diverse data sources, and developing talent with the right skills to work with big data.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise boosts blood flow and levels of neurotransmitters and endorphins which elevate and stabilize mood.
Khushi Saini, An Intern from The Sparks Foundationkhushisaini0924
This is my first task as an Talent Acquisition(Human resources) Intern in The Sparks Foundation on Recruitment, article and posts.
I invitr everyone to look into my work and provide me a quick feedback.
LinkedIn Strategic Guidelines for June 2024Bruce Bennett
LinkedIn is a powerful tool for networking, researching, and marketing yourself to clients and employers. This session teaches strategic practices for building your LinkedIn internet presence and marketing yourself. The use of # and @ symbols is covered as well as going mobile with the LinkedIn app.
Section 79(A) of Maharashtra Societies act 1860ManmohanJindal1
Lot of redevelopment projects are going on, where law and procedures are not followed , causing harm to the members of the society . This PPT is useful for every citizen living in society Building
2. AGENDA
Data warehouse and BI overview
Data warehouse Data Flow
Staging Area
Transformation
Loading
ETL tools
Data Marts
Business Intelligence (BI)
OLAP
BIG DATA
3. DATA WAREHOUSE AND BI OVERVIEW
• A data warehouse is a database that is designed for query and analysis
rather than for transaction processing. It usually contains historical data
derived from transaction data, but it can include data from other sources. It
separates analysis workload from transaction workload and enables an
organization to consolidate data from several sources.
• In addition to a relational database, a data warehouse environment includes
an extraction, transformation, and loading (ETL) solution, an online
analytical processing (OLAP) engine, client analysis tools, and other
applications that manage the process of gathering data and delivering it to
business users.
• Business intelligence (BI) is defined as the ability for an organization to
take all its capabilities and convert them into knowledge. This produces
large amounts of information which can lead to the development of new
opportunities for the organization.
4. FEW KEY IMPORTANT WORDS
• Business Operation
• Business Intelligence
• Business Management
• Operational System
• Data Warehouse
• Operational Data store
• Data Mart
• Meta Data Management
5. STEPS TO CREATE A DATAWAREHOUSE
• Understand the business problem to be solved
• Gather requirements
• Determine appropriate end user technology to support the solution
• Build a prototype
• Develop data warehouse data model
• Map the DW requirements based on the user’s requirement definitions
• Generate ETL code
• Test the DW
• Once validate, move the data and code to Production
6. SUBJECT
• Referred as subject oriented data warehouse
• Subject refers to data subject or major category of data relevant to business.
• Subset of enterprise data and consist of related entities and relationship.
• Examples Customers,Products,Sales,Geo
7. ENTITY
• Defined as person ,place, thing concept or relevant in which an enterprise has both
interest and capability to capture and store information
• Primary entity – defined as an entity that does not depend on any other entity for its
existance
• SUBTYPE Entity – is logical division of or category of a parent (super type) entity.
Examples – Customers can be Wholesale customers and Retail customers. Both inherits
parent attributes of parent entity.
• Attribute - It handles a group of data for an entity that can occur multiple times.
• Associative Entity - it depends upon 2 or more entities for its existence . Like Orders
consists of Customer and Items purchased.
• Primary Key – Servers as unique identifier for an Entity and is used in the physical
database to locate a record for storage or access
8. CHARACTERISTICS OF A PRIMARY KEY (PK)
• The key is never NULL
• The key is unique and unique by design and not by circumstances
• The key is persistence over the time
• The key is manageable – consists of integers and characters strings
and no embedded symbols or odd characters
• The key should not contain any embedded intelligence
9. RELATIONSHIP
• Relationship documents the business rules associating two entities together. The relationship is used to
describe how the two entries are naturally linked to each other.
• Example Customers can place orders.
• Cardinality *** - denotes the maximum number of occurrence of one entity to another that can relate to
another entity. Usually these are expressed as “ONE” or “MANY”
• Identifying Relationship – An identifying relationship means that the child table cannot be uniquely
identified without the parent
• Example...
Account (AccountID, AccountNum, AccountTypeID)
PersonAccount (AccountID, PersonID, Balance)
Person(PersonID, Name)
• The Account to PersonAccount relationship and the Person to PersonAccount relationship are identifying because the child
row (PersonAccount) cannot exist without having been defined in the parent (Account or Person). In other words: there is no
personaccount when there is no Person or when there is no Account.
• NON Identifying relationship - A non-identifying relationship is one where the child can be identified
independently of the parent
• Example...
Account( AccountID, AccountNum, AccountTypeID )
AccountType( AccountTypeID, Code, Name, Description )
• The relationship between Account and AccountType is non-identifying because each AccountType can be identified without
having to exist in the parent table.
10. NORMALIZATION
• Normalization is the process of efficiently organizing data in a database. There are two
goals of the normalization process: eliminating redundant data (for example, storing the
same data in more than one t) and ensuring data dependencies make sense (only storing
related data in a table). Both of these are worthy goals as they reduce the amount of
space a database consumes and ensure that data is logically stored.
• The database community has developed a series of guidelines for ensuring that
databases are normalized. These are referred to as normal forms and are numbered from
one (the lowest form of normalization, referred to as first normal form or 1NF) through
three (third normal form or 3NF).
11. FIRST NORMAL FORM (1NF)
• Eliminate duplicative columns from the same table.
• Create separate tables for each group of related data and identify each row with a unique
column or set of columns (the primary key).
• The first rule dictates that we must not duplicate data within the same row of a table.
Within the database community, this concept is referred to as the atomicity of a table.
Tables that comply with this rule are said to be atomic.
• Let’s explore this principle with a classic example – a table within a human resources
database that stores the manager-subordinate relationship. For the purposes of our
example, we’ll impose the business rule that each manager may have one or more
subordinates while each subordinate may have only one manager.
12. Option
STUDENT 1: Make a determinant of the repeating
group (or the multivalued attribute) a part of the
Stud_ID Name Course_ID Units
primary key.
101 Lennon MSI 250 3.00
101 Lennon MSI 415 3.00
125 Johnson MSI 331 3.00
Composite
Primary Key
STUDENT
Stud_ID Name Course_ID Units
101 Lennon MSI 250 3.00
101 Lennon MSI 415 3.00
125 Johnson MSI 331 3.00
13. Option 1: Make a of the repeating
determinant
group (or the multivalued attribute) a part of
Composite
the primary key.
Primary Key
STUDENT
Stud_ID Name Course_ID Units
101 Lennon MSI 250 3.00
101 Lennon MSI 415 3.00
125 Johnson MSI 331 3.00
14. Option 2: Remove the entire repeating group from the relation.
Create another relation which would contain all the attributes of
the repeating group, plus the primary key from the first relation.
In this new relation, the primary key from the original relation
and the determinant of the repeating group will comprise a
primary key.
STUDENT
Stud_ID Name Course_ID Units
101 Lennon MSI 250 3.00
101 Lennon MSI 415 3.00
125 Johnson MSI 331 3.00
15. STUDENT
Stud_ID Name
101 Lennon
125 Jonson
STUDENT_COURSE
Stud_ID Course Units
101 MSI 250 3
101 MSI 415 3
125 MSI 331 3
16. SECOND NORMAL FORM (2NF)
• Goal: Remove Partial Dependencies
Composite Partial Dependencies
Primary Key
STUDENT
Stud_ID Name Course_ID Units
101 Lennon MSI 250 3.00
101 Lennon MSI 415 3.00
125 Johnson MSI 331 3.00
17. CUSTOMER STUDENT_COURSE
Stud_ID Name Course_ID Units Stud_ID Cours _ID
e
101 Lennon MSI 250 3.00 101 MSI 250
101 Lennon MSI 415 3.00 101 MSI 415
125 Johnson MSI 331 3.00 125 MSI 331
STUDENT COURSE
Stud_ID Name Course_ID Units
101 Lennon
MSI 250 3.00
101 Lennon
MSI 415 3.00
125 Johnson
MSI 331 3.00
18. THIRD NORMAL FORM (3NF)
• Goal: Get rid of transitive dependencies.
Transitive Dependency
EMPLOYEE
Emp_ID F_Name L_Name Dept_ID Dept_Name
111 Mary Jones 1 Acct
122 Sarah Smith 2 Mktg
19. THIRD NORMAL FORM (3NF)
• Remove the attributes, which are dependent on a non-key
attribute, from the original relation. For each transitive
dependency, create a new relation with the non-key attribute
which is a determinant in the transitive dependency as a
primary key, and the dependent non-key attribute as a
dependent.
EMPLOYEE
Emp_ID F_Name L_Name Dept_ID Dept_Name
111 Mary Jones 1 Acct
122 Sarah Smith 2 Mktg
20. THIRD NORMAL FORM (3NF)
EMPLOYEE
Emp_ID F_Name L_Name Dept_ID Dept_Name
111 Mary Jones 1 Acct
EMPLOYEE
122 Sarah Smith 2 Mktg
Emp_ID F_Name L_Name Dept_ID
111 Mary Jones 1
122 Sarah Smith 2
DEPARTMENT
Dept_ID Dept_Name
1 Acct
2 Mktg
22. ZACHMAN FRAMEWORK FOR ENTERPRISE ARCHITECTURES
• As you can see from Figure 4, there are 36 intersecting cells in a Zachman grid—one for each
meeting point between a player's perspective (for example, business owner) and a descriptive
focus (for example, data.). As we move horizontally (for example, left to right) in the grid, we
see different descriptions of the system—all from the same player's perspective. As we move
vertically in the grid (for example, top to bottom), we see a single focus, but change the player
from whose perspective we are viewing that focus.
• The first suggestion of the Zachman taxonomy is that every architectural artifact should live in
one and only one cell. There should be no ambiguity about where a particular artifact lives. If it
is not clear in which cell a particular artifact lives, there is most likely a problem with the artifact
itself.
• The second suggestion of the Zachman taxonomy is that an architecture can be considered
a complete architecture only when every cell in that architecture is complete. A cell is complete
when it contains sufficient artifacts to fully define the system for one specific player looking at
one specific descriptive focus.
• The third suggestion of the Zachman grid is that cells in columns should be related to each
other. Consider, for example, the data column (the first column) of the Zachman grid. From the
business owner's (Bret's) perspective, data is information about the business. From the
database administrator's perspective, data is rows and columns in the database.
23. ZACHMAN GRID
5 ways in which the Zachman grid can help in the development of a enterprise architecture
• Ensure that every stakeholder's perspective has been considered for every descriptive focal
point.
• Improve the client’s artifacts themselves by sharpening each of their focus points to one
particular concern for one particular audience.
• Ensure that all of client’sbusiness requirements can be traced down to some technical
implementation.
• Convince client’s technical team isn't planning on building a bunch of useless functionality.
• Convince Client that the business folks are including her IT folks in their planning.
24. THE OPEN GROUP ARCHITECTURE FRAMEWORK (TOGAF)
• TOGAF is the Architecture Development Method
• TOGAF divides an enterprise architecture into four categories, as follows
• Business architecture—Describes the processes the business uses to meet its goals
• Application architecture—Describes how specific applications are designed and how
they interact with each other
• Data architecture—Describes how the enterprise datastores are organized and accessed
• Technical architecture—Describes the hardware and software infrastructure that
supports applications and their interactions
• Zachman tells you how to categorize your artifacts. TOGAF gives you a process for
creating them.
25. DAY-TO-DAY EXPERIENCE OF CREATING AN ENTERPRISE ARCHITECTURE
WILL BE DRIVEN BY THE ADM
A high-level view
26. PHASE A & PHASE B
• The culmination of Phase A will be a Statement of Architecture Work, which must be
approved by the various stakeholders before the next phase of the ADM begins. The
output of this phase is to create an architectural vision for the first pass through the
ADM cycle. Architect will guide Client into choosing the project, validating the project
against the architectural principles established in the Preliminary Phase, and ensure that
the appropriate stakeholders have been identified and their issues have been addressed.
• The Architectural Vision created in Phase A will be the main input into Phase B. Client’s
goal in Phase B is to create a detailed baseline and target business architecture and
perform a full analysis of the gaps between them.
• Phase B is quite involved—involving business modeling, highly detailed business
analysis, and technical-requirements documentation. A successful Phase B requires input
from many stakeholders. The major outputs will be a detailed description of the baseline
and target business objectives, and gap descriptions of the business architecture.
27. PHASE C
• Develop baseline data-architecture description
• Review and validate principles, reference models, viewpoints, and tools
• Create architecture models, including logical data models, data-management process models, and
relationship models that map business functions to CRUD (Create, Read, Update, Delete) data operations
• Select data-architecture building blocks
• Conduct formal checkpoint reviews of the architecture model and building blocks with stakeholders
• Review qualitative criteria (for example, performance, reliability, security, integrity)
• Complete data architecture
• Conduct checkpoint/impact analysis
• Perform gap analysis
• The most important deliverable from this phase will be the Target Information
and Applications Architecture.
28. PHASE D & PHASE E
• Phase D completes the technical architecture—the infrastructure necessary to support the
proposed new architecture. This phase is completed mostly by engaging with Client’s
infrastructure and technical team.
• Phase E evaluates the various implementation possibilities, identifies the major
implementation projects that might be undertaken, and evaluates the business opportunity
associated with each. The TOGAF standard recommends that Client’s first pass at Phase
E "focus on projects that will deliver short-term payoffs and so create an impetus for
proceeding with longer-term projects.―
• A good starting place to look for such projects is the organizational pain-points that
initially convinced by client’s CEO to adopt an enterprise architectural-based strategy
29. PHASE F , PHASE G & PHASE H
• Phase F is closely related to Phase E. In this phase, Teri works with MedAMore's
governance body to sort the projects identified in Phase E into priority order that include
not only the cost and benefits (identified in Phase E), but also the risk factors
• In Phase G, Client takes the prioritized list of projects and creates architectural
specifications for the implementation projects. These specifications will include
acceptance criteria and lists of risks and issues
• The final phase is H. In this phase, Client modifies the architectural change-management
process with any new artifacts created in this last iteration and with new information that
becomes available