The document discusses the evolutionary architecture and design approach taken for the CIS (Corporate Information System) application developed by Pragati Software. It describes how the architecture and design were incrementally implemented and refined over multiple sprints through story implementation and refactoring. This allowed the architecture to evolve based on real requirements rather than being pre-defined, reducing risks while delivering value to customers early. Key principles included envisioning architecture needs early but evolving them over time through real code and refactoring.

4. About Pragati Software Bangalore Chennai Hyderabad Mumbai Pune Ahmedabad Vadodara New Delhi Shimla Bhopal Kolkata Thiruvananthapuram

13. Cross-Cutting Requirement: Change History

14. Cross-Cutting Requirement: Change History

18. Form-Centric Design Form_load: fetch data from Cities table populate the grid New_click: display blank entry form //…on return from the entry form re-populate the grid from Cities table etc. OK_click: validate data INSERT into Cities values … exit form etc.

20. Layered Architecture D A T A B A S E

22. Distributed Architecture D A T A B A S E

25. Second Story: Companies

26. Framework Evolution

27. Framework Evolution Common behavior in the framework’s classes (such as UIManager), with hook methods for story-specific implementation.

34. Architecture and Design Evolution

39. Thank You