Client Interaction. Ravichandran Client Client Client Interaction. Client Interaction. Interaction. Perform analysis Interaction. Role: Analyze system Requirements Make sure the Perform analysis of game features Perform analysis architecture used architecture of prototype to to ensure of game features Engineer, UML in previous games design meets ensure adherence adherence to to ensure Modeler built by client. specified to stakeholder stakeholder win adherence to Capture requirements. win conditions. conditions. stakeholder win requirements of conditions. Secondary Secondary Secondary new game. Responsibility Responsibility Responsibility Secondary Negotiate win- Work with Ensure prototype Ensure game Responsibility conditions with system architect adheres to UML features adhere to Ensure game stakeholders. and develop diagrams UML diagrams features adhere Secondary UML diagrams. designed earlier. designed earlier. to UML Responsibility Help build diagrams Provide feasibility design assets. designed earlier. evidence for gathered requirements. Name: Primary Primary Primary Primary Primary John Leibowitz Responsibility Responsibility Responsibility Responsibility Responsibility: Role: Client Client Client Interaction. Client Client interaction. IIV&V, Quality Interaction. Interaction. Analyze system Interaction. Analyze current Focal Point Analyze system Analyze architecture Analyze system of client’s architecture prototype design. design developed existing games. design. Secondary implemented. system Secondary Secondary Responsibility Secondary thoroughly and Responsibility: Responsibility Ensure quality of Responsibility ensure smooth Analyze the Scrutinize the the prototype Ensure quality of integration with requirements quality of the meets game being client’s existing specified. stakeholder developed meets system. system’s architecture, requirements. standards Negotiate Secondary client’s each and meets all Responsibility with development success critical Ensure quality of stakeholders. item, and design game developed stakeholders’ asset. requirements. meets client’s standards and meets all success critical stakeholders’ requirements. Name: Primary Primary Primary Primary Primary Nitin Surana Responsibility: Responsibility Responsibility Responsibility Responsibility Role: Analyze Plan and Develop detailed Develop detailed Develop detailed Life Cycle requirements and estimate project iteration project iteration project iteration Planner, Software plan the project life timeline for plan. plan. plan for the Architect cycle, and duration each iteration. Identify tasks to Identify tasks to integration of each iteration. Identify time incorporate in incorporate in phase. Secondary and effort each iteration. each iteration. Identify tasks to required for Identify Identify incorporate in Responsibility: Evaluate system each task. responsibilities. responsibilities. each iteration. requirements. Secondary Plan for backlog Plan for backlog Identify
Ravichandran Role: Requirements Engineer, UML Modeler Client Interaction. Analyze system architecture used in previous games built by client. Capture requirements of new game. Negotiate win- conditions with stakeholders. Secondary Responsibility Provide feasibility evidence for gathered requirements. Client Interaction. Make sure the architecture design meets specified requirements. Secondary Responsibility Work with system architect and develop UML diagrams. Help build design assets. Client Interaction. Perform analysis of prototype to ensure adherence to stakeholder win conditions. Secondary Responsibility Ensure prototype adheres to UML diagrams designed earlier. Client Interaction. Perform analysis of game features to ensure adherence to stakeholder win conditions. Secondary Responsibility Ensure game features adhere to UML diagrams designed earlier. Client Interaction. Perform analysis of game features to ensure adherence to stakeholder win conditions. Secondary Responsibility Ensure game features adhere to UML diagrams designed earlier. Name: John Leibowitz Role: IIV&V, Quality Focal Point Primary Responsibility: Client interaction. Analyze current system of client’s existing games. Secondary Responsibility: Analyze the requirements specified. Negotiate with stakeholders. Primary Responsibility Client Interaction. Analyze system architecture design. Secondary Responsibility Scrutinize the quality of the system’s architecture, each development item, and design asset. Primary Responsibility Client Interaction. Analyze prototype design. Secondary Responsibility Ensure quality of the prototype meets stakeholder requirements. Primary Responsibility Client Interaction. Analyze system architecture design implemented. Secondary Responsibility Ensure quality of game being developed meets client’s standards and meets all success critical stakeholders’ requirements. Primary Responsibility Client Interaction. Analyze developed system thoroughly and ensure smooth integration with client’s existing system. Secondary Responsibility Ensure quality of game developed meets client’s standards and meets all success critical stakeholders’ requirements. Name: Nitin Surana Role: Life Cycle Planner, Software Architect Primary Responsibility: Analyze requirements and plan the project life cycle, and duration of each iteration. Secondary Responsibility: Evaluate system requirements. Primary Responsibility Plan and estimate timeline for each iteration. Identify time and effort required for each task. Secondary Primary Responsibility Develop detailed project iteration plan. Identify tasks to incorporate in each iteration. Identify responsibilities. Plan for backlog Primary Responsibility Develop detailed project iteration plan. Identify tasks to incorporate in each iteration. Identify responsibilities. Plan for backlog Primary Responsibility Develop detailed project iteration plan for the integration phase. Identify tasks to incorporate in each iteration. Identify