SPPM 6

• 
  TSP provides a defined operational process to guide engineers and managers through the team building steps.
• This process specifies the steps that is needed to establish an effective environment.
• Without specific guidelines,engineers must work out the details of team-building and team-working for themselves.
• TSP provides the operational process needed to form the engineering teams to establish an effective team environment.
• TSP is one of the series of methods that can help engineering teams,to establish an effective team environment.

·        LAUNCHING A TSP TEAM:

·         Day 1:

1.      Establish product and business goals.
2.     Assign roles and define team goals.
3.      Product development strategy.

            Day 2:

1.      Build top-down and next phase plans.
2.     Develop the quality plan.
3.     Build bottom-up and balanced plans.

Day 3:

1.      Conduct risk assessment.
2.      Prepare management briefing and launch report.

Day 4:

1.      Hold management review.
2.     Perform the launch postmortem.
3.      TSP process review.

STRUCTURE OF THE TSP:

                                                                                                   

• Before the members can participate on the TSP team, they must know how to do the disciplined work.
• PSP training includes how to make detailed plans,gathering and processing data.
• Engineering can be trained before they can participate in the TSP team.

TSP TEAM WORKING PROCESS.

Ø Leading the team.

Ø Process discipline

Ø Issue tracking

Ø Communication

Ø Management reporting.

Ø Maintaining the plan

SPPM 5

§     The PSP is the self-improvement process.

§     It helps to control,manage and improve the work you develop.

§     It is a structured framework of forms,guidelines and procedures for developing software.

§     PSP used to provide data that you need to make commitments.

§     The PSP  also provide the framework for understanding why you make errors and how best to find fix, and prevent them.

§  THE LOGIC OF THE SOFTWARE ENGINEERING DISCIPLINE

§     Software has become the critical part of many of the systems on which modern society depends.

§     Everyone seems to need more and better software.

§     The intuitive software development methods generally used today are acceptable only if there is no alternative.

§  USING DISCIPLINED DEVELOPMENT PROCESS

§      A defined process specifies precisely how to do something.

§     If we have not done such work before and we don’t have a definitely good process

§     Unfortunately without prior experience or a lot of guidance few of us would know precisely how to do the requirements work.

§  OPERATIONAL PROCESS

§      Most development, object to the idea of using the operational process.

§     We all object to being told how to do our job, particularly by someone who doesn't know as much about the work as we do.

§  DEFINING AND USING THE PERSONAL PROCESS

§     With the defined and the measured process not only will you know how well you are doing your job today, you will see how to improve  and to keep improving as long as you can develop software.

§  LEARNING TO USE A PERSONAL PROCESS

SPPM 2

      Functional requirements: -

                    These are statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.

                    It may also state what the system should not do explicitly.

                   Describe the system function in detail, its inputs and outputs, expectations and so on.

                   Expressed in numerous ways:-

• LIBSYS:- able to search the database. able to read the document. provide unique ID. single interface. allows the user to download copies.

Requirements must be precise and should not be ambiguous.

Identify what the customer wants.

Changes to the previous requirements or new ones established.

Complete and consistent. complete means all services ought be defined. consistent in the sense there should be no contradictory definitions. 

Large system would lead to many mistakes and omissions; since there are numerous stake holders with different views; so we need deeper analysis.

Non functional requirements: -

              The non functional requirements are constraints on the services.

The constraints include 

•       Timing constraints. 
•       Development constraints.  
•       Standard constraints.      

Applied system as a whole.

1. Product 
2. Organizational
3. External.

Product in the sense behavior of the system

•  efficiency(include Performance and space)
• reliability
• usability
• portability.

Organizational include policies and procedures in an organization

• Delivery
• Implementation
• Standards.

External in the sense external factors

• Interoperability 
• Ethical
• Legislative.

Non functional requirements must be verifiable. 

Non functional requirements have goals.

Non functional requirements interacts with other functional and non functional requirements.

Metrics: -

• Speed. 
• Size.
• Ease of use.
• Reliability.
• Robustness.
• Portability.