SRS - Sign2Speech: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
No edit summary
Line 15: Line 15:
== Assumptions and dependencies ==
== Assumptions and dependencies ==


= Specific requirements, covering functional, non-functional and interface requirements =document external interfaces,
= Specific requirements, covering functional, non-functional and interface requirements =
* document external interfaces,
* document external interfaces,
* describe system functionality and performance
* describe system functionality and performance
Line 22: Line 22:
* emergent system properties and quality characteristics.
* emergent system properties and quality characteristics.


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


Line 48: Line 48:


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






Revision as of 11:53, 25 January 2016

Introduction

Purpose of the requirements document

Scope of the product

Glossary

References

Overview of the remainder of the document

General Description

Product perspective

Product functions

User characteristics

Operating environment

General constraints

Assumptions and dependencies

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.

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

Function:Live transcription

Description: When the receptionist speak a live transcription can be seen by both users.

Inputs: Voice command or button press to start the transcription.

Source: Mouse or microphone.

Outputs: Screen (Touchscreen?)

Destination: This device is designed to used in a reception environment susceptible of welcoming deaf (or impaired) people.(University, Post office...)

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:


Other Nonfunctional Requirements

Performance requirements

Safety requirements

Security requirements

Software quality attributes

Project documentation

User documentation

Other Requirements

Appendix A: Terminology/Glossary/Definitions list

Appendix B: To be determined