Requirements management tools Sample Clauses

Requirements management tools. To manage all of the before mentioned activities, the market offer different solutions to carry out all the lifecycle that we need to cover. These kind of tools allows to map all the requirements in Use cases and modelling these in the system to achieve the UML models for transformation process in MDA. For example, Rational RequisitePro is an easy to use requirements management tool that lets a team: • Author and share their requirements using familiar document-based methods while leveraging database-enabled capabilities such as requirements traceability and impact analysis. • Apply requirements management using the Use Case technique which should help the eDIANA project to manage individual requirement artifacts and fit requirements within the Rational Unified Process (RUP). • Make customizations to the requirements process specific to the eDIANA project and work with guidelines and techniques for capturing functional and system requirements. • Use traceability and tools to automate time-consuming processes . Specify, validate and manage evolving requirements. At the end, Use Cases provide the basis for the whole object-oriented, software life cycle including architecture, design (including GUI design) and development. At the same time Use cases help testing efforts by facilitating the creation of test cases. All tests must contain a sequence of events, which will be followed to test a particular area of the eDIANA system.
AutoNDA by SimpleDocs

Related to Requirements management tools

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Traffic Management The Customer will not utilize the Services in a manner which, in the view of the Centre Operator, significantly distorts traffic balance on the Centre Operator’s circuits which are shared with other users. If, in the reasonable view of the Centre Operator, the Customer’s traffic patterns cause or may cause such distortion, the Customer should have a dedicated circuit capability. If the Customer declines to do so then the Centre Operator may suspend the Services while the matter is being resolved. If there is no resolution within 5 business days then either party may terminate the Agreement.

  • Programme Management The Government will establish a programme management office and the Council will be able to access funding support to participate in the reform process. The Government will provide further guidance on the approach to programme support, central and regional support functions and activities and criteria for determining eligibility for funding support. This guidance will also include the specifics of any information required to progress the reform that may be related to asset quality, asset value, costs, and funding arrangements.

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following:

  • Network Management 60.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Time Management Because of the nature of the duties performed by these supervisors, it is impracticable to apply provisions which prescribe normal work hours. However, it is normally expected that eighty (80) hours of work shall constitute a normal payroll period. It is recognized that these supervisors are responsible for managing and accounting for their own hours of work and that they may work hours in excess of the normal work day and/or payroll period and may make adjustments in hours of work in subsequent work days and/or payroll periods, provided such time management system does not result in overtime payment or guarantee hour-for-hour time off for extra hours worked.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.

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