1

Topic: How to organize the knowledge base on to functions and project business rules?

Came to the new company, to me analysts in it were not, requirements were considered orally and not fixed in any way. Told to write the document with the description of features of the project (hierarchy of the user functions, in other words) that further it was possible to see at arguing of a new functional before eyes existing (to see conflicts ). I decided to make  with hierarchy of functions, communicated with  and  the manager, pulled out from them tons of the facts on hierarchy  functions and business rules on which they work. As that it is necessary to organize these facts in the knowledge base. I think if to thrust this all in one  (and  functions, and business rules) - there will be a porridge. If to mark business rules as that (cloudlets-comments) to features - whether it it will be evident enough? Can eat any best method it to implement in the form of one document?

2

Re: How to organize the knowledge base on to functions and project business rules?

Hello, opposer, you wrote: O> Told to write the document with the description of features of the project (hierarchy of the user functions, in other words) that further it was possible to see at arguing of a new functional before eyes existing (to see conflicts ). I decided to make  with hierarchy of functions, communicated with  and  the manager, pulled out from them tons of the facts on hierarchy  functions and business rules on which they work.  to reveal the user functions, it is necessary to speak not so much with the technical principal (is responsible for technical implementation) or the manager (is responsible  and the budget), how many with the ultimate user. O> if to mark business rules as that (cloudlets-comments) to features - whether it it will be evident enough? Begin with creation of normal hierarchy Feature - Sub-Feature - Sub-Feature Element. I think, at the first stage of it will be enough.