Valour (software)

Valour is a copy/backup/restore program for IBM's VM environment.

## The product

[edit]

Valour, also called DiskWorks as well as strategic marketing brands chosen by vendors, grew out of a plan to rewrite the aging Westinghouse Disc Utility (WDU) and target the full range of IBM operating systems.

Valour runs as a highly privileged CMS task, designed to accommodate any model disc drive or tape drive. The product incorporated a number of unique concepts and technologies. It was one of the earliest products to use a primitive form of windowing, including dialogue boxes capable of real-time updates.[1]

The product offered a wide variety of hierarchical backups, data streaming, alternating tape drives, and an ability to defragment minidisks.[1]

## Development

[edit]

Valour, also called DiskWorks, grew out of a joint effort between Westinghouse and III of Orlando, Florida. Original plans called for both VM/CMS and VSE versions led by Dr. Ray Ferguson of Westinghouse and Leigh Lundin of III. John Gaston was selected to lead the VSE team. Part way into development, Westinghouse began to break up the division during the outsourcing thrust of the Reaganomics era. Through badly managed negotiations, Westinghouse ended up with neither developers or outsourcing partners, which spelled the end for one of the industries foremost software groups.

The VM product was developed by III (Independent Intelligence Incorporated) of Orlando, Florida. The software designer was Leigh Lundin. Other core developers included Dr. Ray Ferguson, Kevin Beauregard, Mark Woodruff, and Jean-François Groff.

Product development occurred at III offices within Westinghouse Automation Intelligence division, Orlando, Florida. Broad range in-depth testing was conducted at IBM's data center in Tampa, Florida and the IBM lab in Böblingen, Germany.

The team first built an OOPS environment using a combination of procedural Rexx and assembler language. Valour may have been one of the first commercial products that looked to object-oriented programming to underpin its development platform.

Development brought new techniques and concepts, including its own hi-speed access method, network hierarchical data structures, windowing, and a buffer block concept referred to as granularity.

## Marketing

[edit]

The product had a feature unique for its time. By changing a table and a splash screen, the product could be re-labeled or re-branded for any distributor in any Roman language. As such, the product was localized for France, Germany, Switzerland, and Netherlands, each with local marketing companies. III contracted with distributors using a non-exclusive license.

For example, the distributor in the US branded it USR/Backup,[2] while a German company, SysCon, labeled it SysCon/I.[3]

Westinghouse Electric Management Systems, SA (WEMSSA), Paris, London, Geneva, Zürich, Munich, and Amsterdam, acquired the marketing rights, initially for Europe, Africa, and the Far East. Westinghouse Electric, Pittsburgh, subsequently acquired rights for the Americas.

Through legal agreements, III then contracted with other companies and distributors.

Over time, Valour (DiskWorks) replaced competing products [4] acquired by Dowling Associates of Dublin, Ohio.

## References

[edit]

1. ^ a b Valour User Manual © 1999
2. ^ USR sales literature © 1998
3. ^ SysCon brochure
4. ^ VM Software's Backup/CMS

* v
* t
* e

Software distribution

Licenses|

* Beerware
* Floating licensing
* Free and open-source
* Free
* Open source
* Freely redistributable
* License-free
* Proprietary
* Public domain
* Source-available

Compensation models|

* Adware
* Commercial software
* Retail software
* Crippleware
* Crowdfunding
* Freemium
* Freeware
* Pay what you want
* Careware
* Donationware
* Open-core model
* Postcardware
* Shareware
* Nagware
* Trialware

Delivery methods|

* Digital distribution
* File sharing
* On-premises
* Pre-installed
* Product bundling
* Retail software
* Sneakernet
* Software as a service

Deceptive and/or illicit|

* Unwanted software bundling
* Malware
* Infostealer
* Ransomware
* Spyware
* Trojan horse
* Worm
* Scareware
* Shovelware

Software release life cycle|

* Abandonware
* Long-term support
* Software maintenance
* Software maintainer
* Software publisher
* Vaporware
* list

Copy protection|

* Digital rights management
* Software protection dongle
* License manager
* Product activation
* Product key
* Software copyright
* Software license server
* Software patent
* Torrent poisoning

* v
* t
* e

Software engineering

Fields|

* Computer programming
* DevOps
* Empirical software engineering
* Experimental software engineering
* Formal methods
* Requirements engineering
* Search-based software engineering
* Site reliability engineering
* Social software engineering
* Software deployment
* Software design
* Software maintenance
* Software testing
* Systems analysis

Concepts|

* Abstraction
* CI/CD
* Compatibility
* Backward compatibility
* Compatibility layer
* Compatibility mode
* Forward compatibility
* Software incompatibility
* Component-based software engineering
* Data modeling
* Enterprise architecture
* Functional specification
* Modeling language
* Programming paradigm
* Software
* Software archaeology
* Software architecture
* Software configuration management
* Software development process/methodology
* Software quality
* Software quality assurance
* Software system
* Software verification and validation
* Structured analysis
* Essential analysis

Orientations|

* Agile
* Aspect-oriented
* Object orientation
* Ontology
* SDLC
* Service orientation

Models|

| Developmental|

* Agile
* EUP
* Executable UML
* Incremental model
* Iterative model
* Prototype model
* RAD
* Scrum
* Spiral model
* UP
* V-model
* Waterfall model
* XP
* Model-driven engineering
* Round-trip engineering

|

Other|

* CMMI
* Data model
* ER model
* Function model
* Information model
* Metamodeling
* Object model
* SPICE
* Systems model
* View model

Languages|

* IDEF
* SysML
* UML
* USL

Systems design|

|  Requirements|

* Functional requirement
* Non-functional requirement

|

Capacity|

* Users
* Compute
* Memory
* Storage
* Network
* Web traffic

Interface|

* API
* SOAP
* REST
* GraphQL
* gRPC
* Webhook

High-level design|

* Client
* Load balancing
* Application server
* Message queue

Integration|

* Vertical
* Peer-to-peer
* API Gateway
* pub-sub
* Event Source
* ETL
* Batch
* Stream
* Orchestration

Architectures|

* Monolithic
* Microservices
* Event-Driven
* Client–server
* Serverless
* Circuit breaker
* Rate limiting

Database|

* Relational
* NoSQL
* Graph
* Key–value
* LSM Tree
* Time series
* Column Oriented

Principles|

* Consistency
* Reliability
* CAP theorem
* Maintainability
* Configurability
* Modularity
* Durability

Scalability|

* Stateless
* Asynchronous I/O
* Loose coupling

Availability|

* Fault tolerance
* Failover
* Single point of failure
* Replication
* Consistent hashing
* Circuit breaker

Latency|

* Cache
* CDN
* Shard
* Database index
* Pre-caching

Storage|

* Object storage
* Block storage

Observability|

* Logging
* Metrics
* Tracing
* Error rate
* Queries per second
* Notification system
* Anomaly detection

Related fields|

* Computer engineering
* Computer science
* Information science
* Project management
* Risk management
* Systems engineering

* Category
* Commons

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template