Answer the below question with 50 words on each topic and two replies with 50 words each on each topic. You should have a total of 3 posts.

Define and describe a capital expense. How are capital expenses different from operational expenses?

• Discuss why a designer should avoid selecting an implementation platform for as long as possible during the design process.
• Using Yahoo! Pipes, create a pipe that displays the names of pizza restaurants within a given zip code.
• Define scalability.

Reply:

Rightsizing

Right-sizing presents two recommendations, both the performance and cost-based recommendation. Therefore, right-sizing refers to identifying an optimal cloud computing configuration that will improve the performance and lower cost. In other words, it means the avoidance of increasing costs or wasting money on unnecessary practices. It ensures that the harvest most out of cloud computing (Khanduja & Mishra, 2012).

Functional and non-functional requirements

The difference between the two system requirements is that functional requirements describe the systems’ fundamental behaviors, while non-functional requirements refer to how they should perform its functions (Kaur, 2015). The other difference is that functional requirements revolve around product features, while non-functional requirements are concerned with the product features. An example of functional requirements is that they should only allow managers to access customer-banking data. The other example is that the website should load whenever the user clicks the button. An excellent example of a non-functional requirement is that all web site should take less than four minutes to load. The other example is that the security of a database should meet the HIPAA requirements.

Non-functional requirements trade-off

When the developer is defining the technical requirements of the system, they must consider the system availability. In other words, they should define whether the system is available 24/7. The other consideration is the supportability of the system. That is whether the support is in-house or external. They should also consider that robustness of the software would depict a rise in total development cost. The application should also support upgrades and modifications as it grows or changes the environment.

Profit margin

We were provided with $2.5 million in revenue and an expense of $2.1 million. The profit is the difference between revenue and expense.

Profit = $(2.5-2.1) million

Profit =$ 0.4 million

Profit margin = 0.4/2.5

Profit margin = 0.16 which is 16%

second post

Moore’s law and influence cloud migration

Moore’s law states that “The number of transistors that can be placed on an integrated circuit doubles every two years”. This law was proposed by American Engineer Gordon Moore, who is also one of the cofounders of Intel. As per this law, the computing power and disk storage capacity also double at nearly this rate. The result is that capital investment in computing devices has a very short effective life expectancy. The systems we buy today maybe only be half as fast as those we will purchase two to three years from now. By shifting computer resources to the cloud, companies eliminate the need to update their own data center, storage, and servers, which may result in considerable cost savings. Today, within the cloud environment, based on the requirement we have different services such as SaaS, PaaS, and IaaS (Jamsa,2013).

Functional and Non-functional Requirements

A requirement states how a particular functionality or feature of a product should work. Organizations need a few types of requirements to create a good product. System requirements are classified into two categories: functional requirements and non-functional requirements (Jamsa,2013).

Functional Requirements

The functional requirements specify what the system does—that is, the specific tasks the system will perform. Functional requirements describe what the product should do. Such software requirements capture the intended behavior of the system. A functional detail should be aligned to a business need to avoid project failure. Normally, the functional requirements are provided by the system or business analyst to the designer within the specification of the things that the system needs to do. Functional requirements cover Business rules Transaction corrections, adjustments, and cancellations Requirements for administrative functionality Authentication Authorization levels Audit tracking, etc (Matyunina, 2021). Some of the examples of functional requirements

• The system should allow only managers to access a user’s personal data.
• The background color for all application windows will be #3333FF.
• Only employees at a certain level have the right to view revenue data
• The software system should be integrated with a certain API

Non-functional requirements

Nonfunctional requirements specify how the system will work behind the scenes. a non-functional requirement is any requirement that specifies how the system performs a particular function. A non-functional requirement describes how a system should behave and the limits of its functionality. Non-functional requirements answer for all the requirements that are left uncovered by functional requirements. Nonfunctional requirements are often called quality requirements and include common factors such as performance, reliability, and maintainability (Matyunina, 2021). Some of the examples of non-functional requirements are

• All web pages should be able to load within three seconds.
• The system must accommodate a minimum of three million concurrent users.
• The system should require users to enter their passwords every 60 days.

Scalability

Scalability is the ability to increase or decrease resource use such as servers or data storage on the users demand, as processing needs require. Scalable applications can scale up resources when there is high user demand and scale down resources when there is low demand. A system, business or software that is described as scalable has an advantage because it is more adaptable to the changing needs or demands of its users or clients. Scalability is often a sign of stability and competitiveness, as it means the network, system, software or organization is ready to handle the influx of demand, increased productivity, trends, changing needs and even presence or introduction of new competitors (Jamsa,2013).

Importance of HTML5

HTML5 Fifth release of the hypertext markup language, which provides device-independent support for multimedia capabilities previously available through Flash-based applications. HTML5 works across all devices so developers do not have to worry about missing out on a significant potential audience. In fact, it’s thought that many native apps will eventually just act as a portal into an HTML5 web passed app, with users not being aware of any difference. With HTML5, rich media aspects that were formally handled by plugins (think Flash), are now built-in. That’s why there are <audio> and <video> media tags (Sophia, 2016).