Why
I want to write a journal where all the decisions, problem evaluation and errors are a part of the story. So instead of focusing on the end result, this code story will focus on the journey. Actually there might never be a end result or the end result could/will change during the journey.
How
Instead of inventing a problem domain, I choose to make a photo gallery. Wife Lyhr and you(the reader) will act as customers, and your feedback decide where the journey goes.
What
Version 1.0
| Goals | Requirements |
| Privacy | |
| Authentication | |
| Authorization | |
| Users | |
| Groups | |
| Roles | |
| Content discoverability | |
| Albums | |
| Labels | |
| Metadata | |
| Searchable | |
| Easy human direct access | |
| Community feedback | |
| Comments | |
| Rating | |
| Favorites |
Goals should be fairly static, and all requirements should fit into a goal. Every code story episode will break down a requirement into specifications, the specification might never be implemented or change any number of times.
Technical Restrictions
- The project is developed in .NET, and the code is written in C#.
- A webserver running ASP.NET MVC.NET is the main interface for the user, and the webserver owns all data. No other application can have direct access to any data.
- Photos can be placed in a database or in a folder.
- Must support multiple databases (MSSQL and MySQL as a minimum).
Project Name
Every project should have a name, and I am usually very bad at picking them. Since its based on the .NET framework, and one of the top domains is .net, I choose the name phogal.net (short for "Photo Gallery Dot Net").
Quality
The output of this should be production quality, and you can hopefully help/guide me when I am on a wrong track. I not saying that everybody will be happy with my decisions, but I will try to explain why I choose as I do. Debate about the decisions are more than welcome.
No comments:
Post a Comment