حكاية مصري بجواز سفر أمريكي بقلم : الأستاذ الدكتور محمد فياض
$8.59 – $14.99
I am an American of Egyptian descent, a university professor, scientist, and founder of some new sciences. I am 72 years old, a resident of San Jose, and a lover of all humanity. However, my company and I have long suffered from collective injustices from most people and organizations I deal with. I am facing disastrous problems and severe obstacles in my work and private life, as if this is an intentional thing and a systematic campaign against me and all the innovators and their companies in Egypt, America, and the Arab countries in general. People, communities, and organizations must unite worldwide to do good and help those in need. However, unfortunately, many people and man y governmental and civil organizations join and gather to do me wrong as if they find pleasure in it, whether in the USA or Egypt, as if they were enjoying my pain, getting high while sipping from my flowing blood in full cups, and eating at the table of my tragedy as if only they were at their last supper. It seems that these problems I suffer from also affect all startups and their founders, as injustice has spread, justice is missing, conscience is dead, and morals are lost. If all these abuses are against me only, then I reluctantly accept them. However, suppose they extend to affect the human community as a whole. In that case, we must stand up and combat this injustice and resist the hateful racism that destroyed the dreams of millions of people, including me. Should we, as a human society, wait for the advent of another Martin Luther King, waging wars to end racism and injustice to all human beings? In Your Hands is a book from a series that depicts my tragedy and personal experience. I deposited my grievances between its covers to be read by every person with a lively conscience, an enlightened mind, and a heart that beats with truth and goodness. This is to relieve me of the injustice that has befallen me and restore some of my lost rights. If you have the same experience and suffer from the same tragedy, please get in touch with me to unite to eliminate the injustice against you and my startup companies. We are the basis of renaissance, civilization, and development worldwide.
BOOK |
Hardcover ,Paperback ,Kindle |
---|
Product details
-
Publisher : AEEH PRESS INC
-
Release Date: January 15, 2025
-
Number of Pages – 161 pages
-
Language : English
-
Paperback : 255 pages
-
ISBN-13 :
(Ready to be Published)
-
Item Weight : 1.14 pounds
-
Dimensions : 6 x 0.68 x 9 inches
Book flyers
Copyright © 2025 AEEH PRESS INC
All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the written permission of the author.


MAECENAS IACULIS
Vestibulum curae torquent diam diam commodo parturient penatibus nunc dui adipiscing convallis bulum parturient suspendisse parturient a.Parturient in parturient scelerisque nibh lectus quam a natoque adipiscing a vestibulum hendrerit et pharetra fames nunc natoque dui.
ADIPISCING CONVALLIS BULUM
- Vestibulum penatibus nunc dui adipiscing convallis bulum parturient suspendisse.
- Abitur parturient praesent lectus quam a natoque adipiscing a vestibulum hendre.
- Diam parturient dictumst parturient scelerisque nibh lectus.
Scelerisque adipiscing bibendum sem vestibulum et in a a a purus lectus faucibus lobortis tincidunt purus lectus nisl class eros.Condimentum a et ullamcorper dictumst mus et tristique elementum nam inceptos hac parturient scelerisque vestibulum amet elit ut volutpat.
Related products
Concurrent Software Development Model (CSDM) (Software Stability Model (SSM))
Software Stability Model (SSM) is a radically new and disruptive innovation in the field of software engineering. It is a new way of looking at how any software development effort should be undertaken, different from the approaches that we see today. SSM moves on from the traditional ways of software development where a specific software artifact is developed for every different specific application scenario to an approach that promotes factoring in the needs for the future as well and thus making the software thus developed, ‘stable’ over time, i.e.it need not be changed in a big way repeatedly. SSM provides unique and unified methodology such as high returns on investment, complete and comprehensive development of concurrent, unified, stable, executable functional and non-functional requirements, Ultimate Design, Unified Software Architectures on-Demand, and unified Immune Testing, etc. SSM brings along a list of qualities, such as true unification, stability, scalability, adaptability, extensibility, configurability, maintainability, unlimited reuse, applicability, and more to any software developed in any domain along the lines of this development methodology. SSM also does not draw a hard line of transition between the various steps in any software development methodology. For example, the requirements, design, coding, and testing for any given functionality are done in one go. Such activities can be done for each of the functionalities that have to be included in the software, in a concurrent fashion, thus SSM can also be termed as the Concurrent Software Development Model (CSDM). This presentation is an introduction to the Software Stability Model and how it can be used for any software development undertaking from start to the delivery.
Software Engineering in The Small.
Over the past many years, software has become a vital component of almost every business and national economy. Virtually any product or service has become software enabled. As a result, organizations’ competitiveness largely depends on their ability to use the software as a competitive weapon. What makes the competitive landscape more complex is the kind of pressures organizations face in terms of time to market, new features, cost, and, of course, quality and reliability. Furthermore, organizations are finding it increasingly challenging to operate as convergence, discontinuity, and economic boundarylessness lead to the birth of a new breed of global customers. And any organization’s survival—let alone success—is therefore clearly becoming dependent on an ability to understand the characteristics of such international customers and serve them accordingly. In their quest for software excellence, organizations must rely increasingly on software engineering techniques and methodologies and rely on and refine their traditional business strategies. This book: 1. Extends four well-known CACM thinking (O=Object) Objective Software Engineering in the Small columns: I. Software Engineering in the Small II. Problems with Scalability III. Management in the Small IV. Process Improvement in the Small 2. Discuss the September/October 2000, IEEE Software Introduction: Software Engineering in the Small theme Issue 3. Comments and explains responses, 4. Answers many questions.
Software Process Development
The software/system process is the fundamental way of abstracting and implementing software/system functional and non-functional requirements, design, architectures, and software testing. Software process describes the steps required to abstract and develop some goal, usually unified skills. Software Processes transform textbook theories and method descriptions into actual action steps. It is essential to realize that processes are codified steps that describe a particular organization's way of achieving development goals. That means development processes cannot be acquired off the shelf but must be developed over time. Management must support the move to process-based development. The software process must be maintained when schedule pressures loom, or process costs initially slow some development phases. Development Processes are essential for innovation development teams, even in a well-organized group. Individuals will often perceive themselves as less skilled than before, and the routines they have established with others will undoubtedly change. Management must ensure that setting process-oriented development will allow team members to contribute positively. This book: 1. Extends four well-known CACM thinking (O=Object) Objective Software Process Development columns: I. Software Development Processes: The Necessary Evil II. Process Assessment: Considered Wasteful III. Surviving a Process Performance Crash IV. The Art of Managing Multiple Processes 2. Comments and explains responses, 3. Answers many questions. 4. Illustrates Software Development Process in three ways: Textual, Dataflow Diagram, and Activity Diagram.
The Brutality of Tyrants – First Volume by Dr. M.E. Fayad,
In The Brutality of Tyrants, Dr. Mohamed Fayad recounts his journey through systemic injustice, racism, and corruption that profoundly impacted both his personal and professional life. His story extends beyond individual experiences, revealing public issues affecting millions of American citizens today. Dr. Fayad’s experiences within academia, healthcare, and financial institutions illustrate how individuals and systems have not only marginalized him but continue to suppress countless others. Facing deliberate negligence, exclusion, and even threats to his life, Dr. Fayad’s narrative highlights the devastating impact of institutional oppression on everyday citizens. This book is not intended to offend any person, institution, group, political party, government, or country. Rather, it is Dr. Fayad’s means of reporting his own experiences, with the hope that recounting these injustices will prevent them from happening to others. His account critiques the failure of justice in America, particularly for marginalized individuals, and underscores the urgent need for reforms across multiple sectors within the nation. The Brutality of Tyrants serves as both a personal memoir and a broader critique of institutional oppression, issuing a strong call for accountability and change in what Dr. Fayad describes as one of the greatest nations on Earth. Through his narrative, he urges readers to confront the corruption and inequality that persist in America, hoping to inspire a collective push toward a fairer, more transparent system for all.
The Success of Achieving the Ultimate Goals of Any Word When Clearly Defined (Any Culture, Any Advice, Any Slogan, and Any Task )
Capabilities (WORDs) are the business-centric workhorses called Business Objects (BOs) that support the realization of fulfillment of a goal where goals (WORDs) are Enduring Business-centric Themes called (EBTs). Goals and capabilities are enduring artifacts, but with a minor difference: They are externally adaptable via hooks that are easily connected to the application objects called Industrial Objects (IOs) The Goals and Capabilities present the problem space, which are stable and unified functional requirements that do not exist in current system development. The “Golden Rule”: Ultimate Goal (UG) is considered to be the first of more than 50 discovery keys and follows the “golden rule”: (1) Most BOs have a unified, Stable, and final goal. (2) A few BOs have two goals. (3) Rare BOs have three goals. This volume shows that the ultimate goals that are discovered of: Any Culture, Any Advice, Any Slogan, and Any Task.
The Success of Achieving the Ultimate Goals of Any Word When Clearly Defined (Any Project, Any Proposal, Any Debate, Any Strategy)
Capabilities (WORDs) are the business-centric workhorses called Business Objects (BOs) that support the realization of fulfillment of a goal where goals (WORDs) are Enduring Business-centric Themes called (EBTs). Goals and capabilities are enduring artifacts, but with a minor difference: They are externally adaptable via hooks that are easily connected to the application objects called Industrial Objects (IOs) The Goals and Capabilities present the problem space, which are stable and unified functional requirements that do not exist in current system development. The “Golden Rule”: Ultimate Goal (UG) is considered to be the first of more than 50 discovery keys and follows the “golden rule”: (1) Most BOs have a unified, Stable, and final goal. (2) A few BOs have two goals. (3) Rare BOs have three goals. This volume shows that the ultimate goals that are discovered of: Any Project, Any Proposal, Any Strategy, and Any Debate.
Unified Software Engineering Reuse (USER)
USER and systems built by using it answer the problems of low reuse, high costs, phasing out software solutions, components with significant impedance mismatch to be reused, and more. Research and development done for USER would enable the practitioners and researchers of software engineering to look at new ways of developing software that solves these problems, especially dealing with the issues associated with requirements and domain analysis in reuse. Unified Software Engineering Reuse (USER) would give rise to a new way of looking at software and building software solutions. USER can enable interdisciplinary research development in a big way and can bring different bodies of knowledge, and applications together, e.g., for biochemistry, bioinformatics, medicine, media, etc. USER enables building software systems that are self-adaptable and applicable for applications spanning multiple domains, unlike traditional software tools. It can be a catalyst for bringing scientists and students from varied fields to a common ground and building applications across these different bodies of knowledge. USER takes the field of software engineering to the next level. Software has become integral to everything our environment consists of today. The book presents a pragmatic and an intuitive approach to understanding the problem of existing reuse and utilizing USER as the central perspective of experience and business-centric intuition (stable reuse techniques and assets).
الطريق إلى النجاح: تحقيق الأهداف النهائية لأي كلمة عند تحديدها
Capabilities (WORDs) are the business-centric workhorses called Business Objects (BOs) that support the realization of fulfillment of a goal where goals (WORDs) are Enduring Business-centric Themes called (EBTs). Goals and capabilities are enduring artifacts, but with a minor difference: They are externally adaptable via hooks that are easily connected to the application objects called Industrial Objects (IOs) The Goals and Capabilities present the problem space, which are stable and unified functional requirements that do not exist in current system development. The “Golden Rule”: Ultimate Goal (UG) is considered to be the first of more than 50 discovery keys and follows the “golden rule”: (1) Most BOs have a unified, Stable, and final goal. (2) A few BOs have two goals. (3) Rare BOs have three goals. This volume shows that the ultimate goals that are discovered of: Any Culture, Any Advice, Any Slogan, and Any Task.
Reviews
There are no reviews yet.