air - User contributions [en]

RICM4 2017 2018 - Dashboard/ SRS

2018-02-05T11:22:11Z

Titouan.Larnicol: /* 2.2 Product functions */

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"
|+ 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
| TBC
| TBC
| 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 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.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=
=6. Index=

RICM4 2017 2018 - Dashboard/ SRS

2018-02-05T11:20:00Z

Titouan.Larnicol: /* 2.1 Product perspective */

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"
|+ 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
| TBC
| TBC
| 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==
==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=
=6. Index=

RICM4 2017 2018 - Dashboard/ SRS

2018-02-05T11:19:39Z

Titouan.Larnicol: /* 1.2 Scope of the product */

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"
|+ 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
| TBC
| TBC
| 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==
==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=
=6. Index=

RICM4 2017 2018 - Dashboard/ SRS

2018-02-05T11:19:12Z

Titouan.Larnicol: /* 1. Introduction */

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"
|+ 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
| TBC
| TBC
| 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==
==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==
==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=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:22:19Z

Titouan.Larnicol: /* 2.2 Product functions */

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"
|+ 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
| TBC
| TBC
| 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. It describes how the system is supposed to work with functional and non functional requirements.

==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==
SPA : Single Page Application

==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 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.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=

DashBoard-SRS

2018-02-05T10:22:08Z

Titouan.Larnicol: /* 2.2 Product functions */

=1. Introduction=
==1.1 Purpose of the requirements document==
The Software Requirements Specification (SRS) is a document describing the software system of our project: DashBoard for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
Our product is intended for a client, using OAR as manager of resources and tasks

==1.3 Definitions, acronyms and abbreviations==
* Cluster : It is a grouping of multiple servers to perform calculations.
* SPA : Single Page Application

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

==2.2 Product functions ==
* Add/Remove resources
* Submit/Delete jobs
* See information about resources and tasks
* Login/Logout

==2.3 User characteristics==
Client using OAR as manager of resources and tasks

==2.4 General constraints==
*AngularJS
*SB Admin v2.0
*Approach of a SPA

==Add resource==
'''Description :''' Adding a resource to the cluster if all input are good

'''Input :''' Hostname, CPU id, CORE id, MEM, besteffort

'''Output :''' Return a message to the client if the resource is created or not

==Remove resource==
'''Description :''' Delete a resource to the cluster

'''Output :''' Return a message to the client if the resource is deleted or not

==Submit job==
'''Description :''' Submitting a job if the 2 inputs are good

'''Input :''' Resource, Program to run (Name, Type, Reservations, ...)

'''Output :''' Return a message to the client if the job is submitted or not

==Delete job==
'''Description :''' Deleting a job if the 2 inputs are good

'''Output :''' Return a message to the client if the job is submitted or not

==See Resources==
'''Description :''' Describe all the resources

'''Output :''' Table of all resources

==See Jobs==
'''Description :''' Describe all the jobs

'''Output :''' Panel of all jobs

==Login==
'''Description :''' Connect the client

'''Input :''' Username, Password

==Logout==
'''Description :''' Disconnect the client

=4. Product evolution=
* Add more fonctions
* Add graphics to have a better view of the cluster's use

DashBoard-SRS

2018-02-05T10:21:47Z

Titouan.Larnicol: /* 2.2 Product functions */

=1. Introduction=
==1.1 Purpose of the requirements document==
The Software Requirements Specification (SRS) is a document describing the software system of our project: DashBoard for OAR.
It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
Our product is intended for a client, using OAR as manager of resources and tasks

==1.3 Definitions, acronyms and abbreviations==
* Cluster : It is a grouping of multiple servers to perform calculations.
* SPA : Single Page Application

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

==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==
Client using OAR as manager of resources and tasks

==2.4 General constraints==
*AngularJS
*SB Admin v2.0
*Approach of a SPA

==Add resource==
'''Description :''' Adding a resource to the cluster if all input are good

'''Input :''' Hostname, CPU id, CORE id, MEM, besteffort

'''Output :''' Return a message to the client if the resource is created or not

==Remove resource==
'''Description :''' Delete a resource to the cluster

'''Output :''' Return a message to the client if the resource is deleted or not

==Submit job==
'''Description :''' Submitting a job if the 2 inputs are good

'''Input :''' Resource, Program to run (Name, Type, Reservations, ...)

'''Output :''' Return a message to the client if the job is submitted or not

==Delete job==
'''Description :''' Deleting a job if the 2 inputs are good

'''Output :''' Return a message to the client if the job is submitted or not

==See Resources==
'''Description :''' Describe all the resources

'''Output :''' Table of all resources

==See Jobs==
'''Description :''' Describe all the jobs

'''Output :''' Panel of all jobs

==Login==
'''Description :''' Connect the client

'''Input :''' Username, Password

==Logout==
'''Description :''' Disconnect the client

=4. Product evolution=
* Add more fonctions
* Add graphics to have a better view of the cluster's use

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:20:19Z

Titouan.Larnicol: /* 1.3 Definitions, acronyms and abbreviations */

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"
|+ 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
| TBC
| TBC
| 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. It describes how the system is supposed to work with functional and non functional requirements.

==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==
SPA : Single Page Application

==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==
==2.3 User characteristics==
==2.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:18:58Z

Titouan.Larnicol: /* 1.2 Scope of the product */

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"
|+ 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
| TBC
| TBC
| 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. It describes how the system is supposed to work with functional and non functional requirements.

==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==
==2.3 User characteristics==
==2.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:17:23Z

Titouan.Larnicol: /* 1.1 Purpose of the requirements document */

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"
|+ 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
| TBC
| TBC
| 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. It describes how the system is supposed to work with functional and non functional requirements.

==1.2 Scope of the product==
==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==
==2.3 User characteristics==
==2.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:13:58Z

Titouan.Larnicol: /* 2.1 Product perspective */

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"
|+ 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
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
blablabla
==1.2 Scope of the product==
==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==
==2.3 User characteristics==
==2.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=

RICM4 2017 2018 - ChatBot / SRS

2018-02-05T10:12:08Z

Titouan.Larnicol: /* 2.4 General constraints */

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"
|+ 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
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
blablabla
==1.2 Scope of the product==
==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==
==2.2 Product functions==
==2.3 User characteristics==
==2.4 General constraints==

Angular5
SB Admin Angular5 based
SPA development

==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=
=6. Index=