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 […]
We have discussed the nonfunctional requirements for extensibility in our earlier posts. Now we turn to others in the nonfunctional list of requirements. Today we are going to consider maintainability. Maintainability is the measure of ability to successfully repair or fix the product after manufacturing, usually in the field, and over time. For manufacturing entities, […]
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 […]
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 […]
Recent events have prompted us to preempt our CMMI requirements management series for this waste of company resources that we can only attribute to an overly politicized work environment and fear. The downside of functional or siloed organizations is demonstrated in the sentiment “fix your own sandbox”. Complications of the Organization In general, the work […]
CMMI and Understanding Requirements We have recently been involved in a LinkedIn discussion about understanding requirements. We have had several quick blog posts on requirements over the years. For example, we have written about the connection of requirements and project management. We have also discussed how requirements grow over the course of the development of […]
This post was inspired by David Greer who presented us with the topic of devops and continuous delirium. When it comes to devops, continuous delirium has two connotations as in wildly excited, and incoherent and bewildering. When done appropriately, the development personnel and our customer will be wildly excited to be a part of such a wonderful […]