|
Home
News
Offerings
Services
Training
Products
Partners
Contact Us
myAPG
Public training
calendar

ISV and Partner
Reseller and Partner
Reseller and Partner
Influencing Member
Architecture Forum Member


Advisory Group Member
|
|
OpenUP
|
Overview |
|
OpenUP (Open Unified Process) is an open-source
software development process framework that covers a
broad set of development needs. OpenUP takes an agile approach to
software development, providing only the most
fundamental content needed to describe a simple set of
work products, roles, tasks, and guidance.
OpenUP is a result of the Eclipse Process Framework (EPF) project.
Click here to view OpenUP online, right now!
|

|
|
|
Features & Benefits |
- Sustainable agile software development
- Iterative and risk-driven
- Minimally sufficient for small, co-located teams
- Extendable to meet needs of larger teams and more complex environments
- Four integrated sub-processes
- Collaboration and communication
- Management
- Intent
- Solution
- Described with roles, tasks, and activities
- Supporting guidance (checklists, templates, guidelines, examples)
- Open source
|
|
Description |
|
OpenUP/Basic is a common language – a common way of doing things – that
aligns how stakeholders and practitioners understand a project. It 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 is characterized by four mutually supporting core principles:
- Collaborate to align interests and share understanding
- Balance competing priorities to maximize stakeholder value
- Focus on articulating the architecture
- Evolve continuously to obtain feedback and improve
OpenUP/Basic is ready to use as-is; nothing needs to be added or removed.
OpenUP/Basic also serves as a foundation on which process content can be
added or tailored using the EPF Composer tool.
“OpenUP is the least amount of process for any project; but not all the
process for every project.” – Chris Armstrong
|
|
Screenshots |

Introduction
|

Lifecycle
|

Inception
|

Role: Project Manager
|

Task: Plan Project
|

Example: Project Burndown
|
Click on images to enlarge |
|
|
Audience |
- Process architect
- Process author
- Process coach
- Project manager
- IT manager
|
|
|
System Requirements |
- Mozilla Firefox 1.5+
— or —
- Microsoft Internet Explorer v6.0+
|
|
|
|
|