Managing the Iterative Requirements Process in a Multi-national Project Using an Issue Tracker

Prause, Christian R.; Scholten, M.; Zimmermann, Alfred; Reiners, René; Eisenhauer, M.

doi:10.1109/icgse.2008.14

Cited by 8 publications

(5 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many tools available can track all bugs in Web application such as BONTQ [17], Bugzilla [18,19], JIRA [20,21], MANTIS [22], Change Request.com [23] and You Track [24]. These bug-tracking systems track and record all the requests by the users and assists developers or maintainers to manage all the requests.…”

Section: User-centered Technique For Maintenancementioning

confidence: 99%

“…User has to choose the type of requests manually and categorize it based on its version. JIRA [19,20] is a more dynamic tool as compared with other tools, which allows administrator to create, edit and delete requests, projects, user, security privileges and workflow by their own. Other than that, JIRA integrates with FISHEYE [25] and CRUCIBLE [26] in order to track all source code changes.…”

Section: User-centered Technique For Maintenancementioning

confidence: 99%

See 1 more Smart Citation

User-centered technique for managing and tracking modification requests in prototype-based web applications

Kamalzaman

Sulaiman

Syed-Mohamad

2011

2011 Malaysian Conference in Software Engineering

View full text Add to dashboard Cite

Nowadays, a lot of development of Web applications use prototyping approach such as throw-away prototyping and evolutionary prototyping. In order to fulfill the users' requirements, developers need to communicate with the users, therefore prototyping is widely used in software development to assist these developers. As we develop Web application and release them as a number of versions or releases of prototype, it constantly requires changes to evolve and meet users' specific requirements. Thus, prototyping approach may cause more maintenance cost to be incurred due to scope creep during software development. In addition, it provides the challenges to a maintenance team who is mostly not the actual development team, to manage and track maintenance process of such Web applications. This paper proposes a user-centered technique for managing and tracking modification requests in a Web application. We anticipate that the proposed technique can assist maintainers to manage and track modification of a Web application in more effective and efficient manner by capturing, classifying and validating the enhancement requests, problem report and modification requests directly from the users during the prototyping process itself. This in turn will avoid unexpected modification requests once we release the Web application and to allow the tracing of both enhancement and problem report during prototyping and modification requests and problem report during maintenance.

show abstract

Section: User-centered Technique For Maintenancementioning

confidence: 99%

Section: User-centered Technique For Maintenancementioning

confidence: 99%

User-centered technique for managing and tracking modification requests in prototype-based web applications

Kamalzaman

Sulaiman

Syed-Mohamad

2011

2011 Malaysian Conference in Software Engineering

View full text Add to dashboard Cite

show abstract

“…Many EU research projects are subsidized but no concrete goals are defined. The project Hydra, for example, has a sophisticated requirements process [16], and is very successful, yet development is not that requirements-driven as intended in the beginning.…”

Section: B Details On Questions and Answersmentioning

confidence: 99%

“…However, other approaches -like a Jira 3 -based Volere process for distributed requirements engineering -were successfully used in such environments [16]. In general, processes are the result of consensus in a consortium of equitable partners and not established by force of a single higher instance.…”

Section: Introductionmentioning

confidence: 99%

Empirical Study of Tool Support in Highly Distributed Research Projects

Prause

Reiners

Dencheva

2010

2010 5th IEEE International Conference on Global Software Engineering

Self Cite

View full text Add to dashboard Cite

The EU subsidizes research projects in the ICT area with hundreds of millions of Euros per year with the aim of strengthening Europe's global competitiveness. A key requirement of EU projects is the involvement of partners from at least three different countries. This leads to highly distributed software environments where company, country, and culture boundaries run in the midst of tasks like requirements engineering, architectural design, implementation or testing. We present results from an empirical study involving more than 50 transnational, multimillion Euro projects of the Sixth Framework Programme. The results show which tools are accepted by developers and used in practice in the respective phases of the software process. Finally, we shape the idea of Research Software Engineering.

show abstract

“…its planning, monitoring and re-planning, requires coordination artifacts [ 1,33 ] , computerized tools ranging from simple to-do-lists and bulletin boards to advanced enterprise solutions. Among the tools used to aid the coordination of work are issue trackers [ 34,35 ] used in Software Development.…”

Section: Introductionmentioning

confidence: 99%

Supporting Reflection in Software Development with Everyday Working Tools

Krogstie

Divitini

2010

Proceedings of COOP 2010

View full text Add to dashboard Cite

Through their day-to-day usage collaboration tools collect data on the work process. These data can be used to aid participants' retrospective reflection on the process. The paper shows how this can be done in software development project work. Through a case study we demonstrate how retrospective reflection was conducted by use of an industry approach to project retrospectives combined with the examination of historical data in Trac, an issue tracker. The data helped the team reconstruct the project trajectory by aiding the recall of significant events, leading to a shift in the team's perspective on the project. The success of the toolaided retrospective reflection is attributed to its organization as well as the type of historical data examined through the tool and the tool features for navigating the data. These insights can be used to help project teams determine the potential of their tools to aid retrospective reflection. IntroductionSoftware development (SD) is highly cooperative work which has received considerable attention in CSCW [1][2][3] . In SD, mistakes are common as well as costly [ 4 ] , and learning from experience is essential [ 5 ] .In SD organizations using large integrated systems to support and coordinate work, efforts to have the organization learn from experience may be integrated into predefined work processes and supported by tool functionality for collecting and providing experience data. The idea of experience factories [ 6 ] reflects a similar idea. In other settings, as in agile software development [ 7 ] , learning from experience may be more informal and deferred to face-to-face project meetings and retrospective B. Krogstie ( ) and M. Divitini

show abstract

Managing the Iterative Requirements Process in a Multi-national Project Using an Issue Tracker

Cited by 8 publications

References 5 publications

User-centered technique for managing and tracking modification requests in prototype-based web applications

User-centered technique for managing and tracking modification requests in prototype-based web applications

Empirical Study of Tool Support in Highly Distributed Research Projects

Supporting Reflection in Software Development with Everyday Working Tools

Contact Info

Product

Resources

About