Software Requirements Management

Last published posts

Mobile Application Testing: 10 Steps Approach
Posted on

Mobile application testing is crucial in order to create a reliable product. In this post, we’ll go over the entire testing process step-by-step. Testing is a crucial part of the mobile application lifecycle. However, due to all the time and effort, it takes to complete the full cycle of app testing, it gets overlooked by…
Read more…

Real Agile Approach to Performance Testing
Posted on

Performance testing helps to determine if a system is reliable and comfortable to use. In this post, we’ll explain the main principles of Agile performance testing as well as its benefits. Before launching an app or a website, it’s crucial for a developer and admin to know how the entire system behaves under stressful situations….
Read more…

THE MAIN ESSENCE OF DEVOPS
Posted on

In the development and delivery of software, the most important contribution of DevOps is the elimination of the time lag between project phases: development, testing, trial operation, and delivery of the product to the final consumer. The time2market indicator is one of the key indicators of the competitiveness of products and the success of companies…
Read more…

SOFTWARE REQUIREMENTS MANAGEMENT

General Information

Software requirements management is a process that includes the identification, documentation, analysis, tracking, requirements prioritization, reaching an agreement on requirements, change management, and notification of the interested parties.

The organization of the requirements management process allows us to provide documentation and requirements control as well as implementation in accordance to the customer’s expectations.

Problems it will solve

  1. Minimizing the risks of defects in new software functionality or its noncompliance with the expectations of the customer;
  2. Cutting the operational costs during the implementation of the new releases or system updates by minimizing the number of change iterations or corrections to the implemented functionality;
  3. Cutting down the time frames for system implementation (time-to-market) or its new functionality by implementing system functionality in accordance to the initial customer requirements;
  4. Cutting down the time frames for the analysis of the effect that changes may have on the current system’s functionality;
  5. Raising the effectiveness of managing business expectations through a more precise release launch; and
  6. Raising software quality by implementing centralized requirements storage, managing all changes, and conducting a risk analysis during the implementation of new requirements.

Deliverables

  1. A deployed and tuned Software Requirements Management System.
  2. Regulations for requirements management that contain:
    • The roles and responsibilities of the process participants and
    • The working order with the Software Requirements Management System.
  3. Implementation plan (MS Project)

Scope of work for the requirements management process organization project

  1. Analysis
    • Determine all participants for the current requirements management process, their roles, and approach to working with requirements;
    • Determine criteria for choosing software management testing tools;
    • Determine requirements for the management tool and infrastructure; and
    • Coordinate the choosing of the tool with the customer.
  2. Execution
    • Prepare the regulations for the software requirements management;
    • Implement the requirements management tool;
    • Customize the requirements management tool; and
    • Educate customer’s employees to work with tool
  3. Pilot launch
    • A trial launch of the new requirements management process for the first system;
    • Analysis of the pilot launch, discovery of weaknesses in the process; and
    • Customization of the tools, processes, and changing the working regulations.
  4. Implementation of the requirements management process for all systems

Tools and licences

We might use following tools and licences during the project:

  • HP ALM (HP Application Lifecycle Management, HP Quality center)
  • TFS (Team Foundation Server)
  • TestLink + JIRA
  • TestLink + Readmine