COMPUTER,Software,Software engineering,Software development process,Systems development life cycle,Object-oriented modeling,Unified Process,Object-oriented analysis and design,Bitwise operation,Assembly language,High-level programming language,Arithmetic logic unit,Status register,High-level programming language,Modeling language,Unified Modeling Language,Data modeling,Class,Object,Class diagram,Object diagram,Systems Modeling Language,Use case,Use Case Diagram,
Activity diagram,Hierarchy of UML 2.5 Diagrams,Structural Diagram,Class Diagram,Object Diagram,Component Diagram,Deployment Diagram,Behavioral Diagram,Use case Diagram,Sequence Diagram,Collaboration Diagram,
Statechart Diagram,Activity Diagram
Statechart Diagram,Activity Diagram
COMPUTER
Full Form of COMPUTER is Common Operating Machine Particularly Used for Trade, Education, and Research
ENIAC - the first electronic general-purpose computer
A computer is a device that can be instructed to carry out an arbitrary set of arithmetic or logical operations automatically. Their ability of computers to follow a sequence of operations, called a program, make computers very flexible and useful. Such computers are used as control systems for a very wide variety of industrial and consumer devices. This includes simple special purpose devices like microwave ovens and remote controls, factory devices such as industrial robots andcomputer assisted design, but also in general purpose devices like personal computers and mobile devices such assmartphones. The Internet is run on computers and it connects millions of other computers.
Software
Computer software, or simply software, is that part of a computer system that consists of encoded information or computer instructions, in contrast to the physical hardware from which the system is built.
Software engineering
Software engineering is the application of engineering to the design, development, implementation, testing and maintenance of software in a systematic method.
Software development process
In software engineering, a software development methodology (also known as a system development methodology, software development life cycle, software development process, software process) is a splitting of software development work into distinct phases (or stages) containing activities with the intent of better planning and management. It is often considered a subset of the systems development life cycle. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.
Systems development life cycle
The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software engineering to describe a process for planning, creating, testing, and deploying an information system.The systems development life-cycle concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both.
Object-oriented modeling
Object-oriented modeling is an approach to modeling an application that is used at the beginning of the software life cycle when using an object-oriented approach to software development.
Unified Process
The Unified Software Development Process or Unified Process is a popular iterative and incremental software development process framework. The best-known and extensively documented refinement of the Unified Process is the Rational Unified Process (RUP). Other examples are OpenUP and Agile Unified Process
Object-oriented analysis and design
Object-oriented analysis and design (OOAD) is a popular technical approach for analyzing, designing an application, system, or business by applying the object-oriented paradigm and visual modeling throughout the development life cycles to foster better stakeholder communication and product quality.
Bitwise operation
In digital computer programming, a bitwise operation operates on one or more bit patterns or binary numerals at the level of their individual bits. It is a fast, simple action directly supported by the processor, and is used to manipulate values for comparisons and calculations.
On simple low-cost processors, typically, bitwise operations are substantially faster than division, several times faster than multiplication, and sometimes significantly faster than addition.
Assembly language
An assembly (or assembler) language, often abbreviated asm, is a low-level programming language for a computer, or other programmable device, in which there is a very strong (generally one-to-one) correspondence between the language and the architecture's machine code instructions. Each assembly language is specific to a particular computer architecture. In contrast, most high-level programming languages are generally portable across multiple architectures but require interpreting or compiling. Assembly language may also be called symbolic machine code.
Assembly language is converted into executable machine code by a utility program referred to as an assembler. The conversion process is referred to as assembly, or assembling the source code. Assembly time is the computational step where an assembler is run.
Arithmetic logic unit
An arithmetic logic unit (ALU) is a combinational digital electronic circuit that performs arithmetic and bitwise logical operations on integer binary numbers. This is in contrast to a floating-point unit (FPU), which operates on floating point numbers. An ALU is a fundamental building block of many types of computing circuits, including the central processing unit (CPU) of computers, FPUs, and graphics processing units (GPUs). A single CPU, FPU or GPU may contain multiple ALUs.
The inputs to an ALU are the data to be operated on, called operands, and a code indicating the operation to be performed; the ALU's output is the result of the performed operation. In many designs, the ALU also exchanges additional information with a status register, which relates to the result of the current or previous operations.
Status register
A status register, flag register, or condition code register is a collection of status flag bits for a processor. An example is the FLAGS register of the x86 architecture or flags in a program status word (PSW) register.
The status register is a hardware register that contains information about the state of the processor. Individual bits are implicitly or explicitly read and/or written by the machine code instructions executing on the processor. The status register lets an instruction take action contingent on the outcome of a previous instruction.
High-level programming language
In computer science, a high-level programming language is a programming language with strong abstraction from the details of the computer. In comparison to low-level programming languages, it may use natural language elements, be easier to use, or may automate (or even hide entirely) significant areas of computing systems (e.g. memory management), making the process of developing a program simpler and more understandable relative to a lower-level language. The amount of abstraction provided defines how "high-level" a programming language is.
Modeling language
A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.
Data modeling
Data modeling in software engineering is the process of creating a data model for an information system by applying formal data modeling techniques.
Class
In object-oriented programming, a class is an extensible program-code-template for creating objects, providing initial values for state (member variables) and implementations of behavior (member functions or methods). In many languages, the class name is used as the name for the class (the template itself), the name for the default constructor of the class (a subroutine that creates objects), and as the type of objects generated by instantiating the class; these distinct concepts are easily conflated.
Object
In computer science, an object can be a variable, a data structure, or a function or a method, and as such, is a location in memory having a value and possibly referenced by an identifier.
In the class-based object-oriented programming paradigm, "object" refers to a particular instance of a class where the object can be a combination of variables, functions, and data structures.
In relational database management, an object can be a table or column, or an association between data and a database entity (such as relating a person's age to a specific person).
Class diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling.The classes in a class diagram represent both the main elements, interactions in the application, and the classes to be programmed.
Object diagram
An object diagram in the Unified Modeling Language (UML), is a diagram that shows a complete or partial view of the structure of a modeled system at a specific time.
Systems Modeling Language
The Systems Modeling Language (SysML) is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems.
Use case
In software and systems engineering, a use case is a list of actions or event steps, typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system, to achieve a goal. The actor can be a human or other external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements.
Use Case Diagram
A use case diagram at its simplest is a representation of a user's interaction with the system that shows the relationship between the user and the different use cases in which the user is involved. A use case diagram can identify the different types of users of a system and the different use cases and will often be accompanied by other types of diagrams as well.
Activity diagram
Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams are intended to model both computational and organizational processes (i.e. workflows). Activity diagrams show the overall flow of control.
Activity diagrams are constructed from a limited number of shapes, connected with arrows.
The most important shape types are
rounded rectangles represent actions,
diamonds represent decisions,
bars represent the start (split) or end (join) of concurrent activities,
a black circle represents the start (initial state) of the workflow,
an encircled black circle represents the end (final state),
Arrows run from the start towards the end and represent the order in which activities happen.
Hierarchy of UML 2.5 Diagrams
Structural Diagram
The structural diagrams represent the static aspect of the system. These static aspects represent those parts of a diagram which forms the main structure and therefore stable.
Class Diagram
Class diagrams basically represent the object oriented view of a system which is static in nature.
Object Diagram
Object diagrams are a set of objects and their relationships just like class diagrams and also represent the static view of the system.
Component Diagram
Component diagrams represent a set of components and their relationships. These components consist of classes, interfaces or collaborations.Component diagrams represent the implementation view of a system.
Deployment Diagram
Deployment diagrams are a set of nodes and their relationships.
Behavioral Diagram
Behavioral diagrams basically capture the dynamic aspect of a system.
Use case Diagram
Use case diagrams are a set of use cases, actors and their relationships. They represent the use case view of a system.
Sequence Diagram
Sequence diagram is used to visualize the sequence of calls in a system to perform a specific functionality
Collaboration Diagram
collaboration diagram is to visualize the organization of objects and their interaction.
Statechart Diagram
State chart diagram is used to visualize the reaction of a system by internal/external factors.
Activity Diagram
Activity diagrams are used to visualize the flow of controls in a system.
trending keywords on this topic / related keywords / trending hashtags
OBJECT ORIENTD MODELLING AND DESIGN
Object Oriented Programming and Design Principles
Object Oriented Concepts
Nature and purpose of models
Object Modeling
Dynamic Modeling
Functional Modeling
System Design-
Object Design
UML Structural Modeling:
Basics of UML based object oriented analysis and design
Classes
Relationships
Interfaces
Roles
Class diagrams
Advanced classes and relationship
Packages
Instances
Object diagrams
UML Behavioral Modeling:
Interactions
Use cases
Interaction diagrams
Use case diagrams
Activity diagrams
Events
Signals
State Machines
Processes
Threads
State chart diagrams
UML Architectural Modeling
Component diagrams
Deployment diagrams
Collaborations
Unified Processes
Introduction to Software Architecture:
Design frameworks
Design pattern
Describing the architecture in Architecture description language (ADL)
Hierarchy of UML 2.5 Diagrams
Structural Diagram
Class Diagram
Object Diagram
Component Diagram
Deployment Diagram
Behavioral Diagram
Use case Diagram
Sequence Diagram
Collaboration Diagram
Statechart Diagram
Activity Diagram
Structural Diagram
Class Diagram
Object Diagram
Component Diagram
Deployment Diagram
Behavioral Diagram
Use case Diagram
Sequence Diagram
Collaboration Diagram
Statechart Diagram
Activity Diagram
No comments:
Post a Comment