Similar Posts
Tracing the Rationale Behind UML Model Change Through Argumentation
Neglecting traceability—i.e., the ability to describe and follow the life of a requirement—is known to entail misunderstanding and miscommunication, leading to the engineering of poor quality systems. Following the simple principles that (a) changes to UML model instances ought be justified to the stakeholders, (b) justification should proceed in a structured manner to ensure rigor…
When (if ever) Is a Claim Objective?
“Objective”, as in, for example, “what I’m saying is objective”, or “that statement is objective”, or “we need objective criteria when making these decisions”, is a complicated term. It takes a lot of effort to make sure it is understood as intended (or closely enough). It is therefore a costly word to use. Why is…
Dynamic Requirements Specification for Adaptable and Open Service-Oriented Systems
It is not feasible to engineer requirements for adaptable and open service-oriented systems (AOSS) by specifying stakeholders’ expectations in detail during system development. Openness and adaptability allow new services to appear at runtime so that ways in, and degrees to which the initial functional and nonfunctional requirements will be satisfied may vary at runtime. To…
Speed vs Uncertainty
Figures 1 and 2 show cost versus time; Figure 1 shows long iterations, Figure 2 short iterations. We choose to do something at time zero, at the origin of the graph in the Figure, and when we do so, we do it under some assumptions that we made at that time. Dashed red lines convey…