High-Level Language Programming Paradigms Flashcards
Low-level Lang
Machine-oriented, usually one instruction to one machine code instruction, mnemonics for operations, labels for addresses.
Low-level Lang Use
For coding device drivers, embedded systems where processing capabilities and memory capacity are limited.
Object-oriented Lang
Solution for a problem can be visualised in terms of objects that interact passing messages back and forth. Classes & objects.
Object-oriented Lang Use
For producing re-usable code and use in large software projects where data and the methods acting on are kept together.
Declarative Lang
Program consists of facts and rules. States what is required but not how to do it. Statements not needed in specific order.
Declarative Lang Use
Expert systems (knowledge based systems) e.g. medical diagnosis. Also Artificial Intelligence and Pattern Recognition.
Procedural Lang
Imperative language, uses sequence, selection, iteration, procedures and functions. States what to do and how to do it.
Procedural Lang Use
Used for set tasks that need to be completed in a specific way. E.g. stock control.
Data encapsulation (OOL)
Data is hidden. Data can only be accessed using the operations defined for the class. This maintains data integrity.
Class (OOL)
A template for a set of objects that have state and behaviour.
Object (OOL)
An object is an instance of a class. It is a real-world entity and holds attributes and operations.
Derived Class (sub class) (OOL)
A class that has all the attributes and operations of its superclass and may have attributes and operations of its own.
Inheritance (OOL)
A derived class inherits all the attributes and operations from its superclass.
UML
Standard way to present the design of a system. Visual, so easy to understand. Allows analysts, programmers and clients to communicate. Makes system maintenance easier when modifying a system.
Class diagram (UML)
Describes the classes to achieve the tasks that the system must perform and the relationships between them.
Object diagram (UML)
Shows the individual attributes of a specific object from a class and the operations including parameter values / return value that are active at that specific point in time. Shows association between objects with lines.
Use case diagram (UML)
Describes the tasks which the system must help to perform. Describes the requirements of a system.
State diagram (UML)
In order to implement, maintain or test a class we need to understand what the dependencies are between the state of an object and its reactions to messages or other events.
Sequence diagram (UML)
A type of interaction diagram. Describe record in detail how objects interact to perform a task. Shows the objects [and actors] which take part in a collaboration at the top of dashed lines
Activity diagram (UML)
Activity diagrams describe how activities are co-ordinated. For example, an activity diagram could be used to show how an operation could be implemented. They are also useful for describing use cases in detail.
Communication diagram (UML)
A type of interaction diagram. Also known as a collaboration diagram. Describe record in detail how objects interact to perform a task. Show the order of messages / signals passed between the linked objects.
Backtracking (Dec. Langs)
Going back to a previously found successful match in order to continue a search.
Instantiation (Dec. Langs)
Giving a value to a variable in a statement.
Predicate Logic (Dec. Langs)
A branch of mathematics that manipulates logical statements that can be either True or False.
Variable (Dec. Langs)
Is written as a sequence of letters and digits, beginning with a capital letter (or underscore). E.g. A, Male, _male
Satisfying goals (Dec. Langs)
A goal is a statement we are trying to prove either True or False.
