RICM4 2017 2018 - Dashboard/ SRS - Revision history

Sekina.Belguendouz: Blanked the page

2018-04-07T06:45:59Z

Blanked the page

← Older revision		Revision as of 06:45, 7 April 2018
Line 1:		Line 1:
	{\|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
	\| February 5, 2018
	\| BELGENDOUZ Sekina, LARNICOL Titouan
	\| TBC
	\| TBC
	\| TBC

	\|}


	=1. Introduction=
	==1.1 Purpose of the requirements document==
	The SRS is a document describing the software system of our DashBoard project for OAR.
	==1.2 Scope of the product==


	Our web application is for people using AOR as manager of ressources tasks

	==1.3 Definitions, acronyms and abbreviations==
	==1.4 References==
	==1.5 Overview of the remainder of the document==

	=2. General description=
	==2.1 Product perspective==
	A dashboard web application single page for the task manager and resource OAR.

	==2.2 Product functions==
	* Add/Remove ressources
	* Submit/Delete/Configure jobs
	* See information about ressources and tasks
	* Restricted access : login/Logout
	* Time management of the cluster (check saturated bus ...)
	* Numerous graphic ways to monitor the grid

	==2.3 User characteristics==

	A user who will use the dashboard to manage ressources and tasks

	==2.4 General constraints==

	Make the interface as simple as possible for the user

	Make It enough performant to be easily usable to the users

	==2.5 Assumptions and dependencies==

	=3.Specific requirements, covering functional, non-functional and interface requirements=
	* Use OAR API
	* Availability is important

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

	'''Description''':

	'''Inputs''': A token defining a user and a ressource list

	'''Source''':

	'''Outputs''': A boolean to indicate that the ressource is allocated or not

	'''Destination''':

	'''Action''':
	Select a user -> select ressources and dedicated values (<= available) -> validate -> notify user

	'''Non functional requirements''': -

	'''Pre-condition''': A user token must be created

	'''Post-condition''': The alllocated ressources must be locked to the user (should not apppear as available for the next allocations)

	'''Side-effects''': -

	=4. Product evolution=

	=5. Appendices=
	=6. Index=

Sekina.Belguendouz at 05:40, 12 March 2018

2018-03-12T05:40:47Z

← Older revision		Revision as of 05:40, 12 March 2018
Line 1:		Line 1:
	The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.


	'''Read first:'''
	* 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]

	{\|class="wikitable alternance"		{\|class="wikitable alternance"
	\|+ Document History		\|+ Document History

Aurelien.Surier-Garofalo: /* 3.Specific requirements, covering functional, non-functional and interface requirements */

2018-02-05T11:40:57Z

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

← Older revision		Revision as of 11:40, 5 February 2018
Line 66:		Line 66:

	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=
			* Use OAR API
	* document external interfaces,
			* Availability is important
	* 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)==		==3.1 Requirement X.Y.Z (in Structured Natural Language)==

Aurelien.Surier-Garofalo at 11:37, 5 February 2018

2018-02-05T11:37:24Z

← Older revision		Revision as of 11:37, 5 February 2018
Line 20:		Line 20:
	!scope="row" \|		!scope="row" \|
	\| 0.1.0		\| 0.1.0
			\| February 5, 2018
	\| TBC
			\| BELGENDOUZ Sekina, LARNICOL Titouan
	\| TBC
	\| TBC		\| TBC
	\| TBC		\| TBC

Aurelien.Surier-Garofalo: /* 3.1 Requirement X.Y.Z (in Structured Natural Language) */

2018-02-05T11:30:08Z

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

← Older revision		Revision as of 11:30, 5 February 2018
Line 73:		Line 73:

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

	'''Description''':		'''Description''':

	'''Inputs''':		'''Inputs''': A token defining a user and a ressource list

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

			'''Outputs''': A boolean to indicate that the ressource is allocated or not
	'''Outputs''':

	'''Destination''':		'''Destination''':

	'''Action''':		'''Action''':
			Select a user -> select ressources and dedicated values (<= available) -> validate -> notify user
	* 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''':		'''Non functional requirements''': -

	'''Pre-condition''':		'''Pre-condition''': A user token must be created

			'''Post-condition''': The alllocated ressources must be locked to the user (should not apppear as available for the next allocations)
	'''Post-condition''':

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

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

Joffrey.Ferreira: /* 2.5 Assumptions and dependencies */

2018-02-05T11:26:22Z

2.5 Assumptions and dependencies

← Older revision		Revision as of 11:26, 5 February 2018
Line 64:		Line 64:

	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=
	* document external interfaces,		* document external interfaces,

Joffrey.Ferreira: /* 2.4 General constraints */

2018-02-05T11:24:42Z

2.4 General constraints

← Older revision		Revision as of 11:24, 5 February 2018
Line 58:		Line 58:

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

			Make the interface as simple as possible for the user

			Make It enough performant to be easily usable to the users

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

Aurelien.Surier-Garofalo: /* 2.2 Product functions */

2018-02-05T11:24:04Z

2.2 Product functions

← Older revision		Revision as of 11:24, 5 February 2018
Line 46:		Line 46:

	==2.2 Product functions==		==2.2 Product functions==
	* Add/Remove ~~resources~~		* Add/Remove ressources
	* Submit/Delete jobs		* Submit/Delete/Configure jobs
	* See information about ~~resources~~ and tasks		* See information about ressources and tasks
	* ~~Login~~/Logout		* Restricted access : login/Logout
	* Time management of the cluster ( check ~~saturate~~ bus ...)		* Time management of the cluster (check saturated bus ...)
			* Numerous graphic ways to monitor the grid

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

Joffrey.Ferreira: /* 2.3 User characteristics */

2018-02-05T11:23:51Z

2.3 User characteristics

← Older revision		Revision as of 11:23, 5 February 2018
Line 53:		Line 53:

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

			A user who will use the dashboard to manage ressources and tasks

	==2.4 General constraints==		==2.4 General constraints==
	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

Titouan.Larnicol: /* 2.2 Product functions */

2018-02-05T11:22:11Z

2.2 Product functions

← Older revision		Revision as of 11:22, 5 February 2018
Line 46:		Line 46:

	==2.2 Product functions==		==2.2 Product functions==
			* Add/Remove resources
			* Submit/Delete jobs
			* See information about resources and tasks
			* Login/Logout
			* Time management of the cluster ( check saturate bus ...)

	==2.3 User characteristics==		==2.3 User characteristics==
	==2.4 General constraints==		==2.4 General constraints==