Tag Info

New answers tagged

0

(I assume, you do not mean "in Agile", but more specifically "in Scrum" - otherwise asking for "what is the formal method" does not make much sense). If the change is so essential that the work on the sprint, as it was planned, becomes nonsensical, the product owner should cancel the current sprint and initiate a new one (see, for example, here). Of ...


1

Generally, the product owner would create a new story that describe new requirements and you would estimate and prioritize the new story as any other story.


0

Don't outright say no as that would hurt his feelings. Just make it clear that due to technology constraints that 60% of the time it will work every time. And once he realises the impracticality and cost involved in such an undertaking, suggest a more practical approach within his budget such as having a setting that allows you to change text size. And the ...


1

I will say that it's not limited to functional programming, it's more related to the goal of the project. By using predicate logic (higher order logic) you can create prove for the logic used in the requirement. Translating the logic into functional languages is probably easier. It's also possible to then translate the proven functional language ...


-1

That's one way to deal with functional programming. It tends to fall out from the flowcharts and data flow diagrams of the "old days." Instead of thinking in terms of objects, functional programming tends to focus on what actions need to be performed. The data becomes incidental, bits of fluff to carry along to hold on to what you're trying to do.


0

In my research, I have found Specifications to be used for patents and House Construction (as part of a contract). The definition of a requirement from Webster's Unabridged Dictionary (3rd New Int'l Ed.) is: a) something that is wanted or needed: Necessity b) something called for or demanded: a requisite or essential condition: a required quality, ...


1

Non-Functional requirements and Quality Attributes are one and the same The idea behind the name change in recent times is that, these so called non-functional requirements are in fact system functionality (or a set of system functionality) that has a cross-cut impact in the system. Meaning, the transversal impact that this kind of "special functionality" ...



Top 50 recent answers are included