There are various ways in which stakeholders perceive the software development process and product life cycle. Views are ways of categorizing or labeling these different perspectives. The most software development life-cycles do not bring architecture view to the forefront as they do requirements, design, implementation, and testing. This paper proposes the role of architectural view in software development life- cycle and why they are important to bring it forefront in design life- cycle. This paper also proposes the proposed architecture view in software development life-cycle. The views may appear to be processes from the point of view of individual stakeholders. When synthesized, they form a coherent view of the entire software life cycle. A software architect will need to understand these views in order to work within them and communicate activities within these views. Our approach defines the newly added phase in architectural view and the related result.