System Specification Sample Clauses

System Specification. A Deontic Approach. PhD thesis, Imperial College of Science and Technology, University of London. [Xxxxxx, 1999] Xxxxxx, X. (1999). Communicating and Mobile Systems: the π-Calculus. Cambridge University Press. [Xxxxxx, 1942] Xxxxxx, M. H. A. (1942). On theories with a combinatorial definition of” equivalence”. Annals of mathematics, pages 223–243. [Xxxx and Xxxxxxxxxxx, 2012] Xxxx, X. X. and Xxxxxxxx- nik, F. (2012). Contracts for Interacting Two-Party Sys- tems. In FLACOS’12, volume 94 of ENTCS, pages 21– 30.
AutoNDA by SimpleDocs
System Specification. (a) means the specification recorded in the following documents, as amended from time to time by agreement in accordance with the Contract Variation Process:
System Specification. The system specification must be clearly defined and reflect characteristics of the chosen application.
System Specification. The system specification for TULIPP use cases is based on the above analysis: • Performance (speed, capacity, throughput) – Throughput: 940 MBit/s – Speed (MFLOPs): depending on use case • Connectivity – Video Input: GbE, CameraLink – Video Output: HDMI – Control output (UAV use case): USB or CAN – Connection of multiple MPSoCs: PCIe 2.0 • Scalability: different types of MPSoCs (computing power/energy consumption) should be available • Energy efficiency: – maximum power consumption less than 25 W – high efficiency (for example, MFLOPs/Xxxx), – Modern power saving capabilities (DVFS, dynamically switch off unused IOs and components etc.) • Physical compatibility – Working temperatures: –65 -+120 – Small sizes and weight (boards) The specification contains many more or less “hard” requirements, but it does not select the hardware components definitely in all cases. In complex cases, additional parameters must be analysed to make a decision: costs, availability, reliability, support, etc.
System Specification. A Deontic Ap- proach. PhD thesis, Imperial College of Science and Technology, University of London. Xxxxxx, X. (1999). Communicating and Mobile Systems: the π-Calculus. Cambridge University Press.
System Specification. RCC has commissioned, during 2015.16, the installation of an expanded and upgraded CCTV system across Uppingham town centre. This system will remain in the ownership of RCC. This system now comprises 8 cameras, each in a separate location, each strategically positioned to maximise the coverage and being mindful of known areas of crime and disorder.
System Specification. The webserver has all the business logic written in PHP scripts. The customer details including bid details and auction details are held in the PostgreSQL database also on the webserver. Customers are notified of auction and bid details by email or by logging into their account.
AutoNDA by SimpleDocs
System Specification. Storage During the storage of the grabbed data, the system will use a simple lock scenario, where the chunks currently written are locked (marked as inaccessible) in the database. This will be much simpler then writing. Indeed, the object will be simply marked as inaccessible in the fs metadatabase. As a result, nobody will be able to access this object. Then, it could simply be removed on garbage-collection basis. The storage chain is illustrated below: Grabbed data are split into chunks (We suppose the size of one data block (chunk) to be around 20s of recording, which is approximately 3MB). These chunks are scattered around the storage cluster. So no neighbor chunks (in view of chunks' sequence) are stored on the same OSN (Object Storage Node). Each chunk is stored at (at least two) mutually disjoint OSNs to achieve data redundancy. Object is defined as a sequence of the chunks. FS-metadata are stored in a relational database. Stored information consists of: ChunkIDPrefix, SeqNum, OSNID, CTYPE, Flags (e.g. "intention to delete"). You get ID of the chunk if you put together ChunkIDPrefix and SeqNum (see figure below). Motivation behind this is that we want to have as simple as possible retrieving and storing chunks (thus SeqNum, which will increment by 1 for each next chunk and some kind of prefix which will distinguish particular data sources). ChunkIDPrefix consists of NodeID, ChannelID and number of days since 1.1.2001.
System Specification. CorporateSMS Server: The CorporateSMS server contains the business logic written in PHP scripts, querying data held in a PostgreSQL database, containing all the users account information. An XML interface transports the data between the two front end applications and the central CorporateSMS server. All information sent to and from the server is sent through HTTP protocol. All exchanges of data are identified by an application identifier and a user identifier that are specific to each and every Corporate account and sub account. Contents: PostGreSQL Database PHP Scripts HTTP Gateway Interface CorporateSMS Administration Interface: MobileMail provides users an intuitive web based administrative interface. Designated corporate account administrators can create & modify user account settings, and messaging parameters. The administration interface is a web based application using PHP interpreted language to query the PostgreSQL database in the CorporateSMS server. Access to the resources handled by the administration tool is supervised by a login mechanism. Access is granted for “Super Administrators”, “System Administrators” and “Corporate Account” administrators, each with differing access rights and associated functionality. Features: • Manage all client accounts from one central web interface • Change the language of the application for international clients • Select multiple SMS providers • Apply shared short codes and MO numbers for two way messaging • Control the pricing structure applied to specific accounts • Set limits to SMS volumes on specific accounts • Control billing requirements – pre-pay or monthly invoices available • Improved SMS messaging reports & statistics • Automated on-line Pay-Pal integration MAILSMS MailSMS, developed using MS Visual Basic, is a COM add-in within Microsoft Outlook. The file, CorporateSMS.dll, is the interface that handles the communication between the client application and the CorporateSMS server and can be used by other software developers to connect to the server and use the CorporateSMS functionality. This modular approach represents an important feature related to the forward development of the CorporateSMS product suite.MailSMS is downloaded, as a plug in to MS Outlook, onto the clients PC utilising a download wizard. The application is compatible with Microsoft Windows 98 / ME / NT4 / 2000 / XP, and requires Microsoft Outlook 2000 / 2002 / 2003. Features: • Send instant messages and scheduled SMS reminders dir...
System Specification. The procurement and supplies management department at Princess Alexandra Hospital NHS Trust (the trust), is embarking on a modernisation agenda to transform procurement and sourcing. Central to the procurement strategy framework of the trust is implementation of strategic sourcing and contracts management to enhance visibility of its expenditure landscape and deliver supply chain excellence. The contract authority therefore seeks offers from providers of e-sourcing systems to enable the attainment of this strategic goal. The Princess Alexandra Hospital NHS Trust seeks to enter into contract with the successful supplier. The Contract shall run for a period of 2 years with an option to extend for a further 2x12months. Number Product/Service Required Importance
Time is Money Join Law Insider Premium to draft better contracts faster.