1) Design Phase: – This is very important and critical phase of the SDLC cycle. Because we are going to build new software, so we need the base very strong to handle all the problems at the same time. For that we have to have the unique design for solving the multiple tasks with it. It becomes really crucial for us to have the best design as per the requirement. As an Architect we are going to do the analysis for the design like “What we are have in the database at present similar to our requirements. If we are having something similar to our requirements then we don’t need to create all the new structure. We can leverage something with the existing database. If we are not having anything related to our requirements then we are going to create the new database structure to store the data for the new projects and process. As an Architect we are responsible to create the best design and solutions for the multiple problems. We are responsible for creating the documentation and Data Model for the each component of the requirements. We are going to create the Data Flow Diagram (DFD), Data Model, Architect Approach Document (AAD), Technical Design Document (TDD) and then support to testing environment. Data Flow Diagrams are really helpful for us to understand the overview of the requirement for the given project. This is always done by the System Architect and Database Architect. Then we have to have some discussion on the Architect Approach and Data Flow to get close to the requirements in details. Then we are start working on the Data Model also known as Entity Relationship Diagram (E-R). This E/R diagram is really important for us to get the idea “How we are going to take care of the all the data required for this process. After creating the data model we are responsible for the creating the documents for the supporting the table and columns to define the values and purpose of the table and columns. Then in more detail we have to specify that what changes we need to be done in this project is always written in the Technical Design Document. Then we should change the Data Model and AAD and TDD after the review with all the team members from management side, database team and QA team as well.

2) Developing Phase:- After the design phase it comes the developing phase, in which actual we have to do the changes into the existing and the new table and columns. We are responsible for the creating the new tables and columns, we can add more columns to the existing database to accommodate the possibility of all the requirements. In this phase we have to take the guidance of the Architect to start doing the right things in the right direction. If we are having doubts in the design, then we can consult with the people around us in the project team. We can check with BSA (Business System Analyst) and Architect as well. Then we are responsible to give the support to Quality Assurance team for the projects. If we are getting feedback from the testing team then we are good to solve the problems before going into the production environment and live. We have to create a release note for the changes done during the developing the processes and procedures. Then it will get deployed into testing environment. In testing we are going to test all the changes.

Thanks to everyone for reading this article. Please send us the comments on this article for the better performance and ease of handling it and launching it into the market.

Thanks,
Sandeep Rajmail