is a structural model that demonstrates the other systems in the environment of the system being developed

is concerned with the architecture of complex enterprise systems that include other systems, programs, and program components

shows how the software is decomposed for development.

shows the key abstractions in the system as objects or object classes

shows how, at run-time, the system is composed of interacting processes

shows the system hardware and how software components are distributed across the processors in the system

is concerned with the architecture of individual programs. At this level, we are concerned with the way that an individual program is decomposed into components

localize critical operations and minimize communications. use large rather than fine-grain components

use a layered architecture with critical assets in the inner layers

localize safety-critical features in a small number of sub-systems

include redundant components and mechanisms for fault tolerance

use fine-grain, replaceable components

It accepts a natural or artificial language as input and generate some other representation of that language and may include an interpreter to act on the instructions in the language that is being processed. It is used in situations where the easiest way to solve a problem is to describe an algorithm or describe the system data

These systems are often implemented as multi-tier client server/architectures

Distributed system model which shows how data and processing is distributed across a range of components

Variants of this approach are very common. When transformations are sequential, this is a batch sequential model which is extensively used in data processing systems

takes input language tokens and converts them to an internal form

holds information about the names of entities used in the text that is being translated

checks the syntax of the language being translated

an internal structure representing the program being compiled

uses information from the syntax tree and the symbol table to check the semantic correctness of the input language text

'walks' the syntax tree and generates abstract machine code

used as a way of facilitating discussion about the system design and as a way of documenting an architecture that has been designed

is a stylized description of good design practice, which has been tried and tested in different environments

organizes the system into a set of layers (or abstract machines) each of which provide a set of services

are a means of representing, sharing and reusing knowledge. It may be represented using tabular and graphical descriptions

describe the dynamic interaction between objects

describe the static structure of the system in terms of object classes and relationships

show the objects and object classes and relationships between these entities

Production software does not usually execute on the same computer as the software development environment

Most modern software is constructed by reusing existing components or systems. When you are developing software, you should make as much use as possible of existing code

Many agile methods argue that producing a requirements document is a waste of time as requirements change so quickly.

During the development process, you have to keep track of the many different version of each software component in a ____ system

At this level, you don't reuse software directly but use knowledge of successful abstractions in the design of your software

At this level, you directly reuse objects from a library rather than writing the code yourself

collections of objects and object classes that you reuse in application systems

At this level, you reuse entire application systems

____ should be sufficiently abstract to be reused in different settings

are used to show how objects respond to different service requests and the state transitions triggered by these requests

uses class diagrams for interface specification but Java may also be used

IDE is an approach to software development in which the source code of a software system is published and volunteers are invited to participate in the development process

is an approach to software development in which the source code of a software system is published and volunteers are invited to participate in the development process

is a set of software tools that supports different aspects of software development, within some common framework and user interface

It includes the installed operating system plus other supporting software such as a database management system or an interactive development environment

show how sequence of object interaction

show logical groupings of objects into coherent subsystems

User requirements are statements in natural language plus diagrams of the services the system provides and its operational constraints.

The design process for identifying the sub-systems making up a system and the framework for sub-system control and communication is _____

The requirements themselves are the descriptions of the system services and constraints that are generated during the requirements engineering process.

The output of this design process is a description of the ______

is the stage in the software engineering process at which an executable software system is developed

Most software is developed on one computer (the ___), but runs on a separate machine

Most software is developed on one computer, but runs on a separate machine (the ___),

The results and trade-offs of applying the pattern

A meaningful pattern identifier

Not a concrete design but a template for a design solution that can be instantiated in different ways

Structured object-oriented design processes involve developing a number of different system models

From the 1990s to the 2000s, most new software was developed from scratch, by writing all code in high-lvel programming language

From the 1960s to the 1990s, most new software was developed from scratch, by writing all code in high-lvel programming language

Which of the following is/are true on inference specification?

Is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system.

System modeling is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system

Requirements engineering is the process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed

more detailed requirements and may include more technical information

User requirements have to be understandable by end-users and customers who do not have a technical background

As a way of documenting an existing system, models should be an accurate representation of the system but need not be complete

Use case diagrams and sequence diagrams may be used for interaction modeling

Sequence diagram shows the sequence of interactions that take place during a particular use case or use case instance

These define system properties and constraints e.g. reliability, response time and storage requirements

Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations

are constraints on the system from the domain of operation

Tool support are tools that may be used range from specialist requirements management systems to spreadsheets and simple database systems

May be used range from specialist requirements management systems to spreadsheets and simple database systems

must be uniquely identified so that it can be cross-referenced with other requirements

set of activities that assess the impact and cost of changes

define the relationships between each requirement and between the requirements and the system design that should be recorded

is the process of managing changing requirements during the requirements engineering process and system development

concerned with demonstrating that the requirements define the system that the customer really wants

During this stage, the problem or the change proposal is analyzed to check that it is valid. This analysis is fed back to the change requestor who may respond with a more specific requirements change proposal, or decide to withdraw the request

The effect of the proposed change is assessed using traceability information and general knowledge of the system requirements. Once this analysis is completed, a decision is made whether or not to proceed with the requirements change

The requirements document and, where necessary, the system design and implementation, are modified. Ideally, the document should be organized so that changes can be easily implemented

show the sequence of actions involved in processing input data and generating an associated output

shows how classes that are collections are composed of other classes.

models of the dynamic behavior of a system as it is executing. They show what happens or what is supposed to happen when a system responds to a stimulus from its environment

show the activities involved in a process or in data processing

show the interactions between a system and its environment

show the interactions between actors and the system and between system components

Activity diagrams show the interactions between a system and its environment.

is a link between classes that indicates that there is some relationship between these classes.

show the object classes in the system and the associations between these classes

show how the system reacts to internal and external events

Class diagrams show how the system reacts to internal and external events

These are transformations of the platform-independent model

These model the operation of the system without reference to its implementations. It usually described using UML models that show the static system structure and how it responds to external and internal events

These model the important domain abstractions used in a system. sometimes called domain models

shows how a system responds to external and internal events

show system states as nodes and events as arcs between these nodes. When an event occurs, the system moves from one state to another

an integral part of the UML and are used to represent state machine models

an approach to software development where models rather than programs are the principal outputs of the development process

Functional Requirements describe functionality or system services

A model-focused approach to software design and implementation that uses a subset of UML models to describe a system. It was the precursor of more general model-drive engineering

used to illustrate the operational context of a system - they show what lies outside the system boundaries

May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called _____.

Structured specifications is an approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way

Does the system provide the functions which best support the customer's needs?

Are there any requirements conflicts?

Are all functions required by the customer included?

Can the requirements be implemented given available budget and technology?

Can the requirements be checked?

Which of the following is not included in requirement checking?