Each Android app must have an Android manifest file. It is one of the most important configuration files manually written by developers. In addition to various configuration parameters required to run an app, it also contains configuration parameters which are used to implement security, compatibility, and accessibility of an app. Any mistakes in writing the manifest file can cause serious implications in terms of security, reliability, and availability of an app. In this paper, we study and report different types of mistakes committed by developers in writing Android manifest files. The study was performed on 13,483 real-world Android apps. We also present an open source rule-based static analysis tool which detects developer mistakes in the manifest file. The tool generates a warning message if it detects any misconfigurations in the manifest file. We used the tool to perform the empirical study and it generated total 59,547 configuration errors in 11,110 apps. Only 2,373 apps, among studied apps, do not have any configuration errors.

Embedded system covers a large range of highly sensitive area where a slightest error can damage large number of resources even cost human life. So testing embedded system is extremely essential concern in computer science industry. Errors can lies between interacting software and hardware module of embedded system. This interactions can be modeled in terms of data flows between subsystems, i.e. Module, component etc. Tracking data flow across different components is important because applications use this to activate interactions that acquire different values and resources in ways that may ultimately exercise faults. Integration testing is a verification technique of the interfaces among system parts. The integration test of software components is especially concerned with the detection and uncover of interface errors, which are not detectable during unit testing. Existing integration testing approaches typically focused on direct interaction of subsystems which is done by function call but there exists other interactions for indirect dependencies between subsystems, which may occur faults in the system. There are no specific general models for representing all interactions. In this paper we propose an interaction model to cover all possible direct and indirect interaction and provide an integration testing approach using data flow analysis to generate minimal test cases efficiently.

It is well known that requirements engineering plays a critical role in software quality. The use case approach is a requirements elicitation technique commonly used in industrial applications. Software requirements are stated as a collection of use cases, each of which is written in the user's perspective and describes a specific flow of events in the system. The use case approach offers several practical advantages in that use case requirements are relatively easy to describe, understand, and trace. Unfortunately, there are a couple of major drawbacks. Since use cases are often stated in natural languages, they lack formal syntax and semantics. Furthermore, it is difficult to analyze their global system behavior for completeness and consistency, partly because use cases describe only partial behaviors and because interactions among them are rarely represented explicitly. We propose the Constraints-based Modular Petri Nets (CMPNs) approach as an effective way to formalize the informal aspects of use cases. CMPNs, an extension of Place/Transition nets, allow the formal and incremental specification of requirements. The major contributions of the paper, in addition to the formal definitions of CMPNs, are the development of: 1) a systematic procedure to convert use cases stated in natural language to a CMPN model; and 2) a set of guidelines to find inconsistency and incompleteness in CMPNs. We demonstrate an application of our approach using use cases developed for telecommunications services.

Process modeling has become increasingly attractive in the software engineering community. In process modeling, the enactment of software process model is a dominant theme. In order to correctly and smoothly enact the software process model, it is necessary to detect the inconsistencies contained in the software process model early, before the software process model is instantiated to actual enactment engine. We provide an analysis framework and an enactment mechanism for the AttNet model which is based on Petri nets and supports the distributed software processes.>