The Description Of Developing Software From An Abstract Perspective

Software development is done by software programmers

. Since this is a human activity, it exhibits a number of aspects. It can be analyzed from different view points. Social scientists examine interactions between developers and clients. On the other hand, trade unionists and lawyers view software systems as a way of changing the way we work. Business theorists check development projects for profitability and Return on Investment (ROI).

The task of software developers is to create clear descriptions of complex systems. This is true of all kinds of software developers the world over- be it a Java programmer Sydney professional, a ASP.NET programmer Sydney professional and even a low cost database programmer sitting in front of his or her computer in any part of the world. Emphasis is laid on description compared to invention, on structure compared to calculation and on achieving obvious clarity in contrast to making proofs of opaque truths.

Software development can be explained as a description. The aim of this particular activity is to construct a machine. In the core of every system is a machine. If it is a distributed system, there will be multiple machines. The end product will be tangible and not a mathematical abstraction.

The basic rule of methodology is the proportionate method rule. The scale of the method must be in proportion to the scale of the problem. For software development, the program will be written in the programming language that is available. For slightly complex tasks, the program itself is structured. If the problem becomes more complex, the subject matter must be examined.

A description can be given to the subject matter. This description can be found out by simply reading the program texts. The machine deals with the environment where the problem is situated. The interaction can be seen as an interface of phenomena that is shared.

However, the interface between the machine and its environment is opaque. In an administrative system, the interface consists of a complex structure of software and hardware. Events and states of domain are not shared with the machine, but are found to be unreliably transmitted and with considerable delay. The modeling justification is also imperfect.

A distinction between requirements, specifications and programs can be made at this stage. A requirement is situated in the problem domain. The problem domain is different from the machine domain. It is the area where the client of the software will experience, interpret and evaluate the effects that are brought on by the machine. A requirement is not a vague or informal specification. It can be as formal as wanted.

In comparison, a specification is a description of the machine itself. It explains the properties that the machine must have to satisfy the requirement. The specification is usually considered to be a more abstract description of the machine compared to a program. According to experienced software developers, to solve a problem, it is required to fit into a tighter conceptual framework. Such a framework is termed as a Problem Frame.

by: Aaron Hunter

POST COMMENT

School Management System College Management Software Graphic Design Software - The Battle Major Benefits Of Customer Relationship Management Software A Cut Above The Rest Canada Accounting Software The Versatility Of E-discovery Software Resource Management Software For Wholesale Companies Where To Buy Truck Diagnostic Software Partnering With An Offshore Software Development Firm Easy Documents Handling With E-discovery Software Video Conferencing Software With Support For Scalable Video Coding (svc) & Vp8 Codec Tech Support For Your Property Management Software Open Source Development India For Reliable Custom Software Solutions Additional Features Of Surveillance Software