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 –
How to identify (business) processes for automation?
I recently started at a company and am working on statistical data analysis and data handling (market research). A lot of my tasks were previously done entirely by hand, so I created a few tools to automate much of my work.
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.
Use Cases with respect to downstream systems
Use cases are primarily meant for interaction between user and a system. It could be used for interaction between system and another system. The actors are primarily roles.
Conducting a requirements analysis interview
Why do requirements interviews never pan out as they are planned – and how do I prepare for that? I’m looking for the following kind of help regarding how to prepare for these interviews and what I can pay attention to in order to make the most of them.
In a functional requirements document, is the Assumptions section dangerous?
I am currently a reviewer on a Best Practices document for Developers or Business Analysts in writing a Functional Requirements document. This document is not necessarily a template for functional requirements documents, but a guide to what elements are necessary, optional, and dangerous to include a Functional Requirements document.
What is the benefit of the MoSCoW technique?
I do not see how the MoSCoW Method’s “Must, Should, Could, Would” prioritisation is better that simply 1,2,3,4? If I receive the requirements from the customer, they already are prioritised, usually using this range.
Also what is so interesting on this MoSCoW thing, why it is so ‘famous’?
How to get better understanding of the users as a programmer
I work at a company that wants to be agile, but the business analysts often provide us “user stories” that are more solution than problem statement. This makes it difficult to make good design decisions, or in more extreme cases, leaves few design decisions to be made. It does not help the programmers understand the user’s needs or make better design decisions in the future. Our product owner makes an effort to provide us with problem statements, but we still sometimes get solution statements, and that tends toward a “code monkey” situation.