20th-century Engineer Quotes
I started keeping a list of these annoyances but it got too long and depressing so I just learned to live with them again. We really are using a 1970s era operating system well past its sell-by date. We get a lot done, and we have fun, but let's face it, the fundamental design of Unix is older than many of the readers of Slashdot, while lots of different, great ideas about computing and networks have been developed in the last 30 years. Using Unix is the computing equivalent of listening only to music by David Cassidy.
I strongly feel that, if we are successful, our program will mark the beginning of a renaissance for manned space flight. This might even be similar to that wonderful time period between 1908 and 1912 when the world went from a total of ten airplane pilots to hundreds of airplane types and thousands of pilots in 39 countries. We need affordable space travel to inspire our youth, to let them know that they can experience their dreams, can set significant goals and be in a position to lead all of us to future progress in exploration, discovery and fun. Thanks to the X PRIZE [Foundation] for the inspiration.
Like many fields in their early stages, the software field has had its share of project disasters: the software equivalents of Beauvais Cathedral, the S. S. Titanic, and the "Galloping Gertie" Tacoma Narrows Bridge. The frequency of these disaster projects is a serious concern: a recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project.
Enterprise Engineering is defined as that body of knowledge, principles, and practices having to do with the analysis, design, implementation and operation of an enterprise. In a continually changing and unpredictable competitive environment, the Enterprise Engineer addresses a fundamental question: how to design and improve all elements associated with the total enterprise through the use of engineering and analysis methods and tools to more effectively achieve its goals and objectives...
We consider an organization to be a set of constraints on the activities performed by agents. This view follows that of Weber, who views the process of bureaucratization as a shift from management based on self-interest and personalities to one based on rules and procedures.
The world about us can be looked at in a variety of ways. One way is to see the world as made up from many interacting systems: weather, societal, economic, ecological, floral, faunal, tectonic plate, oceanic, and so on. This is very much a connected view of the world: nothing is isolated and totally independent; everything is part of something bigger, and everything comprises many interacting parts — subsystems.
Project management is the planning, organizing, directing, and controlling of company resources for a relatively short-term objective that has been established to complete specific goals and objectives. Furthermore, project management utilises the systems approach to management by having functional personnel (the vertical hierarchy) assigned to a specific project (the horizontal hierarchy).
I would like to comment briefly on Professor Zadeh's presentation. His proposals could be severely, ferociously, even brutally criticized from a technical point of view. This would be out of place here. But a blunt question remains: Is professor Zadeh presenting important ideas or is he indulging in wishful thinking? No doubt Professor Zadeh's enthusiasm for fuzziness has been reinforced by the prevailing climate in the U.S.-one of unprecedented permissiveness. 'Fuzzification, is a kind of scientific permissiveness; it tends to result in socially appealing slogans unaccompanied by the discipline of hard scientific work and patient observation.
Human anatomy is either general, specific, topographical or surgical. These terms do not imply the dissection and anatomy of generals, specialists, topographers and surgeons, as they might seem to imply, but really mean something else. I would explain here what they actually do mean if I had more room and knew enough to do it.
Business process engineering aims to achieve the greatest efficiency possible in terms of business-organizational solutions. Organizational departments, reengineering project teams or even business process owners can be responsible for process engineering. While work schedule development for manufacturing processes might be institutionally allocated to a certain department for years as job preparation, other kinds of business processes are not quite as regimented.