Hi All, I am working on a project where I need to document Database architure requirements which are all Policy driven. We currently have a client maintence screen which is driven by look up tables and business logic held in Back end SQL server tables, which are delivered to analysts every month via a fairly simple Access database which houses all the tables and fields for further analysis on specific data. Having had preliminary discussions with the business, it has been suggested that we change this monthly deliverable to include new fields, apply certain elements of business logic which will feed the population of the fields and in general, change the way the information is captured via the UI;s. I am comfortable in writing these up in the wide array of documentation types which are currently being used by analysts globally, but woudl apprecaite if anyone knows of a specific documentation type which would encompass database changes, being driven by policy requirements etc etc. Thanks, Jason
Hi Jason,
My first comment on this is that you should first work out the business drivers behind all these changes before doing the solution. If the business says "I want these extra fields", that isn't their requirement, that is their perceived solution for their requirement. When you get to what are the real requirements you may find that what they want as a solution will not work or that there is a better way. Looks like you have this approach anyway from your comment I saw on another posting and the fact that policy requirements are behind the database requirements?
As for documentation, I suggest doing a UML class diagram. In this case I'd do a data dictionary to back up the class diagram as well. If you also have your policy requiremnts, link the policy requirements to the classes or even the attributes. Also to your business rules, functional requirements and UI. Then when your policy changes, you'll know what classes, screens, rules, functions, etc you need to look at to see if they need changing.
Not sure I answered your question - particular the bit about getting monthly deliverables from the Access database - but I hope that helps.
Kimbo
Hi Kimbo, Thanks very much for the rather prompt response. I think problem is because some of my requirement stakeholders and SME's are relatively tech savy, the requirements elicitation process already started of with "we want these new fields" and "We want backwards and forwards linking between these date fields, so we can analyssi x y or z" that actuall businss drivers were not discussed, even though I nudged alot to get something out of them. But thanks for the comment, will capture the policy requirements first, which will act as the main impetus for the actual functional and database change requirments and will map these onto the UI screens etc etc. Would be helpful if you have a sample document of some sort which would provide some sort of Visual as to way in which you envisaged this, if not,its not a problem! Its the joys of being a BA, we can pretty much document stuff the way we want to as long as ous stakeholders and we understand them! Jason
The actual project I worked on was a consulting job at a government department. I used a modelling tool called Holocentric (www.holocentric.com) on this project. That was a couple of years ago. I now use Enterprise Architect by Sparx systems (www.sparxsystems.com). Key is just to create links between the various objects. Then when something changes, you see what its linked to and work out what you need to change. EA (and holocentric) are very visual. Create links by joining objects on diagrams. I created a type of requirement called "legislation" I think and then put all the legislation clauses into requirements. Managed to package them up properly someway. Then linked each "legislation" requirement to the other objects that realise it. Of course the links are all many to many and its just a best guess but it can help if you maintain it properly. the Government department liked it.
So sorry, no sample document. It was all model based. Generated word documents (and web sites) out of the modelling tool. Much harder to just do it in Word. Do you have access to a modelling tool? Most of them should be able to handle it.
brought to you by enabling practitioners & organizations to achieve their goals using: