REVATURE INTERVIEW- QUESTIONS AND ANSWERS| LATEST UPDATE 100% SOLVED
SDLC (Software Development Life Cycle) the process of developing software through
analysis, design, implementation and maintenance.
Analysis: used to plan the basic project approach and to conduct product feasibility
Requirements: clearly define and document the product requirements
Design: this is where the design functions and operations are described in detail. Diagrams and
pseudocode are some ways to describe the software.
Development: this is where the the product starts getting built.
Implementation: After making the product it goes into testing
Maintenance: Fixing bugs and updating technologies. Agile is an example where requirements
are flexible whereas, waterfall has a set path and predictability.
Datatypes varchar: string of any character data
integer: signed 32-bit whole number
,smallint: 16-bit whole number
float: floating point number
date: a date value
timestamp: includes data and time
null: represents an empty value
Unified Modeling Language (UML) 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. Using Activities, Actors, Database Schemas, Programming Language
Statements. UML's appear in the Software Requirements Specification (SRS) document- a
description of a software system to be developed. It lays out functional and non-functional
requirements, and may include a set of use cases that describe user interactions that the
software must provide.
-(static) Structure diagrams show the things in a system being modeled. In a more technical
term, they show different objects in a system. Ex: Use-case, class
-(Dynamic) Behavioral diagrams shows what should happen in a system. They describe how the
objects interact with each other to create a functioning system. Ex: Sequence, Activity
, Use case diagram Use case- summary of scenarios for a single task or goal. Shows scenarios
of what happens when someone interacts with the system. ex: patient calls clinic to make
appointment. Receptionist finds empty slot and schedules it.
Helpful in 3 areas: Determining features, communicating with clients, generating test cases
Class diagrams gives an overview of a system by showing its classes and relationships among
them. Class diagrams are static- they display what interacts but not what happens when they
do interact.
Relationships of Class Diagrams:
-Association: just shows a link connecting two classes
-Aggregation: shows which class belongs to a collection. For example, the class "library" is made
up of one or more books, among other materials. In aggregation, the contained classes are not
strongly dependent on the life cycle of the container. In the same example, books will remain
so even when the library is dissolved.
Composition: Stronger form of aggregation. For example, a shoulder bag's side pocket will also
cease to exist once the shoulder bag is destroyed.
-Generalization: Shows a class is a superclass of the other. Ex: Payment is a superclass of Cash,
Check and Credit
-Realization: denotes the implementation of the functionality defined in one class by another
class. Ex: the printing preferences that are set using the printer setup interface are being
implemented by the printer.
SDLC (Software Development Life Cycle) the process of developing software through
analysis, design, implementation and maintenance.
Analysis: used to plan the basic project approach and to conduct product feasibility
Requirements: clearly define and document the product requirements
Design: this is where the design functions and operations are described in detail. Diagrams and
pseudocode are some ways to describe the software.
Development: this is where the the product starts getting built.
Implementation: After making the product it goes into testing
Maintenance: Fixing bugs and updating technologies. Agile is an example where requirements
are flexible whereas, waterfall has a set path and predictability.
Datatypes varchar: string of any character data
integer: signed 32-bit whole number
,smallint: 16-bit whole number
float: floating point number
date: a date value
timestamp: includes data and time
null: represents an empty value
Unified Modeling Language (UML) 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. Using Activities, Actors, Database Schemas, Programming Language
Statements. UML's appear in the Software Requirements Specification (SRS) document- a
description of a software system to be developed. It lays out functional and non-functional
requirements, and may include a set of use cases that describe user interactions that the
software must provide.
-(static) Structure diagrams show the things in a system being modeled. In a more technical
term, they show different objects in a system. Ex: Use-case, class
-(Dynamic) Behavioral diagrams shows what should happen in a system. They describe how the
objects interact with each other to create a functioning system. Ex: Sequence, Activity
, Use case diagram Use case- summary of scenarios for a single task or goal. Shows scenarios
of what happens when someone interacts with the system. ex: patient calls clinic to make
appointment. Receptionist finds empty slot and schedules it.
Helpful in 3 areas: Determining features, communicating with clients, generating test cases
Class diagrams gives an overview of a system by showing its classes and relationships among
them. Class diagrams are static- they display what interacts but not what happens when they
do interact.
Relationships of Class Diagrams:
-Association: just shows a link connecting two classes
-Aggregation: shows which class belongs to a collection. For example, the class "library" is made
up of one or more books, among other materials. In aggregation, the contained classes are not
strongly dependent on the life cycle of the container. In the same example, books will remain
so even when the library is dissolved.
Composition: Stronger form of aggregation. For example, a shoulder bag's side pocket will also
cease to exist once the shoulder bag is destroyed.
-Generalization: Shows a class is a superclass of the other. Ex: Payment is a superclass of Cash,
Check and Credit
-Realization: denotes the implementation of the functionality defined in one class by another
class. Ex: the printing preferences that are set using the printer setup interface are being
implemented by the printer.
