In March 2002 this photograph of Bahill was installed
Terry Bahill has retired from the University of Arizona.
This list of Bahill's major publications summarizes the research contributions of his career.
Here is a short biographical sketch.
This link will take you to the slides and papers that were presented in his Spring 2012 course Engineering the Sport of Baseball
Systems Engineering is an interdisciplinary process that ensures that the customer's needs are satisfied throughout a system's entire life cycle. This process is comprised of the seven following tasks: Stating the problem, Investigating alternatives, Modeling the system, Integrating the system, Launching the system, Assessing performance, and Re-evaluation. This process can be summarized with the acronym SIMILAR (Bahill and Gissing, 1998). My What Is Systems Engineering? directory has a paper and a slide show describing the systems engineering process.
Here are abstracts for a series of seminars and short courses that Bahill has given many times world wide.
My Systems Engineering Process is use case based, which means that we start with the use cases, using the use cases we discover the requirements, then we use the use cases to create the test plan.
The following posters describe various aspects of the systems engineering process. You are welcome to use them.
The phrase "To a man with a hammer everything looks like a nail," is attributed to Mark Twain. We teach students how to use a tool. Then they use that tool for everything. We should teach them to study each problem and then select the best tool for that problem.
The spiral Model for Systems Engineering. The system engineering process starts in the middle with the customers' needs, often described with use cases. Next, we discover requirements. Then, as time progresses, the process spirals outward as we design, build, simulate, verify and validate models. Finally, there is a review and we start all over again, except everything is bigger. This process repeats many times with models, prototypes, pre-production and manufacturing: each of these phases has multiple iterations. Then we have operations, maintenance, retirement and finally replacement.
Shadows. The size of each icon indicates the cost of the activity. Discovering requirements costs much less than manufacturing. The size of each shadow indicates the influence of the activity on the design. Discovering requirements has a big influence on the system: whereas, by the time you get to manufacturing, you can change little.
Functional Decomposition. What do we need to fly? For centuries, humans have been unsuccessful in their attempts to fly, because they used physical decomposition (brain, eyes, legs and wings). The Wright Brothers used functional decomposition and focused on three functions: control, horizontal thrust and vertical lift. They flew successfully.
Systems Engineering is a Fractal Process. The systems engineering process is applied (at different times and in different places) at levels of different detail. It is applied to the system, the subsystems, the components, etc. Similarly, for the fractal pattern above, the same algorithm was applied at the large structural level, at the medium-scale level and at the fine-detail level, etc. This fractal analogy was created by Bill Nickel at Sandia Laboratories in the summer of 1995.
Proper Wine Tasting Technique. First see the wine: behold its color, clarity and legs. Then smell the wine: nose the fruit. Finally taste the wine and savor the finish: but don't be a dog and slurp it.
Bahill has done research on the Science of Baseball.
If you are interested, go to this
Most of these papers were co-authored with
Dave and I presented a paper at the baseball research conference
(SABR 36) in Seattle, June 29, 2006.
Slides of our presentation
are right here. (The file is 6 Mbytes.)
I highly recommend that you read Dave Baldwin's autobiography Snake Jazz. It has some baseball stuff, and it is highly entertaining. His philosophy on life is that, if you lose a game, don't blame society. Just go back and work harder.
Here are some carefully worded definitions about systems and states. I had lots of help in writing this.
I do not think that slides are a good handout to accompany a presentation, but so many people have asked me for copies of my slides, that I have decided to make them available in my slides directory. I have also put a program for computing Wymorian Scoring Functions in this directory. Feel free to download any or all of these.
Pinewood contains the complete documentation for the design of a Pinewood Derby. In particular it has several examples of tradeoff studies. Here is the the Pinewood Derby chapter from Chapman, Bahill and Wymore.
Wayne Wymore was the theoretician for our Systems Engineering community. I have his photograph, his autobiography, two of his theoretical papers on Systems Engineering, and a lecture he gave in my class in this directory dedicated to Wymore. Wayne died February 24, 2011.
For the lighter side of lexicology, look at my laugh directory.
Here is a review of the book The Ghost of the Executed Engineer (3 Kbytes).
I am often asked about systems engineering tools. For now I will just refer you to the INCOSE tools site.
Some good examples of the Wymorian documentation are in this directory, which was created for SIE-454/554 students.
This site belongs to Terry Bahill: (520) 742-5469. The last major change was made on March 24, 2012.