Management and Organizational Issues

(click to go to roadmap)

WISR 1 - Human Roles (Bailin, Gilroy, Wartik, Latour) (click to go to overview)
WISR 4 - Towards a Reuse Handbook (Griss)
- Parts:
  - A two-volume set: startup and steady state
  - Separate volumes for managers, producers, consumers
  - Standard set of relatively independent modules (towards Griss Domain Specific Toolkits - to overview)
  - Need for reuse metrics
  - Scalability
  - Practically useful principles for components (and, oh yes, other design entities, whatever they may be)
- Handbook issues:
  - Handbooks will be huge
  - Teaching must be "operationalized"
  - Basic principles exist:
    - black-box components
    - encapsulation
    - unbreakable abstraction
    - and extension by addition only
    - (hmmm... local certifiability)
WISR 4: Reuse Driven Lifecylcle Maturity Model (Joos)
- Goals: To develop a Maturity Model Matrix measuring reuse related factors
- Factors:
  - Motivation/Culture
  - Planning for Reuse
  - Breadth of Involvement
  - Responsibility for making reuse happen
  - Reuse implementation process
  - asset inventory
  - classification activity
  - technology support
  - metrics
  - legal, contractual, accounting considerations
WISR 5: Management and Tech Transfer (Joos, Griss, Tirso)
- Goals: To discuss Do's and Dont's in management, organization, champions, economics, and metrics
- Issues:
  - Management goals and incentives
  - Education and training
  - Implementation structure
  - Metrics
  - Economic Models
  - Tech Transfer of above
  - classification activity
  - champions
  - maturity and process models
WISR 5: Industry Perspective (Yglesias)
- Goals: To determine issues for further study
- Issues:
  - practical domain analysis, with guidelines
  - specific domain modeling methods
  - systematic design approaches
  - reverse engineering
  - Economic Models
  - generators
  - automated certification
  - language enhancements facilitating reuse
  - specific OO reuse methods
  - metrics
WISR 6: Management Issues (Patricia Stump, Terry Huber) (click to go to overview)
- Goals: To explore impact of reuse on business practices - especially differences in incentives and customer involvement
- Case: HP's Flexible Software Factory Model:
  - Customer and Values Elements
  - Business System Elements
  - Structural System Elements
  - Support System
  - People System
- Factors affecting reuse potential
  - Market Potential
  - Commonalities
  - Domain standards, stability, maturity
  - existing assets
WISR 6: Technology Transfer (Bailin) (click to go to overview)
- Goals: To explore the following technology transfer issues
- Issues:
  - What is it?
  - Does Reuse require special approaches?
  - How is it done well?
  - What drives it?
  - Who pays for it?
  - How do we speed it up?
  - How do we advocate for it?
  - How do we measure it?
  - Who are the "players" and what are their roles?
- Recommendations
  - Identify key players and use "pull"
  - Position customer closer to user
  - Reuse other TT efforts
WISR 7: "The Organization" (Benner) (click to go to overview)
- Goals: To explore systematic software reuse within the context of a real example (modeled after Andersen)
- Strategic Activities:
  - Reuse Planning: assessment of business env, scoping (kits), infrastructure planning, project planning
  - Reuse Infrastructure development: educational, technical, incremental improvement
  - Tactical Reuse Activities - Asset creation, management, and utilization
- Recommendations
  - Goal: to reuse, without mods, 60-80% of existing modules
  - Tools:
    - improve user understanding of system design and architecture (framework for repository)
    - improve versioning capability
    - improve traceability
  - Process: can it be generalized past the single customization example?
  - People: steps must be taken for extensive training and education
WISR 7: Domain Processes and Engineering (or, more aptly named, "Domain Engineering as Theater") (Bailin) (click to go to overview)
- Goals: To use a "theatrical script" technique to document the sequence of events that play out between "players" in the organization
- Characters: GM, Director of Tech., Portfolio Manager, Project Manager, SE, Domain Analyst, Domain Expert, Domain Model Maintainer
- Plan: perform "mini"-domain analysis to identify common component needs rapidly.
- Outcome: Goal not met, but close enough to present DA results to portfolio manager. Unfortunately it's incompleteness provided ammunition for sabotage. Issue of asset ownership not resolved.
WISR 7: Barriors to ISR using current T&E (click to go to overview)
- Barriers:
  - Adaptation
  - Education vs. Cost
  - Metrics
  - Standards
  - Management
  - Tool Availability