by
10 years ago
 

Links between work items and their intended meaning

One of the great things in Polarion is the possibility to link all kind of artefacts and work items together. As a result you are able to trace the impact of a change request down to the changes you made in the source code. However links can be used in different ways and for various reasons. In this blog I want to give an overview about the links provided by Polarion and how they are intended to be used.

Has parent / is parent of

The link should always point from child to parent. You should always use that type of link when you have a refinement situation. Typical scenario is the refinement of customer requirements. At the beginning you have general requirements which are refined over time. Derived requirements are linked as child requirements to the parent requirement


Has parent link in treeview


Has parent link in workitem editor

Depends on / is dependent on

Use this type of link if you want to express that one item can only start when the other item has been finished. Typically you will have that type of relationship between tasks. The link should always point from a task to the task it depends on.

Duplicates / is duplicated by

Sometimes work items are entered in the system twice as people sometimes tend to forget to perform a search first to check weather the bug or requirement already exists in the system. In this cases you can close the duplicated item at once indicating by a link that it duplicates the item that was already in the system. Link should point from item the item you close because of duplication to the item that is still open.

In some situation you have some features that are not completely finished but lets say 80% done. However the current functionality can be released and works. In these cases it would not be correct just to close the item representing the feature as not 100% of it was implemented. A good way out of that dilemma is creating a follow up item that indicates the missing 20% of the feature. By doing this you can make sure that you won’t forget the missing functionality in future releases. The link should point from the closed item to the follow-up item


Is follow-up link

Relates to / is related to

Use that link when you want to express a generic relationship between two items. In requirements management you have very often situation in which requirements have dependencies (no refinements as mentioned above in parent link) to other requirements.

Rule of thumb: Use the link when none of the other relationships can be applied

Implements / is implemented by

At some point of time somebody has to do the work. Usually you will end up with a bunch of work packages represented by tasks in the system. To give the assignee of the task as much information as easy available as possible you should link the task to the corresponding input element. Tasks are normally linked to following input elements:requirements, change requests, bugs or features. The link should pint from the task to the input element.


Is implemented by link

Stay tuned for upcoming blogs on linking and planning

by
10 years ago
 

Polarion SVN 2.6.5 Linux Installers Available

We have released new platform-specific Linux installers for Polarion for Subversion v. 2.6.5. Automated interactive installers are now available for:

  • Red Hat/Fedora Core
  • Debian
  • SuSE

(We had previously released an interactive installer for Windows®, and a generic Linux installation archive for manual Linux installations.)

The new installers are suitable for new installations, or for upgrading from version 2.6.0 to version 2.6.5.

You can download any of the available installers/archives at http://www.polarion.com/downloads.php#sub. Click the link Login & Download and user your polarion.com account credentials (or register for a new account). All downloaders automatically receive an evaluation license by e-mail.

If you have questions regarding the new installers please e-mail
support@polarion.com

by
10 years ago
 

Subversive page is live at eclipse.org

Some weeks before the Polarion weblog was launched, Subversive, our open source client plugin for Subversion, was accepted as an Eclipse project. The project is now in the incubation phase, and may one day become part of the standard Eclipse distribution.

In case you haven’t yet heard, the Subversive project page is now live on the Eclipse web site at http://www.eclipse.org/subversive/ and you can keep tabs on its progress there. You can contribute to the project through discussions, or become a committer if you are so inclined.

For those who may not be familiar with Subversive, in addition to functioning as a Subversion client plugin for Eclipse, it is also bundled with FastTrack – our free tracker pugin for Eclipse which provides both stand-alone tracking and basic collaboration features using Subversion, and can also serve as an Eclipse client for our next-generation ALM platform, Polarion for Subversion.

by
10 years ago
 

Open source Subversion training materials launched

SubTrain LogoWe are pleased and excited to offer the industry’s first open source training materials for Subversion through the new SubTrain project on the Polarion Community website.

If your organization is thinking about rolling out Subversion (or if it has recently done so), or if you are a professional trainer, now you don’t have to reinvent the wheel when it comes to training users on Subversion. The free, open-source SubTrain course provides a set of PowerPoint slides, plus exercises, “cheat sheets” and more which you are free to reuse and customize. You can also contribute additional materials and or improvements to the existing materials.

We think the open source concept applied to training materials is an exciting new idea and we hope that you will find it beneficial. So hop on over the the Polarion Community and check out SubTrain!

SubTrain Slide Sample

More info at polarion.com…

by
10 years ago
 

Workflow: recording status change dates

This new feature of Polarion 2.6.5 lets users to store important process information: the dates when work items change their workflow status. This information is always available in Polarion, but now we have the opportunity to easily use this data.

For example Polarion users can export status change dates to MS Word documents to highlight the evidence, important for quality processes, of the acceptance of work items (i.e. Requirement or Problem Report). Or we can export such information in MS Excel sheets and use it to audit/measure the time performances of some activities (i.e. how much time elapsed between creating a bug and fixing it).

How it works

The status change dates will be stored in specific custom field(s) of each individual item. So, first of all we have to define the custom fields where we would have dates stored.

For example, we are working on Defect item type and we would like to store the resolution dates.

Custom field definition:

Administration perspective: [select project] : Work Items > Custom Fields topic

Download the defect-custom-fields.xml file and add the following element:

<field id="resolutionDate"
type="date-time"
name="Resolution Date"
description=""/>

Upload the modified configuration file back to Polarion. Then we can go on to define the workflow for the Defect item type

Workflow definition:

Using the Web Interface in the Administration Perspective choose topic Work Items/Workflow and create a new workflow definition specific for the Defect Work Item Type (click Create in the Actions column).

Find the Actions table and for action to resolve click on the check icon in the last column on right side (labeled Actions).

Now we should have a new pop-up dialog like this one:

workflow dialog action  resolve

In the Function dropdown menu select the FieldValueChange option and click the plus icon and then the check again.
Now we have the Parameters dialog where we have to specify following values:

workflow dialog action resolve parameter

So after closing the two dialogs and saving changes on the main workflow design page we should have the new workflow definition configuration file defect-workflow.xml

Here the fragment of the file with the new function defined:

    <functions>
        <function name="FieldValueChange">
            <param name="field.name" value="resolutionDate"/>
            <param name="field.value.type" value="current.date"/>
        </function>
    </functions>

Now clear the system caches (Administration : Repository, Topic: System > Caches ) and go to try the result of your work!

Note that this new feature is a nice and generic function that we can find implemented out of the box; now, in Polarion 2.6.5, you can also design and implement your own custom functions that could be invoked during workflow transitions!

Custom code invocation in workflow transitions is a very advanced topic, and if you like, we will write some notes on that here on this blog!

In this part of the article we have seen how to record workflow status changes, in the second part we will show how to use these data. Stay tuned.

by
10 years ago
 

Polarion Live Approach Presentation at ALM Expo Web Conference

ALM Expo Webcast 2007

In the last few years, some of the most widely adopted best practices from Software Engineering, especially the adoption and refinement of Agile methods, have significantly reduced software development risk and increased project success rates.

ALM is the next, state-of-the-art proposition in the software development tools market also significantly increasing project success rates. It offers broad support to people covering different roles in software development, deep feature sets for each of them and integrated functionalities. But, so far, most ALM tools aren’t really agile. They support different roles with different tools having different processes; integrations do batch transport of information from one repository to another, preventing instant notifications of change; and, can overshadow team interchangeability through forced project role specialization.

The Live Approach can solve the problem of integrating Agile development teams into a wider company/corporate infrastructure by providing developers with Live and Available access to the wider corporate information via the tools they prefer and need to use, and not add extra work or ”processes.” The Live Approach is a set of guidelines designed to define a roadmap for software development environments and tools to make them open to support different development methods with a higher degree of usability, and able to provide “live” information about project status.

Our own Stefano Rizzo will be showing how the ability to mix the benefits of Agile software development and more formal requirements management, planning and governance methods of the Live Approach opens new directions in creating Live methodologies and tools to support the needs of different business sectors. One attendee to this webcast will receive an iPod nano!

Wednesday, May 2, 2007
12 noon PDT | 3 pm EDT | 8 pm GMT

Registration is FREE but you do need to register to attend the webcast. REGISTER NOW

by
10 years ago
 

FastTrack and Subversive Updates Released

We have released new versions of Subversive, our open source Subversion client for Eclipse, and FastTrack, our free tracker plugin for Eclipse (which includes the Subversive update). The newly released versions of the tools support different Eclipse versions.

Downloads for Eclipse 3.2:
FastTrack version 1.1.0
Subversive version 1.1.0:
   » Update site
   » Archived Update Site and Source Code downloads

Downloads for Eclipse 3.0 – 3.1
FastTrack version 1.0.4:
Subversive version 1.0.4

by
10 years ago
 

And we have a winner!

We are pleased to announce the lucky winner in the recently closed Discover Polarion survey and giveaway. Congratulations to Tsvetelina Kovacheva, winner of a new Apple iPod. Tsvetelina, of Sofia, Bulgaria, is a software quality manager. When asked what she particularly likes about Polarion for Subversion, Tsvetelina told us:

“The strength of Polarion is achievement of an integrated unified platform from requirements, across development, to project management.”

Thanks, Tsvetelina, and thanks to all who participated in the survey. We plan to have another one, with another opportunity to win a nice prize, following the next major release of Polarion for Subversion – which of course will be announced here, so stay tuned to the Polarion blog!

by
10 years ago
 

Welcome to the new Polarion weblog

The new Polarion weblog and its associated RSS feeds is your “single source” for news and information about all things Polarion.

Here is where we’ll announce everything from product releases and updates, to events of possible interest. The Technical Support team will also post bulletins about any issues of wide interest that may arise. Look for posts in the Support Bulletinse category. Additionally, the guys from the Professional Services team will be posting practical tips, tricks, and how-to articles from time to time. Look for posts in the Tips, Tricks, How-To category.

For the time being, comments are allowed, but are moderated. This is a new endeavor for us and have limited moderation resources, so we’re going to see how it works out.

If you currently subscribe to any of the existing Polarion RSS feeds, these are being discontinued – please subscribe to the weblog’s RSS.

Thanks for stopping by and checking out the new blog. We hope you will find it a useful source of information