Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document priorities #3

Open
bepetersn opened this issue Aug 10, 2013 · 2 comments
Open

Document priorities #3

bepetersn opened this issue Aug 10, 2013 · 2 comments

Comments

@bepetersn
Copy link
Member

Here's some great priorities for places to start, taken from here: stackoverflow.com/a/5272219/1151229

the required steps for a Django application?

You do it like this.

Gather use cases.

Prioritize the use cases.

Define the actors. The classes of actors becomes groups in the security model.

Define enough "applications" to satisfy the first release of use cases. Define the url structure. Cool URL's don't change.

Build the first use case: models (including security), admin, urls, tests, forms, views and templates. Note that these are the file names (models.py, admin.py, ...) except for templates. Also note that forms and admin should be defined in separate modules even though this isn't required. Also note that templates will be split between a generic templates directory for top-level stuff and application-specific templates.

Build the second use case: models (including security), admin, urls, tests, forms, views and templates.

@bepetersn bepetersn changed the title Setting up priorities and organization Document priorities Apr 16, 2014
@bepetersn
Copy link
Member Author

We have decided on some basic functionality for an alpha or first deployment of this application. Find this here:

https://github.com/sc3/django-townsquare/wiki/Alpha-Requirements

@bepetersn bepetersn reopened this Apr 16, 2014
@bepetersn
Copy link
Member Author

Still needs work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant