This action might not be possible to undo. Are you sure you want to continue?
1 Purpose – mentions first and foremost the complete title of the proposed software; states the main objectives of the proponents in proposing the system. The benefits of the proposed system are also stated in general; mentions the problems that the proposed system will solve. 1.2 Scope- mentions, in general, the main features and functions of what the proposed software/system can do; no negatives. 1.3 Glossary - (Definitions, acronyms and abbreviations) – enumerates and defines each of the terms unique to the software/system being develop. It also includes those terms relevant to the understanding of the proposed system/software. 2. Overall Description 2.1 Product Functions – functions/features/menus offered by the proposed system; access to each function is also indicated; capabilities in detail; description of usability, reliability (error recovery, user input validation), help features, etc. 2.2 Analysis Model (UML, flowchart, class diagram, etc.) – shows features/functions of the product; includes narrative description of each diagram used. models the context, behavior, objects of the product. For WebApps: content, interaction, functional, configuration 2.4 Constraints – Limitations; extend of applicability; 3. Specific Requirements 3.1 External Interface Requirements 3.1.1 User Interfaces - mentions interaction style i.e., direct manipulation, menu selection, Form fill-in, command language, natural language; interface and aesthetic features, special features 3.1.2 Hardware Interfaces – design diagram, placement 3.1.3 Software Interfaces - screen shots, information presentations 3.2 Functional Requirements 3.2.1 User Class 1 126.96.36.199 Functional Requirement 1.1 – should match the product functions detailing it by mentioning specific facilities provided by the product; all services required by the user are stated here, its inputs, outputs, exceptions, etc.; searching and retrieving functionality, navigation and browsing features 188.8.131.52 Functional Requirement 1.2 – based on Functional requirement 1.1 but more detailed. 3.3 Performance (Nonfunctional) Requirements 3.3.1 Availability – access constraints, searching and retrieving constraints 3.3.2 Security – security constraints 3.3.3 Control – navigation and browsing constraints
etc.5 Software system attributes – installation and distribution schemes. restrictions imposed by the amount of scrolling that the user tolerate (page generation speed). licensing. 3.6 Other Requirements .4 Design constraints – maybe imposed by download speed (response time performance). 3.3.