Software Requirements Specification (SRS) Graphical Model Editing Framework (GMEF) Motorola 1

Size: px
Start display at page:

Download "Software Requirements Specification (SRS) Graphical Model Editing Framework (GMEF) Motorola 1"

Transcription

1 Software Requirements Specification (SRS) Graphical Model Editing Framework (GMEF) Motorola 1 Final Draft Due December 7, 2006 Authors: Greg Heil, Andrew Holder, Karli Lopez, Josh Detwiler Customer: Kabe Vanderbaan Instructor: Dr. Betty H.C. Cheng 1 Introduction (Due Nov. 16) This document provides a Software Requirements Specification (SRS) document for a Graphical Modeling Editing Framework (GMEF) that allows for the development of graphical model editors, which will then be used by programmers. Section one of the Software Requirements Specification document details the purpose of the SRS document, and who the intended readers of this document shall be. Furthermore, we analyze the scope of the GMEF and provide an overview on the functionality in which it will provide to the users of the framework. Also, any definitions, acronyms, and abbreviations, which are used throughout this document, will be discussed within section one. Section two describes the constraints and functionality that the software product itself will possess. Additionally, expectations of who will be using GMEF will be covered and how much experience is required in order to understand and manipulate the framework. Undocumented constraints, also known as assumptions, will also be covered in this section. Section three highlights the main purpose for the GMEF and defines the hierarchy of specific system requirements in which the framework must adhere to. This section will specifically address, at a high level, the core functionality that is expected by the end user (a programmer). Section four discusses the specifications of GMEF. It primarily describes multiple diagrams of the system including use cases, class diagrams, and state diagrams. Use cases of the system should reflect specific scenarios of the system, which are then depicted by sequence diagrams. Each goal within our goal diagram should relate to a specific use case. Our system s state diagram should also capture each key class used within the system. Section five introduces a prototype of GMEF and describes how the prototype functions, what is required to run the prototype, and sample scenarios that the prototype can represent.

2 Section six lists all of the documents, which are referenced throughout this SRS document. Section seven informs whom to contact for any questions regarding the SRS document and the information contained within the SRS document. 1.1 Purpose The purpose of this document is to specify, in detail, the software requirements for GMEF. This document describes the features of the framework, the constraints under which it will operate, and any external interfaces used by the framework. It also describes in detail specific requirements obtained from the customer specification and dialog between the requirements engineering team and Kabe Vanderbaan, our Motorola contact. The intended audience of this document are the stakeholders of GMEF. Current stakeholders include: the requirements engineering students, programmers creating editors with the GMEF framework, and users of these editors. 1.2 Scope The software described in this Software Requirements Specifications document is referred to as Graphical Model Editing Framework (GMEF). The purpose of this software is to allow for the programmatic creation of multiple graphical editors, which modify an underlying model [2]. GMEF is a framework that relies heavily on abstraction, allowing for the manipulation of an underlying model designed using one of many available third-party modeling tools. One problem that is apparent in some modeling languages is that they often try to encapsulate so much functionality that it often results in redundancy and infrequently used diagrams. Specifically, the Unified Modeling Language (UML) has been criticized for the complexity of its diagrams. However, GMEF enables a programmer to take an underlying model which may have been developed using, for example, Microsoft Visio and its UML templates, and create a unique tool set which incorporates the classes of the UML diagram as shapes, and offers its own set of connectors between the shapes to represent class relationships. Using a GMEF-powered programmatically created tool set and model editor, an end-user of the system may then graphically constrain the representation of an underlying model, something not generally allowed by UML. An important goal of GMEF is that the framework must to be written as an Eclipse plug-in. Eclipse is an open, extensible framework for which software can be written for. In particular, Eclipse offers a Graphical Editing Framework (GEF) in which a programmer may develop a graphical modeling environment within Eclipse. One main advantage of designing an Eclipse plug-in is that these plug-ins are loosely coupled, and offer developers the freedom to choose exactly what they need for their specific applications. With such an open and customizable framework, it is quite clear that Eclipse offers the best features needed to realize the objectives of GMEF. GMEF enables a programmer to create a graphical model editor along with a palette consisting of shapes and connections. An end-user of the system is presented with a workspace in which they are able to drag and drop shapes and connections from the

3 palette. GMEF will then interface between the underlying model and the current diagram that is being designed using the graphical model editor. Furthermore, any connections that are created or deleted within an active diagram will be reflected by its underlying model. Consequently, any changes that occur within our underlying model must then be reflected in any current opened diagrams. GMEF will also allow the user to save an open diagram in order that it may be reopened in future sessions and manipulated further. It is also required that GMEF may allow for the selection of elements. Once an element has been selected, it may be moved and / or deleted from the current diagram. There are also several restrictions on the types of operations that GMEF may perform. GMEF will in no way be able to modify anything other than connections and relationships between shapes in the underlying model. All other model objects and properties must remain intact during the execution of a GMEF editor. Key requirements and constraints that GMEF should allow and forbid are discussed below. 1.3 Definitions, acronyms, and abbreviations Following is a list of the terminology used throughout this SRS document as well as detailed tables of acronyms and definitions. SRS GMEF GEF UML API GUI Eclipse Programmer End-user Acronyms Software Requirements Specifications Graphical Model Editing Framework Graphical Editing Framework Unified Modeling Language Application Programmer Interface Graphical User Interface Definitions An open source development platform comprised of multiple extendable framework. A programmer is a stakeholder who will be programmatically creating the graphical editor along with the API framework [2]. An end-user of the system represents a stakeholder who will not deal with any programming but will solely use GMEF and a graphical editor to manipulate an underlying model [2]. Graphical Model Editor A graphical model editor is programmatically created and is considered a workspace in which a user may drag and drop shapes and connections to form a diagram of the underlying system model [2]. Framework Plug-in A software structure in which another software project can be developed under. A framework may take multiple artifacts such as programs, dynamic libraries, and other content to link together multiple project components [1]. Specific software which is developed and intended to function within an already exiting application [1]. GMEF Specific Definitions

4 Palette Shape Connector Diagram Underlying model A container which will hold the shapes and connections programmatically defined within GMEF [2]. A shape represents an abstraction of a core element of the underlying model [2]. Represents a relationship between two elements within the diagram [2]. A diagram represents a current workspace within GMEF. A diagram can be thought of as a view into our underlying model. A diagram is an abstraction of our underlying model [2]. The base model which was designed in a specific modeling language. This model will then provide GMEF with the specific shapes that will be contained in the palette [2]. 1.4 Organization The rest of the Software Requirements Specifications document will discuss in detail the product functions and constraints, assumptions of the system, the specific requirements that GMEF must adhere to, depict several models of the system in representative scenarios, a prototype of GMEF, and any references which were used throughout the SRS document. The SRS document is organized in such a fashion where the actual software functionality is described first to aid in developing an idea of what GMEF should accomplish. Once the software is discussed thoroughly, the SRS document concentrates on specific requirements that the system must meet. These requirements are also reflected in various diagrams, including use case diagrams and state diagrams. The last section of this document presents a prototype for GMEF as well as sample scenarios depicting an end-user of the system would interact with GMEF. 2 Overall Description (Due Nov. 16) This section of the Software Requirements Specifications document discusses the product, GMEF, and the core functionality, which is encapsulated by the system. Subsection one describes the context of GMEF and the type of system that GMEF belongs to. Also, subsection one highlights several constraints of GMEF ranging from the system interface, user interfaces, and software interfaces. Subsection two summarizes the specific functions that GMEF should perform which are then depicted as hierarchal goal diagram. The goal diagram of the system should include both high and low level goals. Subsection three explains the specific expectations that an end-user of the system should possess. Specifically, this section will discuss what type of background a user of GMEF should have, what type of skill level is required to understand the system s functionality, and what areas of expertise are required from the end user in order to operate GMEF. Subsection four discusses specific constraints that the system must adhere to in order to properly function. This section also describes what types of conditions are encountered when these constraints are broken. Also, system critical properties are detailed and describe how they cause the system to fail.

5 Subsection five lists various assumptions, also known as undocumented constraints, which the system should abide by. The assumptions of GMEF should include software, environment, and user interactions. Finally, subsection six discusses requirements of GMEF that are outside the scope of the product. 2.1 Product Perspective The GMEF toolset provides an Application Programmer s Interface (API) that enables a programmer to develop their own graphical model editor for a specific type of model. This API in turn, relies on extending the Eclipse Graphical Editing Framework (GEF) to provide an environment in which the editor functions, and the programmer can create a graphical editor and palette of shapes in order to modify an underlying model. GMEF provides an interface with which the programmer implements said editor for a given underlying model. Such instance of the GMEF editor allows a user to drag objects from a specified model into a working GMEF diagram. This diagram only shows the objects dragged by the user and any existing connections between these objects. The user can also add and remove connections between these objects as needed using the palette supplied, thus modifying the underlying model. However, GMEF cannot manipulate the actual objects in this model. GMEF also provides the capacity to save the visual state of an open diagram to a file. The programmer must provide implementations of functions that draw objects and their connections, as well as functions that add and remove connections. The latter function will be handled by a specific event listener. Any changes made in real-time to the underlying model will also be updated in the diagram through a separate event listener. The GMEF toolset primary interface is the Eclipse framework itself. This framework provides all necessary keyboard and mouse interfaces as well as the graphical interface. The only requirement made on the hardware platform is that it must be able to comfortably run an instance of the Eclipse software suite (i.e. CPU speed, memory, etc. must be sufficient). The event listeners in turn communicate only with third party modeling software already running in eclipse (see Figure 1, Data Flow Diagram) and do not need to communicate with any software outside of Eclipse. No further customizations other than those made by the programmer need to be done for instances of GMEF. 2.2 Product Functions The main functions of GMEF can be illustrated through two different use cases that offer varied perspectives. The first use case scenario depicts the case in which a programmer uses the GMEF framework to create an editor for a specify type of model. The second use case depicts an editor user s perspective. It is not necessary for this user to have any programming background or even know GMEF is the underlying framework in order to utilize the editor properly. The way a framework provides functionality for a programming is by Application Programming Interfaces(API). GMEF will provide an API for a programmer build different types of editors. The programmer will specify properties the editor should have,

6 such the connectors available for use. The programmer will also specify the type model to be edited and how its objects will be drawn as well as implement the interface by which GMEF is notified of changes in the underlying model. The second part of the GMEF framework is the user interface for editing the model. The framework allows the user to create and delete connections on a model. The model editor is to be built as an Eclipse plug-in, which provides a GUI environment for model editing and diagram creation, saving, and loading. An editor user will use GMEF to create, modify, and delete connections on an underlying model. The editor itself is made up of a class selection box, a canvas, and a connections palette. The class selection box will display a shape with the details of the selected class onto the canvas. The user can add connections between the classes by selecting the type of connection from the palette and the classes involved. Connections between the classes will be handles by the framework, so repositioning of a class elsewhere on the canvas does not effect the connections. Following is our goal model used to illustrate how each primary requirement is satisfied. Our primary Goal Interface with GEF depicts the need to provide a functional Eclipse plug-in using its plug-in framework. Interface within GEF This is the top level goal. Form Plug-In Form plug-in is required using Eclipse. This plug-in displays an editor, a palette, and navigates graphs. Navigate Graph - The plug-in needs to be able to navigate a graph. Create Connections In order to navigate a graph, a graph has to exist. The editor allows connection creation. Create Palette The plug-in needs to be able to create a palette of shapes and connections. Create Editor The plug-in must create an editor for displaying classes as shapes, creating connections, and moving them around via a GUI. Save Description of Diagram The plug-in must be able to save a description, probably file, of a diagram created in the editor. Allow Update Views - Shape Compartments The palette contains shapes and connections. The shapes can contain zero or more compartments for types of data. Manipulate Shapes The palette allows different types of manipulations to shapes, depending on selection. Delete Element An element may be deleted by selecting an item from the palette. Select Element An element may be selected.

7 Figure 2. GMEF Goal Model Interface within GEF Form Plug-In Navigate Graphs Create Editor Create Palette Create Connections Save Description of Diagram Allow Update Views Shape Compartments (0...n) Manipulate Shapes Delete Element Select Element 2.3 User Characteristics The two types of users for this framework are: editor programmers and Eclipse editor users. An editor programmer uses GMEF s APIs to create a graphical editor for one of their models. An Eclipse editor user would use the GUI plug-in created by an editor programmer using GMEF. The programmer is expected to be proficient in Java to utilize the GMEF framework. The programmer must have the capacity to understand or learn the documentation and resources needed to utilize GMEF. The editor user is expected to be able to perform basic GUI operations, is familiar with the modeling language they are using and should understand that GMEF is editing a diagram of an underlying model.

8 2.4 Constraints General constraints within GMEF are of a limited scope. The GMEF toolset must be able to work under the Eclipse GEF framework itself. GMEF must itself be written in Java. All programs that use this API must also be written in Java. The internal functionality of GMEF must also adhere to GEF s own API requirements and style. Furthermore, event listeners must also conform to Eclipse s own even handling scheme. GMEF runs as part of a single eclipse process and therefore has no need for advanced parallel operations or complex interfaces to external resources. The most important critical constraint within GMEF is that it must maintain the integrity of the underlying model. This means that underlying model objects cannot be created or destroyed by GMEF. Moreover, GMEF must allow the user to add and remove connections between objects as they please. It is also critical that GMEF editors run reliably and not cause any instability within eclipse or the system as a whole. Finally, concurrency constructs such as event handlers and listeners must be handled properly within GMEF. In addition to these critical constraints, diagrams must be properly notified when the underlying model changes. Should this not be the case, GMEF should handle such discrepancies between the diagram and the underlying model through an error message or by modifying the diagram as needed and logging the change. GMEF should also handle cases where a diagram retrieved from a file is corrupt and contains erroneous information. Two of these constraints can be demonstrated using SCR specifications. The first property (referred to as property 1) described is that which the GMEF editor allows users to add and remove connections between objects as they please. Figure 3. Property 1 Mode Table Current ConnectEnd MarkDeletion VerifyDeletion CancelOperation New Mode Mode Connecting - - Deleting Idle - - Idle Deleting - - Idle - - Idle The property s Mode Table (Figure 3) shows us the basic behavior of this property. When connecting one end of a connector to an object, the system would send the ConnectEnd event. This event can be handled by both the Idle and Connecting states. The Idle state (being our initial state) will transition to Connecting when the user has initiated a connection. Once another ConnectEnd event has been received during the Connecting state (signaling that a second object has been selected,) the systems completes the connection and returns to the Idle state. However, if the user cancels the operation, no connection is made and the system returns to the Idle state. Upon receiving a MarkDeletion event (which signals that a connection has been marked for deletion) the system enters the Deleting state. The system may wish to receive confirmation from the user before deleting a connection, and so it waits for a VerifyDeletion event before

9 deleting the connection and returning to the Idle state. Alternatively, the system might not require verification, in which case the VerifyDeletion event automatically fires. The system may also interrupt the Deleting state via the CancelOperation event and thus keep the connection intact before returning to the Idle state. There are no relevant Event or Condition Tables for this property. The second property (referred to as property 2) is that which handles discrepancies between the GMEF diagram and its underlying model. We assume that the diagram is modified in such a case and the change is logged. Figure 4. Property 2 Mode Table Current Mode OpenDiagram ReadElement ElementRead InvalidID ResolvedError New Mode LoadDiagram LoadDiagram LoadElement InvalidDiagram LoadElement LoadDiagram InvalidElement InvalidElement LoadDiagram InvalidDiagram Idle This property s Mode Table (Figure 4) illustrates how GMEF can read a diagram from a file. The system initially responds to an OpenDiagram event while it is in its initial state Idle. The system then proceeds to load a diagram that corresponds to a known model. The system receives an InvalidID event if the model type is not found and will transition to the InvalidDiagram state. In this state, the system will alert the user of the error and after receiving the ResolvedError event, return to the Idle state. If the underlying model is found, the system will load the module (not depicted) and will wait for a ReadElement event, which indicates to the system that a new Diagram Element is being read. Upon receiving this event, the system will transition into the LoadElement state, where the system is concerned with loading a single element. The system receives an InvalidID event if the element s ID is not found in the underlying model and will transition to InvalidElement. In this state, the system may alert the user of the change in the model, remove any connections associated with the defunct object, and after receiving the ResolvedError event, proceed to the LoadDiagram state in order to continue loading more diagram elements. (Alternatively, the system may stop loading the file and transition back to Idle after alerting the user of the error.) There are no relevant Event or Condition Tables for this property. 2.5 Assumptions and Dependencies An unavoidable problem during Software production is the presence of assumptions, or undocumented requirements, during the design phase. GMEF is a Java-based platform-independent product capable of running on different types of systems. However, it is assumed that every GMEF client will be running the same version of Eclipse. Conflicts due to clients using an older version of Eclipse are beyond the scope

10 of this document, it is assumed that GMEF will be built using the latest version of Eclipse as of the time of writing. GMEF, being Java-based, is designed to run across multiple platforms, ranging from Mac, Windows 9X/NET/XP, to Linux. We must assume that the client will have stable running versions of their operating systems and that all versions of GMEF will behave identically no matter what operating system they are running. Furthermore, certain user interactions of GMEF are assumed to be known by the enduser. Specifically, the assumption is made that an end-user of GMEF should know whether or not it is logical to make a connection between certain shapes. That is, GMEF itself should not have to worry about erroneous connection, since the programmer and/or user will already know when these conditions may occur. Due to the fact that GMEF is an Eclipse-based framework, the customer has specifically stated that hardware specifications are beyond the scope of this SRS document and have no need to be elaborated upon. 2.6 Approportioning of Requirements The customer does not have any requirements approportioned for future versions of GMEF. 3 Specific Requirements (Due Nov. 16) 1. Development of a Graphical Modeling Editing Framework (GMEF) 1.1. Framework should be created and deployed as an Eclipse plug-in [2] Framework should be build as an extension to the already existing Eclipse Graphical Editing Framework (GEF) [2] Framework should save a description of a diagram into a separate file. This allows for the diagram to be reloaded and later manipulated in its previous state [2] Framework should allow for the creation of an Application Programming Interface (API) and a set of classes. 1.5 GMEF should be created as an Eclipse plug-in and should also conform to the best practices described in the book, Eclipse: Building Commercial Quality Plug-ins [2]. 2. Programmatic creation of graphical model editors 2.1. A graphical model editor should be created via GMEF programmatically 2.2. Any modifications of a diagram within the editor should be reflected in the underlying model. The same should hold true vice versa The graphical model editor shall consist of a palette. The palette should contain various shapes, which represent the classes of our underlying model All shapes inside the graphical editor s palette should conform to the requirements of a given modeling language Shapes should be able to display 0 n compartments. Compartments resemble a class diagrams in which it holds three compartments: an

11 identification compartment, an attribute compartment, and an operations compartment [2] Elements, or shapes, can be selected using the graphical model editor A selected shape may be moved and or deleted [2]. 3. Connections 3.1. The framework of GMEF must ensure that all diagrams conform to the properties of a graph. This includes that all shapes and their connections must be capable of being efficiently navigated assuming the graph is an undirected cyclic graph or a directed acyclic graph [2] Connectors between shapes should be anchored to the center of these shapes A connector should allow for the creation of multiple vertices on the connector. These vertices will provide the end-user a method for routing the connector within the diagram Connections made between two shapes should be done using an orthogonal procedure, otherwise known as best guess. This procedure will approximate an appropriate routing of a connector, which creates a visually organized diagram Connectors must have a distinct means to represent ends of a connection. An example would be using arrowheads to symbolize the end of a connection. 4 Modeling Requirements (1 st draft: Nov. 28; Final draft: Dec. 7) Start of your text. 5 Prototype (Due Nov. 27, 5:00 p.m.) 5.1 How to Run Prototype 5.2 Sample Scenarios 6 References Start of your text. [1] D. Thakore and S. Biswas, Routing with Persistent Link Modeling in Intermittently Connected Wireless Networks, Proceedings of IEEE Military Communication, Atlantic City, October [2] K. Vanderbaan and D. Raymer Graphical Model Editing Framework MSU Requirements Engineering Proposal for Fall 2006 Networks and Infrastructure Research Lab, Motorola Labs, September Point of Contact For further information regarding this document and project, please contact Prof. Betty H.C. Cheng at Michigan State University (chengb at cse.msu.edu). All materials in this

12 document have been sanitized for proprietary data. The students and the instructor gratefully acknowledge the participation of our industrial collaborators.

TITLE: User Guide for the Graphical Model Editing Framework. MSU Capstone

TITLE: User Guide for the Graphical Model Editing Framework. MSU Capstone TITLE: User Guide for the Graphical Model Editing Framework SOURCE: Networks and Infrastructure Research Lab AUTHORS: Name Kabe VanderBaan Scott Brodie Jerrid Matthews April Noren Aman Rastogi Organization

More information

Software Requirements Specification (SRS) Onboard Diagnostics System

Software Requirements Specification (SRS) Onboard Diagnostics System Software Requirements Specification (SRS) Onboard Diagnostics System Authors: Jonathan Rietveld, Kyle Bartush, Yuanchun Zhao, Brandon Dorazio Customer: Dr. Ed Nelson, Ford Motor Company, Innovation Center

More information

Code Check TM Software Requirements Specification

Code Check TM Software Requirements Specification Code Check TM Software Requirements Specification Author: Richard McKenna Debugging Enterprises TM Based on IEEE Std 830 TM -1998 (R2009) document format Copyright 2017 Debugging Enterprises No part of

More information

TETRIS TEAM SMART DRIVER ASSISTANT SOFTWARE DESIGN DESCRIPTIONS. METU-Computer Engineering. 0 P a g e

TETRIS TEAM SMART DRIVER ASSISTANT SOFTWARE DESIGN DESCRIPTIONS. METU-Computer Engineering. 0 P a g e METU-Computer Engineering TETRIS TEAM SMART DRIVER ASSISTANT SOFTWARE DESIGN DESCRIPTIONS Team Members: Seymur Mammadli Shkelim Memmola Nail Ibrahimli Mehmet Kurhan 0 P a g e PREFACE This Document contains

More information

SOFTWARE DESIGN DESCRIPTION

SOFTWARE DESIGN DESCRIPTION MIDDLE EAST TECHNICAL UNIVERSITY COMPUTER ENGINEERING DEPARTMENT SOFTWARE DESIGN DESCRIPTION Group Name : Smeshers Group Members : Uğur Yanıkoğlu Furkan Odluyurt Dicle Ayzit Emre Barış Advisors : Yusuf

More information

Adobe Fireworks CS6 Voluntary Product Accessibility Template

Adobe Fireworks CS6 Voluntary Product Accessibility Template Adobe Fireworks CS6 Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding

More information

AADL Graphical Editor Design

AADL Graphical Editor Design AADL Graphical Editor Design Peter Feiler Software Engineering Institute phf@sei.cmu.edu Introduction An AADL specification is a set of component type and implementation declarations. They are organized

More information

A Top-Down Visual Approach to GUI development

A Top-Down Visual Approach to GUI development A Top-Down Visual Approach to GUI development ROSANNA CASSINO, GENNY TORTORA, MAURIZIO TUCCI, GIULIANA VITIELLO Dipartimento di Matematica e Informatica Università di Salerno Via Ponte don Melillo 84084

More information

SILVACO. An Intuitive Front-End to Effective and Efficient Schematic Capture Design INSIDE. Introduction. Concepts of Scholar Schematic Capture

SILVACO. An Intuitive Front-End to Effective and Efficient Schematic Capture Design INSIDE. Introduction. Concepts of Scholar Schematic Capture TCAD Driven CAD A Journal for CAD/CAE Engineers Introduction In our previous publication ("Scholar: An Enhanced Multi-Platform Schematic Capture", Simulation Standard, Vol.10, Number 9, September 1999)

More information

Lab Manual. Object Oriented Analysis And Design. TE(Computer) VI semester

Lab Manual. Object Oriented Analysis And Design. TE(Computer) VI semester Lab Manual Object Oriented Analysis And Design TE(Computer) VI semester Index Sr. No. Title of Programming Assignment Page No. 1 2 3 4 5 6 7 8 9 10 Study of Use Case Diagram Study of Activity Diagram Study

More information

Computer Principles and Components 1

Computer Principles and Components 1 Computer Principles and Components 1 Course Map This module provides an overview of the hardware and software environment being used throughout the course. Introduction Computer Principles and Components

More information

IDERA ER/Studio Software Architect Evaluation Guide. Version 16.5/2016+ Published February 2017

IDERA ER/Studio Software Architect Evaluation Guide. Version 16.5/2016+ Published February 2017 IDERA ER/Studio Software Architect Evaluation Guide Version 16.5/2016+ Published February 2017 2017 IDERA, Inc. All rights reserved. IDERA and the IDERA logo are trademarks or registered trademarks of

More information

Software Design Description Report

Software Design Description Report 2015 Software Design Description Report CodeBenders Haldun Yıldız 1819663 Onur Aydınay 1819002 Deniz Can Yüksel 1819697 Ali Şihab Akcan 1818871 TABLE OF CONTENTS 1 Overview... 3 1.1 Scope... 3 1.2 Purpose...

More information

Solo 4.6 Release Notes

Solo 4.6 Release Notes June9, 2017 (Updated to include Solo 4.6.4 changes) Solo 4.6 Release Notes This release contains a number of new features, as well as enhancements to the user interface and overall performance. Together

More information

Adobe Illustrator CS5.1 Voluntary Product Accessibility Template

Adobe Illustrator CS5.1 Voluntary Product Accessibility Template Adobe Illustrator CS5.1 Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments

More information

iserver Free Archimate ArchiMate 1.0 Template Stencil: Getting from Started Orbus Guide Software Thanks for Downloading the Free ArchiMate Template! Orbus Software have created a set of Visio ArchiMate

More information

Adobe Illustrator CC Voluntary Product Accessibility Template

Adobe Illustrator CC Voluntary Product Accessibility Template Adobe Illustrator CC Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding

More information

Getting Started with Papyrus for RealTime v0.9

Getting Started with Papyrus for RealTime v0.9 1. Introduction This tutorial will show the creation of a simple model using Papyrus for RealTime version 0.9.0 (based on Eclipse Neon). As a precondition to going through this tutorial, you must have

More information

Implementing a Real-Time Architecting Method in a Commercial CASE Tool

Implementing a Real-Time Architecting Method in a Commercial CASE Tool Implementing a Real-Time Architecting Method in a Commercial CASE Tool José L. Fernández-Sánchez Escuela Técnica Superior de Ingenieros Industriales C/ José Gutiérrez Abascal 2 28006 Madrid - Spain Phone:

More information

Summary Table Voluntary Product Accessibility Template. Please refer to the attached VPAT.

Summary Table Voluntary Product Accessibility Template. Please refer to the attached VPAT. Date: July 20, 2017 Name of Product: SmartDraw Cloud Contact for more Information: http://www.smartdraw.com SmartDraw Products SmartDraw Cloud Summary Table Section 1194.21 Software Applications and Operating

More information

Requirements Specification with the IEEE 830 Standard

Requirements Specification with the IEEE 830 Standard Requirements Specification with the IEEE 830 Standard Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE 830-1998 Standard, Daniel

More information

Programmazione. Prof. Marco Bertini

Programmazione. Prof. Marco Bertini Programmazione Prof. Marco Bertini marco.bertini@unifi.it http://www.micc.unifi.it/bertini/ Introduction Why OO Development? Improved structure of software easier to: Understand Maintain Enhance Reusable

More information

Purpose and Structure of Requirements Specifications (following IEEE 830 Standard)

Purpose and Structure of Requirements Specifications (following IEEE 830 Standard) SEG3101 (Fall 2010) Purpose and Structure of Requirements Specifications (following IEEE 830 Standard) Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with

More information

Adobe Dreamweaver CC Voluntary Product Accessibility Template

Adobe Dreamweaver CC Voluntary Product Accessibility Template Adobe Dreamweaver CC Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding

More information

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created> Software Requirements Specification for Version 1.0 approved Prepared by Software Requirements Specification for Page 2 Table of Contents Revision

More information

Multi-Board Systems Design

Multi-Board Systems Design Multi-Board Systems Design D A T A S H E E T MAJOR BENEFITS: Xpedition optimizes multi-board system design from logical system definition through manufacturing. Overview Electronic multi-board systems

More information

Apply a Design Pattern

Apply a Design Pattern Apply a Design Pattern Objectives After completing this lab, you will be able to: Given Apply a design pattern to a model. Transform UML classes to Java classes. Explore the transformation results. No

More information

Perfect Timing. Alejandra Pardo : Manager Andrew Emrazian : Testing Brant Nielsen : Design Eric Budd : Documentation

Perfect Timing. Alejandra Pardo : Manager Andrew Emrazian : Testing Brant Nielsen : Design Eric Budd : Documentation Perfect Timing Alejandra Pardo : Manager Andrew Emrazian : Testing Brant Nielsen : Design Eric Budd : Documentation Problem & Solution College students do their best to plan out their daily tasks, but

More information

ARCHER Metadata Schema Editor. User Guide METADATA EDITOR. Version: 1.1 Date: Status: Release

ARCHER Metadata Schema Editor. User Guide METADATA EDITOR. Version: 1.1 Date: Status: Release ARCHER Metadata Schema Editor User Guide METADATA EDITOR Version: 1.1 Date: 2008-08-26 Status: Release Change History Version Date Author Description 0.1D 2008-04-15 Ron Chernich First Draft 1.0 2008-05-01

More information

Using the JSON Iterator

Using the JSON Iterator Using the JSON Iterator This topic describes how to process a JSON document, which contains multiple records. A JSON document will be split into sub-documents using the JSON Iterator, and then each sub-document

More information

Software Architectures. Lecture 6 (part 1)

Software Architectures. Lecture 6 (part 1) Software Architectures Lecture 6 (part 1) 2 Roadmap of the course What is software architecture? Designing Software Architecture Requirements: quality attributes or qualities How to achieve requirements

More information

3. UML Class Diagrams Page 1 of 15

3. UML Class Diagrams Page 1 of 15 3. UML Class Diagrams Page 1 of 15 The UML Class Diagram: Part 1 In the last article, we saw what use cases were, and how to identify and create use cases. Taking the series ahead, in this article, we

More information

Adobe InDesign CC Voluntary Product Accessibility Template

Adobe InDesign CC Voluntary Product Accessibility Template Adobe InDesign CC Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding

More information

The Metro Map Maker TM0 Software Requirements Specification

The Metro Map Maker TM0 Software Requirements Specification The Metro Map Maker TM0 Software Requirements Specification Author: Richard McKenna Debugging Enterprises TM Based on IEEE Std 830 TM -1998 (R2009) document format Copyright 2017 Debugging Enterprises

More information

PART I. The Lay of the Land. CHAPTER 1: Exploring SharePoint Designer

PART I. The Lay of the Land. CHAPTER 1: Exploring SharePoint Designer PART I RI AL The Lay of the Land CO PY RI GH TE D MA TE CHAPTER 1: Exploring SharePoint Designer 1Exploring SharePoint Designer WHAT YOU WILL LEARN IN THIS CHAPTER How SharePoint Designer fits into Microsoft

More information

Adobe Flash Professional CC Voluntary Product Accessibility Template

Adobe Flash Professional CC Voluntary Product Accessibility Template Adobe Flash Professional CC Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments

More information

18.1 user guide No Magic, Inc. 2015

18.1 user guide No Magic, Inc. 2015 18.1 user guide No Magic, Inc. 2015 All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be shared, copied, or reproduced by any means. All information

More information

TeamSpot 3. Introducing TeamSpot. TeamSpot 3 (rev. 25 October 2006)

TeamSpot 3. Introducing TeamSpot. TeamSpot 3 (rev. 25 October 2006) TeamSpot 3 Introducing TeamSpot TeamSpot 3 (rev. 25 October 2006) Table of Contents AN INTRODUCTION TO TEAMSPOT...3 INSTALLING AND CONNECTING (WINDOWS XP/2000)... 4 INSTALLING AND CONNECTING (MACINTOSH

More information

Recommended Practice for Software Requirements Specifications (IEEE)

Recommended Practice for Software Requirements Specifications (IEEE) Recommended Practice for Software Requirements Specifications (IEEE) Author: John Doe Revision: 29/Dec/11 Abstract: The content and qualities of a good software requirements specification (SRS) are described

More information

Middle East Technical University. Department of Computer Engineering

Middle East Technical University. Department of Computer Engineering Middle East Technical University Department of Computer Engineering TurkHITs Software Requirements Specifications v1.1 Group fourbytes Safa Öz - 1679463 Mert Bahadır - 1745785 Özge Çevik - 1679414 Sema

More information

Develop Unified SNMP, XML, CLI, and Web-based Management for Embedded Real-Time Systems with MIBGuide

Develop Unified SNMP, XML, CLI, and Web-based Management for Embedded Real-Time Systems with MIBGuide 1 Overview Develop Unified SNMP, XML, CLI, and Web-based Management for Embedded Real-Time Systems with MIBGuide SNMP Research International, Inc. Knoxville, Tennessee 1 Overview Support for remote management

More information

Oracle Forms Developer 10g: Build Internet Applications

Oracle Forms Developer 10g: Build Internet Applications Oracle University Contact Us: +966 1 1 2739 894 Oracle Forms Developer 10g: Build Internet Applications Duration: 5 Days What you will learn Oracle Forms Developer 10g is used to build high performance

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/06-6 revision 2 Date: May 22, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation

More information

Introduction to Events

Introduction to Events Facilitation Guide Introduction to Events ( http://www.alice.org/resources/lessons/introduction-to-events/ ) Summary This guide is intended to guide the facilitator through the creation of events and using

More information

WPS Workbench. user guide. "To help guide you through using the WPS user interface (Workbench) to create, edit and run programs"

WPS Workbench. user guide. To help guide you through using the WPS user interface (Workbench) to create, edit and run programs WPS Workbench user guide "To help guide you through using the WPS user interface (Workbench) to create, edit and run programs" Version: 3.1.7 Copyright 2002-2018 World Programming Limited www.worldprogramming.com

More information

Sequence Diagram Generation with Model Transformation Technology

Sequence Diagram Generation with Model Transformation Technology , March 12-14, 2014, Hong Kong Sequence Diagram Generation with Model Transformation Technology Photchana Sawprakhon, Yachai Limpiyakorn Abstract Creating Sequence diagrams with UML tools can be incomplete,

More information

Guide to the Trial Edition

Guide to the Trial Edition Enterprise Architect User Guide Series Guide to the Trial Edition The Trial Edition of Sparx Systems Enterprise Architect provides a free 30-day exploration of the features and facilities of the application,

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/04-023 revision 2 Date: September 06, 2005 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular

More information

Relay Setting Tools CAP 501 Operator s Manual

Relay Setting Tools CAP 501 Operator s Manual Relay Setting Tools CAP 501 Operator s Manual $%% 1MRS751271-MUM Issue date: 31.01.2000 Program revision: 2.0.0 Documentation version: B CAP 501 Relay Setting Tools Operator s Manual Copyright 2000 ABB

More information

Implementation Architecture

Implementation Architecture Implementation Architecture Software Architecture VO/KU (707023/707024) Roman Kern ISDS, TU Graz 2017-11-15 Roman Kern (ISDS, TU Graz) Implementation Architecture 2017-11-15 1 / 54 Outline 1 Definition

More information

<Company Name> <Project Name> Software Requirements Specification For <Subsystem or Feature> Version <1.0>

<Company Name> <Project Name> Software Requirements Specification For <Subsystem or Feature> Version <1.0> For Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed

More information

BPMN Getting Started Guide

BPMN Getting Started Guide Enterprise Studio BPMN Getting Started Guide 2017-09-21 Applies to: Enterprise Studio 3.0.0, Team Server 3.0.0 Table of contents 1 About modeling with BPMN 5 1.1 What is BPMN? 5 1.2 BPMN modeling 5 1.3

More information

Unified Modeling Language

Unified Modeling Language Unified Modeling Language Modeling Applications using Language Mappings Programmer s Reference Manual How to use this Reference Card: The consists of a set of fundamental modeling elements which appear

More information

IBM Rational Rhapsody Gateway Add On. User Manual

IBM Rational Rhapsody Gateway Add On. User Manual User Manual Rhapsody IBM Rational Rhapsody Gateway Add On User Manual License Agreement No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any

More information

Deliverable: D 1.2 Specification of Traceability concepts

Deliverable: D 1.2 Specification of Traceability concepts (ITEA 2 13017) Enabling of Results from AMALTHEA and others for Transfer into Application and building Community around Deliverable: D 1.2 Specification of Traceability concepts Work Package: 1 Continuous

More information

CaseComplete Roadmap

CaseComplete Roadmap CaseComplete Roadmap Copyright 2004-2014 Serlio Software Development Corporation Contents Get started... 1 Create a project... 1 Set the vision and scope... 1 Brainstorm for primary actors and their goals...

More information

Software Engineering Lab Manual

Software Engineering Lab Manual Kingdom of Saudi Arabia Ministry Education Prince Sattam Bin Abdulaziz University College of Computer Engineering and Sciences Department of Computer Science Software Engineering Lab Manual 1 Background:-

More information

Adobe Experience Manager 6.0 Voluntary Product Accessibility Template

Adobe Experience Manager 6.0 Voluntary Product Accessibility Template Adobe Experience Manager 6.0 Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments

More information

IBM Rational Rhapsody Gateway Add On. User Guide

IBM Rational Rhapsody Gateway Add On. User Guide User Guide Rhapsody IBM Rational Rhapsody Gateway Add On User Guide License Agreement No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any

More information

Accessible PDF Documents with Adobe Acrobat 9 Pro and LiveCycle Designer ES 8.2

Accessible PDF Documents with Adobe Acrobat 9 Pro and LiveCycle Designer ES 8.2 Accessible PDF Documents with Adobe Acrobat 9 Pro and LiveCycle Designer ES 8.2 Table of Contents Accessible PDF Documents with Adobe Acrobat 9... 3 Application...3 Terminology...3 Introduction...3 Word

More information

Experiment no 4 Study of Class Diagram in Rational Rose

Experiment no 4 Study of Class Diagram in Rational Rose Experiment no 4 Study of Class Diagram in Rational Rose Objective-: To studyclass Diagram in Rational Rose. References-: www.developer.com The Unified Modeling Language User Guide by Grady Booch Mastering

More information

Pro/ENGINEER Wildfire 2.0 Curriculum

Pro/ENGINEER Wildfire 2.0 Curriculum Pro/ENGINEER Wildfire 2.0 Curriculum Live Classroom Virtual Class Web Based NOTE: For a graphical depiction of the curriculum based on job role, please visit this page: http://www.ptc.com/services/edserv/learning/paths/ptc/proe_wf2.htm

More information

<PROJECT NAME> IMPLEMENTATION PLAN

<PROJECT NAME> IMPLEMENTATION PLAN IMPLEMENTATION PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Project Implementation Plan was controlled and tracked.

More information

Content Author's Reference and Cookbook

Content Author's Reference and Cookbook Sitecore CMS 7.0 Content Author's Reference and Cookbook Rev. 130425 Sitecore CMS 7.0 Content Author's Reference and Cookbook A Conceptual Overview and Practical Guide to Using Sitecore Table of Contents

More information

Tennessee. Business Technology Course Code Web Design Essentials. HTML Essentials, Second Edition 2010

Tennessee. Business Technology Course Code Web Design Essentials. HTML Essentials, Second Edition 2010 Tennessee Business Technology Course Code 6501240 Web Design Essentials HTML Essentials, Second Edition 2010 Notation Key SE Student Edition LE Learning Expectation Standard 1.0 Demonstrate knowledge of

More information

Software Architecture

Software Architecture Software Architecture Does software architecture global design?, architect designer? Overview What is it, why bother? Architecture Design Viewpoints and view models Architectural styles Architecture asssessment

More information

Introduction to Eclipse

Introduction to Eclipse Introduction to Eclipse Getting started with Eclipse 05/02/2010 Prepared by Chris Panayiotou for EPL 233 1 What is Eclipse? o Eclipse is an open source project http://www.eclipse.org Consortium of companies,

More information

Chapter 4 Objectives

Chapter 4 Objectives Chapter 4 Objectives Eliciting requirements from the customers Modeling requirements Reviewing requirements to ensure their quality Documenting requirements for use by the design and test teams 4.1 The

More information

CHAPTER 1 COPYRIGHTED MATERIAL. Finding Your Way in the Inventor Interface

CHAPTER 1 COPYRIGHTED MATERIAL. Finding Your Way in the Inventor Interface CHAPTER 1 Finding Your Way in the Inventor Interface COPYRIGHTED MATERIAL Understanding Inventor s interface behavior Opening existing files Creating new files Modifying the look and feel of Inventor Managing

More information

Software Design Specification

Software Design Specification Software Design Specification for Document Version Prepared by Group Name:

More information

Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS. For IBM System i (5250)

Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS. For IBM System i (5250) Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS For IBM System i (5250) 1 Lab instructions This lab teaches you how to use IBM Rational HATS to create a rich client plug-in application

More information

Adobe Photoshop CS6 Voluntary Product Accessibility Template

Adobe Photoshop CS6 Voluntary Product Accessibility Template Adobe Photoshop CS6 Voluntary Product Accessibility Template The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding

More information

GIS LAB 1. Basic GIS Operations with ArcGIS. Calculating Stream Lengths and Watershed Areas.

GIS LAB 1. Basic GIS Operations with ArcGIS. Calculating Stream Lengths and Watershed Areas. GIS LAB 1 Basic GIS Operations with ArcGIS. Calculating Stream Lengths and Watershed Areas. ArcGIS offers some advantages for novice users. The graphical user interface is similar to many Windows packages

More information

visualstate Reference Guide

visualstate Reference Guide COPYRIGHT NOTICE Copyright 2000 2014 IAR Systems AB. No part of this document may be reproduced without the prior written consent of IAR Systems. The software described in this document is furnished under

More information

Topics in Object-Oriented Design Patterns

Topics in Object-Oriented Design Patterns Software design Topics in Object-Oriented Design Patterns Material mainly from the book Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides; slides originally by Spiros Mancoridis;

More information

European Component Oriented Architecture (ECOA ) Collaboration Programme: Architecture Specification Part 2: Definitions

European Component Oriented Architecture (ECOA ) Collaboration Programme: Architecture Specification Part 2: Definitions European Component Oriented Architecture (ECOA ) Collaboration Programme: Part 2: Definitions BAE Ref No: IAWG-ECOA-TR-012 Dassault Ref No: DGT 144487-D Issue: 4 Prepared by BAE Systems (Operations) Limited

More information

Customized Enterprise Installation of IBM Rational ClearCase Using the IBM Rational ClearCase Remote Client plug-in and the Eclipse SDK

Customized Enterprise Installation of IBM Rational ClearCase Using the IBM Rational ClearCase Remote Client plug-in and the Eclipse SDK Customized Enterprise Installation of IBM Rational ClearCase Using the IBM Rational ClearCase Remote Client plug-in and the Eclipse SDK Fred Bickford IV Senior Advisory Software Engineer IBM Rational Customer

More information

Picture This: Creating Controls on the Fly

Picture This: Creating Controls on the Fly Picture This: Creating Controls on the Fly by Benjamin A. Rayner Architect, Measurement & Automation Data Science Automation, Inc. USA Category: Prototype/Test Products Used: LabVIEW 8.2.1 The Challenge:

More information

[MS55199]: SharePoint 2016 End User Training. Audience Profile This course is intended for new and existing users of SharePoint.

[MS55199]: SharePoint 2016 End User Training. Audience Profile This course is intended for new and existing users of SharePoint. [MS55199]: SharePoint 2016 End User Training Length : 3 Days Audience(s) : Information Workers Level : 100 Technology : Microsoft SharePoint Server Delivery Method : Instructor-led (Classroom) Course Overview

More information

Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS For IBM System i (5250)

Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS For IBM System i (5250) Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS For IBM System i (5250) Introduction to Eclipse Rich Client Platform Support in IBM Rational HATS 1 Lab instructions This lab teaches

More information

Issues surrounding model consistency and QVT

Issues surrounding model consistency and QVT Issues surrounding model consistency and QVT Laurence Tratt, Tony Clark laurie@tratt.net, anclark@dcs.kcl.ac.uk December 6, 200. Introduction This document is intended to outline some of the issues surrounding

More information

Architectural Documentation 1

Architectural Documentation 1 Architectural Documentation Architectural Documentation 1 The Purpose of Architectural Documentation The documentation shall give the reader good understanding of the application's architecture and design.

More information

Middle East Technical University Department of Computer Engineering RECOMMENDER SYSTEM. Software Design Description Document V1.1.

Middle East Technical University Department of Computer Engineering RECOMMENDER SYSTEM. Software Design Description Document V1.1. Middle East Technical University Department of Computer Engineering RECOMMENDER SYSTEM Software Design Description Document V1.1 Dcengo Unchained DuyguKabakcı 1746064 Işınsu Katırcıoğlu 1819432 Sıla Kaya

More information

SharePoint 2013 End User

SharePoint 2013 End User SharePoint 2013 End User Course 55031A; 3 Days, Instructor-led Course Description This SharePoint 2013 End User class is for end users working in a SharePoint 2013 environment. The course teaches SharePoint

More information

BridgePoint Modeling Exercises in Building Executable Models Mentor Graphics Corporation

BridgePoint Modeling Exercises in Building Executable Models Mentor Graphics Corporation BridgePoint Modeling Exercises in Building Executable Models Mentor Graphics Corporation Published April 2013 Copyright 2006-2013 Mentor Graphics Corporation 1. Lab 1 1.1 Background BehindTheTimes Inc.

More information

XBS Application Development Platform

XBS Application Development Platform Introduction to XBS Application Development Platform By: Liu, Xiao Kang (Ken) Xiaokang Liu Page 1/10 Oct 2011 Overview The XBS is an application development platform. It provides both application development

More information

UNIT 5 - UML STATE DIAGRAMS AND MODELING

UNIT 5 - UML STATE DIAGRAMS AND MODELING UNIT 5 - UML STATE DIAGRAMS AND MODELING UML state diagrams and modeling - Operation contracts- Mapping design to code UML deployment and component diagrams UML state diagrams: State diagrams are used

More information

Detailed Design. Java Problem Repository & Education Platform JPREP

Detailed Design. Java Problem Repository & Education Platform JPREP Team Members: Luke Greiner Denis Kalic Abigail McCarthy Robert Tateo Nguyen Truong Patrick White Detailed Design Java Problem Repository & Education Platform JPREP Revision: 1.1 Date: 3/07/14 1 D e l t

More information

IP Office Contact Center 10.X Wallboard Voluntary Product Accessibility Template (VPAT)

IP Office Contact Center 10.X Wallboard Voluntary Product Accessibility Template (VPAT) IP Office Contact Center 10.X Wallboard Voluntary Product Accessibility Template (VPAT) IP Office Contact Center 10.X is a multimedia contact center suite that runs on the Windows Operating System. The

More information

Access Gateway Client User's Guide

Access Gateway Client User's Guide Sysgem Access Gateway Access Gateway Client User's Guide Sysgem AG Sysgem is a trademark of Sysgem AG. Other brands and products are registered trademarks of their respective holders. 2013-2015 Sysgem

More information

CS 2110 Fall Instructions. 1 Installing the code. Homework 4 Paint Program. 0.1 Grading, Partners, Academic Integrity, Help

CS 2110 Fall Instructions. 1 Installing the code. Homework 4 Paint Program. 0.1 Grading, Partners, Academic Integrity, Help CS 2110 Fall 2012 Homework 4 Paint Program Due: Wednesday, 12 November, 11:59PM In this assignment, you will write parts of a simple paint program. Some of the functionality you will implement is: 1. Freehand

More information

THE UNIVERSITY OF BRITISH COLUMBIA CPSC 110: MIDTERM 1 Part B May 26, Important notes about this examination

THE UNIVERSITY OF BRITISH COLUMBIA CPSC 110: MIDTERM 1 Part B May 26, Important notes about this examination THE UNIVERSITY OF BRITISH COLUMBIA CPSC 110: MIDTERM 1 Part B May 26, 2014 Last Name: First Name: Signature: UBC Student #: Important notes about this examination 1. This exam has two separate parts. Your

More information

Voluntary Product Accessibility Template (VPAT)

Voluntary Product Accessibility Template (VPAT) Voluntary Product Accessibility Template (VPAT) The purpose of the Voluntary Product Accessibility Template, or VPAT, is to assist Federal contracting officials and other buyers in making preliminary assessments

More information

WP 15: DBE Business Modeling Language

WP 15: DBE Business Modeling Language D.B.E. Digital Business Ecosystem Contract No: 507953 WP 15: DBE Business Modeling Language D15.2: BML Editor 2 nd Release Project funded by the European Community under FP6 D15.2: BML Editor 2 nd Release

More information

A QUICK OVERVIEW OF THE OMNeT++ IDE

A QUICK OVERVIEW OF THE OMNeT++ IDE Introduction A QUICK OVERVIEW OF THE OMNeT++ IDE The OMNeT++ Integrated Development Environment is based on the Eclipse platform, and extends it with new editors, views, wizards, and additional functionality.

More information

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created>

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created> Software Requirements Specification for Version 1.0 approved Prepared by Copyright 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute

More information

RUP for Systems Z and other Legacy Systems

RUP for Systems Z and other Legacy Systems IBM Software Group RUP for Systems Z and other Legacy Systems Susan M Burk Senior Managing Consultant IBM smburk@us.ibm.com 413-726-9361 2006 IBM Corporation Agenda Objectives A Quick Introduction to RUP

More information

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold.

2.0.3 attributes: A named property of a class that describes the range of values that the class or its instances (i.e., objects) may hold. T0/06-6 revision 0 Date: March 0, 2006 To: T0 Committee (SCSI) From: George Penokie (IBM/Tivoli) Subject: SAM-4: Converting to UML part Overview The current SCSI architecture follows no particular documentation

More information

ACCESSIBILITY POLICY Effective Date: March 20, 2017

ACCESSIBILITY POLICY Effective Date: March 20, 2017 OVERVIEW The federal government requires all public institutions to comply with Rehabilitation Act of 1973, 29 U.S.C. 794d, Section 508, subpart B 1194.22 "Web-based intranet and internet information and

More information

2.5.1: Reforms in Continuous Internal Evaluation (CIE) System at the Institutional Level

2.5.1: Reforms in Continuous Internal Evaluation (CIE) System at the Institutional Level D Y Patil Institute of Engineering and Technology, Ambi, Pune Address:Sr.No.124 & 126, A/p- Ambi, Tal-Maval, MIDC Road, TalegaonDabhade, Pune-410506, Maharashtra, India Tel: 02114306229, E-mail : info@dyptc.edu.in

More information