Software Engineering Terms - M

Sunday, October 2, 2011


MAINTENANCE
The process of supporting production software to detect and correct faults, optimize
performance, and ensure appropriate availability to end-users.

MASTER TABLE
A table containing data on which detail data in another table depends. Master tables
have a primary key that's matched to a foreign key in a detail table and often have a oneto-
many relationship with detail tables.

MEGABYTE (MB)
Approximately one million bytes. A unit of computer storage capacity.

MEGAHERTZ (MHZ)
A measure of the clock speed of the CPU in a computer. One megahertz equals one
million cycles per second.

METADATA
Data that describes the structure, organization, and/or location of data. In essence,
metadata is "data about data."

METHODOLOGY
A set of processes, procedures, and standards that defines an engineering approach to
the development of a work product.

METRICS
Numeric data representing measurements of business processes or database activity.

MILESTONE
In project management, a scheduled event of significance for which an individual or team
is accountable. Often used to measure progress.

MODEL
An abstract representation that illustrates the components or relationships of a specified
application or module.

MODULE
A functional part of an application that is discrete and identifiable with a specific subject.

MODULE TESTING
The process of testing individual software modules or sets of related modules to verify
the implementation of the software.

MULTIUSER
Concurrent access to a single database by more than one user, usually through the use
of client workstations.

Read more...

Software Engineering Terms - L


LIFECYCLE
A set of software development activities, or stages that function together to guide the
development and maintenance of software products. Each stage is finite in scope,
requires a specific set of inputs, and produces a specific set of deliverables.

Read more...

Software Engineering Terms - K


KEY FIELD
A field used to identify a record or group of records by its value. See also primary key
and foreign key.

KEY PROCESS AREA
A software engineering process identified by the Software Engineering Institute Capability
Maturity Model that is an essential to an organization's ability to develop consistently
high-quality software products.

KILOBYTE (KB)
One thousand bytes (actually 1024 storage positions). Used as a measure of storage
capacity.

KNOWLEDGE MANAGEMENT
The process of systematically managing and leveraging the stores of knowledge in an
organization. This knowledge is generally stored as sets of documents or database
records.

Read more...

Software Engineering Terms - J


JOIN
A database operation or command that links the rows or records of two or more tables by
one or more columns in each table.

JOINT APPLICATION DESIGN (JAD)
A design technique that brings users and IT professionals into a facilitated meeting for
the purpose of interactively designing an application.

Read more...

Software Engineering Terms - I


IMPLEMENTATION ELEMENTS
A specific software component created to fulfill a specific function defined in the
functional and system design documents.

IMPLEMENTATION STAGE
A stage in the software development lifecycle during which a software product is created
from the design specifications and testing is performed on the individual software units
produced. Also referred to as the programming stage.

INCREMENTAL DEVELOPMENT
A software development technique where multiple small software development lifecycles
are used to develop the overall software product in a modular fashion.

INDEX
A specialized data structure used to facilitate rapid access to individual database records
or groups of records.

INFORMATION
Data that has been shaped into a form that is meaningful and useful to humans.

INFORMATION SYSTEM
Interrelated components working together to collect, process, store, and disseminate
information to support decision-making, coordination, control, analysis, and/or
visualization in an organization.

INHERITANCE
A feature of object-oriented programming where a specific class of objects receives the
features of a more general class.

INITIAL DATA LOAD
When a new database application is first brought online, certain sets of data are
preloaded to support operations. In some cases, a large amount of data is transferred
from one or more legacy systems that the new database application is replacing. The
initial data load figure is calculated as the sum of all records in operational and support
data areas on day zero of the applications production lifecycle. This figure is used as a
baseline for estimating development effort, server hardware requirements and network
loads.

INNER QUERY
Synonym for sub query.

INSERTION POINT
The position of the cursor within a block of text.

INSPECTION
Also termed desk checking. A quality assurance technique that relies on visual
examination of developed products (usually source code or design documentation) to
detect errors, violation of development standards, and other problems.

INSTALLATION STAGE
A software lifecycle stage that consists of the testing, training, and conversion efforts
necessary to place the developed software application into production.

INTEGRITY
The degree to which a software component or application prevents unauthorized access
to, or modification of, programs or data.

INTEGER
A whole number, usually limited to a range of -32,000 to +32,000.

INTERFACE
A formal connection point defined between two independent applications for the purpose
of data exchange.

INTERFACE TESTING
A testing technique that evaluates whether software components pass data and control
correctly to one another.

INTERSECTION
A group of data elements included in two or more tables as part of a Join operation. 

Read more...

Software Engineering Terms - H


HARDWARE
Physical computer equipment and peripherals used to process, store, or transmit
software applications or data.

HIERARCHICAL MENU
A menu with multiple levels, consisting of a main Menubar that leads to one or more
levels of sub menus from which choices or actions are made.

HYPERTEXT MARKUP LANGUAGE (HTML)
A programming tool that uses HyperText to establish dynamic links to other documents
stored in the same or remote computers.

Read more...

Software Engineering Terms - G


GROUP

During report generation, one or more records that are collected into a single category, usually for the purpose of totaling. Also used to identify a collection of database users with common access privileges. 

Read more...

Software Engineering Terms - F

Saturday, June 18, 2011


FEASIBILITY STUDY
A process that determines whether the solution under analysis is achievable, given the
organization's resources and constraints.

FIELD
Synonym for a data element that contains a specific attribute's value; a single item of
information in a record or row.

FOCUS
The application object to which the user-generated input (usually keyboard and mouse) is
directed.

FOREIGN KEY
A field or set of fields in a table whose value must match a primary key in another table
when joined with it. Also see primary key and join.

FORM
A screen formatted to facilitate data entry and review. Utilizes data entry fields, option
selection tools, and control objects such as buttons and menu items.

FUNCTIONAL AREA
Any formally organized group focused on the development, execution, and maintenance
of business processes in support of a defined business function.

FUNCTIONAL DESIGN STAGE
That stage of the software development lifecycle that focuses on the development and
validation of designs for architecture, software components, data and interfaces. Often
combined with the system design stage into a single stage for smaller applications.

FUNCTIONAL ELEMENT
A definition that specifies the actions that a software component, product, or system must
be able to perform.

FUNCTIONAL TESTING
Also known as end-user testing. Testing that focuses on the outputs generated in
response to selected inputs and execution conditions.

FUNCTION POINT ANALYSIS
A software measurement process that focuses on the number of inputs, outputs, queries,
tables, and external interfaces used in an application. Used for software estimation and
assessment of developer productivity.

Read more...

Software Engineering Terms - E


ENCRYPTION
The coding and scrambling of messages to prevent unauthorized access to or
understanding of the data being stored or transmitted.

END-USER REVIEW
The review of a deliverable for functional accuracy by a Subject Matter Expert who is
familiar with the software product under design or development. See Review.

ENTITY
A collection of attributes related to and describing a specific subject, such as Products.

ENTITY-RELATIONSHIP DIAGRAM
A diagram illustrating the relationship between various entities in a database.

EXECUTABLE
A binary data file that can be run by the operating system to perform a specific set of
functions. In Windows, executables carry the extension .EXE and can be launched by
double-clicking on them.

EXTERNAL INTERFACE
In database applications, an external interface is a defined process and data structure
used to exchange data with other systems. For example, an order processing application
may have an interface to exchange data with an external accounting system.

EXTERNAL INTERFACE COMPLEXITY
The level of complexity associated with an external interface. A simple interface is
generally unidirectional, with limited, stable logic defining the structure of the exchanged
data. A standard export from a database to a spreadsheet is considered a simple
interface. A complex interface may be bi-directional, or may have extensive, adaptive
logic defining the structure of the exchanged data. The transmission of labor data to a
corporate payroll system, with its attendant validation and transaction confirmation
requirements, is considered a complex interface.

Read more...

Software Engineering Terms - D


DATA
Streams of raw facts representing events before they have been organized and arranged
into a form that people can understand and use. See information.

DATA DICTIONARY
A structured description of database objects such as tables, indexes, views and fields,
with further descriptions of field types, default values and other characteristics.

DATA ELEMENT
See field.

DATA ENTITY
A data representation of a real world object or concept. Usually represented as a row in
a database table, such as information about a specific Product in inventory.

DATA FLOW DIAGRAM
A primary tool in structured analysis that graphically illustrates a system's component
processes and the flow of data between them.

DATA TYPE
A description of how the computer is to interpret the data stored in a particular field. Data
types can include text or character string data, integer or floating point numeric data,
dates, date/time stamps, true/false values, or Binary Large Objects (BLOBs) which can
be used to store images, video, or documents.

DATABASE
A set of related data tables and other database objects, such as a data dictionary, that
are organized as a group. A collection of data organized to service many applications at
the same time.

DATABASE OBJECT
A component of a database, such as a table or view.

DATABASE ADMINISTRATOR
Person(s) responsible for the administrative functions of databases, such as system
security, user access, performance and capacity management, and backup and
restoration functions.

DATABASE MANAGEMENT SYSTEM (DBMS)
Software used to create and maintain a database and enable individual business
applications to extract the data they need without having to create separate files or data
definitions for their own use.

DEFAULT
An initial value assigned to a field by the application when a new database record is
created. Used to facilitate data entry by pre-entering common values for the user.

DELIVERABLE
A specific work product, such as requirements or design documentation, produced during
a task or activity to validate successful completion of the task or activity. Sometimes,
actual software is delivered.

DESIGN ELEMENT
A specification for a software object or component that fulfills, or assists in the fulfillment
of a functional element. A part of the system design specification.

DESIGN STAGE
A stage in the software development lifecycle that produces the functional and system
design specifications for the application under development.

DEVELOPER SKILLS/RESOURCES
The availability of developers and other resources with appropriate skills is a significant
factor in project success. When developers and resources are readily available, the
likelihood of project success is very high. Most development firms manage multiple
projects, allowing some contention between projects for developers and other resources.
This project risk factor is considered high when one or more developers with specific skill
sets, or resources with specific capabilities, need to be acquired before the project can
continue.

DOCUMENTATION
Information made available to: 1) assist end-users in the operation of a software
application, generally in the form of on-line help, or 2) assist developers in locating the
correct root procedure or method for a specific software function, generally in the form of
an implementation map. Note that printed manuals are rarely delivered with software
anymore; on-line documentation is more consistently available from within the application
and is easier to use.

Read more...

Software Engineering Terms - C

Saturday, January 29, 2011


CLIENT
1. The user point-of-entry for an application. Normally a software executable
residing on a desktop computer, workstation, or laptop computer. The user
generally interacts directly only with the client, using it to input, retrieve, analyze
and report on data.
2. A device or application that receives data from or manipulates a server device or
application.

CODE REVIEW
A meeting at which source code is presented for review, comment, or approval.


COMPONENT
One of the parts that make up a system. A component may be hardware, software, or
firmware and may be subdivided into other components.

COMPUTER SOFTWARE
Detailed, pre-programmed instructions that control and coordinate the work of computer
hardware and firmware components in an information system. 


COMPUTER-AIDED SOFTWARE ENGINEERING (CASE)
The automation of step-by -step methodologies for software and systems development to
reduce the amount of repetitive work required of the analyst or developer.


CONFIGURATION MANAGEMENT
A process that effectively controls the coordination and implementation of changes to
software components.


CONSTRAINT
A restriction, limitation, or regulation that limits a given course of action.


CONTEXT DIAGRAM
Overview data flow diagram depicting an entire system as a single process with its major
inputs and outputs.


CONVERSION
The process of changing from the old system to the new system.


CRITICAL SUCCESS FACTORS (CSFS)
A set of specific operational conditions shaped by the business environment that are
believed to significantly impact the success potential of an organization or business
function. In a software development effort, critical success factors are composed of
assumptions and dependencies that are generally outside the control of the development
team.


CUSTOMER RESOURCES
The number of subject matter experts for each Use Case (UC) in an application under
development. This project risk factor is considered low when more than one SME is
available perUC. A high risk ensues when outside SMEs are involved with a software
development effort.

Read more...

Software Engineering Terms - B

Tuesday, January 25, 2011


BANDWIDTH
The capacity of a communications channel.

BASELINE
A set of software components and documents to that has been formerly reviewed and
accepted, that serves as the basis for further development or current production, which
can be changed only through formal change control procedures. See Release version.

BATCH PROCESSING
A method of collecting and processing data in which transactions are accumulated and
stored until a specified time when it is convenient or necessary to process them as a
group.

BUSINESS PROCESSES
The unique ways in which organizations coordinate and organize work activities,
information, and knowledge to produce a product or service. For example, in a sales
environment, the information used and steps taken to record a new customer order is
considered a business process.

BUSINESS PROCESS COMPLEXITY
A project risk factor that takes into consideration the complexity of the business process
or processes under automation. Project risk is considered low when all processes involve
fairly simple data entry and update operations. Project risk is considered medium when a
minority of the business processes under automation are complex, involving multiple
steps, exchanges with external systems or significant validation/processing logic. Project
risk is considered high when a majority of the business processes under automation are
considered to be complex.

BUSINESS PROCESS MATURITY
A project risk factor that takes into consideration the maturity and stability of the business
process or processes to be automated. Project risk is considered low when standard
business processes that have been stable and in place for a significant period of time are
being automated. Project risk is considered medium when one or more nonstandard but
stable business processes, generally unique to the customers situation, are being
automated. Project risk rises significantly when the development team is attempting to
automate one or more new or unusual business processes.

BUSINESS RULE
A logical or mathematical test that determines whether data entered in a database
complies with an organization's method of conducting its operations.

Read more...

Software Quality Assurance Interview Questions | SQA Questions | SQA Paper

Saturday, January 22, 2011



  1. what is software?

  1. what is representation?

  1. what is continuous representation and stage representation?

  1. what are the major difference b/w stage and continuous?

  1. can any industry apply CMMI?

  1. what is CMM and CMMI and differences?

  1. what is Specific goal specific practices and Generic goal and generic practices?

  1. what are the flow or How to work or how to apply SP GP SG GG? Which will comes under sp gg gp sp, I mean which will come first under levels?

  1. how to achieve these SP GP SG GG? What the process to achieve these SP GP SG GG?

  1.  types of testing?

  1.  which control chart will be apply in s/w? and why?

  1.  what is the process area?

  1. what is spice and tickit?

  1.  what is JAD?

  1.  what is s/w metrics and what is need?

  1.  how to gather the data?

  1. what is scrum methodology?

  1.  what is s/w engineering document?

  1.  what is task force?

  1.  what is use of SPSS , clear case?

  1. what are tools which we are using in s/w?

  1. listing of metrics?

  1.  what is schedule variances effort variances?

  1.  defect rate. Deliver defect rate, requirement stability index?

  1.  review effectiveness, QA effectiveness, project utilization?

  1. what is vss, cvs?

  1.  what is configuration management?

  1.  what is change management?

  1.  risk management?

  1. quantitative product management?

  1. DAR?

  1.  process capability in s/w?

  1.  what is baseline?

  1.  work product?

  1.  what is the s/w development life cycle?

  1.  what are the inputs and outputs of SDLC for each phases?

  1.  types of models like spiral, agile etc..?


Read more...

Chitika

About This Blog

Followers

  © Blogger template The Professional Template II by Ourblogtemplates.com 2009

Back to TOP