Software Requirements Specification | Research Paper Help



  1. Introduction. 3

1.1      Purpose. 3

1.2      Document Conventions. 3

1.3      Intended Audience and Reading Suggestions. 3

1.4      Product Scope. 3

1.5      References. 3

  1. Overall Description. 4

2.1      Product Perspective. 4

2.2      Product Functions. 4

2.3      User Types and Characteristics. 4

2.4      Operating Environment 4

2.5      Design and Implementation Constraints. 4

2.6      User Documentation. 5

2.7      Assumptions and Dependencies. 5

  1. External Interface Requirements. 6

3.1      User Interfaces. 6

3.2      Hardware Interfaces. 6

3.3      Software Interfaces. 6

3.4      Communication Interfaces. 6

  1. System Features. 7

4.1      System Feature 1. 7

4.2      System Feature 2 (and so on) 7

  1. Other Nonfunctional Requirements. 8

5.1      Performance Requirements. 8

5.2      Safety Requirements. 8

5.3      Security Requirements. 8

5.4      Software Quality Attributes. 8

5.5      Business Rules. 8

  1. Other Requirements. 9

Appendix A: Glossary. 10

Appendix B: Analysis Models. 11



1.    Introduction

1.1    Purpose

The goal of this document is to provide a detailed overview of the Alfred System’s prerequisites. This project serves as a jumping-off point for the future customer base. By designing this app to regulate the programmable thermostat, we are laying the groundwork for the regulation of all smart appliances from IOS and Android gadgets. We will provide users with a reliable and consistent, secure, and simple interface for controlling all gadgets. This software gives the corporation a competitive advantage as it will be the first on the market to regulate all connected devices in a single application. This report is meant for CapraTek stake – holders and as a reference for the project team as they work on the first version of the product.

1.2    Document Conventions

The person who engages the mobile phone application is alluded to as a user.

Stakeholder- Any non-developer who has level of interactivity with the software.

1.3    Intended Audience and Reading Suggestions

This report is meant for CapraTek stake – holders, project teams, sales representatives, and the development team to evaluate for prerequisites.

1.4    Product Scope

The Alfred! System will track smart thermostats and provide subscribers with ultimate control over the gadget. The objective of this project is to create a standalone login create account module that would be used to regulate Alfred system users. All contemporary CapraTek users will be moved to the new Alfred framework. Customers will be able to adjust the temperature, set schedules for use, and fine tune the thermostat configurations. Gadgets could be added or removed from the platform, and a location designated to a gadget. The software will monitor usage, and give users the alternative to use Energy Eco mode to maximize thermostat utilization. The Alfred system will give the users all facets of the thermostat.

1.5    References

Capella.Edu, 2021, Accessed 08 December 2021.

2.    Overall Description

The subsequent sections of this report provide a general overview, including attributes of this development’s users, the product’s hardware, and the product’s functional and non-functional prerequisites.

2.1    Product Perspective

Alfred is a new app that monitors and controls users’ smart thermostats. The Alfred software will be launched by the Apple app store, and all product users will be able to reach it via the smartphone device. Users must register in order to use the product, and all essential documentation will be stored in a database. This software program would be used to oversee a CapraTek advanced thermostat. This will be a project initiated for a prospective platform that would support Android and iOS for all CapraTek connected gadgets.

2.2    Product Functions

Users will be able to manage smart thermostats in different locations using this smartphone application. To access the system, users must first sign up and create an account. All new website visitors will have instantaneous access to latest smartphone application. Users are allowed to change settings, create a plan, adjust ambient temperature, and record the thermostat’s consumption. The customer can update or delete gadgets, and these gadgets could be in one or more areas. This new software would include an Energy Eco mode for conserving energy. At the installed location, the programmable thermostat will function as a traditional thermostat. To provide better customer service, error alerts for malfunctions or disrupted communications would be sent to subscribers and the customer support center.

2.3    User Types and Characteristics

Property owners, real estate agents, and homeowners would be the primary users of this product. Homeowners can use this software to manage various dwellings by establishing a minimum and maximum thermostat for all gadgets, or they can regulate each gadget independently. Real estate agents can use this software to regulate the temperature in a household on demand in order to decrease the consumption of energy used in properties for sale. In addition, the programmable thermostat could become a component sold alongside the home. This software will be used by property owners to measure and manage the temperature changes in their homes. They can use a timeline to optimize the thermostat or manually regulate the temperature.

2.4    Operating Environment

Only iOS devices will be supported by Alfred, software information will be stored in the cloud on a safe AWS container, and Oracle 12c would be hosted on Red Hat Linux servers.

2.5    Design and Implementation Constraints

The Alfred App will be available only for iOS devices and will necessitate a 5g LTE or Wi-Fi connectivity. One restriction of the application is the need for a Broadband connection. Because the software accesses data from the Oracle through the Internet, internet is required.

2.6    User Documentation

There will be a help section within the app with a step-by-step guidance for using the software, and also FAQs and a chat functionality for notifying customer support.

2.7    Assumptions and Dependencies

The product’s first assumption was that it would to use on a mobile iOS device. The second assumption is that the client has Wi-Fi access in the phone’s position and a 5gLTE or Wi-Fi linkage to the phone iOS gadget. It is reasonable to assume that users will know who to connect with and will access the software using smart phones.

3.    External Interface Requirements

3.1    User Interfaces

The user interface will include registration and login displays, a device list, a timeline screen for the gadget, and usage and cost details. When a first-time user opens the smartphone application, they should see the log-in section; if they have not enrolled, they would be able to do so by tapping the registration link on the login screen. The login screen would include two textbox with tags for login details. The device display will be a list of all the gadgets owned by clients. Devices can be added and removed from this display, and there is a link to alter the handset profile details. Every gadget in the roster would have a button for planning, and the timetable and temperature would be set with a calendar regulation to clarify days of the week and particular timeframes, and the thermostat would be set with a slide control.

3.2    Hardware Interfaces

The smartphone application would then communicate with CapraTek’s dataset and users via a secure AWS container.


3.3    Software Interfaces

All interfaces would be written for the iOS platform. The software would be hosted on AWS reliable containers and will communicate with CapraTek’s Oracle 12c dataset. For safety purposes, AWS will be made accessible via port 443.

3.4    Communication Interfaces

The mobile iOS app will communicate with AWS via internet protocol and would use port 443 to do so.

4.    System Features

4.1    System Feature 1

The Alfred system would include an ios app in which subscribers must sign up for an account with their client information. Customers have access to forgot username and forgot password links. They can then modify their details in the User profile, changing their passcodes, changing their contact information, changing their login details, emails, and other account information. In the customer device account, users will be able to add or remove devices, set up schedules for gadgets in different locations, track usage, cost, and change the settings. They will be able to save energy by using a pre-programmed Energy Eco mode. The system will send out notifications if there is no power or connection. The gadget will have a minimum and maximum temperature that it can safely reach. In addition, the framework will report all malfunction mistakes to CapraTek and notify users.


5.    Other Nonfunctional Requirements

5.1    Performance Requirements

This iOS app would be documented in Objective-C. Servers must have two or more processors and high-speed internet access to accommodate multiple links. To ensure scalability, a SAN for storage capabilities should be incorporated for the dataset. RAID V Disk Stripping will be used for redundant, off-site storage of databases. The initial load time of the product is determined by the intensity of the internet access.

5.2    Safety Requirements

The occupants of the residence may be harmed if the temperature is too excessive in either way.

5.3    Security Requirements

Users must verify themselves by logging in and having their identities authenticated by the directory. All communications must be encoded with an AES hash of 256 bits. To safeguard user information, databases should be encoded.

5.4    Software Quality Attributes

The user’s ability to enter data into the device in a sensible fashion, which should not be any more challenging than if they were at a desktop. To be deemed usable, all elements would be tested, along with user testing. Throughout the development process, screening will take place. Testing the entire application to guarantee that it does not take up a lot of space or runs too slowly, causing subscribers to be unable to fit it on the gadget.

5.5    Business Rules

The company must carefully consider the energy specifications and standards applicable to the region in which the smart home appliance is used in order to comply with the laws and guidelines imposed by the nation’s or state’s general law body.


6.0 Other Requirements

 Figure 1: Entity Relationship Diagram

Cite this Page

Software Requirements Specification | Research Paper Help . (2022, June 21). Essay Writing . Retrieved July 03, 2022, from
“ Software Requirements Specification | Research Paper Help .” Essay Writing , 21 Jun. 2022,
Software Requirements Specification | Research Paper Help . [online]. Available at: <> [Accessed 03 Jul. 2022].
Software Requirements Specification | Research Paper Help [Internet]. Essay Writing . 2022 Jun 21 [cited 2022 Jul 03]. Available from:
Do My paper price
Pages (550 words)
Approximate price: -
eskort bodrum - eskort eskişehir - mersin eskort - eskort mersin - mersin eskort bayaneskort bodrum - eskort eskişehir - mersin eskort - eskort mersin - mersin eskort bayan