This is a collection of integrated programs.

It is subsists of carefully-organized instructions and code written by developers on any of various particular computer languages.

It is the application of scientific and practical knowledge to invent, design, build, maintain, and improve frameworks, processes, etc.

Have to analyze user needs, company necessities, budget, and the style to develop and implement a software system resolution that supports those demands.

It is an engineering branch related to the evolution of software product using well-defined scientific principles, techniques, and procedures. The result of software engineering is an effective and reliable software product.

Big software is always complicated and challenging to progress. Software engineering has a great solution to reduce the complication of any project. Software engineering divides big problems into various small issues. And then start solving each small issue one by one. All these small problems are solved independently to each other.

Software needs a lot of hardwork and software engineers are highly paid experts. A lot of manpower is required to develop software with a large number of codes.

Anything that is not made according to the project always wastes time. And if you are making great software, then you may need to run many codes to get the definitive running code.

Big projects are not done in a couple of days, and they need lots of patience, planning, and management.

Software should be secure, means if you have delivered the software, then it should work for at least its given time or subscription

It comes if anything has made according to the standards.

It is the set of activities and associated outcome that produce a software product. Software engineers mostly carry out these activities.

The functionality of the software and constraints on its operation must be defined.

The software to meet the requirement must be produced.

The software must be validated to ensure that it does what the customer wants.

The software must evolve to meet changing client needs.

This is a specified definition of a software process, which is presented from a particular perspective.

This shows the series of activities in the process along with their inputs, outputs and dependencies.

This represents the process as a set of activities, each of which carries out some data transformations.

This means the roles of the people involved in the software process and the activities for which they are responsible

This takes the above activities and produces them as separate process phases such as requirements specification, software design, implementation, testing, and so on. After each stage is defined, it is "signed off" and development goes onto the following stage.

This method interleaves the activities of specification, development, and validation. An initial system is rapidly developed from a very abstract specification.

This method is based on producing a formal mathematical system specification and transforming this specification, using mathematical methods to a program.

This method assumes the parts of the system already exist. The system development process target on integrating these parts rather than developing them from scratch.

Software is becoming more expensive and more complex with the growing complexity and expectation out of software. For example, the code in the consumer product is doubling every couple of years.

Many software products have poor quality, i.e., the software products defects after putting into use due to ineffective testing technique. For example, Software testing typically finds 25 errors per 1000 lines of code.

Software development is costly i.e. in terms of time taken to develop and the money involved. For example, Development of the FAA's Advanced Automation System cost over $700 per lines of code.

Serious schedule overruns are common. Very often the software takes longer than the estimated time to develop, which in turn leads to cost shooting up. For example, one in four large-scale development projects is never completed.

______ is more than programs. Any ______ is a subset of software, and it becomes software only if documentation & operating procedures manuals are prepared.

It is a combination of source code & object code.

It is consists of different types of manuals. Examples of documentation manuals are: Data Flow Diagram, Flow Charts, ER diagrams, etc.

It consist of instructions to set up and use the software system and instructions on how react to the system failure.

It (also termed process model) is a pictorial and diagrammatic representation of the software life cycle.

It is a spiritual model used in project management that defines the stages include in an information system development project, from an initial feasibility study to the maintenance of the completed application

It is a continuous software development model in which development is seen as flowing steadily downwards (like a waterfall) through the steps of requirements analysis, design, implementation, testing (validation), integration, and maintenance.

It is the process is an adoption of the waterfall model; it targets developing software in a short period.

It is similar to the iterative model in its emphasis on repetition. It goes through the planning, design, build and test phases over and over, with gradual improvements at each pass.

In this type of SDLC model testing and the development, the step is planned in parallel. So, there are verification phases on the side and the validation phase on the other side.

It is not a separate model. It is necessarily a series of waterfall cycles. The requirements are divided into groups at the start of the project.

It is a practice which promotes continues interaction of development and testing during the SDLC process of any project.

It is the entire project is divided into small incremental builds. All of these builds are provided in iterations, and each iteration lasts from one to three weeks.

It is a particular implementation of a software development life cycle that focuses on an initial, simplified implementation, which then progressively gains more complexity and a broader feature set until the final system is complete.

A model that is focusing on all types of resources in software development and coding, with no or very little planning. The requirements are understood and implemented when they come

It starts with the requirements gathering. The developer and the user meet and define the purpose of the software, identify the needs, etc.

It is the average time between repairable failures of a technology product.

It is the average time it takes to repair a system (usually technical or mechanical).

It is the average time it takes to recover from a product or system failure.

It is the average time it takes to fully resolve a failure.

It is the average time it takes to recover from a product or system failure from the time when you are first alerted to that failure.

It is the average time it takes from when an alert is triggered to when work begins on the issue. This metric is useful for tracking your team’s responsiveness and your alert system’s effectiveness.

It is a software quality assurance activity that focuses on the identify cation and assessment of potential hazards that may affect software negatively and cause an entire system to fail.

It is important to note that MTBF and related measures are based on ______, not wall clock time.

It describes quality assurance elements in generic terms that can be applied to any business regardless of the products or services offered.

Hardware fails because of design and manufacturing errors or because components have reached the end of their natural life.

Software fails due to errors in its specification, design or implementation.

Human operators make mistakes. Now perhaps the largest single cause of system failures in socio-technical systems.

The probability that the system will be up and running and able to deliver useful services to users.

The probability that the system will correctly deliver services as expected by users.

A judgment of how likely it is that the system will cause damage to people or its environment.

A judgment of how likely it is that the system can resist accidental or deliberate intrusions.

A judgment of how well a system can maintain the continuity of its critical services in the presence of disruptive events such as equipment failure and cyberattacks.

It reflects the extent to which the system can be repaired in the event of a failure.

It reflects the extent to which the system can be adapted to new requirements

It reflects the extent to which the system can deliver services whilst under hostile attack.

It reflects the extent to which user input errors can be avoided and tolerated.

it is a hardware devices, some of which may be computers; most devices will include an embedded system of some kind.

It provides a set of common facilities for higher levels in the system.

ü  Communications and data management: middleware that provides access to remote systems and databases.

It is a specific functionality to meet some organization requirements.

It is a set of processes involving people and computer systems that support the activities of the business.

It is a higher level strategic business activities that affect the operation of the system.

It laws, regulation and culture that affect the operation of the system.

These are properties of the system as a whole rather than properties that can be derived from the properties of components of a system.

It is system (the total space occupied) varies depending on how the component assemblies are arranged and connected.

It depends on component reliability but unexpected interactions can cause new types of failures and therefore affect the reliability of the system.

It is a complex property that cannot be easily measured. Attacks may be devised that were not anticipated by the system designers and so may defeat built-in safeguards.

This property reflects how easy it is to fix a problem with the system once it has been discovered.

This property reflects how easy it is to use the system. It depends on the technical system components, its operators, and its operating environment.

This is the type of emergent properties that appear when all the parts of a system work together to achieve some objective.

These relate to the behavior of the system in its operational environment. They are often critical for computer-based systems as failure to achieve some minimal defined level in these properties may make the system unusable.

To keep more than a single version of critical components so that if one fails then a backup is available.

It provide the same functionality in different ways in different components so that they will not fail in the same way.

This is one that does not depend entirely on individual skills; rather can be enacted by different people.

A process that has a defined process model that is used to drive the software production process.

A process that does not rely on individual interpretation and judgment.

This is where a mathematical model of the software is created and analyzed.

This is where the software design is explicitly documented as a set of graphical models, and the links between the requirements and these models are documented.

This is where the different descriptions of the system are inspected and checked by different people.

This is where automated checks are carried out on the source code of the program.

This is where a comprehensive set of system tests is designed.

It is often requires certification so both process and product documentation has to be produced.

It is also essential to discover requirements and requirements conflicts that may compromise the safety and security of the system.

It may be defined that incorporates techniques such as iterative development, test-first development and user involvement in the development team.

It is defined as the set of reachable and exploitable vulnerabilities present in a software product.

It is a routine part of system testing.

It spells out the actions to be carried out by each system stakeholder in response to specific attacks.

It is a set of activities that can be planned in advance and conducted systematically.

It is a documents to the software team’s approach to testing by defining a plan that describes an overall strategy and a procedure that defines specific testing steps and the types of tests that will be conducted.

It refers to the set of tasks that ensure that software correctly implements a specific function.

It refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements.

It is a process compromises of the verification and validation process of the software code.

It begins at the culmination of integration testing, when individual components have been exercised, the software is completely assembled as a package, and interfacing errors have been uncovered and corrected.

It is achieved through a series of tests that demonstrate conformity with requirements.

It is an important element of the validation process is a ______.

It can be conducted over a period of weeks or months, thereby uncovering cumulative errors that might degrade the system over time.

It is conducted at the developer’s site by a representative group of end users.

It is conducted at one or more end-user sites.

It is a variation on beta testing that is sometimes performed when custom software is delivered to a customer under contract.

It is generally used by developers as part of the development and component testing process.

It consists of a set of programming rules, naming conventions (e.g., Classes should start with capital C) and layout specifications (e.g., Indent 4 spaces towards right).

It is basically the measurement of depth of nesting, cyclomatic number and number of lines of code.

It tells us about the effort required to write the code in the first place, to understand the code while making the change, or to test the code using tools or techniques.

It addresses the sequence in which the instructions are executed.

It follows the track of the data item as it is accessed and modified by the code.

It refers to the organization of the data itself, independent of the program.

Repetitive work is very boring if it is done manually. People tend to make mistakes when doing the same task over and over.

People have tendency to do the same task in a slightly different way even when they think they are repeating something exactly.

If a person calculates a value from the software or incident reports, by mistake they may omit something, or their own one-sided preconceived judgments or convictions may lead them to interpret that data incorrectly.

Information presented visually is much easier for the human mind to understand and interpret.

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

It is made up of interacting objects that maintain their own local state and provide operations on that state.

This processes involve designing object classes and the relationships between these classes.

The models present complementary views of the relationships between a system and its environment.

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

It is a dynamic model that shows how the system interacts with its environment as it is used.

It is derived from ideas put forward by Christopher Alexander (Alexander et al., 1977), who suggested that there were certain common patterns of building design that were inherently pleasing and effective.

Most modern software is constructed by reusing existing components or systems.

During the development process, many different versions of each software component are created.

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

At this level, you don’t reuse software directly but rather 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.

These are collections of objects and object classes that operate together to provide related functions and services.

At this level, you reuse entire application systems. This usually involves some kind of configuration of these systems.

It is the name given to the general process of managing a changing software system.

It is provided to keep track of the different versions of software components.

It is provided to help developers define what versions of components are used to create each version of a system.

It is provided to allow users to report bugs and other problems, and to allow all developers to see who is working on these problems and when they are fixed.

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

If a component is designed for a specific hardware architecture, or relies on some other software system, it must obviously be deployed on a platform that provides the required hardware and software support.

High-availability systems may require components to be deployed on more than one platform. This means that, in the event of platform failure, an alternative implementation of the component is available.

If there is a high level of communications traffic between components, it usually makes sense to deploy them on the same platform or on platforms that are physically close to one other.

It 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 (Raymond, 2001).

This is the best-known open source product which is widely used as a server system and, increasingly, as a desktop environment.

This is a so-called ‘reciprocal’ license that, simplistically, means that if you use open source software that is licensed under the GPL license, then you must make that software open source.

This is a variant of the GPL license where you can write components that link to open source code without having to publish the source of these components.

It is a process of executing a program with the intent of finding an error.

It is one that uncovers an as-yet-undiscovered error.

It is one that has a high probability of finding an as-yet undiscovered error.

This is a non-reciprocal license, which means you are not obliged to republish any changes or modifications made to open source code.

A method of identifying the possible causes of a system failure.

It refers to the design and analysis of software systems that are required to respond to events or inputs within strict timing constraints.

They are devoted to quality management.

It is the average time between non-repairable failures of a technology product

It is the ratio of time a system or component is functional compared to the total time it is required or expected to function.