Several members are involved in development and management of the Distributed Software Projects. Each member needs to know the responsibilities of each other for proper management of the activities of such distributed projects to produce coherent outcomes. Distribution middleware software has higher-level distributed programming models whose reusable APIs (application programming interface) and components automate and extend native operating system capabilities. Software management tools like Work breakdown structure (WBS), Gantt chart, Critical Path Method, and Critical Chain Method etc. does not fully help the managers to manage the member's responsibilities during the development of distributed applications. The layered architecture can help to do so. This style not only gives the layer level description of the activity involved, it also defines and directs the group of workforce. By listing the groups of workforce, the development team as well as the customer can know the activity and the member involved to work on those specific activities. This layered architecture is much benefited to development team and also to numbers of stakeholder of the large distributed project. The extended new approach of layer pattern with 'Responsibility Index' adds extra value to manage all the members' responsibilities. Managers, stakeholders and others can have an easy management system. The request or complaint from the customer can be passed to appropriate team without much delay. Most importantly this will give facility to collect timely feedback from all levels of customers.