Requirements Gathering and Analysis: Functional Requirements
Tweet 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 really want to go into detail on use...
Read MoreRequirements Gathering and Analysis: Assumptions, Dependencies, and Constraints
Tweet 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 replace an old one (or a system of workflows), therefore, there will be some unknowns. When writing requirement documentation, you want...
Read MoreRequirements Gathering and Analysis: User Requirements
Tweet 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 especially ensure that you understand what stakeholders and users want as well. This is what makes...
Read More15 Areas to Think About When Writing Non-Functional Requirements
Tweet Non-functional requirements should be defined when you are also creating and writing functional requirements. These are requirements that detail the constraints and quality standards that the system you are building should adhere to. You can find out what these non-functional requirements should be by your experience, interviews, and industry standards. Also, you can use functional use cases to try and discover what non-functional...
Read MoreQuestions to Ask Yourself When Collecting and Writing Security Requirements
Tweet Security is one of the most important things to consider when developing any type of system. There are numerous malicious attacks that could happen at any time that you have to ensure that your system is protected. The first step in doing this is thinking and developing the requirements that will drive the way your team and you handle anything that comes your way. Security requirements are important because you will have sensitive...
Read More
