Openup
Different projects have different process needs. Typical factors dictate the needs for a more formal or agile process, such as team size and location, architecture complexity, technology novelty, conformance to standards, among others. Nevertheless, there are good software development practices that benefit any project team and help them to be more effective.
This paper introduces the building blocks of OpenUP – an agile and Unified Process that contains the minimal set of practices that help teams to be more effective in developing software. OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a tools-agnostic, low-ceremony process that can be used as is or extended to address a broad variety of project types.
What is OpenUP
OpenUP is a minimally sufficient software development process – meaning that only fundamental content is included. Thus, it does not provide guidance on many topics that projects may deal with, such as large team sizes, compliance, contractual situations, safety or mission critical applications, technology-specific guidance, etc. However,
OpenUP is complete in the sense it can be manifested as an entire process to build a system. For addressing needs that are not covered in its content, OpenUP is extensible to be used as foundation on which process content can be added or tailored as needed.
OpenUP is an agile process. Though OpenUP is lightweight, there is much more to agility than simply being light. Most recognized agile practices are intended to get a team communicating with one another providing a shared understanding of the project. Agile methods have drawn our attention back to the importance of coordinating understanding, benefiting stakeholders over unproductive deliverables and formality.
OpenUP has the essential characteristics of a lean Unified Process that applies iterative and incremental