rup

The RUP, working off the IEEE definition, defines architecture as 'the highest level concept of a system in its environment.

The result of this approach is a Responsibility Matrix defined as much as possible in terms of RUP roles and artifacts.

Sadly, RUP is often perceived to be in competition with a project management standard like PMBOK.

Proceeding on your own, with your team looking to you for guidance, can be difficult without prior hands-on experience in tailoring RUP.

For MSF, the word "discipline" refers to a more comprehensive and generic set of processes than in RUP.

Instead of defining the length of an iteration in a RUP project, the workload is always aligned with the 30-day length sprint.

The RUP consultant starts with an inventory session, during which all the stakeholders within the company are present.

However, it is often the case that team members play only one or a few RUP roles over the course of a single project.

But the opposite is not always true, because RUP has several artifacts that currently do not exist in MSF.

The deliverable would be a documented RUP process configuration as well as a more capable development organization.

This article is only a first attempt to formalize the method development process that the RUP team follows.

Along these lines, many PMs would like to see RUP Inception phase preceded by an additional period where such issues could be taken care of.

When organizations first adopt RUP, completing such a series of Development Cases can be an onerous, time-consuming process.

The basic development cycle was as shown in Figure 1 (which borrows heavily from the RUP).

To put it simply, RUP describes a development process in terms of phases that have iterations.

The project plan, like the rest of the RUP framework, is easily adaptable to projects other than software development.

The RUP consultant should see to it that any company-specific artifacts and roles do not overlap those already identified in RUP.

Many use one set of RUP processes for development (often deploying RUP process assets straightforwardly right out of the box).

A number of applicants for the position have the necessary work experience, but a few of them also are certified in RUP by IBM.

Within the informal work method of RUP, this is often unnecessary.

Likewise, using RUP as the foundation for an enterprise information architecture would be equally unjustified.

In fact, you need to learn all of RUP to be able to tailor it in a useful way, so you'll be very busy for the coming six months.

Or, you could define in your plug-in a replacing work product for a RUP work product that defines your own variant.

Many development teams choose to instantiate the RUP in an agile manner, and many others choose to borrow a few agile ideas here and there.

It is worth mentioning that several attempts have been made to extend the scope of RUP toward the enterprise as a whole.

It would be wonderful if all we had to tailor was the RUP Project Management discipline.

More formally, you could treat it as the equivalent of the RUP Software Architecture Document.

MDA is a new and emerging approach, and significant best practice with MDA as applied to RUP projects is only now becoming available.

Initiating, in red, is mapped to three RUP activities: Developing Business Case, Initiate Project, Initiate Iteration (also shown in red).

RUP's Define Test Approach consists of a number of steps, including the step called to determine the required depth of testing.

At the risk of sounding too much like a commercial, tailoring RUP is now easier than ever with the use of the Rational Process Workbench.

Liz, the IT manager, has decided to start with a proof of concept to evaluate the benefits of RUP tailoring.

A more effective solution is to enhance your existing RUP process framework to make it compliant with CMMI best practices.

Due to the complexity of this process, RUP describes it as a series of workflows and models that can gradually establish the system.

Although guidance for navigating workflows is included with RUP, it may be inapplicable or only a partial fit in real projects.

The TMap activities mentioned below are part of the Execution phase and are mapped to the corresponding RUP activities, shown in Table 5.

TMap is a very extensive and complete test approach, whereas in RUP, testing is just one of many aspects.

Set the right expectations. It takes more than one project to be an expert in RUP and the various IBM Rational products that support it.

Unfortunately, the PSP material cannot be applied directly by workers using RUP; it must be modified so that it suits the RUP context.

Note that we used the term "variation" in this template as shorthand for the RUP concept of alternate flow.

Like many other IT project participants, project managers often think of RUP as a single, out-of-the box process.

The result of this tailoring is part of what RUP calls a development case.

RUP and other iterative methodologies recommend that artifacts are kept up-to-date throughout the project.

Managers can also use this assessment to see where they might use RUP productively to supplement their organization's current processes.

A comparison of roles between RUP and MSF reveals one of the main differences between these process frameworks.

Some people try to organize it like that, and if you're starting out with RUP.

Fortunately, RUP is built upon an extensible architecture that allows you to use plug-ins to adapt the process to your needs.

A process engineering task requires good understanding of RUP taxonomy (meta-model) and availability of a consistent extension mechanism.

In each of these phases the RUP best practices give us the opportunity to verify the progress and quality of the project.

A Method Configuration is a characterization of a version of the method (like RUP for Small Projects and RUP for Large Projects).

The set of phases, iterations, and disciplines comprise the full RUP-based lifecycle, as shown in Figure 1.

In a previous section, we defined a model as a logical construct, according to RUP. We followed that with a definition of modeling file.

RUP Organizer allows you to create simple plug-ins that complement, without altering, RUP's underlying structure.

The discussion assumes a good understanding of requirements engineering using use cases and a basic understanding of RUP.

To obtain this experience, taking on an active role during activities throughout the RUP lifecycle is imperative.

As you will see in Part 2 of this series, RUP's Elaboration phase focuses on addressing technical risk early in the lifecycle.

As shown in Figure 3, during the service asset production phase, you may use supporting guidance from RUP for SOMA to model services.

This section includes materials to help you implement RUP for System z on your project.

Therefore, for RUP purposes, a model could be a drawing on a napkin or a whiteboard, something in a modeling tool, or even a mental image.

It also describes the main differences between the traditional waterfall development model and the RUP iterative development model.

The IBM Rational Unified Process, or RUP, is rooted in a set of best practices that address the challenges outlined above.

RUP describes testing as a means for continuously assuring quality throughout the software development lifecycle.

The RUP-inspired "rhythm of the iterations" is in full swing by Construction phase, and this heartbeat has particular relevance to testers.

The iterative nature of RUP will reveal our errors, and allow us to correct them with minimum damage to work we have already done.

RUP has no shortage of guidance regarding what needs to be done and when.

However, RUP has the principles of OOAD as its foundation, and therefore, does not lend itself easily to be aligned to SOA design.

The best place in RUP to do this is the Use Case Modeling Guidelines document.

RUP provides excellent guidance for this approach, and I encourage your organization to consider it.

The activities of the TMap Completion phase and its RUP counterparts are shown in Table 6.

Picture a salary negotiation with an employer who has deployed or wants to deploy RUP within the organization.

The architect, acting as an asset consumer, will typically search for assets during the Inception and Elaboration phases of RUP.

Over the years, the RUP team has adapted its own processes and techniques to the specific needs of method development.

In fact, RUP iterations can be visualized as being "mini projects" with a plan, deliverables, and assessment.

Also note that the risk stages align well with the Rational Unified Process (RUP) lifecycle phases, as shown in Figure 10.

A discipline in the RUP can be described as a grouping of interrelated activities and the artifacts or deliverables they produce.

Examples of a capability pattern from the base RUP include "use-case based requirements management" and "validate build. "

In the RUP, the Activity Prepare for Project Close-Out, found in the Transition Phase, calls for an update of the reference architecture.

With the plan approved and the use cases captured during the Inception phase, RUP steered the project the rest of the way.

From the viewpoint of RUP, the architecture of a system is the structure of its major components interacting via defined interfaces.

If an aim is to secure more time for business analysis or political maneuvering, it has little to do with RUP.

What does all this mean with respect to the activities described in the RUP SE plug-in?

RUP defines the AT insufficiently, merely as a rerun of a subset of the ST test cases.

It is unfortunate that RUP phases feel like they were extrapolated from a building development lifecycle model of the construction industry.

The opportunity to create C-RUP emerged as the result of several business drivers.

But an external RUP consultant will have limited knowledge about your business, not to mention your organization or company culture.

The Transition phase of RUP is focused on final delivery of the solution to its intended users.

For a test process in a RUP project, only tool support is specific, the other two are "business as usual. "

RUP is designed to be easily configurable for specific projects in specific organizational contexts.

A challenging aspect of introducing RUP into a traditional waterfall environment is that it urges far less reliance on sign-offs.

In the first scenario, the AT is implemented as a project on its own, which is executed independent of the remaining RUP projects.

RUP includes key principles around priority balancing, iterative development, visual modeling, software quality, and team collaboration.

Time compression in the Elaboration and Construction phases of RUP was where the team observed the greatest time savings.

It was important that the project be managed according to RUP principles for the PBR-UP technique to be applied.

As a Web-based solution, RUP extends easily to support your development team at all locations.

In a RUP project, the lifecycle consists of four distinct phases: Inception, Elaboration, Construction, and Transition.

The RUP product includes tool mentors that make it easier for teams to work with tools sold by Rational Corporation.

In contrast, RUP focuses mainly on the immediate business context for the solution to be developed.

In RUP, these patterns could be made available as design mechanisms that would increase code quality and boost development productivity.

All references other RUP elements had to the original work product will be automatically replaced with references to your element.

RUP defines the infrastructure at a later stage, known as Verify Test Approach.

RUP Modeler allows you to create structural plug-ins for RUP that change RUP's underlying meta-model.

These requirements artifacts become inputs to the subsequent analysis and design activities of the Analysis and Design discipline in RUP.

The long term vision included implementing the new system using RUP in conjunction with AMDD.

As proposed, IBM will donate major tool components and content from the next-generation RUP platform.

Since the third step of our process deals with actual code analysis, there is no equivalent discipline in RUP.

RUP for System z is based on RUP, an all-encompassing modern process framework applicable to any software development environment.

The set of questions is fixed, and is developed by a team of RUP specialists.

From a management perspective, the RUP software lifecycle consists of four sequential phases, each concluded by a major milestone.

As a consequence, junior RUP project managers may not follow RUP guidelines and fail to do thorough testing early on.

The latter is addressed in a joint realization table (JRT), an extension to RUP-SE's current service specification development artifact.

One of the misconceptions about RUP has been that it is a process rather than a process framework.

In RUP, this would be near the end of the Inception Phase.

The TMap phase Specification can be mapped to Test and Evaluate in RUP, as shown in Table 4.

It can be useful to extend or reduce the contents of RUP artifacts to meet the needs of the company.

Based on my experience, the column entitled "Review Type" in the RUP-provided Development Case is not adequate for a typical organization.

In Part One, I described some of the challenges with traditional approaches to DW development and how RUP addresses them.

Unlike the waterfall approach, RUP relies more heavily on expertise-based estimation, especially during the Inception phase.

The second one is rup_psm, the plug-in for PSM, or Practical Software Measurement, which supports a metrics approach for your project.

As I became more knowledgeable with RUP and the CMM, I added more artifacts, activities, checkpoints, and guidelines to the respective tab.

Systems Engineering is not obviously delineated as a separate discipline on the RUP Website.

Substituting a standard work product with a custom one is a common requirement during RUP tailoring.

First, where there is a RUP complement to your work product, does it in fact capture what you want?

With stakeholder agreement on your process story, you can now begin to identify key differences between your process and RUP.

Following RUP with the addition of codes of conduct can ensure, at a minimum, software financial information is accurate and reliable.

Rational Unified Process (RUP) for SOMA provides best practice offering accelerates this process, especially for modernizing legacy systems.

And although many organizations and projects tailor RUP to their own needs, the standard RUP framework is the subject of the certification.

A part of the RUP compile_software_development_plan task is to build an implementation plan for the whole project.

Demonstrations took place at several points in the ASDI project, but especially during the RUP elaboration and construction phases.

We recommend leveraging the RUP process framework with customized out-of-the-box delivery processes based on project needs.

Is it possible to take some of your work products and collapse them into a RUP work product?

Certified RUP specialists can be justifiably proud of their accomplishment.

Extend RUP workflows with accessibility-related activities, modifying existing workflow details rather than adding new ones.

Each slice of a cylinder represents a different discipline; according to RUP best practices, all disciplines are involved in each iteration.

The architecture-centric approach promoted by RUP leads to careful consideration and selection of various applicable architectures.

RUP has provided the framework in terms of iterations and organization of use cases.

It would be a better investment of time to stick with the RUP's project planning recommendations.

While there were a number of things we changed in going from waterfall to RUP, we didn't throw out everything from our original plans.

If the majority of the answers to these questions is "yes" , you should consider using RUP for your project.

As the RUP states, it is in closing out the project that architectural fruits are harvested.

RUP describes a software engineering process as activities, roles, and artifacts distributed across several disciplines.

For a complete list of roles and artifacts see the RUP Requirements Discipline Activities, Artifacts, and Workflow.

This article attempts to address this through extension and adaptation of the RUP framework to create more realistic schedules.

It is not known what parts of the process areas the RUP does not cover.

Second, RUP extends this definition by defining analysis classes in three disjoint categories: as entity, controller, and boundary classes.

Whenever the guidelines in the IBM RUP SE plug-in call for the use of a subsystem, you can simply substitute the contained system.

It should not be read as a summary of or primer for the RUP Test Discipline.

A sample hierarchical representation of the RUP meta-model is shown in Table 4 below.

Unlike PMBOK, RUP does not address project management as an end-to-end process.

The consultant can assist in modifying RUP templates to your needs and optimally using them as a tool for creating useful artifacts.

The method plug-in will gather all the additional and customized material created for the tailored RUP framework.

The common thread of those projects is their small size and RUP's ability to provide a rigorous and flexible methodology.

Now they want to go a step further in the process adoption, so they plan to adapt some parts of the RUP content to their specific needs.

This does not exclude the OO viewpoint adopted by RUP, but rather implements another layer of abstraction above it.

The following sections will describe a number of RUP-specific hints regarding test strategy development and test specification techniques.

Figure 6 illustrates how the PMBOK framework is implemented during each iteration within a RUP project.

RUP defines the end-to-end development cycle as an iterative process, as shown in Figure 3.

The importance of accurate estimation to a RUP project cannot be overstated.

Whether RUP is the best solution to a problem is a different question, however.

Over the years, the RUP Lifecycle Diagram shown in Figure 1 has been the classic way to represent the RUP interpretation of Boehm's model.

For instance, RUP has one administrator role, the system administrator.

The RUP Lifecycle Diagram depicts RUP along a micro-iterative dimension that adequately represents the effort required for small projects.

Just like RUP, OpenUP offers descriptions of roles, work products, and tasks that are essential to software development teams.

CLASP is available as both a stand-alone process and a plugin to the RUP environment.

Checklists based on personal defect data. The workers in the RUP do not perform reviews based on personal defect data.

Besides the fourth TMap activity, Preserving Testware, this RUP step also contains the evaluation of the test process.

In this phase, the objective is to prove the tooling architecture of your solution -- this is analogous to the RUP Elaboration phase.

As shown in Figure 1, organizations can use CMMI requirements to supplement the RUP plug-in in these two areas to achieve Level 2 maturity.

Newer or less experienced software engineers can use RUP as a map for communication and structured context.

A strong benefit of the RUP was its focus on mitigating risk.

Adopt RUP best practices and be guided by the spirit of RUP. Restructuring your project plan is not enough.

RUP acknowledges four levels of testing: unit testing, integration testing, system testing, and acceptance testing.

Similarly, specific combinations of asset lifecycle use-case activities and RUP activities can correlate with certain RUP phases.

During my years as the "RUP curmudgeon, " I had the opportunity to visit and observe many customers.

It is also important to understand the way the MDSD plug-in is articulated with respect to the rest of RUP.

I also added a sample non-RUP organizational-specific work product -- a Questionnaire -- for eliciting stakeholder requests.

MDSD inclusive of the existing RUP disciplines is, however, a Systems Engineering lifecycle process.

RUP includes workflows and templates that you can use to configure the basic unified process framework.

Where RUP can really help these situations is by helping teams to recognize that all iterations are not the same.

The RUP and other agile software engineering processes are capable of addressing these challenges.

Here, we indicate a number of the important aspects to consider in applying RUP to an MDA project.

As shown in Figure 2, each iteration in the RUP is a pass through the disciplines.

The four phases in a RUP project represent different project styles in the software engineering process.

More pervasively, the primary changes to RUP consist of a more subtle change of perspective on the development process.

Amid the swarm of overlapping methodologies, these stand apart as three pillars of modern information systems architecture.

This installment discusses the team's progressing into implementation, and hence into the RUP's construction phase.

Like RUP, Scrum does not force teams to build specific visual artifacts, but rather delegates this to the Scrum team.

RUP's testing recommendations comprise unit testing, integration testing, system testing, and pilot testing.

Unfortunately, many such managers say they are using RUP for a project, but they revert to waterfall techniques.

The RUP enforces requirements management throughout the lifecycle.

Most of the tasks and work products required to reverse-engineer a system can be found in RUP.

A RUP-based project may have anything from one (generally a bad practice) to a dozen or more iterations.

Figure 11 shows the extent to which the RUP and TOGAF lifecycles overlap.

The application of MDA involves many RUP roles, but they typically will not require additional activities.

A number of documents we planned to produce on our waterfall project we still planned to produce on our RUP project.

Because we were largely working within the RUP framework, this worked well for us.

To share process changes within the organization, the process engineer releases the process via RUP Builder.

Experienced RUP mentors can help remove work products from the Development Case that will never be necessary for your organization.

I believe testers have the opportunity to contribute broadly to the project in each of the RUP phases.

It is important to note that no explicit test activities take place in this TMap phase, whereas this is the case in the RUP workflow.

However, developing a method framework like RUP is not quite the same as developing a software application.

The asset lifecycle is exercised within the confines of a project, which is where we see most of RUP applied.

This is such an important thing that the RUP includes the Configuration and Change Management discipline which specifically addresses it.

Note: Analysis-level models often evolve into design-level models, so there's only one RUP discipline for analysis and design.

This demonstrates the incremental aspect of RUP: each task, or iteration, builds on, and adds to, the work done previously.

Her workflow will be composed of RUP process-related metrics and graphs as well as RUP artifact and activity summaries.

It is worth mentioning the central role played by the use-case model in this work as in any RUP-based software development project.

The section on Rational Method Composer plug-ins for asset-based development and RUP for SOMA provides more information on this topic.

Scrum and XP are squarely in the Agile sector while RUP and Evo are more in the traditional (plan-driven) iterative camp.

The RUP encourages architecture teams to prove their architectural concepts by executing prototypes.

I strongly recommend RUP; even as PMBOK will normally act as an anchoring project standard.

Existing approaches like SOMA, and using RUP as the overall framework, can help guide the discussion.

As we noted earlier, RUP can be adapted to become an integrated development framework for accessible design.

As described in the previous chapter, these tests are not described in enough detail in RUP to do a thorough mapping process.

RUP is sometimes seen -- rightly or wrongly -- as a method with a high level of process ceremony.

Often, first timers proclaim that they "get RUP, " then turn right around and use a waterfall method to install "The New Process. "

RUP provides no implementation of the Supplier Agreement Management process area.

The RUP process framework can serve as a guide, providing useful steps and artifacts to consider.

You can persuade the client that using RUP will further enhance the value of these tools.

These perceptions would make it more challenging for us to apply the RUP in the best possible way.

Figure 4 shows the flip side to this view wherein asset-based development fits into the service modeling stages specified by RUP for SOMA.

Table 1 shows RUP-SE's typical system modeling viewpoints, as well as sample development artifacts produced for specific model levels.

Rational Unified Process is the de facto industry standard for project lifecycle development and management.

This illustration also shows the steps recommended by RUP within the context of Use Case Analysis.

Many of the iterative and incremental approaches encouraged by the RUP had good justification, and ASDI was seeing the benefits.

Embedding this approach into a proven process framework, such as RUP, is an ideal way to introduce it into a development organization.

As we mentioned earlier, this series of articles considers the analyst, architect, and developer roles, as defined by the RUP.

Below I provide several examples of how you can use the Extension-Definition template to capture RUP customization requirements.

Here I was, writing about a software development process, and to do this I was using a course development process that mirrored RUP itself.

Now that we have this use case as a starting point, let's follow the RUP steps of Use Case Analysis.

These two dimensions, "Validation" and "Verification" traceability, are illustrated in Figure 1 with reference to the core RUP disciplines.

RUP with the MDSD plug-in is a systems engineering process for which software engineering (via RUP) then becomes a subset.

The RUP role of test designer defines and implements the test approach, including techniques, tools, and procedures.

One of the key artifacts in the RUP framework is the project plan.

This is precisely the reason why IBM Rational developed systems engineering extensions for RUP, more commonly known as RUP-SE.

Despite all these deficiencies having been addressed long ago, the perception of RUP as a ceremonial and stiff process still exists.

The RUP tool helped us understand and communicate the roles, tasks, and responsibilities of the team.

This should not cause any confusion, but the RUP terminology uses a different name for similar key concepts.

In RUP terms, we rebuild the Business Use Case and its Business Analysis Model.

To answer this question, you need to understand both RUP and CMMI.

Remember that unlike pure Agile methodologies, with RUP each iteration is not treated the same.

The RUP provides a framework of rules and practices that mitigate the unpredictability of software development.

Fortunately, many of these guidelines already exist in RUP and other respected sources, so you need not write them yourself.

RUP uses a master test plan for the overall project and an iteration test plan per iteration.

Table 4 is a snapshot of the process elements that need to be created or enhanced in RUP for addressing compliance with CMMI.

As in the RUP Elaboration phase, this phase of the change initiative focuses on reducing risk.

When an organization starts a RUP project, it generally tries to use known methods as much as possible for maximum efficiency.

This template follows IBM Rational Unified Process (RUP) methodology guidelines.

The RUP does not provide an answer to this issue of employee competence.

And, compared to other system development methods, RUP provides detailed test instructions.

RUP is a risk-driven, use-case-based, and architecture-centric, iterative software development process.