An Ameliorated Methodology for the Abstraction of Object Oriented Features from Software Requirements Specification

AbstractThe Business Process (BP) requirements is specified in the form of software requirements specification (SRS). This SRS serves as a base for software development. The software needs to be developed in a syllogized software development life cycle (SDLC) stages. The SRS which denote the requirements of BP is used as input to the analysis stage from which the paradigm dependent components are to be abstracted. Hither to the components are abstracted manually with the exception of hiatuses of semi-automated methods for few of the components. The SRS is construed with reference to the specific paradigm through which the design is to be developed. Unfortunately, no complete automated methodology exists for the abstraction of all paradigm dependent components. The automated methodology eliminates the possible human errors which would have ripple effect to damage the entire software. This paper develops an innovative, unique methodology to resurrect the SRS statements as modular statements. Further develops an automated methodology for abstraction of control and data flow graphs. Further it develops an automated methodology for abstraction of useful components required for the class diagram. The class diagram emphasizes both structural and behavioral aspects. This facility is effectively used to abstract object class attributes, object methods, visibility, signature, return type etc.Information systems are developed through software projects which use the specific software requirements specification (SRS) provided for them as the base. The SRS contains details of the information system through which appropriate software can be developed. The information systems are also viewed perceptively with different pragmatics like work, work process or usecase. The usecase is one of the prime perspective views whose sum forms the information system. In this paper, an attempt is made to abstract object class, object class attributes, object methods, interrelationships between object classes and starting with/ending with actor from unformatted, unstructured SRS text. This is achieved through our own developed classing and slicing techniques to identify respectively the class structure & object methods. Then usecase is developed through the interrelationships between object methods of different classes and start with or end with the actor. The stages involve moulding the SRS, designing control flow graph for the SRS & data flow table for the SRS statements, developing appropriate classing and slicing criteria, creating actor & actors’ interface attributes table, create slicing criteria for each usecase and then slice relevant statements for each usecase. Here, we have attempted to use Weiser modified algorithm1 to abstract exact usecase. The slicing criterion is obtained through the intersection of actor's interface attributes and the referenced/defined attributes present between two consecutive actors. Attempts have been made to resolve synonyms & heteronyms present in the SRS. The correctness & completeness of the proposed methodology depends on the realization of actor & actors’ interface attributes

Integration of Object Oriented Host Program with Network DBMS

AbstractSeveral mapping techniques are in use for the storage of objects in Network Database Management System (NDBMS). Though there is a generation gap between the evolution of NDBMS and Object Oriented Technology (OOT), both are either analogous or complementary to each other. Therefore the mapping technique to map class diagram onto Bachman diagram has been evolved. Host program accessing the database and accessing the independent data file may differ in the number and use of attributes and classes. Hence along with the mapping techniques, the implementation subsets of structural and behavioral aspect are to be considered. Moreover, the persistent closure (connected dependent objects) is to be maintained during the storage and retrieval of the objects. Thus, the mere mapping technique is not sufficient for the storage and retrieval of objects as the host program has to establish the relevancy of the database with respect to its authorized subset. In this paper, we have made an attempt to develop a guidelines to assist the programmer to determine the closure of every mapped class and accordingly to design the persistent constructor and loader for the storage and retrieval of the objects respectively. The persistent closure is determined by the type of interrelationship (degree of cohesion) between objects (classes) is identified. For illustrative portion of the class diagram depicting the business process and its implementation in the NDBMS, a table containing the implemented classes with their connected classes is prepared, and then the guidelines are proposed to integrate object oriented host program to access the database through NDBMS

An Ameliorated Methodology to Abstract Object Oriented Features from Programming System

AbstractIn software testing through reverse engineering, the programming semiotics are to be transformed to Unified Modeling Language (UML) semiotics. This process needs the abstraction of UML syntactics, semantics from the programming system. As a preamble, this paper attempts to develop an automated methodology to abstract object oriented technology (OOT) components required for the class diagram from the programming system to be tested for its correctness & completeness. The methodology comprises of initial classing & slicing the programming system on the referenced attributes of the entry with no defined attributes and then using the sole referenced entry and sole defined entry on these sliced programming units the candidate key/s are identified which are used to find individual object structure of the class in our classing technique. The programming system is sliced based on individual class structure and then these slices are used to obtain the object methods through whose nature of the parameters we identify the interrelationship between the classes and their types. The intermediate clairvoyant study of parameter indicates the visibility of the object methods. This paper contains the detailed procedure for each method of our automated methodology. Therefore, their correctness and completeness is self evident. The proposed procedures are based on sound logical positivism and implicitly incorporate good database design and good software engineering principles. This paper reengineers the programming system into various appropriate UML design diagrams so as to reduce the enormity of the syntactics and semantics of programming language into limited syntactics and semantics. This enables to develop the correct and complete software testing methodology

The imprint of salivary secretion in autoimmune disorders and related pathological conditions

Xerostomia is a state of oral dryness associated with salivary gland dysfunction and is induced by stress, radiation and chemical therapy, various systemic and autoimmune diseases, and specific medications. Fluid secretion is interrupted by the stimulation of neurotransmitter-induced increase in cytosolic calcium ([Ca2+]i) in salivary gland acinar cells, prompting the mobilization of ion channels and their transporters. Salivary fluid and protein secretion are principally dependent on parasympathetic and sympathetic nerves. Various inflammatory cytokines allied with lymphocytic infiltration cause glandular damage and Sjogren's syndrome, an autoimmune exocrinopathy associated with hyposalivation. A defect in IP3Rs, a major calcium release channel, prompts inadequate agonist-induced [Ca2+]i in acinar cells and deters salivary flow. The store-operated calcium entry-mediated Ca2+ movement into the acini activates K+ and Cl- channels, which further opens a water channel protein, aquaporin-5, and triggers the release of fluid secretion from the salivary glands. The cellular mechanism of salivary gland dysfunction and hyposalivation has not yet been elucidated. In this review, we focused mainly on the proteins responsible for deficient saliva, the correlation between inflammation and salivation, autoimmune disorders and other ailments or complications associated with hyposalivation. © 2018 The Authors.1