Distinguish between software errors, software faults and software failures. Give an appropriate live example to differentiate.

Introduction to Error, Defect, and Failure

Let’s try to understand the inter-relation between Error, Defect, and Failure:

It is well said by Thomas Muller “A person can make an error (mistake), which produces a defect (fault, bug) in the code, in software or a system, or a document. If the execution of the defect in code happens, the system will fail to do what it should do (or something it shouldn’t), which causes a failure.”

 Fault : It is a condition that causes the software to fail to perform its required function.

Error : Refers to difference between Actual Output and Expected output.

Failure : It is the inability of a system or component to perform required function according to its specification.

IEEE Definitions

Failure: External behavior is incorrect

Fault: Discrepancy in code that causes a failure.

Error: Human mistake that caused fault

Note:

Error is terminology of Developer.

Bug is terminology of Tester

What is Quality? How quality is related to testing?

 What Is Quality Assurance?

Quality assurance is a way to avoid mistakes in the project’s product or service, and thus prevent problems for your stakeholders. It’s the part of quality management that focuses on maintaining the integrity of the product or service, which gives stakeholders the confidence that their quality requirements will be met. It is, therefore, a foundational pillar of project management.

The Difference Between Quality Assurance and Quality Control

The difference between quality assurance and quality control is subtle but significant, although both terms are often used interchangeably to describe the quality management of the project’s product or service.

The difference is a matter of where the focus occurs in a project. Quality control is more concerned with quality earlier in the project process. Assurance, though, is more about the implementation of inspection and structured testing throughout every phase of the project.

Quality Assurance Approaches

• Failure Testing: Also referred to as stress testing, failure testing is a way to push a product to its limits by increasing vibration, temperature, humidity, etc., to expose inherent weaknesses, and then use those findings to improve the product to uphold a higher standard.
• Statistical Control: This type of quality assurance is based on analyses of objective and subjective data to track quality data, and then chart it against a common cause variance.
• Total Quality Management: Here the quality of the product is dependent on the participating constituents, some sustainable and controllable, others not. If the specification does not match its true quality requirements, then the quality is not guaranteed.
• Models and Standards: This is an international standard that has general requirements for competence. There are tests to carry out, 15 management requirements and 10 technical requirements, in a laboratory that is accredited.
• Company Quality: This concept came about in the 1980s and focuses on all departments approaching quality lead by management to develop a quality improvement process. This is done through controls, job management, process, performance, knowledge, skills and experience, integrity, confidence and infrastructure.

Whats the real meaning of 143

143 hmmm…. In numerical terms it is a three digit number, at the hundreds place is 1 and tens place is 4 and at the units place is 3 this is what I taught to my kid who is in grade 2…

For a guy proposing a girl it is 143 or I love you and if the girl doesn't like it is I Hate you….

Then one more I remembered now is I Like you , ‘ I Miss You’…

--------------------------------------------------------------------------------------------

143 in General as in India many a people consider it a language of letters..for example those who cannot say ‘I Love You’ directly use 1-4-3.
Then, it goes for the same ‘I Hate You’ , ‘ I Miss You’..etc
It entirely depends upon the connection you’ve with person saying or using it on you or in front of you.

I - 1 letter

Love - 4 letters

You - 3 letters

Even though there can be many words that can be formed in this format like

I kick you

I hate you

I miss you

I kiss you and many other but 143 for I love you is more familiar

Thank you 

How to run one-time setup code before executing any XCTest

One approach

When you try to use dispatch_once anyway, Xcode (>=8) is as always very smart and suggests that you should use lazily initialized globals instead. Of course, the term global tends to have everyone indulge in fear and panic, but you can of course limit their scope by making them private/fileprivate (which does the same for file-level declarations), so you don't pollute your namespace.

Imho, they are actually a pretty nice pattern (still, the dose makes the poison...) that can look like this, for example:

private let _doSomethingOneTimeThatDoesNotReturnAResult: Void = {
    print("This will be done one time. It doesn't return a result.")
}()

private let _doSomethingOneTimeThatDoesReturnAResult: String = {
    print("This will be done one time. It returns a result.")
    return "result"
}()

for i in 0...5 {
    print(i)
    _doSomethingOneTimeThatDoesNotReturnAResult
    print(_doSomethingOneTimeThatDoesReturnAResult)
}
This prints:

    This will be done one time. It doesn't return a result.
    This will be done one time. It returns a result.
    0
    result
    1
    result
    2
    result
    3
    result
    4
    result
    5
    result

Side note: Interestingly enough, the private lets are evaluated before the loop even starts, which you can see because if it were not the case, the 0 would have been the very first print. When you comment the loop out, it will still print the first two lines (i.e. evaluate the lets).
However, I guess that this is playground specific behaviour because as stated here and here, globals are normally initialized the first time they are referenced somewhere, thus they shouldn't be evaluated when you comment out the loop.

Model View View-Model (MVVM): Getting Started

Android MVVM 

MVVM stands for Model, View, ViewModel.

Model: This app contains data. He cannot speak directly to the scenario. In general, it is recommended to expose the data to the viewmodel by the observables.

View: It represents the UI of any application logic-free application. It observes the viewmodel.

ViewModel: It acts as a link between the model and the view. It is responsible for transforming the data from the model. It provides the data stream to the view. It also uses hooks or callback to update the view. It wants data from the model.

The following flow describes the main MVVM pattern.

hike wallpaper download HD

Hike wallpaper download HD 

Using Retrofit 2.x as REST client - Tutorial 1

1. Retrofit

1.1. What is Retrofit

Retrofit is a REST Client for Java and Android. It makes it relatively easy to retrieve and upload JSON (or other structured data) via a REST based webservice. In Retrofit you configure which converter is used for the data serialization. Typically for JSON you use GSon, but you can add custom converters to process XML or other protocols. Retrofit uses the OkHttp library for HTTP requests.

Add the following dependencies to your build.gradle file.

// retrofit
implementation 'com.squareup.retrofit2:retrofit:2.1.0'
implementation 'com.squareup.retrofit2:converter-gson:2.1.0'

Create New Java file RetrofitInterface.java

import retrofit2.Call;
import retrofit2.http.Field;
import retrofit2.http.FormUrlEncoded;
import retrofit2.http.POST;

/**
 * Interface for Retrofit
 */

public interface RetrofitInterface {


    @POST("user/login")
    @FormUrlEncoded
    Call<PojoUserLogin> login(@Field("countryCode") String countryCode,
                              @Field("userName") String userName,
                              @Field("fullName") String fullName,
                              @Field("birthDate") String birthDate,
                              @Field("profileUrl") String profileUrl,
                              @Field("loginType") String loginType,
                              @Field("deviceInformation") String deviceInformation);

}

Create New Java file Common.java  Application in manifest file.

import java.io.IOException;
import java.util.List;
import java.util.concurrent.TimeUnit;

import io.fabric.sdk.android.Fabric;
import okhttp3.Interceptor;
import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.Response;
import okhttp3.logging.HttpLoggingInterceptor;
import retrofit2.Retrofit;
import retrofit2.converter.gson.GsonConverterFactory;

public class Common extends Application {

    private Context mContext;
    private static RetrofitInterface mRetrofitInterface;

    @Override
    public void onCreate() {
        super.onCreate();
        Fabric.with(this, new Crashlytics());


        mContext = this;
        AppCompatDelegate.setCompatVectorFromResourcesEnabled(true);

    }


    public static boolean isInternetConnected(Context context) {
        ConnectivityManager connectivityManager = (ConnectivityManager) context.getSystemService
                (Context.CONNECTIVITY_SERVICE);
        NetworkInfo activeNetwork = connectivityManager != null ? connectivityManager
                .getActiveNetworkInfo() : null;
        return activeNetwork != null && activeNetwork.isConnectedOrConnecting();
    }

    public static RetrofitInterface getRetroFitInterface(Context mContext) {
        if (mRetrofitInterface == null) {
            initializeRetrofit(mContext);
        }
        return mRetrofitInterface;
    }

    private static void initializeRetrofit(final Context mContext) {
        OkHttpClient.Builder builder = new OkHttpClient().newBuilder();
        builder.readTimeout(Constants.TIMEOUT_SECONDS, TimeUnit.SECONDS);
        builder.connectTimeout(Constants.TIMEOUT_SECONDS, TimeUnit.SECONDS);
        builder.followRedirects(false);

        if (BuildConfig.DEBUG) {
            HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
            interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);
            builder.addInterceptor(interceptor);
        }
       
        builder.addInterceptor(new Interceptor() {
            @Override
            public Response intercept(Interceptor.Chain chain) throws IOException {
                Request original = chain.request();
                Request request;
             
                    request = original.newBuilder()
                            .header(mContext.getString(R.string.android), mContext.getString(R.string.android))
                            .header(mContext.getString(R.string.apiKey), mContext.getString(R.string.testAppKey))
                            .method(original.method(), original.body())
                            .build();
               
                return chain.proceed(request);
            }
        });

        Retrofit retrofit = new Retrofit.Builder().baseUrl(BuildConfig.BASE_URL)
                .addConverterFactory(GsonConverterFactory.create())
                .client(builder.build()).build();
        mRetrofitInterface = retrofit.create(RetrofitInterface.class);
    }


    public static void setUserData(PojoUserLogin.ResponseData responseData, Context mContext, String mLoginType, String mMobileNumber, String mCountryCode) {

        if (responseData.getPojoSettingModel() != null) {
            new PreferenceDefaultSettings(mContext).setSession(responseData.getPojoSettingModel().getSensitivity(), responseData.getPojoSettingModel().isNotifyCharger() + "",
                    responseData.getPojoSettingModel().isChargerDetection() + "", responseData.getPojoSettingModel().isVibrate() + "",
                    responseData.getPojoSettingModel().isFlash() + "", responseData.getPojoSettingModel().getbAlarmTime(), responseData.getPojoSettingModel().getbDetectionTime(), responseData.getPojoSettingModel().getAlarmTone());
            new PreferenceSettings(mContext).setToneId(responseData.getPojoSettingModel().getAlarmTone());
        }
        
    }

  
}

what about this pattern: 1 2 3 4 8 7 6 5 9 10 11 12 16 15 14 13 without matrix in java

what about this pattern: without matrix in  java 

1 2 3 4  

8 7 6 5  

9 10 11 12  

16 15 14 13

class pattern
{ 
    static void printPattern(int n)
    {
int count = 1;
for(int i=1;i<=n;i++)
{
for(int j=1;j<=n;j++)
{
if(i%2!=0)
{
System.out.print(count++);
}
else
{
System.out.print(count--);
}
}
if(i%2!=0)
{
count = count+3;
}
else
{
count = count+5;
}
System.out.println();
}   
}
    public static void main(String[] args) 
    {
        printPattern(4);      
    }

}

android architecture or Android software stack

or Android software stack is categorized into five parts:

1. linux kernel
2. native libraries (middleware),
3. Android Runtime
4. Application Framework
5. Applications

Let's see the android architecture first.

1) Linux kernel

It is the Android system design in the Android design. The Linux kernel is responsible for device drivers, power management, memory management, device management, and asset acquisition.

2) ancient libraries

The library's first library, such as WebKit, OpenGL, FreeType, SQLite, Media, C runtime library (libc), is at the top of the Linux Lunar Calendar.

The WebKit library is responsible for browser support, SQLite support, font support, FreeType for font support, audio and video formats for media playback.

3) Android Runtime

The main library in the android program and the DVM (Dalvik Virtual Machine) are responsible for running the android application. DVM, like JVM, is optimized for mobile devices. It uses less memory and provides faster performance.

4) Android Framework

There is a android framework on top of libraries and on the top of Android. Android API as an Android API, such as UI (UI), telephony, resources, locations, content providers (data), and bundled administrators. Includes. Enriching the Android application provides you with lots of features and interactions.

5) Applications

There are apps on the top of the Android infrastructure. All apps, such as home, contacts, settings, games and browsers are android configurations that use android launcher and libraries. Android Run and Native Libraries are using linux kernal. 

software requirements specification (SRS)

software requirements specification (SRS)

      Specification of Software Requirements (SRS) is a detailed description of the purpose and environment of the software under development. SRS fully describes what the software will do and how it will be expected.

1. INTRODUCTION

1.1 PURPOSE

The purpose of this document is to build an online system to manage flights and passengers to reduce flight management. << Include goals that are applicable to your project >>

1.2 CONVENTIONS OF DOCUMENTS

This document uses the following conventions. << Include conventions as per your application >>

DB Database

DDB Distributed Database

ER Entity Relationship

1.3 SUGGESTED SITUATION AND READING SUGGESTIONS

This project is a prototype for flight management system and is restricted within college areas. It was implemented under the guidance of college professors. This project is useful for flight management teams as well as for passengers.

1.4 SCOPE PROJECT

The purpose of the online flight management system is to reduce flight management and to create a convenient and easy-to-use application for passengers, trying to buy airline tickets. The system is based on a relational database with its flight management functions and reservation. We will have a database server that supports hundreds of major cities around the world as well as thousands of flights by various airline companies. Above all, we hope to provide a comfortable user experience with the best available pricing.

1.5 REFERENCES

https://krazytech.com/projects

Basis of database systems by ramez elmarsi and shamkant b.navathe

2. GENERAL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

A distributed database system of the airline stores the following information.

Flight details:

This includes the origin of the flight terminal and destination terminal, including stops between, the number of seats booked / available seats between the two destinations etc.

Customer description:

This includes customer code, name, address and phone number. This information may be used for maintaining customer records for any emergency or for any other type of information.

Reservation description:

This includes customer details, code number, flight number, booking date, travel date.

2.2 PRODUCT FEATURES

The main features of the airline database system as shown below entity-relationship model (ER model)

2.3 USER CLASS and CHARACTERISTICS

System users should be able to get flight information between two provided cities with the provided date / travel time from the database. A route from city A to city B is a sequence of connecting flights from A to B such that: a) with the most two connecting stops, excluding the city's starting city and destination travel, b) the connection time is between one to two hours. The system supports two types of user privileges, Customer, and Employee. Customers will have access to customer functions, and employees will have access to both customer management and flight management functions. Customer must have the following functions:

Make a new reservation

• A lane

• Back and forth

• Multiple cities

• Flexible Date / time

• Confirmation

Cancel an existing reservation

See his itinerary

The employee must have the following management functions:

CUSTOMER FUNCTIONS.

• Get all customers with seats available on a given flight.

• Get all the flights for a given airport.

• View the flight schedule.

• Get all the flights that the arrival and departure times are timely / delayed.

• Calculate total sales for a given flight.

ADMINISTRATIVE

• Add / Remove flight

• Add a new airport

• Update fares for flights.

• Add a new flight leg opportunity.

• Update departure / arrival times for flight leg instance.

Each flight has a limited number of available seats. There are a number of flights to leave or come to different cities at different dates and times.

2.4 LOCAL CHANGES

The operating environment for the airline management system is as listed below. << Include details according to your application >>

distributed database

client / server system

Operating system: Windows.

database: sql + databases

platform: vb.net/Java/PHP

2.5 DESIGN and IMPLEMENTATION CONSTRAINTS

The global schema, fragment schema, and allocation scheme.

SQL commands for the above questions / applications

How to generate response for application 1 and 2. Assume they are global queries. Explain how different fragments work together to do this.

Implement the database at least using a centralized database management system.

2.6 DEPENDENCY OF ASPLEMENTS

Let's say that this is a distributed airline management system and is used in the following applications:

A request for reservations / cancellations of a flight from any source at any destination, providing connected flights in case of no direct flight between the specified Source-Destination pair exists.

Calculating the high fliers (most frequently fliers) and calculating the appropriate rewards points for the fliers.

Assuming both transactions are single transactions, we design a distributed geographic database by dispersed in four cities Delhi, Mumbai, Chennai, and Kolkatta as shown in fig. below.

3. SYSTEM FEATURES

DESCRIPTION and PRIORITY

The airline reservation system maintains information about flights, seat classes, personal preferences, prices, and bookings. Of course, this project has a high priority because it is very difficult to travel to countries without prior reservations.

STIMULUS / RESPONSE SEQUENCES

Find Airline Flights for two Travel Cities

Displays a detailed list of available flights and make "Reservation" or Book a ticket on a particular flight.

Cancel an existing Reservation.

FUNCTIONAL REQUIREMENTS

Other system features include:

DISTRIBUTED DATABASE:

The provided database indicates that a single application should work well with data that spreads across different databases and connected through a network of communications as shown below.

CLIENT / SERVER SYSTEM

The term client / server mainly refers to an architectural or logical division of responsibilities, the client is the application (also known as front-end), and the server is the DBMS (also known as back-end).

A client / server system is a distributed system where,

Some sites are client sites and others are server sites.

All data is located on server sites.

All applications execute on client sites.

4. REQUIREMENTS OF EXTERNAL INTERFACE

4.1 USER INTERFACES

Front-end software: Vb.net version

Back-end software: SQL +

4.2 hardware INTERFACES

Windows.

A browser that supports CGI, HTML and Javascript.

4.3 INTERFACES OF SOFTWARE

The following are the software used for online flight management management. << Include software details as per your project >>

Software used	Description
Operating system	We have chosen Windows operating system for its best support and user-friendliness.
Database	To save the flight records, passengers records we have chosen SQL+ database.
VB.Net	To implement the project we have chosen Vb.Net language for its more interactive support.

4.4 COMMUNICATIONS INTERFACES

This project supports all kinds of web browsers. We use simple electronic forms for reservation forms, ticket reservations etc.

5. NONFUNCTIONAL REQUIREMENTS

5.1 REQUIREMENTS OF PERFORMANCE

The steps involved to carry out the implementation of the airline database are as listed below.

A) E-R DIAGRAM

The E-R Diagram generates a technique for representing the logical structure of a database in a pictorial way. After this analysis is used to sort the data as a relation, normalizing the relationship and finally getting a database of relevance.

ENTITIES: Which distinguish real-world objects in an application.

REQUIREMENTS / REQUIREMENTS: Which define the characteristics of an entity and relationships.

RELATIONSHIP: Which entities connect and represent significant dependencies between them.

B) NORMALIZATION:

The primary purpose of normalization is to reduce the redundancy which means that information should be stored only once. Information storage several times leads to waste storage space and increase in total data size stored.

If a database is not properly designed it can increase with anomalous change. Changing anomalies will appear when the data is added to, modified or deleted from a database table. Similarly, in traditional databases as well as improperly designed relational databases, data redundancy can be a problem. These can be removed by normalizing a database.

Normalisation is the process of collapse of a table into smaller tables. So that each table is related to a single theme. There are three different types of anomaly changes and consists of the first, second and third normal forms (3NF) being considered sufficient for most practical purposes. It should be considered only after careful analysis and complete understanding of its implications.

5.2 SAFETY REQUIREMENTS

If there is extensive damage to a large portion of the database due to failure of failure, such as a disk crash, the recovery method returns a previous copy of the database that is backed up to archival storage (usually tape ) and reconstructs a more current state by reapply or reduces the operations of the assigned transactions from backed up logs, to the time of failure.

5.3 SECURITY REQUIREMENTS

Security systems require database storage like many other applications. However, special security requirements in the market means that vendors should choose their database partner carefully.

5.4 SOFTWARE QUALITY QUALITY

REQUIREMENTS: The flight must be available at the specified date and specified time many customers are making advance reservations.

KATARUNGANG: The flight must reach the start of the right starting terminal and must reach the correct destination.

MAINTAINABILITY: Administrators and flight chargers must maintain proper flight schedules.

USABILITY: Flight schedules should satisfy a maximum number of customer needs.

firebase push notification android example

firebase push notification android example 

In recent times, Google moved from Google Cloud Messaging (GCM) to Firebase Cloud Messaging (FCM). Just like GCM, FCM is a cross-platform messaging solution that allows you to send messages. FCM is completely free and there are no limitations.

If you have followed any of my previous tutorials about GCM, I strongly recommend you migrate to Firebase today itself. In this article we learn the features of firebase cloud messaging by building a simple app. We’ll also learn how to integrate firebase to your backend, so that you can send the messages from your server.

AndroidManifest.xml

<uses-permission android:name="android.permission.INTERNET"/>

<service android:name=".firebase.FireIDService">
    <intent-filter>
        <action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
    </intent-filter>
</service>
<service android:name=".firebase.FireMsgService">
    <intent-filter>
        <action android:name="com.google.firebase.MESSAGING_EVENT" />
    </intent-filter>
</service>

build.gradle Project

classpath 'com.google.gms:google-services:3.1.0'

build.gradle App

dependencies {

    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation 'com.android.support:appcompat-v7:26.1.0'

    implementation 'com.android.support.constraint:constraint-layout:1.1.0'

    compile 'com.google.firebase:firebase-messaging:11.0.2'

    testImplementation 'junit:junit:4.12'

    androidTestImplementation 'com.android.support.test:runner:1.0.1'

    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'

}

apply plugin: 'com.google.gms.google-services'





FireIDService.java

import android.util.Log;

import com.google.firebase.iid.FirebaseInstanceId;
import com.google.firebase.iid.FirebaseInstanceIdService;

public class FireIDService extends FirebaseInstanceIdService {
    @Override    public void onTokenRefresh() {
        String tkn = FirebaseInstanceId.getInstance().getToken();
        Log.d("Device Token","Token ["+tkn+"]");
    }
}


FireMsgService.java


import android.app.NotificationManager;
import android.app.PendingIntent;
import android.content.Context;
import android.content.Intent;
import android.support.v4.app.NotificationCompat;
import android.util.Log;

import com.firebasedemo.activity.MainActivity;
import com.firebasedemo.R;
import com.google.firebase.messaging.FirebaseMessagingService;
import com.google.firebase.messaging.RemoteMessage;

/** * Created by Rid's Patel on 22-04-2018. */
public class FireMsgService extends FirebaseMessagingService {

    @Override    public void onMessageReceived(RemoteMessage remoteMessage) {
        super.onMessageReceived(remoteMessage);

        Log.d("Msg", "Message received ["+remoteMessage+"]");

        // Create Notification        Intent intent = new Intent(this, MainActivity.class);
        intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
        PendingIntent pendingIntent = PendingIntent.getActivity(this, 1410,
                intent, PendingIntent.FLAG_ONE_SHOT);

        NotificationCompat.Builder notificationBuilder = new                NotificationCompat.Builder(this)
                .setSmallIcon(R.mipmap.ic_launcher)
                .setContentTitle("Message")
                .setContentText(remoteMessage.getNotification().getBody())
                .setAutoCancel(true)
                .setContentIntent(pendingIntent);

        NotificationManager notificationManager =
                (NotificationManager)
                        getSystemService(Context.NOTIFICATION_SERVICE);

        notificationManager.notify(1410, notificationBuilder.build());
    }
}