50 likes | 62 Views
Guidelines for software engineering project evaluation, presenting results, setting goals, and individual contributions. Evaluation factors, team collaboration, and future milestones. Begin preparations now!
E N D
CSE403 Software EngineeringAutumn 2000Benchmark day Gary Kimura Lecture #23 November 17, 2000
Today • Heap libraries due today for benchmarking • What’s left to do on the projects
Repeat of what’s needed on Wednesday • Each group will present in class the results of running their test and benchmark suite against all the other heaps. • What ran • What didn’t run • Performance in terms of size and time • You should use a table to consolidate all this information. • Put in your public release directories a copy of those programs that’s didn’t run.
The project for the next three weeks • Each group should meet and discuss their goals for the next three weeks “You’ve just released a beta version, and haven’t won that trip to Disneyland. The competition is on the same schedule as you are.” • Need a set of realistic goals • Fixing bugs • Performance tuning • Major redesign? • More benchmarks that make you look good but not your competition? • Need goals for all team members • Don’t forget the schedule
Individual requirements before I can give you a grade • After the group presentations during finals weeks each student must submit an evaluation of the project to the instructors. • The evaluation has six parts for you to fill out. • What went right with the project? Why? • What went wrong with the project, or could have been done better? What specifically would have made it better? • What was your specific contribution to the project? What were you signed up to do and did you accomplish it? • What did you learn from the project? • Who was the star in your group? Why? • Any other information you wish to tell the instructors. • I advise everyone to start working on this now.