Open Source Lifecycle

October 20 2007 | In Open Source | No Comments

Deciding how to develop or acquire open source systems is different than standing in the store looking at software boxes. Open source will continue to develop against a constantly evolving and improving background. If there was a defined open source lifecycle for the construction of open source data and processing techniques, maybe the open source lifecycle could mimic the lifecycle of building construction, occupancy, and upkeep. The tasks and roles are set forth in numbered groups below.

 

Jerusalem Gold, A Modern Approach to Tradition
by Isaac Brynjegard-Bialik at NiceJewishArtist

1. The Owner - has a holistic goal, a site, and a program. Before engaging an Architect and Contractor, the Owner (which may be a person or organization) defines:

1A - Scope of Work

1B - Payment Procedures (Bid, Negotiated, Manager, No Payment)

1C - Legal Needs

1D - Acquires Property if necessary

1E - Initial Community of Practice Survey in context of their goal

1F - Infrastructure Evaluation and Plans

1G - Assessment of Relevant, Existing Standards

1H - Initial Review of Compliance Procedures

1I - Survey of related government organizations and jurisdictions

1J - Reporting requirements

1K - Presentation and Communication Methods for this project

1L - Logistics, Delivery, Schedule

1M - Goals for Long Term, Slow Change to CoP and their goal

The Persona Lifecycle, Keeping People in Mind During Product Design

2. The Architect/Engineer

2A - Analysis

2B - Design

2C - Ontology

2D - Defines Performance Requirements

2E - Produces a Design that complies with code

2F - Develops Measurable Features

2G - Sets Limits

2H - Defines Controls

2I - Sets Specification Values

2J - System Function - Item Evaluation and Acceptance - Elimination versus Collection

2K - Conflict Resolution Procedures

2L - Corrective Action

2M - Documentation of Error Correction

2N - Approval Process

2O- Permit Review, a milestone set deadline

2P - Integration

2Q - Scheduling and updating fixed, released documents versus live participatory models

2R - Testing and Inspection

2S - Certification Requirements

2T - Workflow

2U - Configuration Selection

2V - Thinking

Life Cycle of a Bug Bugzilla

3. Structural

3A - Change

3B - Parts of a System

3C - Ranking and Classification

3D - Data, Equipment, Structural Modification

3E - Disposition, Effect of Permanent Removal of Previous Support

3F - Impact

3G - Mathematical Work

3H - Prediction of Slow Change and Settling Over Time

Technology Lifecycle Management Phunghi, Inc.

4. Contractor/Manufacturing

4A - Acquires Raw Materials, not property
4B - Purchase, Furnish, and Install

4C - Supply Chain

4D - System of Parts

4E - Physical Process

4F - Geographic Process

4G - Production Process

4H - Transportation

4I - Delivery and Acceptance

4J - As Built Documentation

4K - Activation

4L - Assignment

PR Lifecycle Model, Inoue Public Relations

5. Security vs. Public Systems

5A - Warehouse/Distribution Center

5B - Customer Payment

5C - Selling and Marketing

5D - Open Licensing

5E - Distribution

5F - Release

5G - Lawyer

5H - Comply with Governance Requirements
5I - Press

5J - Documentation

5K - Network Standards

Control Objectives for Information and related Technology (COBIT)
Information Systems Audit and Control Association

6. Monitoring

6A - Installation

6B - Audit

6C - Monitor

6D - Feedback and Error Correction

6E - Measure Impact

6F - Operations

6G - Maintenance

6H - Service

6I - User Manuals

6J - System Updates

Stained glass window available from Tenyes Glass

7. Community of Practice (CoP)

7A - Reintegration

7B - Giving

7C - Receiving

7D - Mining

7E - Discovery

7F- Evolution

7G - Slow Change

7H - Communication

7I - Story Telling

7J - Record Keeping

7K - Public Records

7L - Instruct, Learn, Teach, Train

7M - Collect

7N - Generate

________________

The interrelated cycle keeps going until a new owner sets a goal and decides to start a new project, the architect, structural, systems designers, reviewers, contractors, manufacturers, distributors, standards bodies, auditors, and CoP end users begin to implement their special areas of expertise again with more knowledge, better data, and more powerfully connected networks and machines.