The document discusses structuring an application project including goals, components, design decisions, architecture choices, guiding principles, tools used, and lessons learned. The project aimed to augment a tax assessment system with GIS tools, provide workflow management, and minimize data entry. Key aspects included centralizing business logic, using a model-view-presenter pattern, a plug-in architecture, and pushing GIS code to a framework. The project emphasized separation of concerns, reuse, and avoiding repetition through automation and refactoring. Tools like MSBuild, SQL, and Windows Installer XML were also discussed. Mistakes around unnecessary complexity, testing, and communication were noted.

1. Structuring an Application Some Thoughts

2. Topics VENDOR project goals Quick tour System architecture choices Mistakes

3. Project Goals Augment commercial tax assessment system with GIS tools Provide workflow management tools for clerks, appraisers, and GIS editors Minimize data entry and re-entry by plugging in 3rd party data sources Be stable enough for commercial deployment to multiple tax districts

4. Delivered Components

5. Design Decisions Centralize business logic in model classes Model View Presenter for GUI applications Plug-in architecture for 3rd party data sources Push GIS code to framework wherever possible Mostly because of unfamiliarity of team

6. System Architecture Choices Separation Web stuff belongs in web projects GIS stuff belongs in GIS projects Etc. Reuse The model is what ties things together so attempt to centralize and reuse

7. Guiding Principle NEVER REPEAT YOURSELF! Handle GIS archiving/versioning in one place only Rule set for generating XML documents in one place only If we do something twice, automate and refactor

8. The Softer Side Mandatory phone meetings twice a week for 6 months Knowing who the client is: “product owner” vs. who can sign the acceptance Post deployment: client interactions via issue tracking web site

9. Tools I’m forgetful How to do something in SQL How to write that thingy in C# Which users to add to what group Which things are different on my PC vs. clients Tooling and automation is one way to avoid pitfalls

10. MSBuild Biggest discovery of 2008 for my productivity Makes even simple things easier in the short run with multiple developers Learned to isolate what is different on my machine than other machines Team members, client machine

11. MSBuild Really cool GUI  Let’s look at an example

12. WIXWindows Installer XML Open sourced tool from Microsoft to create Microsoft Installers (MSI) Scriptable and can do anything, with a learning curve Has nice extensions for AD, IIS, etc. Used to create documentation only on this project. See more use in future

13. WIXWindows Installer XML

14. WIXWindows Installer XML Example – Building documentation

15. Goofs and Gaffs When things went horribly wrong

16. Mistakes Being strict with structure led to unnecessary complexity a.k.a. I learned something in a peer review Even just with plethora of projects Staying on top of testing At some point I just let them slide for older code while adding more for new stuff

17. Suggestion Strive for “good enough” not perfection If it works as expected, it’s perfect to the client Perfection is in the eye of the beholder Does not mean you should not try to do a good job Resist the temptation to “make a quick improvement” – DONE == DONE!

18. Mistakes Not being rigorous with understanding the goal before starting work Very complex system, tons of business rules Became more successful through time because we began to do this

19. Suggestion Use descriptive text and pictures to verify your assumptions with the client

20. Mistakes Not communicating enough Make a DB schema change which is not communicated Update a config setting which is not communicated Change method signature on web service which is not communicated

21. Suggestion You absolutely cannot communicate too much If you need time to get things done close your door, “Do Not Disturb” on IM, and block off calendar Otherwise…5 minute conversation now could save 1 hour later today.

22. What is your experience? How have you done it?