Software Requirements

Netflix - SRS Document
Created by: App Avengers

04/01/2023
1. Introduction
This document defines and describe the requirements of the project to be built with React JS
(Python, Node. JS, Java, Kotlin, and Swift.)
Overview
The product is an internet entertainment services provider for watching movies and
television shows.
2. General Description
Product Functionality
The product has a internet subscription base model that offers TV shows & movies such
as original series, documentaries, & feature films on the TV, computer, & mobile
devices.
User Characteristics
The audience of Netflix is from diverse age groups and demographics, young, tech-savvy
users and anyone with digital connectivity.
User Problem Statement

Limited access to people
User Objectives
A service that allows one to order a movie online. A video technology, which will
revolutionized home-based video entertainment.
General Constraints
Limited users & Internet subscription
3. Functional Requirements
Items provided to the IDANRV shall be stored in the Access Database.

1. Items shall be stored on the laptop machine and have complete fields.
2. Very high criticality
3. Limited network / wi-fi availability could present a technical challenge
4. The above stated factor is a risk we have encountered. Eliminate it by reducing the
dependency of our program on these things.

5. This requirement is the basis of the project; all other aspects depend on it.
2. The items shall be accessible via queries and reports.

1. Users of the database should be able to run reports on the data that has been put into
the database. They should also be able to run queries.
3. We do not foresee any technical issues preventing the implementation of this.
4. Given the capabilities of Access, this requirement is able to be satisfied.
5. This requirement depends on requirement number one.
3. The data stored should be able to be manipulated through forms.

1. Items and other data should be able to be added and updated through the use of forms.
3. We do not foresee any technical risks involved in this requirement.
4. The only factor we can encounter here is the user of the system not being able to use
it correctly. We will overcome this by training those who will be using it.
5. This requirement is dependent on requirement one.
4. Interface Requirements
4.1 User Interfaces
 4.1.1 GUI
The user interface for this program is the interface provided by Microsoft Access 2007.
Access includes forms and reports for the users to query and organize data to suit their
needs. Forms and reports both have builders that let the user specify which fields they
want to use and which constraints they want to define.
 4.1.2 CLI
There is no command line interface
 4.1.3 API
There is no API for the product
Shock Force Software Team 1

 4.1.4 Diagnostics or ROM
There is a troubleshooting and help section provided by Microsoft
4.2 Hardware Interfaces

The program (Access) uses the hard disk. Access to the hard drive and other hardware is
managed by the operating system and Access.
4.3 Communications Interfaces
If we decide to implement an Ad Hoc network for a shared database, the operating system will
handle those connections.
4.4 Software Interfaces
The Access system may be used to import and export data with Microsoft Excel. This
functionality is built in to the user interface.
5. Performance Requirements
The database is designed to be operated through Microsoft Access 2007, thus no additional
system requirements exist beyond those required to run Microsoft Office 2007, except for a
negligible amount of hard drive space to store the database.
Microsoft lists the requirements for Access 2007 as follows:

500 MHz processor or higher
256MB RAM or higher
1.5GB Available Hard Drive Space
Windows XP SP2 or later operating system.
Windows Office Professional 2007 (Windows Access)
There is also Access Available for Mac OS X, the clients have not stated a need thus far.
6. Other non-functional attributes

.
6.1 Security
The system shall be designed with a level of security appropriate for the sensitivity of
information enclosed in the database. More interaction is needed with client about the volatility
of the information. Since there is no obvious information that is of a high security level such as
credit card information, the only requirements that could be implemented are encrypting the
database and/or making the database password-protected, by user’s request.
6.2 Binary Compatibility
This system will be compatible with any computer that has Microsoft Office Professional 2007
or later installed (whether PC or Mac), and will be designed with more than one computer in
mind.

6.3 Reliability
Reliability is one of the key attributes of the system. Back-ups will be made regularly so that
restoration with minimal data loss is possible in the event of unforeseen events. The system will
also be thoroughly tested by all team members to ensure reliability.
6.4 Maintainability
The system shall be maintained by Sheila Roop, of the IDA, or delegated to another employee.
6.5 Portability
The system shall be designed in a way that shall allow it to be run on multiple computers with
Microsoft Office Professional 2007 or later installed.
6.6 Extensibility
The system shall be designed and documented in such a way that anybody with an understanding
of Microsoft Access shall be able to extend the system to fit their needs with the team’s basic
instructions.
6.7 Reusability
The system should be designed in a way that allows the database to be re-used regularly for the
various silent auctions that the organization shall hold.
6.8 Application Affinity/Compatibility
This system requires the Microsoft Office Professional 2007 suite or later, as it operates
primarily through Microsoft Access, in conjunction with Microsoft Excel.
6.9 Resource Utilization
The resources used in the creation of this system include: Dr. Lewis, the client (Sheila Roop), the
computers in Davis Hall, and the internet.
6.10 Serviceability
The maintenance of the system should be able to be sufficiently performed by any person with a
basic understanding of Microsoft Access.
7. Operational Scenarios
Scenario A: Initial Item Definitions
The user shall enter the information about the items into the database for its initial
construction and evolution. The fields will be completed via a form that will manipulate the data.

Scenario B: Customer Check-out
The user shall be able to enter information about the customer purchasing a particular
item, and record their bid and other information. They will also enter the winning bid
Scenario C: Database Maintenance

The user may want to alter/delete information after the auction is over, In this case they
will need to be able to remove the data that has been entered.
8. Preliminary Use Case Models and Sequence Diagrams

This section presents a list of the fundamental sequence diagrams and use cases that satisfy the
system’s requirements. The purpose is to provide an alternative, "structural" view of the
requirements stated above and how they might be satisfied in the system.
8.1 Use Case Model

8.2 Sequence Diagrams

9. Updated Schedule
The updated PERT/GANTT chart is attached at the end of the document
10. Updated Budget

An updated budget is attached at the end of this document
11. Appendices
11.1 Definitions, Acronyms, Abbreviations
IDANRV- Intellectual Disabilities Agency of the New River Valley

Software Requirements

Uploaded by

Copyright:

Available Formats

Software Requirements

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements

Uploaded by

Copyright:

Available Formats

Netflix - SRS Document

Created by: App Avengers

User Problem Statement

Items provided to the IDANRV shall be stored in the Access Database.

2. Very high criticality

3. Limited network / wi-fi availability could present a technical challenge

dependency of our program on these things.

2. The items shall be accessible via queries and reports.

the database. They should also be able to run queries.

2. Very high criticality

3. We do not foresee any technical issues preventing the implementation of this.

4. Given the capabilities of Access, this requirement is able to be satisfied.

5. This requirement depends on requirement number one.

3. The data stored should be able to be manipulated through forms.

2. Very high criticality

3. We do not foresee any technical risks involved in this requirement.

5. This requirement is dependent on requirement one.

Shock Force Software Team 1

4.2 Hardware Interfaces

Microsoft lists the requirements for Access 2007 as follows:

6. Other non-functional attributes

6.2 Binary Compatibility

Shock Force Software Team 2

6.8 Application Affinity/Compatibility

6.9 Resource Utilization

Shock Force Software Team 3

Scenario C: Database Maintenance

8. Preliminary Use Case Models and Sequence Diagrams

Shock Force Software Team 4

Shock Force Software Team 6

10. Updated Budget

Shock Force Software Team 7

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.