The transformation of gobbledygook into a specification of requirements

  • Easy
  • 40 min

Let's talk about attracting a system analyst to non-system tasks of product development.

Situation. A business has an idea. It is not possible to convey the idea directly to developers in the language of business. It's like a blind man talking to a deaf man. An arbitrary system analyst is pulled out: a specification of development requirements is needed. At the entrance — a quarter of a page of text with incomprehensible terminology. Is it possible to formulate requirements without diving into the subject area? 

Let's look at a few simple steps that will allow you to turn several paragraphs of arbitrary text into a document that you are not ashamed to give to the developer.

Comments ({{Comments.length}} )
  • {{comment.AuthorFullName}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

Chat with us, we are online!