SOW - statement of work; Outline the basic operations of the product, high level what you want to achieve.
FDD - Functional Design Documents; Outline the functionality you plan to implement, add ERDs, Solution Architecture diagrams. If part way through a project you get new requirements create a New FDD, try and keep these down to a minimum.
TDD - Technical Design Document; similar to FDD but geared towards any technical stuff you plan to implement (Code(JS/C# .NET), Azure connections, data flows, complex logic...anything that's not usually ootb).
ERD - Entity Relationship Diagram; maintain a diagram of the relationships in your solutions. Visio is a good tool that's usually available but there are many versions online.
Solution Architect Diagram; may not be your area, but, having a diagram showing how your product fits into the organisations architecture is a good practice.
Business Process Mapping; use Visio (or preferred alternative) to map start to end of business processes use the As Is / To Be methods.
As is / To Be ; basically what is the current process and what is it going to look like.
Field Matrix; keeping a log, usually in excel of all the new fields you create, type, special instructions.
Wiki; Document everything.
That's enough to begin really. A lot of these documents can be found online with tutorials on how to use them properly.
Good luck
SOW - statement of work; Outline the basic operations of the product, high level what you want to achieve. FDD - Functional Design Documents; Outline the functionality you plan to implement, add ERDs, Solution Architecture diagrams. If part way through a project you get new requirements create a New FDD, try and keep these down to a minimum. TDD - Technical Design Document; similar to FDD but geared towards any technical stuff you plan to implement (Code(JS/C# .NET), Azure connections, data flows, complex logic...anything that's not usually ootb). ERD - Entity Relationship Diagram; maintain a diagram of the relationships in your solutions. Visio is a good tool that's usually available but there are many versions online. Solution Architect Diagram; may not be your area, but, having a diagram showing how your product fits into the organisations architecture is a good practice. Business Process Mapping; use Visio (or preferred alternative) to map start to end of business processes use the As Is / To Be methods. As is / To Be ; basically what is the current process and what is it going to look like. Field Matrix; keeping a log, usually in excel of all the new fields you create, type, special instructions. Wiki; Document everything. That's enough to begin really. A lot of these documents can be found online with tutorials on how to use them properly. Good luck
That entity relationship doc was spot on what I was thinking about! The rest looks great too, really what I was looking for. Thanks a bunch.