Methods of office automation
This report covers various methods that can facilitate office automation. The article chooses two methods that prove to be critical in better cloud implementation. These methods are;
- Prototype testing
- Ad hoc testing
Ad hoc testing avails the various informal methods that can be used to detect errors in an automated system. The test analyzes such as system with the aim of breaking it to come up with a more advanced project;
At what time should it be used?
In the times where a company needs urgent ways of detect sources of faulst in their system, the ad hoc method come in handy to solve them. The test done shouls also be an exhaustive examination that ad hoc provides. After a sytem ahs beee n built and needsassuranc eof its performance level, the ad hoc tester is issued the jb to quickly rate is performance level. Critical to its applicaton is the skills of the testrer, if the examiner is well skilled in testing office automated systems then an ad hoc test is viable for use.
Ways that improve the efficiency of ad hoc testing
When one prepares a documented version of a similar software, the ability of identifying a fault in the tester increases incredibly thereby faults can be identified easily.
- Getting a rough method of approach
By using a rough method of approach, the examiner is inclined to increase the focus to solve the task at hand.
- Divide and rule
Some automated offices have alrge sytemsthat are to be tested. The best way to solve this problem is to create a partioned prooblem form the main one and try solving these partions one by one.
- Prototyping model
Prototyping involves consequent usage of less and simpler projects that represent main aim to com e up with a final project that represents it. Prototypes are these previous sampled and used inventions.
Ad hoc method main benefits.
- Ad hoc testing enables using newer testing ways that facilitate better spotting of faults in designed systems.
- Whenever there is a short time in developing a workable automated office, ad hoc test is used.
- The testers in ad hoc method are much focused since there is no need for documenting the procedure of invention leaving task in solving.
- The ad hoc test is applicable at any time wherever the Software Development Cycle is begun.
Ad hoc testing issues
- The undocumented way of solving defects in a system leads to creation of other defects.
- The method is best applicable with well skilled personnel.
- Over reliance on memory can lead to defective test building since the human mind is prone to forgetting.
Prototyping model benefits
- The employees and customers are able to take part in the development cycle.
- Faults in the system are detected prior before the last inveting proceduere.
- The staff in the automated office get to have a rough idea on the software operation during its development.
- The defects in the tested systema re easilty identified.
- There are well performing projects are can be developed when users get involved. (Karan Singh, 2013).
Prototyping model issues
- The cosequent advance in system imrovemwnt make the softawre complex.
- The steps involved in the system design are recurring making the implementation tiresome.
Advice to the SoftArch Engineering Company
Office automation that lead to cloud computing can be invented by a number of applicable procedures. In this excerpt the chosen ways to automate an office is by ad hoc testing that involves rough examination of a system till it breaks or the prototyping model that aims at recurrence in developing an automated office. With these two ways of implementation, there comes there advantages and disadvantages.
Secondly, the model that involves prototypes comes as a preferred method that takes panning to execute. Steps are developed in it to improve the examining approach to the system. These steps involve development of prototypes along the way.
The second method that entails development of prototypes, prototyping method, comes out as a better application of office automation. The better characteristics are in the points of involving the users of the software in developing the cloud compute. This provides a viewing point in the software usage before the final intended outcome of the intention is achieved. The prototypes also easily identify defects leading to better developed solutions to the intended design. Also, the method has less isue that come up after the end cycle.
Differences existing in locally hosted infrastructure and IaaS provider.
- Hardware differences
Locally hosted infrastructure require purchasing of hardware that become obsolete in the coming years due to hardware improvement but in IaaS the cloud uses a central host storage device that is class in technology that withstands many technological improvements.
- Software differences
A rise or drop in staff in locally hosted infrastructure make the company spend cash to purchase or dispose the related equipments but in IaaS there exist a flexible way of increasng or reducing the facilities required. The cloud computing avails vrtual allocation that supplies software for usage.
- Support differences
The locally hosted infrastructure has a disadvantage when it comes to system improvement as the complexity of the internet servicing devices increases gradually. The labor involved also is lump sum as the equipment are many. In IaaS, the provider’s support system is able to be expandable and the labor involved in the servicing is also small.
- Access differences.
The traditional way of accessing information, by physically being available. Elevates the dependency of the user to the network provider as there may be network disconnection in some areas but in IaaS, there are dedicated servers that boost network connections thus reducing dependency in the network systems.
- Performance differences
Whenever there is an onsite premise that requires installation, the installers capability affects performance thus a varying performing network is installed but in IaaS there is one central hosted servicing equipment developed and maintained by highly skilled individuals to produce a one better performing network (Norbert Pohlmann, 2011).
- Security Differences
There is a security risk if all the staff or users can physically access data in a network as in the locally hosted infrastructure but in IaaS the cloud provider issues high level security for those personnel that need to access data. It has reduced number of individuals physically accessing information in the network thus good security.
- Scalability differences.
At any given time the company’s economy may increase or decrease. In Locally hosted infrastructure, a change in the economy leads to high cost in the resulting change to fit the change. An increase its productivity leads to an increase in maintenance and allocation of equipment. In IaaS, an increase in economy of a company simply means purchasing more services in the cloud or decrease means unsubscribing from it. Thus making its scalability to be high.
- Power and cooling differences.
In large locally hosted infrastructure, there is a high power usage and cooling facilities that are large. The rate of power consumption in them is very big. In IaaS, a centralized hosting system powers the network making a much reduced power consumption with better cooling ability.
Summarized advice to the company
Locally hosted infrastructure
The locally hosted infrastructure involves access of data physically and lead to insecurity in the network service system. The network is highly dependent on the internet serving facility and therefore makes production and servicing much harder. The increase or decrease of equipment affects the system heavily making its scalability to be low. There is a poor disaster recovery solution in this sort of web.
The IaaS constitutes individual monitoring of the site in use. The user takes the responsibility of managing the given account. This characteristic proves profitable in the disaster recovery methods as data are backed up in a central host well protected.
Recommendation on the best infrastructure.
Comparing and contrasting the two infrastructures makes the article conclude to that IaaS is the better. IaaS is profitable. More to that is the strict access of data in it makes a better secured networking service. The idea of providing security clearance for highly specified content is proof. There needs not to be a lot description as IaaS has proven to have well servicing infrastructure of the two.
Difference between IaaS, PaaS, and SaaS
Software as a Service (SaaS) has a front-end design that allows third personnel provider to service and deliver over the web. The software issued in this site can be purchased by the users. Mainly the third- party is the management of this infrastructure.
Platform as a Service (PaaS) gives out platform for software development. The platform comsisst of software subscription and hardwarepurchasing. These facilities are crucila fro application development within the cloud network. The networking provicion allows faster and efficient testing. (Chao, 2012).
Lastly, Infrastructure as a Service (IaaS) provides hardware and software s a service in the aim of giving a highly functional server and storage systems. The provider gives out a network that enables access, managing and monitoring of the cloud service. This can be explained by the use Google Compute Engine.
Recommendation of the best cloud service network
The Software as a Service (SaaS) comes out the better of the three infrastructures. It has a more profitable marketing strategy that is competitive in the marketing economy. The characteristics are end produce of the benefits of using SaaS as a servicing web infrastructure.
Firstly, the web service gives the chance of configuring information. Further, the configuration makes it to be customizable in nature. Thereby a self-serving environment is available just as the individual owned computers.
Secondly, the staff in the newtork can collbotate to produce quality work through confrencing in the cloud. The sharing capabilty in these sort of services makes them banefeicial fro moblie workers. In addition to that, the third-party proider supervises the usage of the web cloud to comeup with improved versions of these servicing infrastructure.
Issues encountered in Software as a Service (SaaS)
To begin with, the SaaS requires constant internet service connection whenever it has to be used. This feature hinders staff members form collaborating in their work ventures in case there is limited internet access in the region.
Another drawback is the level of security that companies risk in admitting its document to internet service providers. Companies involved in the SaaS take the chance to give their high valued documents to cloud networks though they might get lost or interfered with. This nature is hard to get over as sensitive documents mean probability of losing sensitive company data.
The SaaS avails automatic system update and upgrade. Both the software and hardware changed regardless of the effect it poses on specific businesses. Some upgrades and updates may lead to losses. The losses are due to infringement in the architecture of an individual company. The company therefore could opt to retain the outdated facilities that specifically makes it better in functioning.
Solving the discussed issues
SaaS servicing entails constant connection to the web. Invention of Software plus Service helps in solving this. Initially, the SaaS had the disadvantage of failing to serve during internet disconnection. The Software plus Service give a hybrid internet connection where internet connection physically over the web.
The disadvantage of handing crucial management and client information to a servicing network can be solved by providing legal documents that bind the two parties to a contract that ensures security of the data. When one hand over comprehensive, sensitive company information to service providers, insecurity arises. This can be handled by ensuring the provision of a well legally documented contract that provides security as per the service level contract.
Staying at current software update hinders group progress. The SoftArc Engineering Company can request for a better customized software that functions to their advantage. The custom may be the past better working software or an improved version of the current (RAO, 2015).
Chao, L. (2012). Cloud Computing for Teaching and Learning: Strategies for Design and Implementation: Strategies for Design and Implementation. Fresno: IGI Global.
Daoliang Li, Y. C. (2015). Computer and Computing Technologies in Agriculture VIII. San Jose: Springer.
Gill, A. Q. (2015). Adaptive Cloud Enterprise Architecture. Saint Paul: World Scientific.
Karan Singh, A. K. (2013). Quality, Reliability, Security and Robustness in Heterogeneous Networks: 9th International Confernce, QShine 2013, Greader Noida, India, January 11-12, 2013, Revised Selected Papers. Albuquerque: Springer.
Kavis, M. J. (2014). Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS). Mesa: Wiley.
Marinescu, D. C. ( 2013). Cloud Computing: Theory and Practice. Milwaukee: Newnes.
Norbert Pohlmann, H. R. (2011). ISSE 2010 Securing Electronic Business Processes: Highlights of the Information Security Solutions Europe 2010 Conference. Washing DC: Springer Science & Business Media.
Paolo Bellavista, R.-S. C.-C.-F. (2010). Advances in Grid and Pervasive Computing: 5th International Conference, CPC 2010, Hualien, Taiwan, May 10-13, 2010, Proceedings. Seattle: Springer Science & Business Media.
Raj, P. (2012). Cloud Enterprise Architecture. Jacksonville: CRC Press.
RAO, M. (2015). CLOUD COMPUTING. San Diego: PHI Learning Pvt. Ltd.
Ruay-Shiung Chang, T.-H. K.-L. (2011). Security-Enriched Urban Computing and Smart Grid: Second International Conference, SUComS 2011, Hualien, Taiwan, September 21-23, 2011. Proceedings. Dallas: Springer.
Syed A. Ahson, M. I. (2010). Cloud Computing and Software Services: Theory and Techniques. Atlanta: CRC Press.
Tejaswi Redkar, T. G. (2011). Windows Azure Platform. Milwaukee: Apress.
Thomas Erl, R. P. (2013). Cloud Computing: Concepts, Technology & Architecture. Austin: Prentice Hal.
Tim Mather, S. K. ( 2009). Cloud Security and Privacy: An Enterprise Perspective on Risks and Compliance. Tucson: O'Reilly Media, Inc.
Victor Chang, M. R. ( 2017). Enterprise Security: Second International Workshop, ES 2015, Vancouver, BC, Canada, November 30 – December 3, 2015, Revised Selected Papers. Stockton: Springer.