PRaCoSy: Document Deliverables
This document is updated from UNU/IIST Doc. No. dyl/deliv/2. It lists latest versions of PRaCoSy related document deliverables with their Doc. No., Date and Abstract. The document entries form a subset of those listed in the Document Catalogue (UNU/IIST Doc. No. lls/table/01, which is updated from Doc. No. jdh/catal/08).
Abstract : This document is updated from UNU/IIST Doc. No. dyl/deliv/2. It lists latest versions of PRaCoSy related document deliverables with their Doc. No., Date and Abstract. The document entries form a subset of those listed in the Document Catalogue (UNU/IIST Doc. No. lls/table/01, which is updated from Doc. No. jdh/catal/08).
(Note: This is a self-reference !)
Doc. No.: cwg/2 Doc. Date: August 1996
Abstract : The Executive Overview document is aimed at providing an overall description of the PRaCoSy Project, without going into very specific technical details. Individual documents cover specific aspects of this project. Exact references and synopses of documents giving details, are listed in a companion document called Document Catalogue (UNU/IIST Doc.No.: lls/table/01).
Doc. No.: jdh/fnlrpt/01 Doc. Date: November, 1994
Abstract : In this document, we summarise the development process, achievements and experience with the PRaCoSy project.
Doc. No.: SP/5/3 Doc. Date: January 7, 1994
Abstract : This document presents a formal description of the problem domain of the PRaCoSy project: operation of a railway system. The model presented are rather generic (not specific to a particular railway system), although where trade-offs were relevant, a bias towards the Problem Frame of the PRaCoSy project has been adopted.
The model covers: (1) topology of railway systems, (2) creation of schedules, and (3) rescheduling in response to detected events (such as delays). However, the current draft version needs extensive annotations.
Doc. No.: lls/dfd/01 Doc. Date: August 18, 1995
Abstract : This document presents a series of data flow diagram description of the Zhengzhou-Wuhan Train Dispatch System. It includes detailed data flow diagram narratives.
Doc. No.: CWG/1/1 Doc. Date: 25 April 1995
Abstract : This document is a contribution to the PRaCoSy (Peoples Republic of China Railway Computing System) project, a collaboration between the Chinese Ministry of Railways and UNU/IIST. It builds on previous work that formalized the notions of railway networks, timetables and scheduling. It aims to deal with two problems: (i) how to reschedule as well as schedule trains (ii) how to distribute these tasks.
Doc. No.: hm/1/1 Doc. Date: 30 June, 1995
Abstract : This document is to give a generic concurrent architecture for a distributed train rescheduling system. It is developed from the general distributed map theory.
Doc. No.: dyl/17/1 Doc. Date: 15 May, 1995
Abstract : This document is about the formal and rigorous development of RoManS (Route Management System) for railway station route management. Route management deals with train traffic within a station, and routes trains according to timetables and station layout so that smooth, accident-free (somehow optimal) train traffic can be ensured. RoManS is software that can support station staff in managing routes. This is also the master thesis of the author.
Doc. No.: SP/12/3 Doc. Date: July 15, 1994
Abstract : This document serves to (i) introduce a minimal application domain model of railway systems, as needed to capture the manipulation of train journeys: time-tables, route planning and (re-)scheduling, and (ii) describe a first, minimal tool architecture: a tool that will allow railway systems: stations and lines, to be read from descriptor files, will allow segments (subsets of all stations) and time intervals to be defined, will allow time tabels to be read, and finaly to graphically display the projection of a timetable against a given segment and a given interval.
Doc. No.: jdh/trans/02 Doc. Date: 29, Apr. 1994
Abstract : This document specifies the policy to be adopted for displaying, on a grid, a successive subset of the set of stations belonging to a segment. The display on the screen (grid) is achieved by a three-step transformation: 1. Balanced, 2. Normalised (standardised), 3. Projection. In the standardised height, all stations of the given segment are preserved. On the grid, only a contiguous subset of these stations will be displayed.
Doc. No.: lx/tool/02 Doc. Date: 28 Aug, 1994
Abstract : We specify the functions & facilities of a running map display tool with minimum facilties. This minimal tool is expected to serve as a prototype for richer and more complete running map systems. We also describe some X11/Widget inplementation details.
Doc. No.: par/desc/06 Doc. Date: 6 Apl. 1994
Abstract : The purpose of this document is to first describe formally, in a BNF-like notation, the layout of textual descriptor files for storing data about railways. The Section on Running Maps, uses these data for defining a Running Map and its operations.
Doc. No.: sgq/12/1 Doc. Date: November 3, 1994
Abstract : This document is a user script for Timetable Preparation Tool. This tool provides a friendly, convenient interface for user to input, modify, save a timetable interactively. Along with user's operating procedure, it runs a variety of checking functions, reports error messages immediately.
Doc. No.: sgq/11/3 Doc. Date: November 3, 1994
Abstract : This document serves to propose ways of modelling a tool for preparation of basic timetable, based on Minimal Formal Model(sp/12/3). The model covers(i)Basic States Specification, (ii)Station-visit Input Specification, (iii)Journey Input Specification, and (iv)Timetable Input Specification.
This model is an extension and modification of the models written by Mr.Chris George
Doc. No.: SP/11/1 Doc. Date: March 14, 1994
Abstract : This document introduces a system enabling a group of people to share files, such as source code, scripts, make files, etc., during program development. The system, called VC, provides a simple way of letting individuals develop and compile programs separately, while sharing official files (modules) in a safe manner. The system is constructed as a number of shell scripts which in turn utilizes the Revision Control System (RCS).
Doc. No.: mc/design/1 Doc. Date: October 23, 1994
Abstract : This document presents an overview decription of software design and implementation (SD&I) of the PRaCoSy project prototype system. The design and implementation principle and methods, and procedures are described here. An example is given in order to give a clear formulation.
Doc. No.: lx/11/1 Doc. Date: 13 Mar. 1994
Abstract : This document gives a collection of data structure signatures for stations. In this document, there are two sections. Section 1, describes the data structure of stations, such as station maps, station records, station identifier, station typex, and corresponding functions. Section 2 describes the data structure of platforms, such as platform maps, platform records, platform types, platform lengths and corresponding functions.
Doc. No.: sgq/2/1 Doc. Date: March 14, 1994
Abstract : This document gives a collection of data structure signatures for lines. It describes the data structure of lines, such as line maps, line records, line identifers, line types, line lengths, from-stations, to-stations and corresponding functions.
Doc. No.: sgq/3/1 Doc. Date: June 14, 1994
Abstract : This document gives the data structure signatures for network. It describes the data structure of networks, gives basic operation functions on data structures and network checking function.
Doc. No.: mc/dstr4/1 Doc. Date: Nov. 9, 1994
Abstract : This document gives the collection of data structure signatures for segment objects. It describes the data structure of segment and its corresponding functions.
Doc. No.: mc/dstr1/1 Doc. Date: May 24, 1994
Abstract : This document gives the collection of data structure signatures for train-journey objects. It describes the data structures of train-journeys, station-visits, etc. and their corresponding functions.
Doc. No.: mc/dstr2/1 Doc. Date: May 24, 1994
Abstract : This document gives the collection of data structure signatures for time-table objects. It describes the data structure of time-tables and their corresponding functions.
Doc. No.: sgq/4/1 Doc. Date: July 4, 1994
Abstract : This document gives the data structure signatures for projection. It describes the data structures of projections, gives basic functions on data structures and functions for projecting time-tables before or after a given time, over a period of time, over a segment or over a network.
Doc. No.: mc/dstr3/1 Doc. Date: Nov. 9, 1994
Abstract : This document gives the collection of data structure signatures for parameter handling objects. It describes the data structure of parameters and their corresponding functions.
Doc. No.: lx/12/01 Doc. Date: 31 Aug, 1994
Abstract : This document specify the relationship between the requirment and C code widget module of running map display tool. It also list the callback functions, event handler functions and widget tree.
Doc. No.: lx/plan/02 Doc. Date: Sep 7, 1994
Abstract : This document is user script for the (Plan) demo. This
demo is a Running Map Display Tool which projects
time-tables on segments and perform graphic display.
The purpose of this document is to be used in connection with
operating and testing a Plan demo.
Doc. No.: yd/define/1 Doc. Date: Mar. 6, 1996
Abstract : Because the requirement has been changed, so we write the new specification of PRaCoSy on the basis of former specification written by SP(See document sp/12/3) and reference the new requirement document. The new requirement and rule document of PRaCoSy is written by LLS.(See document lls/math/01).
Doc. No.: yd/event/1 Doc. Date: Sep.4 , 1995
Abstract : This is the description of events and information flows for the Train Dispatch System. They are classified by event type.
Doc. No.: lls/math/01 Doc. Date: Oct. 11, 1995
Abstract : This document presents the calculating rules which are used for drawing and adjusting stage plans. Each formula is presented in mathematical form. The symbols used to adjust the running map are explained too.
Doc. No.: lls/conv/01 Doc. Date: 12 Feb. 1996
Abstract : This document defines some conventions for programming. In order to design standard software, we establish these conventions so as to co-operate in developing high quality software.
Doc. No.: lls/struct/02 Doc. Date: 12 Feb. 1996
Abstract : This document gives a collection of all structures for PHASE-II. All structures are described in the C language. Each structure is treated as one section, which is illustrated with two paragraphes. Data structure paragraph gives three level structures according to record, map and object respectively. These names of structures and types are standard, and will be carried through to programming.
Doc. No.: yd/techdraft/1 Doc. Date: Mar. 6, 1996
Abstract : This document give us some suggestions and proposals about PRaCoSy, it contains many details of actual Operation and Programming. You can refer to some other relative documents, such as lls/math/01, lls/struct/02, yd/define/1. We will discuss four main subjects here, they are: System, Dispatch Unit, Station, Map.
Doc. No.: lls/impl/01 Doc. Date: 7 Mar. 96
Abstract : This document contains three implementation aspects of PRaCoSy: layout, rescheduling and communication. It mainly defines the man-machine interface and functional requirements.