Advanced Management

Information System

Dr. Ebadati

University of Economic Science

‫ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ﻭ ﻧﺤﻮﻩ ﻃﺮﺍﺣﻲ ﺁﻥ‬
The Traditional Approach Versus
the Database Approach
• Traditional approach: separate data files are
created for each application
• Results in data redundancy (duplication)
• Data redundancy conflicts with data integrity
• Database approach: pool of related data is
shared by multiple applications
• Significant advantages over traditional approach
The Traditional Approach Versus the
Database Approach (continued)
• The Traditional Approach to Data Management
The Traditional Approach Versus the
Database Approach (continued)
• The Database Approach to Data Management
The Traditional Approach Versus the
Database Approach (continued)
• Advantages of the Database Approach
The Traditional Approach Versus the
Database Approach (continued)
• Advantages of the Database Approach
(continued)
The Traditional Approach Versus the
Database Approach (continued)
• Disadvantages of the Database Approach
 ‫ﻃﺮﺍﺣﻲ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ﺍﻱ )ﺍﻃﻼﻋﺎﺗﻲ(‬
‫ﻃﺮﺍﺣﻲ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ﺍﻱ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺳﻪ ﻣﺮﺣﻠﻪ ﺍﻱ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺖ‪.‬‬

‫ﻣﺮﺣﻠﻪ ﺍﻭﻝ‪ :‬ﻣﺪﻟﺴﺎﺯﻱ ﻣﻔﻬﻮﻣﻲ ﺍﻃﻼﻋﺎﺕ ﺷﺪ‪.‬‬

‫ﻣﺮﺣﻠﻪ ﺩﻭﻡ‪ :‬ﻃﺮﺍﺣﻲ ﻣﻨﻄﻘﻲ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺖ ﻛﻪ ﻣﺪﻝ ﻣﻔﻬﻮﻣﻲ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺑﻪ ﺗﻮﺻﻴﻒ ﻣﻨﻄﻘﻲ‬

‫ﺍﻃﻼﻋﺎﺕ ﺑﻪ ﻛﺎﺭ ﻓﺘﻪ ﺑﻪ ﻭﺳﻴﻠﻪ ﻳﻚ ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‪ ،‬ﺗﺒﺪﻳﻞ ﻣﻲ ﻛﻨﺪ )ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ‬

‫ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺕ(‬

‫ﻣﺮﺣﻠﻪ ﺳﻮﻡ‪ :‬ﻃﺮﺍﺣﻲ ﻓﻴﺰﻳﻚ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺖ ﻛﻪ ﺗﻮﺻﻴﻒ ﻣﻨﻄﻘﻲ ﺭﺍ ﺑﻪ ﻣﺪﻝ ﻓﻴﺰﻳﻜﻲ ﻣﺒﺪﻝ ﻣﻲ‬

‫ﺳﺎﺯﺩ‪.‬‬
‫ﺩﺭ ﺣﻴﻦ ﻃﺮﺍﺣﻲ ﻣﺪﻝ ﻣﻨﻄﻘﻲ ﻭ ﻓﻴﺰﻳﻜﻲ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﻣﻮﺍﺭﺩ‬
‫ﺯﻳﺮ ﺑﺎﻳﺪ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻪ ﺷﻮﻧﺪ‬

‫ﺍﻧﻌﻄﺎﻑ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺗﻐﻴﻴﺮﺍﺕ ﺁﺗﻲ ﺩﺭﺁﻥ‪،‬‬

‫ﺗﺪﺍﺑﻴﺮ ﻛﻨﺘﺮﻟﻲ ﺑﺮﺍﻱ ﺣﻔﺎﻇﺖ ﺍﺯ ﺍﻧﺴﺠﺎﻡ ﺩﺍﺩﻩ ﻫﺎ ﺩﺭ ﭘﺎﻳﮕﺎﻩ‬

‫ﺍﻃﻼﻋﺎﺗﻲ‪،‬‬

‫ﻛﺎﺭﺁﻳﻲ ﺳﻴﺴﺘﻢ ﺑﻬﻨﮕﺎﻡ ﺳﺎﺯﻱ ﻭ ﺑﺎﺯﻳﺎﺑﻲ ﺩﺍﺩﻩ ﻫﺎ‪،‬‬

‫ﻛﺎﺭﺁﻳﻲ ﭼﮕﻮﻧﮕﻲ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻇﺮﻓﻴﺘﻬﺎﻱ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ‬

‫ﺧﺎﺭﺟﻲ‪.‬‬
 ‫ﻃﺮﺍﺣﻲ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﻣﺴﺘﻠﺰﻡ‬
‫ﺷﻨﺎﺧﺖ ﻣﻮﺍﺭﺩ ﺫﻳﻞ ﺍﺳﺖ‬
When building a database, consider:
• Content: What data should be collected, at what cost?
• Access: What data should be provided to which
users, and when?
• Logical structure: How should data be arranged to
make sense to a given user?
• Physical organization: Where should data be
physically located?
‫ﻣﺮﻭﺭﻱ ﻛﻠﻲ ﺑﺮ ﮔﺎﻡﻫﺎﻱ ﻃﺮﺍﺣﻲ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‬
 Data Modeling
• Building a database requires two types of
design:
• Logical design: Shows an abstract model of
how data should be structured and
arranged to meet an organization’s
information needs
• Physical design: Fine-tunes the logical
database design for performance and cost
considerations
 Data Modeling (continued)

• Data model: a diagram of data entities and

their relationships
• Use Case
• DFD
• Entity-relationship (ER) diagrams: data models that
use basic graphical symbols to show the organization
of and relationships between data
‫“ﺳﺎﺧﺘﻪ” ﻫﺎﻱ ﻃﺮﺍﺣﻲ ﻣﻨﻄﻘﻲ ﭘﺎﻳﮕﺎﻩ‬
‫ﺍﻃﻼﻋﺎﺗﻲ‬
‫“ﺳﺎﺧﺘﻪ” ﻫﺎﻱ ﻃﺮﺍﺣﻲ‪ ،‬ﺳﺎﺧﺘﺎﺭ ﻣﻨﻄﻘﻲ ﻭ ﻓﻴﺰﻳﻜﻲ ﺍﻃﻼﻋﺎﺕ‬
‫ﻳﻚ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍ ﺗﺸﺮﻳﺢ ﻣﻲ ﻛﻨﺪ ﺳﺎﺧﺘﺎﺭ ﻣﻨﻄﻘﻲ‬
‫ﺍﻃﻼﻋﺎﺕ ﺍﺯ ﭼﻬﺎﺭ ﺳﺎﺧﺘﻪ ﺗﺸﻜﻴﻞ ﻣﻲ ﺷﻮﺩ‪:‬‬
‫ﻋﻨﺎﺻﺮ ﺍﻃﻼﻋﺎﺕ‬

‫ﺳﺎﺑﻘﻪ ﻫﺎﻱ ﻣﻨﻄﻘﻲ‬

‫ﻛﻠﻴﺪﻫﺎ‬

‫ﺭﻭﺍﺑﻂ‬
 Data Modeling (continued)
• An Entity-Relationship (ER) Diagram for a
Customer Order Database
 The Relational Database Model

• Relational model: all data elements are placed

in two-dimensional tables (relations), which are
the logical equivalent of files
• In the relational model:
• Each row of a table represents a data entity
• Columns of the table represent attributes
• Domain: the allowable values for data attributes
The Relational Database Model
(continued)
‫ﺳﺎﺧﺘﻪﻫﺎﻱ ﻣﺪﻝ ﻣﻨﻄﻘﻲ ﺍﻃﻼﻋﺎﺕ‬
‫ﺍﻟﻒ ‪:‬‬
‫ﻧﺎﻡ ﻣﺸﺘﺮﻱ‬ ‫ﻋﻨﺼﺮ ﺍﻃﻼﻋﺎﺕ‬

‫ﻣﺸﺘﺮﻱ‬ ‫ﺳﺎﺑﻘﻪ‬ ‫ﺏ‪:‬‬

‫ﺳﺎﺑﻘﻪ‬ ‫ﺝ‪:‬‬
‫ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ‬ ‫ﻛﻠﻴﺪ‬

‫ﻣﺸﺘﺮﻱ‬ ‫ﺳﺎﺑﻘﻪ‬ ‫ﺩ‪:‬‬

‫ﺷﻤﺎﺭﻩ ﺳﻔﺎﺭﺵ‬ ‫ﻛﻠﻴﺪ‬
‫»‪ «1‬ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ‬ ‫»‪ «1‬ﻛﻠﻴﺪ‬
‫»‪ «1‬ﺷﻤﺎﺭﻩ ﻭﺿﻌﻴﺖ ﺳﻔﺎﺭﺵ‬ ‫»‪ «1‬ﻛﻠﻴﺪ‬
 ‫ﺭﺍﺑﻄﻪ‬

‫• ﺭﺍﺑﻄﻪ‪ ،‬ﺍﺭﺗﺒﺎﻁ ﻣﻴﺎﻥ “ﺳﺎﺑﻘﻪ”ﻫﺎ ﺑﺮ ﻗﺮﺍﺭ ﻣﻲ ﻛﻨﺪ‬

‫• ﺭﻭﺍﺑﻂ ﻣﻴﺎﻥ “ﻣﻮﺟﻮﺩﻳﺘﻬﺎ” ﺩﺭ ﻣﺪﻝ ﻣﻔﻬﻮﻣﻲ ﺑﻪ ﺭﺍﺑﻄﻪ ﻣﻴﺎﻥ‬

‫“ﺳﺎﺑﻘﻪ ﻫﺎ” ﺩﺭﻣﺪﻝ ﻣﻨﻄﻘﻲ ﺗﺒﺪﻳﻞ ﻣﻲﺷﻮﺩ‪.‬‬
 ‫ﺳﺎﺧﺘﺎﺭ ﻣﻨﻄﻘﻲ ﺍﻃﻼﻋﺎﺕ ﭘﺎﻳﮕﺎﻩ‬
‫ﺍﻃﻼﻋﺎﺗﻲ ﺷﺮﻛﺖ ﻋﺪﺍﻟﺖﮔﺴﺘﺮ‬
‫ﻣﺸﺘﺮﻱ‬
‫ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ‬
‫ﺳﻔﺎﺭﺵ‬ ‫ﺩﺭﻳﺎﻓﺖ ﻣﻲﻛﻨﺪ‬
‫ﻧﺎﻡ ﻣﺸﺘﺮﻱ‬
‫ﺷﻤﺎﺭﻩ ﺳﻔﺎﺭﺵ‬ ‫ﻧﺸﺎﻧﻲ ﭘﺴﺘﻲ ﺧﻴﺎﺑﺎﻥ ﻣﺸﺘﺮﻱ‬
‫»‪ «1‬ﺷﻤﺎﺭﻩ ﻭﺿﻌﻴﺖ ﺳﻔﺎﺭﺵ‬ ‫ﻧﺸﺎﻧﻲ ﭘﺴﺘﻲ ﺷﻬﺮ ﻣﺸﺘﺮﻱ‬ ‫ﻣﺤﻤﻮﻟﻪ‬
‫ﺷﻤﺎﺭﻩ ﺻﻮﺭﺗﺤﺴﺎﺏ‬
‫ﺷﻤﺎﺭﻩ ﻣﺤﻤﻮﻟﻪ‬
‫ﺗﺎﺭﻳﺦ ﺻﻮﺭﺗﺤﺴﺎﺏ‬
‫ﺗﺎﺭﻳﺦ ﻣﺤﻤﻮﻟﻪ‬
‫ﺩﺭ ﺑﺮ ﺩﺍﺭﺩ‬ ‫ﻧﺎﻡ ﻭﺳﻴﻠﻪ ﺣﻤﻞ ﻣﺤﻤﻮﻟﻪ‬

‫ﺍﻗﻼﻡ ﺳﻔﺎﺭﺵ‬
‫ﺷﻤﺎﺭﻩ ﺳﻔﺎﺭﺵ‬
‫ﻣﺤﺼﻮﻝ ‪2 -‬‬
‫ﺷﻤﺎﺭﻩ ﻣﺤﺼﻮﻝ‬
‫ﺍﺭﺳﺎﻝ ﻣﻲﺷﻮﺩ‬ ‫ﺷﻤﺎﺭﻩ ﻣﺤﺼﻮﻝ‬
‫ﺷﻤﺎﺭﻩ ﺍﻗﻼﻡ ﺳﻔﺎﺭﺵ‬ ‫ﻣﺤﺼﻮﻝ ‪1 -‬‬
‫ﻣﺘﻦ ﺗﻮﺻﻴﻒ ﻣﺤﺼﻮﻝ‬
‫ﺳﻔﺎﺭﺵ ﻫﺎ‬ ‫ﻣﺤﺼﻮﻝ ‪1 -‬‬
‫ﺷﻤﺎﺭﻩ ﻣﺤﺼﻮﻝ‬ ‫ﻣﺤﺼﻮﻝ ‪2 -‬‬
‫ﻣﺒﻠﻎ ﻗﻴﻤﺖ ﻣﺤﺼﻮﻝ‬
 ‫ﺳﺎﺧﺘﺎﺭ ﻣﻨﻄﻘﻲ ﺍﻃﻼﻋﺎﺕ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‬
‫ﺷﺮﻛﺖ ﻋﺪﺍﻟﺖﮔﺴﺘﺮ )ﺍﺩﺍﻣﻪ(‬

‫• ﺩﺭ ﻧﻤﻮﺩﺍﺭ ﭘﻴﺸﻴﻦ ﻋﻨﺼﺮ “ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ” ﺩﺭ ﺳﺎﺑﻘﻪ “ﺳﻔﺎﺭﺵ”‬

‫ﺭﺍﺑﻄﻪ ﻣﻴﺎﻥ “ﺳﺎﺑﻘﻪ ﻣﺸﺘﺮﻱ” ﺑﺎ “ﺳﺎﺑﻘﻪ ﺳﻔﺎﺭﺵ” ﺭﺍ ﻣﻌﻴﻦ ﻣﻲ ﻛﻨﺪ‪.‬‬
 ‫ﻧﺸﺎﻥ ﺩﺍﺩﻥ ﺭﺍﺑﻄﻪ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻛﻠﻴﺪ‬
‫ﺧﺎﺭﺟﻲ‬

‫ﻣﺤﻤﻮﻟﻪ‬ ‫ﻣﺸﺘﺮﻱ‬
‫ﺷﻤﺎﺭﻩ ﻣﺤﻤﻮﻟﻪ‬ ‫ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ‬
‫ﻣﺸﺘﺮﻱ‬ ‫ﺗﺎﺭﻳﺦ ﻣﺤﻤﻮﻟﻪ‬
‫ﺷﻤﺎﺭﻩ ﻣﺸﺘﺮﻱ‬
 ‫ﺳﻴﺴﺘﻤﻬﺎﻱ ﻣﺪﻳﺮﻳﺖ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‬
‫• ﻫﺪﻑ ﺭﻫﻴﺎﻓﺖ ﺩﺍﺩﻩ ﮔﺮﺍ ﺩﺭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ‪ ،‬ﺍﻳﺠﺎﺩ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‬
‫ﺍﺳﺖ ﻛﻪ ﺳﻴﺴﺘﻤﻬﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ﻣﺘﻌﺪﺩ ﺑﺘﻮﺍﻧﻨﺪ ﺁﻥ ﺭﺍ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻗﺮﺍﺭ ﺩﻫﻨﺪ‪.‬‬

‫• ﺗﻨﻮﻉ ﺍﺣﺘﻤﺎﻟﻲ ﻣﺪﻟﻬﺎﻱ ﻓﻴﺰﻳﻜﻲ ﻭ ﻣﻨﻄﻘﻲ ﺩﺭ ﺗﺮﻛﻴﺐ ﺑﺎ ﺳﻴﺴﺘﻤﻬﺎﻱ‬

‫ﻛﺎﺭﺑﺮﺩﻱ ﻣﺘﻌﺪﺩﻱ ﻛﻪ ﺍﺣﺘﻤﺎﻻً ﻧﻴﺎﺯ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺍﻃﻼﻋﺎﺕ ﺩﺍﺭﻧﺪ ﻃﺮﺍﺣﻲ‬
‫ﭘﺎﻳﮕﺎﻩ ﺭﺍ ﺑﻪ ﻣﺴﺎﻟﻪ ﺑﺴﻴﺎﺭ ﺩﺷﻮﺍﺭﻱ ﺗﺒﺪﻳﻞ ﻣﻲ ﻛﻨﺪ‪.‬‬
 ‫ﻧﺤﻮﻩ ﺗﻌﺮﻳﻒ ﻧﻮﻉ ﺩﺍﺩﻩ ﺩﺭ ﭘﺎﻳﮕﺎﻩ‬
‫ﺍﻃﻼﻋﺎﺕ‬

‫ﻧﺎﻡ=ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ ﻣﺸﺘﺮﻱ‪ ،‬ﺩﺳﺘﺮﺳﻲ‬ ‫ﺷﺮﺡ ﭘﺎﻳﮕﺎﻩ ﺍﻃﻼﻋﺎﺗﻲ‬

‫ﻧﺎﻡ=ﻣﺸﺘﺮﻱ‪ ،‬ﺳﺎﺑﻘﻪ ﻣﺎﺩﺭ=‪ ،0‬ﺑﺎﻳﺖ=‬ ‫ﺑﺨﺶ‬

‫ﻧﺎﻡ=ﺷﻤﺎﺭﻩ‪-‬ﻣﺸﺘﺮﻱ ‪ ،‬ﺑﺎﻳﺖ=‪ ، 10‬ﺁﻏﺎﺯ=‪1‬‬ ‫ﻓﻴﻠﺪ‬

‫ﻧﺎﻡ=ﻧﺎﻡ‪-‬ﻣﺸﺘﺮﻱ ‪ ،‬ﺑﺎﻳﺖ=‪ ، 40‬ﺁﻏﺎﺯ=‪11‬‬ ‫ﻓﻴﻠﺪ‬

‫ﻧﺎﻡ=ﺳﻔﺎﺭﺵ‪ ،‬ﺳﺎﺑﻘﻪ ﻣﺎﺩﺭ=‪0‬ﻣﺸﺘﺮﻱ ‪ ،‬ﺑﺎﻳﺖ=‬ ‫ﺑﺨﺶ‬

‫ﻧﺎﻡ=ﺷﻤﺎﺭﻩ‪-‬ﺳﻔﺎﺭﺵ ‪ ،‬ﺑﺎﻳﺖ= ‪ ،‬ﺁﻏﺎﺯ=‬ ‫ﻓﻴﻠﺪ‬

Database Management Systems
(DBMS)

• Interface between
• Database and application programs
• Database and the user
• Database types
• Flat file
• Single user
• Multiple users
 Creating and Modifying the
Database
• Data definition language (DDL)
• –Collection of instructions/commands that
define and describe data and data relationships
in a database
• –Allows database creator to describe the data
and the data relationships that are to be
contained in the schema and the subschemas
• •Data dictionary: a detailed description of all
the data used in the database
 Creating and Modifying the
Database (continued)
• Using a Data Definition Language to Define a
Schema
 Creating and Modifying the
Database (continued)
• A Typical Data Dictionary Entry
 Storing and Retrieving Data
• When an application requests data from the
DBMS, the application follows a logical access
path
• When the DBMS goes to a storage device to
retrieve the requested data, it follows a path to
the physical location (physical access path)
where the data is stored
 Storing and Retrieving Data
(continued)
• Logical and Physical Access Paths
 Manipulating Data and
Generating Reports (continued)
• Database Output
 Popular Database Management
Systems
• Popular DBMSs for end users: Microsoft Access
and Corel Paradox
• •The complete database management software
market includes databases by IBM, Oracle, and
Microsoft
• •Examples of open-source database systems:
PostgreSQL and MySQL
• •Many traditional database programs are now
available on open-source operating systems
 Selecting a Database
Management System
• Important characteristics of databases to
consider:
• Size of the database
• Number of concurrent users
• Performance
• Ability to be integrated with other systems
• Features of the DBMS
• Vendor considerations
• Cost of the system
 Using Databases with Other
Software
• Database management systems are often used
with other software packages or the Internet

• A database management system can act as a

front-end application or a back-end
application
• Front-end application: interacts with users
• Back-end application: interacts with applications
 the Company Database to the
Internet

• Corporate databases can be accessed by

customers, suppliers, and employees through:
• The Internet
• Intranets
• Extranets
 Distributed & Replicated
Databases
• Distributed database
• Data may be spread across several smaller
databases connected via telecommunications
devices
• Corporations get more flexibility in how databases
are organized and used
• Replicated database
• Holds a duplicate set of frequently used data
 What Is an ERD?
• A picture showing the information created, stored,
and used by a business system.
• Entities generally represent similar kinds of
information
• Lines drawn between entities show relationships
among the data
 Using the ERD to Show Business
Rules
• Business rules are constraints that are followed
when the system is in operation.
• ERD symbols can show when one instance of an
entity must exist for an instance of another to
exist
• A doctor must exist before appointments for the
doctor can be made
 Using the ERD to Show Business
Rules
• ERD symbols can show when one instance of an
entity can be related to only one or many
instances of another entity
• One doctor can have many patients; each patient
may have only one primary doctor
• ERD symbols show when the existence of an
entity instance is optional for a related entity
instance
• A patient may or may not have insurance
coverage
An ERD Example
ERD Elements
 Entity
• A person, place, event, or thing about which data is collected
• Must be multiple occurrences to be an entity
• Example: If a firm has only one warehouse, the warehouse
is not an entity. However, if the firm has several
warehouses, the warehouse could be an entity if the firm
wants to store data about each warehouse instance.
Entities and Instances
 Attributes
• Information captured about an entity
• Only those used by the organization should be included
in the model
• Attribute names are nouns
• Sometimes entity name is added at the beginning of the
attribute name for clarity
 Identifiers
• One or more attributes can serve as the entity identifier,
uniquely identifying each entity instance
• Concatenated identifier consists of several attributes
• An identifier may be ‘artificial,’ such as creating an ID
number
• Identifiers may not be developed until the Design Phase
Choices for Identifiers
 Relationships
• Associations between entities
• The first entity in the relationship is the parent
entity; the second entity in the relationship is the
child entity
• Relationships should have active verb names
• Relationships go in both directions
 Cardinality
• Cardinality
• refers to the number of times instances in one entity
can be related to instances in another entity
• One instance in an entity refers to one and only one
instance in the related entity (1:1)
• One instance in an entity refers to one or more instances
in the related entity (1:N)
• One or more instances in an entity refer to one or more
instances in the related entity (M:N)
 Modality
• Modality
• Refers to whether or not an instance of a child entity
can exist without a related instance in the parent
entity
• Not Null means that an instance in the related entity must
exist for an instance in another entity to be valid
• Null means that no instance in the related entity is
necessary for an instance in another entity to be valid
M : N Relationships
Data Dictionary Entry for the Patient
Entity (Shown Using Erwin)
 Un-normalized Entity
Begin with an
entity from
the logical data
model
 First Normal Form (1NF)
Look for repeating groups of attributes and
remove them into separate entities
 Second Normal Form (2NF)
If an entity has a concatenated identifier, look for attributes
that depend only on part of the identifier. If found, remove to
new entity.
 Third Normal Form (3NF)
Look for attributes that depend only on another non-
identifying attribute.
If found, remove to new entity. Also remove any calculated
attributes.
 Summary
• Hierarchy of data: bits, characters, fields, records,
files, and databases
• An entity is a generalized class of things (objects) for
which data is collected, stored, and maintained
• Attribute: characteristic of an entity
• Data model: diagram of entities and relationships
 Summary (continued)
• A database management system (DBMS) is a
group of programs used as an interface
between:
• The database and application programs
• The database and the user
• Data dictionary: detailed description of all the
data used in the database
 References
• Charles Parker, Thomas Case. (2000). “Management Information Systems: Action &
Strategy”. (2nd Edition).
• Kenneth C. Laudon & Jane P. Laudon (2001). “Management Information Systems:
Managing a Digital Firm”.(7th Edition)
• James O’Brien. (1998). “Introduction to Information Systems: A Networked
Enterprise Perspective”. (2nd Edition).
• Chris Woodward (2001), CSC Research Services. Creating Information Systems
Harmony
(http://www.csc.com/features/2001/21.shtml)
• CSC Research Services. “CEOs are from Mars, CIOs are from Pluto”.
(http://www.csc.com/features/2002/22.shtml)
• Grover S. Kearns (1997). “Alignment of Information Systems Plans with Business
Plans”. (http://hsb.baylor.edu/ramsower/ais.ac.97/papers/kearns.htm)
• Ralph M. Stair & George W. Reynolds (2012). “Fundamentals of Information Systems”. (6th
Edition)
• James A. O’Brien, George M. Marakas (2010). “INTRODUCTION TO INFORMATION SYSTEMS”.
(15th Edition)
• Ralph Stair, George Reynolds (2006). “Fundamentals of Information Systems”. (3rd /4th Edition).
• Stephen Haag, Maeve Cummings (2009). “INFORMATION SYSTEMS ESSENTIALS”. (3rd Edition)
‫ﻣﻮﻓﻖ ﺑﺎﺷﻴﺪ‬