Added include graph
This commit is contained in:
		
							
								
								
									
										21
									
								
								readme.md
									
									
									
									
									
								
							
							
						
						
									
										21
									
								
								readme.md
									
									
									
									
									
								
							@@ -11,4 +11,23 @@ Or click the build icon in vscode *shrugs*
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
# Parkmanne
 | 
					# Parkmanne
 | 
				
			||||||
## A stroll in the park
 | 
					## A stroll in the park
 | 
				
			||||||
Parkmanne aims to achieve provisionary effectiveness in the sector of parking. This problem had. 
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					This is a graph of how everything is connected.
 | 
				
			||||||
 | 
					If you need to add functionality that doesn't fall in any of these, and you're unsure of what to include, you can decide something like this:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Take my customer class for example. 
 | 
				
			||||||
 | 
					It needs to be able to save to db, so it needs data.
 | 
				
			||||||
 | 
					It needs to modify and save park_time objects, so it needs those. 
 | 
				
			||||||
 | 
					It needs to encrypt and decrypt passwords. BUT since data already includes encrypt, it doesn't have to be encrypted.
 | 
				
			||||||
 | 
					So customer includes those.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Another example is Parkspot.
 | 
				
			||||||
 | 
					It needs information about both customers and save to the database.
 | 
				
			||||||
 | 
					Since customer also includes data, i don't have to include it again.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Last example:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user