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 ...
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 ...
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 ...
By day, word lover who loves writing technical documents and proposals. By night, superhero fighting to change the drinking culture.
check out more about me
