System Design Specification Computer Science Essay

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

This System Design Specification document describes the detailed structure of the components of the Remote Fiber Optic Communications Laboratory. It documents the design and design decisions in order to provide the basis for implementation and unit test.

This document delineates the structure of the Laboratory based on the Interactive iLabs Architecture 3.0.2 and traces the precise implementation details required to satisfy the requirements as specified in the Software Requirements Specifications (SRS).

Intended audience

This System Design Document is written for the knowledgeable in technical Developer, Supervisory and Reviewer positions.

Important Definitions, Acronyms

For a complete list of the definitions and acronyms used in the remainder of this document, refer to Appendix A.

Architectural Design

This section outlines the system and hardware architecture design of the laboratory. It describes the system architecture, how the systems interact with other applications and how the components interact with each other.

System Architecture

The laboratory will be based on the Interactive iLabs Shared Architecture. The iLabs Shared Architecture is a framework that provides for the development and deployment of remotely accessible laboratories. It runs on a three-tiered model based on web services consisting of lab clients, service broker middleware, and lab servers. The Interactive labs grant the user higher and active control of lab instruments during the execution of an experiment and can generate large amounts of data. The Interactive iLab topology is explained as shown below.

Extreme left is the Lab Server, Service Broker and Lab Scheduling Service, which constitute the Lab Side system, and the rest constitute the Client Side. The Service Broker sets up a connection between the client user and the lab server, and the two can communicate directly. The Lab Side Scheduling service enables the Administrator to allocate time blocks to the experiment and the User Side Scheduling Service grants an authorized client user a session within the set time block. During experiment execution, the Service Broker no longer has an upper hand in the experiment data and thus data handling is done by the Experiment Storage Service, a stand-alone service for data storage.

System Design

Hardware Interface


The NI ELVIS II Platform is a LabVIEW-based design and prototype environment for University Science and Engineering Laboratories. It is used to teach concepts in circuit design, instrumentation, controls, telecommunications, and embedded/MCU theory. It consists of LabVIEW-Based virtual instruments, a multifunction data acquisition (DAQ) device, and a bench-top workstation and prototype board. Because it is based on LabVIEW and provides complete data acquisition and prototyping capabilities, the system is ideal for academic coursework that range from lower-division classes to advanced project-based curriculum.

NI ELVIS II is chosen because it has all the necessary circuitry inbuilt and is compatible with a computer as well as LabVIEW programming language.


The EMONA FOTEx is an add-in module integrated on the NI ELVIS II and fully compatible with LabVIEW programming environment. It is a collection of blocks/modules that can be patched together to emulate/implement a dozen fiber optic communications scenarios. It supports incorporation of optical fiber cable in the circuitry.

Software Interface Description

Operating System

Windows Server 2003 (Win2K3) operating System will be used. The choice of Win2K3 is based its ability to:

Act as an application server and perform server-oriented functions

Manage Your Server - a role management administrative tool that allows an administrator to choose what functionality the server should provide

Capability to host message queues

Authenticate users

Serve streaming media

Share files

Support Internet Information Services (IIS)

Windows XP Service Pack 2 can also be used.

Database Server

SQL Server 2000 is the high performance relational database system with a rich development environment that suits the purpose.

Development Environment

Microsoft Visual Studio is an Integrated Development Environment from Microsoft and thus works well with Win2K3. It covers such functions as development of console and Graphical User Interface applications along with Windows Forms applications, web sites, web applications and web services for all platforms supported by the .NETFramework. Visual Studio includes a code editor, debugger, forms designer for building GUI applications and web designer. MS Visual Studio 2003 will be used.

Programming Language

LabVIEW is a platform and development environment for a visual programming

language from National Instruments. It is a graphical programming language that uses icons instead of lines of text to create applications. It is ideal for test, measurement, data acquisition, instrument control, and industrial automation on a variety of platforms including Microsoft Windows. LabVIEW extensively supports

access to instrumentation hardware.

Equipment Drivers:

NI ELVISmx drivers will be installed to enable students access all the 12 instruments through the NI-ELVISmx instrument launcher. The FOTEx drivers will avail reach of the modules in the FOTEx.

Communications Interfaces

Web Browsers

Considering that the system will be built on a Windows platform, the most efficient browsers are Internet Explorer, Mozilla Firefox and Google Chrome.

Application Program Interfaces

DataSocket for LabVIEW supports live data exchange between different applications on one computer or between computers connected through a network. It connects data from a number of sources such as webserver, specifies data location through the use of the URL. The data socket Transfer Protocol connects the data socket application to the datasocket server.

User Interface Design

The user will interface with the system through a web page. It will have a provision for user registration, authentication and authorization. It will have links to documentation that guides the user through the pertinent experiments.