Background Background 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’ • 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
Transcript
BackgroundBackgroundBackgroundBackground
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
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
Problem domainProblem domainBackground
Problem Problem domaindomain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
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 domainProblem 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.
Background
Problem Problem domaindomain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-cases
Risks
Current SituationCurrent SituationBackground
Problem domain
Current Current situationsituation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-cases
Risks
•kuigkjgh
Proposed solutionProposed solutionBackground
Problem domain
Current situation
Proposed Proposed solutionsolution
System architecture
Functional requirements
Non-functionalrequirements
Major use-cases
Risks
System architectureSystem architecture
ךלחיךחלי•
Background
Problem domain
Current situation
Proposed solution
System System
architecturearchitecture
Functional requirements
Non-functionalrequirements
Major use-cases
Risks
Network 1
EncoderEncoder
CameraCamera
Switch
Archiver DirectoryEDBClient
The new application
Network 2
EncoderEncoder
CameraCamera
Switch
System architectureSystem architecture
• Technologies:– The system is developed under .NET platform using C#.
– The system interfaces to data base of type SQL Server 2003.
• Platform constraints– Developers– Clients– The system
• SE Project constraints– Equipment– Project presentation
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalNon-functional
requirementsrequirements
Major use-cases
Risks
Major use-casesMajor use-cases• Network units identification
• Profiles definition
• Users definition
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Network units Network units identificationidentification
• 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.
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Network units Network units identificationidentification
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Profiles definitionProfiles 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.
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Profiles definitionProfiles definitionBackground
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Users definitionUsers 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.
Background
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
Users definitionUsers definitionBackground
Problem domain
Current situation
Proposed solution
System architecture
Functional requirements
Non-functionalrequirements
Major use-casesMajor use-cases
Risks
RisksRisks• Complex configuration process, can lead to result that is different
