The Experts below are selected from a list of 5394 Experts worldwide ranked by ideXlab platform
Philippe Kruchten - One of the best experts on this subject based on the ideXlab platform.
-
tutorial introduction to the rational Unified Process
International Conference on Software Engineering, 2002Co-Authors: Philippe KruchtenAbstract:The Rational Unified Process® (RUP®) is a software engineering Process framework. It captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organizations. It embeds object-oriented techniques and uses the UML as the principal notation for the several models that are built during the development. The RUP is also an open Process framework that allows software organizations to tailor the Process to their specific need, and to capture their own specific Process know-how in the form of Process components. Many Process components are now developed by various organizations to cover different domains, technologies, tools, or type of development, and these components can be assembled to rapidly compose a suitable Process. This tutorial will introduce the basic concepts and principles, which lie under the RUP framework, and show concrete examples of its usage.
-
how to fail with the rational Unified Process seven steps to pain and suffering
2002Co-Authors: Craig Larman, Rational Fellow, Philippe Kruchten, Kurt BittnerAbstract:The Rational Unified Process provides a valuable framework for approaching the business of developing software. As a framework, however, it must be adapted to the needs of each project team and their circumstances; it is intended to be applied in a light and agile style, and not adopted as a one-size-fits-all Process. This article shares a number of common pitfalls experienced by teams attempting to adapt the Rational Unified Process to their needs, presented with a little tongue-in-cheek.
-
the rational Unified Process an introduction second edition
2000Co-Authors: Philippe KruchtenAbstract:From the Publisher: This concise book offers a quick introduction to the concepts, structure, content, and motivation of the Rational Unified Processa Web-enabled software engineering Process that enhances team productivity and delivers software best practices to all team members. The Rational Unified Process is unique in that it allows development teams to recognize the full benefits of the Unified Modeling Language (UML), software automation, and other industry best practices. The Rational Unified Process unifies the entire software development team and optimizes the productivity of every team member by putting the collective experience derived from thousands of projects and many industry leaders at your fingertips. With this book as your guide, you will be able to more easily produce, within a predictable schedule and a reasonable budget, the highest-quality software possible. Throughout the book, the author shares his inside knowledge of the Process, focusing his coverage on key aspects that are critical to mastering this proven approach to software development. This Second Edition has been updated to match and reflect the contents of the latest version of the Rational Unified Process. In particular, RUP 2000 offers: More guidance for e-development Roadmaps that provide overviews of how to apply the Process to a wide variety of projects and technologies Expanded analysis of testing, spanning the entire product lifecycle Improved coverage of application interface designespecially as it applies to developing effective web applications Enhanced details for developing real-time and reactive systems Insights intodesigning systems using patterns and frameworks
-
the rational Unified Process
1999Co-Authors: Philippe KruchtenAbstract:Preface. Goals of This Book. Who Should Read This Book? How to Use This Book. Organization and Special Features. For More Information. Second Edition. Acknowledgments. I. THE Process. 1. Software Development Best Practices. The Value of Software. Symptoms and Root Causes of Software Development Problems. Software Best Practices. Develop Software Iteratively. Manage Requirements. Use Component-Based Architectures. Visually Model Software. Continuously Verify Software Quality. Control Changes to Software. The Rational Unified Process. Summary. 2. The Rational Unified Process. What Is the Rational Unified Process? The Rational Unified Process as a Product. Process Structure: Two Dimensions. Software Best Practices in the Rational Unified Process. Other Key Features of the Rational Unified Process. A Brief History of the Rational Unified Process. Summary. 3. Static Structure: Process Description. A Model of the Rational Unified Process. Workers. Activities. Artifacts. Workflows. Additional Process Elements. A Process Framework. Summary. 4. Dynamic Structure: Iterative Development. The Sequential Process. Overcoming Difficulties: Iterate! Gaining Control: Phases and Milestones. A Shifting Focus across the Cycle. Phases Revisited. Benefits of an Iterative Approach. Summary. 5. An Architecture-centric Process. The Importance of Models. Architecture. The Importance of Architecture. A Definition of Architecture. Architecture Representation. An Architecture-centric Process. The Purpose of Architecture. Component-Based Development. Other Architectural Concepts. Summary. 6. A Use-Case-Driven Process. Definitions. Identifying Use Cases. Evolving Use Cases. Organizing Use Cases. Use Cases in the Process. Summary. II. Process WORKFLOWS. 7. The Project Management Workflow. Purpose. Planning an Iterative Project. The Concept of Risk. The Concept of Metrics. What Is a Metric? Workers and Artifacts. Workflow. Building an Iteration Plan. Summary. 8. The Business Modeling Workflow. Purpose. Why Business Modeling? Using Software Modeling Techniques for Business Modeling. Business Modeling Scenarios. Workers and Artifacts. Workflow. From the Business Models to the Systems. Modeling the Software Development Business. Tool Support. Summary. 9. The Requirements Workflow. Purpose. What Is a Requirement? Types of Requirements. Capturing and Managing Requirements. Designing a User-Centered Interface. Requirements Workflow. Workers in Requirements. Artifacts Used in Requirements. Tool Support. Summary. 10. The Analysis and Design Workflow. Purpose. Analysis versus Design. How Far Must Design Go? Workers and Artifacts. The Design Model. The Analysis Model. The Role of Interfaces. Artifacts for Real-Time Systems. Component-Based Design. Workflow. Tool Support. Summary. 11. The Implementation Workflow. Purpose. Builds. Integration. Prototypes. Workers and Artifacts. Workflow. Tool Support. Summary. 12. The Test Workflow. Purpose. Quality. Testing in the Iterative Lifecycle. Dimensions of Testing. The Test Model. Workers and Artifacts. Workflow. Tool Support. Summary. 13. The Configuration and Change Management Workflow. Purpose. The CCM Cube. Workers and Artifacts. Workflow. Tool Support. Summary. 14. The Environment Workflow. Purpose. Workers and Artifacts. Workflow. Summary. 15. The Deployment Workflow. Purpose. Workers and Artifacts. Workflow. Summary. 16. Typical Iteration Plans. Purpose. Defining the Product Vision and the Business Case. Building an Architectural Prototype. Implementing the System. Summary. 17. Configuring and Implementing the Rational Unified Process. Introduction. The Effect of Implementing a Process. Implementing the Rational Unified Process Step by Step. Configuring the Process. Implementing a Process Is a Project. Summary. Appendix A: Summary of Workers. Appendix B: Summary of Artifacts. Acronyms. Glossary. Bibliography. Index. 0201707101T04062001
-
the rational Unified Process an introduction
1998Co-Authors: Philippe KruchtenAbstract:(NOTE: Each chapter concludes with a summary.) Preface. I. THE Process. 1. Software Development Best Practices. The Value of Software. Symptoms and Root Causes of Software Development Problems. Software Best Practices. Develop Software Iteratively. Manage Requirements. Use Component-Based Architectures. Visually Model Software. Continuously Verify Software Quality. Control Changes to Software. The Rational Unified Process. 2. The Rational Unified Process. What Is the Rational Unified Process? The Rational Unified Process as a Product. Software Best Practices in the Rational Unified Process. Other Key Features of the Rational Unified Process. A Brief History of the Rational Unified Process. 3. Static Structure: Process Description. A Model of the Rational Unified Process. Roles. Activities. Artifacts. Disciplines. Workflows. Additional Process Elements. A Process Framework. 4. Dynamic Structure: Iterative Development. The Sequential Process. Overcoming Difficulties: Iterate! Gaining Control: Phases and Milestones. A Shifting Focus across the Cycle. Phases Revisited. Benefits of an Iterative Approach. 5. An Architecture-Centric Process. The Importance of Models. Architecture. The Importance of Architecture. A Definition of Architecture. Architecture Representation. An Architecture-Centric Process. The Purpose of Architecture. Component-Based Development. Other Architectural Concepts. 6. A Use-Case-Driven Process. Definitions. Identifying Use Cases. Evolving Use Cases. Organizing Use Cases. Use Cases in the Process. II. Process DISCIPLINES. 7. The Project Management Discipline. Purpose. Planning an Iterative Project. The Concept of Risk. The Concept of Measurement. Roles and Artifacts. Workflow. Building an Iteration Plan. 8. The Business Modeling Discipline. Purpose. Why Business Modeling? Using Software Engineering Techniques for Business Modeling. Business Modeling Scenarios. Roles and Artifacts. Workflow. From the Business Models to the Systems. Modeling the Software Development Business. Tool Support. 9. The Requirements Discipline. Purpose. What Is a Requirement? Types of Requirements. Capturing and Managing Requirements. Requirements Workflow. Roles in Requirements. Artifacts Used in Requirements. Tool Support. 10. The Analysis and Design Discipline. Purpose. Analysis versus Design. How Far Must Design Go? Roles and Artifacts. Designing a User-Centered Interface. The Design Model. The Analysis Model. The Role of Interfaces. Artifacts for Real-Time Systems. Component-Based Design. Workflow. Tool Support. 11. The Implementation Discipline. Purpose. Builds. Integration. Prototypes. Roles and Artifacts. Workflow. Tool Support. 12. The Test Discipline. Purpose. Testing in the Iterative Lifecycle. Dimensions of Testing. Roles and Artifacts. Workflow. Tool Support. 13. The Configuration and Change Management Discipline. Purpose. The CCM Cube. Roles and Artifacts. Workflow. Tool Support. 14. The Environment Discipline. Purpose. Process Engineering Process. Roles and Artifacts. Workflow. Tool Support. 15. The Deployment Discipline. Purpose. Roles and Artifacts. Workflow. 16. Typical Iteration Plans. Defining the Product Vision and the Business Case. Building an Architectural Prototype. Implementing the System. 17. Implementing the Rational Unified Process. Introduction. The Effect of Implementing a Process. Implementing the Rational Unified Process Step by Step. Implementing a Process Is a Project. Appendix A: Summary of Roles. Appendix B: Summary of Artifacts. Appendix C: Acronyms. Glossary. Bibliography. Index. 0321197704T11172003
Manoj Wadhwa - One of the best experts on this subject based on the ideXlab platform.
-
exsrup hybrid software development model integrating extreme programing scrum rational Unified Process
Indonesian Journal of Electrical Engineering and Computer Science, 2015Co-Authors: Nidhi Sharma, Manoj WadhwaAbstract:Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits & demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium & large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.
-
eXSRUP: Hybrid Software Development Model Integrating Extreme Programing, Scrum & Rational Unified Process
Indonesian Journal of Electrical Engineering and Computer Science, 2015Co-Authors: Nidhi Sharma, Manoj WadhwaAbstract:Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits & demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium & large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.
Richard C Holt - One of the best experts on this subject based on the ideXlab platform.
-
software Process recovery using recovered Unified Process views
International Conference on Software Maintenance, 2010Co-Authors: Abram Hindle, Michael W Godfrey, Richard C HoltAbstract:The development Process for a given software system is a combination of an idealized, prescribed model and a messy set of ad hoc practices. To some degree, Process compliance can be enforced by supporting tools that require various steps be followed in order; however, this approach is often perceived as heavyweight and inflexible by developers, who generally prefer that tools support their desired work habits rather than limit their choices. An alternative approach to monitoring Process compliance is to instrument the various tools and repositories that developers use — such as version control systems, bug-trackers, and mailing-list archives — and to build models of the de facto development Process through observation, analysis, and inference. In this paper, we present a technique for recovering a project's software development Processes from a variety of existing artifacts. We first apply unsupervised and supervised techniques — including word-bags, topic analysis, summary statistics, and Bayesian classifiers — to annotate software artifacts by related topics, maintenance types, and non-functional requirements. We map the analysis results onto a time-line based view of the Unified Process development model, which we call Recovered Unified Process Views. We demonstrate our approach for extracting these Process views on two case studies: FreeBSD and SQLite.
-
ICSM - Software Process recovery using Recovered Unified Process Views
2010 IEEE International Conference on Software Maintenance, 2010Co-Authors: Abram Hindle, Michael W Godfrey, Richard C HoltAbstract:The development Process for a given software system is a combination of an idealized, prescribed model and a messy set of ad hoc practices. To some degree, Process compliance can be enforced by supporting tools that require various steps be followed in order; however, this approach is often perceived as heavyweight and inflexible by developers, who generally prefer that tools support their desired work habits rather than limit their choices. An alternative approach to monitoring Process compliance is to instrument the various tools and repositories that developers use — such as version control systems, bug-trackers, and mailing-list archives — and to build models of the de facto development Process through observation, analysis, and inference. In this paper, we present a technique for recovering a project's software development Processes from a variety of existing artifacts. We first apply unsupervised and supervised techniques — including word-bags, topic analysis, summary statistics, and Bayesian classifiers — to annotate software artifacts by related topics, maintenance types, and non-functional requirements. We map the analysis results onto a time-line based view of the Unified Process development model, which we call Recovered Unified Process Views. We demonstrate our approach for extracting these Process views on two case studies: FreeBSD and SQLite.
Chen Zhiwen - One of the best experts on this subject based on the ideXlab platform.
-
compare essential Unified Process essup with rational Unified Process rup
Conference on Industrial Electronics and Applications, 2015Co-Authors: Wang Quanyu, Chen ZhiwenAbstract:Essential Unified Process (EssUP) is a new software development Process invented by Ivar Jacobson around 2006. It is based on Rational Unified Process (RUP) and takes Agile development philosophy into account. RUP was proposed by IBM Rational and now it is implemented as part of the IBM Rational tools. It is well known that EssUP is practice separation and lightweight and UP is an integrated and heavyweight Process. In this paper, we introduce and characterize EssUP by systematically comparing it with traditional RUP from different aspects such as separation of concerns, flexibility, presentation, and tailorable. Comparison results show that EssUP is very flexible to be adopted, adapted, and configured. In other words, there is no actual Process for EssUP and EssUP is just composed of a set of selected practices. Moreover, to successfully apply EssUP requires experiences and expertise. The contribution of the paper is that we provide readers a comprehensive and insight view of EssUP by thoroughly comparing it with commonly-used RUP.
Antje Baer - One of the best experts on this subject based on the ideXlab platform.
-
ibm rational Unified Process reference and certification guide solution designer
2016Co-Authors: Antje BaerAbstract:Thank you for reading ibm rational Unified Process reference and certification guide solution designer. Maybe you have knowledge that, people have look numerous times for their chosen readings like this ibm rational Unified Process reference and certification guide solution designer, but end up in harmful downloads. Rather than enjoying a good book with a cup of coffee in the afternoon, instead they juggled with some malicious virus inside their laptop.
