I don't need the essay to be written just the program to be done if possible, I will write the essay by my self
22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 1/15 Printable page generated Thursday, 22 Apr 2021, 10:31 EMA This end-of-module assessment (TM352 EMA) must be submitted by 12 noon (UK local time) on 08 June 2021. This module uses the online TMA/EMA service for submission of the EMA. You can access this service through your Student Home page. A link to the booklet Information for Students Submitting Examinable Work Electronically will be sent to you approximately six weeks prior to the EMA submission cut-off date by the university’s Examinations and Assessment department. This will give you formal guidance about submitting your EMA, and you should read it carefully. Submission of your EMA is not the same as submission of your TMAs, and you must follow the instructions given in the booklet. This EMA takes the place of an examination and so is also referred to as the ‘examinable component’. The EMA makes up 50% of the assessment for this module and it is split into the following three sections: 1. a table contrasting different approaches to realising an app (18%) 2. the development of a demonstration mobile application (42%) 3. a discussion of the future development of the applications and their implications (40%). The EMA documentation is presented across two documents: The EMA scenario and questions EMA Database and API document which provides an overview and details of the EMA database, its content and the API with which it can be accessed. Please ensure you read both documents in conjunction with one another before embarking on your work for the EMA. What to submit It is a good approach to have a separate folder for your code files produced for part two and then to zip these folders together with your Solution Document to create a single EMA zip file for submission. You only need to create a single Solution Document file which contains the written answers for all three parts of the EMA. Your Solution Document should be a .doc, .docx or .rtf file that can be opened in Microsoft Word. Be sure to put your name, your personal identifier, the module code, the assignment number and the date on the title page of your Solution Document. It is also useful for the marker if you include this information as part of the 22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 2/15 header or footer of your document. Part 1 For this part your answer will comprise a single table and an appropriate set of references. The table will contrast three different approaches to developing mobile apps, such as a hybrid approach as demonstrated by Cordova against the two other approaches you have seen. Part 2 For this part your answer will consist of a section in your Solution Document, which contains your description of the functional requirements that you have implemented, along with a guide to installing and running your app. You must also submit your Cordova project’s www directory, ensuring that all your HTML and JavaScript is included. Put these elements together into a folder for part 2 to zip up as part of your EMA submission. Part 3 Your answer for this part should be a section in your Solution Document that discusses the four issues you have selected. Your complete zipped EMA file must be no more than 10 MB. If your file is bigger than this then you may need to compress any images you may have used in order to reduce the overall size. Please note that the cut-off for this assignment is 12 noon UK time. You can find guidance on using the online TMA/EMA service via StudentHome. Because the EMA is equivalent to an exam, your marks will not be returned to you via the TMA/EMA service. Your EMA will be marked in the same way as an exam and you will be informed of your results, by letter, approximately 2–3 months after the submission date. The EMA includes use of a database, which you may not be familiar with. You do not have to interact directly with the database however, because a REST API is used. You therefore only need to examine the database tables and sample data, which are quite simple to understand and these are described in a separate document. Experience has shown that students generally do much better if they read the EMA, understand the requirements and make a plan of work as a schedule so that it is clearer how the work will be completed in time for the submission deadline. Plagiarism 22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 3/15 It is imperative that you avoid plagiarism, as it is a form of cheating. If you do plagiarise, then you won’t simply lose marks: instead, your work will be referred for further disciplinary action. If you are in any doubt as to what constitutes plagiarism, please refer to the University guidelines or see the Module Guide. Extensions to the submission date for your examinable work are not available. If you are not able to submit your completed examinable work by the submission cut-off date, then please refer to the Information for Students booklet to see what options may be available to you. Scenario Note that although you have met MegaMaxCorp in earlier TMAs, the emphasis in the company’s profile and their desired direction have changed in some ways. You should therefore review the scenario carefully. The MegaMax Corporation sells widgets worldwide to large companies and small businesses and intends to develop its offering so that it can sell to the public, through the web and via a mobile sales force. Naturally, their stock situation is constantly fluctuating, as sales and deliveries are made, so they retain accurate information in a database. Specifically, they retain information on: products and prices special offers existing clients (or ‘customers’) salespeople – including their names, addresses, and contact details stock types and levels. These data are stored centrally, with varying levels of security, permissions and access. This allows access for: internal management and report generation internal sales staff who visit established clients public access, e.g. for purchasing products via the web. Prices are reviewed and altered on a day-to-day basis, with special deals regularly being made available on certain products, and to favoured clients. The database is currently hosted internally, with selected fields made available to web clients;, however, the company is currently considering migrating much of its data to cloud storage. http://www3.open.ac.uk/assessment/ug/ https://learn2.open.ac.uk/mod/oucontent/olink.php?id=1681532&targetdoc=Module+Guide&targetptr=5.2 22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 4/15 The company currently maintains a conventional set of web pages through which members of the public may obtain information about products, prices and deliveries, and through which they may place or view orders. These obviously interface with the stock, price and other data. In addition to conventional ordering from clients across the internet, the company retain a large and scattered sales force in the UK and worldwide, working generally with large corporations and businesses that make massive orders. These salespeople are given broad responsibility to: take orders from existing clients recruit new clients negotiate and strike special deals that are not currently available centrally with new and existing clients. The company thereforerequires an app for their sales force to use on a range of mobile devices. The app will provide read access to the company databases through a REST API to find: current customer data customer order history current price data currently available special deals. The app will also have write access to the databases via a REST API to register: new customer details updates to existing customer details orders (which may include special price deals). These functions will all be achieved through a set of forms displayed on a mobile device. The app may also provide some client-side processing to assist the salesperson in preparing orders, etc. (e.g. VAT calculations and totalling). Moreover, since the company tracks the locations of all members of their sales force, the app can use the geolocation capacities of the device on which it is running to report its position whenever access is made to the company’s central servers (and/or cloud storage), as well as recording the location when a sale is made. The geolocation facility can also be used with externally available map data to plot and cost routes between clients. To demonstrate the potential benefits and risks of using REST, web and mobile technologies, MegaMax would like to see some simple prototypes developed as rapidly as possible to show how these technologies might work together and to act as a focus for discussion and future development for the company. It is important to the company that the potential to develop a new website and a mobile application are demonstrated with both applications being based on the same instance of the company sales database. To this end, the company is considering employing a REST API for the database and have already developed an initial limited prototype of the API. 22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 5/15 It is thought that under this scheme (shown in Figure 1) a set of web pages would provide both the website for online ordering by clients, and a mobile app for the sales staff to place orders. Both applications would access the sales database via a single REST API. The website will call the API over the internet, while the mobile app, used by the mobile sales force, will make calls to the API over a mobile phone network. The API itself and the website will both run on web servers. The API will translate requests from applications into SQL operations on the database and will then return the appropriate data or an error message if something goes wrong. Figure 1 Components of web and mobile applications The prototype database and REST API are described in a separate document ‘EMA Database and API’. Part 1 Contrasting approaches to mobile development In Block 3 you worked with Cordova to develop a mobile application. This software requires that you adopt a certain approach to designing, developing and distributing an application. There are at least three different approaches to developing a mobile application. One of these is demonstrated by Cordova in terms of supporting the ‘hybrid’ approach. Each different approach embodies a range of positive and negative characteristics which can be considered in deciding which approach to adopt. Create a table which provides a concise and clear view for anyone to decide which approach they prefer for their own work. The table should have three columns, one for each development approach, and a row for each aspect you consider significant where you contrast the approach. Table 1: Example of initial table contrasting development approaches (cloud approach) Native Web based Hybrid Offers customisation Have control over service and can customise it as wish Little control or access over service and operation for customisation Can base customisations etc locally if appropriate but not in remote service 22/04/2021 EMA: View as single page https://learn2.open.ac.uk/mod/oucontent/view.php?id=1681532&printable=1 6/15 In your