Requirements Intelligence Sample Clauses

Requirements Intelligence role in the architecture The overall OpenReq architecture is composed of the OpenReq REST Services and the different stakeholder applications who use the services (see Figure 2). Besides the trial partner applications, the OpenReq Prototype (a showcase of major OpenReq functionalities) accesses the different OpenReq services. The OpenReq Prototype includes basic OpenReq functionalities offered to end users through an understandable and user-friendly user interface. In all cases where end users interact with OpenReq functionalities, a special focus will be given on usability.
Sample 1
AutoNDA by SimpleDocs
Requirements Intelligence. This component will encapsulate an analytics backend and include text-mining algorithms that allow the analysis of natural language in text-based documents or user feedback (user feedback can be either explicit or implicit - see Figure 2). In addition to that also interactive visualization will be supported by this component. In particular, interactive visualization supports stakeholders in visualizing descriptive and predictive analytics data. An example of such a visualization is shown in Figure 3. Figure presents the trend of different app review types (e.g., a user requests a new feature or a bug to be fixed) over time, for a specific app and over its different versions. Figure 2: Example for explicit and implicit feedback Figure 3: Example trend of different app review types
Sample 1
Requirements Intelligence. In OpenReq, we define requirements intelligence (RI) similar to business intelligence (BI). For BI, we use the definition of [Xxxxxx 2004]: “BI systems combine data gathering, data storage, and knowledge management with analytical tools to present complex internal and competitive information to planners and decision makers.” RI follows the same definition but focuses on requirements of software products. RI is the systematic collection, analysis, processing, and visualization of requirements and user feedback coming from natural text such as issue trackers, app reviews, or legacy requirements. The goal of RI is to provide new insights about software products based on diverse data sources of natural language and metadata. In order to describe the state of the art, we separate RI into the topics mining, classification, clustering, and visualization of requirements (a deeper literature analysis can be found in D2.1). With text mining, we are able to retrieve requirements or related information to those in natural text. A survey by Xxxx et al. [2004] found that 79% of companies use unstructured natural language in their requirements documents; 16% use structured natural language (e.g., using templates); 5% use formal approaches. Therefore, the application of natural language processing (NLP) to requirements engineering has attracted a lot of attention from software engineering researchers and practitioners [Xxxxx 1995]. Already in the late 1990s, NASA built a tool that leverages NLP for requirement engineering (Automated Requirements Measurement, or ARM) [Xxxxxxx and Xxxxxxxx 2014]. In the area of software engineering, several approaches have been developed in the recent years with many focusing on app stores as shown in [Harman et al. 2012], [Xxxxxx et al. 2017], [Xxxxxx and Xxxxxx 2013]. An interesting source of information can be found in user reviews, comments, and social media in general, as people use these platforms to describe their desires and issues online [Xxxxxx and Xxxxxx 2014], [Xxxxxxxx and Xxxxxxx 2017], [Xxxxxx et al. 2017]. The next step is the classification of requirements, which deals, among others, with the classification of requirements into functional (FR) and non-functional (NFR) as shown by the authors [Xxxxxxxx et al. 2016], [Xxxxxxxxxxx and Xxxxxx 1997], and [Xxxxxxxxxx and Xxxxxx 2017]. In addition, RI will take advantage of the research done in the identification of bug reports, feature requests, and non-informative text in user r...
Sample 1
Requirements Intelligence. We define requirements intelligence (RI) similarly to business intelligence (BI) but with a focus on requirements of software products. RI is about the systematic collection, analysis, processing, and visualization of requirements and user feedback coming from natural text such as issue trackers, app reviews, or legacy requirements. The goal of RI is to provide new insights about software products based on diverse data sources of natural language and meta data. These insights can be generated from software product descriptions and used to analyze the product features and compare it to its competitors. More insights can also come from explicit feedback such as user reviews, or from implicit data gathered from the software product itself. Further, data can come from different channels such as social media, issue trackers, emails, and other media. Combining data from different perspectives and channels leads to new ways of creating and adapting requirements as they are based on facts (e.g., implicit feedback) and customers’ subjective impressions (e.g., explicit feedback). User feedback can be used to recommend, for example, software features the customers often wishes for, which the stakeholders can then turn into requirements. OpenReq will identify those actively discussed software features and recommend them to the stakeholders. The stakeholders might agree with the discussion and turn the discussed feature to a requirement. RI will also provide insights to understand user needs, especially for companies that are overwhelmed by the huge amount of data, by aggregating the opinion and sentiment of a large number of reviews related to their software product. In this document, we describe the technical approach to mining, processing, and visualizing requirements-related data.
Sample 1

Related to Requirements Intelligence

  • Insurance and Fingerprint Requirements Information Insurance If applicable and your staff will be on TIPS member premises for delivery, training or installation etc. and/or with an automobile, you must carry automobile insurance as required by law. You may be asked to provide proof of insurance. Fingerprint It is possible that a vendor may be subject to Chapter 22 of the Texas Education Code. The Texas Education Code, Chapter 22, Section 22.0834. Statutory language may be found at: xxxx://xxx.xxxxxxxx.xxxxx.xxxxx.xx.xx/ If the vendor has staff that meet both of these criterion: (1) will have continuing duties related to the contracted services; and (2) has or will have direct contact with students Then you have ”covered” employees for purposes of completing the attached form. TIPS recommends all vendors consult their legal counsel for guidance in compliance with this law. If you have questions on how to comply, see below. If you have questions on compliance with this code section, contact the Texas Department of Public Safety Non-Criminal Justice Unit, Access and Dissemination Bureau, FAST-FACT at XXXX@xxxxx.xxxxx.xx.xx and you should send an email identifying you as a contractor to a Texas Independent School District or ESC Region 8 and TIPS. Texas DPS phone number is (000) 000-0000. See form in the next attribute to complete entitled: Texas Education Code Chapter 22 Contractor Certification for Contractor Employees

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Technology Requirements The Customer is required to obtain and maintain, at the Customer’s own expense, compatible Electronic Channels, hardware, operating systems, and software approved for such use by Royal Bank, and which are up-to-date and unaltered from manufacturer specifications. Royal Bank is not responsible for, and makes no representations or warranties of any nature, with respect to any such Electronic Channels, hardware, operating systems, and software provided by any other Person. Royal Bank has the right, in its sole discretion, without notice, to make changes to this Service from time to time which may result in the Customer’s Electronic Channels, hardware, operating systems, and software no longer being compatible with this Service, and in such event, Royal Bank will have no responsibility or liability to the Customer or any other Person.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Academic Requirements 4. a) If a student is not able to maintain a course load of at least eighteen units, as defined in section 2, the student will be required to withdraw from residence and to meet the financial responsibilities, as outlined in section 16. A student who cannot maintain a course load of at least eighteen units for medical, or compassionate reasons must submit a written appeal with supporting documents to Residence Admissions to be considered for permission to remain in residence.

  • Procurement Requirements The below listed provisions of State Procurement requirements shall be complied with throughout the contract period:

  • CLEARANCE REQUIREMENTS CONTRACTOR shall comply with the requirements of California Education Code section 44237, 35021.1, 35021.2, and 56366.1 including, but not limited to: obtaining clearance from both the California Department of Justice (hereinafter referred to as “CDOJ”) and clearance from the Federal Bureau of Investigation (hereinafter referred to as "FBI") for CONTRACTOR’s employees and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students. CONTRACTOR hereby agrees that CONTRACTOR’s employees and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students shall not come in contact with students until CDOJ and FBI clearance are ascertained. CONTRACTOR shall certify in writing to LEA that none of its employees, and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students, or contractors who may come into contact with students have been convicted of a violent or serious felony as those terms are defined in California Education Code section 44237(h), unless despite the employee’s conviction of a violent or serious felony, he or she has met the criteria to be eligible for employment pursuant to California Education Code section 44237 (i) or (j). Contractor shall certify to LEA that they have successful background checks and enrolled in subsequent arrest notification service for all employees who may come into contact with students. Notwithstanding the restrictions on sharing and destroying criminal background check information, CONTRACTOR, upon demand, shall make available to the LEA evidence of a successful criminal background check clearance and enrollment in subsequent arrest notice service, as provided, for each owner, operator, and employee of the NPS/A. CONTRACTOR is required to retain the evidence on-site, as specified, for all staff, including those licensed or credentialed by another state agency. Background clearances and proof of subsequent arrest notification service as required by California Penal Code section 11105.2 for all staff shall be provided upon request.

  • Customer Requirements ▪ Seller shall comply with the applicable terms and conditions of any agreements between Buyer and Xxxxx’s Customer (the “Customer Purchase Orders”) pursuant to which Buyer agreed to sell to Buyer’s Customer products or assemblies which incorporate the goods provided by Seller hereunder. This provision specifically includes costs and obligations imposed by warranty programs instituted by the original equipment manufacturer that ultimately purchases Buyer’s products that incorporate the goods sold by Seller if applicable to Buyer under the terms of the Customer Purchase Order. ▪ If Buyer is not acting as a Tier One supplier, the defined term “Customer Purchase Order” shall also include the terms and conditions of the original equipment manufacturer that ultimately purchases Buyer’s product that incorporates the goods or services sold by Seller. ▪ Seller will be responsible to ascertain how the disclosed terms affect Seller’s performance under the Purchase Order. ▪ By written notice to Seller, Buyer may elect to disclose and have the provisions of the Customer’s Purchase Orders prevail over any term of the Purchase Order at any time.

Time is Money Join Law Insider Premium to draft better contracts faster.