Service selection of names and names from idea to implementation or Django as an excellent platform for startups. Continuation
In the previous article I wrote how the startup namingservice.org began. In this topic, I will continue to describe the next stage of the idea materialization. After the “Vision of the project” document was ready, I thought that it would be great to put on a paper the views of the site, that is, how it should look, and how I imagined it.
It all started with the look of the home page. It was supposed to give a brief idea of ​​the project, and contain a page header (logo, slogan, navigation, login and registration buttons), plus I decided that it would be useful to display orders directly on the main page with a brief description and price.
The result was a document consisting of 15 species, which formed the basis of the site design. What came out of this can be viewed directly on the site , but in order to feel the difference between what was designed and what came out, I will cite a few more basic types.
')
This document outlined the basic data requirements.
To store the personal settings of users is the standard table Django User.
User accounts reflect current user balance. Information stored in user accounts includes:
Transactions keep a history of all transactions performed on user accounts. Information stored in transactions includes:
Orders contain all information about incoming, active and already completed orders. Information stored in orders includes:
It contains all the offers coming from users. Information stored in sentences includes:
* Cardinality - the type of connection (1: M - one-to-many, M: N - many to many).
** Participation rate is obligatory, it is not necessary to have this connection for each tuple (line) of entity (table) (P is partial participation in the link, T is full participation in the link).
The result is a scheme that connects the database structure with applications Django Framework
This is where the design of the project was completed, after which there was no more strength and patience to design further, and I started writing code in the Django Framework.
Kinds
It all started with the look of the home page. It was supposed to give a brief idea of ​​the project, and contain a page header (logo, slogan, navigation, login and registration buttons), plus I decided that it would be useful to display orders directly on the main page with a brief description and price.
The result was a document consisting of 15 species, which formed the basis of the site design. What came out of this can be viewed directly on the site , but in order to feel the difference between what was designed and what came out, I will cite a few more basic types.
')
View "My Orders"
View "My order"
View "My account"
Data requirements
This document outlined the basic data requirements.
1 User Profiles
To store the personal settings of users is the standard table Django User.
2 User Accounts
User accounts reflect current user balance. Information stored in user accounts includes:
- Amount of funds in the account
- Account currency (may be needed in the future, the default is USD)
3 Transactions
Transactions keep a history of all transactions performed on user accounts. Information stored in transactions includes:
- date
- Type of
- Amount
- Status
- The note
4 Orders
Orders contain all information about incoming, active and already completed orders. Information stored in orders includes:
- Description
- Order keywords
- Restrictions
- Additionally
- Price
- Status
- date of creation
- Date of change
- Language (so that later in translation to take this into account when showing)
5 Offers
It contains all the offers coming from users. Information stored in sentences includes:
- Sentence
- Status
- date of creation
- Date of change
6 Entity Types
- Profile
- Score
- Transaction
- Order
- Sentence
7 Types of relationships
| Entity Type | Connection | Entity Type | Cardinality * | Participation Rate ** |
|---|---|---|---|---|
| Profile | It has | Score | 1: M | T: T |
| Score | It has | Transaction | 1: M | P: T |
| Profile | It has | Order | 1: M | P: T |
| Profile | It has | Sentence | 1: M | P: T |
| Order | It has | Sentence | 1: M | P: T |
* Cardinality - the type of connection (1: M - one-to-many, M: N - many to many).
** Participation rate is obligatory, it is not necessary to have this connection for each tuple (line) of entity (table) (P is partial participation in the link, T is full participation in the link).
The result is a scheme that connects the database structure with applications Django Framework
This is where the design of the project was completed, after which there was no more strength and patience to design further, and I started writing code in the Django Framework.
Source: https://habr.com/ru/post/126437/
All Articles