Team: Maya Zalcberg Diana Attar Levona Hershtik Academic advisor: Prof. Ehud Gudes ADD Presentation.

Slides:



Advertisements
Similar presentations
Logical and Physical Design of an Information System
Advertisements

Always Best Connected Architecture and Design Rajesh Mishra Ericsson Berkeley Wireless Center.
Database System Concepts and Architecture
A new Network Concept for transporting and storing digital video…………
Lecture-7/ T. Nouf Almujally
UNDERSTANDING JAVA APIS FOR MOBILE DEVICES v0.01.
RFID Shelving ADD Presentation: 19 Mar 2007 Guy Shtub Idit Gershoni.
IMS1907 Database Systems Week 5 Database Systems Architecture.
A CHAT CLIENT-SERVER MODULE IN JAVA BY MAHTAB M HUSSAIN MAYANK MOHAN ISE 582 FALL 2003 PROJECT.
14.1 © 2004 Pearson Education, Inc. Exam Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure.
Security and Digital Recording System Students: Gadi Marcu, Tomer Alon Number:D1123 Supervisor: Erez Zilber Semester:Spring 2004 Mid Semester Presentation.
Background Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major.
Authentication Center for SDP Federation Motorola Israel Project: ADD The Team: Alina Mirinzon Gabi Brontvin Raz Zieber Dadi Suissa.
(NHA) The Laboratory of Computer Communication and Networking Network Host Analyzer.
Ch 12 Distributed Systems Architectures
Chapter 4: Database Management. Databases Before the Use of Computers Data kept in books, ledgers, card files, folders, and file cabinets Long response.
Strabismus Checking System The Team: Lior Barak Omri Mosseri Application Design Document.
Academic Advisor: Dr. Yuval Elovici Professional Advisor: Yuri Granovsky Team: Yuri Manusov Yevgeny Fishman Boris Umansky.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Overview of Database Languages and Architectures.
Operating Systems.
Automatic Software Testing Tool for Computer Networks ARD Presentation Adi Shachar Yaniv Cohen Dudi Patimer
Database Environment 1.  Purpose of three-level database architecture.  Contents of external, conceptual, and internal levels.  Purpose of external/conceptual.
Chapter 9 Elements of Systems Design
Forms Authentication, Users, Roles, Membership Svetlin Nakov Telerik Corporation
MAHI Research Database Data Validation System Software Prototype Demonstration September 18, 2001
COMP 410 & Sky.NET May 2 nd, What is COMP 410? Forming an independent company The customer The planning Learning teamwork.
A Metadata Catalog Service for Data Intensive Applications Presented by Chin-Yi Tsai.
Automatic Software Testing Tool for Computer Networks ADD Presentation Dudi Patimer Adi Shachar Yaniv Cohen
Course Presentation EEL5881, Fall, 2003 Project: Network Reliability Tests Project: Network Reliability Tests Team: Gladiator Team: Gladiator Shuxin Li.
Module 7: Fundamentals of Administering Windows Server 2008.
SUSE Linux Enterprise Desktop Administration Chapter 12 Administer Printing.
Module 10: Monitoring ISA Server Overview Monitoring Overview Configuring Alerts Configuring Session Monitoring Configuring Logging Configuring.
National Center for Supercomputing Applications NCSA OPIE Presentation November 2000.
MCTS Guide to Microsoft Windows Server 2008 Applications Infrastructure Configuration (Exam # ) Chapter Four Windows Server 2008 Remote Desktop Services,
Database Administration COMSATS INSTITUTE OF INFORMATION TECHNOLOGY, VEHARI.
Local Alarm Station Data Acquisition, Storage and Visualization for Radiation Portal Monitor (RPM).
Oracle 10g Database Administrator: Implementation and Administration Chapter 2 Tools and Architecture.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
A ISP free video conferencing application for mobile devices using wireless and VoIP Technology.
The Client/Server Database Environment Ployphan Sornsuwit KPRU Ref.
Overview of the SAS® Management Console
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved. Computer Software Chapter 4.
Chapter 1 Introduction to Databases. 1-2 Chapter Outline   Common uses of database systems   Meaning of basic terms   Database Applications  
9 Systems Analysis and Design in a Changing World, Fourth Edition.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
1 CMPT 275 High Level Design Phase Modularization.
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
Experiment Management System CSE 423 Aaron Kloc Jordan Harstad Robert Sorensen Robert Trevino Nicolas Tjioe Status Report Presentation Industry Mentor:
Core 3: Communication Systems. Network software includes the Network Operating Software (NOS) and also network based applications such as those running.
Jini Architecture Introduction System Overview An Example.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Java Programming: Advanced Topics 1 Enterprise JavaBeans Chapter 14.
Network Monitoring Through Mobile (MOBTOP) Developed By : Akanksha Jain. (102199) Shikha Arora (101319) Team Name: Beans Course: CS532 Guided By:Prof.
Gaia An Infrastructure for Active Spaces Prof. Klara Nahrstedt Prof. David Kriegman Prof. Dennis Mickunas
Technician Table Editor Academic advisor : Professor Ehud Gudes Technical advisor : Menny Even Danan Team: Olga Peled Doron Avinoam Ira Zaitsev ADD Presentation.
Interstage BPM v11.2 1Copyright © 2010 FUJITSU LIMITED INTERSTAGE BPM ARCHITECTURE BPMS.
START Application Spencer Johnson Jonathan Barella Cohner Marker.
 Project Team: Suzana Vaserman David Fleish Moran Zafir Tzvika Stein  Academic adviser: Dr. Mayer Goldberg  Technical adviser: Mr. Guy Wiener.
9 Systems Analysis and Design in a Changing World, Fifth Edition.
VIRTUAL NETWORK COMPUTING SUBMITTED BY:- Ankur Yadav Ashish Solanki Charu Swaroop Harsha Jain.
Technician Table Editor Company: DVTel Academic advisor: Professor Ehud Gudes Technical advisor: Menny Even Danan Team: Olga Peled Doron Avinoam.
Architecture Review 10/11/2004
The Client/Server Database Environment
Configuration for Network Security
THE STEPS TO MANAGE THE GRID
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
Data, Databases, and DBMSs
File service architecture
Presentation transcript:

Team: Maya Zalcberg Diana Attar Levona Hershtik Academic advisor: Prof. Ehud Gudes ADD Presentation

System Requirements System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Network Identification Storage Initialization Network Units Identification System Initialization Profiles Definition Schedules Definition Users Definition Control Center Graphical View - Video profile - Picture profile - Recording profile - Admin - Viewer - Guest

System Architecture ךלחיךחלי Network 1 Encoder Camera Switch ArchiverDirectoryEDBClient The new application Network 2 Encoder Camera Switch System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

System Architecture (cont’d) Archiver: a server component in charged of the Discovery process, archiving video and managing edge units. Directory: one of the control components. In charge of managing access to the various applications, maintaining a repository of all system settings and simplifying database structure. EDB: Event Distributor, is used as an interface for passing events and actions between different components, as well as between the system and external devices and programs. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

System Architecture (cont’d) On the client side The new application interfaces to database of type SQL Server 2003, which holds the entire systems’ data There is no need for installing external software The clients’ only requirement is to have CPU power of Pentium 4 System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Main Classes System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Main Classes (cont’d) GUI This module represents a graphical user interface, through which the user communicates with the system. This module contains all the different screens. This module “listens” to the user requests. Once a user request is made, it is transferred to the GUI Façade for handling it. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Main Classes (cont’d) Physical Package This module is in charge of the communication with the operating system. For example: defining storage, discovering networks and executing the ARP protocol. Additional responsibility: discovering the edge devices. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Logical Package This module is in charge of the logical aspect of the system. For example: creating new profiles, creating new schedules, attaching schedules to units, etc’.

Main Classes (cont’d) User Management Package Responsible for creating new user of a specific type and adding new privilege to him. Also responsible for managing the authentication process. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Data Access Package This module is in charge of managing the access to : - the DVTel SQL Server database. - the general configuration file. - the localization configuration file. This module also stores and uploads the system definitions.

Main Classes (cont’d) Physical Package - PhysicalMngr: responsible of the systems’ physical configuration. - DVTelPhysicalFacade: responsible of the communication between the DVTel system API and the physical package. - OSFacade: responsible of the communication with the operating system. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Logical Package - SceneFactory: responsible of creating a suitable scene for each port of the edge devices, selected by the user and displaying video.. - ScheduleMngr: responsible of managing the schedules’ operations. - DVTelLogicalFacade: responsible of the communication between the DVTel system API and the logical package.

Main Classes (cont’d) System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Data Access Package User Management Package - DBHandler: responsible of all communication with the different databases of the system. - DVTelUserMngFacade: responsible of the communication between the DVTel system API and the user management package. - UserMngr: responsible of the different users scenarios in the system.

Class Diagram System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Class Diagram (cont’d) System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

In order to avoid saving the same data in several different places, we will use the DVTel database. To represent new aspects of our system that does not exist currently we will add the following tables to the database: DB (tables description) System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

- Users: this table describes the different user types. The user type acts as a unique identifier. Tables Description (cont’d) - Privileges: this table describes the different privileges that exist in the system. Each privilege has a unique identifier. - Users-Privileges: this table describes for each user type his set of authorized privileges in the system and his set of denied privileges. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Main Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface View Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Build New Profile Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Build New Schedule Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Attach Schedule Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Camera Details Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

User Interface Add user Screen System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Testing Capacity We will check that the system does not allow to attach more than 32 edge units (as defined in the specification). We will check that the system still work properly with the maximal number of units attached to it. Availability We will check that the system does not crush after an extended and consecutive run. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Testing (cont’d) Safety & Security We will try to login the system using an incorrect username/password. We will try to login the system as a Viewer and perform operation that we are not authorized to. We will try to login the system as a Guest and perform operation that we are not authorized to. Data Integrity We will change the system definitions and check that these changes indeed took place. We will check the integrity and correctness of data stored in the database. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List

Create and integrate the GUI. Creation of the different Schedule entities. Creation of the different Profile entities. Add ability to attach Schedule to a unit. Implementing the login process. System Requirements System Architecture Main classes Class Diagram Tables Description User Interface Testing Task List Add ability to present lists of existing entities