This presentation provides a framework for developing and maintaining a reusable software component repository. It focuses on establishing effective systems to enhance reusability through useful and traceable components. The repository aims to increase qualified reusable components using a "reuse first" approach backed by a mature repository management system and smart selection options for users. This is intended to yield greater benefits through reduced effort, time, and improved quality. The presentation outlines aspects of the repository such as architecture, types of components, submission and review processes, search and retrieval, governance practices, and a culture of rewarding contributors and users to encourage participation.

1. SOFTWARE REUSABLE
REPOSITORY MANAGEMENT
VISHNU VARTHANAN MOORTHY
10 FEB 2018

2. REUSABLE REPOSITORY MANAGEMENT
Objective:
This presentation provides a basic framework for developing and maintaining the Reusable Repository for software
components. The focus is on enhancing reusability by establishing effective system , useful components with improved
traceability.
Focus:
Addition of Assets in repository can be focused to Technology & Domain. Encouraging Assets which are White Box in nature, where modification
of code/content is possible is a preferred option compared to Black Box /compiled codes/unmodifiable contents usage.
Repositories can be focusing on Related Asset building for any given area (ex: a domain/type of lifecycle/platform/technology) or Having assets
which can be used in multiple conditions/multiple platforms. Repository focus should be based on what benefit the user community will get and
how that in turn will impact overall business results. The benefits can be effort , time saving or complexity addressing or Quality improvement,
etc
Increase of ‘Qualified Reusable Components’ with a ‘Reuse first’ Approach backed by a ‘matured repository’ management system practices and
‘smart select’ option for user can yield greater Benefits.

3. SOFTWARE REUSABLE REPOSITORY MANAGEMENT - ARCHITECTURE
Component
Submission
Self
Declaration
L1 Review by team
L2 Legal Check –
With Contributor
Submission Category
& Agree on Terms
User Submitted – Not
Reviewed
Reviewed and
Accepted – Silver
Standard
IP Cleared – Gold
Standard (on
Demand/ based on
Category)
Published
User formally claims the
Copyright and asks for
legal review
Submission and Validation
Subscription, Maintenance & Auto
Expiry Usage & Rating
Contributor/proj
ect team
Auto Alert on
Publishing All Subscribers
Monthly Newsletter All Subscribers
Top 20 Assets -
Highlight
New Assets -
Highlight
Auto-Expiry after X
period & usage
based Renewal
Contributor &
Subscriber Informed
Inform retired asset
list
Text Analytics
Search
Advanced Search
Views & Downloads
Count
Likes & Rating
Content
Credit Score for
Contributor on
Crossing threshold
of Download
Quarterly Credit
Score
Effectiveness
Reporting
Text Mining based
solution
Download Terms
Acceptance
Usage of
Components as per
terms in contract
Reusable Components Repository
Retrieval Logic

4. COMPONENTS IN A REUSABLE REPOSITORY
Reusable Repository
Java,.Net,
Python, SAP,
etc Criteria for use,
recommended
context
Technology
Usage Context
Saving effort,
time & Improve
Quality
Benefit
Script, Program,
utility, manual
Type of Component
Additional
Component,
Steps involved,
etc
Dependency Details
Limitation with
Server, OS, IDE,
etc
Compatibility
Conditions
• Design Documents
• EXE files
• Source code
• Test Scripts
• Installation manuals
• Algorithms
• Business flows
• Utility programs
• Interfaces
• Specifications
• Plugins
• Others
Selection of a Tool with publishing abilities, alert system, good search, feedback abilities
plays vital role in enabling reusability and a good system for repository

5. SUBMISSION OF ASSET – ADDRESSING IP, REVIEW & RETRIEVAL NEEDS
Submitted by
Email Id
Project Id
Other Contributors
Date of Creation
Type of Asset
Program/Interface/Logic/Architecture/Docume
nt/test script/etc
Technology
Java/Python/.Net/SAP/Oracle/etc
Domain
Healthcare/Insurance/telecom/etc
Benefit Area
Design Complexity /Code Maintainability/Quick Test/Defect
reduction/etc
Self Created Y/N
Project Team Created
Y/N
Project Contract Do have
any IP Clause Y/N
Known Client Component
Involved
Y/N
Cleansing of Confidential
Data Completed
Y/N
Usage of Asset Needs Any
additional Permission Y/N
Contains Third Party/Open
Source material Y/N
Description of Asset ( in 250
words)
How the Asset was used in Original
Context ( in 100 words)
Interoperability of Asset
Supportive Asset
Attached/Reference
Dependency if any for Using
Usage Instructions
User Submitted Fields
Gold Status Requested Y/N
User can request a Gold Status when an Asset Significantly
reduces effort & legally it can be claimed as IP ( if needed can be
registered)
*Open Source/Third party Assets can be given as a “Reference” in Repository only
with Metadata and disclaimers. This will increase usage and Single Store view to
users.

6. REVIEW OF ASSETS –CATEGORIZATION & CERTIFIED ASSET
• Description of Asset
• Category selection
• Submission legal claims
• Completeness and Consistency of data
submitted with asset
• Asset Navigation for Accuracy
• Cleansing Completeness
Primary Validation for ‘All’
Assets
• Origin of Asset and References
• Demo case of application
• Benefits claim verification
• Client/management
Approval/acknowledgements
• Interoperability and application
Secondary Validation for
‘Gold’ Assets*
• Related Client Contract Check
• Review of any open Source/Third
involvement
• IP Clauses Check
• Marketable Solution (Only for I.P
Registering)
• Copyright usage for non marketable
Assets
Legal Validation for ‘Gold’
Assets*
Cross skilled Team – 3 to 4
People
SME – 3 to 4 People
Legal or DPO office
Request
Additional
Information
Published- Not Reviewed
Published- Reviewed and Validated
“Silver”
Published- Reviewed and Validated
“Gold”
Contributor
It can be a “Gold” Asset or ‘Certified’ Asset

7. MAINTAINING THE REPOSITORY
Regular Review of System
• Integrity Check
• Accuracy of information
• Links working
• Completeness information
Address - User Reported Feedback
• Copyright Violation reports
• Inaccuracy of information
• Needs more information and
support
• Visible Feedback
• Mail id to Connect
Asset - Retirement
• Liver Duration
• Auto-retirement
• Unused Assets by Size ratio
• Renewal of Auto-retirement
period based on usage
Asset Addition
• Confirmation to Contributor
• Publishing Status
• Auto-mailer to Subscribed users
• Monthly Newsletter/mail on
Additions
Asset Upgrade
• Newer Version of Asset
• Modification requested by
Contributor
• Enhanced Interoperability
• Self declaration – mandate on
update
Asset Metadata change
• Additional Contributor
• Additional links/ asset
connector with existing one
• Any IP claim change –Need
Complete review cycle
Admin&
Contributor
Administrator
Automated Publishing Systems can reduce the role of Admin to large extent

8. EASE OF ASSET RETRIEVAL – INCREASING REUSABILITY
Ex: Maps interface code or API
Smart Search Enabling
Advanced Search Enabling
Domain Technology
Design
Related Component found
Google maps interface
Maps interface test cases
Building custom maps
Google Maps
Interface
Other Users Downloaded
Map of
world
Interface
Download
Agree on Terms of Usage and Aware of Reusable
components usage conditions
This component is written in Java for application
interface with ……..
Description
This component will connect……..
Context of usage
Your Rating
Avg. User Rating
Contributor@Company.com
Planning to use this Asset Y/N

9. CULTURE ENABLING REUSABILITY
Measurements for RepositoryContributor Reward System
• Number of Hits
in a Month
• Number of
Downloads
Percent of Assets
in a Rating Level -
Distribution
Ratio of Asset
Viewed/Total
Assets
Asset Addition Per
week
No. of users
subscribed
Potential Effort
saving per month
No. of
components used
in Project
Potential Effort
Saving in Project
Opportunity vs
Reusable
Component
utilization (%)
Reusability in Project
• Threshold Based Monitoring
• Breach of threshold needs warrants a Drive to pull more user and Contributors
• Targets can be of positive nature than mandatory/negative nature (raises
quality issue)
• Auto mailer of
Acknowledgement
• Top Contributor in Quarter
– Certificate
• Mailer on Top 10
Downloaded Asset in
month
• Reward points on Every Reviewed
Asset ‘10’
• Yearly Accumulation of more than
’50’ points – rewards can be
planned
• Every Gold Status /Certified Asset –
A online certificate and 50 points
additions
User Reward System
• User Submission of ‘Usage’
details – Acknowledge mail
• Quarterly Certificate on
‘user/project’ for maximum
usage of reusable
component
• Reward points on Every Usage
context and Review Submission– 5
points
• Additional Points on Every Sample
submission and Benefits data – 5
points
• Reward claim upon ‘100’ point
Discussion Forums and sharing of assets can be linked with the Reusable
Repository

10. THE END
PLEASE CONNECT : VISVARTHANA@GMAIL.COM