Documenting Software Using An Entity Relationship Diagram

http://bit.do/dgeXm EdrawSoft secret sale page.
One of the first diagrams I usually draw at the beginning of a project is an entity relationship diagram. It allows you to document the information the business uses and I would be drawing this while discussing the processes we are concerned with automating or building an application around. It will be helpful in the step where you start to design and build your database model. For the other techniques, see my playlist Documenting software in 60 seconds https://www.youtube.com/playlist?list=PL67_9ze31skoZwr7Gs1KRBMxdOseRit41 Content: 00:04 An entity relationship diagram can help you both understand and explain what information is used and processed. 00:13 You're best drawing it when talking with the people involved. 00:16 Whenever a noun is used or the business group information together, draw them as boxes. 00:21 These are called entities. 00:23 For example, a customer is an entity, an invoice is one and products would be one too. 00:27 Entities should be named using the language everyone in the business uses 00:32 So if they talk about a clouent rather than using the word customer, then be sure to use that name instead. 00:39 Crows foot notation is used to show the entities are associated. 00:43 Starting with a customer relationship to orders, they may not have placed any, so we first draw a zero, but, they could have one or more. 00:51 Now you see the crows foot. 00:52 Looking at the orders, they're usually made up of one or more products. 00:56 You'd never have an order without a product, so it's slightly different than the previous relationshop 01:01 Also I didn't draw in that a product can have several orders, so let's add it now. Software Development Done Right Blogs https://www.clouded.ch/blog/ SUBSCRIBE ON YOUTUBE: https://goo.gl/CyKqGI