Home

This is the draft plan for developing a revised version of the current UrbanSim pro forma and developer modules.

Running List of Questions

• How to organize project vis-a-vis full urbansim and urbansim_defaults repositories
• Need to discuss:
  • Releases and versioning scheme
  • Proper setup for an open source python package

Features

Paul's writeup of desired features in the Discourse forum is a good starting place. See the Features page for more discussion.

Key Clients

• We have a consulting contract with MAG (Phoenix) to complete this work. See requirements
• SEMCOG (Detroit) is also interested in improvements to this functionality. See requirements

Team

• Conor (client support, code review, possible coding)
• Martin (code review, possible coding)

Initial notes

• It will be much easier to refactor and reorganize the existing code than to rewrite it. Thus, early steps will be to see whether planned features, particularly multiperiod evaluation and development, are compatible with the current functionality, now or after refactoring.
• Need to decide what is/is not in the scope of this initial project (what we're releasing by the end of April). 3D visualization at the site level, for instance, is probably not in this scope. (to do Wednesday)
• No relationship with Fletcher/PyForma on this

Roadmap

Week 1 (beginning January 30)

Activities

1. Contact interested clients (MAG and SEMCOG) and ask for desired features, implementation, and test data (done)
2. Get or create test data for new features (e.g. a multi-period development) (probably skip this step)
3. Code/Data Assessment (Tuesday)
   • Input data - do we need to get back into thinking about RSMeans, cost data. Currently in SqftProFormaConfig object.
   • Pro Forma module
   • Developer module
   • urbansim_default model(s)
4. Review features in detail (Wednesday)
5. Complete high-level project plan (Wednesday)
6. Get signoff from team, Paul (Thursday)
7. Kickoff meeting with team to discuss the plan (Friday)
   • Should come with a detailed, structured plan in response to features
   • Conor and I should have processed and discussed MAG wishlist and data by then (and SEMCOG if possible)

Features

• No new features

Deliverables

• Decision on extent of refactoring vs. rewriting
• High-level architectural decisions
• Prioritization of features
• Revised roadmap

Week 2 (beginning February 6)

Activities

• Set up UDST repo, versioning/release scheme
• General refactoring
• Review test coverage and add tests as needed
• Ensure backward compatibility

Features

• No new features

Deliverables

• No deliverables

Week 3 (beginning February 13)

Paul Sohn on vacation

Week 4 (beginning February 20)

Paul Sohn on vacation

Week 5 (beginning February 27)

Activities

• General refactoring

Features

• No new features

Deliverables

• Release: refactored modules with no added features

Week 6 (beginning March 6)

Features

• Multiperiod development
• Multiperiod evaluation

Week 7 (beginning March 13)

Features

• Multiperiod development
• Multiperiod evaluation

Deliverables

• Release: Multiperiod development and evaluation

Week 8 (beginning March 20)

Features

• Improved search over feasible project configurations
• Uncertainty analysis

Week 9 (beginning March 27)

Features

• Market analysis
• Trade-off analysis

Deliverables

• Release

Week 10 (beginning April 3)

Features

• Other features! (To discuss)

Week 11 (beginning April 10)

Week 12 (beginning April 17)

Week 13 (beginning April 24)

Deliverables

• Final release