Metodologia de Desenvolvimento de Software www.cin.ufpe.br/~mds Hermano Moura Alexandre Vasconcelos, André Santos, Augusto Sampaio, Hermano Moura, Paulo.

Apresentação em tema: "Metodologia de Desenvolvimento de Software www.cin.ufpe.br/~mds Hermano Moura Alexandre Vasconcelos, André Santos, Augusto Sampaio, Hermano Moura, Paulo."— Transcrição da apresentação:

1 Metodologia de Desenvolvimento de Software www.cin.ufpe.br/~mds Hermano Moura Alexandre Vasconcelos, André Santos, Augusto Sampaio, Hermano Moura, Paulo Borba © Centro de Informática Universidade Federal de Pernambuco

2 Planejamento & Gerenciamento Hermano Moura (com textos e figuras do RUP) Objetivo Depois desta aula você terá uma visão geral das seguintes atividades do fluxo de planejamento e gerenciamento do RUP: Dimensionamento da Equipe do Projeto Desenvolvimento do Plano de Iteração Execução do Plano de Iteração Avaliação da Iteração Revisão da Lista de Riscos

3 Planejamento & Gerenciamento

4 Dimensionamento da Equipe de Projeto n Purpose u To map available resources onto the skill sets needed for the project. u To group available resources into relatively independent but collaborating teams.

5 Dimensionamento da Equipe de Projeto n Steps u Consider staffing needs across phases: F Staffing the Inception and Elaboration Phases F Staffing the Construction Phase F Staffing Testing Activities F Staffing the Transition Phase u Map Staff Skills to Workers u Form Teams u Train Project Staff

6 Dimensionamento da Equipe de Projeto n Input Artifacts: u Development Case u Project Plan n Resulting Artifacts: u Staffing Plan in the Software Development Plan n Worker: u Project Manager

7 Desenvolvimento do Plano de Iteração n Purpose u To develop a fine-grained plan for one single iteration, consisting of: F a detailed work breakdown structure of the activity and responsibility assignments F intra-iteration milestones and deliverables F evaluation criteria for the iteration

8 Desenvolvimento do Plano de Iteração n Steps u Determine the Iteration Scope u Define Iteration Evaluation Criteria u Define Iteration Activities u Assign Responsibilities n Input Artifacts: u Software Development Plan u Software Architecture Document u Development Case u Project Plan

9 Desenvolvimento do Plano de Iteração n Resulting Artifacts: u Iteration Plan n Frequency: u Once per iteration n Worker: u Project Manager

10 Execução do Plano de Iteração n Purpose u To produce an executable release n Input Artifacts: u Iteration Plan n Resulting Artifacts: u Implementation Model (a release) n Frequency: Once per iteration n Worker: Project Manager

11 Avaliação da Iteração n Purpose u Determine success or failure of the iteration u Capture lessons learned to modify the project or improve the process n Steps u Collect Metrics u Assess the Results of the Iteration u Consider External Change u Examine the Evaluation Criteria u Create Change Requests

12 Avaliação da Iteração n Input Artifacts: u Iteration Plan u Test Plans u Test Results u Business Case u Measurement plan

13 Avaliação da Iteração n Resulting Artifacts: u Iteration assessment u Change proposals for: F Risk List F Project Plan F Iteration Plan for the next iteration

14 Avaliação da Iteração n Frequency: u Once per iteration n Worker: u Project Manager n Guidelines: u Reviews

15 Revisão da Lista de Riscos n Purpose u To update the Risk List to reflect the current project status. n Steps u Revisiting Risks during the Iteration u Revisiting Risks at the End of an Iteration n Input Artifacts: u Risk List u Risk List change proposals

16 Revisão da Lista de Riscos n Resulting Artifacts: u Risk List n Frequency: u Once per iteration n Worker: u Project Manager

17 Avaliação de Status n Purpose F Status assessments provide a mechanism for addressing, communicating, and resolving management issues, technical issues, and project risks. Continuous open communication with objective data derived directly from ongoing activities, and the evolving product configurations are mandatory in any project. These project snapshots provide the heartbeat for management attention. While the period may vary, the forcing function needs to capture the project history.

18 Avaliação de Status (Modelo) n 1. Objectives u A brief description of the purpose of the Status Assessment. n 2. Scope u A brief description of what the Status Assessment applies to; what is affected or influenced by this document. n 3. References u A list of related or referenced documents.

19 Avaliação de Status (Modelo) n 4. Resources F 1. Personnel/staffing: Status of personnel. Report any issues or concerns. F 2. Financial data: Current costs and revenue compared to the plan. n 5. Top 10 risks u Report the status of the top 10 risks. n 6. Technical progress u Report technical progress using metrics snapshots, etc.

20 Avaliação de Status (Modelo) n 7. Major milestone results u Report the status of major milestones to date. n 8. Total project/product scope u Report status of project/product scope. n 9. Action items and follow-through u A list of action items and their current status.

21 P&G: Artefatos

22 Planejamento & Gerenciamento Hermano Moura Leitura adicional Navegar pelo fluxo de planejamento e gerenciamento na página do RUP (http://www.cin.ufpe.br/~alms/RUP).

23 Artefatos a serem produzidos para P&G n Business Case n Lista de Riscos n Plano de Projeto

24 Metodologia de Desenvolvimento de Software www.cin.ufpe.br/~mds Hermano Moura Alexandre Vasconcelos, André Santos, Augusto Sampaio, Hermano Moura, Paulo Borba © Centro de Informática Universidade Federal de Pernambuco