What are the advantages of RAM over Sharepoint, how is it different from what Sharepoint does?
I am trying to write up the business case for getting RAM and wanted to know what the advantages of RAM are over Sharepoint. How is RAM different from Sharepoint
|
One answer
IBM Rational Asset Manager is used to catalog, govern and share software and systems development assets. Catalog, govern and share formal outputs to: · Enable strategic reuse of designs, business cases, code, components, tests and more · Discover information about enterprise assets, how they relate, who owns them and where to get them · Improve the efficiency and quality of formal hand offs
Unlike wiki's, source control, Sharepoint, file systems, document management systems, or other generic solutions, Rational Asset Manager (RAM) has been purpose built to function as a definitive library, so you can:
• Deliver solutions faster by using or referencing approved deliverables and information, governed in the definitive library
• Improve quality by involving all the necessary stakeholders in the governance of shared deliverables; resulting in approved, published, auditable software and business assets
• Reduce delivery risk by being more consistent and using pre-existing materials hardened, tested, and packaged (commercial and pre-approved open source software), resulting in increased quality and reliability of solutions
• Lower communication and collaboration costs by enabling a single source of truth so you can understand what assets they have, how they are related and are driving business value
RAM provides friendly and easy to use web access to business and other non-development stakeholders. It integrates with the development platform including Eclipse-based IDE's and Jazz-based products to provide in-context sharing and linking of development assets throughout the application lifecycle. It provides out of the box integrations with Tivoli CCMDB, WSRR, Lotus Connections, and common SCM tools. It provides a fully documented API for integration with other systems.
The patterns of usage include: · Enterprise ALM · SOA Governance · DevOps · Information / IP management
Address Customer Pain Points: • Awareness that teams are solving the same or similar problems, thus duplicating effort with skyrocketing costs• Difficulty keeping stakeholders engaged in the decision making, resulting in deliverables that lack sufficient quality checks • Compliance mandates and lack of policy enforcement results in unmanaged risks, such as using unapproved open source components • Not getting promised value of Agile, SOA or globally distributed development, because the deliverables produced by geographically distributed teams cannot be discovered, approved and reused • Difficult to identify assets and resources that are driving business value resulting in improper resource allocation |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.