Please enable JavaScript.
Coggle requires JavaScript to display documents.
THE PERSONAL SOFTWARE PROCESS STRATEGY - Coggle Diagram
THE PERSONAL SOFTWARE PROCESS STRATEGY
PSP´s PURPOSE
Plan better
Track your performance properly
Measure the quality of your products
DO BETTER JOB IN:
• Design programs
• Develop requirements
• Write documentation
• Maintain existing software, etc.
THE LOGIC FOR A SOFTWARE ENGINEERING DISCIPLINE
Professionals develop their own private method, some of the professionals are outstandingly creative, the process is distressingly unpredictable.
This analogy suggests that large-scale software development should be treated as a problem of crowd control.
This approach, while generally tolerated, has been expensive.
The software engineer must be part composer as well as performer, the performance of a software system can be damaged by almost any defective part.
When the products become larger and are used in increasingly critical applications, the potential of damaging error will almost certainly increase.
The software industry has responded to this threat by resorting to increasingly rigorous an time-consuming tests (but it isn´t totally effective)
A disciplined software engineering will have well-defined practices for a quality control.
Practices disciplines have the further benefit of making software engineering more fun. But this fun is affected by committing the same mistakes over and over.
WHAT IS A SOFTWARE PROCESS?
Defined processes are what Deming calls operational definitions. They provide benefits like:
• Effective communication among users, developers, managers, customers and researchers.
• Provide a precises basis for process automation
• Facilitate process reuse
• Provides an effective means for process leanrning to support process evolution
• Provides a framework for an effective management
PROCESS MATURITY
Processes are hard to establish and even harder to break
The processes for large-scale software development can themselves be quite large and complex, they are hard to define, to comprehend and even harder to introduce.
The software process maturity framework was developed to determine the capabilities of their current processes and to establish priorities for improvement.
There are 5 levels of mature process capability
1.- Initial
2.- Repeatable
3.- Defined
4.- Managed
5.- Optimizing
The CMM is the best available description of the goals, methods, and practices needed for the industrial practice of software engineering.
YOUR PERSONAL RESBONSABILITIES
Personal excellence
Consistent high performance takes persistent effort, an understanding of your own abilities, and a dedication to personal excellence.
Personal motivation
The PSP is a self-improvement process. Mastering it requires research, study, and a lot of work.
THE PSP STRATEGY
Identify those methods that can be used by indivduals
Define the subset of this methods that can be applied while developing small programs
Structure these methods and practices so they can be gradually introduced
The process improvement phases are:
• PS0 THE BASELINE PROCESS: Establish a baseline that includes some basic measurements and a reporting format
• PSP1: THE PERSONAL PLANNIGN PROCESS: Adds a test report and resource estimation. Documented plans to : help you understand the relation between size and time, make commitments you can meet, give an orderly plan for doing the work, and give a framework for determining the status of your work
• PSP2 PERSONAL QUALITY MANAGEMENT PROCESS: Help you learn early on how to deal realistically and objectively with the program defect that result form your errors.
• PSP3 A CYCLIC PERSONAL PROCESS: PSP has concentrated on a simple linear process for building small programs. The strategy is to subdivide a larger program into PSP2- sized pieces.
LOGIC FOR PSP
Is based in 5 principles:
• A defined and structured process can improve working efficiency
• Defined personal processes should conveniently fit the individual skills and preferences of each software engineer
• Be involved in its definition
PRODUCTIVITY AND THE PSP
Productivity judgments:
• Productivity is affected by the size of the product to be produced.
• When additional commenting or documentation is included, the amount of work will increase, and productivity will decline
• When the numbers of defect entering fluctuate widely, the test time will do the same, thus further affecting productivity.