Software Engineering

Introduction 1. Hardware based testing: The device including the internal processors, internal hardware, screen sizes,  resolution, space or memory, camera, radio, Bluetooth, WIFI etc.  2. Software or Application testing: The applications that work on mobile devices and their functionality are tested.  I.e. Mobile Application Testing Step of Mobile Application Testing Documentation Testing: Requirement analysis ,Test plan, Test cases  are created Functionality Testing Installation and Running the application Fields: Verify all fields works correctly, Mandatory and optional  fields are displayed differently.  Business Functionalities Testing Interruptions : Notifications, Network, SD Card Insert or remove Constant User Feedback: Progress bar, Network error,  Deleting important info. App Update : App Update process, ensure previous user  data is saved. Device Resource: Memory, Installation on SD Card etc .  3. Usability Testing : Usability testing is aimed to ensure the convenience of u

System permissions are divided into several protection levels. The two most important protection levels to know about are normal and dangerous permissions: Normal permissions cover areas where your app needs to access data or resources outside the app's sandbox, but where there's very little risk to the user's privacy or the operation of other apps. For example, permission to set the time zone is a normal permission. If an app declares that it needs a normal permission, the system automatically grants the permission to the app. For a full listing of the current normal permissions, see Normal permissions . Dangerous permissions cover areas where the app wants data or resources that involve the user's private information, or could potentially affect the user's stored data or the operation of other apps. For example, the ability to read the user's contacts is a dangerous permission. If an app declares that it needs a dangerous permission, the user has to explic

THE RISK DRIVEN MODEL - Introduction As digital systems become part of everyday life for most of us that caused increase in the development of software systems and applications hugely. The increasing number also shows the worries of developers for risk of failure for different stages of the development and different platforms including web. The management of risk is very important factor to be considered for all software development processes. The risk driven model is very simple and easy to use with having low “risk of failure” level which attracts most of the developers. However, the development of software means developer must anticipate the possible risk of failure for different stages by using right tools and techniques. Though which development technique is more reliable? Or which architecture is enough for developer? And which is model should developer use is still a question. So here I present how risk driven is enough for the developers for all stages (including an