Ahmed Elsawi | Polish Japanese Institute of Information Technology (original) (raw)

Papers by Ahmed Elsawi

Research paper thumbnail of The Electronic Judicial Notice: Between Legalization and Technology

Journal of Arts and Social Sciences [JASS], 2019

The judicial notice is unquestionably important, and flawed execution undermines the procedural a... more The judicial notice is unquestionably important, and flawed execution undermines the procedural action and negates its legal effects. In this regard, the means used to deliver the judicial notice to the addressee, its speed, and its appropriateness for the context are as important as the notice itself. Traditional notification methods have become inefficient, both in terms of the simplification of procedures and in saving effort, time, and expenditure. This reveals the importance of this research: it aims primarily to activate the use of the electronic judicial notice and access to a mechanism that harmonizes modernity and technological development while maintaining the guarantees inherent in and the validity ofthe proceedings.

Research paper thumbnail of Introducing the open source metamodel concept

The Model Driven Architecture (MDA) is a model centric software engineering methodology that aimi... more The Model Driven Architecture (MDA) is a model centric software engineering methodology that aiming to enhance software productivity, reusability, maintainability and quality by focusing on models and metamodels in place of conventional code. By adopting the separation of concern these models defined in different levels of abstraction where each model syntactically conforms to a particular metamodel. Under the MDA context this work presents a novel approach for representing models and metamodels. Benefiting from the knowledge representation capability and the open structure of the Entity Attribute Value (EAV) model, we represent metamodels and its instance models in a single EAV designed repository in to support of model transformations and introducing a new concept of what we call it an Open Source Metamodel. Also this work demonstrate an integration between UML static and behavioral models

Research paper thumbnail of Model Driven Atchitecture in to Support of Software Product Line

Product management is focusing on variation description; as current and future possible market po... more Product management is focusing on variation description; as current and future possible market positioning, acceptable limitations, business opportunity, etc. On the other hand, the Architectural Modeling is concentrating on creation and description of software platform and how it extends and evolves to deliver and support all or any of these product management and product line scenarios. In product line engineering software features are always defined by the variability model. While the requirements specifications, architectural, design, implementation and testing are normally captured by the solution space. In this work we are utilizing the architectural modeling concept of the Model Driven Architecture (MDA) as a complementary of the software product line concerning the solution space part. Aiming to improve software quality and productivity the MDA principles has been adopt. We explicitly employed the Platform Model (PM) designed by the Entity-Attribute-Value (EAV) concept, to provision the transformation between Platform Specific Models (PSM) to the targeted platforms from side, and to manage the platforms diversity and volatility from other side. A case study presented to demonstrate the software productivity under the orthogonal relationship between the MDA and the SPL at the later solution space side.

Research paper thumbnail of The civil liability of the consortium members for the individual mistake of one member

International Journal of Engineering & Technology, Apr 15, 2018

Nowadays, the various forms of contractual agreements have spread between the different contracti... more Nowadays, the various forms of contractual agreements have spread between the different contracting companies for the purpose of executing the huge international contracts which require the synergy of all efforts. This has led to the appearance of new forms of cooperation between the international contractors, called the "Consortium Agreement", which is a kind of special partnership entered into for the purpose of executing a certain project, and ends at the completion of this project, without the constitution of a separate entity for the parties of this consortium. Nonetheless, many and various legal implications result from this consortium, some of which may be attributed to the subordination relationship between this agreement and the international contract of construction; while other legal implications might be attributed to the Consortium Agreement itself. The main problem in this regard may arise, if the consortium members did not agree on the accurate determination of the civil liability for each party, whether it was during the pre-contractual stage, or during the contract's execution; as well as the specific determination of the consortium members' liability towards the employer for the individual mistake of one member, especially in light of the multiple parties and the unity of purpose. In this regard, the liability may take one of the following two forms: first, to consider all members of the consortium as joint partners before the employer; second, to adopt the personal liability of each member separately, thus, each member shall be liable only for the part assigned to him. Hence, we will try here to answer a major question regarding the liability of the consortium members for the individual error of one member towards each other or towards the employer, taking into consideration the special nature of the Consortium Agreement.

Research paper thumbnail of The Electronic Judicial Notice: Between Legalization and Technology

Journal of Arts and Social Sciences [JASS], 2019

The judicial notice is unquestionably important, and flawed execution undermines the procedural a... more The judicial notice is unquestionably important, and flawed execution undermines the procedural action and negates its legal effects. In this regard, the means used to deliver the judicial notice to the addressee, its speed, and its appropriateness for the context are as important as the notice itself. Traditional notification methods have become inefficient, both in terms of the simplification of procedures and in saving effort, time, and expenditure. This reveals the importance of this research: it aims primarily to activate the use of the electronic judicial notice and access to a mechanism that harmonizes modernity and technological development while maintaining the guarantees inherent in and the validity ofthe proceedings.

Research paper thumbnail of Introducing the open source metamodel concept

The Model Driven Architecture (MDA) is a model centric software engineering methodology that aimi... more The Model Driven Architecture (MDA) is a model centric software engineering methodology that aiming to enhance software productivity, reusability, maintainability and quality by focusing on models and metamodels in place of conventional code. By adopting the separation of concern these models defined in different levels of abstraction where each model syntactically conforms to a particular metamodel. Under the MDA context this work presents a novel approach for representing models and metamodels. Benefiting from the knowledge representation capability and the open structure of the Entity Attribute Value (EAV) model, we represent metamodels and its instance models in a single EAV designed repository in to support of model transformations and introducing a new concept of what we call it an Open Source Metamodel. Also this work demonstrate an integration between UML static and behavioral models

Research paper thumbnail of Model Driven Atchitecture in to Support of Software Product Line

Product management is focusing on variation description; as current and future possible market po... more Product management is focusing on variation description; as current and future possible market positioning, acceptable limitations, business opportunity, etc. On the other hand, the Architectural Modeling is concentrating on creation and description of software platform and how it extends and evolves to deliver and support all or any of these product management and product line scenarios. In product line engineering software features are always defined by the variability model. While the requirements specifications, architectural, design, implementation and testing are normally captured by the solution space. In this work we are utilizing the architectural modeling concept of the Model Driven Architecture (MDA) as a complementary of the software product line concerning the solution space part. Aiming to improve software quality and productivity the MDA principles has been adopt. We explicitly employed the Platform Model (PM) designed by the Entity-Attribute-Value (EAV) concept, to provision the transformation between Platform Specific Models (PSM) to the targeted platforms from side, and to manage the platforms diversity and volatility from other side. A case study presented to demonstrate the software productivity under the orthogonal relationship between the MDA and the SPL at the later solution space side.

Research paper thumbnail of The civil liability of the consortium members for the individual mistake of one member

International Journal of Engineering & Technology, Apr 15, 2018

Nowadays, the various forms of contractual agreements have spread between the different contracti... more Nowadays, the various forms of contractual agreements have spread between the different contracting companies for the purpose of executing the huge international contracts which require the synergy of all efforts. This has led to the appearance of new forms of cooperation between the international contractors, called the "Consortium Agreement", which is a kind of special partnership entered into for the purpose of executing a certain project, and ends at the completion of this project, without the constitution of a separate entity for the parties of this consortium. Nonetheless, many and various legal implications result from this consortium, some of which may be attributed to the subordination relationship between this agreement and the international contract of construction; while other legal implications might be attributed to the Consortium Agreement itself. The main problem in this regard may arise, if the consortium members did not agree on the accurate determination of the civil liability for each party, whether it was during the pre-contractual stage, or during the contract's execution; as well as the specific determination of the consortium members' liability towards the employer for the individual mistake of one member, especially in light of the multiple parties and the unity of purpose. In this regard, the liability may take one of the following two forms: first, to consider all members of the consortium as joint partners before the employer; second, to adopt the personal liability of each member separately, thus, each member shall be liable only for the part assigned to him. Hence, we will try here to answer a major question regarding the liability of the consortium members for the individual error of one member towards each other or towards the employer, taking into consideration the special nature of the Consortium Agreement.