Seattle University Non-Functional Requirements Sur

Before design or coding, we perform interviews of potential or previous users to determine how they will use the product

During design we construct personas or roles that describe the traits of different types of users who will use our product. Using these constructs, we identify how to build the interface for the primary users

We use open beta testing in which anyone in your user base can test the software before implementation

We use closed beta testing in which only select users are allowed to use the pre-release version of the software

During testing or after implementation we use interviews or surveys to learn what users think of the product and its interface

During testing or after implementation, we perform long term studies with some users at their place of work (“in situ”) to determine how the users interact with the product after they have acclimated to it.

We don’t identify our users.

Other

Background

This Survey

Your Participation

Related templates and questionnaires

QuestionPro in your language


Page 1 of 5 Hello! You are invited to participate in our survey about better understanding the current state of the software industry and its efforts to effectively manage non-functional (quality) requirements. Background The cost of modifying software late in the software development lifecycle is high, and in the case of non-functional requirements such as security, reliability, performance and usability, the impacts of not considering these factors early and in a formal manner can be devastating to a product’s marketability and profitability. Our project looks to gain an understanding of where in the development lifecycle companies address different non-functional requirements and what methods, if any, they are taking to address these requirements earlier in the development lifecycle. The goal of this research is to highlight the sporadic industry acceptance of some popular yet theoretical methods for designing for non-functional requirements and to suggest some practical approaches that are applicable for companies that also must consider the demands of schedule and cost. This Survey In this survey, approximately 100 people will be asked to complete a survey that asks 10 questions about non-functional requirements. It will take approximately 10 to 15 minutes to complete the questionnaire. Your Participation Your participation in this study is completely voluntary. There are no foreseeable risks associated with this project. However, if you feel uncomfortable answering any questions, you can withdraw from the survey at any point. As a professional in software engineering, your opinions are very important to us. Your survey responses will be strictly confidential and data from this research will be reported only in the aggregate. Your information will be coded and will remain confidential. If you have questions at any time about the survey or the procedures, you may contact us using the contact information at the end of the survey. Thank you very much for your time and support. Please start with the survey now by clicking on the Next --> button below. At what stage of a project’s development does your team address software performance? (distribute 100 points evenly) Requirements Gathering Design and Documentation Coding Integration Internal testing and measurement Post-implementation measurement and feedback 0 Indicate the following methods that your team uses to ensure that your product will meet the performance requirements of your customer. (select all that apply) We identify the scenarios or use cases that are most important to our product and work on improving the performance of those features We identify the critical path in our architecture so that we can design our product to satisfy the minimum performance requirements. We perform design reviews that focus on identifying potential bottlenecks and/or applying industry “best practices” for improving performance We use automated testing products or algorithms to test the performance of our software before integration During the integration of our product we use a hierarchy or another method to “silo” or “de-couple” our code modules from one another so that poorly performing sections will be “fire-walled” and prevented from negatively affecting the rest of the product. We measure the overall performance of our software after implementation Other Complete the following sentence: If I had only one metric for determining if my product meets performance requirements, I would measure: Specify what you do to identify your users during the development of your product. (select all that apply) Before design or coding, we perform interviews of potential or previous users to determine how they will use the product During design we construct personas or roles that describe the traits of different types of users who will use our product. Using these constructs, we identify how to build the interface for the primary users We use open beta testing in which anyone in your user base can test the software before implementation We use closed beta testing in which only select users are allowed to use the pre-release version of the software During testing or after implementation we use interviews or surveys to learn what users think of the product and its interface During testing or after implementation, we perform long term studies with some users at their place of work (“in situ”) to determine how the users interact with the product after they have acclimated to it. We don’t identify our users. Other Identify the percentage of the following methods you use to design your user interface. (distribute 100 points evenly) Simple or low fidelity prototypes such as paper. Medium fidelity such as Powerpoint High fidelity prototypes that are interactive but have little or no functionality (such as Adobe Flash or Adobe Director) Evolutionary prototype built on end-product technology that is later used as a starting point for the product Other 0 Complete the following sentence: If I had only one metric for determining if my product meets usability requirements, I would measure: How do you verify that your product meets the reliability requirements of your users? (select all that apply) We perform static code analysis We use test code coverage to ensure that all lines of code have been tested We use load testing that mimics actual usage patterns We use stress testing to define the limits of our product After implementation, we gather metrics on failures (e.g. automated crash reports, user supplied log reports) Complete the following sentence: If I had only one metric for determining if my product meets reliability requirements, I would measure: How do you ensure that your product is secure? (select all that apply) We use managed-code (C#, Java, etc.) so that security issues are addressed by the compiler in a consistently secure manner. During design we analyze our data flow to determine vulnerable areas that could comprise security or data integrity. We use static code analyzers to identify potential security issues. We use fuzz testing to inject random errors into the data stream. We use security experts to examine the code and/or product to identify potential deficiencies. Complete the following sentence: If I had only one metric for determining if my product meets security requirements, I would measure: Name Email address If you have additional comments you may contact us at the following email addresses: Ward Vuillemot [email protected] Wai Wong [email protected] David Yager [email protected]