1 / 20

Final Presentation

Final Presentation. Outline. Summary of the project work Experiences gained Requirements and Design Regarding SCORE Demonstration Questions?. Workload in hours. Total workload (w2): 611h. Project activities. Project Gantt Chart. The development process. List of Project Milestones.

Download Presentation

Final Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Final Presentation

  2. Outline • Summary of the project work • Experiences gained • Requirements and Design • Regarding SCORE • Demonstration • Questions?

  3. Workload in hours Total workload(w2): 611h

  4. Project activities

  5. Project Gantt Chart

  6. The development process

  7. List of Project Milestones

  8. Application requirements

  9. Planning issues • Requirements definition took a little more time than planned • Implementation, integration and testing should have been done in parallel • Creating a good SCORE report took a lot more time than planned

  10. Division of work

  11. Communication • Weekly Skype meeting • Status update and setting responsibilities • Once per week • Discussions on Google Groups • General questions towards the entire group • About 25 messages per week • Personal communication

  12. Achievements • Application: • All requirements implemented • except for one low-priority requirement • Not thoroughly tested • Documentation: • SCORE documentation reviewed three times and finished • DSD documentation not yet finished

  13. General experiences • Communication was the right amount • Don’t be afraid to change the initial planning and/or the initial subteams • Check the planning more often • Next time: one large checklist

  14. Fundamental requirements

  15. Requirements cont. • Non-functional requirements • None • Difficult • Track reducing algorithm • Strict requirements • Load and save, track reducing algorithm • Other requirements • Simple GUI

  16. Program decomposition Model-View-Controller Structure of the program

  17. SCORE • Contact with customer • Customer view on requirements was available from project start • Discussing requirements was no problem • Customer responded quick and to-the-point on status reports sent by e-mail

  18. SCORE • SCORE Final Report • Not just combining all DSD documents • About 5 extra topics • Including implementation, verification and validation • Four authors for one week • Three reviews

  19. Demonstration

  20. Questions?

More Related