EEL5881 Software Engineering I | Fall 2000 | Informal Science Education 2
Project Name: Informal Science Education 2
Team Web site: Project Web Page
Web Pages for Other Team Members:
Contents of this Document
Individual Weekly Time and Activity Log:
September 21, 2000 (1:00 pm - 2:00 pm): Web Page Setup time
September 22, 2000 (8:00 am- 8:50 am): Meeting with client, discussed possible project topics, discussed Cellular Automata, discussed background of current project.
September 27, 2000 (3:00 pm - 4:00 pm): Meeting with client, project ideas discussed. Client wants a general purpose cellular automata simulator. Product should be able to take as input transition rules and begining state and perform a simulation. Product should have a graphical user interface as an easy way to setup the simulation.
October 2, 2000 (12:00 pm - 1:00 pm): Began working on SRS template.
October 6, 2000 (11:00 pm - 3:00 pm): Began the framework of the project. Involved learning how to handle events in Java 2 because we are going to use the advanced windowing features of Swing.
October 12, 2000 (1:00 pm - 3:00 pm): Began working on Project Management Plan
October 19, 2000 (1:00 pm - 3:30 pm): Worked on SRS template.
October 29, 2000 (12:00 pm - 2:00 pm): Worked on coding the project.
November 1, 2000 (10:30 pm – 11:30 pm): Began work on the project management report.
November 6, 2000 (12:00 pm – 2:30 pm): Completed the project management report.
November 12, 2000 (7:30 am – 10:00 am): Wrote the class that will load and save the transition states, and the initial settings.
November 13, 2000 (10:30 am – 11:30 am): Helped Mike with test plan. Developed tests to run on the code that I have written.
November 18, 2000 (11:00 am – 12:30 pm): Began trying to integrate Mike’s code into my existing code.
November 19, 2000 (6:00 pm – 9:00 pm): Continued working on integrating Mike’s code with my code.
November 20, 2000 (7:00 pm – 8:30 pm): Coding
November 21, 2000 (11:00 pm – 2:30 pm): Coding
November 22, 2000 (7:30 pm – 9:30 pm): Coding
November 22, 2000 (11:00 pm – 12:00 am): Coding
November 23, 2000 (10:00 am – 1:00 pm): Coding
November 24, 2000 (5:00 pm – 7:00 pm): Coding
November 25, 2000 (1:00 pm – 3:00 pm): Coding
November 27, 2000 (10:00 pm – 3:30 am): Mike and I finished the coding portion of our program, and are now moving into the testing phase. We also completed our final presentation.
December 5, 2000 (3:00 pm – 9:00 pm): Completed the testing of the final product. All known have been removed. We are know preparing for our final presentation to our client.
December 6, 2000 (10:00 am – 2:00 pm): Completed the test results template and the project legacy.
December 11, 2000 (10:00 am – 11:30 am): Updated this page.
Weekly statements of individual progress and status:
- Week#1: Setup for WebPages is complete. I had to learn how to build tables in html make the formatting of the document look good.
- Week#2: The project is progressing well, I am learning many new things about how a simulation works and how cellular automata relates.
- Week#3: Working on the SRS template is going to take a lot of time, decided to get started early. Also learned a little bit about event handling in Java 2.
- Week#4: This week I have tests in all of my other classes, I probably will not have much time this week to spend on the project.
- Week#5: SRS template is very time consuming, Mike and I are planning on setting up a meeting on a weekend to begin coding the product.
- Week#6: The coding of the project is going well. I am learning a lot of new things about how a windowing system works.
- Week#7: We have completed our first project management report. The overall status of the project is going well. Although, I believe that I need to start concentrating more on the code to be written. In class, I heard someone mention class serialization, and I discovered that you can save classes to files, much the same way you would write a variable to a file.
- Week#8: I learned about class serialization, how to save classes to files in Java. It is very easy, and I should be able to write two simple classes to save and load the files that our program will use.
- Week#9: The project is progressing well. We are currently developing test cases for our final product. We have discovered that there are many different things that we need to include in the product to make it robust.
- Week#10: I am making progress in the integration of Mike’s code into mine. Until this point my part of the project has been stalled, waiting on the code that Mike has produced. Now that we have a working model of exactly how the transitions will work, I can begin incorporating it into my existing code.
- Week#11: The project is now completed, we are in the process of finishing up all of our final deliverables to be turned in.
- Week#12: Finished all final deliverables.
Log of individual technical or management issues and their resolution:
We have had some difficulty setting up meetings with our client. We emailed to suggest more times. It seems that our client's schedule is opposite of ours.
Began learning more Java that will be required for this project. Started learning event handlers in Java 2.
I am currently trying to integrate the code that Mike has written with the code that I have written. I am finding it a little difficult because I have never tried to use code that another person has written before.
Notes, lessons learned, etc.
Lesson learned: Not everyone replies to email, if no response is received email again or call to setup appointment.
Integrating another programmer’s code can be very difficult. It helps to have a detailed description of each class.
Template created by G. Walton (GWalton@mail.ucf.edu) on August 15, 2000
This page last modified by Jeffrey Miller (firstname.lastname@example.org) December 11, 2000