1 / 18

Background

Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks. Latitude 5.0 is a platform which enables its users to manage cameras, sensors, microphones, relay motors etc’

mervin
Download Presentation

Background

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Latitude 5.0 is a platform which enables its users to manage cameras, sensors, microphones, relay motors etc’ During the development a need for easy, fast and simple way of deploy and administer the NVMS is realized Small and medium businesses utilize the system for the basic need to record and view video from 4 to 32 cameras Background

  2. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks 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. Problem domain

  3. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Problem domain • Unit:A unit, also known as an edge device, refers to any external device controlled by an Archiver. The units included in the system are: encoders, decoders and IP cameras (which contain built-in encoders). • Control Center:is Latitude's client application for monitoring and reviewing video, audio and alarms.

  4. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks kuigkjgh Current Situation

  5. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Proposed solution

  6. The new application Switch Switch Client Archiver EDB Directory Encoder Encoder Encoder Encoder Network 1 Network 2 Camera Camera Camera Camera Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks System architecture • ךלחיךחלי

  7. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks System architecture • Technologies: • The system is developed under .NET platform using C#. • The system interfaces to data base of type SQL Server 2003.

  8. Profile Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Functional requirements • Network Identification • Storage initialization • Network units identification • System initialization • Profiles definition • Users definition • Control Center • Graphical view Digital Video quality Analog video quality Recording Admin Viewer Guest

  9. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Non-functional requirements • Performance constraints • Speed • Capacity • Availability • Reliability • Usability • Safety & Security • Platform constraints • Developers • Clients • The system • SE Project constraints • Equipment • Project presentation

  10. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Major use-cases • Network units identification • Profiles definition • Users definition

  11. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Network units identification • The story: The Admin initiate the edge units discovery process and in the end of it the Admin selects which specific units to include in the system. • The revealing of the edge devices is done by an existing process called Discovery. The Discovery process reveals units on one network only, and we will have to apply this process to all of our different networks in the system. • Primary Actors: Admin. • Preconditions: The process of network identification was completed. • Post conditions: All the edge units are discovered and the specified units are attached to the network the Admin filled.

  12. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Network units identification

  13. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Profiles definition • The story: The Admin wishes to define new profiles in the system. The profiles can be from three different categories: Digital video quality, Analog video quality and Recording. Each profile is attached to a specific unit along with coverage which describes when the profile is activated. • Primary Actors: Admin. • Preconditions: The edge units the Admin wishes to attach the new profile to have already been discovered and attached to our network. • Post conditions: New profiles are defined in the system and are attached to specific edge units with a schedule, by which they will be activated.

  14. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Profiles definition

  15. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Users definition • The story: The Admin defines new users in the system. The Admin can define three types of users: other Admin users, Viewer and Guest, which differ in their authorizations (see 2.6).Each user in the system is authenticated by a unique username and password. • Primary Actors: Admin. • Preconditions: The Admin is logged in the system. • Post conditions: New users are defined in the system and are authorized to perform a specific set of actions.

  16. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Users definition

  17. Background Problem domain Current situation Proposed solution System architecture Functional requirements Non-functional requirements Major use-cases Risks Risks • Complex configuration process, can lead to result that is different from the purpose. • Security breach • Wrong use of network units

  18. THE END

More Related