Move Requirements


 

Move Requirements

OpenRose - Requirements Management

An Open Source and FREE Requirements Management Application / Tool

Direct Link to YouTube Video : https://www.youtube.com/watch?v=MOhYURQqne8

Video Transcript :

Hello and welcome to OpenRose, an open-source requirements management application. You can find more information about it at https://github.com/openrose.

Today we are going to look into moving items or moving requirements. Let me start by going to the project list and showing you an example project, which is "Barclay's Tariff of Personal Customer." Barclays Bank has released a public document explaining tariffs for personal customers, and I have used that document to convert it into a requirement structure here as an example.

Let me show you that we have several requirements captured in a nice structured way. If I want to move one of those requirements, such as "What's Covered by Tariff," I can take the source requirement's ID, open the "Move Items Under" option using control-click, which will open it in a different tab. There, I will provide the ID of the source item and the ID of the target item. Since I'm moving it under, it will become a child of the target item. The target item could be a requirement within the project, across different projects, or an item type.

I want to move "What's Covered by Tariff" under "Account Eligibility and Fees" and place it at the bottom of the existing list or top of the existing list, which is the option I will select. Since I want to move it under this item type, I will pick up the ID of that item type as my target and provide the target item type ID. Then, I will say move it to the top of the existing list of children, which means it will go to this location. When I do the move, I get confirmation that the move was successful. Let me refresh my view, and we should see that "What's Covered by Tariff" is at the top location under "Account Eligibility and Fees."

Similarly, I can move it back to its original location. Let's take that ID again and quickly move it back to its original location. Again, I will select "At the Top" in that item type. When I go back and refresh my Treeview, it should be back in its original location.

The second option is to move the entire hierarchy. I can select, let's say, this item currently at the bottom of the list of "Debit Card Charges." This is "Charges in the UK and Abroad," and it has a nice structure. Let's take this parent item along with all its child items. I will select the ID of the parent item and say I want to move that item over to "Account Eligibility and Fees" at the bottom. I will go back to the "Account Eligibility and Fees" ID and select "At the Bottom" of the child list, which means after "Fee Declaration."

When I do that move, I get confirmation that it has successfully moved. If I refresh the view, we should see "Charges in the UK and Abroad" has moved into "Account Eligibility and Fees" at the bottom along with all its children. Again, let's move it back to its original place. I will use the same ID as my source, and my target will be "Debit Card Charges." I will select "At the Bottom," then refresh my view, and you can see that the item has gone back to its original location.

Another thing I can do is move these items into a different project altogether. To do that, let me first go to the Project List view and create a dummy project. It will be a dummy project with the status "New" and "Dummy" as its description. It's the new project I just created. When I go to the Treeview for that project, I can see the Parking Lot item type is already there. I will create a new item type called "Dummy Item Type" and save that detail. This is the ID of that dummy item type. Let's refresh this view, and that's where we can see the dummy item type.

I would like to move the item "If You Have an Older Account" with four children. I will select that item, and this time, in the target, I will use the dummy project and the dummy item type. That's the ID I have copied. It doesn't matter if I select the top or the bottom of the child list, as there are no children. When I refresh the target project, I will see the data here, and when I go back to my original project, that data is gone from Bay's project.

Let's bring it back into Bay's project. Going back to the dummy project, I will select that ID and use it as my source ID back to Bay's project under this item type. I am moving in the target item type at the bottom. You can easily move multiple records, including hierarchical records, in one shot from one project to another.

Another thing I wanted to demonstrate is the ability to move items using the Details view. If I go to my requirement details view, I can see this data in this format and order: "Older Accounts," "Rates for Savers," "Fee Information Document," and "Declaration." I can use the up and down buttons to reorder requirements at that level within the Details view. This is another way to move records up and down within a given level and reorder them within the tree.

Finally, let me show you that in my Barclay's project, if I go back to the Treeview under the Parking Lot item type, I can create a few items here. I'm just creating some structure, and you can see some items and siblings are created. Maybe a few more child records as well. This is the new structure I just created. Now, I would like to delete all this data. If I delete the parent record here, it will by default delete all its children—14 records in total—permanently from the repository.

However, we can take the top item, select the ID in the Details view, and move that source record into my target project, dummy. Since the dummy project doesn't have any data, I will move it to the dummy item type or parking lot within the dummy project. All 14 records are now gone over to this dummy project. We can see them here. When I delete the project itself via the Details view, it confirms whether I want to delete the dummy project. If I say yes, all those 14 records are now gone as orphan items. They don't have the same hierarchy as in the dummy project, but the records are still available.

I can pick up one of those records, open the record to see the details, copy the record ID, and move a single record into our project, say Bay's. I will move it into the Parking Lot here. Let me take the Parking Lot ID as my target, and then I can say move it to the top of the Parking Lot.


Now, with that, if I go back, refresh my view, and go right to the bottom of the Parking Lot, we can see the new item at the top location within the Parking Lot item type. So, you are able to bring back data from orphaned items into a given project, which means my orphan items will now go down to 13 records.

Another option I have is to permanently delete all the data from orphaned items. This is something we will cover in a future video. To conclude this video, I would like to say that moving items is very simple, allowing you to move items under a specific location.

In fact, we forgot to have a look at the "Move Items Between" option. Let me go back into my Barclays project. I would like to take the fee information, which is right in the middle of these records. Let me take the ID of that, and this time, I'm going to move it between.

"Move Between" works by allowing the source item to be moved to target items that have siblings. This means I can move it between these two records, or these two records, or perhaps these two records here. I cannot move it below this particular record because it doesn't have a second sibling—it has a sibling as a previous item. I have to select "Replacement Debit Card Charges" as my first item, which will automatically select "Charges in the UK and Abroad" as my second item.

In this case, let's move the fee information document in between "Replacement Debit Card Charges" and "Charges in the UK and Abroad." Let's take the ID of "Replacement Debit Card Charges" and select that as the first item. It will automatically select "Charges in the UK and Abroad" as the second item. Ultimately, it will move the fee information document between these two records. Let's click "OK," and we should now see that change here.

You can see the fee information document has been moved between "Replacement Debit Card Charges" and "Charges in the UK and Abroad." That's moving an item in between existing records.

Let me move this back to its original location. So, the source is my first item, and my target would be this because it needs to go in between "Rate for Savers" and "Declaration." Let me take that as my first item ID, and the second is automatically selected. Click on "OK" to move it back to its original location.

When I move the data, here I'm just selecting one item, but if I moved "If You Have an Older Account" in between "Replacement Debit Card Charges" and "Charges in the UK and Abroad," it would move all five records, including its hierarchy.

Now we can conclude this video, where I was just showing how requirements can be moved between projects, between work item types, up and down within its own hierarchical level, across orphan items, and back from orphan items into the project.

Thank you so much for listening. I appreciate any feedback you may have. Please share the link with others who can benefit from this free requirements management application called OpenRose. Thanks again and have a great day!

Document Ref : 



Comments

Post a Comment

Popular posts from this blog

Introduction to OpenRose - Requirements Management

Image
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 b...
Read more

What is Requirement?

Image
What is Requirement? OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=3qQzKbfvRPA Video Transcript :   Hi, welcome to OpenRose, an open-source and free requirements management application. Please visit https://github.com/openrose for more information. Let's go to the project dashboard, and this time, let's open a deep hierarchical level project. This is just a demo project, so when I open that project in the TreeView and start expanding the project, I can see some sample item types along with a Parking Lot, which is the system item type. Inside item type one, I have a top-level item, then item one and item two, which are broken down into further items. You can see I've given the names which indicate a kind of logical hierarchical structure in the name. Here, you can see L1, L2, L3, L4—that's the level. The project is considered as level one, and item ...
Read more

Details View - OpenRose - Requirements Management

Image
    Details View OpenRose - Requirements Management An Open Source and FREE Requirements Management Application / Tool Direct Link to YouTube Video : https://www.youtube.com/watch?v=FC67o7lUy3I Video Transcript : Hello. OpenRose is a requirements management application, which is freely available and published on GitHub. Simply go to github.com/openrose to find more. Today, we will discuss the Details View. When you go into the Projects section where you can see your list of projects, there are two main views: the Tree View and the Details View. When I click on Details View, I enter the project one level at a time, or I exit the project one level at a time. Inside the project, we know that there are item types. In this particular view, we can see that I have a parking lot, which is a system item type, and four other item types that I have created. This is a public document published by Barkley's Bank, which I have tried converting into some sort of specification or requirem...
Read more