Posts tagged: methodology

Jul 21 2009

Lessons in Software Development From the Apollo Moon Missions.

apollo11_launch
Monday was the 40th anniversary of the Apollo 11 lunar landing. The story of the Apollo program is an historic and inspirational one, but it’s also relevant to software development.

To understand the significance of the Apollo program from an engineering standpoint, we must begin at the beginning…
Gus Grissom, Ed White and Roger B. Chaffee were killed on the launch pad when the Apollo 1 capsule burst into flames just prior to the launch test. What happened? Well, according to Wikipedia (I know, far from an unimpeachable source, but bear with me here):

“Although the ignition source of the fire was never conclusively identified, the astronauts’ deaths were attributed to a wide range of lethal design hazards in the early Apollo command module. Among these were the use of a high-pressure 100 percent-oxygen atmosphere for the test, wiring and plumbing flaws, flammable materials in the cockpit (such as Velcro), an inward-opening hatch that would not open in this kind of an emergency and the flight suits worn by the astronauts.”

In short, no one knows for sure what specifically caused the fire, but everyone agrees that some fundamental errors led to the conditions (whatever they ultimately were).

what really went wrong was at the planning and design stage. NASA was in such a rush to make up lost time in the space race with the USSR, that they got cocky after early successes, cut corners and went full bore toward a fully manned, Apollo capsule before they were really ready.

The precursor missions to Apollo were the Mercury and Gemini projects. These projects had highly specific mission statements and each was directed toward a discrete piece of the overall lunar landing mission. Project Mercury was directed toward getting a man into space, and back again. The goal of project Gemini was to perform extra-vehicular activity (pre-cursor to space walk), and docking maneuvers.

NASA began the mission to the moon with an iterative approach, but switch to a more waterfall like approach where they tried to construct a whole new capsule module from scratch, with the intent of landing on the moon and returning. They used the knowledge gained from the earlier Mercury and Gemini projects, but constructed new - and untested - equipment for Apollo.

The parallel to software development is using an iterative approach to develop phase I of a project, only to throw it away and start over on phase II. The whole purpose of the iterative approach is to focus on small, achievable parts of a greater whole to maintain momentum but also to limit what must be tested and hence limit (theoretically) the universe of possible bugs.

I think the 2 most important software development lessons we can learn from the Mercury, Gemini and Apollo missions are:

  1. To be successful, have clear and concise mission objectives (goals).
  2. Start small, and build on each success.

This is what made the Gemini and Mercury missions so successful, and ultimately made Apollo 11 possible and it will drastically improve the odds of your next software project being a success as well.

Blog Traffic Exchange Related Posts Blog Traffic Exchange Related Websites
  • Rookie and Beginner Woodwork Projects Just like with many other types of jobs, when it comes to woodwork projects, planning is of the utmost level of importance. Cutting wood and working with wood is always going to demand that you utilize careful planning and a step by step approach toward reaching the ultimate goal for......
  • cpa marketing illinois [mage lang="" source="flickr"]cpa marketing illinois[/mage] A Short History of Systems Development"If they do not have an appreciation of whence we came, I doubt they will have an appreciation of where we should be going." - Bryce's Law INTRODUCTION I always find it amusing when I tell a young person in......
  • Popular Personal Productivity Software Cartoon August 2006 I virtually took a small group to a tropical island in Thailand. I was committing myself to a 30 day Time Management Training month. 33 personal productivity software programs were put through their paces. And this cartoon by the living legend Mark Joyner sums up what I found......
  • Forex Courses In Chennai Role of human resources consultants in India with regard to the IT sector COVER 1. Sachin Kumar Name:. N. Naravane 2. Occupation: Sr.Lecturer-MBA 3. Place: Koppal, Karnataka state and India 4. E-mail : Sachin_naravani@yahoo.co.in The role of consultants HR job with reference IT industry in India ABSTRACT Consultancy in India......
  • The Correct Project: Start, Developing, End. Main principles of making short projects. As an example of short projects on working out of software it is possible to result site working out, small information systems for own needs, the first versions of programs for external consumers, working out of shareware and so on. Such short project usually......
Jul 14 2009

The 3 Most Important Questions You Should Ask About Each Bug You Find.

I stumbled upon (quite literally) an article by Tom Van Vleck titled Three Questions About Each Bug You Find today, and thought I would share it:

“The key idea behind these questions is that every bug is a symptom of an underlying process. You have to treat the symptoms, but if all you do is treat symptoms, you’ll continue to see more symptoms forever. You need to find out what process produced the bug and change the process. The underlying process that caused your bug is probably non-random and can be controlled, once you identify what happened and what caused it to happen.”

Tom uses these questions to get to the heart of the matter and weed out the root cause of the bug.

1. Is this mistake somewhere else also?

You want to know if this bug was unique, or due to a problem in a pattern of approach to the specific problem. If it’s unique, you can move on to the next question, but if it’s systemic, you’ll need to address your approach to the development problem the code was intended to solve and devise a new pattern or correct the one in place.

2. What next bug is hidden behind this one?

Often times a bug will either halt the execution of code, or cause the lines after the bug to be bypassed. once you fix the bug, those other lines of code will begin to execute. Be sure to check those for any bugs. Also, consider whether your fix to this bug could cause any new bugs to be introduced.

3. What should I do to prevent bugs like this?

Learn from this mistake. Could the problem be avoided by adding a new test condition to your NUnit test(s)? Should you implement a change to your pattern to check for null reference or out of bounds exceptions sooner? Bugs happen, but if you can use them as teachable moments and learn from them, then they will at least provide some value and make you less likely to run into the same bug in the future.

It’s not always an easy process, mostly because it requires a sort of detached introspection and willingness to be critical and objective when looking at your work. These character traits are not always in high supply, and we humans can often get in the way, but if you can master these techniques you will go far young padawan.

Blog Traffic Exchange Related Posts Blog Traffic Exchange Related Websites
  • Stoic Fate There is a missing element that modern Stoics don’t usually embrace. The Hegemon, or logos, is still alive and aware in the world. The world is itself possessed of intelligence in the original Stoic view.  They saw life as a constant dialogue, a "debate" if you will, with that intelligence.......
  • Pregnancy Fetal Development at Week 1 Although it may seem strange to think about, the journey of your pregnancy actually begins before the baby has actually been conceived. The very first week of your pregnancy does not begin with conception, or with the growth of the fetus in your body, but rather it begins with the......
  • Language Development and your Four Year Old The preschool age is a wonderful age during childhood and I really enjoyed teaching children in this age group.  They are interested in learning about any topic from bugs to space and have countless questions for you to answer.  Developmentally, they should be at a level to really express their......
  • Home Network Security [/caption] Home Computer security 1. What is computer security? Computer security is the process of preventing and detecting unauthorized use of your computer. Prevention measures help you to stop unauthorized users (also known as "intruders") from accessing any part of your computer system. Detection helps you to determine whether or......
  • Baby Development Milestones at Week 5 After weeks' worth of rapid cell development, one of the biggest baby development milestones during this week is that your baby is taking on a much more distinct form. During your fifth week worth of pregnancy, here are some of the things that are happening inside of you: Your baby's......