|
| Titre : |
Development Of A Business Layer to Ensure Communication Between Distributed Information Systems |
| Type de document : |
texte imprimé |
| Auteurs : |
Ramy Dekari, Auteur ; Mohamed Zegadi ; SAIDI ,Mohamed, Directeur de thèse |
| Editeur : |
Setif:UFA |
| Année de publication : |
2024 |
| Importance : |
1 vol (96 f .) |
| Format : |
29 cm |
| Langues : |
Anglais (eng) |
| Catégories : |
Thèses & Mémoires:Informatique
|
| Mots-clés : |
Web services
BPEL language
LifeCycle Manager
Data warehouse |
| Index. décimale : |
004 - Informatique |
| Résumé : |
The evolution of computer science has transformed business operations, revolutionizing
data processing and storage methods. However, this progress has also
complicated company’s information systems, making them more diverse and challenging
to handle. To tackle this issue, we’ve proposed an efficient solution in this
study: integrating multiple information systems using web services and a composite
module built with the BPEL language.
This approach streamlines processes, enhancing overall efficiency. This dissertation
explores how to combine various information systems into a single, cohesive unit. It
discusses theoretical concepts before showing how these ideas are put into practice
to create an integrated application that offers improved efficiency through the use
of multiple services.
At the conclusion of our project, we have achieved the development of an advanced
hospital system ”LifeCycle Manager” aimed at resolving the challenges associated
with enhancing the efficiency of data warehousing between the hospital and other
crucial departments, including the municipality , police , post and funeral charities.
Our comprehensive system is meticulously designed to streamline and optimize all
operations among these entities, thereby simplifying processes and fostering seamless
communication. By implementing our solution, we aim to significantly improve
overall efficiency while ensuring ease and simplicity in managing data exchanges. |
| Note de contenu : |
Sommaire
1 Conceptual Overview 13
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Standardization of information systems . . . . . . . . . . . . . . . . . 15
1.2.1 Definition of IS standardization . . . . . . . . . . . . . . . . . 15
1.2.2 SOA (Service Oriented Architecture) . . . . . . . . . . . . . . 16
1.2.3 SOA Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.4 Characteristics of SOA architecture . . . . . . . . . . . . . . . 16
1.2.5 Advantages of a service-oriented architecture . . . . . . . . . . 17
1.3 Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.1 Web Services Definition . . . . . . . . . . . . . . . . . . . . . 18
1.3.2 The Importance of web services . . . . . . . . . . . . . . . . . 19
1.3.3 Characteristics of Web services . . . . . . . . . . . . . . . . . 19
1.3.4 Operations in a Web service architecture . . . . . . . . . . . . 20
1.3.5 Web Service Architecture . . . . . . . . . . . . . . . . . . . . 21
1.3.6 Web Services Technology . . . . . . . . . . . . . . . . . . . . . 23
1.3.7 Static and dynamic web services . . . . . . . . . . . . . . . . . 28
1.4 Composition of web services . . . . . . . . . . . . . . . . . . . . . . . 29
1.4.1 Definition of composition of web services . . . . . . . . . . . . 29
1.4.2 Life cycle of a web service composition . . . . . . . . . . . . . 29
1.4.3 Types of Service Composition . . . . . . . . . . . . . . . . . . 31
1.5 Web Services Composition Language . . . . . . . . . . . . . . . . . . 33
1.5.1 BPEL definition . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.5.2 Characteristics of BPEL . . . . . . . . . . . . . . . . . . . . . 34
1.5.3 BPEL processes . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.5.4 Elements of a BPEL process . . . . . . . . . . . . . . . . . . . 35
1.5.5 Activities of the BPEL process . . . . . . . . . . . . . . . . . 35
1.6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2 Design And Analysis 37
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.2 Study of the existing . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3 Problem and motivations . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4 Presentation of our case study . . . . . . . . . . . . . . . . . . . . . . 39
2.4.1 Proposed solution . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.2 Presentation of our system . . . . . . . . . . . . . . . . . . . . 40
2.4.3 Our system requirements . . . . . . . . . . . . . . . . . . . . . 43
2.4.4 Our System’s Web Services . . . . . . . . . . . . . . . . . . . 43
2.5 UML modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.2 The UML modeling tool . . . . . . . . . . . . . . . . . . . . . 46
2.5.3 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 47
2.5.4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.5 Deployment diagram . . . . . . . . . . . . . . . . . . . . . . . 51
2.5.6 Sequence diagram . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3 Implementation 55
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2 The development environment and technical choices. . . . . . . . . . 56
3.2.1 Languages Used . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.2.2 The Software Environment . . . . . . . . . . . . . . . . . . . . 60
3.2.3 Hardware Environment . . . . . . . . . . . . . . . . . . . . . . 63
3.3 Implementation Of The System . . . . . . . . . . . . . . . . . . . . . 64
3.3.1 Database Implementation . . . . . . . . . . . . . . . . . . . . 64
3.3.2 Definition Of Web Services . . . . . . . . . . . . . . . . . . . . 68
3.3.3 Web Services Testing . . . . . . . . . . . . . . . . . . . . . . . 70
3.3.4 Composition Of Web Services . . . . . . . . . . . . . . . . . . 77
3.4 The Interfaces Of Our System . . . . . . . . . . . . . . . . . . . . . . 84
3.5 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 |
| Côte titre : |
MAI/0923
|
Development Of A Business Layer to Ensure Communication Between Distributed Information Systems [texte imprimé] / Ramy Dekari, Auteur ; Mohamed Zegadi ; SAIDI ,Mohamed, Directeur de thèse . - [S.l.] : Setif:UFA, 2024 . - 1 vol (96 f .) ; 29 cm. Langues : Anglais ( eng)
| Catégories : |
Thèses & Mémoires:Informatique
|
| Mots-clés : |
Web services
BPEL language
LifeCycle Manager
Data warehouse |
| Index. décimale : |
004 - Informatique |
| Résumé : |
The evolution of computer science has transformed business operations, revolutionizing
data processing and storage methods. However, this progress has also
complicated company’s information systems, making them more diverse and challenging
to handle. To tackle this issue, we’ve proposed an efficient solution in this
study: integrating multiple information systems using web services and a composite
module built with the BPEL language.
This approach streamlines processes, enhancing overall efficiency. This dissertation
explores how to combine various information systems into a single, cohesive unit. It
discusses theoretical concepts before showing how these ideas are put into practice
to create an integrated application that offers improved efficiency through the use
of multiple services.
At the conclusion of our project, we have achieved the development of an advanced
hospital system ”LifeCycle Manager” aimed at resolving the challenges associated
with enhancing the efficiency of data warehousing between the hospital and other
crucial departments, including the municipality , police , post and funeral charities.
Our comprehensive system is meticulously designed to streamline and optimize all
operations among these entities, thereby simplifying processes and fostering seamless
communication. By implementing our solution, we aim to significantly improve
overall efficiency while ensuring ease and simplicity in managing data exchanges. |
| Note de contenu : |
Sommaire
1 Conceptual Overview 13
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Standardization of information systems . . . . . . . . . . . . . . . . . 15
1.2.1 Definition of IS standardization . . . . . . . . . . . . . . . . . 15
1.2.2 SOA (Service Oriented Architecture) . . . . . . . . . . . . . . 16
1.2.3 SOA Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.4 Characteristics of SOA architecture . . . . . . . . . . . . . . . 16
1.2.5 Advantages of a service-oriented architecture . . . . . . . . . . 17
1.3 Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.1 Web Services Definition . . . . . . . . . . . . . . . . . . . . . 18
1.3.2 The Importance of web services . . . . . . . . . . . . . . . . . 19
1.3.3 Characteristics of Web services . . . . . . . . . . . . . . . . . 19
1.3.4 Operations in a Web service architecture . . . . . . . . . . . . 20
1.3.5 Web Service Architecture . . . . . . . . . . . . . . . . . . . . 21
1.3.6 Web Services Technology . . . . . . . . . . . . . . . . . . . . . 23
1.3.7 Static and dynamic web services . . . . . . . . . . . . . . . . . 28
1.4 Composition of web services . . . . . . . . . . . . . . . . . . . . . . . 29
1.4.1 Definition of composition of web services . . . . . . . . . . . . 29
1.4.2 Life cycle of a web service composition . . . . . . . . . . . . . 29
1.4.3 Types of Service Composition . . . . . . . . . . . . . . . . . . 31
1.5 Web Services Composition Language . . . . . . . . . . . . . . . . . . 33
1.5.1 BPEL definition . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.5.2 Characteristics of BPEL . . . . . . . . . . . . . . . . . . . . . 34
1.5.3 BPEL processes . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.5.4 Elements of a BPEL process . . . . . . . . . . . . . . . . . . . 35
1.5.5 Activities of the BPEL process . . . . . . . . . . . . . . . . . 35
1.6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2 Design And Analysis 37
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.2 Study of the existing . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3 Problem and motivations . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4 Presentation of our case study . . . . . . . . . . . . . . . . . . . . . . 39
2.4.1 Proposed solution . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.2 Presentation of our system . . . . . . . . . . . . . . . . . . . . 40
2.4.3 Our system requirements . . . . . . . . . . . . . . . . . . . . . 43
2.4.4 Our System’s Web Services . . . . . . . . . . . . . . . . . . . 43
2.5 UML modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.2 The UML modeling tool . . . . . . . . . . . . . . . . . . . . . 46
2.5.3 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 47
2.5.4 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.5 Deployment diagram . . . . . . . . . . . . . . . . . . . . . . . 51
2.5.6 Sequence diagram . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3 Implementation 55
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2 The development environment and technical choices. . . . . . . . . . 56
3.2.1 Languages Used . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.2.2 The Software Environment . . . . . . . . . . . . . . . . . . . . 60
3.2.3 Hardware Environment . . . . . . . . . . . . . . . . . . . . . . 63
3.3 Implementation Of The System . . . . . . . . . . . . . . . . . . . . . 64
3.3.1 Database Implementation . . . . . . . . . . . . . . . . . . . . 64
3.3.2 Definition Of Web Services . . . . . . . . . . . . . . . . . . . . 68
3.3.3 Web Services Testing . . . . . . . . . . . . . . . . . . . . . . . 70
3.3.4 Composition Of Web Services . . . . . . . . . . . . . . . . . . 77
3.4 The Interfaces Of Our System . . . . . . . . . . . . . . . . . . . . . . 84
3.5 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 |
| Côte titre : |
MAI/0923
|
|
Ajouter le résultat dans votre panier Affiner la rechercheDevelopment Of A Business Layer to Ensure Communication Between Distributed Information Systems / Ramy Dekari
