Introduction to OpenRose - Requirements Management

Watch it on YouTube at : https://www.youtube.com/watch?v=P0x3ZaHg8sA

OpenRose - Requirements Management Application

VIDEO TRANSCRIPT

Hello, and thanks for joining in for the launch of OpenRose, an open-source requirements management application.

The main purpose is to help users and teams "do it right" and ultimately reduce waste. OpenRose is released on GitHub at [github.com/OpenRose](https://github.com/OpenRose). Users can look at the source code and documentation at the same location.

Let me do a quick demo of the application. In this environment, I'm using Windows 11 on a desktop computer, not a server. I have installed IIS and deployed a web deployment package over IIS. When you connect to OpenRose, on the homepage, you will see a welcome message like this: "Welcome to OpenRose." One would start by creating a new project.

For this demo, I've created two separate projects. The first project is a small example of how I converted a document published by a bank called Bays. They released new tariff plans for customers and updated tariff details. This project demonstrates how Bays would capture necessary information from different teams and departments to produce the ultimate guide about the updated tariff.

When I go into the project details view, you can see the actual public document published by Bays. The document outlines the updated tariff contract, account eligibility, fees, debit card charges, borrowing options, and more. The internal initiative at Barclays required different teams to provide input on the tariff, review it, negotiate, and finalize the document for customers. OpenRose could come in handy here by capturing these requirements and information.

In OpenRose, I created a project called "Bays Tariff for Personal Customers" and converted key topics into item types. Inside a project, you have item types, and within each item type, you have individual items representing requirements. For example, "Account Eligibility and Fees" is an item type, and within it, there are items like "Account Type Eligibility for Premier Banking" and "Eligibility and Fee for Barclays Rewards." This structuring helps capture requirements in a nested hierarchy.

In the detail view, you can see the table similar to the public document, capturing information from contributors. Users can edit items to update details like name, status, priority, severity, and description. The information can also be visualized in a tree view, allowing easy navigation through the project data.

OpenRose also offers a feature to link data between items, such as linking a requirement about tariff coverage to eligibility for Premier Banking. Users can create new items, update existing ones, and track changes in the change log. Items can be moved around within the repository, and baselines (snapshots at given points in time) can be captured.

OpenRose is built using .NET, Entity Framework Core, and SQL Server. It can be deployed as an EXE application, on IIS, or in the cloud. The open-source nature of OpenRose allows users to decide where to store their data, ensuring it stays within their control, whether locally or within a corporate network.

In summary, OpenRose is a simple, lightweight requirements management application that aims to help users manage their requirements effectively while reducing waste. We appreciate your time and participation in spreading the word about this open-source initiative.

Thank you for your time today, and have a great day!