Data modeling is a process used to define and analyze data requirements needed to support the business processes within the scope of corresponding information systems in organizations.
● Data Modeling and Data Models.
● Business Rules (Translating Business Rules into Data Model Components).
● Emerging Data Models: Big Data and NoSQL.
● Degrees of Data Abstraction (External, Conceptual, Internal and Physical model).
Data modeling is a process used to define and analyze data requirements needed to support the business processes within the scope of corresponding information systems in organizations.
● Data Modeling and Data Models.
● Business Rules (Translating Business Rules into Data Model Components).
● Emerging Data Models: Big Data and NoSQL.
● Degrees of Data Abstraction (External, Conceptual, Internal and Physical model).
It includes:
Introduction to Database Management System
DBMS vs File System
View of data
Data models
Database Languages: DML, DDL
Database users and administrators
Transaction Management
Database System Structure
Application architectures
It includes:
Introduction to Database Management System
DBMS vs File System
View of data
Data models
Database Languages: DML, DDL
Database users and administrators
Transaction Management
Database System Structure
Application architectures
Measuring Software: From Data to Actionable KnowledgeRadu Marinescu
Presented at SAM 2015 (2nd International Workshop on Software Architecture and Metrics): http://www.sei.cmu.edu/community/sam2015/speakers/
Nowadays we have tools that compute a myriad of metrics and throw at us thousands of warnings. Managers are gazing ecstatically at complex dashboards full of complex and vividly colored charts and trend lines. Sophisticated "technical debt calculators" are converting, with great boldness, internal quality issues to scary financial figures. With such an impressive arsenal of methodologies, techniques, and tools, software projects should be under full control. Except they are not! Often, metrics leave us clueless on how to improve the quality of our software; even worse, following blindly the goal of fixing some metric values usually leads to a degradation of a system's quality. In this talk, I will share some of the practical lessons learned on how to use software metrics to actually improve a system's design. I will also discuss the need to find new ways of correlating the various sources of information about a project, in order to move from raw data to insightful knowledge that can lead to real improvement actions.
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Identify the tools that a systems analyst could use.
2. Describe and differentiate each tool.
3. Use the appropriate tool for a certain and different situation.
TOPIC:
1. Systems development life cycle (SDLC)
2. Planning phase
3. Analysis phase
4. Design phase
5. Development phase
6. Implementation phase
7. Structured systems analysis
8. System model
9. Tools of structured analysis
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Identify the nature of systems.
2. Define what a system is.
3. Differentiate the types and classifications of the system.
4. Discuss different business systems and information systems.
5. Give an overview of system fundamentals and the general system
principles.
6. Identify who are the players in the system's game.
TOPIC:
1. The nature of systems
2. System definition
3. Classification
4. Types
5. Business systems and Information systems
6. System fundamentals
7. General systems principles
8. Players in the system's game
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Give an overview of the analysis.
2. Define what analysis is and systems analysis.
3. Lists the advantages and limitations of systems analysis.
4. Cite the responsibilities of the systems analysts.
5. Identify the scientific method of problem-solving.
TOPIC:
1. Overview of analysis
2. Definition of analysis
3. The study of systems analysis
4. Definition systems analysis
5. Advantages of systems analysis
6. Limitations of systems analysis
7. Responsibilities of the systems analyst
8. The scientific method of problem-solving
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Identify the different feasibility studies that could be used by the systems
analyst.
2. Describe and differentiate each feasibility study.
3. Use and apply a certain and appropriate feasibility study according to the
needs of the organization’s information system being developed.
TOPIC:
1. Technical feasibility
2. Operational feasibility
3. Economic feasibility
4. Cost-benefit study
5. Market analysis
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Identify the tools that a systems analyst could use.
2. Describe and differentiate each tool.
3. Use the appropriate tool for a certain and different situation.
TOPIC:
1. Systems development life cycle (SDLC)
2. Planning phase
3. Analysis phase
4. Design phase
5. Development phase
6. Implementation phase
7. Structured systems analysis
8. System model
9. Tools of structured analysis
SPECIFIC LEARNING OBJECTIVES:
At the end of this module you MUST be able to:
1. Identify the tools that a systems analyst could use.
2. Describe and differentiate each tool.
3. Use the appropriate tool for a certain and different situation.
TOPIC:
1. Systems development life cycle (SDLC)
2. Planning phase
3. Analysis phase
4. Design phase
5. Development phase
6. Implementation phase
7. Structured systems analysis
8. System model
9. Tools of structured analysis
Embracing GenAI - A Strategic ImperativePeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
Palestine last event orientationfvgnh .pptxRaedMohamed3
An EFL lesson about the current events in Palestine. It is intended to be for intermediate students who wish to increase their listening skills through a short lesson in power point.
Francesca Gottschalk - How can education support child empowerment.pptxEduSkills OECD
Francesca Gottschalk from the OECD’s Centre for Educational Research and Innovation presents at the Ask an Expert Webinar: How can education support child empowerment?
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
2. WRAP UP
The Database Environment and Development Process
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Data
Information
Data vs. Information
Database
Metadata
DBMS
Data Dictionary
Data Models
Types of Models
Relational Model
Keys
ERD
Data Mining
Components of DB
DB Dev. Process
3. Modeling Data in the
Organization
IS-DBS 313-2
1. E-R Model Notation
2. Modeling the Rules of the
Organization
3. Modeling Entities and Attributes
4. Modeling Relationship
TOPICS
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
4. Entity-Relationship Model
Models conceptual database design
in terms of entities, attributes, and
relationships between entities
E-R Model
Developed by Chen in 1976
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Enhanced E-R model (EER
model)
24. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
ER SYMBOLS
UNARY
One entity
BINARY
2
1 TERNARY
2
1
3
2 entities
3 entities
25. E-R Model Constructs
person, place, object, event, concept
(often corresponds to a row in a table)
Entity (instance)
collection of entities (often
corresponds to a table)
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Entity Set or Type
Entities
26. Strong vs Weak
Entities
exist independently of other types
of entities
has its own unique identifier
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
represented with single-line
rectangle
STRONG ENTITY
27. Strong vs Weak
Entities
Does not have a unique identifier
dependent on a strong
entity…cannot exist on its own
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
represented with double-line
rectangle
28. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
STRONG
ENTITY
WEAK
ENTITY
EMPLOYEE HAS
emp_id emp_name date_of_birth
dep_name
mid_name
first_name
last_name
29. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Analyze
the flow
30. Entity has attributes links together
All relationships for the associative entity
should be many
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Independent of the other entities
ASSOCIATIVE
ENTITY
preferably has a unique identifier, and
should also have other attributes
participating in other relationships other than
the entities of the associated relationship
32. What Should an
Entity Be?
An object that will have many
instances in the database
SHOULD BE:
An object that will be composed of
multiple attributes
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
An object that are trying to model
33. An Entity Should
Not Be?
A user of the database system
An output of the database
system (e.g. a report)
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
34. RECAPITULATION
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
ENTITY
SYMBOL
S
ATTRIBUTE
SYMBOL
S
RELATIONSHIP
SYMBOL
S
RELATIONSHIP
CARDINALIT
IES
RELATIONSHIP
DEGREE
S
36. E-R Model Constructs
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Entities
THINGS
TANGIBLE
ROLES
PLAYED
ORGANIZA-
TIONAL UNITS DEVICES
INCIDENTS,
EVENTS,
INTERACTIONS
SITES
LOCATIONS
Airplane
Book
Vehicle
Document
Worksheet
Employees
Customer
Doctor
Patient
End User
System
Admin
Division
Department
Section
Task Force
Work group
Sensor
Timer
Controller
Printer
Keyboard
Mouse
Button
Flight
Service Call
Logon
Logoff
Contract
Purchase
Payment
37. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
E-R Model Constructs
property or characteristic of
an entity or relationship type
(often corresponds to a
column in a table)
Attributes
38. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
E-R Model Constructs
Primary Key - unique
Types of Attributes
Foreign Key – PK in another
DB
39. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
E-R Model Constructs
Simple versus Composite Attribute
Classification of
Attributes
Single-Valued versus Multivalued Attribute
Stored versus Derived Attributes
Identifier Attributes
40. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
E-R Model Constructs
Composite Attributes
address
street_add
city state
postal_code
41. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
ATTRIBUTE
{MULTIVALUED}
ATTRIBUTE
[DERIVED]
ATTRIBUTE
42. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
E-R Model Constructs
Multivalued and
Derived Attributes
emp_name
emp_id add
date_employed
year_employed skill
employee
43. Relationship Set or Type
E-R Model Constructs
link between entities (corresponds to
primary key-foreign key equivalencies
in related tables)
Relationship (instance)
category of relationship…link
between entity types
Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
Relationship
45. Presented By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
ER SYMBOLS
MANDATORY ONE
MANDATORY MANY
OPTIONAL ONE
OPTIONAL MANY
MANY TO MANY ONE TO ONE
ADDITIONAL
46. Prepared By: Dr. Rosemarie S. Guirre | IS-DBS 313-2
END OF MODULE 1
Editor's Notes
Entity-Relationship Model
a detailed, logical representation of the entities, associations, and data elements for an organization or business area.
(E-R Model)
Models conceptual database design in terms of entities, attributes, and relationships between entities
Developed by Chen in 1976
Enhanced by others over the years
Enhanced E-R model (EER model)
Entity-Relationship Symbols
Entity
a “thing” in the real world
has an independent existence
Attribute(s)
One specific piece of information about a thing
a property of the entity
has a value (or value set or domain)
Multivalued - Attribute contains more than one value associated with the key of the enity.
Relationship
Naturally occurring association among specific things
Occur in two directions
Cardinality/multiplicity
Identifying Relationship - exist when the primary key of the parent entity is included in the primary key of the child entity.
1. RELATIONSHIP
2. IDENTIFYING
RELATIONSHIP
Cardinality
the number of instances of an entity that are associated with another entity
Specify number of entity types involved
MANDATORY
ONE
OPTIONAL MANY
MANY TO MANY
MANDATORY MANY
OPTIONAL ONE
Degree of Relationship
number of entities that participate in the relationship
Unary (recursive)
degree one
A relationship between instances of one entity.
One entity related to another of the same entity type
Binary
degree two
A relationship between instances of two entities
Entities of two different types related to each other
Ternary
A relationship between instances of three entities
Entities of three different types related to each other
Identifying relationship
– links strong entities to weak entities
– represented with double line diamond
Associative Entities
It’s an entity – it has attributes
AND it’s a relationship – it links entities together
When should a relationship with attributes instead be an
associative entity?
– All relationships for the associative entity should be many
– The associative entity could have meaning independent of the other
entities
– The associative entity preferably has a unique identifier, and should also
have other attributes
– The associative may be participating in other relationships other than the
entities of the associated relationship
Associative entity involves a rectangle with a diamond inside. Note that many to many cardinality symbols face toward the associative entity and not toward the other entities
An Entity is a thing the users need to know (i.e, record) something about.
Identifier (primary key / key attribute)
An attribute (or attributes) selected as the unique, identifying characteristic for an entity.
Foreign Key
An attribute (or attributes) in one database table that is the primary key in another database table
Identifier (primary key / key attribute)
An attribute (or attributes) selected as the unique, identifying characteristic for an entity.
Foreign Key
An attribute (or attributes) in one database table that is the primary key in another database table