Reference no: EM132576679

Prepare Software Requirements Specification

FACEBOOK FOR ANDROID

Software Requirements Specification

1. Introduction
[The introduction of the SRS should provide an overview of the entire SRS. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of the SRS.]
1.1 Purpose
[Specify the purpose of this SRS. The SRS should fully describe the external behavior of the application or subsystem identified. It also describes nonfunctional requirements, design constraints and other factors necessary to provide a complete and comprehensive description of the requirements for the software.]
1.2 Scope
[A brief description of the software application that the SRS applies to; the feature or other subsystem grouping; what Use Case model(s) it is associated with, and anything else that is affected or influenced by this document.]
1.3 Definitions, Acronyms and Abbreviations
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to interpret properly the SRS. This information may be provided by reference to the project Glossary.]
1.4 References
[This subsection should provide a complete list of all documents referenced elsewhere in the SRS. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
1.5 Overview
[This subsection should describe what the rest of the SRS contains and explain how the SRS is organized.]

2. Overall Description
[This section of the SRS should describe the general factors that affect the product and its requirements. This section does not state specific requirements. Instead, it provides a background for those requirements, which are defined in detail in section 3, and makes them easier to understand. Include such items as product perspective, product functions, user characteristics, constraints, assumptions and dependencies, and requirements subsets.]
2.1 Use-Case Model Survey
[If using use-case modeling, this section contains an overview of the use-case model or the subset of the use-case model that is applicable for this subsystem or feature. This includes a list of names and brief descriptions of all use cases and actors, along with applicable diagrams and relationships. Refer to the use-case model survey report, which may be used as an enclosure at this point.]
2.2 Assumptions and Dependencies
[This section describes any key technical feasibility, subsystem or component availability, or other project related assumptions on which the viability of the software described by this SRS may be based.]

3. Specific Requirements
[This section of the SRS should contain all the software requirements to a level of detail sufficient to enable designers to design a system to satisfy those requirements, and testers to test that the system satisfies those requirements. When using use-case modeling, these requirements are captured in the use cases and the applicable supplementary specifications. If use-case modeling is not used, the outline for supplementary specifications may be inserted directly into this section.]
3.1 Use-Case Reports
[In use-case modeling, the use cases often define the majority of the functional requirements of the system, along with some non-functional requirements. For each use case in the above use-case model, or subset thereof, refer to or enclose the use-case report in this section. Make sure that each requirement is clearly labeled.]
3.2 Supplementary Requirements
[Supplementary Specifications capture requirements that are not included in the use cases. The specific requirements from the Supplementary Specifications which are applicable to this subsystem or feature should be included here, refined to the necessary level of detail to describe this subsystem or feature. These may be captured directly in this document or refer to separate Supplementary Specifications, which may be used as an enclosure at this point. Make sure that each requirement is clearly labeled.]

4. Supporting Information
[The supporting information makes the SRS easier to use. It includes: a) Table of contents, b) Index, c) Appendices. These may include use-case storyboards or user-interface prototypes. When appendices are included, the SRS should explicitly state whether or not the appendices are to be considered part of the requirements.]

REQUIREMENT ANAYSIS
(Please fill all the relevant fields, you can leave the field blank which is not applicable)

1. Course pursuing _____________________________________________________
2. Topic of the assignment - software requirement analysis project
3. Any particular case study / company / article / software to be taken yes they provide a list of example like uber, facebook, web browser etc..we have to choose one from that.
4. Any particular reading module or material required while doing the assignment already provided
5. Referencing style to be used not specify
6. Word limit not specify
7. Rubrics attached (Y/N) No
8. Number of minimum references to be used not specify
9. Format to be followed not specify
10. Other specifications or requirements use case diagrams are important

The purpose of this exercise is to get you accustomed to the various Use Case Diagrams and techniques. You may pick any software that you like, as long as you can show your excellence and command using features of that software. You don't have to document all the features of that software, but you must have one type of Use Case Diagram describing the feature.

Pick a subset of features; hopefully you can pick a subset that has something in common. Your requirement document must have at least 8 Textual Use Cases and a Use Case diagram that includes the Use Cases.

Attachment:- project-template.rar