Documentos de Académico
Documentos de Profesional
Documentos de Cultura
0)
To use this template: 1. Replace any red italicized text with your own text. You may remove or add sections as needed for your particular projects. 2. Enter the project name in the title and footer and chan!e the document version num"er# if necessary$. %. &f your document is very lon!# "rea' each num"ered chapter into its own document section# "e!innin! it on a new pa!e. This will ma'e it easier to replace(upda!te ). *elete these instructions and any other italicized instructions. Project: Date(s): Prepared by: Document status: __ Draft __ Proposed __ Va idated __ !pproved
1. Introduction
"#is document contains t#e system requirements for project name. "#ese requirements #ave been derived from severa sources$ inc udin% brief listing of most important sources.
!eader('pecific 'ections &n this section# name any parts of the document which are intended only for one or another of the reader types identified a"ove# and which may therefore "e s'ipped "y other readers. 'ection &rder Dependencies &f readers will need to read certain sections in a specific order# note those sections here. /lso point out any sections that may "e read independently with no loss of understandin!.
2. -eneral Description
"#is section 'i %ive t#e reader an overvie' of t#e project$ inc udin% '#y it 'as conceived$ '#at it 'i do '#en comp ete$ and t#e types of peop e 'e e,pect 'i use it. 0e a so ist constraints t#at 'ere faced durin% deve opment and assumptions 'e made about #o' 'e 'ou d proceed. This section contains a nontechnical description of the project# usually in narrative form# which may serve to ac.uaint new readers with the purpose of the project. &t also sets the sta!e for the specific re.uirement listin! which follows.
&n this section# list any assumptions you made a"out your project for example# did you assume that the finished product would need to "e delivered over the internet2$. &f your project depends on any particular technical infrastructure# or re.uires administrators or others with specific s'ills# note that here.
). 'pecific !e%uirements
"#is section of t#e document ists specific requirements for name of project. Requirements are divided into t#e fo o'in% sections: 1. 2ser requirements. "#ese are requirements 'ritten from t#e point of vie' of end users$ usua y e,pressed in narrative form. ). 3ystem requirements. "#ese are detai ed specifications describin% t#e functions t#e system must be capab e of doin%. -. &nterface requirements. "#ese are requirements about t#e user interface$ '#ic# may be e,pressed as a ist$ as a narrative$ or as ima%es of screen moc+*ups.
*. Appendices
&f you wish to append any documents# do so here. You may wish to include some or all of the followin!: 5ersonas and scenarios developed for this project Transcripts of user interviews# o"servations# or focus !roups 6opies of communications which contain user re.uirements 7ri!inal project proposals or other historical documents -ists of similar projects or products# with notes a"out how they differ from yours / list of re.uirements which were 8wish,listed8 or mar'ed unfeasi"le at present 7ri!inal screen moc'ups# if they are relevant
,. -lossar
&nclude a !lossary of definitions# acronyms# and a""reviations that mi!ht "e unfamiliar to some readers# especially technical terms that may not "e understood "y end,users or domain,specific terms that mi!ht not "e familiar to developers.
/. !eferences
-ist references and source documents# if any# in this section.
0. Inde1
&f your document is very lar!e# consider compilin! an index to help readers find specific items.