Chief Technology Officer (CTO)
TiknoSoft Information Sciences, Co.
Total years of experience :31 years, 5 Months
§ Maintain most of the technical executive operations of TiknoSoft in Egypt and Abroad.
§ Directing and participating in development of couple of critical mission applications. The main market is focused on Arab Gulf area. Projects are employing a lot of technologies such as .NET, Javascript, JQuery, AngularJS, Joomla, Drupal, MSSQL, MS Visual Studio, CSS, Web Development, PHP, Mobile Development, Object Pascal, and DataFlex.
Consolidate all my successful experience into "Full Stack Software Services, Products, and Consultancy. Using wide gained experience with commercial and government information technology (IT) projects including skills and knowledge in Project Management, Security Systems, Software Production, Databases and Applications, CMMI Process Improvement, Decision Analysis, Software Engineering and Quality Assurance, Financial Database Applications, Microsoft Development Tools and Mobile Applications. Focus on Mobile and Web Applications and Service.
§ IT Solutions Consultant - Triamer Information Sciences, Inc - USA - Providing full-time IT Consultancy Services for the company Operations through the Globe including USAID projects.
§ Senior Management Information System (MIS) Specialist for Family Justice Project - Cairo, Egypt, a USAID funded project under the Agreement No. 294-263 between the Government of Egypt (GOE) and the Government of the United States of America. (End at Feb, 2007)
Care Services SAE.- Cairo - Electronic Security Dept., since 2002, I offered the technical support in making offers, and execute projects in the field of IT. An important example is the electronic security system using LAN for the Kadbury Factory - at 10th of Ramadan city.
This thesis is concerned with the invention of an object-oriented framework for database applications developers, which increases the re-usability and maintainability of business rules logic. The suggested framework would apply the object oriented concepts and components technology to establish a model for reusable business objects. The RBRM stands for “Reusable Business Rules Model”. The RBRM is composed of four (4) layers, (Reusable Library Layer1, Reusable Business Rules Layer2, Reusable Interface B.Rules Layer3, and Application Presentation Layer4). The Reusable Library Layer1 will be expressed by the HMBRulesBase which is the ancestor class of all business rules classes implemented using the RBRM. The work will introduce a proposal for a group of real business applications which can be developed based on the RBRM framework, while taking the General Ledge (GL) application as the reusable core business rules. The General Ledger (GL) application will be used as the main core application for exploring the RBRM framework. All tables of the GL application will be represented as RBRM business rules classes. A complete tour of how to implement the RBRM layers will be discussed in details. The tour starts by the Physical Data Model (PDM), passing through tables designs documentation, business rules presentation, business rules statements, and ends by application presentation layer-4. After having that tour the reader will be ready to start implementation of the RBRM for any other database application to be reusable. Furthermore, the reader will experience a sophisticated algorithm of how to do standard design, documentation, and implementation of reusable business rules. The separation of business rules logic from the user-interface is one advantage of implementing RBRM framework. This separation increases the maintainability of the application by isolating the business rules from any further modifications or additions to the user interface logic. Also, it increases the maintainability and re-usability by keeping the chance of encapsulating more business rules & logic into layer-2 while keeping the user-interface (layer-4) as it is. Furthermore, it increases the portability between Database Engines without sensible changes in the application code. So, RBRM increases the ability to reuse a whole application from one database engine to another without any changes at all, or simply by making small changes, and get basically the same results. A preparation process for the General Ledger business rules will be discussed, so that the HMJOURNALH_CLASS2_EXTERN class will be produced as the interface class for external applications integrating with General Ledger application. Four (4) examples of reusing scopes will be shown including two external applications examples (Accounts Payable & Payroll). An intuitive benefit of the RBRM framework, which is the polymorphism implementation of the business objects plugged into the user-interface will be discussed. By following up the object oriented concepts and rules of the RBRM the resulting applications will have the facility of recreating as many user-interface forms objects of the same source form class as user needs. This is happening while having all forms objects connected to the same business rules methods and keeping all forms objects working simultaneously & independently through the same database engine connection. This results resources using minimization, and faster achievement for the end-user. An example of the Self-Reusing within business rules scope was found while implementing the GL business rules classes in layer-2.