Baseline Requirements Include and Exclude
Baseline Requirements Include and Exclude
OpenRose - Requirements Management
An Open Source and FREE Requirements Management Application / Tool
Direct Link to YouTube Video : https://www.youtube.com/watch?v=UWvSL5pjYS4
Video Transcript :
Hi, welcome to OpenRose, a free and open-source requirements management application. Get more information at https://github.com/openrose.
Today we are going to talk about including and excluding requirements within the baseline. To learn more about baselining, please look at the Baseline Introduction video.
Let's go to Projects, and there we will connect to our sample project, "Bay St for Personal Customers." This project has a well-structured set of requirements. A baseline is nothing but a snapshot of our data.
Before we take the snapshot of this project, let's have a quick look at the first requirement here, "What's covered by the Tariff," which has a traceability to "Eligibility for Premier Banking." This requirement has a child trace currently available under the second item type, "Account Eligibility and Fees," where we have "Eligibility for Premier Banking." Please remember there is a trace between this requirement as a child and "What's covered by the Tariff" as its parent.
Now let's go and take the baseline for this project. To capture the snapshot, we go to the project itself and then to the baselines. Here, we have two options: Baseline by the project, which takes a baseline of the entire project, or Baseline by item type, which takes a subset of the project data snapshot associated with a particular item type.
Let's create an entire project baseline snapshot and name it "Snapshot 1." You can use different naming conventions for your baseline, depending on the purpose of that baseline, and describe it here. This description is a markdown text box, allowing you to capture formatted text, including bullet points, numbers, bolds, italics, headings, tables, and links.
Click on "Create," and it will create a snapshot for the entire project, "Snapshot 1," and assign it an ID. Snapshots or baselines are always associated with the project, irrespective of whether they are project-based baselines or item type-based baselines.
Let's open this snapshot. You can see the snapshot icon is different from the project icon, and we can see the item types available under that particular snapshot and all the captured requirements. When I go to a particular requirement, you will notice I do not have the option to modify this requirement; it is only in read-only form because it is a snapshot from the project itself. The only thing I can do is include or exclude the requirement inside the baseline.
Let's go to "Account Type." Since it is an individual single requirement without any child requirements below it, it is just sitting at the "Account Eligibility and Fees" item type. If I exclude this, we are clearly indicating that for whatever reason, the project has decided not to deliver "Account Type" in the first snapshot or iteration. It's as simple as clicking on the "Include" or "Exclude" option to remove that particular requirement.
Let's go back to "If You Have an Older Account," which has four children below it. If I exclude the parent, it will exclude all the children. When I go to the child, I cannot include it back into the project unless I include the parent requirement first. When I include the parent requirement, I have two options: I can include only the single parent requirement by clicking on "Include" or I can include all child requirements part of this baseline's requirements breakdown structure.
Let me include only the parent requirement here. The icon changes, indicating it is now included in the baseline, but the four children are not included at this stage. Now I can go back to "Fee Information Document" and include that specific child in the snapshot. This is possible because its immediate parent is included.
Another option is to exclude everything and then click "Include" to add everything back. You can work your way around how you want to use these options. As you can see, the parent and one of the children are included. When I click on "Include All Items," everything is included in the snapshot. That's how you can decide the inclusion and exclusion of data within the snapshot.
You might remember we started this discussion with traceability. Going back to that particular requirement, we can see there's trace data available. The traceability is to "Eligibility for Premier Banking" as a child trace. If I exclude the parent, the trace for that particular requirement is automatically excluded, irrespective of whether they are parent traces or child traces.
Now, let me exclude that requirement in the traceability. You will not see that particular trace because the item or requirement is excluded from the baseline. If I go to "Eligibility for Premier Banking" and check the traceability, I will not see the trace back to "What's covered by the Tariff." The purpose of excluding traceability for excluded items or requirements is to ensure we reduce the scope of the snapshot, as we are not going to deliver or work on that particular requirement.
If I include the main requirement back, we should be able to see in the traceability that the parent is "What's covered by the Tariff." I can show the same information from the other side. If I exclude the child traceability item, I will not see any parent traces, and if I go to the parent itself, I will not see any child traces. Remember, excluding requirements from within the snapshot will also exclude the traceability.
One more important piece of information is that snapshots are data at a particular point in time from the original project or item type. Because we have taken the snapshot and marked it as read-only, we felt it was unnecessary to show all the change history for all the requirements. This would be additional data we would have to capture from the original requirements from the project itself. We thought it was sufficient to show the snapshot as read-only data from the project, so we decided not to include the change log in your requirements.
What I mean by that is, if I go back to the project and look at any item here, if that item has changed, in the change log you will see the information about it. This change history or change log is not available inside the baselining, and the delete item option is also not available for baselining. Instead of deleting items, you can include or exclude requirements from the baseline snapshot.
With that, I would like to conclude this video and say thank you for attending. Please take care and have a great day! Bye-bye.
Document Ref :
Comments
Post a Comment