Service Life Cycle Management

Project requirements for <X> project

Note: This is a very detailed requirements template, with many sections that may be unnecessary for a given project. Because this is a template, you should feel free to adapt it to the needs of your project. A stract: [Provide a very brief summary of the documents contents.]

Contents <After you make changes to the document, right-click in the table of contents and select Update Field.> Project requirements for <X project..................................................................................! "ontents...............................................................................................................................! #ersion notice......................................................................................................................! Trademar$s..........................................................................................................................% &ecurity chec$list.................................................................................................................% !. 'ntroduction......................................................................................................................( %. )eneral information.........................................................................................................* (. Processing flows..............................................................................................................* *. &ystem architecture..........................................................................................................* +. ,etailed requirements......................................................................................................+ -. &ystem 'nterfaces.'mpacts.............................................................................................../. )lobal requirements........................................................................................................./ 0. Testing considerations.....................................................................................................1 1. &ummary .........................................................................................................................1 !ersion notice 2ll revisions of this document are listed in chronological order. There is no relationship between the document number and the software release number.
Document release Date Description Software release

raft ! raft ( )elease !

mm"dd"yyyy mm"dd"yyyy mm"dd"yyyy

[#his information is o$tional. %f you &ish to do so, give a brief descri$tion of this and subse'uent drafts.] *irst release.

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management #his document &as created by <&riters organi+ation> &ithin ,-.PA/0 /A.1. ,-.PA/0 has made every effort to ensure that this document is accurate at the time of $rinting. -btain additional co$ies of this document, as &ell as u$dated releases, from the follo&ing organi+ation2 <Provide contact information for the document.> "ra#emar$s The trademar$s contained in this document are the property of their respective owners. Security c%ec$list 'f the answer to any of the following questions is 3yes3, then the 'T &ecurity 4ffice should review additional details of the proposed implementation. 5ill sensitive data be stored on, or transmitted through, the system 6for e7ample, &ocial &ecurity 8umbers, employee or student records, health information9: ,oes the application require authentication: 5ill the vendor be providing and maintaining the hardware or software: 5ould abuse or compromise of the system potentially damage the university;s image or brand, or adversely affect public relations:

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management

&' (ntro#uction <Purpose: &ystem requirements are developed to capture client needs and to provide a benchmar$ to which designs will be validated. Purpose)Scope [3riefly e4$lain the $ur$ose and goal of the $ro5ect. 6ummari+e the $roblem clients e4$erience &ith the $resent system, if one e4ists, or the need clients have for a system solution. %dentify goals that &ould be achieved &ith the $ro$osed system and the assum$tions and de$endencies that these statements are based on. efine the sco$e of this system re'uirements document. 7hat releases does it include8 7hat does it e4clude8] Summary of c%anges <%nclude a summary of changes that have been made to the system re'uirements document. 6$ecify &here these changes have been made and ho& they are identified &ithin the document.> "arget au#ience < escribe &ho needs to understand and use this re'uirement document. 7ho is im$acted by it8> *evie+)Concurrence information <Provide a list of team members and stakeholders &ho are res$onsible for revie&ing the re'uirement document.> Structure an# use < escribe the document structure and numbering system.> "racea ility < escribe the method by &hich re'uirements &ill be tracked during design.> ,isclaimer < escribe any limitations of the information included in the document.>

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management -' .eneral information C%allenge)/pportunity <%nclude a brief statement that describes the $otential obstacles that may be encountered &ith your a$$lication"system. efine areas &here o$$ortunities e4ist.> 0eature)Project #escription <Provide s$ecific background information, ma5or functions, and related functions of the a$$lication"system. escribe associations to other systems business use. 9ist the clients that are associated &ith your a$$lication"system. Also list any clients that could be affected if any changes are made to your a$$lication"system, e.g., .ass .arket .ega ,enters, P.- 6ites, etc. Provide a list of end users to your a$$lication"system. Also $rovide a list of end users that could be affected if any changes are made to your a$$lication"system.> 1enefit)!alue < escribe the added benefits and"or value that your a$$lication"system $rovides.> Assumptions2 ,epen#encies2 Constraints < escribe any assum$tions being made &ith regard to your a$$lication"system, e.g., you are $lanning a (:; gro&th across the board on all a$$lications on your system. 9ist any constraints that may kee$ your re'uest from being com$leted, e.g., your system cannot be taken do&n at any time during the month of .arch due to heavy traffic load. 9ist any de$endencies your a$$lication"system may have, e.g., does your a$$lication rely on another a$$lication or system8> Security ris$ assessment <Provide an evaluation of the security risks associated &ith your a$$lication"system.> 3' Processing flo+s < escribe the current method of o$eration if one e4ists and the desired method of o$eration.> 4' System arc%itecture 5ar#+are requirements

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management < escribe the hard&are re'uirements for your system"a$$lication. %f the re'uirements are different before and after the change re'uest, list them se$arately. 7hat tools"soft&are &ere used in develo$ment8> Soft+are requirements < escribe the soft&are re'uirements for your system"a$$lication. %f the re'uirements are different before and after the change re'uest, list them se$arately. 7hat tools"soft&are &ere used in develo$ment8> 6' ,etaile# requirements Common requirements < escribe re'uirements that must be carried through all $ro5ects containing the functionality being described.> ,ata mo#eling requirements <Provide any data models available for your system"a$$lication.> 0unctional requirements < escribe the functional re'uirements. %f the re'uirements are different before and after the change re'uest, list them se$arately.> Client 78ser9 interface requirements < escribe the client <user= interface re'uirements. %f the re'uirements are different before and after the change re'uest, list them se$arately. #hings to consider include2 All documentation <$a$er and"or online= needed by clients of this a$$lication )e$orts that the $ro$osed a$$lication must generate, including general information content )e'uirements for screen color, si+e, resolution, mouse 9ogon and logoff re'uirements )e'uirements for automatic $o$ulation of fields 1rror handling re'uirements

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management )e'uirements for on-line reference material 7hether $rinters are local or remote #y$ical or re'uired number of $rintouts $er user $er a standard time interval Print 'uality re'uirements.>

,ata ase requirements < escribe the database re'uirements of your system"a$$lication. %f the re'uirements are different before and after the change re'uest, list them se$arately.> 1uil#ing loc$ requirements <A building block re'uirement is a re'uirement that is derived from a change that is being made to the core a$$lication of a $roduct or system. #he change to the >core? re'uires that changes be made to its surrounding subsystems. escribe the building block re'uirements in this section. %f the re'uirements are different before and after the change re'uest, list them se$arately.> Contract requirements <,ontract re'uirements are re'uirements that enforce an agreement bet&een $roducts or a$$lications to maintain the integrity of the interface re'uirements bet&een the $roducts of a$$lications. An e4am$le of a contract re'uirement is a file format for data e4change bet&een t&o a$$lications. escribe the contract re'uirements in this section. %f the re'uirements are different before and after the change re'uest, list them se$arately.> ,ata communications requirements < escribe the data communications re'uirements of your system"a$$lication. %f the re'uirements are different before and after the change re'uest, list them se$arately.> /t%er < escribe other re'uirements, not s$ecifically listed above, that e4ist.> :' System (nterfaces)(mpacts Project interfaces < escribe your current system interface re'uirements. %f the interface re'uirements are different before and after the change re'uest, list them se$arately. #hese should include $ro5ect interfaces, conversion, and de$endencies"transition.>

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management ;' .lo al requirements Availa ility)*elia ility requirements <#hings to consider include 2 -n-line availability re'uirements, including2 Acce$table blockage Acce$table delays o&ntime allo&ance for functions or com$onents 3acku$ and recovery re'uirements, including2 %nformation that must be backed u$ uration of storage #ime limitations 9ocal or remote Amount of automation )es$onsibility isaster recovery A$$lication availability.>

Performance requirements < escribe the $erformance $arameters for your system"a$$lication, e.g., 7hat do your end users e4$ect from your system"a$$lication, e.g., 7hat do your end users e4$ect from your system"a$$lication8 7hat are acce$table res$onse times8 #hings to consider include2 )es$onse time $arameters. <#hese should be measurable. @ive thought to ho& these &ould be tested.= #hrough$ut re'uirements in terms of number of transactions or amount of data to be $rocessing in a give time $eriod <e.g., daily= /umber of simultaneous users the system must su$$ort

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management /umber of simultaneous transactions the system must su$$ort /umber of terminals the ne& a$$lication must su$$ort /umber of files and records 6i+e of tables and files *re'uency, volumes, and mode <e.g., batch vs. on-line= of e4ternal interface communications 6i+ing, scaling needs to meet $lanned gro&th -ther kno&n constraints the system must adhere to <e.g., e4isting $olicies, standards, hard&are, or interfaces=.>

Security requirements <,onsider a$$lication security re'uirements, including $ass&ord $rotection, restricted communications bet&een areas of a $rogram, etc., as &ell as control and audit trail re'uirements.> <nvironmental constraints < escribe the environmental constraints of the system"a$$lication.> Client or site=specific requirements < escribe any client or site-s$ecific re'uirements. #his re'uirement is ty$ically included in the contract.> System a#ministration requirements < escribe the system administration re'uirements.> (nformation #evelopment requirements < escribe any s$ecific training desired for the system"a$$lication team &ith res$ect to this change re'uest. escribe any training desired for the clients of your system"a$$lication in reference to this change re'uest.> 8sa ility requirements < escribe any s$ecific usability re'uirements for the system"a$$lication.>

Rev. 2/20/2014

212397019.doc

Service Life Cycle Management >' "esting consi#erations < escribe the conditions that affect testing.> ?' Summary <Provide a brief summary of the system re'uirements s$ecified in this document.> /pen issues < escribe any outstanding issues that still e4ist &ith res$ect to the effective im$lementation of your system"a$$lication.> Ac$no+le#gements <0ou may list any entities that $rovide su$$ort on this $ro5ect.> *eferences <%nclude a list of documents that &ere referenced in this re'uirement $lan.> .lossary <%nclude a list of terms or acronyms that are s$ecific to this $ro5ect.> Attac%ments <%nclude additional details such as checklists or tables.>

Rev. 2/20/2014

212397019.doc