1 / 4

Developing Urban Simulation: Effective Practices for Continuous Improvement

This lecture discusses innovative practices in the development of Urban Simulation (Urban Sim), highlighting the importance of version control even for solo projects. Key concepts include the removal of redundant code to enhance design, maintaining a master copy for continuous development, and quick release cycles. The lecture also examines the implications of rapid requirement changes, debugging processes, and priorities in bug fixing. Emphasizing a culture of high-quality code through testing and integration, it explores how effective feedback loops contribute to the overall success of Urban Sim projects.

louvain
Télécharger la présentation

Developing Urban Simulation: Effective Practices for Continuous Improvement

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. CSE 403Lecture 13 Discussion of Urban Sim Dev Process

  2. Urban Sim • Use version control, even for solo projects • Interesting idea: • Removing all redundant code, in itself, leads to good design • Informal work atmosphere • Pointy hats, traffic lights, smiley faces • Mileage may vary

  3. Urban Sim (cont.) • Incremental build • Master copy always up to date and working • Continuous development • Very quick release cycle • Implications for development and test process • Rapid requirements change? • Where was test?

  4. Code / debug cycle • Lead codes quickly, junior programmers fix bugs • Recognized as a stupid approach • Feedback cycle the wrong direction • The worse your code, the more you write • Devs aim for high quality through testing their own code • Major testing phase after integration • Continuous bug fixing • Clear all Pri 1 bugs as detected • Depends upon early integration

More Related