Question on System Requirement
I have a scenario where a specific webservice must be consumed based on the state to setup user info. For instance if the state is NY or NJ call service A , if state is WA call service B etc. But specifying what service must be called is I guess is “HOW” to setup a user info and not a “WHAT”.
How to label software requirements?
What is a good strategy to label software requirements in an SRS?
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.
Rigorous way to compare designs that support the same project
When having 4 different designs that can be delivered for a project and there is a strong difference of opinions on which design is preferred taking into account functional/non-functional requirements/effort etc is there some standard template/framework that can be used rigorously for comparison of the approaches?
I could come up with my own spreadsheet, I was interested if there is some existing framework that can be used in such cases?
How to deal with high level requirements that contain implementation details?
My question actually applies to a physical device development, but I guess it is equivalent to a software development workflow, so perhaps someone here can enlighten me.
How to consider the login function collecting requirements of an application? is it a user requirement?
I am working on an application that expected to the user logs in when the application is started (as for example it is in Skype: the user open the application and appear to him a login mask when he insert the username and password to start work with the application)
How to consider the login function collecting requirements of an application? is it a user requirement?
I am working on an application that expected to the user logs in when the application is started (as for example it is in Skype: the user open the application and appear to him a login mask when he insert the username and password to start work with the application)
How to consider the login function collecting requirements of an application? is it a user requirement?
I am working on an application that expected to the user logs in when the application is started (as for example it is in Skype: the user open the application and appear to him a login mask when he insert the username and password to start work with the application)
How to consider the login function collecting requirements of an application? is it a user requirement?
I am working on an application that expected to the user logs in when the application is started (as for example it is in Skype: the user open the application and appear to him a login mask when he insert the username and password to start work with the application)
How to consider the login function collecting requirements of an application? is it a user requirement?
I am working on an application that expected to the user logs in when the application is started (as for example it is in Skype: the user open the application and appear to him a login mask when he insert the username and password to start work with the application)