Proj-2015-2016-Extensions IPOPO/SRS - Revision history

Abdelaziz.Founas at 13:21, 4 April 2016

2016-04-04T13:21:24Z

@@ Line 134: / Line 134: @@
-==3.3 Requirement 3 : Creation of a Certificate Authority ==
+==3.3 Requirement 3 : Creation of a Root Certificate Authority ==
 '''Description''':
-The administrator of an iPOPO application can create a certification authority that will allow to generate client certificates.
+The administrator of an iPOPO application can create a root certification authority that will allow him to generate intermediate certificate authority.
 '''Inputs''':
-* Name of the authority to be created
+* Name of the root authority to be created
 * A root certificate authority
 '''Source''':
@@ Line 159: / Line 186: @@
 '''Post-condition''':
 '''Side-effects''':
 ==3.5 Requirement 5 : Creation of a Client's Key and Certificate ==
 ==3.6 Requirement 6 : Revocation of a Client's Certificate ==
 =4. Product evolution=

Marwan.Hallal: /* 3.3 Requirement 3 : Creation of a Certificate Authority */

2016-04-04T09:45:34Z

3.3 Requirement 3 : Creation of a Certificate Authority

@@ Line 135: / Line 135: @@
 ==3.3 Requirement 3 : Creation of a Certificate Authority ==
 ==3.4 Requirement 4 : Creation of a Server's Key and Certificate ==
 ==3.5 Requirement 5 : Creation of a Client's Key and Certificate ==

Remi.Gattaz at 16:35, 7 March 2016

2016-03-07T16:35:25Z

← Older revision		Revision as of 16:35, 7 March 2016
Line 68:		Line 68:

	=3. Specific requirements, covering functional, non-functional and interface requirements=		=3. Specific requirements, covering functional, non-functional and interface requirements=
	* document external interfaces,
	* describe system functionality and performance
	* specify logical database requirements,
	* design constraints,
	* emergent system properties and quality characteristics.

		⚫	==3.1 Requirement 1 : An encrypted remote shell server ==

⚫	==3.1 Requirement 1 : An encrypted remote shell ==

	'''Description''':		'''Description''':
			Service allowing a client to connect with an encrypted connexion to an IPOPO remote shell. The client and the server are mutually authenticated.
	Messages transmitted between the IPOPO instance and a client must be encrypted

	'''Inputs''':		'''Inputs''':
			* Server Key
	'''Source''':
			* Server Certificate

			* Chain of certification
	'''Outputs''':

	'''Destination''':

	'''Action''':
	*

	'''Non functional requirements''':

	'''Pre-condition''':

	'''Post-condition''':

	'''Side-effects''':


⚫	==3.2 Requirement 2 : ==

	'''Description''':
	Clients certificates are generated by an administrator of an IPOPO application. This certificate is signed using the private certificate of the same application and will be used to remotely access to the IPOPO shell.

	'''Inputs''':
	User informations. It includes name and email.

	'''Source''':		'''Source''':
	The information is given by the user to the IPOPO application administrator.

	'''Outputs''':		'''Outputs''':
			* A secured remote shell connection is created for every client providing an accepted certificated
	A new certificate signed with the application private certificate.

	'''Destination''':		'''Destination''': IPOPO application administrator
	The created certificate is given to the user designated in the meta-information of the certificate.

	'''Action''':		'''Action''':
			* Creation of a TCP server
	* A user must ask for the creation of a certificate to the administrator of an IPOPO application. He will provide his name and his mail address with his request
			* SSL wrapping of every new connection
	* The administrator shall generate a new certificate using the given information.
		⚫	* Verification of client certificates
	* The administrator will send the generated certificate to the user who asked for it
			* Reception/Emission of encrypted messages to client


	'''Non functional requirements''':		'''Non functional requirements''':
			* The Server Key, certificates and chain of certification must exist
	* Easy to use
	* The generation can be done on any Linux system (and windows ?)

	'''Pre-condition''':		'''Pre-condition''':
	The administrator must have a server (private) certificate

	'''Post-condition''':		'''Post-condition''':
	Users are identifiable from the certificate they are using

	'''Side-effects''':		'''Side-effects''':
	None

		⚫	==3.2 Requirement 2 : An encrypted remote shell client ==

⚫	~~==3.3~~ ~~Requirement 3 : Revocation~~ of client certificates ==

	'''Description''':		'''Description''':
	Client ~~certificates~~ ~~can~~ be ~~revoked. Preventing any access~~ to ~~the~~ IPOPO shell ~~using~~ the ~~revoked~~ ~~certificate~~.		Client using a secured connection to an encrypted IPOPO remote shell server. The client and the server are mutually authenticated.

	'''Inputs''':		'''Inputs''':
			* Client Key
	Information identifying a single certificate ( email address ?).
			* Client Key
			* Chain of certification

	'''Source''':		'''Source''':

	'''Outputs''':		'''Outputs''':
			* A secured remote shell connection
	An entry is added in the application's revocation list.

	'''Destination''':		'''Destination''': Any IPOPO user

	'''Action''':		'''Action''':
			* Creation of a TCP socket
	* The IPOPO administrator decides to revoke a certificate and retrieve its id.
			* SSL wrapping of the socket
	* The IPOPO administrator revokes a certificate and an entry is added to the revocation list of the application
			* Verification of server's certificates
			* Reception/Emission of encrypted messages

	'''Non functional requirements''':		'''Non functional requirements''':


	'''Pre-condition''':		'''Pre-condition''':
			* The Server Key, certificates and chain of certification must exist
	The soon to be revoked certificate must be valid and identified

	'''Post-condition''':		'''Post-condition''':
	The revoked certificate cannot be used to access the remote shell anymore

	'''Side-effects''':		'''Side-effects''':
	Modify the revoked certificate list on the remote-shell accessible IPOPO instances


			==3.3 Requirement 3 : Creation of a Certificate Authority ==
			==3.4 Requirement 4 : Creation of a Server's Key and Certificate ==
			==3.5 Requirement 5 : Creation of a Client's Key and Certificate ==
			==3.6 Requirement 6 : Revocation of a Client's Certificate ==

	=4. Product evolution=		=4. Product evolution=

Remi.Gattaz at 15:40, 7 March 2016

2016-03-07T15:40:46Z

@@ Line 27: / Line 27: @@
 ==1.2 Scope of the product==
 ==1.3   Definitions, acronyms and abbreviations==
 ==1.4   References==
 The main page of the project: [[Services étendus pour le modèle de composants iPOPO pour Python | '''IPOPO Projects''']]
 ==1.5   Overview of the remainder of the document==
 =2.   General description=
 ==2.1   Product perspective==
 ==2.2   Product functions==
 ==2.3   User characteristics==
 ==2.4   General constraints==
 ==2.5   Assumptions and dependencies==
 * document external interfaces,
 * describe system functionality and performance
@@ Line 46: / Line 74: @@
 * emergent system properties and quality characteristics.
-==3.1 Requirement 1 : Creation of client certificates ==
+==3.1 Requirement 1 : An encrypted remote shell ==
 '''Description''':
@@ Line 83: / Line 136: @@
-==3.2 Requirement 2 : Revocation of client certificates ==
+==3.3 Requirement 3 : Revocation of client certificates ==
 '''Description''':
@@ Line 113: / Line 166: @@
 '''Side-effects''':
 Modify the revoked certificate list on the remote-shell accessible IPOPO instances

Remi.Gattaz at 13:39, 19 January 2016

2016-01-19T13:39:31Z

@@ Line 83: / Line 83: @@
-==3.3 Requirement 2 : Revocation of client certificates ==
+==3.2 Requirement 2 : Revocation of client certificates ==
 '''Description''':
@@ Line 94: / Line 94: @@
 '''Outputs''':
-An entry is asked in the application revocation list.
+An entry is added in the application's revocation list.
 '''Destination''':
 '''Action''':
 '''Non functional requirements''':
+*
 '''Pre-condition''':
@@ Line 110: / Line 138: @@
 '''Side-effects''':
 =4. Product evolution=

Remi.Gattaz at 15:50, 18 January 2016

2016-01-18T15:50:39Z

@@ Line 46: / Line 46: @@
 * emergent system properties and quality characteristics.
-==3.1 Requirement X.Y.Z (in Structured Natural Language)==
+==3.1 Requirement 1 : Creation of client certificates ==
 '''Description''':
 '''Inputs''':
 '''Source''':
 '''Outputs''':
 '''Destination''':
 '''Action''':
 '''Non functional requirements''':
 '''Pre-condition''':
@@ Line 72: / Line 110: @@
 '''Side-effects''':
 =4. Product evolution=

Remi.Gattaz at 14:20, 18 January 2016

2016-01-18T14:20:43Z

← Older revision		Revision as of 14:20, 18 January 2016
Line 14:		Line 14:
	\| January 18, 2016		\| January 18, 2016
	\| Marwan HALLAL, Rémi GATTAZ, Abdelaziz FOUNAS		\| Marwan HALLAL, Rémi GATTAZ, Abdelaziz FOUNAS
			\| Creation of the document
	\| IPOPO description
	\| TBC		\| TBC
	\| TBC		\| TBC
Line 22:		Line 22:

	=1. Introduction=		=1. Introduction=
	==Purpose of the requirements document==		==1.1 Purpose of the requirements document==
	This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.		This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.
	In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.		In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

	==Scope of the product==		==1.2 Scope of the product==

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	==1.4 References==		==1.4 References==
	*The main page of the project: [[~~Proj-2013-2014-StartAIR-2~~]]		The main page of the project: [[Services étendus pour le modèle de composants iPOPO pour Python \| '''IPOPO Projects''']]

	==1.5 Overview of the remainder of the document==		==1.5 Overview of the remainder of the document==

Marwan.Hallal: /* 1.1 Purpose of the requirements document */

2016-01-18T14:13:16Z

1.1 Purpose of the requirements document

← Older revision		Revision as of 14:13, 18 January 2016
Line 22:		Line 22:

	=1. Introduction=		=1. Introduction=
	==~~1.1~~ Purpose of the requirements document==		==Purpose of the requirements document==
	This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.		This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.
	In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.		In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

Marwan.Hallal: /* 1.2 Scope of the product */

2016-01-18T14:12:59Z

1.2 Scope of the product

← Older revision		Revision as of 14:12, 18 January 2016
Line 26:		Line 26:
	In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.		In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

	==~~1.2~~ Scope of the product==		==Scope of the product==

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	==1.4 References==		==1.4 References==

Remi.Gattaz: Created page with " {|class="wikitable alternance" |+ Document History |- | !scope="col"| Version !scope="col"| Date !scope="col"| Authors !scope="col"| Description !scope="col"| Validat..."

2016-01-18T14:03:00Z

Created page with " {|class="wikitable alternance" |+ Document History |- | !scope="col"| Version !scope="col"| Date !scope="col"| Authors !scope="col"| Description !scope="col"| Validat..."

New page

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| January 18, 2016
| Marwan HALLAL, Rémi GATTAZ, Abdelaziz FOUNAS
| IPOPO description
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.
In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

==1.2 Scope of the product==
==1.3 Definitions, acronyms and abbreviations==
==1.4 References==
*The main page of the project: [[Proj-2013-2014-StartAIR-2]]

==1.5 Overview of the remainder of the document==
=2. General description=
==2.1 Product perspective==
==2.2 Product functions==
==2.3 User characteristics==
==2.4 General constraints==
==2.5 Assumptions and dependencies==
=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''':

'''Source''':

'''Outputs''':

'''Destination''':

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

'''Non functional requirements''':

'''Pre-condition''':

'''Post-condition''':

'''Side-effects''':

=4. Product evolution=

=5. Appendices=

==5.1. SRS structure==
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.

'''References:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

=6. Index=