An ameliorated methodology for the design of Product Data Flow Diagram

The Software Requirements Specification (SRS) is prepared by the strategic management of the client organization, after collecting the end users requirements. The developer makes the feasibility study for cost estimation, availability of human & other resources and scope identification in consultation with the client for appropriate modification in the SRS. After the delivery of the software product, the end user is deprived of the modifications made in the SRS and the software architecture of the product as configured to the changing needs of the client. If the software product is used without the Product Data Flow Diagram (PdDFD), the incorporated modifications are invisible to the end users; as a result the product software becomes peripeteia with respect to client's perspective. To avoid this, it is preferable to design PdDFD by the developer. Unfortunately, in the absence of domain knowledge, the developer may not design correct and complete PdDFD. Therefore, there is an urgent need to delink the design task from the domain knowledge. As a sophomore attempt in the design of PdDFD, this paper attempts to develop the automated methodology for the abstraction of the model elements along with their values required for the PdDFD from the SRS. In this design, virtually we have narrowed down the art of defining the usecase, work process & work into engineering. In our proposed research paper, as an intermediate product we have also developed the product Work break down structure (PdWBS). This designed intermediate PdWBS can serve as the base for the design of software architecture. We have also represented the PdDFD in the tabular form without compromising its sensitive nature.