1 / 27

Software Project Managerment

Software Project Managerment. K15T02 – Team02. 1. 3. 3. Contents:. Software Development Process. Introduce TSP. 2. TSP Process. 4. TSP & CMMI. Software Development Process. The software development process is the set of coordinated activities performed by : Engineers Managers

miette
Télécharger la présentation

Software Project Managerment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Software Project Managerment K15T02 – Team02

  2. 1 3 3 Contents: Software Development Process Introduce TSP 2 TSP Process 4 TSP & CMMI

  3. Software Development Process • The software development process is the set of coordinated activities performed by : • Engineers • Managers • Technical writers • Software development process aims to create software products

  4. Software Development Process • There are four operation are the foundation of most software process is: • Software specification • The software development • Evaluation software • The evolution of software

  5. Software Development Process Activities and steps

  6. 1. Requirement • Indentify the system development • Establish project scope and time • Develop project plan • Identify and requirements analysis : • Clarify requirements • Review requirements • documentation requirements.

  7. 2. Architect • Develop technical design architecture works • Identify the system output, input and user interface. • Select the system components • Determine how to integrate the components

  8. 3. Implement • Translating the design into code • Find and check the identification code to prevent syntax errors

  9. 4. Test • Check your code • Check the performance of the system in hardware. • Testing the system in the business environment.

  10. 5. Maintain • Continued monitoring and support • Provide support (debugging, repair, improve)

  11. Software Development Process • Software development model

  12. 1. The Waterfall Model • Sequential development model • Only move to the next phase when the preceding phase is completed. • Use for a large software system with stable requirements

  13. 2. The Spiral Model • Combines elements of both design and prototyping concepts • Combines prototyping model and the waterfall model • Estimates (i.e. budget, schedule, etc.) • Issues are discover earlier and cope with the changes better .

  14. 3. AUP (Agile Unified Process) • AUP is a simplified version of the Rational Unified Process (RUP) and using agile techniques • AUP applies agile techniques include : • Test driven development (TDD) • Agile Model Driven Development (AMDD) • Agile change management • Database refactoring to improve your productivity. • Use for medium and small projects, requiring fast development.

  15. 3. AUP (Agile Unified Process)

  16. 4. Scrum • Scrum use the AGILE methodology • Include: establish , monitoring, and managing the job is not done, the current work, the risks, problems and changes. • SCRUM particularly suitable for the requested project or quickly change.

  17. 5. Extreme Programming • XP is operating iteration model • The advantage of this model is that the project team to quickly get feedback from customers. • The necessary changes will be applied immediately in the next iteration.

  18. 1 3 3 Contents: Software Development Process Introduce TSP 2 TSP Process 4 TSP & CMMI

  19. Team Software Process (TSP) • Introduce TSP:

  20. 1 3 3 Contents: Software Development Process Introduce TSP 2 TSP Process 4 TSP & CMMI

  21. Implementation Strategy:The TSP has three general parts:1. The first part is team formation, during which you recruit potential team members and provide them and their mangers with any needed training or orientation2. Second comes the team launch, in which management tells the team what they want done and the team builtsits plan to do the necessary work.3. The third part is ongoing team operation, where the team follows its plan to do the job. TSP Process:

  22. Implementation Strategy • The first step in a TSP initiative is to train all team members who can write programs in PSP • The result of the PSP: • learn about good processes • improve their own processes • measure the effects of those process changes • quantify the benefits they have experienced, and set goals for further improvements • Personal Software Process (PSP)

  23. Those who complete the PSP boot camp emerge with the knowledge and skills to make accurate plans, work to those plans, and produce superior quality products.

  24. The TSP Launch Process

  25. 1 3 3 Contents: Software Development Process Introduce TSP 2 TSP Process 4 TSP & CMMI

  26. TSP & CMMI: • CMMI and TSP form a powerful set of technologies that businesses can use to improve performance and meet their business goals, sometimes even quicker than using one by itself. • The TSP has the same roots as the CMMI, being based on the Software Engineering Institute’s (SEISM) early research that produced the CMM for Software (SW-CMM). As such, it aligns well with the CMMI and partly or fully satisfies the CMMI’s goals. • So, adding the TSP to a CMMI initiative does not mean adding more work to an already overworked group. Rather, it can be an effective way to accelerate that initiative by laying a solid foundation of process discipline, engaging the engineers from the very beginning, and providing processes that already address a significant number of CMMI practices. The costs of incorporating the TSP into your CMMI initiative should be more than returned as you achieve your CMMI goals more quickly and with less organizational pain.

  27. ‘Thank’ THE END

More Related