Mohamed Jber | Sudan university of Science and technology (original) (raw)

Papers by Mohamed Jber

Object technology is believed to be crucial in achieving the long sought-after goal of widespread... more Object technology is believed to be crucial in achieving the long sought-after goal of widespread reuse. This goal is the most frequently stated reason for adopting OT. Unfortunately, many people naively equate reuse with objects, expecting it to "automatically" ensure reuse, but often do not get much reuse. Based on my experience with reuse at HP, Objectory and Rational, and with many customers, I know that without extensive changes to support component-based development and systematic reuse, OT as used today will not succeed in giving users reuse. Without an explicit reuse agenda, and a systematic approach to the design and use of reusable components and frameworks, 00 reuse will not succeed. In almost all cases of successful reuse, architecture, a dedicated component development and support group, management support, and a stable domain were the keys to success. These largely non-technical issues seem to be more important to successful reuse than the specific language or design chosen.

The pre-natal death of the Corporate Information System (CIS) project The invisible target princi... more The pre-natal death of the Corporate Information System (CIS) project The invisible target principle All critical system attributes must be specified clearly. Invisible targets are usually hard to hit (except by chance).

Software Engineering, IEEE …, Jan 1, 1984

... Divided into two parts, this textbook addresses every stage of requirements engineering--from... more ... Divided into two parts, this textbook addresses every stage of requirements engineering--fromelicitation, validation, and management to non-functional specification, classical techniques, viewpoint-oriented techniques, and interactive specifications. top of page AUTHORS. ...

... 11526051. Software Engineering Report of a conference sponsored by the NATO Science Committee... more ... 11526051. Software Engineering Report of a conference sponsored by the NATO Science Committee Garmisch Germany 7th-11th October 1968 (1969). ... Herausgeber, Scientific Affairs Division, NATO. Archiv, University of Newcastle Library E-Print Archives (United Kingdom). ...

... Software engineering metrics and models. ... Publication: · Book, Software engineering metric... more ... Software engineering metrics and models. ... Publication: · Book, Software engineering metrics and models. Benjamin-Cummings Publishing Co., Inc. Redwood City, CA, USA ©1986 ISBN:0-8053-2162-4. 1986 Book. Bibliometrics. ...

Conceptual modeling: Foundations and …, Jan 1, 2009

Essentially a software system's utility is determined by both its functionality and its non-funct... more Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.

… , Software Engineering Institute, Camegie Mellon …, Jan 1, 1994

Many software development defects are caused by misunderstandings and confusion.

Handbook of software reliability engineering / Michael R. Lyu, editor in chief. p. cm. Includes i... more Handbook of software reliability engineering / Michael R. Lyu, editor in chief. p. cm. Includes index. ISBN 0-07-039400-8 (alk. paper) 1. Computer software-Reliability-Handbooks, manuals, etc. I. Lyu, Michael R. QA76.76.R44H36 1995 005.1 -dc20 95 -46468 CIP

Recherche, Jan 1, 2001

... interruption. Plus d'un mill... more ... interruption. Plus d'un million de titres à notre catalogue ! »Afficher votre panier«. WebAnalytics solution by WebAnalytics - AT Internet. Notice. Imprimer la notice. Component based software engineering : putting the pieces together. ...

This book provides selective, in-depth coverage of the fundamentals of software engineering by st... more This book provides selective, in-depth coverage of the fundamentals of software engineering by stressing principles and methods through rigorous formal and informal approaches. In contrast to other books which are based on the lifecycle model of software development, ...

Artificial intelligence, Jan 1, 2000

Cleanroom software engineering is a theory-based, team-oriented engineering process for developin... more Cleanroom software engineering is a theory-based, team-oriented engineering process for developing and certifying very high quality software under statistical quality control.(The name “Cleanroom” was chosen in analogy to the precision engineering of hardware ...

Software Engineering, IEEE Transactions on, Jan 1, 1984

Tata McGraw Hill Publication Tata …, Jan 1, 1982

Object technology is believed to be crucial in achieving the long sought-after goal of widespread... more Object technology is believed to be crucial in achieving the long sought-after goal of widespread reuse. This goal is the most frequently stated reason for adopting OT. Unfortunately, many people naively equate reuse with objects, expecting it to "automatically" ensure reuse, but often do not get much reuse. Based on my experience with reuse at HP, Objectory and Rational, and with many customers, I know that without extensive changes to support component-based development and systematic reuse, OT as used today will not succeed in giving users reuse. Without an explicit reuse agenda, and a systematic approach to the design and use of reusable components and frameworks, 00 reuse will not succeed. In almost all cases of successful reuse, architecture, a dedicated component development and support group, management support, and a stable domain were the keys to success. These largely non-technical issues seem to be more important to successful reuse than the specific language or design chosen.

The pre-natal death of the Corporate Information System (CIS) project The invisible target princi... more The pre-natal death of the Corporate Information System (CIS) project The invisible target principle All critical system attributes must be specified clearly. Invisible targets are usually hard to hit (except by chance).

Software Engineering, IEEE …, Jan 1, 1984

... Divided into two parts, this textbook addresses every stage of requirements engineering--from... more ... Divided into two parts, this textbook addresses every stage of requirements engineering--fromelicitation, validation, and management to non-functional specification, classical techniques, viewpoint-oriented techniques, and interactive specifications. top of page AUTHORS. ...

... 11526051. Software Engineering Report of a conference sponsored by the NATO Science Committee... more ... 11526051. Software Engineering Report of a conference sponsored by the NATO Science Committee Garmisch Germany 7th-11th October 1968 (1969). ... Herausgeber, Scientific Affairs Division, NATO. Archiv, University of Newcastle Library E-Print Archives (United Kingdom). ...

... Software engineering metrics and models. ... Publication: · Book, Software engineering metric... more ... Software engineering metrics and models. ... Publication: · Book, Software engineering metrics and models. Benjamin-Cummings Publishing Co., Inc. Redwood City, CA, USA ©1986 ISBN:0-8053-2162-4. 1986 Book. Bibliometrics. ...

Conceptual modeling: Foundations and …, Jan 1, 2009

Essentially a software system's utility is determined by both its functionality and its non-funct... more Essentially a software system's utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.

… , Software Engineering Institute, Camegie Mellon …, Jan 1, 1994

Many software development defects are caused by misunderstandings and confusion.

Handbook of software reliability engineering / Michael R. Lyu, editor in chief. p. cm. Includes i... more Handbook of software reliability engineering / Michael R. Lyu, editor in chief. p. cm. Includes index. ISBN 0-07-039400-8 (alk. paper) 1. Computer software-Reliability-Handbooks, manuals, etc. I. Lyu, Michael R. QA76.76.R44H36 1995 005.1 -dc20 95 -46468 CIP

Recherche, Jan 1, 2001

... interruption. Plus d'un mill... more ... interruption. Plus d'un million de titres à notre catalogue ! »Afficher votre panier«. WebAnalytics solution by WebAnalytics - AT Internet. Notice. Imprimer la notice. Component based software engineering : putting the pieces together. ...

This book provides selective, in-depth coverage of the fundamentals of software engineering by st... more This book provides selective, in-depth coverage of the fundamentals of software engineering by stressing principles and methods through rigorous formal and informal approaches. In contrast to other books which are based on the lifecycle model of software development, ...

Artificial intelligence, Jan 1, 2000

Cleanroom software engineering is a theory-based, team-oriented engineering process for developin... more Cleanroom software engineering is a theory-based, team-oriented engineering process for developing and certifying very high quality software under statistical quality control.(The name “Cleanroom” was chosen in analogy to the precision engineering of hardware ...

Software Engineering, IEEE Transactions on, Jan 1, 1984

Tata McGraw Hill Publication Tata …, Jan 1, 1982