What kind of metrics, if any, can be collected from requirements development?
We elicit requirements from our product stakeholders by creating and refining user stories in monthly sprint planning meetings. This includes defining use cases, acceptance criteria, and identifying constraints, and the final result is a sprint backlog of user stories. The high-level customer requirements are refined into lower-level product requirements through design reviews among the development team throughout the sprint. The design reviews result in UML diagrams, software interfaces, and, in general, a human language description of various software requirements.
How to use TFS as a query tracking system?
We already use tfs for managing defects in code etc, etc. We additionally need a way to “understand the domain & requirements of the products”. Normally, without tfs we exchange emails with the consultants and have the questions/queries answered. If it is a feature implementation we sometimes “find” conflicts in the implementation itself. And when that happens the userstory is modified and the enhancement/bug as per that is raised in TFS.
How can I better manage far-reaching changes in my code?
In my work (writing scientific software in C++), I often get asked by the people who use the software to get their work done to add some functionality or change the way things are done and organized right now. Most of the time this is just a matter of adding a new class or a function and applying some glue to do the job, but from time to time, a seemingly simple change turns out to have far-reaching consequences that require me to redesign a substantial amount of existing code, which takes a lot of time and effort, and is difficult to evaluate in terms of time required. I don’t think it has as much to do with inter-dependence of modules, as with changing requirements (admittedly, on a smaller scale).
Requesting quality analysis test cases up front of implementation/change
Recently I have been assigned to work on a major requirement that falls between a change request and an improvement. The previous implementation was done (badly) by a senior developer that left the company and did so without leaving a trace of documentation.
Here were my initial steps to approach this problem:
Requesting quality analysis test cases up front of implementation/change
Recently I have been assigned to work on a major requirement that falls between a change request and an improvement. The previous implementation was done (badly) by a senior developer that left the company and did so without leaving a trace of documentation.
Here were my initial steps to approach this problem:
User Stories – How should it be defined for complex changes involving multiple applications
This is one of the definitions that I asw for user stories –
Level of detail in System Requirements
I’ve read in multiple places that the requirements must not be influenced by solution and must not contain solution. So in the below example , please can you help in letting me which is correct –
System Requirements – Use of Conjunctions
I have come across many blogs and books where it is stated that it is bad for a system requirement to contain conjunctions like “and”. However in reality I am often coming across scenario where a requirement is satisfied when a certain set of conditions are met. For instance, Shopkeeper should sell alcohol only if the buyer is older than 18 years, he has the necessary proof and he does not have any alcohol related problems. The requirement would not be complete if I break it down into multiple system requirements and I cannot complete the requirement without use of “and”.
Agile Development & Interaction with Developers
I have read in few blogs that as part of agile development , the product owner closely interact with developers to state their requirements and come up with a solution. However in case of a large project (in terms of number of applications involved) involving multiple systems , is this possible? Shouldn’t the project have a business analyst / solution designer in order to capture the requirements properly and come up with a solution which states how the the requirement could be fulfilled and which systems must do what activity?
Functional Requirements / Specification and relationship to DEV and QA
Functional Requirements state “WHAT” needs to be done from a user’s perspective
Functional Specification state “HOW” it needs to be done from technical standpoint.