About the first post of this blog, I want to add something:
the correct description of the problem in correct language (formal) can often be the solution .
Let's talk about software requirements are a representation of the problem, but also the design is a representation of the problem. This is because it describes (in detail, it is hoped) the domain of the problem to be solved, giving the actors and relationships. Where the requirements document is a passive description of the problem, it is a description of the design on.
software emerges from a description (and thus, by an understanding) more and more of the problem to be solved.
Ahh, what a beautiful post.
then I look around ...
0 comments:
Post a Comment