This is not the document you are looking for? Use the search form below to find more!

Report home > Others

Srs template

0.00 (0 votes)
Document Description
Srs template
File Details
  • Added: April, 25th 2011
  • Reads: 897
  • Downloads: 28
  • File size: 319.27kb
  • Pages: 8
  • Tags:
  • content preview
Submitter
  • Name: theo
Embed Code:

Add New Comment




Related Documents

Marketing Plan Template

by: samanta, 8 pages

The purpose of writing a marketing plan is to focus your efforts and money towards what will most increase the profits of your business. The point is not to write a large 100 page plan that is too ...

KORG nanoKontrol Skin Template

by: Yuliyan Ilev, 1 pages

This is a skin template for the KORG nanoKONTROL. It is fully editable in Illustrator. Just replace the skin with your favourite graphics and print. Cut off the pink areas and stick it on your Korg ...

Headband Template

by: Alex, 1 pages

Headband template

Leading Drupal Template Development Company - Openxcell.Inc

by: androidapplication, 2 pages

Drupal Template Theme Development - OpenXcell has professional and expertise drupal template and theme developer team to provide custom Drupal 6 and Drupal 7 templates. Openxcell is leading Drupal ...

Joomla Template Development at www.openxcell.com

by: androidapplication, 2 pages

Joomla Template Development - Openxcell is Joomla based open source Joomla CMS development company. Reach to Openxcell for expert Joomla Template Developer.

Quality manual template example

by: iso9001checklist, 11 pages

ISO 9001 quality manual template example

ISO 9001 quality manual template example

by: iso9001checklist, 11 pages

ISO 9001 quality manual template example

SRS Prime Floor Palwal – Vision Plus Properties in Palwal @9891700111

by: visionplusproperties, 7 pages

FRESH BOOKING OPEN IN Prime Floors Srs City Sector- 6, Palwal. Size 180 sq yd & 250 sq yd starting Rs. 13.75 lacs. Booking amount Rs. 1,50,000/- Possession within 24 months. SRS City is a 106 ...

FREE PPT TEMPLATE FROM BUYAPRESENTATION

by: buyapresentation, 21 pages

free premium presentation template from buyapresentation.com. Visit us to download the ppt/pptx file

Prime Floors Srs City Sector- 6, Palwal

by: visionplusproperties, 2 pages

FRESH BOOKING OPEN IN Prime Floors Srs City Sector- 6, Palwal. Size 180 sq yd & 250 sq yd starting Rs. 13.75 lacs. Booking amount Rs. 1,50,000/- Possession within 24 months. SRS City is a 106 ...

Content Preview
Software Requirements Specification for <Project> Version 1.0 approved Prepared by <author> <organization> <date created> Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. Software Requirements Specification for <Project> Page ii Table of Contents Table of Contents ..................................................................................................................... ii Revision History ....................................................................................................................... ii 1. Introduction ......................................................................................................................... 1 1.1 Purpose ....................................................................................................................................... 1 1.2 Document Conventions ................................................................................................................ 1 1.3 Intended Audience and Reading Suggestions ................................................................................ 1 1.4 Project Scope .............................................................................................................................. 1 1.5 References................................................................................................................................... 1 2. Overall Description .............................................................................................................. 2 2.1 Product Perspective ..................................................................................................................... 2 2.2 Product Features ......................................................................................................................... 2 2.3 User Classes and Characteristics ................................................................................................. 2 2.4 Operating Environment ................................................................................................................ 2 2.5 Design and Implementation Constraints ....................................................................................... 2 2.6 User Documentation .................................................................................................................... 2 2.7 Assumptions and Dependencies ................................................................................................... 3 3. System Features ................................................................................................................... 3 3.1 System Feature 1 ......................................................................................................................... 3 3.2 System Feature 2 (and so on) ....................................................................................................... 4 4. External Interface Requirements ........................................................................................ 4 4.1 User Interfaces ............................................................................................................................ 4 4.2 Hardware Interfaces .................................................................................................................... 4 4.3 Software Interfaces...................................................................................................................... 4 4.4 Communications Interfaces .......................................................................................................... 4 5. Other Nonfunctional Requirements.................................................................................... 5 5.1 Performance Requirements .......................................................................................................... 5 5.2 Safety Requirements .................................................................................................................... 5 5.3 Security Requirements ................................................................................................................. 5 5.4 Software Quality Attributes ......................................................................................................... 5 6. Other Requirements ................................................................ Error! Bookmark not defined. Appendix A: Glossary ............................................................................................................... 5 Appendix B: Analysis Models ................................................................................................... 5 Appendix C: Issues List ............................................................................................................ 6 Revision History Name Date Reason For Changes Version Software Requirements Specification for <Project> Page 1 1. Introduction 1.1 Purpose The purpose of this document is to enumerate the requirements needed for building a computer version of the game Battleship. The document describes the requirements for all components of the Battleship game. The SRS document should directly lead to a feasible design for implementing the system. 1.2 Document Conventions <Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.> 1.3 Intended Audience and Reading Suggestions This document is intended for the developers, testers, and help documentation writers of the project Battleship. Section one and two should be read by all members of the intended audience. System designers should refer to sections three and four for a detailed description of the system’s functional requirements. 1.4 Project Scope <Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here. An SRS that specifies the next release of an evolving product should contain its own scope statement as a subset of the long-term strategic product vision.> 1.5 References <List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.> Software Requirements Specification for <Project> Page 2 2. Overall Description 2.1 Product Perspective <Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.> 2.2 Product Features <Summarize the major features the product contains or the significant functions that it performs or lets the user perform. Details will be provided in Section 3, so only a high level summary is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or a class diagram, is often effective.> 2.3 User Classes and Characteristics Battleship will have one primary user class, the player. Members of this user class may be from ages seven to adult and will have basic computer literacy skills (including use of a keyboard and mouse). There are no strict educational requirements for this user class outside of a basic understanding of two dimensional coordinate systems. 2.4 Operating Environment <Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.> 2.5 Design and Implementation Constraints <Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).> 2.6 User Documentation User help files will be available from the game itself. The help files will explain the rules of the game as well as the layout of the user controls. Software Requirements Specification for <Project> Page 3 2.7 Assumptions and Dependencies <List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).> 3. System Features <This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.> 3.1 System Feature 1 <Don’t real y say “System Feature 1.” State the feature name in just a few words.> 3.1.1 Description and Priority <Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).> 3.1.2 Stimulus/Response Sequences <List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.> 2.1.3 Functional Requirements <Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.> <Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.> REQ-1: REQ-2: Software Requirements Specification for <Project> Page 4 3.2 System Feature 2 (and so on) 4. External Interface Requirements 4.1 User Interfaces <Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.> 4.2 Hardware Interfaces <Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.> 4.3 Software Interfaces <Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.> 4.4 Communications Interfaces <Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.> Software Requirements Specification for <Project> Page 5 5. Other Nonfunctional Requirements 5.1 Performance Requirements 5.1.1 Game Board Update Within one second of firing a torpedo, a player’s offensive board and his opponent’s defensive board should be updated with the status of the shot (hit or miss) according to functional requirement 3.6.3. 5.1.2 After a multiplayer game is started, the matchmaking server shall update its open game list within 5 seconds. 5.2 Security Requirements During a network game, only information concerning the coordinates of fired shots shall be sent over the network. The system shall not have the ability to execute arbitrary commands based on data received via the network. Potential security risks are eliminated by ensuring that the system itself will not allow for information received over the network to alter any part of the remote system except for the game itself. 5.3 Software Quality Attributes 5.3.1 Portability Portability is an important factor for Battleship so that the game may be played independent of a particular platform. The system should support a network game between two players running the game on his own distinct platform. 5.3.2 Usability Usability is equally important since the software exists solely for entertainment purposes. A player with basic computer literacy (i.e. keyboarding and mouse skills) should quickly master the game play controls. Appendix A: Glossary Hit A hit occurs when the coordinates of a fired torpedo coincide with any of the coordinates occupied by an enemy ship. Software Requirements Specification for <Project> Page 6 Miss Any fired torpedo that is not a hit is a miss. Ship Position The set of coordinates occupied by a ship. Sink A ship is sunk when all of the coordinates of the ship’s position have been hit. Offensive Board A player’s view of the enemy’s defensive board, including the hits and misses recorded. Defensive Board A grid showing the position of the player’s ships. Appendix B: Analysis Models <Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.> Appendix C: Issues List < This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Download
Srs template

 

 

Your download will begin in a moment.
If it doesn't, click here to try again.

Share Srs template to:

Insert your wordpress URL:

example:

http://myblog.wordpress.com/
or
http://myblog.com/

Share Srs template as:

From:

To:

Share Srs template.

Enter two words as shown below. If you cannot read the words, click the refresh icon.

loading

Share Srs template as:

Copy html code above and paste to your web page.

loading