|
|
|
Down |
Use this link if you want more information about Open Source project support services. This project's summary page on SourceForge.net. Suggestions on how to improve this project are welcome here. |
Status and Text Reference Coding This project is currently in the design and documentation stage. This web page is also less than beautiful. Suggestions on how to improve either the project itself, these web pages or both are welcome here. Purpose and OriginsWhile 'C' and Unix use the This project discusses and implements an alternative method for encoding status information, and associating descriptive text with that information, in an easy to understand way. This facility was inspired by a facility in Digital Equipment Corporation's VMS operating system. A similar facility exits on Microsoft's Windows platform. This facility is broadly similar to its predicessors but is an independent and original development. In particular an attempt has been made to bring this facility into alignment with the POSIX standards. OutlookIf the facility implemented by this project is used in other projects, the following benefits are likely to result:
Design PhasesThe primary implementation will be for the 'C' language. An implementation for 'C' can be translated to other languages with a preprocessor or that can use the 'C' preprocessor as a front end. Special implementations for 'C++' and other languages may or may not be produced as user demand dictates. This project has been split into two phases. This first phase must be implemented before the design of the second phase begins. The first phase provides the encoded status data type and related components. The second phase provides services for managing internationalization and message customization. Links to usage informationProgrammer's Guide – descriptive information intended for the people using the results from this project. Links to developers' informationImplementation Notes – descriptions of the project components, their inter-relation and theory of operation. This information is a primary resource for people maintaining or modifying the source material for this project. Maintenance Notes – warnings about things that didn't work and things to watch out for when working on project elements. It should summarize the reasons for major changes and significant bug fixes. It should be maintained by the quality assurance team and is required reading for maintainers and project developers. Links to other project pagesBackground – what is available on other platforms. Requirements – elements, features, interfaces and procedures that must be present in the result. This is a design phase document and may or may not be kept up to date after the design phase is complete. Analysis – an analysis and extension of the requirements with the intent of specifying a usable result. This is a design phase document and may or may not be kept up to date after the design phase is complete. Specifications – a high level description of what the project will do. This is a design phase document and may or may not be kept up to date after the design phase is complete. Design – an analysis of the specifications with the intent of implementing the project. This is a design phase document and may or may not be kept up to date after the design phase is complete. NOTE The formal documentation technique used for this project is mostly for demonstration purposes. It can be made to work for a small project like this one. For large projects this outline may be useful, but strict adherence to this documentation methodology can seriously hamper the progress of a project. What must be done in large projects is to recognize that all the useful information from the early documents will be copied into later documents and that maintaining the early documents is almost always a waste of resources. Major project work items:
Secondary and continuing project work items:
Minor project work items:
|
|
|
|
Down |