Details View - OpenRose - Requirements Management

 

 

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 requirements within this particular project. You can find more information about this small application demo in the Introduction to OpenRose video.

Inside the Details View, I can start navigating further into my project. Let's go into the About of Tariff item type. When I go inside, we see that I am now looking at the item type "About of Tariff" in a read-only view. I can click on "Edit Item Type" to work with the data associated with that item type, or I can cancel out and continue exploring my project.

Within this item type, we have two items that are requirements. This particular requirement has an older account and furthermore has four sub-items. We are currently at level two, considering the Project is level one and the Item Type is level two. Then, at level three, we have two requirements. When I go into one of the level three requirements, I can see four more requirements under it.

Again, when I go into an item, I can see the details about the item in the read-only view. I can click on "Edit Item" to see other details and modify the item. Here, I can change the name, status, priority, severity, description, modify the traceability for the item, and review the history data.

The reason we have this view called the Details View is to allow collaboration between team members and customers. People who are supposed to work and provide input for this requirement work together to define it clearly and precisely. Eliciting the requirements as part of your requirements engineering process involves focused time to work on specific requirements and building well-defined, well-structured requirements.

The second reason is the Tree View can load all project data, which can be overwhelming if you have large amounts of data. You may not want cluttered information on your screen while focusing on specific areas of your project or your initiative. We kept the Details View to allow users to focus on their requirements. We could have called it Focused View, Precision Panel, Insight View, Collaboration Corner, or Brainstorming Bay or Booth, Idea Incubator View, but decided on Details View.

The Details View is important because it loads specific data when we drill into the project, improving the application's overall performance and reducing network usage. Even with slow connectivity, users can work more efficiently with their data in the Details View compared to the Tree View, depending on their project size.

Another reason for keeping the Details View is its ability to work with orphan items. These items are not associated with any project but sit on the side, similar to a recycle bin or in a separate repository container. You can bring these items back into your project. When designing the Details View, our team sought suggestions from a co-pilot and AI engine. We narrowed our choices to the current name after considering various options.

The Details View also allows working with orphan items in the Edit View, showing the full requirement and what we asked the AI and co-pilot engine. We decided to keep the view concept simple and lightweight, settling on the Details View name. The purpose of the Details View is to provide a focused area, reduce network traffic, improve performance, and manage items not yet finalized or associated with a project, termed orphan items.

With that, I conclude this explanation of the Details View. Thank you for your time. We appreciate if you spread the word about the OpenRose application to your colleagues and friends, so they can benefit from this free, open-source requirements management application. 

Thanks again and have a great day!