1

Closed

Specification Document

description

Specification Document which explains the purpose of the application and collects all its requirements

Sample application will be e.g Flick feed reader that simply demonstrates how the same webcontent /-service can be scaled at different platforms. There is The Flickr.Net API Library for accessing the Flickr API. Current CodePlex Flickr.NET API is written in C# and it can be accessed from the following framework:
*.Net Framework 2.0 and above.
*.Net Compact Framework 2.0 SP1 and above.
*Silverlight 3.0 and above.
*Windows 7 Phone
*Mono
*Monotouch for iPhone

cross-platform requirements for Flickr application
*easy to create different UI Views based on the multiple web clients
*mobile connectivity and bandwidth issues

Scenario

Scenario where user can view and search Flickr pictures with the device.
  1. Users should be able to view list of Flickr Categories with the device
  2. The category list should be searchable
  3. User should be able to choose one picture from the Category list
  4. Using device input method user should be able retrieve picture to View
Closed Mar 3, 2013 at 3:25 PM by pekollik
removing comment

comments

pekollik wrote Mar 2, 2013 at 1:00 PM

Jump to: navigation, search

A Software requirements specification (SRS), a requirements specification for a software system, is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

The software requirements specification document enlists all necessary requirements that are required for the project development.[1] To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with the project team and customer. A example organization of an SRS is as follows [2][3]
Introduction
    Purpose
    Definitions
    System overview
    References
Overall description
    Product perspective
        System Interfaces
        User Interfaces
        Hardware interfaces
        Software interfaces
        Communication Interfaces
        Memory Constraints
        Operations
        Site Adaptation Requirements
    Product functions
    User characteristics
    Constraints, assumptions and dependencies
Specific requirements
    External interface requirements
    Functional requirements
    Performance requirements
    Design constraints
        Standards Compliance
    Logical database requirement
    Software System attributes
        Reliability
        Availability
        Security
        Maintainability
        Portability
    Other requirements

wrote Mar 2, 2013 at 1:51 PM

wrote Mar 2, 2013 at 8:31 PM

wrote Mar 2, 2013 at 8:31 PM

wrote Mar 3, 2013 at 3:22 PM

wrote Mar 3, 2013 at 3:25 PM

wrote May 16, 2013 at 6:17 AM