Raise your level of abstraction
This is my first time post.
When I make the Requirement Specification , then I often use Use Case diagram, Use Case Description(I often use Sequence Diagram) ,State Machine Diagram, and more.
But, many people make the Requirement Specification by Natural Language.
And, they share that in Wiki.
# Of course, the tool used by the development domain is different.
They want to change that, they can change that in web from anywhere.
And they can attach screen images.
They can share the application image.
But, there are a lot of probrems of writing specification by natural language.
For example, vagueness...
I think that the Model (ex.UML) as the communications tool and the model by whom the computer is processed might be fundamentally different.
The model as communication tool might be expected that everybody can edit anytime, anywhere and everybody can attach the screen image like wiki.
Are not I and people want the mechanism of it converting it from the model as the communications tool to a formal model(processed by computer)?
I don't know English very well.(this is excuse)
Please question me if you do not understand.
Add a Comment