# 1.1 Purpose (S_1)
- [ ] purpose of software (ps)

# 1.2 Scope (S_2)
- [ ] the software product's identifying (isp)
- [ ] what software product will provide (spd)
- [ ] benefit of the software product (spb)
- [ ] objectives of the software product (spo)
- [ ] goals of the software product (spg)

# 1.3.1 Product perspective (S_3)
- [ ] software system's relationship to other related products (srrp)
- [ ] software operation within the system interfaces (sosi)
- [ ] software operation within the user interfaces (soui)
- [ ] software operation within the hardware interfaces (sohi)
- [ ] software operation within the software interfaces (soswi)
- [ ] software operation within the communications interfacse (soci)
- [ ] software operation within the memory (som)
- [ ] software operation within the operations (soo)
- [ ] software operation within the site adaprion requirements (sosar)

# 1.3.2 Product functions (S_4)
- [ ] major future functions of the software (mf)

# 1.3.3 User characteristics (S_5)
- [ ] general characteristics of the software product's groups of users (gcigu)
- [ ] general characteristics which influence usability (gciu)

# 1.3.4 Limitations (S_6)
- [ ] regulatory policies (rp)
- [ ] limitations of hardware (hwl)
- [ ] interfaces to other applications (ioa)
- [ ] parallel operation (plo)
- [ ] audit functions (af)
- [ ] control functions (cf)
- [ ] requirements of higher-order language (holr)
- [ ] protocols of signal handshake (shp)
- [ ] quality requirements (quar)
- [ ] criticality of the application (ca)
- [ ] considerations of safety and security (ssc)
- [ ] physical/mental considerations (pmc)

# 1.4 Definitions (-)
- [ ] definitions for any words or phrases that have meaning beyond dictionaries (dbd)

# 2 References (-)
- [ ] list of referred documents (lrd)
- [ ] document title, report number, date and publishing organization (tndo)
- [ ] sources which the references can be obtained from (srof)

# 3.1 Functions (S_11)
- [ ] basic actions that must take place in the software when receiving and processing inputs (faapi)
- [ ] basic actions that must occur in the software when processing and generating outputs (fapgo)
- [ ] checks of validity on the inputs (vci)
- [ ] exact sequence of operations (eso)
- [ ] responses to abnormal situations (ras)
- [ ] parameters' effect (ep)
- [ ] relationship of inputs and outputs (rsoi)

# 3.2 Performance requirements (S_13)
- [ ] static numerical requirements (snr)
- [ ] dynamic numerical requirements (dnr)
- [ ] number of supported terminals (nts)
- [ ] number of supported simultaneous users (nssu)
- [ ] amount and type of handled information (athi)
- [ ] numbers of transactions (nota)
- [ ] number of tasks (not)
- [ ] amount of the processed data within certain time periods for normal workload conditions (adnw)
- [ ] amount of the processed data within certain time periods for peak workload conditions (adpw)
- [ ] requirements of performance (prq)

# 3.3 Usability requirements (S_12)
- [ ] usability requirements (ubr)
- [ ] measurable criteria of effectiveness in specific use contexts (mec)
- [ ] measurable criteria of efficiency in specific use contexts (mefc)
- [ ] measurable criteria of satisfaction in specific use contexts (msc)

# 3.5 Logical database requirements (S_14)
- [ ] types of used information (tiuvf)
- [ ] frequency of use (fqu)
- [ ] accessing the capabilities (asc)
- [ ] entities of data and their relationships (der)
- [ ] constraints of integrity (ics)
- [ ] requirements of data retention (drr)

# 3.6 Design constraints (S_15)
- [ ] the software system design's constraints which are imposed by external standards (ces)
- [ ] the software system design's constraints which are imposed by requlatory requirements (crr)
- [ ] the software system design's constraints which are imposed by project limitations (cpl)

# 3.7 Software system attributes (S_17)
- [ ] reliability (rb)
- [ ] availability (avb)
- [ ] security (scr)
- [ ] certain techniques of cryptographic (cct)
- [ ] data sets of specific log or history (slhd)
- [ ] certain functions to different modules (fdm)
- [ ] communications between some areas of the software product (csa)
- [ ] integrity of data for critical variables (dicv)
- [ ] privacy of data (dp)
- [ ] maintainability (mb)
- [ ] portability (pb)
- [ ] the percentage of elements with host-dependent code (pehdc)
- [ ] the percentage of hostdependent code (pchd)
- [ ] portable language use (uppl)
- [ ] particular compiler or language subset use (upcls)
- [ ] operating system use (upos)

# 3.8 Supporting information (S_19)
- [ ] sample input/output formats (siof)
- [ ] cost analysis studies' descriptions (dcas)
- [ ] user surveys' results (rus)
- [ ] supporting or background information that can help the readers of the SRS (sbi)
- [ ] description of the problems which will be solved by the software (dpss)
- [ ] special packaging instructions for the code and the media for security, export, initial loading (spi)

# 4 Verification (S_18)
- [ ] approaches for verification (va)
- [ ] methods for qualifying the software (mqs)

# 5.1 Assumptions and dependencies (S_7)
- [ ] factors which influence the requirements (far)

# 5.2 Acronyms and abbreviations (-)
- [ ] acronyms and abbreviations used in the documents (aa)