Systems engineers

199 quotes found

"God made Homo sapiens a problem-solving creature. The trouble is that He gave us too many resources: too many languages, too many phases of life, too many levels of complexity, too many ways to solve problems, too many contexts in which to solve them, and too many values to balance. First came the law, accounting, and history which looks backward in time for their values and decision-making criteria, but their paradigm (casuistry) cannot look forward to predict future consequences. Casuistry is overly rigid and does not account for statistical phenomena. To look forward man used two thousand years to evolve scientific method - which can predict the future when it discovers the laws of nature. In parallel, man evolved engineering, and later, systems engineering, which also anticipates future conditions. It took man to the moon, but it often did, and does, a poor job of understanding social systems, and also often ignores the secondary effects of its artifacts on the environment. Environmental impact analysis was promoted by governments to patch over the weakness of engineering - with modest success - and it does not ignore history; but by not integrating with system design, it is also an incomplete philosophy. System design and architecture, or simply design, like science and engineering is forward-looking, and provides man with comforts and conveniences - if someone will tell them what problems to solve, and which requirements to meet. It rarely collects wisdom from the backward-looking methodologies, often overlooks ordinary operating problems in designing its artifacts, whether autos or buildings, and often ignores the principles of good teamwork."

- Arthur D. Hall

0 likesPeople from VirginiaElectrical engineersSystems engineers
"The operational sciences hoped to nourish business management, which however largely ignored them, and the latter continues to be undernourished by the business schools which are fairly broad but shallow everywhere. By over focus on short-range financial values, business management in the United States has lost a dozen major markets to the Japanese, added pollution in all its forms, and enriched itself out of all proportion to its value as just one factor of production. Action science, developed by the social sciences over many years in relative isolation from the applied physical sciences, and which might otherwise have humanized them and made engineering more productive, was doomed to fail by being on one end of the two-culture problem wherein science and the humanities do not even speak the same language. I could go on listing a few dozen paradigms: art, law, computer software design, medicine, politics, and architecture, each addressed to a certain context, level, or phase, each good in itself, but each limited to the fields of its origin and its purposes. The methodological problem is the same as if, in designing any large system, each subsystem designer were left to design each subsystem to the best requirements he knew. The overall requirement might not be met; overall harmony could not be achieved, and conflict could ensue to cause failure at the system level. What is envisioned is a new synthesis, a unified, efficient, systems methodology (SM): a multiphase, multi-level, multi-paradigmatic creative problem-solving process for use by individuals, by small groups, by large multi-disciplinary teams, or by teams of teams. It satisfies human needs in seeking value truths by matching the properties of wanted systems, and their parts, to perform harmoniously with their full environments, over their entire life cycles"

- Arthur D. Hall

0 likesPeople from VirginiaElectrical engineersSystems engineers
"In April of 1959, ten of this country's leading scholars forgathered on the campus of Purdue University to discuss the nature of information and the nature of decision... What interests do these men have in common?... To answer these questions it is necessary to view the changing aspect of the scientific approach to epistemology, and the striking progress which has been wrought in the very recent past. The decade from 1940 to 1950 witnessed the operation of the first stored- program digital computer. The concept of information was quantified, and mathematical theories were developed for communication (Shannon) and decision (Wald). Known mathematical techniques were applied to new and important fields, as the techniques of complex- variable theory to the analysis of feedback systems and the techniques of matrix theory to the analysis of systems under multiple linear constraints. The word "cybernetics" was coined, and with it came the realization of the many analogies between control and communication in men and in automata. New terms like "operations research" and "system engineering" were introduced; despite their occasional use by charlatans, they have signified enormous progress in the solution of exceedingly complex problems, through the application of quantitative ness and objectivity."

- Robert E. Machol

0 likesAcademics from the United StatesAerospace engineers from the United StatesSystems engineersNon-fiction authors from the United StatesPeople from New York City
"After earning the PhD degree and acquiring some relatively extensive experience in digital computers… It was time to leave the University. The result of an extensive search for the right job was a family move to Arlington Heights, Illinois, where it was a short commute to the Research Laboratories of the Pure Oil Company at Crystal Lake. I was given the title of Mathematical and Computer Consultant. The Labs were set in a beautiful campus, the professional personnel were eager to learn what I had to teach and to include me in many interesting projects where my knowledge and skills could be put to good use. I was encouraged to initiate my own program of research. I went to work with enthusiasm. The corporate headquarters of Pure Oil were located in down town Chicago. Pure Oil had been trying to install an IBM 705 computer system for all their accounting needs including calculation of all data necessary for the management of exploration, drilling, refining and distribution of oil products and even royalties to shareholders in oil wells. Typical for those early days, the programming team was in deep difficulties and needed help; they lacked adequate resources and suitable training. The Executive Vice President of Pure Oil, when he heard that there was a computer expert already on the payroll at the Crystal Lake lab, ended our family blissful dream and I was reassigned to the down town office."

- A. Wayne Wymore

0 likesSystems engineersAcademics from the United StatesMathematicians from the United States
"In April 1946, when I came to Hughes Aircraft to institute high-technology research and development, it was far from the place it was to become. Howard Hughes, I was informed, rarely came around. When he did show up, it was to take up one or another trivial issue. He would toss off detailed directions, for instance, on what to do next about a few old airplanes decaying out in the yard or what kind of seat covers to buy for the company-owned Chevrolets, or he would say he wanted some pictures of clouds taken from an airplane. An accountant from Hughes Tool Co. ((started by Howard's father)) had the title of general manager but was there only to sign checks. A few of Howard's flying buddies were on the payroll, using assorted fanciful titles like some in Gilbert and Sullivan's Mikado, but apparently did next to nothing. A lawyer was on hand to process contracts, but there were practically none. In addition to the Spruce Goose flying freighter, a mammoth eight-engine plywood seaplane that barely managed to fly even once, there was an experimental Navy reconnaissance plane under development (which, with Hughes at the controls, later crashed, almost killing him). The contracts for both planes had been canceled. Perhaps, I said to myself, this is one of those unforeseeable lucky opportunities. Why not use Hughes Aircraft as a base to create a new and needed defense electronics supplier?"

- Simon Ramo

0 likesPhysicists from the United StatesBusiness theorists from the United StatesSystems engineersPeople from UtahPeople from Salt Lake City