OBJECT-ORIENTED PROGRAMMING IN JAVA

Computers are tools for manipulating and analyzing information. Computer programs are the means for specifying what actions a computer performs. This chapter will look at a simple computer program. Some specific elements covered are: ✓ High-level computer languages ✓ Compiled vs. interpreted languages ✓ A simple C++ program ✓ Specifying variables ✓ Assignment and mathematical operations Programming Languages Computers are among the most complex artifacts made by humans and are comprised of billions of distinct elements. Direct control of such complexity is beyond our abilities. Instead, computer programming relies upon the principal of abstraction to allow us to specify what actions a computer should perform. Abstraction Abstraction is the pruning away of complexity resulting in a simplified mental model of a process. For example, the driver of a car is not required to understand the mechanics of a car engine in order to drive. As long as there is a mental model that the gas pedal makes the car go faster, the brake slows the car, and the steering wheel makes the car turn, a driver can be reasonably effective. Note that this mental model is not really correct – pressing the gas provides torque to the wheels, which may or may not accelerate the car. This example highlights one danger of abstraction; in unusual situations, the simplified model may provide incorrect predictions. For this reason, computer programming practitioners should have some understanding of how computers operate as well as detailed knowledge of the programming language.

Advances in Software Engineering, 2008

The nature of software engineering is discussed with particular reference to softwareintensive application systems-those whose fundamental purpose is to bring about desired effects in a physical and human problem world by interaction with a programmed machine. Such systems bring together a problem world-which is typically composed of heterogeneous domains, most of which are non-formal-and the formal or semi-formal domain of the machine. A clean engineering separation of the two is rarely, if ever, possible; and attempts to treat the application problem world as an extension of the formal machine are obstructed by its non-formal nature. Software engineers have much to learn from the structure and practices of the established branches of engineering. We must learn from their treatment of formal analysis and reasoning, from their practice of intense specialisation, from their attention to particular instances no less than to general concerns, and-above all-from their reliance on normal artifact design and on normal design disciplines: both are the golden fruit of specialisation.

Communications in computer and information science, 2011

The use of general descriptive names, registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.

RESET

ArXiv, 2021

Computer programs are part of our daily life, we use them, we provide them with data, they support our decisions, they help us remember, they control machines, etc. Programs are made by people, but in most cases we are not their authors, so we have to decide if we can trust them. Programs enable computers and computer-controlled machines to behave in a large variety of ways. They bring the intrinsic power of computers to life. Programs have a variety of properties that all citizens must be aware of. Due to the intangible nature of programs, most of these properties are very unusual, but important to understand the digital world. In this position paper, we describe the Nature of Programs in the form of knowledge statements, accompanied by examples from everyday life to clarify their meaning. Everything is formulated in an easily understandable manner and avoids obscure technical language. We suggest that these knowledge statements must be imparted to all teachers and school students....

2012

This article reports on a learning experience that was designed to investigate the extent to which a learning event would draw from both objectivist and constructivist traditions to provide learners with real-world projects so that they can construct their own programmes in collaboration with other individuals and develop new ideas for future systems. The study was done because the current South African curriculum for high school Computer Studies, in our opinion, is weak on higher order thinking skills. An experimental lesson was presented to high school learners, and monitored to determine the extent to which a learning experience could be designed using predominantly objectivist methods, but presented in a constructivist fashion. The evaluation showed that the lesson was successful. Learners scored better in their year-end results than previous years, and indicated that they enjoyed the real-world style. Using techniques developed for this lesson should help learners to do real world programming, and this would narrow the gap between school/university and the real world. Some recommendations for curriculum design emerge.

Q: Prove that software engineering is a layered technology with proper diagram. A: Software engineering is a layered technology. Referring to the above figure, any engineering approach (including software engineering) must rest on an organizational commitment to quality. Total quality management, Six Sigma, and similar philosophies foster a continuous process improvement culture, and it is this culture that ultimately leads to the development of increasingly more effective approaches to software engineering. The bedrock that supports software engineering is a quality focus. The foundation for software engineering is the process layer. The software engineering process is the glue that holds the technology layers together and enables rational and timely development of computer software. Process defines a framework that must be established for effective delivery of software engineering technology. The software process forms the basis for management control of software projects and establishes the context in which technical methods are applied, work products (models, documents, data, reports, forms, etc.) are produced, milestones are established, quality is ensured, and change is properly managed. Software engineering methods provide the technical how-to's for building software. Methods encompass a broad array of tasks that include communication, requirements analysis, design modeling, program construction, testing, and support. Software engineering methods rely on a set of basic principles that govern each area of the technology and include modeling activities and other descriptive techniques. Software engineering tools provide automated or semi-automated support for the process and the methods. When tools are integrated so that information created by one tool can be used by another, a system for the support of software development, called computer-aided software engineering, is established. Q: State and discuss various process models with their applications. A: A generic process model for software engineering encompasses a set of framework and umbrella activities, actions, and work tasks. Each of a variety of process models can be described by a different process flow—a description of how the framework activities, actions, and tasks are organized sequentially