When creating a data dictionary, it is critical not to design with it. You should not be attempting to create a database nor should you be showing the relationships of data. This will be a detailed description of the data involved in your project. It will also be one of the largest morale draining approval [...]
Posts Tagged "data dictionaries"
Number 3 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do instead.” Short-change Time Spent on Software Requirements or Don’t do Them at All Don’t Listen to Your Customer’s Needs Don’t use models Use weasel words [...]
3 Basic Tips to Data Migration Requirements for your Software Project It’s late stage of a project, so it’s time to start worrying about your data migration requirements if you haven’t already! If you have done it, good for you! You can just stop reading. But so many projects push this to the end and [...]
Do you find that you’re always trying to use process flows on your projects, but they just don’t seem to fit your needs? Do you need to start modeling requirements, but can’t quite decide what models to use? There are quite a few requirements models out there to choose from, ranging from the mundane (process [...]
Data dictionaries have been around for quite a long time. I have a book on analysis that was written in 1979 that covers them in great detail. Unfortunately, most of the techniques in that text focus on how to collate and manage the data rather than what data to include. There’s nothing quite like reading [...]