Software Engineering Flashcards

This document provides flashcards related to Software Engineering concepts. The flashcards cover topics such as software development models, testing strategies, design principles, and other key concepts in software engineering.

Software Engineering

A branch of computer science that deals with the design, development, testing, and maintenance of software applications.

Modularity

Breaking software into smaller, reusable components that can be developed and tested independently.

Abstraction

Hiding the implementation details of a component and exposing only the necessary functionality to other parts of the software.

Encapsulation

Wrapping up the data and functions of an object into a single unit and protecting the internal state of an object from external modification.

Reusability

The ability to reuse existing components in multiple applications, saving time and resources.

Maintenance

Updating and improving the software to fix bugs, add new features, and address security vulnerabilities.

Testing

Verifying that the software meets its requirements and is free of bugs.

Design Patterns

Solving recurring problems in design by providing templates for them.

Continuous Integration & Deployment

Continuously integrating code changes and deploying them into the production environment.

Functionality

The ability of the software to perform its intended tasks or functions, including calculations, data processing, and user interface interactions.

Reliability

Related to the ability of the software to perform consistently and predictably under various conditions.

Usability

Focuses on how easy and intuitive it is for users to interact with the software, including user interface design and accessibility.

Efficiency

Refers to the software's ability to perform tasks quickly and with minimal resource usage, including optimizing algorithms and reducing unnecessary overhead.

Maintainability

Measures how easy it is to maintain and update the software over its lifecycle, including code readability and modularity.

Portability

Refers to the software's ability to run on different platforms or environments without major modifications, including consideration for operating systems and hardware architecture.

Software Crisis

Refers to a set of challenges and issues that arise in the development and maintenance of software systems, often leading to delays and budget overruns.

Software Engineering

A process that majorly involves science, information technology, and discrete mathematics, building applications with complex logic and algorithms.

Conventional Engineering

A process that majorly involves mathematics and empirical knowledge, building cars and buildings, applying well-known and tested principles.

S.D.L.C.

Stands for Software Development Life Cycle; a process used by the software industry to design, develop, and test high-quality software.

Requirement and Planning Analysis

The first phase of SDLC, focusing on collecting necessary information from the customer to develop software as per their expectations.

Defining and Feasibility Study

The second phase of SDLC, discussing the costs and benefits of the software; impacts the profit the company recognizes.

Design

The third phase of SDLC in which architects start working on the logical designing of the software and SRS is created.

Coding and Building

The fourth phase of SDLC; a group of developers start coding the design using a programming language.

Testing

The fifth phase of SDLC is when testers are sent to the software; the software is checked for bugs and errors.

Deployment and Maintenance

The sixth phase of SDLC is when testing is complete and the software is live and big free; it is now launched and available for users to use.

Water Fall Model

A simple SDLC model in which phases are organized in a linear and sequential order, resembling a waterfall.

PROTOTYPE MODEL

An iterative approach involving an early working model of requirements with limited functionalities; the feedback is re-built until satisfactory.

PIRAL MODE

A combination of the waterfall model and iterative model and is known as meta model.

EVOLUTIONARY DEVELOPMENT ME

A combination of the iterative and incremental model; the model first implements a few basic features and delivers this to the user.

ITERATIVE ENHANCEMENT MODEL

A model in which you can start with some of the software specifications and develop the first software version.

Software Quality Attributes

Features which facilitate measurement of the performance of a software product by software and testing professionals.

Correctness

A software or system is said to be correct if it behave according to its functional requirement.

Reliability

A system is said to be reliable if it gives desired output even in undesirable condition like hardware or in case of overload.

Robusthess

Explains how a behavior in situtation of incorrect input, vague or powering failure.

Interoperability

Describes the ability of two system to engage in the face of Reformation via contain menu.

Efficiency

The ability of software system fulfill it purpose with best possible utilization of necessary resources (time, storage…).

Security

The software's ability to protect against unauthorized access, data breaches, and other potential threats.

Portability

The property of the software to operate on different platforms or environments without significant modification.

Modularity

The degree to which the software is organized into components or units that separate, manageable, and independently developed or updated.

Testability

The ease with which software can be tested to insure it meets it requirement and performs as expectancy.

Requirement Engineering Process

Refers to the process of defining, documenting, and maintaining requirement in the engineering design process.

Requirement Elicitation

Also known as gathering of requirement related to the various way used to gain about the project domain and require-ments.

Requirement document

This is the end and product of requirement elicitation and analysis.

Requirement review

It process is carried out to improve the quality of the SRS.

Requirement Elicitation

Is the activity during requirements are discovered and revealed from the system.

Brain Storming

Kind of group discussion, which lead to creative ideas.

FAST (faciliated application specification technique).

Encourage the coration of joint team of customer and developer.

Use care approach

Are structured description of the user requirement.

Prototypina

This technique involves creceting model of the software system.

Feasibility Study

A feasibility study specifices whether the proposed software project is practically possible or not.

Economic Feasibility

Decides whether the necessary software can generate profits for an organization.

Schedule Feasibility

Analized for proposals project, how match time the Deadlines.

In this phase Requirement analysis all the Set of requirements analysis

find any inconsistency or conflicts

Data Flow Diagram

Graphical representation of the flow of data within a system.

Piral model

Each phase in spiral model begins with a design goal review with a review the progress.

In Developing the prototype

Helps in building actual design.

Advantage of Model

A software engineer to get high precision and accuracy

Accurate Dimension

High precision and accuracy

In iterative Implementation.

This phase is to to check the behaviour and validity of the project.

Coupling and cohesion

These are two parameter on which we can the design of the project Quality.

module

That is the coupling increases as the number of calls between the Module increase.

Date Coupling

This is call the module from passing the one Date variable to another.

Module communication

If the modules are communication by passing the Control information, the set by to Couplers.

Content Coupling

A Module can modifies the state of another Model.

Functional Colhesion

To that different Module Elements co-operate is achieve a single Function.

Sequential colhesion

To perform operation to with data for it.

communication colhesion

If all task a Module refer relate to uptade to the same to each Function array, stack struct.

Topical Colhesion

The Model include those Functions that are in related to one function during the time.

Logical Colhesion

That all Elements of similar operation that input daty out put perform operations.

Coincidental cohesion

This Model to used to link the Module one form another.

function oriented design

The basic Anotations of the the uses functions the real World Entities.

object oriented model

We found and the all the Class and the de-Component them to form Main Model.

bottom up Model

It mean is solve the smaller Models.

Modularization

This technique devide to a multipole the descretes of Independ Modules which an inter related。

structure chart

That they hierarchical structurne to represent the entire the Model from the higher to higher Models.

psudocode

Find the some the form the to sum two Model.

low level design Model

In system detailed the to one level the components the system.

program

Testing is a proces the is execute a set of instructions is identify any Bugs in

the test Modules

It has to be the test the program with code to all the functionality.

the Unit testing module

To check the program for small models that the developers checks .

Integration Testing

We join the more module that check all that functions the work for good operation.

big Models

Big module of testing to combine the Modules and after testing operation .

top down intergration Model

First take the higher model of the code and after take the lower model components .

bottom up integration

The first Model has the all the components lower and test then after they intergate it to make one functions Models .

sandwich integration

has the components to take the from and top and from the bottom to test that Functions .

system Test

That the System tested to verify to the customer.

acceptance function

To be tested to verify that the quality the code has good operation or not.

regassion Model

New functions the are updated into the Models .

performance testing

The testing operation to know it the function are in perfect with each others.

Function Models

Does the program work in code functions..

Structural analysis testing Model

the test or check the the program that is made in white box and to find error .

Test model

Functions do they work to perform or not .

Stubs model

The program should be perfect or good then after that it work or not

Test data suiltes

That the testing functions of operation there is function the used to all them check .

Alpha program Models

To use some internal code and note the some program

beta model program

To test the more customer to more feedback.

Formal structure reviews.

The code is test but it to in good performance

Walk through system

They used one some code and see is all code .

code instruction

To be coding functions with good operations..

and coding

Code had bound with the numbers.