Requirements Writing Series

I’ve been getting a lot of questions about requirements and how to document them, so I decided to dedicate this week to requirements. Oh, the joys of requirements. It isn’t just using your colleagues and your expertise to come up with the requirements that will be used to design the envisioned system. You have to [...]

Yesterday, I talked about user requirements. In the world of requirements, even if you do a great job gathering and analyzing requirements, there will still be a couple of gray areas. There may be a couple of reasons for this. The main reason is that this is a new system that you are developing to [...]

Before Thanksgiving (how much did you eat? Tell the truth), I wrote about user requirements, assumptions, dependencies, and constraints. This leads the discussion to functional requirements. I am going to break into three parts: basic information about functional requirements, requirements traceability matrix, and use cases. Use cases usually go hand-in-hand with functional requirements, but I [...]

I discussed non-functional requirements in my previous post “15 Areas to Think About When Writing Non-Functional Requirements.” Non-functional requirements are the requirements that stakeholders and users haven’t thought of, but you have to because without them, the system will fail. If you don’t collect non-functional requirements, then you will not be creating a system that [...]

When you are capturing functional requirements, you usually create use cases. There are two parts to a use case: 1. Use case diagram and 2. Writing part. Use cases are used to identify and illustrate the different parts of a process. It captures: Actors Business Rules Pre-conditions Trigger Main Flow Alternate Flow(s) Post-condition Title You [...]