What is RUP and PSP?

[chinmay]

RUP stands for Rational Unified Process It deals with -


• Iterative software development process.
• Visual Modeling of Systems
• Quality Management
• Change Control Management
• Deals with the role, the activity, and the artifact
• For managing OO Software Development Some Features of RUP are -
• Online Repository of Process Information and Description
• Templates for all major artifacts, including:
– Requirements tracking (RequisitePro templates)
Use Cases (Word Templates )
– Project Management (Project Templates)
• Process Manuals describing key processes
PSP stands for Personal Software Process
PSP Objectives are -
– To introduce individuals to a process-based approach to developing software
– To show individuals how to measure, estimate, schedule, and track their work
– To show individuals how to improve the quality of their programs
– In general PSP improves quality and productivity
- The time saved in testing because of better quality reduces time across the project by 20-40%
Advantage of PSP -
– To manage your work & assess/build your talents/skills
– To plan better
– To track your performance precisely
– To measure the quality of your software products

[tctsinc8]

RUP is short for Logical Specific Process
It handles -
• Repetitive application growth procedure.
• Visible Modelling of Systems
• Quality Management
• Change Control Management
• Offers with the part, the action, and the artifact
• For handling OO Software Development
Some Popular features of RUP are -
• Online Database of Process Information and Description
• Layouts for all significant relics, including:
– Specifications monitoring (RequisitePro templates)
– Use Situations (Word Layouts )

[sinelogix]

"Rational Unified Process." RUP is a software development process from Rational, a division of IBM. It divides the development process into four distinct phases that each involve business modeling, analysis and design, implementation, testing, and deployment.


The Personal Software Process (PSP) is a structured software development process that is intended (planned) to help software engineers better understand and improve their performance by tracking their predicted and actual development of code.