documentation - System Requirements Specification: User Requirements? -
i writing srs system , i'm having hard time trying figure out user requirements fit in. i'll give current contents:
table of contents revision history 1. document introduction 1.1 purpose 1.2 scope 1.3 word list 1.4 references 1.5 overview 2. system description 2.1 product description 2.2 project stakeholders 2.3 system characteristics 2.4 context diagram 2.4.1 frontend 2.4.2 backend 2.4.3 database 2.4.4 api 2.5 user requirements // <---- correct place , naming? 2.6 user assumptions , dependencies 2.7 user documentation 3. user requirements // <---- or more appropriate? 4. functional requirements 4.1 frontend 4.1.1 stop 4.1.2 quicklist 4.1.3 journey 4.1.4 settings 4.1.5 system 4.2.6 json 4.2 backend 4.2.1 json 4.2.2 system 5. other non-functional requirements 5.1 software interface 5.2 performance requirements 5.3 security requirements 5.4 software quality attributes 5.5 platform requirements
the user requirements accomodate things such (this example):
the user needs application responsive @ times. user must not confused button , not. user must able save personal preferences within area of application. user must able use application offline. user must able retain personal preferences if log in on device.
if not correct place put them should put them, if there else looks wrong srs say, i'm looking improve skills!
i keep user requirements have them listed @ 2.5 because flow of information follows user dependencies/assumptions. however, if information large enough require own section make more sense. without knowing each section represents it's hard answer question. ordinarily assume users needs defined within scope , purpose of project instead of needing section down further explaining user requires, or "why" of project.
Comments
Post a Comment