Q.no.

1:
What is the project scope?And explain its
relevant example?
Ans:Project scope: is the part of project planning that
involves determining and documenting a list of specific project goals,
deliverables, tasks, costs and deadlines. The documentation of a
project's scope is called a scope statement or terms of reference.
When we documenting a project's scope, stakeholders should be as
specific as possible to avoid scope creep. Scope creep is a situation
in which one or more parts of a project end up requiring more work,
time or effort because of poor planning or miscommunication .

Effective scope management :

Effective scope management requires good
communication.Every person can understands the extent of the
project and agrees the project's goals will be met. As part of scope
management, the team leader should ask for approvals and signoffs
from stakeholders as the project proceeds, ensuring that the
proposed finished project meets everyone's needs.

The importance of defining a project's scope

Writing a project scope statement that includes information
on the project deliverables is a first step in project planning. The
benefits of a project scope statement provides to any organization
undertaking a new initiative include the following:

 articulates what the project entails so that all stakeholders can

understand what's involved;
 provides a roadmap that managers can use to assign tasks,
schedule work and budget appropriately;
 helps focus team members on common objectives; and
prevents projects, particularly complex ones, from expanding
beyound the established vision.

How to define the scope of a project

Defining project scope requires input from the project stakeholders. They work
with project managers to establish the key elements of budget, objectives, quality
and timeline.

To determine scope, project managers must collect requirements for what the
stakeholders need from the project. This includes the following elements:

 the project's objective and deliverables;

 when the project must be completed; and
how much the stakeholders can pay for it.

Change management :
Updates and changes are the part of the project management
process.The manager must recongnize what elements are the part of project’s
scope and what elements which are out of scope.

Avoid Scope creep:

 Always have a written contract. A clearly defined written contract is an
important part of setting expectations at the beginning of a project. ...
 Create a back up plan. ...
 Host a kick-off meeting. ...
 Communicate clearly and often. ...
 Know when to say no. ...
 Provide options for additional work

Project scope example:

If you’re working on a product marketing launch, you want to make sure you align with
stakeholders on relevant teams at your company, like the product team, the design team,
and the content team. Depending on how complex your project is, you may also want to
define a change control process—we’ll get into how you can do that later.

Project scope vs. product scope:

Project scope should not be confused with product scope. Product scope defines the
capabilities, characteristics, features and functions of the deliverables at the end of the
project.

Project leaders should create a separate product scope statement. They should use both
the project scope and the product scope statements to support each other and establish
a clear understanding of what every project aims to achieve.

The takeaway:
Defining project scope is an important step in project planning and
management. Before a project begins, project managers need to understand what
the scope of the project is to determine what must be done and what falls outside
of the project.Scope statements align stakeholders expectations and give
projects a framework for success.
Q.no.3:-
What is the difference between “Black
box testing and White box testing”and
explain give its one technique?

Ans:
Difference between Black Box
Testing vs White Box Testing:
 
1. Black Box Testing is a software testing method in which the internal
structure/design/implementation of the item being tested is not known to the tester.
Only the external design and structure are tested.

Black Box Testing Techniques:

Following are the prominent Test Strategy amongst the
many used in Black box Testing
 Equivalence Class Testing: It is used Boundary value testing is
focused on the values at boundaries. This technique determines whether a
certain range of values are acceptable by the system or not. It is very useful
in reducing the number of test cases. It is most suitable for the systems
where an input is within certain ranges to minimize the number of possible
test cases to an optimum level while maintains reasonable test coverage.
Boundary Value Testing: Boundary value testing is focused on the
values at boundaries. This technique determines whether a certain range of
values are acceptable by the system or not. It is very useful in reducing the
number of test cases. It is most suitable for the systems where an input is
within certain ranges.
Decision Table Testing: A decision table puts causes and their effects
in a matrix. There is a unique combination in each column.

Advantages of Black Box Testing:

 Well suited and efficient for large code segments.
 Code access is not required.
 Clearly separates user's perspective from the developer's perspective
through visibly defined roles.
 Large numbers of moderately skilled testers can test the application with no
knowledge of implementation, programming language, or operating system
s.
Disadvantages of Black Box Testing:
 Limited coverage, since only a selected number of test scenarios is actually
performed.
 Inefficient testing, due to the fact that the tester only has limited knowledge
about an application.
 Blind coverage, since the tester cannot target specific code segments or
errorprone areas.

 The test cases are difficult to design.

2. White Box Testing is a software testing method in which the internal

structure/design/implementation of the item being tested is known
tester. Implementation and impact of the code are tested.
Techniques for white box testing:
Statement Coverage - This technique is aimed at exercising all programming statements
with minimal tests.

Branch Coverage - This technique is running a series of tests to ensure that all branches
are tested at least once.

Path Coverage - This technique corresponds to testing all possible paths which means
that each statement and branch is covered.

Advantages of White Box Testing:

 Forces test developer to reason carefully about implementation.

 Reveals errors in "hidden" code.

 Spots the Dead Code or other issues with respect to best programming practices.

Disadvantages of White Box Testing:

 Expensive as one has to spend both time and money to perform white box testing.

 Every possibility that few lines of code are missed accidentally.

 In-depth knowledge about the programming language is necessary to perform

white box testing.

Differences between Black Box Testing vs White Box Testing: 

 Black Box Testing White Box Testing

It is a way of software testing in which the It is a way of testing the software in which
internal structure or the program or the the tester has knowledge about the internal
code is hidden and nothing is known about structure or the code or the program of the
it. software.

Implementation of code is not needed for Code implementation is necessary for white
black box testing. box testing.

It is mostly done by software testers. It is mostly done by software developers.

No knowledge of implementation is
needed. Knowledge of implementation is required.

It can be referred as outer or external It is the inner or the internal software

software testing. testing.

It is functional test of the software. It is structural test of the software.

This testing can be initiated on the basis of This type of testing of software is started
requirement specifications document. after detail design document.

No knowledge of programming is It is mandatory to have knowledge of

required. programming.

It is the behavior testing of the software. It is the logic testing of the software.

It is applicable to the higher levels of It is generally applicable to the lower levels

testing of software. of software testing.

It is also called closed testing. It is also called as clear box testing.

It is least time consuming. It is most time consuming.

It is not suitable or preferred for algorithm It is suitable for algorithm testing.

 Black Box Testing White Box Testing

testing.

Can be done by trial and error ways and Data domains along with inner or internal
methods. boundaries can be better tested.

Example: search something on google by Example: by input to check and verify

using keywords loops

Types of Black Box Testing:  Types of White Box Testing: 

   
 A. Functional Testing   A. Path Testing 
   
 B. Non-functional testing   B. Loop Testing 
   
 C. Regression Testing  C. Condition testing
   

Q.no.2:
Name and elements/symbols/contructions of
flowchart?
Ans:Flowchart is a diagrammatic representation of sequence of logical steps of a
program. Flowcharts use simple geometric shapes to depict processes and arrows to show
relationships and process/data flow.

Flowchart Symbols:
Here is a chart for some of the common symbols used in drawing flowcharts.

Symbol Symbol Name Purpose

Used at the beginning and end of the algorithm to

Start/Stop
show start and end of the program.
 Indicates processes like mathematical operations.
Process

Input/ Output Used for denoting program inputs and outputs.

Stands for decision statements in a program, where

answer is usually Yes or No.
Decision

Shows relationships between different shapes.

Arrow

Connects two or more parts of a flowchart, which

are on the same page.
On-page Connector

Connects two parts of a flowchart which are spread

over different pages.
Off-page Connector

Guidelines for Developing Flowcharts:

These are some points to keep in mind while developing a flowchart −
 Flowchart can have only one start and one stop symbol
 On-page connectors are referenced using numbers
 Off-page connectors are referenced using alphabets
 General flow of processes is top to bottom or left to right
 Arrows should not cross each other
Example Flowchart:
Here is a flowchart to calculate the average of two numbers.
Constructing Flow Charts:
Constructing a flow chart involves the following main steps:
 Define the process and identify the scope of the flow diagram;
 Identify project team members that are to be involved in the construction of the
process flow diagram;
 Define the different steps involved in the process and the interrelationships
between the different steps (all team members should help develop and agree
upon the different steps for the process);
 Finalize the diagram, involving other concerned individuals as needed and making
any modifications necessary; and
 Use the flow diagram and continuously update it as needed.