I have never worked on a project that took that approach. In my embedded product development experience, the requirements grow as the product iterations are delivered, evaluated and tested. The results of those evaluations and tests will impact the requirements. There will be additions, subtractions, and alterations of the requirements. We will update the requirements documents, […]
Requirements Language As we collect requirements we are going to need to perform some sort of evaluation. We know the attributes of good requirements, now we will compare those attributes against the documented requirements. However, we will not stop our evaluation at the type of language. We will extend this evaluation to other areas that […]
We have been working on product requirements for a number of blogs now, and we will continue that topic for the next few weeks (with exceptions). Requirements are the central driving force behind the design for the product along with risk, cost, and the opportunity of reward for the company. In general, requirement management consists […]
Software Structure Defined Non-functional requirements such as software extensibility can be very difficult to document as we likely do not know all of the future features or growth we can anticipate for the product as it matures. Poorly managed, the code may descend into what is sometimes referred to as spaghetti code. Instead of the […]
We have written much on product requirements on the blog. Requirements are those statements, derived from the project scope, upon which we will build the product. A clear understanding of these and the circumstances surrounding the use of the product will improve our chances of achieving the desired development objective. Nonfunctional Requirements One of the […]
You do not have to go it alone when it comes to developing requirements. There are many templates and well-defined approaches to help in this regard. If you are developing a complex system, it is good to break the requirements up, starting at the highest level of abstraction. We will call that systems specification. The […]
In keeping with our requirements work, we will start by identifying the attributes of a good requirement. We start our project off with the requirements, so it stands to reason if we start off poorly or in the wrong direction, we will not make the objective. This situation will get worse the longer we spend […]
Technical documentation serves as a repeatable communications medium. That is, written so that anybody reading with the appropriate competency will come away with the same conclusion. Not filling this gap or relying upon verbal communications has great limitations. Many of us have likely played that game as children where a group of people line up […]
In this series on CMMI (capability maturity model integration) and requirements, we have discussed: understanding requirements commitment to the requirements control changes to requirements traceability of requirements from detail to scope and back inconsistencies, the difference between of what is included and what is being done The processes above work together and amount to managing the […]
This area of CMMI requirements management has big implications on the project. Experience suggests project managers can get lost in the minutia of the work, but that is the connection to the project. The reason we have taken on the project is to produce some result that is defined (or it should be) in the requirements. […]