Pervasive software development method

Abstract

Software development methods aim at solving the software crisis. Many presented methods gain reputations under special application environments. There are so many kinds of methods that developers are troubled when choosing the most suitable one. This article presents a pervasive software development method aiming at helping developers deal with the trouble. The pervasive method advocates logicality, comprehensiveness, flexibility and self-improvement as development guidelines. Logicality consists of business logic, functional logic and data logic; comprehensiveness clarifies advantages and shortcomings for a development; flexibility benefits developers in a variable or uncertain environment;self-improvement assures selection suitability to development processes and tools. The article compares solutions by the object-oriented method and the pervasive method in a web application as a paradigm. The paradigm shows that the pervasive method helps to decrease development cost.

Increasing Distributed IT&C Application Security

“…The software application lifecycle starts with the decision of meeting an organization, group or individual's demands through the development of task-specialized tools that improve on productivity by the direct or indirect management of economic, social, educational or cultural interactions over uncertain output generation [1], [2]. The procedure of determining the functional needs that turn into specifications in the development of software applications includes the following steps:  observation, awareness of deficiencies in operations or interactions which occur in the processes that characterize human activities; delays in processing a collaborator's request, unavailability of communication, need of computation power in reducing resource spending, lack of the tools by which to disseminate and exchange ideas or capability to homogenously acquire data, satisfaction of an individual or group's social aspirations, extending an already functioning process or improving its results or consequences, all constitute factors to be addressed as part of today's informational society; the source of the observation is usually the beneficiary of the final product, yet software development companies meet demand by trying to discover and describe patterns and tendencies in target consumer area [3]; this approach leads to the building of extensive information warehouses, market studies and also the appearance of discrepancies between predicted and observed results which translate to risks;  executive decisions which lead to the initiation of procedures regarding the construction or acquisition of tools designed to achieve the desired behavior and containing the required set of functions in mediating operational activities; this role belongs to either the party experiencing the lack of resources or to individuals or organizations that act as service providers; the conclusion of this step involves the assignment of analysis, development and testing resources, either external or internal as relating to the beneficiary of the software and clarification of roles each party involved plays in the completion of the application building tasks;  formalization of user requirements, by producing documents and schematics which help model the interactions between components of the system, its users and elements outside the context of the application; in the area of collaborations between the teams involved in the development of an application, differences in training and understanding of functional aspects at one end, alongside the technical details DOI: 10.12948/issn14531305/17.2.2013.13 reliance on the other lead to the gradual abstracting of requirements as intermediate actors translate needs into software development constructs; the specifics of the activity set that the software system will manage may not require direct input or control, yet the end result is always related to the improvement of human activities;  defining application limitations as relating to the proportion in which it mediates or successfully replace inferior productivity factors, action related to the mapping of user requirements and identifying the boundaries that the system will set on the extent in which human activities or outdated processes are transferred to the new functionalities [4]; the understanding of limits helps management plan for future extensions, as well as users and business analysts in the identification of operations and training for interacting with the new solution. Actors involved in DIA functional analysis are tasked with the mapping of the desired behavior to documents and analytical tools, as well as with passing the translated information to subsequent parties involved in the design and development of the distributed application.…”