The Project Scenario

5c1105, Spring 2004

 

Martin Lesser, mlesser@mech.kth.se

 

Below is a scenario for the viewpoint taken in the course project. Other course information can be found on the course website at: http://www2.mech.kth.se/~mlesser/5C1105%20Website.htm

The course text is: From Calculus to Chaos- An Introduction to Dynamics by David Acheson, Oxford University Press. It is available at the KTH student bookstore.

 

Esoteric Publishing Inc.  (EPIC) has decided that the mechanics text "From Calculus to Chaos" has potential for sales in a nonacademic popular science market. After due consideration and market testing it is also realized that the book will have more chance of success as a software package. As EPIC is not experienced in producing software it has put out offers to software developers to produce the needed software. They would like the software to satisfy the following criteria:

 

  1. It should have an attractive and intuitive graphical user interface.
  2. It should be usable on all major platforms.
  3. While the software should be self-contained it is also desirable that the user is motivated to purchase the book version.
  4. The user should be able to play with the various mechanical models such as the two and three body problem or the upside down pendulum in a way that will be attractive and educational.
  5. If possible the user should be able to extend the scope of the problems treated so that he or she can make their own "discoveries".

 

As this is to be a large and expensive project EPIC is asking those bidding for a contract to submit a pilot example with limited scope along with a description of what this implies for the final version of the software.  The pilot software is to cover one of a selected number of possible topics. That is the potential bidder is asked to choose some aspect of one of the following topics:

  1. The two and three body problem and the solar system.
  2. The strange behavior of the inverted pendulum chain.
  3. Nonlinear Oscillators and Chaos.
  4. Variational Principles and the equations of mechanics.

 

EPIC is well aware that even excellent software developers may be weak in the domain knowledge required. Therefore they have also hired the services of the Mission Impossible Mechanics Education Service (MIMES) to assist in helping the prospective bidders acquire the needed domain specific information. This is to be offered in the form of 12 lectures and 5 tutorial sessions. As EPIC wants to see how well this part of their effort works they are asking the participants to hand in a set of completed hand written problems at the end of the lectures. This information will also play a role in deciding who wins the contract.

 

As part of the lectures EPIC has also hired a well know software developer and teacher to carry out several public interviews with company representatives. The purpose of the interviews is to attempt to extract what EPIC really wants verse what they think they want and to ground the project to realistic goals. Attendees will be able to continue this process in the tutorial sessions.

 

About 4 weeks after the start of the lectures the attendees wishing to submit pilot projects are asked to submit a preliminary plan for their projects. This should include the following:

 

  1. The goal of the pilot project.
    1. Which topic is being covered.
    2. What will the software be able to do in general terms.
  2. The composition of the project team, i.e. the names and assignments of each team member.
    1. The area of the team members main contribution:

                                                                  i.      Graphics

                                                                    ii.      Algorithm implementation and development

                                                                      iii.      Project Management

                                                                     iv.      Script Writing

  1. Sketches of proposed graphical user interface.
  2. Protocol of how the software will be used.
  3. How the pilot project fits into the goals of the final product.

 

The final bid is to be composed of a written version as well as a 15-minute oral presentation. The written version should have the following:

 

  1. A double-spaced introduction stating the goals and what was actually achieved. This should be no less than 200 and no more than 500 words. Illustrations may also be used and should be clearly labeled.
  2. A clear example of the use of the software including a detailed example run. This should be no longer than five pages including figures. Some indication of the theory behind the mechanics should also be given here.
  3. A short statement of who did what in the development process.
  4. A short preliminary manual for the software.
  5. The actual code either in an appendix or sent via email to the appropriate tutorial teacher.

 

 

The oral presentation should take less than fifteen minutes and concentrate on point 2 of the report above, i.e. the run through of a clear example with explanation. There will be two or three minutes for questions.

 

 

In the evaluation of the bids one point will be given to the domain knowledge indicated by the written assignment, one point to the project plan and two points to the presentation and final report.

 

The copyrights to all projects belong to the software team and the results will only be used by EPIC with their permission!