ࡱ> cebq  6bjbjt+t+ MbAA1b] $Z Z Z Z P 4 LZ *V zj::::jY*[*[*[*[*[*[*$z,n.* ::  *` ::V ``` J : :Y* J J Y*``VN% M* :* ,hh`Z Z j*0 SUBJECT \* MERGEFORMAT   TITLE \* MERGEFORMAT Software Requirements Specification For Version <1.0> [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).] [To customize automatic fields (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.] [Note: The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system. Following is a typical SRS outline for a project using only traditional natural-language style requirements with no use-case modeling. It captures all requirements in a single document, with applicable sections inserted from the Supplementary Specifications (which would no longer be needed). For a template of an SRS using use-case modeling, which consists of a package containing use cases of the use-case model and applicable Supplementary Specifications and other supporting information, see rup_srs-uc.dot.] Many different arrangements of an SRS are possible. Refer to [IEEE93] for further elaboration of these explanations, as well as other options for SRS organization.] Revision History DateVersionDescriptionAuthor

 Table of Contents  TOC \o "1-3" 1. Introduction  PAGEREF _Toc456598586 \h 4 1.1 Purpose  PAGEREF _Toc456598587 \h 4 1.2 Scope  PAGEREF _Toc456598588 \h 4 1.3 Definitions, Acronyms and Abbreviations  PAGEREF _Toc456598589 \h 4 1.4 References  PAGEREF _Toc456598590 \h 4 1.5 Overview  PAGEREF _Toc456598591 \h 4 2. Overall Description  PAGEREF _Toc456598592 \h 4 3. Specific Requirements  PAGEREF _Toc456598593 \h 4 3.1 Functionality  PAGEREF _Toc456598594 \h 5 3.1.1  PAGEREF _Toc456598595 \h 5 3.2 Usability  PAGEREF _Toc456598596 \h 5 3.2.1  PAGEREF _Toc456598597 \h 5 3.3 Reliability  PAGEREF _Toc456598598 \h 5 3.3.1  PAGEREF _Toc456598599 \h 5 3.4 Performance  PAGEREF _Toc456598600 \h 6 3.4.1  PAGEREF _Toc456598601 \h 6 3.5 Supportability  PAGEREF _Toc456598602 \h 6 3.5.1  PAGEREF _Toc456598603 \h 6 3.6 Design Constraints  PAGEREF _Toc456598604 \h 6 3.6.1  PAGEREF _Toc456598605 \h 6 3.7 Online User Documentation and Help System Requirements  PAGEREF _Toc456598606 \h 6 3.8 Purchased Components  PAGEREF _Toc456598607 \h 6 3.9 Interfaces  PAGEREF _Toc456598608 \h 6 3.9.1 User Interfaces  PAGEREF _Toc456598609 \h 6 3.9.2 Hardware Interfaces  PAGEREF _Toc456598610 \h 6 3.9.3 Software Interfaces  PAGEREF _Toc456598611 \h 7 3.9.4 Communications Interfaces  PAGEREF _Toc456598612 \h 7 3.10 Licensing Requirements  PAGEREF _Toc456598613 \h 7 3.11 Legal, Copyright and Other Notices  PAGEREF _Toc456598614 \h 7 3.12 Applicable Standards  PAGEREF _Toc456598615 \h 7 4. Supporting Information  PAGEREF _Toc456598616 \h 7   TITLE \* MERGEFORMAT Software Requirements Specification Introduction [The introduction of the SRS should provide an overview of the entire SRS. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of the SRS.] Purpose [Specify the purpose of this SRS. The SRS should fully describe the external behavior of the application or subsystem identified. It also describes nonfunctional requirements, design constraints and other factors necessary to provide a complete and comprehensive description of the requirements for the software.] Scope [A brief description of the software application that the SRS applies to; the feature or other subsystem grouping; what Use Case model(s) it is associated with, and anything else that is affected or influenced by this document.] Definitions, Acronyms and Abbreviations [This subsection should provide the definitions of all terms, acronyms, and abbreviations required to interpret properly the SRS. This information may be provided by reference to the project Glossary.] References [This subsection should provide a complete list of all documents referenced elsewhere in the SRS. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.] Overview [This subsection should describe what the rest of the SRS contains and explain how the SRS is organized.] Overall Description [This section of the SRS should describe the general factors that affect the product and its requirements. This section does not state specific requirements. Instead, it provides a background for those requirements, which are defined in detail in section 3, and makes them easier to understand. Include such items as: product perspective, product functions, user characteristics, constraints, assumptions and dependencies, and requirements subsets.] Specific Requirements [This section of the SRS should contain all the software requirements to a level of detail sufficient to enable designers to design a system to satisfy those requirements, and testers to test that the system satisfies those requirements. When using use-case modeling, these requirements are captured in the use cases and the applicable supplementary specifications. If use-case modeling is not used, the outline for supplementary specifications may be inserted directly into this section, as shown below.] Functionality [This section describes the functional requirements of the system for those requirements which are expressed in the natural language style. For many applications, this may constitute the bulk of the SRS Package and thought should be given to the organization of this section. This section is typically organized by feature, but alternative organization methods, for example organization by user, or organization by subsystem may also be appropriate. Functional requirements may include: feature sets, capabilities and security. Where application development tools (requirements tools, modeling tools, etc) are employed to capture the functionality, this section document will refer to the availability of that data and indicate the location and name of the tool which is used to capture the data.] [The requirement description.] Usability [This section should include all of those requirements that affect usability. Examples: Specify the required training time for a normal users and power users to become productive at particular operations. Specify measurable task times for typical tasks, or Base usability requirements of the new system on other systems that the users know and like. Specify requirements to conform to common usability standards e.g., IBMs CUA standards, or the GUI standards published by Microsoft for Windows 95.] The requirement description. Reliability [Requirements for reliability of the system should be specified here. Suggestions: Availability specify % of time available ( xx.xx%), hours of use, maintenance access, degraded mode operations etc. Mean Time Between Failures (MTBF) this is usually specified in hours, but it could also be specified in terms of days, months, or years. Mean Time To Repair (MTTR) how long is the system allowed to be out of operation after it has failed?. Accuracy specify precision (resolution) and accuracy (by some known standard) that is required in the systems output. Maximum bugs or defect rate usually expressed in terms of bugs/KLOC (thousands of lines of code), or bugs per function-point. Bugs or defect rate categorized in terms of minor, significant, and critical bugs: the requirement(s) must define what is meant by a critical bug (e.g., complete loss of data, complete inability to use certain parts of the functionality of the system).] [The requirement description.] Performance [The performance characteristics of the system should be outlined in this section. Include specific response times. Where applicable, reference related Use Cases by name. Response time for a transaction(average, maximum) Throughput (e.g., transactions per second) Capacity (e.g., the number of customers or transactions the system can accommodate) Degradation modes (what is the acceptable mode of operation when the system has been degraded in some manner) Resource utilization: memory, disk, communications, etc.] [The requirement description.] Supportability [This section indicates any requirements that will enhance the supportability or maintainability of the system being built, including coding standards, naming conventions, class libraries, maintenance access, maintenance utilities.] [The requirement description.] Design Constraints [This section should indicate any design constraints on the system being built. Design constraints represent design decisions that have been mandated and must be adhered to. Examples include software languages, software process requirements, prescribed use of developmental tools, architectural and design constraints, purchased components, class libraries, etc.] [The requirement description.] Online User Documentation and Help System Requirements [Describes the requirements, if any, for on-line user documentation, help systems, help about notices, etc.] Purchased Components [This section describes any purchased components to be used with the system , any applicable licensing or usage restrictions, and any associated compatibility/interoperability or interface standards.] Interfaces [This section defines the interfaces that must be supported by the application. It should contain adequate specificity, protocols, ports and logical addresses, etc, so that the software can be developed and verified against the interface requirements.] User Interfaces [Describe the user interfaces that are to be implemented by the software.] Hardware Interfaces [This section defines any hardware interfaces that are to be supported by the software, including logical structure, physical addresses, expected behavior, etc. ] Software Interfaces [This section describes software interfaces to other components of the software system. These may be purchased components, components reused from another application, or components being developed for subsystems outside of the scope of this SRS, but with which this software application must interact.] Communications Interfaces [Describe any communications interfaces to other systems or devices such as local area networks, remote serial devices, etc.] Licensing Requirements [Defines any licensing enforcement requirements or other usage restriction requirements which are to be exhibited by the software.] Legal, Copyright and Other Notices [This section describes any necessary legal disclaimers, warranties, copyright notices, patent notice, wordmark, trademark, or logo compliance issues for the software.] Applicable Standards [This section describes by reference any applicable standards, (and the specific sections of any such standards which apply to the system being described). For example, this could include legal, quality and regulatory standards, industry standards for usability, interoperability, internationalization, operating system compliance, etc.] Supporting Information [The supporting information makes the SRS easier to use. It includes: a) Table of contents, b) Index, c) Appendices. These may include use-case storyboards or user-interface prototypes. When appendices are included, the SRS should explicitly state whether or not the appendices are to be considered part of the requirements.]  DOCPROPERTY "Company" \* MERGEFORMAT  PAGE   SUBJECT \* MERGEFORMAT  Version: <1.0> TITLE \* MERGEFORMAT Software Requirements Specification Date:
 Confidential( DOCPROPERTY "Company" \* MERGEFORMAT , 1999Page  PAGE 2 )*+,CDghM a       " # = > ? @ A B E F N O i j k l m n q r x y       jUmHjwUmHjUmHj}UmHjUmH jUmHCJmHmH5CJ jUG+iL $C$$l\ $  $$.$$+iL  B n  @ w %S 9}.l/eUR_#].7  7.   . .L C$$l\ $  $  B n  @ w %S 9}.l/e @     ! ; < = > ? @ B C W X r s t u v w y z  !"#$%()34NOPQRSXYuvj_UmHjUmHjeUmHjUmHjkUmHjUmHjqUmH jUmHCJmHmHC   456789>?]^xyz{|})jMUmHjUmHjSUmHjUmHjYUmHjUmHCJmH jUmHmHD)*+,-.34LMghijklop*+,-./45EF`abcdejkj UmHj; UmHj UmHjA UmHj UmHjG UmHCJmHmH jUmHjUmHC56PQRSTUYZ}~  +,OP55CJ jUjUmHj)UmHj UmHj/ UmHj UmHCJmHj5 UmH jUmHmHCUR_#]cHp;F!5v. & F/.   @]cHp;F!5v!2@ ] Ƹwme`TOJ>  ..  .  .9/  .\/  .j/  ./  ./   ./ .  .   .   .    .   !2@ ] | T!!!}""""##$$$x%z&& . & F8 h80 . & F8 h80.] | T!!!}""""##$$$x%z&&&&n''÷zpfZUGB; .I .H   H.<  <.>  .  .6  .  .*   . .I   I.  .  .  .(   . .   .&&&n'''(((()))*<*O*+++*,,,u--}....0 . & F8 h8.''(((()))*<*O*+++*,,,u--}..ǹql^YKF:  .   .h   h.    .  .   .  .   .  .*  .  .  .  ...//00j112(22284O45555 6&6'6e6z6{6666666666ǹ}}}{ .  ..  ..  .  .      .   .!.//00j112(22284O45555555555 6$h&`#$$&d$d0.55555555555555555 6 6'6(6?6@6c6d6666666666666660JmH j jU0J j0JUCJ5CJ$OJQJj5CJ$OJQJU& 6&6'6e6z6{66666666P\$$$$h$"$$l$V%$-$$l0$k D($ o 6666666666.8$$lF H$Z Z Z &00&P/ =!"#$%#0:&P/ =!"#$%}DyK _Toc456598586}DyK _Toc456598587}DyK _Toc456598588}DyK _Toc456598589}DyK _Toc456598590}DyK _Toc456598591}DyK _Toc456598592}DyK _Toc456598593}DyK _Toc456598594}DyK _Toc456598595}DyK _Toc456598596}DyK _Toc456598597}DyK _Toc456598598}DyK _Toc456598599}DyK _Toc456598600}DyK _Toc456598601}DyK _Toc456598602}DyK _Toc456598603}DyK _Toc456598604}DyK _Toc456598605}DyK _Toc456598606}DyK _Toc456598607}DyK _Toc456598608}DyK _Toc456598609}DyK _Toc456598610}DyK _Toc456598611}DyK _Toc456598612}DyK _Toc456598613}DyK _Toc456598614}DyK _Toc456598615}DyK _Toc4565986162 [:@: Normal 1$d_HmH sH tH \@\ Heading 1'$ & F0x<@&^`05CJOJQJD@D Heading 2 & F@&^`CJJ@J Heading 3 & F@&^` 56CJ88 Heading 4  & F@&5CJDD Heading 5 & F@ <@&^@ CJHH Heading 6 & F@ <@&^@ 6CJ@@ Heading 7 & F@ <@&^@ DD Heading 8 & F@ <@&^@ 6J J Heading 9 & F@ <@&^@ 56CJ<A@< Default Paragraph FontHH Paragraph2$P^a$B*mH sH u:>@: Title$da$5CJ$OJQJHJH Subtitle $<a$6CJ$OJQJmH sH u>"> Normal Indent|^`|6@6 TOC 1 $<]6@6 TOC 2 $]^2@2 TOC 3 $`^`,@b, Header  !, @r, Footer  !&)@& Page Number Bullet1p & FP>T?^`P Bullet2p & F>Th?^`B* .O. Tabletext $x6B6 Body Text$x^8Y8 Document Map-D OJQJ<&@< Footnote ReferenceCJH*^^ Footnote Text&$$h((&d^h` CJOJQJPP Main Title $d<a$5CJ KHOJQJ88 Paragraph1!$dPa$@"@ Paragraph3"$dP^a$@2@ Paragraph4#$dP^a$&& TOC 4 $X^X&& TOC 5 % ^ && TOC 6 &^&& TOC 7 '^&& TOC 8 (x^x&& TOC 9 )@^@0P0 Body Text 2*6B*FCF Body Text Indent +^ 6>*B*@@ Body,$dx1$a$OJQJtH uZZ Bullet4-$ & FQ hdx1$]h^a$OJQJ6O6 InfoBlue.x^6B*(U@( Hyperlink>*B*>V@> FollowedHyperlink >*B* ph"W@" Strong5\2b(b       "V+2? 9>IIIII]_ad )56"#$%. &. 666 !&(*-/0]] '.6')+,)+Cg">@Njlx  < > W s u  ! # 3 O Q u    5 7 ] y {  * , L h j  + - E a c  5QS} +O2 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%*9>EIcr 3BOVXdU!U! _Toc456598586 _Toc456598587 _Toc456598588 _Toc456598589 _Toc456598590 _Toc456598591 _Toc456598592 _Toc456598593 _Toc456598594 _Toc456598595 _Toc456598596 _Toc456598597 _Toc456598598 _Toc456598599 _Toc456598600 _Toc456598601 _Toc456598602 _Toc456598603 _Toc456598604 _Toc456598605 _Toc456598606 _Toc456598607 _Toc456598608 _Toc456598609 _Toc456598610 _Toc456598611 _Toc456598612 _Toc456598613 _Toc456598614 _Toc456598615 _Toc456598616R]H;!@|}z""$%%<&''(u)}**+,j-..802 ^"boE4 \""$%&N&')(()**+,-'..N02*+h2:"ANmx ? W v  $ 3 R u   8 ] |  - L k  . E d  5T}PCH..11111 2'2d2o2x2222222*+h"ANmx ? W v  $ 3 R u   8 ] |  - L k  . E d  5T}P11111 2'2d2222222Leslee Probasco!C:\RUP Temp\templates\req\srs.dot Ranjan Sinha8D:\lin_SE\Software Requirements\Templates\Template_4.dot SG" p  m :D" NcK- E,1 Q+2 Hu3}tqT6 {B pI +sdO NsR f4F}/m *q 6t Pau 4{ @.@ .@..@...@ ....@ .....@ ......@ .......@ ........* hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(h ^`OJQJo(h pp^p`OJQJo(oh @ @ ^@ `OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h PP^P`OJQJo(oh   ^ `OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(/Hu34{NsR+sdOfSG"Paup qT6Q+26tE,1m*qpI:D"{B(gNcK-F}/mg 0pIg0:D"g0{Bg0ff @h ^`OJQJo(4g @h 8^8`OJQJo( @ :2@@GTimes New Roman5Symbol3& Arial?5 Courier New5& :Tahoma;"HelveticaABook Antiqua;Wingdings"htRftRf,(WJZ!0d62O0#Software Requirements Specification<Project Name>Leslee Probasco Ranjan Sinha Oh+'0$ <H d p | $Software Requirements SpecificationeLeslee Probascoesleslrup_srs Ranjan Sinhaco2njMicrosoft Word 8.0t@@@4Q`@4Q`,( ՜.+,D՜.+,l( px  W621 $Software Requirements Specification Title 6> _PID_GUIDAN{C2257F3B-02AE-11D5-85E2-444553540000}  !"#$%&'()*+,-./013456789;<=>?@ABCDEFGHIJKLMNOPQSTUVWXY[\]^_`adRoot EntrylEmE0E``_ F[`hh`fEData$  21TableEEE0EE:0/WordDocumentE<@\ERLLLLMwMb<@SummaryInformation(+00#D:\ 1RklDocumentSummaryInformation 8in_SELIN_SE-1M**KSoftware ZentsCompObjE F:i+00#D:\ 1ELIN_SE-1M**jSOFObjectPooli+00#D:\ 1hh`hh`entsSOFTWA~  FMicrosoft Word Document MSWordDocWord.Document.89q