Posted under Uncategorized od on czwartek 6 listopad 2008 at 2:13 przed południem
Valour is a copy/backup/restore oprogramowanie for IBM's VM environment.
Contents
//
The product
Valour, also called DiskWorks as well as strategic marketing brands chosen by vendors, grew out of a projekt 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 wzór 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.
The product offered a wide variety of hierarchical backups, termin streaming, alternating tape drives, and an ability to defragment minidisks.
Development
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 ekipa. However, part way into development, Westinghouse began to break up the division during the outsourcing thrust of the Reaganomics epoka. 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 prekluzja center in Tampa, Florida and the IBM lab in Böblingen, Germany.
The ekipa 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 termin structures, windowing, and a buffer block concept referred to as granularity.
Marketing
The product had a feature unique for it's time. By changing a table and a splash screen, the product could be re-labled or re-branded for any distributor in any Roman language. As such, the product was localized for France, Germany, Switzerland, and Nederlands, 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,
Westinghouse Electric Management Systems, SA (WEMSSA), Paris, London, Genève, Zürich, München, and Amsterdam, acquired the marketing rights, initally 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 acquired by Dowling Associates of Dublin, Ohio.
Development models: Agile • Iterative wzór • RUP • Scrum • Spiral wzornik • Waterfall wzór • XP • V-Model
Process models: Function forma • Information wzornik • Object model
Data models: Termin wzornik • Database model
Software engineers
Charles Bachman • Kent Beck • Tim Berners-Lee • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham • Edsger W. Dijkstra • Wolumen Gruber • Michael A. Jackson • Ivar Jacobson • James Martin • Winston W. Royce • James Rumbaugh • Edward Yourdon
Posted under Uncategorized od on środa 5 listopad 2008 at 6:25 po południu
Virtue is a virtual session manager running under IBM's VM.
Contents
//
The product
Virtue , "virtual tube", was the first session manager commercially available for the VM environment on IBM mainframes. The product allows users to use a kanon 3270 monitor to control multiple sessions, whether VM/CMS, DOS/VSE, z/VSE MVS, z/OS, or other operating układ or application such as CICS, Westi, or DUCS sessions.
Virtue runs as a highly privileged CMS task, designed to accommodate any szablon IBM 3270 monitors and their descendants. Even after competition entered the sklep wielkopowierzchniowy, the product remains known for its innovation, speed, and compact size.
Development
The product was developed by III (Independent Intelligence Incorporated) of Orlando, Florida. The software designer was Leigh Lundin.
Although the package nominally ran as a highly privileged CMS session and utilized CMS services, it deployed an internal multitasking mechanism called a subvisor, which queued and prioritized tasks to be done. Macintosh versions prior to OS/X and IBM's OS/2 came to use similar mechanisms for task control.
Product development occurred at III offices within Westinghouse Automation Intelligence division, Orlando, Florida. Broad range in-depth testing was conducted at IBM's prekluzja center in Tampa, Florida and the IBM lab in Böblingen, Germany.
Marketing
Westinghouse Electric Management Systems, SA (WEMSSA), Paris, London, Genève, Zürich, München, and Amsterdam, acquired the marketing rights, initally for Europe, Africa, and the Far East.
Westinghouse Electric, Pittsburgh, subsequently acquired rights for the Americas.
After release, a number of competing products entered the sklep wielkopowierzchniowy, including MultiTerm and Computer Associates' vTerm, also known as vGraf. The concept found its way onto early PC platforms at the time, notably Apple Computer's Switcher for the Macintosh and subsequent products for the IBM PC.
Development models: Agile • Iterative wzór • RUP • Scrum • Spiral wzornik • Waterfall szablon • XP • V-Model
Process models: Function krój • Information wzornik • Object model
Data models: Termin wzór • Database model
Software engineers
Charles Bachman • Kent Beck • Tim Berners-Lee • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham • Edsger W. Dijkstra • Wolumin Gruber • Michael A. Jackson • Ivar Jacobson • James Martin • Winston W. Royce • James Rumbaugh • Edward Yourdon
Posted under Uncategorized od on niedziela 2 listopad 2008 at 10:22 po południu
Swiss Made Software is a label for quality software produced in Switzerland. It was first created in 2007 and has been adopted more than 75 companies up to now.
The Swiss Made Software Label
The Swiss Made Software Label makes it easier for customers to choose reliable, swiss software products. It is a voluntary scheme designed to encourage business to sklep wielkopowierzchniowy products which bear the Swiss Made. The label helps software manufacturers to get recognition for good standards.
Minimum Standards
The label sets minimum standards for a software product to be considered Swiss Made. A software product can obtain the label if:
the Swiss components of the production cost account for at least 50%;
the most essential steps in developing the software have to be carried out in Switzerland.
External links
Software aus der Schweiz, Mitra Blog
Das Label „Swiss Made Software“ geht in die Offensive, Netzwoche
VRSG: Schweizer Informatik für Schweizer Gemeinden, Städte und Kantone
Qnamic AG neu gawęda Qualitätslabel „swiss made software“
PROFFIX entwickelt vollumfänglich in der Schweiz
Contrexx - Hersteller bei "swiss made software" eingetragen
LIIP - SWISS MADE SOFTWARE
Salenture is Swiss Made Software
Retrieved from ""
Categories: Software | Software companies by country | Country of origin
Posted under Uncategorized od on środa 29 październik 2008 at 11:21 przed południem
Quadriga is a commercial audio-archiving workstation for the automated mass przewożenie of legacy sound carriers to digital storage systems. The unique aspect of the ustrój lies in the real-time inspection of the dźwiękowy during the przekazywanie process, statistical reports of which are generated and stored with other melina prekluzja within the resulting dźwiękowy file.
Contents
//
History
Traditional broadcast and sound archives have proven over the years to be extremely labor intensive to maintain and manage. This is due in part to the personnel intensive nature of the extremely important quality control process associated with maintaining the highest possible technical standards. As broadcasting migrated from analog to digital technology, broadcasters were forced to digitize analog assets – something that has been on-going since the early 1990’s.
This transition from single-sound-carriers to everlasting digital prekluzja in the form of sound files represents the evolution from the past to the future – a significant preria towards higher quality and more accessible sound archives. Unlike most analog środki masowego przekazu, digital sound files can be stored in large-scale file servers, which are accessible via the broadcasters network, and / or via the internet.
The most critical stage in the process is the original przenoszenie from the analog to the digital domain, and failure to execute this properly significantly compromises the integrity of the archive. This fact forced broadcasters and archives to seek out technology that would be capable of managing the analog to digital przewożenie process, while maintaining the highest possible level of quality control.
To this end, a sophisticated sprzęt and software based solution called Quadriga was developed in 1998 by Bremen, Germany based “Cube-Tec International GmbH”, in close cooperation with the “Institut für Rundfunktechnik” (IRT) and the German “public broadcasting”. Quadriga is a registered trademark of IRT and is exclusively marketed by Cube-Tec International. The name Quadriga is derived from “QUality from Analog to Digital RIGorously Analyzed”. Quadriga is used internationally by broadcasting companies, archives and music enterprises.
Functionality
If used during the initial przenoszenie, Quadriga automates the digitization process while simultaneously analyzing the incoming dźwiękowy stream for any anomalies or irregularities – all of which are logged into a quality report. For digital files that were transferred without Quadriga, the organizm can be used to analyze those files for detection of the same anomalies and the production of the quality report, which can be checked in real time via dźwiękowy playback and / or visually inspecting the waveform.
The quality reports, in addition to other melina termin information such as source sound carriers and historical prekluzja are maintained as part of the digital sound file. Quadriga is compatible with any existing “środki masowego przekazu Asset Management” ustrój and easily adapts to its networking and database configuration.
Also relevant to digitized archives are two newly developed technologies from Cube-Tec called Dobbin and Cube-Workflow. These sophisticated technologies can be used to fully automate file management, rights management, and publikatory processing functions. Typically labor intensive processes such as normalization, sample-rate conversion, rozmiar conversion, codec encoding / trans-coding, water-marking, dźwiękowy restoration, and other signal processing functions are handled as an off-line automated process.
Posted under Uncategorized od on poniedziałek 27 październik 2008 at 7:18 po południu
ACTRAN is a Finite Faktor Method - Infinite Elements Method (FEM-IFEM) software package developed by Free Field Technologies SA, a Belgian company. ACTRAN is aimed at solving acoustic propagation problems. It has several modules for targeted applications, mainly in the automotive and aeronautic industries obuwie not exclusively. The package contains today tools for vibroacoustic simulations and aeroacoustic simulations.
Contents
//
History
The first version of ACTRAN has been released in 1998. The complete history of the ACTRAN family will be written in the future.
Software Architecture
ACTRAN was primarily written in FORTRAN. The last versions of the code are written partly in C++ and Python. It is a fully 64 bits, parallel implementation. Details will be given in future versions of this draft page.
Interfaces
Interfaces with Meshing tools
ACTRAN is interfaces with the following external meshing tools, not developed by Free Field Technologies:
* MSC.Patran
* Hypermesh
* I-DEAS
* ICEM
* ANSA
* All meshing tools which can export a mesh file in numer UNV, BDF or similar
Interfaces with Structural Dynamics Codes
ACTRAN is interfaces with the following external codes, not developed by Free Field Technologies:
* Nastran
* ANSYS
* Abaqus
Interfaces with Fluid Dynamics Codes
ACTRAN is interfaces with the following external codes, not developed by Free Field Technologies:
* star-CD from CD-adapco
* star-CCM+ from CD-adapco
* Fluent
* CFX
* Powerflow from EXA
* All codes supporting export into ENSIGHT numer
* A few proprietary codes
Posted under Uncategorized od on poniedziałek 27 październik 2008 at 3:13 po południu
It has been suggested that HOWTO article be merged into this article or section. (Discuss)
Software documentation or source code documentation is written text that accompanies computer software. It either explains how it operates or how to use it, and may mean different things to people in different roles.
Contents
//
Types of software documentation
Documentation is an important part of software engineering. Types of documentation include:
Architecture/Design - Overview of software. Includes relations to an environment and construction principles to be used in image of software components.
Technical - Documentation of code, algorithms, interfaces, and APIs.
End User - Manuals for the end-user, organizm administrators and support staff.
Marketing - How to sklep wielkopowierzchniowy the product and analysis of the sklep wielkopowierzchniowy demand.
Architecture/Design documentation
Architecture documentation is a special breed of stylistyka documents. In a way, architecture documents are third derivative from the code (wygląd document being second derivative, and code documents being first). Very little in the architecture documents is specific to the code itself. These documents do not describe how to oprogramowanie a particular routine, or even why that particular routine exists in the form that it does, obuwie instead merely lays out the general requirements that would motivate the existence of such a routine. A good architecture document is short on details obuwie thick on explanation. It may suggest approaches for lower level image, obuwie leave the actual exploration trade studies to other documents.
Another breed of wygląd docs is the comparison document, or trade study. This would often take the form of a whitepaper. It focuses on one specific aspect of the układ and suggests alternate approaches. It could be at the user interface, code, estetyka, or even architectural level. It will outline what the situation is, describe one or more alternatives, and enumerate the pros and cons of each. A good trade study document is heavy on research, expresses its kwestia clearly (without relying heavily on obtuse jargon to dazzle the reader), and most importantly is impartial. It should honestly and clearly explain the costs of whatever solution it offers as best. The objective of a trade study is to devise the best solution, rather than to push a particular point of view. It is perfectly acceptable to state no conclusion, or to conclude that none of the alternatives are sufficiently better than the baseline to warrant a change. It should be approached as a scientific endeavor, not as a marketing technique.
Technical documentation
This is what most programmers mean when using the term software documentation. When creating software, code alone is insufficient. There must be some text along with it to describe various aspects of its intended operation. It is important for the code documents to be thorough, obuwie not so verbose that it becomes difficult to maintain them.
Often, tools such as Doxygen, NDoc, javadoc, Sandcastle, ROBODoc, POD , TwinText , or Universal Report can be used to auto-generate the code documents—that is, they extract the comments from the source code and create reference manuals in such forms as text or HTML files. Code documents are often organized into a reference guide style, allowing a programmer to quickly look up an arbitrary function or class.
Many programmers really like the sprawa of auto-generating documentation for various reasons. For example, because it is extracted from the source code itself (for example, through comments), the programmer can write it while referring to his code, and can use the same tools he used to create the source code, to make the documentation. This makes it much easier to keep the documentation up-to-date.
Of course, a downside is that only programmers can edit this kind of documentation, and it depends on them to refresh the output (for example, by running a cron job to update the documents nightly). Some would characterize this as a pro rather than a con.
Donald Knuth has insisted on the fact that documentation can be a very difficult afterthought process and has advocated literate programming, writing at the same time and location as the source code and extracted by automatic means.
Elucidative Programming is the result of practical applications of Literate Programming in real programming contexts. The Elucidative paradigm proposes that source code and documentation be stored separately. This paradigm was inspired by the same experimental findings that produced Kelp. Often, software developers need to be able to create and access information that is not going to be part of the source file itself. Such annotations are usually part of several software development activities, such as code walks and porting, where third uczta source code is analysed in a functional way. Annotations can therefore help the developer during any stage of software development where a formal documentation układ would hinder progress. Kelp stores annotations in separate files, linking the information to the source code dynamically.
User documentation
Unlike code documents, user documents are usually far more diverse with respect to the source code of the oprogramowanie, and instead simply describe how it is used.
In the case of a software library, the code documents and user documents could be effectively equivalent and are worth conjoining, obuwie for a general application this is not often true. On the other hand, the Lisp machine grew out of a tradition in which every piece of code had an attached documentation string. In combination with strong search capabilities (based on a Unix-like apropos command), and online sources, Lisp users could look up documentation and paste the associated function directly into their own code. This level of ease of use is unheard of in putatively more modern systems.
Typically, the user documentation describes each feature of the oprogramowanie, and assists the user in realizing these features. A good user document can also go so far as to provide thorough troubleshooting assistance. It is very important for user documents to not be confusing, and for them to be up to date. User documents need not be organized in any particular way, obuwie it is very important for them to have a thorough index. Consistency and simplicity are also very valuable. User documentation is considered to constitute a contract specifying what the software will do. See also Technical Writing.
There are three broad ways in which user documentation can be organized.
Tutorial
A tutorial approach is considered the most useful for a new user, in which they are guided through each preria of accomplishing particular tasks.
Thematic
A thematic approach, where chapters or sections concentrate on one particular area of interest, is of more general use to an intermediate user.
List or Reference
The final type of organizing principle is one in which commands or tasks are simply listed alphabetically or logically grouped, often via cross-referenced indexes. This latter approach is of greater use to advanced users who know exactly what sort of information they are looking for.
A common complaint among users regarding software documentation is that only one of these three approaches was taken to the near-exclusion of the other two. It is common to ograniczenie provided software documentation for personal computers to online help that give only reference information on commands or karta items. The job of tutoring new users or helping more experienced users get the most out of a oprogramowanie is left to private publishers, who are often given significant assistance by the software developer.
Marketing documentation
For many applications it is necessary to have some promotional materials to encourage casual observers to spend more time learning about the product. This form of documentation has three purposes:-
To excite the potential user about the product and instill in them a desire for becoming more involved with it.
To inform them about what exactly the product does, so that their expectations are in line with what they will be receiving.
To explain the position of this product with respect to other alternatives.
One good marketing technique is to provide clear and memorable catch phrases that exemplify the point we wish to convey, and also emphasize the interoperability of the oprogramowanie with anything else provided by the manufacturer.
See also
Comparison of documentation generators
Design by contract
Docstring
User Assistance
Design document
README files
Unified Modeling Language UML
Literate programming
References
This article does not cite any references or sources.
Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed.
External links
kelp - a source code annotation framework for architectural, image and technical documentation
Development models: Agile • Iterative krój • RUP • Scrum • Spiral krój • Waterfall wzór • XP • V-Model
Process models: Function szablon • Information wzór • Object model
Data models: Termin szablon • Database model
Software engineers
Charles Bachman • Kent Beck • Tim Berners-Lee • Grady Booch • Fred Brooks • Ward Cunningham • Edsger W. Dijkstra • Wolumin Gruber • Michael A. Jackson • Ivar Jacobson • James Rumbaugh • Edward Yourdon
Retrieved from ""
Categories: Software | Technical communicationHidden categories: Articles to be merged since November 2007 | All articles to be merged | Articles lacking sources | All articles lacking sources
