Winds of Change: From Vendor Lock-in to the Meta Cloud

1476 words (6 pages) Essay

9th Apr 2018 Computer Science Reference this


Disclaimer: This work has been submitted by a university student. This is not an example of the work produced by our Essay Writing Service. You can view samples of our professional work here.

Any opinions, findings, conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of


A software requirement specification is a complete explanation of the system that is to be created. Software requirement specification includes non-functional and functional requirements. Use case technique can be used in prepared to identify the functional requirements of the software inventions. Non-functional requirements are requirements which force constraints on the implementation and design. As systems grew more complex, it becomes more apparent that the goal of the entire system can’t be easily included.

The software requirement specification consists of two important activities.

  • Problem/Requirement investigation
  • Product Function summary

Security is one of the most important points in wireless communication studies because it is an essential challenge since wireless messages are transmitted in the air so there is a chance that hackers can read out the messages and see what all the contents are there in the message.

Purpose of Software Requirement Specification:

A software requirement specification personifies the requirements of a system IEEE standard and is a organized collection of information.

A business analyst (BA), sometimes called system analyst is important for examining the business needs of their clients and for the persons having interest and concern in solving the problems and finding solution for the problems. BA typically performs a communication between the business side of an enterprise and the information technology department.

To list the user requirement in a specified manner is the main purpose of software requirement specification. It defines requirements for the software and restrictions needed to this application and document.

4.2 Performance Requirements


It is easy for the user to understand and respond as the Graphical User Interface of this application is user-friendly.

Response time:

It is the time taken to complete a work by the system by the user is found to be very less.


This system helps us to deliver the need for queries with high possibility and the functionalities that are available in the application.


To improve the quality of the product, the system can be extended to combine the changes that are done in the present application. Scalability is meant for the future works that is to be done on the application.

4.3 Functional Requirements:

Functional requirements are the statements of services the system should supply, how the system should behave in particular condition and how it behaves to certain inputs. Also the functional requirements define what the system should not do in some cases.

The functional requirements is based on the kind of software being evolved, when writing requirements the general approach taken by the organization and the anticipate users of the software. These requirements for a system report what the system should do. The requirements are normally describes in a fairly abstract way when it is exhibited as user requirements. Functional requirements may be exhibited in numerous ways for a software system and it describes the irregularity, its inputs and outputs and functions of system in detail.

Some of the typical functional requirements are:

1. Transaction corrections, adjustments, cancellations:

Here uploading the data on cloud by data owners are by the transactions which is done online. The end users upload the files to each cloud servers can be downloaded and viewed and these end users have to register to cloud service providers.

2. Authentication:

Here the users authentication is required to enter any of the modules implemented in the proposed system and is used to login into the cloud service providers servers.

3. Authorization- functions user is assigned to perform:

Here the users are allowed to login by registering and paying into cloud servers if the cloud services are to be used by paying. User has the right to upload the files to respective cloud servers and track the details which are uploaded after logging into the cloud by registering.

4. Audit Tracking:

An audit trail which is also called as audit log provides documentary proof of the series of activities that have elaborated at any time a particular operation, procedure or event and is a security-applicable chronological record, set of records, and/or at the end of line and source of records. Scientific research and health care data transactions, financial transactions, or communications by individual people, systems, components, accounts or other entities are the activities in which the audit records typically result from. The procedure that generates an audit trail can enter and administer all actions from all users; a standard user is not authorized to stop or change it and is typically required to always run in a prosperous mode. Additionally, database table with a string or trail file is not reachable to normal users in some cases. The use of a role-based security model in the software is another way of dealing with this issue. When using audit trail functionality, the software is required by many companies and it can also work as a ‘closed system’ or with closed-looped controls.

5. Historical Data:

Historical data is the data which is a collection of old records and it should always be present in database. Historical data should not be deleted by the cloud service provider from the database except the data owners are asking to delete the historical data.

4.4 Non-Functional Requirements:

Non-functional requirements are the requirements that are often called the qualities of the system. It can be used to form the operation of the system, rather than specific behaviors. Reliability (accuracy), response time and store occupancy are the emergent system properties that non-functional requirements deal with. Alternatively, they may define the constraints on the data representations used in system interfaces and the system capabilities of I/O devices.

Non-functional requirements are constraints, quality attributes i.e. it provide the method for designing the fitness and suitability of the product, quality goals, non-behavioral requirements i.e. it achieves its job such as reliability(accuracy) and defines the attributes of the system, efficiency(planning), timing constraints etc.. Non-functional requirements are divided into two main classes:

  • Security and usability are execution qualities.
  • Testability, maintainability, extensibility and scalability are evolution qualities.

Some of the non-functional requirements are:

  • Accessibility

Accessibility is the one in which a device, service, product or environment is available to many people as possible. Accessibility advantage from some system or organization and it can be observed as the “ability to access”. The cloud computing system is distributed software so it can be reached from any point of the world through internet without interfering.

  • Availability

Availability is the degree to which a system, subsystem, constituent or equipment is in a detailed operable and occurring state at the start of a mission, when the mission is called for as an unknown i.e. a non-specific time. The cloud computing system is distributed software so it can be reached from any point of the world without interference.

  • Reliability

Software reliability is the accuracy that has possibility that software will work properly in an identified environment and for a given time. The possibility of failure is calculated by testing a sample of all available input states using the following formula.

Probability = Number of failing cases/ Total number of cases under consideration.

System Reliability Specification:

  • Hardware reliability

Possibility a hardware component fails.

  • Software reliability

Possibility a software component will produce an incorrect output

Even though a bad result will occur, software can continue to operate in that condition

  • Operator reliability

Possibility a system user will make an error


Cite This Work

To export a reference to this article please select a referencing stye below:

Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.

Related Services

View all

DMCA / Removal Request

If you are the original writer of this essay and no longer wish to have your work published on the website then please:

Related Lectures

Study for free with our range of university lectures!