Fibrinolysis : international journal of fibrinolysis and thrombolysis

Requirements and architectural design specifications can be conflicting and inconsistent, especially during the design period when requirements and architectural design are co-evolving. One reason is that stakeholders do not have up-to-date knowledge of each other's work to fully understand potential conflicts and inconsistencies. Specifications are often documented in a natural language, which also makes it difficult for tracing related information automatically. In this chapter, we introduce a general-purpose ontology that we have developed to address this problem. We demonstrate an implementation of semantic wiki that supports traceability of co-evolving requirements specifications and architecture design

Long range planning : LRP ; international journal of strategic management

Part 4: Software DevelopmentInternational audienceAgile methods continue their growth in popularity. This spreading usage increases the need for adapting agile approaches to specific organizations. Hence, we investigate how system developers engage in the evolution of both agile systems and agile methods in practice. We study adaptation of the agile method Scrum in six organizations. Based on this study we design a framework explaining how agile methods, and in particular Scrum, are constantly articulated and re-articulated when diffused in practice. This framework includes a two-by-two dimensional grouping that includes three classes of fragments: Objects, Organization, and Process. The fourth class involves a discursive articulation that occurs on the same logical plane as the fragments. Unlike method engineering, the discourse is an inseparable part of the methodology itself, not a separate “meta” method