I need some good definitions of High Level Requirements, Detail Requirements and Detail Design. There seems to be a lot of overlap and uncertainty where one ends and the other begins Saving Changes...
Sort By:
David JonesAtherstone, Warwickshire, United Kingdom
Hi, I really don't think you will get cast iron definitions. It will depend on the project in question and the development process you are following. A a rule of thumb I tend to go with the following:
High level requirements - Business flows, i.e. the business user wants to qualify and flag a customer as suitable to trade with. That is a high level requirement.
Detailed requirements - Using the above example, we will need to understand what steps are involved in qualifying the customer and how the customer status will be changed. So we need to break the above requirement down into steps (in UML a system level use case showing the interactions between the user and the system(s)). What are the exact checks that will be performed in qualifying a customer, what are the potential outcomes of those checks and how will these be dealt with. What is the exact data required for these checks etc.
Detailed Design. Is basically taking the above and turning it into a spec that developers can use to build the software (and testers can use to create test scripts etc). So now we are talking about class models, activity diagrams and even POC code to show exactly HOW this will be achieved.
Each level of analysis feeds from the one above and the requirement at the high level should be traceable through to your test scripts to prove it works as the business requires.
What methodology are you using?? Saving Changes...
Ted GibbsEnterprise Sr Project Manager| HEBSan Antonio, Tx, United States
I am using a PMI basic Waterfall Methodology, of course modified to fit my companies specific needs.
Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Dear Ted, I agree with Davis Jones and would only add that it can be quite helpful to approach High Level Requirements, Detail Requirements and Detail Design with a phase/phase exit approach like you have done. Yes there will be a little overlap, but more helpful is the opportunity to approve, modify, or even terminate a project initiative as early in the process as possible. This not only serves to continue to refine and validate inputs, but to also continue to the next phase or terminate the project with the least amount of time and resources expended. Cheers. -- Mark Perry, VP of Customer Care, BOT International Saving Changes...
There is no overlap. Requirements are the most overlooked, and at the same time the most critical part of any project. Put your high level requirements in the form of a question. Sometimes they are called critical operational issues (COI). eg. Does the system enhance users performance in process XYZ? Detailed Requirements include more detail by including various performance parameters for defining high level Req or COI. e.g. User performance using process X must be ehanced by 50% or more(may include speed, physical, min/max, etc)? Process X may be broken down in to many detailed parameters adding complexity to the detailed requirement. Detailed design is a function. An iterative process to attain systems that meets the requirement/s. If you have the flexability, develop several design alternatives, selecting the one most likely to succeed, and still meet requirements. In other words...reduce risk when ever possible. Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Dear Don, excellent reply and I agree with your comments regarding overlap. High Level Requirements and Detailed Requirements do not need to be viewed as overlapping at all. Detailed Requirements often serve to confirm or even change the initial High Level Requirements. There is no reason to view this as overlap, though many folks including myself sometimes do. Thanks! -- Mark Perry, VP of Customer Care, BOT International Saving Changes...
