Scribd Logo
Upload

Welcome to Scribd!

    • 20 views

    Personal and Team Process Models

    Uploaded by

    bommaiah

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Personal and Team Process Models

    Uploaded by

    bommaiah
    20 views10 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    20 views10 pages

    Personal and Team Process Models

    Uploaded by

    bommaiah

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 10

    PERSONAL AND TEAM PROCESS MODELS

     The best software process is one that is close to


    the people who will be doing the work.
     Each software engineer would create a
    process that best fits his or her needs, and
    at the same time meets the broader needs
    of the team and the organization.
     Alternatively, the team itself would create its
    own process, and at the same time meet the
    narrower needs of individuals and the broader
    needs of the organization.
    PERSONAL AND TEAM PROCESS MODELS

     The quality of a software system is determined by


    the quality of its worst components.
     The quality of a software component is governed
    by the individual who developed it.
     The quality of a software component is governed
    by the quality of the process used to develop
    it.
     The key to quality is the individual developer’s
    skill, commitment, and personal process
    discipline.
    PERSONAL AND TEAM PROCESS MODELS
     As a software professional, you are
    responsible for your personal process.
     You should measure, track, and analyze
    your work.
     You should learn from your performance
    variations.
     You should incorporate lessons learned into
    your personal practices.
    PERSONAL SOFTWARE PROCESS (PSP)
     The personal software process (PSP) emphasizes
    personal measurement of both the work
    product that is produced and the resultant
    quality of the work product.
     The PSP process model defines five framework
    activities:
     planning,
     high-level design,
     high level design review,
     Development and
     postmortem.
    PERSONAL
    Planning: This activity isolates
    SOFTWARE PROCESSrequirements
    (PSP)
    and, base on these develops both size and
    resource estimates.
    In addition, a defect estimate is made. All
    metrics are recorded on worksheets or templates.
    Finally, development tasks are identified and a
    project schedule is created.
     High level design: External specifications for
    each component to be constructed are developed
    and a component design is created. Prototypes are
    built when uncertainty exists. All issues are
    recorded and tracked.
     High level design review: Formal verification
    methods are applied to uncover errors in the
    PERSONAL SOFTWARE
     Development: PROCESS
    The component (PSP) is refined
    level design
    and reviewed. Code is generated, reviewed,
    compiled, and tested. Metrics are maintained for all
    important task and work results.
     Postmortem: Using the measures and metrics
    collected the effectiveness of the process is
    determined. Measures and metrics should provide
    guidance for modifying the process to improve its
    effectiveness.
     PSP stresses the software engineer to identify errors
    early and, as important, to understand the types of
    errors that he is likely to make.
     PSP represents a disciplined, metrics-based approach to software
    engineering.
    TEAM
     The goalSOFTWARE PROCESS
    of TSP is to build (TSP)
    a “self-directed project
    team” to produce high-quality software.
     The following are the objectives for TSP:
     Build self-directed teams that plan and track
    their work, establish goals, and own their
    processes and plans. These can be pure software
    teams or integrated product teams(IPT) of 3 to about
    20 engineers.
     Show managers how to coach and motivate their
    teams and how to help them sustain peak
    performance.
     Accelerate software process
     Provide improvement guidance to high-maturity
    TEAM SOFTWARE PROCESS (TSP)
     A self-directed team defines
    - roles and responsibilities for each team
    member
    - tracks quantitative project data
    - identifies a team process appropriate for
    project
    - a strategy for implementing the process
    - defines local standards that are applicable
    to the teams software engineering work;
    - continually assesses risk and reacts to it
    - Tracks, manages, and reports project
    status.
    TEAM SOFTWARE PROCESS (TSP)
     TSP defines the following framework activities:
     Project launch,
     high-level design,
     implementation,
     integration and test,
     and postmortem.
     TSP makes use of a wide variety of scripts, forms,
    and standards that serve to guide team members in
    their work.
     Scripts define specific process activities and other
    more detailed work functions that are part of the
    team process.
    TEAM SOFTWARE PROCESS (TSP)
     Each project is “launched” using a sequence of
    tasks.
     The following launch script is recommended
     Review project objectives with management and
    agree on and document team goals.
     Establish team roles
     Define the teams development process
     Make a quality plan and set quality targets
     Plan for the needed support facilities

    You might also like