Difference between revisions of "Proj-2013-2014-Open DynDNS/SRS"
Jump to navigation
Jump to search
(Created page with "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-an...") |
|||
| Line 49: | Line 49: | ||
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
==3.1 Requirement X.Y.Z (in Structured Natural Language)== |
||
| + | '''Function''': Implement an open source dynamic DNS server and demon to run on various device (PC, laptop, Android tablet etc) |
||
| − | '''Function''': |
||
| − | '''Description''': |
+ | '''Description''': |
| − | '''Inputs''': |
+ | '''Inputs''': Dynamic IPs |
| + | '''Source''': Users who host their websites or depositories behind a router/modem with dynamic IP |
||
| − | '''Source''': |
||
| − | '''Outputs''': |
+ | '''Outputs''': Dynamic DNS updates |
| − | '''Destination''': |
+ | '''Destination''': Open DynDNS server |
'''Action''': |
'''Action''': |
||
| + | * Open DynDNS client must notify OpenDynDNS server whenever it detects a change in IP adress on the host |
||
| − | * Natural language sentences (with MUST, MAY, SHALL) |
||
| + | * Open DynDNS server updates shall not be modified by non-recognizable device |
||
| − | * 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''': |
| + | * Open DynDNS client may be run on various device such as a laptop, PC or an Android tablet. |
||
| − | '''Pre-condition''': |
+ | '''Pre-condition''': |
'''Post-condition''': |
'''Post-condition''': |
||
Revision as of 14:00, 27 January 2014
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
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | TBC | TBC | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
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: Implement an open source dynamic DNS server and demon to run on various device (PC, laptop, Android tablet etc)
Description:
Inputs: Dynamic IPs
Source: Users who host their websites or depositories behind a router/modem with dynamic IP
Outputs: Dynamic DNS updates
Destination: Open DynDNS server
Action:
- Open DynDNS client must notify OpenDynDNS server whenever it detects a change in IP adress on the host
- Open DynDNS server updates shall not be modified by non-recognizable device
Non functional requirements:
- Open DynDNS client may be run on various device such as a laptop, PC or an Android tablet.
Pre-condition:
Post-condition:
Side-effects: