Software Engineering quotes

From Motley Bytes Wiki
Jump to: navigation, search

Robert_S_Barton

Software from the Middle

“I think at this point in the field we are almost forced to start in the middle, if we are concerned with the problem of general software construction and the organization of the machines to go with these programs.”
Keywords: Software_Engineering_quotes Point_quotes Field_quotes Force_quotes Start_quotes Middle_quotes Concern_quotes Problem_quotes General_quotes Software_quotes Construction_quotes Organization_quotes Machine_quotes Program_quotes Think_quotes

Friedrich_Ludwig_Bauer

Need for Software Engineering

“What we need is Software Engineering.”
  • Source: Friedrich Ludwig Bauer's words at the end of 1967 within the NATO Science Committee charged with assessing the entire field of Computer Science. First generally recorded use of the term software engineering. Bauer also used the term in 1968 in a NATO conference in Garmisch-Partenkirchen, Germany. Reported on page 119 of the book entitled Origins and Foundations of Computing. Written by Friedrich Ludwig Bauer. Published by Springer in 2010. New York, NY. ISBN: 9783642425639.
Keywords: Software_Engineering_quotes Need_quotes Software_quotes Engineering_quotes

Tinkering versus Engineering

“The time has arrived to switch from home-made software to manufactured software, from tinkering to engineering.”
  • Source: Quoted in the book entitled Mechanizing Proof: Computing, Risk, and Trust by Donald Mackenzie. Published in 2001 by Massachusetts Institute of Technology. ISBN: 0262133938.
Keyword: Software_Engineering_quotes Programming_quotes Time_quotes Arrive_quotes Switch_quotes Home_quotes Make_quotes Software_quotes Manufacture_quotes Tinker_quotes Engineering_quotes

Software Engineering Too Difficult

“Software engineering is the part of computer science which is too difficult for the computer scientist.”
  • Source: [Bauer; 1972]. A paper entitled Software Engineering. Written by Friedrich Ludwig Bauer. Published 1972 in Information Processing 71: Proceedings of Ifip Congress 1971, volume 1. ISBN: 9780720420630.
Keywords: Software_Engineering_quotes Programming_quotes Software_quotes Engineering_quotes Part_quotes Computer_Science_quotes Computing_quotes Science_quotes Difficulty_quotes Scientist_quotes

Software Engineering Definition

“(Software engineering is the) establishment and use of sound engineering principles to obtain economically software that is reliable and works on real machines efficiently.”
  • Source: [Bauer; 1972]. A paper entitled Software Engineering. Written by Friedrich Ludwig Bauer. Published 1972 in Information Processing 71: Proceedings of Ifip Congress 1971, volume 1. ISBN: 9780720420630.
Keywords: Software_Engineering_quotes Cost_quotes Reliability_quotes Efficiency_quotes Software_quotes Engineering_quotes Establish_quotes Use_quotes Sound_quotes Principle_quotes Obtain_quotes Economical_quotes Work_quotes Real_quotes Machine_quotes

Robert_N_Britcher

Programming and Engineering

“Some aspects of programming will remain forever beyond the grasp of classical engineering. Programming is too much like writing, too personal and private, too much under the spell of hyperbole, marketing, and self-aggrandizement.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 208.
Keywords: Programming_quotes Classical_quotes Engineering_quotes Software_Engineering_quotes Writing_quotes Privacy_quotes Hyperbole_quotes Marketing_quotes Aggrandizement_quotes Craft_quotes Aspect_quotes Remain_quotes Forever_quotes Beyond_quotes Grasp_quotes Understanding_quotes Personal_quotes Spell_quotes Self_quotes

Knowing Versus Doing

“We should not give up because there is no unified field theory of software engineering. The elements may not be easy to implement, but they are relatively simple, especially when compared with the study of proteins. ... The problem is not that we do not know enough. The problem is that we do not practice what we know.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 209.
Keywords: Persistence_quotes Unification_quotes Theory_quotes Software_Engineering_quotes Element_quotes Hard_quotes Simplicity_quotes Protein_quotes Problem_quotes Knowledge_quotes Action_quotes Practice_quotes Doing_quotes Software_quotes Engineering_quotes Easy_quotes Implement_quotes Relative_quotes Compare_quotes Study_quotes Practice_quotes

Fred Brooks

Brooks' Law

“Adding manpower to a late software project makes it later.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 2, page 25. Known as Brooks' Law.
Keywords: Project_quotes Project_Management_quotes Schedule_quotes Software_Engineering_quotes Software_Management_quotes Human_Resources_quotes Law_quotes Management_quotes Software_quotes Engineering_quotes Human_quotes Resource_quotes Make_quotes Late_quotes

Throw One Away

“Plan to throw one away; you will, anyhow.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 11, page 116.
Keywords: Project_quotes Project_Management_quotes Software_Engineering_quotes Software_Management_quotes Failure_quotes Management_quotes Software_quotes Engineering_quotes Plan_quotes Throw_quotes Away_quotes One_quotes

Tables versus Flowcharts

“Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowcharts; they'll be obvious.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 9, page 102.
Keywords: Software_Engineering_quotes Flowchart_quotes Data_quotes Data_Driven_quotes Programming_quotes Communication_quotes Confusion_quotes Obfuscation_quotes Software_quotes Engineering_quotes Conceal_quotes Table_quotes Continue_quotes Mystify_quotes Need_quotes Obvious_quotes

Rapid Prototyping

“Today the software engineering discipline is much more sophisticated. We recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 23.
Keywords: Software_Engineering_quotes Rapid_quotes Prototyping_quotes Tool_quotes Requirements_quotes Iterative_quotes Goal_quotes Design_quotes Today_quotes Software_quotes Engineering_quotes Discipline_quotes Sophisticated_quotes Recognize_quotes Essential_quotes Formulate_quotes Precise_quotes Process_quotes Set_quotes

Rational Model

“Perhaps the most devastating critique of the Rational Model, although perhaps the hardest to prove, is that most experienced designers just don’t work that way.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 30.
Keywords: Rational_quotes Model_quotes Software_Engineering_quotes Software_Lifecycle_quotes Proof_quotes Experience_quotes Design_quotes Devastate_quotes Critique_quotes Hard_quotes Designer_quotes Work_quotes Software_quotes Engineering_quotes Lifecycle_quotes

Waterfall Model

“The Waterfall Model is wrong and harmful, we must outgrow it.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 34.
Keywords: Waterfall_quotes Model_quotes Software_Engineering_quotes Software_Lifecycle_quotes Harm_quotes Growth_quotes Error_quotes Uselessness_quotes Software_quotes Engineering_quotes Lifecycle_quotes Wrong_quotes

Alexander d'Agapeyeff

Programming too much Art

“Programming is still too much of an artistic endeavour.”
Keywords: Programming_quotes Software_Engineering_quotes Art_quotes Endeavour_quotes

Edward_Emil_David

Explore_First

“Begin with skeletal coding: Rather than aiming at finished code, the first coding steps should be aimed at exploring.”
Keywords: Software_Engineering_quotes Programming_quotes Exploration_quotes Requirements_quotes Skeletal_quotes Coding_quotes Aim_quotes Finish_quotes

Competitive Rush

"Computing has one property, unique I think, that seriously aggravates the uncertainties associated with software efforts. In computing, the research, development, and production phases are often telescoped into one process. In the competitive rush to make available the latest techniques, such as on-line consoles served by time-shared computers, we strive to take great forward leaps across gulfs of unknown width and depth."
Keywords: Software_Engineering_quotes Computer_quotes Uncertainty_quotes Effort_quotes Research_quotes Development_quotes Production_quotes Telescope_quotes Process_quotes Competition_quotes Unknown_quotes Scope_quotes Requirements_quotes Property_quotes Unique_quotes Aggravate_quotes Software_quotes Engineering_quotes Phase_quotes Technique_quotes Console_quotes Timeshare_quotes Strive_quotes Forward_quotes Leap_quotes Gulf_quotes Width_quotes Depth_quotes

Software Engineer Training

"The problem of how the software engineers will get their practice is precisely the same as in other fields of engineering, and is insoluble. This is recognized in industry, where one makes sure that the young engineers coming in will get the proper kind of experience in time."
Keywords: Problem_quotes Software_quotes Software_Engineering_quotes Engineering_quotes Programmer_quotes Practice_quotes Training_quotes Insoluble_quotes Industry_quotes Young_quotes Experience_quotes Time_quotes Field_quotes Proper_quotes

Edsger_Wybe_Dijkstra

Effective Reasoning

“The required techniques of effective reasoning are pretty formal, but as long as programming is done by people that don't master them, the software crisis will remain with us and will be considered an incurable disease. And you know what incurable diseases do: they invite the quacks and charlatans in, who in this case take the form of Software Engineering gurus.”
Keywords: Technique_quotes Effectiveness_quotes Reason_quotes Formal_quotes Programming_quotes Skill_quotes Software_quotes Crisis_quotes Incurability_quotes Disease_quotes Quack_quotes Charlatan_quotes Software_Engineering_quotes Guru_quotes People_quotes Master_quotes Engineering_quotes

Software Crisis

“The turning point was the Conference on Software Engineering in Garmisch, October 1968, a conference that created a sensation as there occurred the first open admission of the software crisis.”
Keywords: Turning_quotes Change_quotes Conference_quotes Software_Engineering_quotes Software_quotes Crisis_quotes Engineering_quotes Sensation_quotes Occur_quotes Admission_quotes

Robert_M_Graham

Wright Brothers Construction

“We tend to go on for years, with tremendous investments to find that the system, which was not well understood to start with, does not work as anticipated. We build systems like the Wright brothers built airplanes — build the whole thing, push it off the cliff, let it crash, and start over again.”
Keywords: Software_Engineering_quotes System_quotes Investment_quotes Cost_quotes Understanding_quotes Requirements_quotes Anticipation_quotes Prediction_quotes Airplane_quotes Cliff_quotes Crash_quotes Repeatability_quotes Tend_quotes Year_quotes Work_quotes Build_quotes WrightBrothers_quotes

Patterson_Hume

University Software Experience

“What really worries me about software engineering is, do universities have to engage in large software projects in order to remain experts in the field of software engineering? Do they have to hire people who have had such experience with large projects, or do they have to have their professors go out and as consultants experience large software engineering projects? Then, when they come to exercise the students, do they have to have laboratories of some considerable consequence in software engineering exercises? Otherwise, who is to formulate principles of software engineering that can be used to train software engineers?”
Keywords: Worry_quotes Software_Engineering_quotes University_quotes Large_quotes Project_quotes Expert_quotes Experience_quotes Hire_quotes Consultant_quotes Professor_quotes Exercise_quotes Student_quotes Laboratory_quotes Formulation_quotes Training_quotes Engineering_quotes People_quotes

Capers_Jones

Quality Software

“High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership.”
  • Source: The Economics of Software Quality by Capers Jones and Oliver Bonsignour, 2011, chapter 7.
Keywords: Quality_quotes Software_quotes Software_Engineering_quotes Cost_quotes Fast_quotes Project_Management_quotes Expensive_quotes Cheap_quotes Maintain_quotes Development_quotes Total_quotes Ownership_quotes

Kenneth_W_Kolence

Software Not Physical

“We clearly do not now have an engineering capability comparable to those based on the physical sciences. Such a capability is what is implied by the term software engineering. But software is not a physical system, it is a description of what one describes how a given physical system (a computer of some sort) should act. Thus software is more akin to engineering drawings, either maintained on paper or within a computer. ... So probably it is incorrect to assume software engineering should be considered as a sibling in the family of the physical science based engineering disciplines.”
Keywords: Engineering_quotes Capability_quotes Compare_quotes Physical_quotes Science_quotes Software_Engineering_quotes Software_quotes System_quotes Computer_quotes Activity_quotes Drawing_quotes Paper_quotes Sibling_quotes Family_quotes Discipline_quotes Consider_quotes Maintain_quotes Incorrect_quotes

Software Engineer

“There are people who call themselves software engineers, and who build software systems that other people trust their lives to that software. So a great deal of progress has really been made since 1962 (when I first began considering myself as a software engineer) and in that respect toward what may be considered as a valid engineering capability. ... Using the term [Software Engineering] ... actually did, for the first time, provide programmers with a more professional description of what they were trying to do. In my opinion, that was a very good thing.”
Keywords: People_quotes Software_Engineering_quotes Programming_quotes Trust_quotes Life_quotes Software_quotes Progress_quotes Engineering_quotes Validity_quotes Capability_quotes Professional_quotes Build_quotes Term_quotes First_quotes Time_quotes Provide_quotes

Software Engineering Body of Knowledge

‘While software engineering may be based on good principles of design activities, it is not a physical science based engineering body of knowledge. So we have to build an engineering capability based on some other body of knowledge.”
Keywords: Software_Engineering_quotes Principle_quotes Design_quotes Activity_quotes Physical_quotes Science_quotes Engineering_quotes Body_quotes Knowledge_quotes Capability_quotes Software_quotes

Michael_Sean_Mahoney

Software Crisis and Software Engineering

“Let me say a bit more about the ‘software crisis’. It emerged in the late 1960s as an increasing number of large projects experienced large cost overruns, missed deadlines and failures to meet specifications. Some had to be canceled altogether. One response was calls for a discipline of ‘software engineering’”
  • Source: Michael S. Mahoney in a paper entitled The Histories of Computing(s). Published 2005 in Interdisciplinary Science Reviews, volume 30, number 2, pages 119–135. DOI: 10.1179/030801805X25927.
Keywords: Software_quotes Crisis_quotes Project_quotes Experience_quotes Cost_quotes Overrun_quotes Deadline_quotes Failure_quotes Specification_quotes Requirements_quotes Cancel_quotes Software_Engineering_quotes Engineering_quotes

Undefined Software Engineering

“If one could not define 'software engineering' at the time, neither could one point to its practice. It was not coined to characterize an ongoing activity but rather to express a desire for one.”
  • Source: Michael S. Mahoney in a paper entitled The Roots of Software Engineering. Published 1990 in CWI Quarterly, volume 3, number 4.
Keywords: Definition_quotes Software_quotes Software_Engineering_quotes Engineering_quotes Time_quotes Practice_quotes Coin_quotes Activity_quotes Desire_quotes

Malcolm_McIlroy

Top and Bottom

“Talking about where one starts is, I think, perhaps a slight lie. One starts in fact with the grand conception, including the top and the bottom.”
Keywords: Talking_quotes Start_quotes Thinking_quotes Lie_quotes Deception_quotes Grand_quotes Conception_quotes Top_quotes Bottom_quotes Software_Engineering_quotes

Programs and Bridges

“There is a difference between writing programs and designing bridges.”
Keywords: Differences_quotes Programming_quotes Design_quotes Bridge_quotes Software_Engineering_quotes Engineering_quotes Writing_quotes

David_E_Nye

Programmers Perfectionists

“A single error in a program thousands of lines long prevented it from running correctly, and computer programmers became known as a fanatically exact group of perfectionists, working in an arcane specialty. Sociologists studying the ‘man-machine' interface found that a programmer's personality often changed after prolonged exposure to the computer, becoming severely logical and machine-like.”
  • Source: A book. Written by David E. Nye. Entitled 'Narratives and Spaces'. Published in 1997 by Univerity of Exeter Press, Exeter, UK. Hardback ISBN 0-85989-555-6. Paperback ISBN 0-85989-556-4. Chapter 10, page 164.
Keywords: Single_quotes Error_quotes Program_quotes Thousand_quotes Line_quotes Long_quotes Prevent_quotes Run_quotes Correct_quotes Computer_quotes Programmer_quotes Fanatic_quotes Exact_quotes Group_quotes Perfectionist_quotes Work_quotes Arcane_quotes Specialty_quotes Sociologist_quotes Study_quotes Man_quotes Machine_quotes Interface_quotes Find_quotes Personality_quotes Change_quotes Prolong_quotes Exposure_quotes Severe_quotes Logical_quotes Software_quotes Engineering_quotes Software_Engineering_quotes

Alan_Perlis

Fit and Try

“Fundamentally, the procedure you mention, which is ‘fit-and-try’, will work very well with three or four people. If you have a hundred people the ‘fit-and-try’ process diverges because of lack of control.”
Keywords: Fundamental_quotes Mention_quotes Process_quotes Procedure_quotes Fit_quotes Try_quotes Work_quotes People_quotes Software_quotes Software_Engineering_quotes Development_quotes

Software Engineering Competence

“It is a fact that there are software engineers around today who are quite competent. There are systems in many places which are quite stable and which provide magnificent service. It is also the case that there are large numbers of efforts, containing large numbers of programs and programmers, which have no software engineers on them, that is that people function as though they did not know how to build software.”
  • Note: Un-indexed continuation of quote: “I have a number of questions: 1. Is it possible to have software engineers in the numbers in which we need them, without formal software engineering education? 2. Is software engineering the same as Computer Science? 3. Is software engineering best provided by baccalaureate programs in universities? Or by adult education courses? Or by two year courses following the standard grade school education? 4. Do the people educated in these programs have a growing and future role in our society? 5. Will they be useful enough in a firm or government or university, and is their value such that they can distribute their talents in other activities, or must they always remain programmers? 6. What curriculum do we have in mind for software engineers, regardless of what level we choose to educate them? 7. Is software engineering really different from what we now call systems engineering?”
Keywords: Fact_quotes Software_Engineering_quotes Competence_quotes System_quotes Place_quotes Stable_quotes Provide_quotes Magnificent_quotes Service_quotes Effort_quotes Large_quotesProgram_quotes Programmer_quotes People_quotes Knowledge_quotes Build_quotes Software_quotes Development_quotes Engineering_quotes

First Software Engineering Conference

“This is the first conference ever held on software engineering and it behooves us to take this conference quite seriously since it will likely set the tone of future work in this field”
Keywords: First_quotes Conference_quotes Software_Engineering_quotes Serious_quotes Tone_quotes Future_quotes Work_quotes Field_quotes Software_quotes Engineering_quotes

Training

“Our problems arise from demands, appetites, and our exuberant optimism. They are magnified by the unevenly trained personnel with which we work. In our deliberations we will not, I believe, be able to avoid the education problem — software engineering does not exist without software engineers.”
Keywords: Problem_quotes Arise_quotes Demand_quotes Appetite_quotes Exuberant_quotes Magnify_quotes Uneven_quotes Training_quotes Personnel_quotes Work_quotes Deliberation_quotes Belief_quotes Avoidance_quotes Education_quotes Software_Engineering_quotes Optimism_quotes Engineering_quotes Engineer_quotes Software_quotes

Franz_Selig

Specification Feedback

“External specifications at any level describe the software product in terms of the items controlled by and available to the user. The internal design describes the software product in terms of the program structures which realize the external specifications. It has to be understood that feedback between the design of the external and internal specifications is an essential part of a realistic and effective implementation process. Furthermore, this interaction must begin at the earliest stage of establishing the objectives, and continue until completion of the product.”
Keywords: Software_Engineering_quotes Specification_quotes Design_quotes Feedback_quotes Implementation_quotes Project_quotes Goal_quotes Objectives_quotes Software_quotes Engineering_quotes Level_quotes Product_quotes Term_quotes Item_quotes Control_quotes Available_quotes Internal_quotes Realize_quotes External_quotes Understand_quotes Essential_quotes Part_quotes Realistic_quotes Effective_quotes Process_quotes Interaction_quotes Stage_quotes Establish_quotes Completion_quotes
Retrieved from "https://motleybytes.com/wiki/index.php?title=Software_Engineering_quotes&oldid=29555"