Test Management Tool Request for Information

Transcription

1 State of Florida Department of Revenue ISP Request for Information Test Management Tool RFI #17/ Introduction The Florida Department of Revenue (the Department or FDOR ), hereby issues this Request for Information ( RFI ) seeking information from interested parties who can provide a test management tool to the Department. The goal of this RFI is to provide the Department with the latest information on testing tools for the purpose of improving the Department s test management capabilities. 2. Purpose of an RFI Rule 60A 1.042, Florida Administrative Code, provides that an agency may request information by issuing a written RFI. Agencies are authorized to use an RFI in circumstances including, but not limited to, determining whether or not to competitively procure a commodity or contractual services, determining what solicitation process to use for a particular need, or researching general, special, and/or technical specifications for a solicitation. A vendor s response to a RFI is not an offer and the agency may not use the vendor s submission to justify a contract with that vendor without otherwise complying with Chapter 287, Florida Statutes (F.S.) and Rule 60A 1.042, F.A.C. Vendors submitting a response to an agency s RFI are not prohibited from responding to any related subsequent solicitation. Any future purchase of the services will be conducted in accordance with Chapter 287, F.S. The Department may use responses to this RFI to prepare one or more competitive solicitations and as the basis for any subsequent vendor meetings. 3. Requirements The Test Tool 3.1. Shall provide the following General Features: must allow for the capability to map or track any test item must allow for out of the box functionality for change control and defect tracking that can be deployed with minimal time and effort must allow for the creation and modification of a test item

2 must be able to easily change or modify mandatory fields must allow for attachments, such as screen shots, reports and/or files to be added to, edited or deleted from a test item must support the ability to include URL links as part of a request must support the ability to manage requests outside of a normal workflow must provide an integrated spell check facility for each text and memo fields as well as allow for the use of custom dictionaries must provide the ability to compose, send and capture user communication pertaining to a request or defect that is initiated via e mail must provide the capability to lock a record during update to prevent overlays as well as offer a user definable time out period for the record lock must allow one or more child workflows to be created that are related to a parent workflow in order to accommodate multiple owners being assigned to a test item. Each child must be able to be fulfilled in serial or parallel and the parent must optionally be able to wait for every child to be completed must provide a utility to transition multiple items at the same time, for instance a group of developers is being reassigned to a project must support the creation of a knowledge base such as a collection of frequently asked questions, common problems/resolutions, etc must provide the ability to assign ownership for all items tracked to ensure accountability for completing items as well as timeliness in resolving them 3.2. Shall provide the following Architectural Requirements: must be Web architected to ensure accessibility from any geographical location via a browser must provide the capability to invoke other browser based tools must be able to scale to support large amounts of data and must not impose any database size restrictions must allow for the creation of support information related to a tracked item to be created and maintained as part of the items history must utilize proven, multi tier client/server architecture to control software development activities across multiple hosts and platforms must support network communication via TCP/IP and be architected to minimize network traffic must store its configuration and historical information in an ODBC compliant, relational database 3.3. Shall provide the following Workflow Requirements:

3 must provide the capability to generate and modify a process flow for any process or request must provide the ability to generate and modify a process flow for any process or request must provide a graphical tree representation of workflow, project and folders hierarchy must provide the capability to link related workflows together, for example linking a test defect workflow to a development workflow 3.4. Shall provide the following Notification/Escalation Requirements: must provide a method to notify a user that something requires their attention must allow for custom notifications to be created that may include an automated action such as executing a script must allow for a user to be able to subscribe to various request and event notifications must provide the ability to easily escalate items without requiring any special programming language must have a rules based engine to assist with the generation of user defined rules that automatically create notifications 3.5. Shall provide the following User Interface/Administration Requirements: All end user product functionality must be available via the Internet User interface must be easy to navigate by non technical as well as technical users must provide the user with the ability to define the user s personal view of the system at initial logon must allow a user to query the database utilizing keywords and wildcards, as well as searches by active/inactive requests, requests owned by a particular user, etc must allow administrative changes to be made to the system without requiring end users to logout or the system to be re cycled must allow for Global Administration as well as the capability to delegate administration duties to others by limiting the rights to administer specific projects, groups or users, workflows, functions, tables, etc should not require the administrator to learn a proprietary scripting language for workflow creation and maintenance must provide an easy to use GUI interface with same look, feel and functionality on all platforms must provide a web browser client administration functions of the product should be flexibly designed and allow for delegation of some administrative tasks to power users or project leads.

4 the product must require minimal administration on a daily basis 3.6. Shall meet the following Integration Requirements: must integrate with complimentary tools that are involved in the actual software change task of the SCM lifecycle must integrate with HP Products must integrate with the Revelations Rev Trac Release Management tool 3.7. Shall meet the following Security Requirements: must allow for user authentication via the native operating system must provide the capability to establish user privileges based upon user and/or group permissions must provide for role based security must provide secured read/write access to libraries that it maintains, ensuring no access to individuals outside the control of the distributed product must provide flexible security with no practical limitations on groupings 3.8. Shall provide the following Reporting and Auditing Requirements: must provide pre defined reports as well as the ability to generate ad hoc, graphical and tabular reports must allow a user to export information to other applications for reporting must allow reports to be created from user written SQL queries must provide the capability for a management dashboard portal must capture and maintain a complete audit trail of every tracked item must provide a historical audit trail of all activity across multiple, heterogeneous platforms 3.9. Shall provide the following Version Requirements: must provide seamless, efficient file transfers between multiple, heterogeneous platforms in disparate geographical locations to effect movement of code (i.e., check outs, check ins, promotions, distribution, etc) during the life cycle of the application must allow access to versions other than the most current must automatically save an unlimited number of old versions of changed files/objects must automatically increment version numbers on checked in files

5 must provide an automated mechanism to recreate/recover a previous version (individual or component package) must provide an efficient process to store old/archived version Shall provide the following Developer Requirement: must support numerous programming languages including, but not limited to C, C++, Java, FirstLogic, SAP Shall provide the following Approvals/Notifications Requirements: must allow authorized users to approve the progression of changes (either individual components or packages) to the next logical step of the application life cycle must be capable of allowing anyone of a selected group of persons to signoff for a change and must allow for a specific signoff order to occur if desired must allow for approvals to occur at any step in the application life cycle must be capable of sending e mail notifications to users or groups of users via a Micro Soft Outlook e mail system must automatically send e mail notifications to designated individuals or groups about any desired activity 4. Response Content Please answer each of the following. Please use the corresponding number, e.g. 4.1, 4.2 and then your response. 4.1 Please provide your solution pertaining to the above listed requirements. Do NOT include pricing in your response. 4.2 Please provide your pricing methodology for your solution (i.e. your basis for charging), but do NOT include actual pricing in your response. Be sure to include your basis for charging for annual maintenance and training. 4.3 Are you currently on any of the following contracts or any other governmental contract that permits cooperative purchasing? (State of Florida State Term Contract with the Florida Department of Management Services, U.S. Communities Contract, GSA Schedule 70 Contract with a cooperative agreement, etc.) If so, please provide the applicable contract number.

6 5. Submission of Response All responses are due by January 22, 2018 at 5pm EST. Send responses to: Please e mail the response to Michael Weyant at michael.weyant@floridarevenue.com. Label your response RFI #17/ Additional Information 6.1. This is a Request for Information (RFI) and should not be construed as intent, commitment or promise to acquire or purchase the proposed services presented by vendors The Florida Department of Revenue will not be obligated to any vendor as a result of this RFI. The Department is not obligated for any cost incurred by vendors in the preparation of their response to this RFI. The Department will not pay for any information herein requested nor be liable for any costs incurred by the vendor This RFI is being submitted strictly for the purpose of gaining knowledge on services available on the market for the provision of these services, related services, and options available From the information collected through this RFI, the Department will review all information and options related to the services, related services, and desirable options At a later time, it is anticipated that the Department will release our requirement through the formal bidding process or through a certified alternate contract source All information obtained shall become the property of the Department upon receipt and will not be returned. The Department cannot guarantee that it will not be compelled to disclose all or part of any public record under the Florida Sunshine Law In the RFI, the Department has addressed a series of questions to vendors, and request that vendors reply to the Department in the same sequence and format The Department also invites vendors to submit any pertinent information that the Department should consider, including topics that were not included in this RFI but are relative to the same subject area The Department requests that all vendors submit responses that are short, clear, concise and complete Submitting a response to this RFI does not exclude any vendor from submitting a response to a solicitation as a result of the information collected from this RFI.