What formal methods do IT companies use to document their product development.
For example, in early days, there was the Unified Modelling Language, consisting of Sequence diagram, Activity diagram, Class Diagram, State diagram and so on...
In this Agile world, with minimal documentation and frequent iterations, how does a Product manager manages documenting the final software product that is developed. For instance, if the product maintenance is to be awarded to a different organization that the one which developed, what piece of document does the original organization share with the new one with respect to the employees getting to know about every functionality of the product.
I understand for relational and big databases, there is still a practice of using Entity-Relationship diagram for Relational and Data flow diagram for Big data. However, what about programming?
How do companies document various Object oriented program codes and front end scripting or some ETL code written in PL/SQL or java...how do they manage to document the same in this fast agile environment?
An insight would be really wonderful! Thanks!
[link] [comments]
from IT https://ift.tt/37nNVgz
No comments: