SlideShare uma empresa Scribd logo
1 de 41
A company DETAC of construction and trading
The main
interface
WELCOME
Contact
2.1.5 FORMS
2.1.6 reports
3- Implementation and loading
3.1 DBMS Software Selection
4-Testing and Evaluation
4.1 Create the Logical
Design
1- Database Life Cycle (DBLC)
1-1 Database Initial study
1.1.1 Identify problems and obstacles.
1.1.2 Objectives:
1.1.3 Scope and Boundaries:
2-1 Database Design
2.1 .1 Normalization
2.1.2 ERD
2.1.3 Tables
2.1.4 Queries
5-Operation
6- Maintenance and Evaluation
6.1 Create the Physical
Design
1-Database Life Cycle (DBLC)
Conceptual Design
ER-Diagram / Normalization
DBMS Software Selection
Create the Logical
Design
Create the Physical
Design
Database Initial study
Database Design
Implementation and loading
Testing and Evaluation
Operation
Maintenance and Evaluation
In this first stage of the Initial study for a database, we
have identified the current study of the operation of the
system within the company how and why the current
system has failed. The overall objective of this study to the
database is as follows:
• Analysis the situation in the company.
• Identify problems and obstacles.
• Setting goals.
• Identify the scope and limits.
1.1 Database Initial study
The company situation describes
When examining the current system in this company and found that work in a variety of departments and
administration departments are hiring their employees as needed, after recording a full data are the Exchange
number for each employee and the follow-up to the employee in terms of attendance and payment of monthly
salaries for each of employee.
In this company is dealing with customers by manual work any models is to mobilize and be Questions and
reports Manual ,this work was very difficult and it takes a great time for reports and correspondence From here
behind us design system that helps this company in the extraction of reports and INQUIRIES easy manner and
in a short time
Through the company's existing situation analysis it found that the system
depends entirely on the manual system in all transactions company's .
and we found inconsistency in data entry or in hand written orders. This has
the effect of not only causing problems with customer service but also marking
information unable be used for reporting or finding trends with data discovery
. reporting and checking that data is robust can be timely and expensive .this is
often an area where significant money can be saved by automation as well as
loss and damage to files and documents, whether natural or human factors
and repeating the mistakes in queries and reports
1.1.1 Identify problems and obstacles.
1.1.2 Objectives:
1.1.3 Scope and Boundaries:
In this stage, to determine the scope and limits of the system:
We have identified the scope of the system and designed it according to operational requirements.
The entire design data and one or more departments within the organization, including the
organization so that helps to identify the required data structures, and the type and number of
entities base, and the actual size of the database according to the required data
1-Conversion of manual system to a computer with the creation of a database covering
all the company's transactions Base
2- Improved data access to users
3- Reduced data entry, storage, and retrieval costs.
4- Greater integrity of data and improve security
5- keeping electronic records - making it easier to get the information, and generate
reports to meet the tax requirements and the preparation of legal reports
2-1 Database Design
• In this second stage, we have designed the sample database that will support
the company's operations and goals. It is the most important stage (DBLC): to
make sure that the proposed system will meet the requirements of the user
and the system.
The dependence on that:
• The easy-relevant for the analysis and design of a larger system, the
database design process.
Input system must be according to the required output
• The establishment of procedures that will help in the conversion of data
within the database to useful information.
2.1 .1 Normalization
First Normal Form (1NF)
Normal Form (NF)
Employees= nu_EM, name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM, add_EM, pho_EM,
qual_EM,Major,accou_EM { nu_ban, name_ban, add_ban, phon_ban, email_ban, un_cont, name_Dep, phon_Dep,
addr_Dep, date_st_work, date_end_work, durat_cont, salary, date_pr_abs, case_pr_abs }.
Employees= (nu_EM, name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM, add_EM, pho_EM,
qual_EM, major, accou_EM, nu_ban, name_ban, add_ban, phon_ban, email_ban, un_cont, name_Dep, phon_Dep,
addr_Dep, date_st_work, date_end_work, durat_cont, salary, date_pr_abs, case_pr_abs ).
Second Normal Form (2NF)
Data_employees= (EM_NUM , name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM,
add_EM, pho_EM, qual_EM, major, accou_EM, nu_ban)
Bank= (nu_ban, name_ban, add_ban, phon_ban, email_ban,
Finance_EMPL= (un_cont, durat_cont, date_st_work, date_end_work, salary, data_cont, un_EM,
date_pr_abs, case_pr_abs)
Department= (nu_dep, name_Dep, phon_Dep, addr_Dep,).
Third Normal Form (3NF)
Data_employee= (EM_nu, EM_NAME, EM_date_bir, EM_gender, EM_NAT, EM_MAR, EM_pass, EM_add ,
EM_phon, EM_qual, BAN_NUM, EM_Accou)
Nationality= (NAT_NUM, NAT_NAME)
Qualification= (QUAL_NUM, QUAL_NAME)
Bank= (BAN_NUM, EM_NUM, BAN_ADDR, phon_ban, Email_ban )
Finance_EMPL= (Cont_NUM, EM_NUM, date_cont, Dep_NU, date_st_work, date_end_work, salary )
Pres_absen= (EM_NUM, Date_pr_ads, Case_pr_abs)
Department= (Dep_NUM, Dep_NAM, Dep_phon, Dep_ADDR).
No. Field Name Type Length Key
1 EM_NUM Auto Number Long Integer Primary Key
2 EM_NAME Text 50
3 EM_date_bir Date/Time Short Time
4 EM_gender Yes/No
5 EM_NAT Short text 20
6 EM_MAR Yes/No
7 EM_pass Number 10
8 EM_add Text 25
9 EM_phon Number 25
10 EM_qual Number Long Integer
11 BAN_NUM Number Long Integer
12 EM_Accou Number 25
Data Dictionary
Table of Data_employee
No. Field Name Type Length Key
1 NAT_NUM Auto Number Long Integer Primary Key
2 NAT_NAME Text 40
Table of Nationality
No. Field Name Type Length Key
1 QUAL_NUM Auto Number Long Integer Primary Key
2 QUAL_NAME
Text
40
Table of Qualification
No. Field Name Type Length Key
1 BAN_NUM Auto Number Long Integer Primary Key
2 BAN_NAME Text 50
3 BAN_ADDR Text Long Integer
4 phon_ban Number Long Integer
5 Email_ban Text 50
Table of Bank
No. Field Name Type Length Key
1 Dep_NUM Auto Number Long Integer Primary Key
2 Dep_NAM Text 50
3 Dep_phon number 50
4 Dep_ADDR number Long Integer
Table of Department
No. Field Name Type Length Key
1 Cont_NUM Auto Number Long Integer Primary Key
2 EM_NUM number Short Time
3 date_cont Date/Time Short Time Foreign key
4 Dep_NU number Long Integer Foreign key
5 date_st_work Date/Time Short Time
6 date_end_work Date/Time Short Time
7 salary number
No. Field Name Type Length Key
1 EM_NUM Number Long Integer Primary Key
2 Date_pr_ads Date/Time Short time Foreign key
3 Case_pr_abs Yes/No - foreign key
Table of Finance_Empl
Table of Pres_absen
Cont..
ER-Diagram
After the normalization process was reached following entities and the relationship
between them are shown in the following figure1
follow up
Data_Employee
EM_add
EM_NAME
EM_date_bir
EM_gender
EM_pass
EM_NATEM_NUM
EM_MAR
EM_phon
EM_qual
BAN_NUM EM_Accou
Cashing FINANCE_EMPL
EM_NUM
Date_st_workDep_NUM
Date_cont
Date_end_work
Cont_NUM
Salary
1
1
PRES_ABSEN
Case_pr_abs
EM_NUM Date_pr_ads
1
M
work in
1
1
Department
Dep_NUM
Dep_ADDRDep_phonDep_NAM
Nationality
NAT_NAME
NAT_NUM
have
M
1
QUAL_NAME
QUAL_NUM
have
M
1
Banks
BAN_NUM
BAN_NAME
BAN_ADDR
phon_ban
Email_ban
registered
M
1
Qualification
ERD
Implementation and loading
DBMS Software Selection
Testing and Evaluation
At this stage, the database contains a series of instructions
that create separate tables, attributes, fields, views,
indexes, security constraints, and storage performance and
design guidelines.
It has been selected ACCESS database to be a project
company database design.
The system was tested after the database design and the
introduction of the logical data were evaluated after
obtaining positive results.
At this stage, the database will be passed the evaluation stage, is considered ready for
action. At this point, the database, the management, users, and application programs
constitute a complete information system. The beginning of the operational phase always
begins the process of evolution of the system.
Operation
Maintenance and Evaluation
At this stage, there must be fully prepared to carry out
routine maintenance work within the database.
Some of the required periodic maintenance work include:
• preventive maintenance (backup).
• Corrective Maintenance (PCR).
• Maintenance of adaptive (enhanced performance,
adding entities and attributes).
• Set the access and maintenance of the new and old users
permissions.
1-Data employee
Database deign Tables and database sheet view
2-Banks
3-Department
4-finance_empl
5-Qualification
6-Nationality
7-Pres_absen
A relationship, in the context of databases, is a situation that exists between two relational database tables when
one table has a foreign key that references the primary key of the other table Relationships allow relational
databases to split and store data in different tables, while linking disparate data items.
Relationship
1-Data_empl _pres5
Queries
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, pres_absen.Date_pr_ads, pres_absen.Case_pr_abs
FROM Data_Employee, pres_absen
WHERE ( Data_Employee.EM_NUM = pres_absen.EM_NUM) and (pres_absen.Date_pr_ads=#1-2-2016#) and (
pres_absen.Case_pr_abs=true );
2-Dataa _empl_date_end
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Cont_NUM, financ_empl.Date_end_work
FROM Data_Employee, financ_empl
WHERE ( financ_empl.EM_NUM = Data_Employee.EM_NUM) and (financ_empl.Date_end_work=#1-1-2018#);
3-Data of employee by bank
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Salary, Banks.BAN_NAME
FROM Data_Employee, financ_empl, Banks
WHERE (Banks.BAN_NUM = Data_Employee.BAN_NUM) and ( financ_empl.EM_NUM =
Data_Employee.EM_NUM) and Banks.BAN_NAME='cimb';
4-Data_employee by qual
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Banks.BAN_NAME,
Data_Employee.EM_accon, financ_empl.Salary
FROM Data_Employee, Banks, financ_empl
WHERE (( Data_Employee.BAN_NUM = Banks.BAN_NUM) and ( financ_empl.EM_NUM =
Data_Employee.EM_NUM ));
5-Data employee by salary
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Salary
FROM Data_Employee, financ_empl
WHERE (financ_empl.EM_NUM = Data_Employee.EM_NUM) and (Salary
BETWEEN 1000 and 2000);
6-Data_empl_department
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Department.Dep_NAM
FROM Data_Employee, Department, financ_empl
WHERE (Department.Dep_NUM = financ_empl.Dep_NU) and
( financ_empl.EM_NUM = Data_Employee.EM_NUM ) and (Department.Dep_NAM="computer");
7-Data_empl_dep_pre
SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Department.Dep_NAM, pres_absen.date_pr_ads,
pres_absen.case_pr_abs
FROM Data_Employee, Department, pres_absen, financ_empl
WHERE ( Department.Dep_NUM = financ_empl.Dep_NU)and ( Data_Employee.EM_NUM = pres_absen.EM_NUM)
and (financ_empl.EM_NUM = Data_Employee.EM_NUM) and (Department.Dep_NAM="computer") and
(pres_absen.Case_pr_abs=true);
FORMS
1-Form Data of Banks 2-Form Data of Employee
4-From of Nationality3-Form of Department
5-Form of presence and absent 6-Form of Qualification
7-Form of financ
1- Report About Officer Data Attendance In Specific Date
reports
2- Report About Data of officer which their contract out of date in
specific date
3- Report About Officer Data According To Their Banks
4- Data Of Officer Financial Matters
5- Report Of Employee They Take Salary Ranging Between 1000-2000
6- Report About Officer Data According To Their Department
7- Report Of Officer Data According To Their Attendance In
Specific Time And Specific Department
Thank you

Mais conteúdo relacionado

Mais procurados

Socio Technical Systems in Software Engineering SE2
Socio Technical Systems in Software Engineering SE2Socio Technical Systems in Software Engineering SE2
Socio Technical Systems in Software Engineering SE2
koolkampus
 
SE - Software Requirements
SE - Software RequirementsSE - Software Requirements
SE - Software Requirements
Jomel Penalba
 
Sample Request Order Tracking Functional Requirements Document V1
Sample Request Order Tracking  Functional Requirements Document V1Sample Request Order Tracking  Functional Requirements Document V1
Sample Request Order Tracking Functional Requirements Document V1
Semon Wu
 

Mais procurados (20)

Is 4 th
Is 4 thIs 4 th
Is 4 th
 
Socio Technical Systems in Software Engineering SE2
Socio Technical Systems in Software Engineering SE2Socio Technical Systems in Software Engineering SE2
Socio Technical Systems in Software Engineering SE2
 
Chapter01 the systems development environment
Chapter01 the systems development environmentChapter01 the systems development environment
Chapter01 the systems development environment
 
Chapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialoguesChapter14 designing interfaces and dialogues
Chapter14 designing interfaces and dialogues
 
Chapter08 structuring system requirements
Chapter08 structuring system requirementsChapter08 structuring system requirements
Chapter08 structuring system requirements
 
Information Management unit 3 Database management systems
Information Management unit 3 Database management systemsInformation Management unit 3 Database management systems
Information Management unit 3 Database management systems
 
SE - Software Requirements
SE - Software RequirementsSE - Software Requirements
SE - Software Requirements
 
System analysis and design
System analysis and designSystem analysis and design
System analysis and design
 
Chapter02 succeeding as a systems analyst
Chapter02 succeeding as a systems analystChapter02 succeeding as a systems analyst
Chapter02 succeeding as a systems analyst
 
System analysis and design chapter 2
System analysis and design chapter 2System analysis and design chapter 2
System analysis and design chapter 2
 
computer Unit 8
computer Unit 8computer Unit 8
computer Unit 8
 
Statistical Model to Validate A Metaprocess-Oriented Methodology based on RAS...
Statistical Model to Validate A Metaprocess-Oriented Methodology based on RAS...Statistical Model to Validate A Metaprocess-Oriented Methodology based on RAS...
Statistical Model to Validate A Metaprocess-Oriented Methodology based on RAS...
 
Se exe 6
Se exe 6Se exe 6
Se exe 6
 
Chapter15 finalizing design specifications
Chapter15 finalizing design specificationsChapter15 finalizing design specifications
Chapter15 finalizing design specifications
 
Chapter13 designing forms and reports
Chapter13 designing forms and reportsChapter13 designing forms and reports
Chapter13 designing forms and reports
 
Agile Data: Automating database refactorings
Agile Data: Automating database refactoringsAgile Data: Automating database refactorings
Agile Data: Automating database refactorings
 
Ch03 (1)
Ch03 (1)Ch03 (1)
Ch03 (1)
 
SE2018_Lec 16_ Architectural Design
SE2018_Lec 16_ Architectural DesignSE2018_Lec 16_ Architectural Design
SE2018_Lec 16_ Architectural Design
 
Sample Request Order Tracking Functional Requirements Document V1
Sample Request Order Tracking  Functional Requirements Document V1Sample Request Order Tracking  Functional Requirements Document V1
Sample Request Order Tracking Functional Requirements Document V1
 
Chapter11 selecting the best alternative design strategy
Chapter11 selecting the best alternative design strategyChapter11 selecting the best alternative design strategy
Chapter11 selecting the best alternative design strategy
 

Semelhante a Assignment of database

PRESS MANAGEMENT Documentation
PRESS MANAGEMENT DocumentationPRESS MANAGEMENT Documentation
PRESS MANAGEMENT Documentation
anuj_rakheja
 
ISAS 600 – Database Project Phase III RubricAs the final ste.docx
ISAS 600 – Database Project Phase III RubricAs the final ste.docxISAS 600 – Database Project Phase III RubricAs the final ste.docx
ISAS 600 – Database Project Phase III RubricAs the final ste.docx
bagotjesusa
 
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docxCIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
clarebernice
 
Mis system analysis and system design
Mis   system analysis and system designMis   system analysis and system design
Mis system analysis and system design
Rahul Hedau
 
It 302 computerized accounting (week 2) - sharifah
It 302   computerized accounting (week 2) - sharifahIt 302   computerized accounting (week 2) - sharifah
It 302 computerized accounting (week 2) - sharifah
alish sha
 
CIS 2303 LO1: Introduction to System Analysis and Design
CIS 2303 LO1: Introduction to System Analysis and DesignCIS 2303 LO1: Introduction to System Analysis and Design
CIS 2303 LO1: Introduction to System Analysis and Design
Ahmad Ammari
 

Semelhante a Assignment of database (20)

PRESS MANAGEMENT Documentation
PRESS MANAGEMENT DocumentationPRESS MANAGEMENT Documentation
PRESS MANAGEMENT Documentation
 
Sdlc1
Sdlc1Sdlc1
Sdlc1
 
ISAS 600 – Database Project Phase III RubricAs the final ste.docx
ISAS 600 – Database Project Phase III RubricAs the final ste.docxISAS 600 – Database Project Phase III RubricAs the final ste.docx
ISAS 600 – Database Project Phase III RubricAs the final ste.docx
 
Issue Management System
Issue Management SystemIssue Management System
Issue Management System
 
Designing the Process of Stores Management for Implementing ERP in Manufactur...
Designing the Process of Stores Management for Implementing ERP in Manufactur...Designing the Process of Stores Management for Implementing ERP in Manufactur...
Designing the Process of Stores Management for Implementing ERP in Manufactur...
 
Designing the Process of Stores Management for Implementing ERP in Manufactur...
Designing the Process of Stores Management for Implementing ERP in Manufactur...Designing the Process of Stores Management for Implementing ERP in Manufactur...
Designing the Process of Stores Management for Implementing ERP in Manufactur...
 
Unit 2 Classical Systems Development Methodology.pptx
Unit 2 Classical Systems Development Methodology.pptxUnit 2 Classical Systems Development Methodology.pptx
Unit 2 Classical Systems Development Methodology.pptx
 
Data Warehouses & Deployment By Ankita dubey
Data Warehouses & Deployment By Ankita dubeyData Warehouses & Deployment By Ankita dubey
Data Warehouses & Deployment By Ankita dubey
 
An Integrated ERP With Web Portal
An Integrated ERP With Web PortalAn Integrated ERP With Web Portal
An Integrated ERP With Web Portal
 
An Integrated ERP with Web Portal
An Integrated ERP with Web Portal An Integrated ERP with Web Portal
An Integrated ERP with Web Portal
 
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docxCIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docx
 
Software Development Life Cycle (SDLC).pptx
Software Development Life Cycle (SDLC).pptxSoftware Development Life Cycle (SDLC).pptx
Software Development Life Cycle (SDLC).pptx
 
College management
College managementCollege management
College management
 
Mis system analysis and system design
Mis   system analysis and system designMis   system analysis and system design
Mis system analysis and system design
 
It 302 computerized accounting (week 2) - sharifah
It 302   computerized accounting (week 2) - sharifahIt 302   computerized accounting (week 2) - sharifah
It 302 computerized accounting (week 2) - sharifah
 
Systems Analysis Midterm Lesson
Systems Analysis Midterm LessonSystems Analysis Midterm Lesson
Systems Analysis Midterm Lesson
 
Unit 1: Introduction to DBMS Unit 1 Complete
Unit 1: Introduction to DBMS Unit 1 CompleteUnit 1: Introduction to DBMS Unit 1 Complete
Unit 1: Introduction to DBMS Unit 1 Complete
 
CIS 2303 LO1: Introduction to System Analysis and Design
CIS 2303 LO1: Introduction to System Analysis and DesignCIS 2303 LO1: Introduction to System Analysis and Design
CIS 2303 LO1: Introduction to System Analysis and Design
 
Planning Data Warehouse
Planning Data WarehousePlanning Data Warehouse
Planning Data Warehouse
 
Hospital E-Token Management(outdoor)
Hospital E-Token Management(outdoor)Hospital E-Token Management(outdoor)
Hospital E-Token Management(outdoor)
 

Mais de ra na (9)

Project
Project Project
Project
 
Networking
NetworkingNetworking
Networking
 
computer website
computer websitecomputer website
computer website
 
hajer
hajerhajer
hajer
 
PM1
PM1PM1
PM1
 
PM3 ARTICALS
PM3 ARTICALSPM3 ARTICALS
PM3 ARTICALS
 
PM2 ARTICALS
PM2 ARTICALSPM2 ARTICALS
PM2 ARTICALS
 
PM3
PM3PM3
PM3
 
PM2
PM2PM2
PM2
 

Assignment of database

  • 1. A company DETAC of construction and trading The main interface
  • 3. Contact 2.1.5 FORMS 2.1.6 reports 3- Implementation and loading 3.1 DBMS Software Selection 4-Testing and Evaluation 4.1 Create the Logical Design 1- Database Life Cycle (DBLC) 1-1 Database Initial study 1.1.1 Identify problems and obstacles. 1.1.2 Objectives: 1.1.3 Scope and Boundaries: 2-1 Database Design 2.1 .1 Normalization 2.1.2 ERD 2.1.3 Tables 2.1.4 Queries 5-Operation 6- Maintenance and Evaluation 6.1 Create the Physical Design
  • 4. 1-Database Life Cycle (DBLC) Conceptual Design ER-Diagram / Normalization DBMS Software Selection Create the Logical Design Create the Physical Design Database Initial study Database Design Implementation and loading Testing and Evaluation Operation Maintenance and Evaluation
  • 5. In this first stage of the Initial study for a database, we have identified the current study of the operation of the system within the company how and why the current system has failed. The overall objective of this study to the database is as follows: • Analysis the situation in the company. • Identify problems and obstacles. • Setting goals. • Identify the scope and limits. 1.1 Database Initial study The company situation describes When examining the current system in this company and found that work in a variety of departments and administration departments are hiring their employees as needed, after recording a full data are the Exchange number for each employee and the follow-up to the employee in terms of attendance and payment of monthly salaries for each of employee. In this company is dealing with customers by manual work any models is to mobilize and be Questions and reports Manual ,this work was very difficult and it takes a great time for reports and correspondence From here behind us design system that helps this company in the extraction of reports and INQUIRIES easy manner and in a short time
  • 6. Through the company's existing situation analysis it found that the system depends entirely on the manual system in all transactions company's . and we found inconsistency in data entry or in hand written orders. This has the effect of not only causing problems with customer service but also marking information unable be used for reporting or finding trends with data discovery . reporting and checking that data is robust can be timely and expensive .this is often an area where significant money can be saved by automation as well as loss and damage to files and documents, whether natural or human factors and repeating the mistakes in queries and reports 1.1.1 Identify problems and obstacles.
  • 7. 1.1.2 Objectives: 1.1.3 Scope and Boundaries: In this stage, to determine the scope and limits of the system: We have identified the scope of the system and designed it according to operational requirements. The entire design data and one or more departments within the organization, including the organization so that helps to identify the required data structures, and the type and number of entities base, and the actual size of the database according to the required data 1-Conversion of manual system to a computer with the creation of a database covering all the company's transactions Base 2- Improved data access to users 3- Reduced data entry, storage, and retrieval costs. 4- Greater integrity of data and improve security 5- keeping electronic records - making it easier to get the information, and generate reports to meet the tax requirements and the preparation of legal reports
  • 8. 2-1 Database Design • In this second stage, we have designed the sample database that will support the company's operations and goals. It is the most important stage (DBLC): to make sure that the proposed system will meet the requirements of the user and the system. The dependence on that: • The easy-relevant for the analysis and design of a larger system, the database design process. Input system must be according to the required output • The establishment of procedures that will help in the conversion of data within the database to useful information.
  • 9. 2.1 .1 Normalization First Normal Form (1NF) Normal Form (NF) Employees= nu_EM, name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM, add_EM, pho_EM, qual_EM,Major,accou_EM { nu_ban, name_ban, add_ban, phon_ban, email_ban, un_cont, name_Dep, phon_Dep, addr_Dep, date_st_work, date_end_work, durat_cont, salary, date_pr_abs, case_pr_abs }. Employees= (nu_EM, name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM, add_EM, pho_EM, qual_EM, major, accou_EM, nu_ban, name_ban, add_ban, phon_ban, email_ban, un_cont, name_Dep, phon_Dep, addr_Dep, date_st_work, date_end_work, durat_cont, salary, date_pr_abs, case_pr_abs ).
  • 10. Second Normal Form (2NF) Data_employees= (EM_NUM , name_EM, date_bir_EM, gender_EM, nat_EM, mar_EM, pass_EM, add_EM, pho_EM, qual_EM, major, accou_EM, nu_ban) Bank= (nu_ban, name_ban, add_ban, phon_ban, email_ban, Finance_EMPL= (un_cont, durat_cont, date_st_work, date_end_work, salary, data_cont, un_EM, date_pr_abs, case_pr_abs) Department= (nu_dep, name_Dep, phon_Dep, addr_Dep,).
  • 11. Third Normal Form (3NF) Data_employee= (EM_nu, EM_NAME, EM_date_bir, EM_gender, EM_NAT, EM_MAR, EM_pass, EM_add , EM_phon, EM_qual, BAN_NUM, EM_Accou) Nationality= (NAT_NUM, NAT_NAME) Qualification= (QUAL_NUM, QUAL_NAME) Bank= (BAN_NUM, EM_NUM, BAN_ADDR, phon_ban, Email_ban ) Finance_EMPL= (Cont_NUM, EM_NUM, date_cont, Dep_NU, date_st_work, date_end_work, salary ) Pres_absen= (EM_NUM, Date_pr_ads, Case_pr_abs) Department= (Dep_NUM, Dep_NAM, Dep_phon, Dep_ADDR).
  • 12. No. Field Name Type Length Key 1 EM_NUM Auto Number Long Integer Primary Key 2 EM_NAME Text 50 3 EM_date_bir Date/Time Short Time 4 EM_gender Yes/No 5 EM_NAT Short text 20 6 EM_MAR Yes/No 7 EM_pass Number 10 8 EM_add Text 25 9 EM_phon Number 25 10 EM_qual Number Long Integer 11 BAN_NUM Number Long Integer 12 EM_Accou Number 25 Data Dictionary Table of Data_employee
  • 13. No. Field Name Type Length Key 1 NAT_NUM Auto Number Long Integer Primary Key 2 NAT_NAME Text 40 Table of Nationality No. Field Name Type Length Key 1 QUAL_NUM Auto Number Long Integer Primary Key 2 QUAL_NAME Text 40 Table of Qualification
  • 14. No. Field Name Type Length Key 1 BAN_NUM Auto Number Long Integer Primary Key 2 BAN_NAME Text 50 3 BAN_ADDR Text Long Integer 4 phon_ban Number Long Integer 5 Email_ban Text 50 Table of Bank No. Field Name Type Length Key 1 Dep_NUM Auto Number Long Integer Primary Key 2 Dep_NAM Text 50 3 Dep_phon number 50 4 Dep_ADDR number Long Integer Table of Department
  • 15. No. Field Name Type Length Key 1 Cont_NUM Auto Number Long Integer Primary Key 2 EM_NUM number Short Time 3 date_cont Date/Time Short Time Foreign key 4 Dep_NU number Long Integer Foreign key 5 date_st_work Date/Time Short Time 6 date_end_work Date/Time Short Time 7 salary number No. Field Name Type Length Key 1 EM_NUM Number Long Integer Primary Key 2 Date_pr_ads Date/Time Short time Foreign key 3 Case_pr_abs Yes/No - foreign key Table of Finance_Empl Table of Pres_absen
  • 16. Cont.. ER-Diagram After the normalization process was reached following entities and the relationship between them are shown in the following figure1
  • 17. follow up Data_Employee EM_add EM_NAME EM_date_bir EM_gender EM_pass EM_NATEM_NUM EM_MAR EM_phon EM_qual BAN_NUM EM_Accou Cashing FINANCE_EMPL EM_NUM Date_st_workDep_NUM Date_cont Date_end_work Cont_NUM Salary 1 1 PRES_ABSEN Case_pr_abs EM_NUM Date_pr_ads 1 M work in 1 1 Department Dep_NUM Dep_ADDRDep_phonDep_NAM Nationality NAT_NAME NAT_NUM have M 1 QUAL_NAME QUAL_NUM have M 1 Banks BAN_NUM BAN_NAME BAN_ADDR phon_ban Email_ban registered M 1 Qualification ERD
  • 18. Implementation and loading DBMS Software Selection Testing and Evaluation At this stage, the database contains a series of instructions that create separate tables, attributes, fields, views, indexes, security constraints, and storage performance and design guidelines. It has been selected ACCESS database to be a project company database design. The system was tested after the database design and the introduction of the logical data were evaluated after obtaining positive results.
  • 19. At this stage, the database will be passed the evaluation stage, is considered ready for action. At this point, the database, the management, users, and application programs constitute a complete information system. The beginning of the operational phase always begins the process of evolution of the system. Operation Maintenance and Evaluation At this stage, there must be fully prepared to carry out routine maintenance work within the database. Some of the required periodic maintenance work include: • preventive maintenance (backup). • Corrective Maintenance (PCR). • Maintenance of adaptive (enhanced performance, adding entities and attributes). • Set the access and maintenance of the new and old users permissions.
  • 20. 1-Data employee Database deign Tables and database sheet view
  • 25. A relationship, in the context of databases, is a situation that exists between two relational database tables when one table has a foreign key that references the primary key of the other table Relationships allow relational databases to split and store data in different tables, while linking disparate data items. Relationship
  • 26. 1-Data_empl _pres5 Queries SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, pres_absen.Date_pr_ads, pres_absen.Case_pr_abs FROM Data_Employee, pres_absen WHERE ( Data_Employee.EM_NUM = pres_absen.EM_NUM) and (pres_absen.Date_pr_ads=#1-2-2016#) and ( pres_absen.Case_pr_abs=true );
  • 27. 2-Dataa _empl_date_end SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Cont_NUM, financ_empl.Date_end_work FROM Data_Employee, financ_empl WHERE ( financ_empl.EM_NUM = Data_Employee.EM_NUM) and (financ_empl.Date_end_work=#1-1-2018#); 3-Data of employee by bank SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Salary, Banks.BAN_NAME FROM Data_Employee, financ_empl, Banks WHERE (Banks.BAN_NUM = Data_Employee.BAN_NUM) and ( financ_empl.EM_NUM = Data_Employee.EM_NUM) and Banks.BAN_NAME='cimb';
  • 28. 4-Data_employee by qual SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Banks.BAN_NAME, Data_Employee.EM_accon, financ_empl.Salary FROM Data_Employee, Banks, financ_empl WHERE (( Data_Employee.BAN_NUM = Banks.BAN_NUM) and ( financ_empl.EM_NUM = Data_Employee.EM_NUM ));
  • 29. 5-Data employee by salary SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, financ_empl.Salary FROM Data_Employee, financ_empl WHERE (financ_empl.EM_NUM = Data_Employee.EM_NUM) and (Salary BETWEEN 1000 and 2000);
  • 30. 6-Data_empl_department SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Department.Dep_NAM FROM Data_Employee, Department, financ_empl WHERE (Department.Dep_NUM = financ_empl.Dep_NU) and ( financ_empl.EM_NUM = Data_Employee.EM_NUM ) and (Department.Dep_NAM="computer");
  • 31. 7-Data_empl_dep_pre SELECT Data_Employee.EM_NUM, Data_Employee.EM_NAME, Department.Dep_NAM, pres_absen.date_pr_ads, pres_absen.case_pr_abs FROM Data_Employee, Department, pres_absen, financ_empl WHERE ( Department.Dep_NUM = financ_empl.Dep_NU)and ( Data_Employee.EM_NUM = pres_absen.EM_NUM) and (financ_empl.EM_NUM = Data_Employee.EM_NUM) and (Department.Dep_NAM="computer") and (pres_absen.Case_pr_abs=true);
  • 32. FORMS 1-Form Data of Banks 2-Form Data of Employee
  • 34. 5-Form of presence and absent 6-Form of Qualification
  • 36. 1- Report About Officer Data Attendance In Specific Date reports
  • 37. 2- Report About Data of officer which their contract out of date in specific date
  • 38. 3- Report About Officer Data According To Their Banks 4- Data Of Officer Financial Matters
  • 39. 5- Report Of Employee They Take Salary Ranging Between 1000-2000 6- Report About Officer Data According To Their Department
  • 40. 7- Report Of Officer Data According To Their Attendance In Specific Time And Specific Department