Proj-2013-2014-Open DynDNS/SRS - Revision history

RICM4-prj14-grp11 at 14:45, 9 April 2014

2014-04-09T14:45:20Z

2014-04-09T14:44:54Z

← Older revision		Revision as of 14:44, 9 April 2014
Line 41:		Line 41:
	\| [[User:Thomas CALMANT\|Thomas Calmant]]		\| [[User:Thomas CALMANT\|Thomas Calmant]]
	\| 18/2/2014		\| 18/2/2014
	\|}		\|
			\|-
			!scope="row" \|
			\| 1.0.0
			\| 20/3/2014
			\| [[User:Lionel BOEY\|Lionel Boey]]
			\| Completed version
			\| [[User:Thomas CALMANT\|Thomas Calmant]]
			\| 21/3/2014
			\|
			}

2014-04-03T13:08:10Z

3.1 Requirement X.Y.Z (in Structured Natural Language)

← Older revision		Revision as of 13:08, 3 April 2014
Line 169:		Line 169:
	- Android tablette (Nexus 10)		- Android tablette (Nexus 10)
	- 2 machine running on Linux		- 2 machine running on Linux
			- Routers must set-up port forwarding for HTTP and DNS

	*Software		*Software
	- Ubuntu desktop		- Ubuntu desktop

	- mDNS ~~clients~~		- mDNS daemons

	- Flask API and Flask REST-ful		- Flask API and Flask REST-ful

	- ~~Kivy~~		- Bind9

	- Liclipse for Python

2014-04-03T12:58:17Z

2.2 Product functions

← Older revision		Revision as of 12:58, 3 April 2014
Line 114:		Line 114:


	* Let it be known that the connection between server and client is protected with and SSL connection.		Let it be known that the connection between server and client is protected with and SSL connection. Updates are sent securely on any network while the identity of the client will be always be verified.

	* If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.		If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.

	==2.3 User characteristics==		==2.3 User characteristics==

2014-04-03T12:57:16Z

2.2 Product functions

← Older revision		Revision as of 12:57, 3 April 2014
Line 114:		Line 114:


			* Let it be known that the connection between server and client is protected with and SSL connection.
⚫	If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.

		⚫	* If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.

	==2.3 User characteristics==		==2.3 User characteristics==

2014-04-03T12:56:11Z

2.3 User characteristics

← Older revision		Revision as of 12:56, 3 April 2014
Line 123:		Line 123:


	'''~~Users~~'''		'''Clients'''
	~~Users~~ should be able to install Kivy and the daemon on their respective devices such as tablets and laptops.		Clients should be able to install Kivy and the daemon on their respective devices such as tablets and laptops.

	==2.4 General constraints==		==2.4 General constraints==

2014-04-03T12:54:52Z

2.5 Assumptions and dependencies

← Older revision		Revision as of 12:54, 3 April 2014
Line 133:		Line 133:
	- HTTP requests (GET, PUT, POST) are enabled on most public wifi network and small private network of a company		- HTTP requests (GET, PUT, POST) are enabled on most public wifi network and small private network of a company

	- DNS queries are enabled on any ~~public~~ network ~~but disabled on small private network of a company~~		- DNS queries are enabled on any network

	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=

2014-04-03T12:54:18Z

2.2 Product functions

← Older revision		Revision as of 12:54, 3 April 2014
Line 111:		Line 111:
	When a newly arrived client or service server arrives on the network, it should be able to locate the DNS servers immediately and sends a REST update to the said DNS server with its new local IP address. From then onwards, the client running the daemon will be accessible by anyone in the network.		When a newly arrived client or service server arrives on the network, it should be able to locate the DNS servers immediately and sends a REST update to the said DNS server with its new local IP address. From then onwards, the client running the daemon will be accessible by anyone in the network.

	The client also automatically sends a REST update when it leaves a network.		The client also automatically sends a REST update when it leaves the network.

2014-04-03T12:53:59Z

2.2 Product functions

← Older revision		Revision as of 12:53, 3 April 2014
Line 109:		Line 109:

	* '''Local'''		* '''Local'''
			When a newly arrived client or service server arrives on the network, it should be able to locate the DNS servers immediately and sends a REST update to the said DNS server with its new local IP address. From then onwards, the client running the daemon will be accessible by anyone in the network.
	A newly arrived user on the local network implementing this version of the software will be able to obtain DNS replies immediately regarding various servers situated inside the multicast network, without having to configure anything on its own machine.

			The client also automatically sends a REST update when it leaves a network.


	If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.		If UPnP is enable on this network, any external user will be able to resolve DNS names to all the machines in the private multicast network.

2014-04-03T12:49:24Z

← Older revision		Revision as of 12:49, 3 April 2014
Line 58:		Line 58:
	* BIND : Berkeley Internet Name Domain		* BIND : Berkeley Internet Name Domain
	* REST : Representational state transfer		* REST : Representational state transfer
			* MDNS : Multicast DNS
	* JSON : JavaScript Object Notation		* JSON : JavaScript Object Notation

Line 64:		Line 65:
	*Kivy : open source Python library for developing multitouch application software with a natural user interface (NUI).		*Kivy : open source Python library for developing multitouch application software with a natural user interface (NUI).
	*Flask : A lightweight web application framework written in Python		*Flask : A lightweight web application framework written in Python
			*Zeroconf : Short for zero configuration IP networking, a method of networking devices via an Ethernet cable without requiring configuration and administration.

	==1.4 References==		==1.4 References==