|
Basic Unified Process (BUP) is a streamlined version of Rational Unified Process (RUP) optimized for small projects.
BUP was developed by IBM. It is transitioned to the Eclipse Process Framework Project (EPF) and got renamed into OpenUP. OpenUP is a subset of OpenUP/Basic.
OpenUP is an open-source software development process framework with only fundamental content providing a simplified set of work products, roles, tasks, and guidance. OpenUP/Basic is an iterative software development process that is minimal, complete, and extensible. It is a process for small, co-located teams that value collaboration and stakeholder benefits over unnecessary deliverables and formality.
OpenUP/Basic is a common language, a common way of doing things that aligns how stakeholders and practitioners understand a project. It focuses on articulating the architecture to facilitate technical collaboration, reduce risk, and minimize scrap and rework. OpenUP/Basic seeks a balance between stakeholder needs and technical costs that maximizes stakeholder value and guides the development process. The system evolves in an iterative lifecycle. This demonstrates ongoing results to the customer and reduces risks of failure.
OpenUP/Basic is ready to use as-it-is. Nevertheless, OpenUP/Basic is extensible, because it can be used as a foundation on which process content can be added or tailored as needed. It is an exemplary and extensible process for a range of software development and management processes that supports iterative, agile, and incremental development. It is applicable to a broad set of development platforms and applications.
OpenUP/Basic is an iterative process distributed throughout four phases: Inception, Elaboration, Construction, and Transition. Each phase consists of one or more iterations, where stable, working versions of the software are developed and released, with the completion of each iteration representing a minor milestone for the project and contributing to the successful achievement of the Phase's major milestone where phase objectives are met.
Is about understanding the project scope and objectives and getting enough information to confirm that the project should proceed - or convince you that it should not. The purpose in this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project.
Especially when architecturally significant risks are addressed. The purpose of this phase is to establish the baseline of the architecture of the system and provide a stable basis for the bulk of the development effort in the next phase.
Construction focuses on design, implementation, and testing of functionalities to develop a complete system. The purpose in this phase is to complete the development of the system based upon the baselined architecture.
The purpose in this phase is to ensure that the software is ready for delivery to users.
|
Open UP/Basic 