PRATICAL :- 1

Write Problem statement to define the Project Title with bounded

scope of the project.

➢ RESOURCES REQUIRED :-
1) Hardware personal computer(i3-i5 preferable)
2) Operating System Windows 7/ windows 8/ windows 10/ linux or any other
3) Software tools:- Any UML tools

EXERCISE :-
1. Describe the characteristics of software.
Ans:- Three most important characteristics of good software are
1) Operational 2)Transitional 3)Maintenance.

2. Write note on development framework.

Ans:- A framework, or software framework, is a platform for developing
software applications. It provides a foundation on which software developers
can build programs for a specific platform. A framework may also include code
libraries, a compiler, and other programs used in the software development
process. Several different types of software frameworks exist. Popular
examples include ActiveX and .NET for Windows development, Cocoa for Mac
OS X, Cocoa Touch for iOS, and the Android Application Framework for
Android.
 PRATICAL:-2

Select relevant process model of define activities & related tasks set
of assignment project.

EXERCISE:-
1. Explain waterfall model.
Ans:- The Waterfall Model was the first Process Model to be introduced. It is
also referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed before
the next phase can begin and there is no overlapping in the phases. The
Waterfall model is the earliest SDLC approach that was used for software
development. The waterfall Model illustrates the software development process
in a linear sequential flow. This means that any phase in the development
process begins only if the previous phase is complete. In this waterfall model,
the phases do not overlap.

2. Explain the basic process frame work activities.

Ans:- A generic process framework encompasses five activities which are given
below one by one:
• Communication: In this activity, heavy communication with customers
and other stakeholders, requirement gathering is done.

• Planning: In this activity, we discuss the technical related tasks, work

schedule, risks, required resources etc.

• Modeling: Modeling is about building representations of things in the

‘real world’. In modeling activity, a product’s model is created in order
to better understanding and requirements.
• Construction: In software engineering, construction is the application of
set of procedures that are needed to assemble the product. In this activity,
we generate the code and test the product in order to make better
product.
• Deployment: In this activity, a complete or non-complete products or
software are represented to the customers to evaluate and give feedback.
On the basis of their feedback we modify the products for supply better
product.
 PRATICAL:-3

Gather Application Specific requirements for assimilate into RE

model

MINIMUM THEROTICAL BACKGROUND:-

1. Functional Requirement:
Ans:- Functional Requirement (FR) is a description of the service that the
software must offer. It describes a software system or its component. A function
is nothing but inputs to the software system, its behavior, and outputs. It can be
a calculation, data manipulation, business process, user interaction, or any
other specific functionality which defines what function a system is likely to
perform. Functional Requirements are also called Functional Specification.
2. Nonfunctional requirement:
Ans:- Nonfunctional Requirements (NFRs) define system attributes such as
security, reliability, performance, maintainability, scalability, and usability.
They serve as constraints or restrictions on the design of the system across the
different backlogs. Also known as system qualities, nonfunctional requirements
are just as critical as functional Epics, Capabilities, Features, and Stories.

➢ RESOURCES REQUIRED:-
1. Hardware personal computer(i3-i5 preferable)
2. Operating System Windows 7/ windows 8/ windows 10/ linux or any
other
EXERCISE:-
1. What is requirement elicitation write in detail?
Ans:- In requirements engineering, requirements elicitation is the practice of
researching and discovering the requirements of a system from users,
customers, and other stakeholders. The practice is also sometimes referred to
as “requirement gathering”. The term elicitation is used in books and research
to raise the fact that good requirements cannot just be collected from the
customer, as would be indicated by the name requirements gathering.
Requirements elicitation is non-trivial because you can never be sure you get
all requirements from the user and customer by just asking them what the
system should do or not do (for Safety and Reliability). Requirements elicitation
practices include interviews, questionnaires, user observation, workshops,
brainstorming, use cases, role playing and prototyping.
 PRATICAL -4

Prepare broad SRS (Software requirement Software) for the above

selected projects.

• Software requirements specification (SRS):

A software requirements specification (SRS) is a description of a software system to
be developed. It is modeled after business requirements specification (CONOPS),
also known as a stakeholder requirements specification (StRS).
The software requirements specification lays out functional and non-functional
requirements, and it may include a set of use cases that describe user interactions
that the software must provide to the user for perfect interaction.
Software requirements specification establishes the basis for an agreement between
customers and contractors or suppliers on how the software product should function
(in a market-driven project, these roles may be played by the marketing and
development divisions). Software requirements specification is a rigorous
assessment of requirements before the more specific system design stages, and its
goal is to reduce later redesign. It should also provide a realistic basis for estimating
product costs, risks, and schedules. Used appropriately, software requirements
specifications can help prevent software project failure. The software requirements
specification document lists sufficient and necessary requirements for the project
development. To derive the requirements, the developer needs to have clear and
thorough understanding of the products under development. This is achieved
through detailed and continuous communications with the project team and
customer throughout the software development process.
MINIMUM THEROTICAL BACKGROUND:
1. RELIABILITY:
Ans:- Software Reliability means Operational reliability. It is described as the
ability of a system or component to perform its required functions under static
conditions for a specific period.
Software reliability is also defined as the probability that a software system
fulfills its assigned task in a given environment for a predefined number of
input cases, assuming that the hardware and the input are free of error.
Software Reliability is an essential connect of software quality, composed with
functionality, usability, performance, serviceability, capability, installability,
maintainability, and documentation.

2. EXTENSIBILITY:
Ans:- Extensibility is a software engineering and systems design principle that
provides for future growth. Extensibility is a measure of the ability to extend a
system and the level of effort required to implement the extension. Extensions
can be through the addition of new functionality or through modification of
existing functionality. The principle provides for enhancements without
impairing existing system functions.
An extensible system is one whose internal structure and dataflow are
minimally or not affected by new or modified functionality, for example
recompiling or changing the original source code might be unnecessary when
changing a system’s behavior, either by the creator or other programmers.
Because software systems are long lived and will be modified for new features
and added functionalities demanded by users, extensibility enables developers
to expand or add to the software’s capabilities and facilitates systematic reuse.

3. SECURITY REQUIREMENT:
Ans:- A security requirement is a statement of needed security functionality
that ensures one of many different security properties of software is being
satisfied. Security requirements are derived from industry standards,
applicable laws, and a history of past vulnerabilities. Security requirements
define new features or additions to existing features to solve a specific security
problem or eliminate a potential vulnerability.
Security requirements provide a foundation of vetted security functionality for
an application. Instead of creating a custom approach to security for every
application, standard security requirements allow developers to reuse the
definition of security controls and best practices. Those same vetted security
requirements provide solutions for security issues that have occurred in the
past. Requirements exist to prevent the repeat of past security failures.

➢ RESOURCES REQUIRED:-
1. Hardware personal computer(i3-i5 preferable)
2. Operating System Windows 7/ windows 8/ windows 10/ linux or any
other
 PRATICAL -5
Prepare USE Cases and Draw Use Case Diagram using modelling
TTool

➢ RESOURCES REQUIRED:-
1. Hardware personal computer(i3-i5 preferable)
2. Operating System Windows 7/ windows 8/ windows 10/ linux or any
other

MINIMUM THEROTICAL BACKGROUND:

I. Use case diagram

Ans:- Use-case diagrams illustrate and define the context and requirements of
either an entire system or the important parts of the system. You can model a
complex system with a single use-case diagram, or create many use-case
diagrams to model the components of the system. You would typically develop
use-case diagrams in the early phases of a project and refer to them throughout
the development process.
II. Actor:
Ans:- An actor represents a role of a user that interacts with the system that
you are modeling. The user can be a human user, an organization, a machine,
or another external system. You can represent multiple users with a single actor
and a single user can have the role of multiple actors. Actors are external to the
system. They can initiate the behavior described in the use case or be acted upon
by the use case. Actors can also exchange data with the system.
 III. Use case:
Ans:- A use case describes a function that a system performs to achieve the
user’s goal. A use case must yield an observable result that is of value to the
user of the system. Use cases contain detailed information about the system, the
system’s users, relationships between the system and the users, and the
required behavior of the system. Use cases do not describe the details of how
the system is implemented. Each use case describes a particular goal for the
user and how the user interacts with the system to achieve that goal. The use
case describes all possible ways that the system can achieve, or fail to achieve,
the goal of the user.

IV. Relationship:
Ans:-
 Association relationships :-
In UML models, an association is a relationship between two classifiers, such
as classes or use cases, that describes the reasons for the relationship and the
rules that govern the relationship.
 Generalization relationships
In UML modeling, a generalization relationship is a relationship in which one
model element (the child) is based on another model element (the parent).
Generalization relationships are used in class, component, deployment, and
use-case diagrams to indicate that the child receives all of the attributes,
operations, and relationships that are defined in the parent.
 Include relationships
In UML modeling, an include relationship is a relationship in which one use
case (the base use case) includes the functionality of another use case (the
inclusion use case). The include relationship supports the reuse of
functionality in a use-case model.
 Extend relationships
In UML modeling, you can use an extend relationship to specify that one use
case (extension) extends the behavior of another use case (base). This type of
relationship reveals details about a system or application that are typically
hidden in a use case.

PRACTICAL RELATED QUESTION:

1. Describe relationship between use cases.
Ans:- Relationships between Use Cases
 COMMUNICATES. The behavioral relationship communicates is used
to connect an actor to a use case. Remember that the task of the use case
is to give some sort of result that is beneficial to the actor in the system.
Therefore, it is important to document these relationships between actors
and use cases. In our first example, a Student communicates with Enroll
in Course. Examples of some components of a student enrollment
example are shown in the use case diagrams in the figure below.

 INCLUDES. The includes relationship (also called uses relationship)

describes the situation in which a use case contains behavior that is
common to more than one use case. In other words, the common use case
is included in the other use cases. A dotted arrow that points to the
common use case indicates the includes relationship. An example would
be a use case Pay Student Fees that is included in Enroll in Course and
Arrange Housing, because in both cases students must pay their fees. This
may be used by several use cases. The arrow points toward the common
use case.

 EXTENDS. The extends relationship describes the situation in which one

use case possesses the behavior that allows the new use case to handle a
variation or exception from the basic use case. For example, the extended
use case Student Health Insurance extends the basic use case Pay Student
Fees. The arrow goes from the extended to the basic use case.
  GENERALIZES. The generalizes relationship implies that one thing is
more typical than the other thing. This relationship may exist between
two actors or two use cases. For example, a Part-Time Student
generalizes a Student. Similarly, some of the university employees are
professors. The arrow points to the general thing.

2. Explain categories of actors.

Ans:- Actors can be primary or secondary actors. Primary actors initiate a use
case, while secondary actors support a use case or receive something of value
from the use case. While this answer might score you some points in the
interview, there is another way to classify actors that is important to know and
can show that you understand some of the finer points of use case diagramming.
Actors can be:
1. Human
2. Systems/Software
3. Hardware
4. Timer/Clock
Many analysts miss key actors during the use case diagramming process
because they only identify human actors. Categorizing use case actors in this
ways helps the analyst ensure they haven’t overlooked any critical actors within
the use case diagram.
 PRATICAL :-6

Develop the activity diagram to represent flow from one activity to

another for software development

➢ RESOURCES REQUIRED:-
1) Hardware personal computer(i3-i5 preferable)

2) Operating System Windows 7/ windows 8/ windows 10/

linux or any other

PRACTICAL RELATED QUESTION:-

1. Draw activity diagram for above defined project

Ans:-
 PRATICAL -7

Develop data Designs using DFD, Decision Table & ER diagram

MINIMUM THEROTICAL BACKGROUND (Related with your project):-

1. Level 0 DFD:
Ans:- DFD Level 0 is also called a Context Diagram. It’s a basic overview of
the whole system or process being analyzed or modeled. It’s designed to be an
at-a-glance view, showing the system as a single high-level process, with its

relationship to external entitie

s. It should be easily understood by a wide audience, including stakeholders,
business analysts, data analysts and developers.

2. Level 1 DFD
Ans:- DFD Level 1 provides a more detailed breakout of pieces of the Context
Level Diagram. You will highlight the main functions carried out by the system,
as you break down the high-level process of the Context Diagram into its
subprocesses.
 3. Level 2 DFD
Ans:- DFD Level 2 then goes one step deeper into parts of Level 1. It may
require more text to reach the necessary level of detail about the system’s
functioning.
4)Decision table
Ans:- Decision table is a brief visual representation for specifying which actions
to perform depending on given conditions. The information represented in
decision tables can also be represented as decision trees or in a programming
language using if-then-else and switch-case statements. A decision table is a
good way to settle with different combination inputs with their corresponding
outputs and also called cause-effect table. Reason to call cause-effect table is a
related logical diagramming technique called cause effect graphing that is
basically used to obtain the decision table.

➢ RESOURCES REQUIRED:-
1) Hardware personal computer(i3-i5 preferable)
2) Operating System Windows 7/ windows 8/ windows 10/ linux or any
other

PRACTICAL RELATED QUESTION:-

1. Explain term attribute with example.
Ans:- In general, an attribute is a property or characteristic. Color, for
example, is an attribute of your hair. In using or programming computers, an
attribute is a changeable property or characteristic of some component of a
program that can be set to different values.
2. Explain the symbol of DFD.
Ans:- DFD symbols are consistent notations that depict a system or a process.
It entails the use of short-text labels, arrows, circles and rectangles to describe
data flow direction. Also forming part of DFDs are varied sub-processes, data
storage points, and data inputs and outputs. A data flow diagram has four basic
elements. The elements include external entities, data stores, processes, and
data flows. The elements are best represented by the two main methods of
notation used in DFDs – Yourdon & Coad, and Gane & Sarson. DFD symbols
vary slightly depending on methodology. Even so, the basic ideas remain the
same.
Basic Data Flow Diagram Symbol :-
 PRATICAL: -8

Draw class diagram, sequence diagram, Collaboration Diagram,

State Transition Diagram for the assigned project.

MINIMUM THEROTICAL BACKGROUND (Related with your project):-

 Class diagram
Ans:- Class diagram is a static diagram. It represents the static view of an
application. Class diagram is not only used for visualizing, describing, and
documenting different aspects of a system but also for constructing executable
code of the software application. Class diagram describes the attributes and
operations of a class and also the constraints imposed on the system. The class
diagrams are widely used in the modeling of object oriented systems because
they are the only UML diagrams, which can be mapped directly with
objectoriented languages. Class diagram shows a collection of classes,
interfaces, associations, collaborations, and constraints. It is also known as a
structural diagram.

 Sequence diagram
Ans:- A sequence diagram simply depicts interaction between objects in a
sequential order i.e. the order in which these interactions take place. We can
also use the terms event diagrams or event scenarios to refer to a sequence
diagram. Sequence diagrams describe how and in what order the objects in a
system function. These diagrams are widely used by businessmen and software
developers to document and understand requirements for new and existing
systems.

 Collaboration diagram
Ans:- A collaboration diagram, also known as a communication diagram, is an
illustration of the relationships and interactions among software objects in the
Unified Modeling Language (UML). These diagrams can be used to portray the
dynamic behavior of a particular use case and define the role of each object.
Collaboration diagrams are created by first identifying the structural elements
required to carry out the functionality of an interaction. A model is then built
using the relationships between those elements. Several vendors offer software
for creating and editing collaboration diagrams.

 State transition diagram

Ans:- The state machine diagram is also called the Statechart or State
Transition diagram, which shows the order of states underwent by an object
within the system. It captures the software system’s behavior. It models the
behavior of a class, a subsystem, a package, and a complete system. It tends out
to be an efficient way of modeling the interactions and collaborations in the
external entities and the system. It models event-based systems to handle the
state of an object. It also defines several distinct states of a component within
the system. Each object/component has a specific state.

PRACTICAL RELATED QUESTION:

1. Draw symbol used in:
• Class diagram.
• Sequence diagram.
• Collaboration diagram.
• State transition diagram.
Ans.
1. Class Diagram :-

2. Sequence Diagram :-
3. Collaboration Diagram :-

4. State Transition Diagram :-

 PRATICAL: -9
Write test cases to validate requirements of assigned project from
SRS

Resources Required:-
Sr. Name of Specification Quantity
No. Resource
1 Computer Any desktop One computer
System with basic system for each
configuration student
2 Operating Windows
System 7/Windows 8/
Windows
10/LINUX or
any other
3 Software Tool Any UML tool

Practical Related Questions

1. What is SRS?
Ans:- A Software Requirements Specification (SRS) is a document that
describes the nature of a project, software or application. In simple words, SRS
document is a manual of a project provided it is prepared before you kick-start
a project/application. This document is also known by the names SRS report,
software document. A software document is primarily prepared for a project,
software or any kind of application.
2. Explain benefits of SRS document.
Ans:-
Benefits of SRS document :-
• It provides client a satisfaction as this is the first response to the client.
• It defines functional and non-functional requirement.
• It eliminates any confusion or misunderstanding on initial stage.
 • It reduces development effort.
• It reduces the chances of requirement creep.
• It makes testing easier.
• It defines project scope.
• It provides the basis for plan charter, work load, dependencies, etc.

3. Explain different fields in test case writing.

Ans:-
1. Functionality Test Case
Test case functionality is used to determine whether the interface of the
application works with the rest of the system and its users. The tests reveal that
the software has succeeded or failed to perform the functions. The cases include
a type of black-box evaluation, which uses the code under review for its
structure, requirements or user background. It allows the experiments to be
performed without the need for access to the software’s function or internal
structures. The QA team usually writes operational test cases because the work
is part of normal Quality assurance processes. You can write and run when a
first function is provided for testing in the development. They can be written
beforehand if each tester has access to the requirements to help manage the
development.

2. Interface Test Case

The aim of this GUI test is to check the GUI according to client requirements.
Detailed design report and GUI mockup screens discuss the intended GUI of
the device. The GUI Testing involves the width of the buttons and the fields in
which all text, tables, and columns are aligned in the display. It also validates
the interface of the request, validates that the site does not differ when choosing
different menu items and lists. After the mouse has moved to the menu or sub-
menus, the configuration stays the same.
 3. Unit Test Case
The testing is referred to as unit testing for a particular software component or
module. This usually happens by the developer and not by the tester, because
the program design and implementation need thorough knowledge. The design
of test drivers or test harnesses may also be appropriate.

4. Integration Test Case

The testing of all merged modules is called integration testing in order to verify
the combined functionality after integration. Usually, the modules are program
modules, individual programs, network client and server applications, etc. It
type of test is particularly important for client/server and systems distributed.

5. Performance Test Case

The terms ‘ pressure ‘ and ‘ load ‘ testing are sometimes used interchangeably.
Performance checks are carried out to decide if the device meets the
performance requirements. To do this analysis, various charging methods and
quality are used.

5. Security Test Case

Cases of safety tests help ensure that the software restricts activities and
permissions where necessary. Such test cases are created to protect data where
and when it needs protection. For penetration testing and other forms of safety-
based tests, protection test cases are used. The emphasis on security test cases
is often authentication and encryption. The security staff usually writes and
executes this assignment.

6. Database Test Case

Database test cases analyze what is taking place in the background. The UI is
clean and all appears to work but where is all this information going? The
database tables, and the stored procedures in order to write such test cases.
Many SQL queries are used by the test team to build test cases in the database.
Database assessments are used to check that the programmer writes the code
in such a way that the data are kept consistent and secure.

7. Usability Test Case

Functionality analysis is done to check functionality. The app flexibility is
checked to see whether new users can easily understand the software or not and
if a user is confused at any point proper support is recorded. In principle, this
experiment checks machine navigation.

4. Write test cases for testing login functionality of any web application,
Ans:- Following is the possible list of functional and non-functional test cases
for a login page:

Functional Test Cases

Sr. Functional Test Cases Type- Negative/
No. Positive Test
Case

1 Verify if a user will be Positive

able to login with a valid
username and valid
password.

2 Verify if a user cannot Negative

login with a valid
username and an invalid
password.

3 Verify the login page for Negative

both, when the field is
blank and Submit button
is clicked.
4 Verify the ‘Forgot Positive
Password’ functionality.

5 Verify the messages for Positive invalid

login.

Sr. Functional Test Cases Type- Negative/

No. Positive Test
Case

6 Verify the ‘Remember Positive

Me’ functionality.

7 Verify if the data in Positive

password field is either visible as
asterisk or bullet signs.

8 Verify if a user is able to Positive

login with a new
password only after
he/she has changed the
password.

9 Verify if the login page Positive

allows to log in simultaneously with
different credentials in a different
browser.

10 Verify if the ‘Enter’ key Positive

of the keyboard is
working correctly on the
login page.

Other Test Cases

 11 Verify the time taken to Performance &
log in with a valid Positive Testing
username and password.

12 Verify if the font, text UI Testing & color,

and color coding Positive Testing
of the Login page is as
per the standard.

Sr. Functional Test Cases Type- Negative/

No. Positive Test
Case

13 Verify if there is a Usability Testing

‘Cancel’ button available
to erase the entered text.

14 Verify the login page and Browser all

its controls in Compatibility & different
browsers Positive Testing.

Non-functional Security Test Cases:

Sr. Security test cases Type-
No. Negative/
Positive
Test Case

1 Verify if a user cannot Negative enter

the characters more than the specified
range in each field (Username and
Password).
2 Verify if a user cannot Positive
enter the characters more
than the specified range in
each field (Username and
Password).

3 Verify the login page by Negative

pressing ‘Back button’ of the browser.
It should not allow you to enter into
the system once you log out.

Sr. Security test cases Type-

No. Negative/
Positive
Test Case

4 Verify the timeout Positive

functionality of the login
session.

5 Verify if a user should not Negative

be allowed to log in with different
credentials from the same browser at
the same time.

6 Verify if a user should be Positive

able to login with the same
credentials in different
browsers at the same time.

7 Verify the Login page Negative against

SQL injection attack.

8 Verify the implementation Positive

of SSL certificate.
 PRATICAL:-10

Identify risks involved in the project and prepare RMMM plan.

Resources Required:-

Sr. Name of Specification Quantity

No. Resource
1 Computer Any desktop One computer
System with basic system for each
configuration student
2 Operating Windows
System 7/Windows 8/
Windows
10/LINUX or
any other
3 Software Tool Any UML tool

Practical Related Questions

1. What are the software Risks?
Ans:-
Risk 1: Inherent Schedule Flaws
Explanation: Software development, given the intangible nature and
uniqueness of software, is inherently difficult to estimate and schedule.
Risk 2: Requirements Inflation
Explanation: As the project progresses more and more features that were not
identified at the beginning of the project emerge that threaten estimates and
timelines.
 Risk 3: Employee Turnover
Explanation: Key personnel leave the project taking critical information with
them that significantly delays or derails the project. Risk 4: Specification
Breakdown
Explanation: When coding and integration begin it becomes apparent that the
specification is incomplete or contains conflicting requirements. Risk 5: Poor
Productivity
Explanation: Given long project timelines, the sense of urgency to work in
earnest is often absent resulting to time lost in early project stages that can
never be regained.

2. What is risk management in software development?

Ans:- Risk management means risk containment and mitigation. First, you’ve
got to identify and plan. Then be ready to act when a risk arises, drawing upon
the experience and knowledge of the entire team to minimize the impact to the
project.

3. Explain RMMM and RMMM plan.

Ans:-
RMMM and RMMM plan :-
A risk management technique is usually seen in the software Project plan.
This can be divided into Risk Mitigation, Monitoring, and Management Plan
(RMMM). In this plan, all works are done as part of risk analysis. As part of
the overall project plan project manager generally uses this RMMM plan. In
some software teams, risk is documented with the help of a Risk Information
Sheet (RIS). This RIS is controlled by using a database system for easier
management of information i.e creation, priority ordering, searching, and other
analysis. After documentation of RMMM and start of a project, risk mitigation
and monitoring steps will start.
 PRATICAL:-11

Evaluate size of the project using Function point metric for the
assigned project.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions

1. What is estimation techniques?
Ans:- An estimate is a rough calculation of something. For example, a project
cost estimate is a general idea of how much it will cost to complete a project.
Estimation techniques are ways to create project estimates. When your client
or another project stakeholder asks you to estimate an aspect of the project,
these techniques help you come up with a realistic number to give them.
 2. What are Function points in software engineering?
Ans:- A Function Point (FP) is a unit of measurement to express the amount of
business functionality, an information system (as a product) provides to a user.
FPs measure software size. They are widely accepted as an industry standard
for functional sizing. For sizing software based on FP, several recognized
standards and/or public specifications have come into existence.

3. How many Information Domain Values are used for Function Point
Computation?
Ans:- The five values are: External Inputs, External Outputs, External
Inquiries, Internal Logical Files and External Interface Files.
 PRATICAL: -12

Estimate cost of the project using COCOMO/COCOMO II

approach for the assigned project.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions

1. Explain COCOMO II Model.
Ans:- COCOMO-II is the revised version of the original Cocomo
(Constructive Cost Model) and is developed at University of Southern
California. It is the model that allows one to estimate the cost, effort and
schedule when planning a new software development activity.

2. What is cost estimation?

Ans:- Cost estimation in project management is the process of forecasting the
cost and other resources needed to complete a project within a defined scope.
Cost estimation accounts for each element required for the project and
calculates a total amount that determines a project’s budget.

3. What is LOC in cost estimation?

Ans:- The LOC (Line of Code) is a product size metric in software engineering.
Here, the number of lines in the code are counted and based on the number of
lines the cost is calculated.
 PRATICAL:-13

Use CPM/PERT for scheduling the assigned project.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions

1. What is the project scheduling?
Ans:- A project schedule is a timetable that organizes project tasks, activity
durations, calendar start and end dates, and sets overall project milestones on
a timeline. Project schedules also define the team members and resources
needed to complete tasks.

2. What are scheduling techniques?

Ans:- Following are scheduling techniques :-
1. Mathematical analysis
a. Critical Path Method
 b. Program Evaluation and Review Technique (PERT)

2. Duration compression
a. Fast Tracking
b. Crashing

3. Simulation
4. Resource-Leveling Heuristics
5. Task List
6. Gantt Chart
7. Calendar

3. Can a project have two critical paths?

Ans:- The critical path method actually began by scheduling thousands of
inter-related tasks, which often ran parallel but eventually fed into each other
(known as the PERT method on the Navy’s Polaris program in the 1950s).
One critical path may not contain all the tasks necessary for project success.
More than one critical path may be required to account for other teams and
their projects. To determine how the duration of one project’s critical path
compares to other linked tasks, a number of critical paths need to be created
 PRATICAL:-14

Use Timeline charts/Gantt charts to track progress of the project.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions

1. What is Gantt chart?
Ans:- A gantt chart is a horizontal bar chart used in project management to
visually represent a project plan over time. Modern gantt charts typically show
you the timeline and status—as well as who’s responsible—for each task in the
project.

2. Is a Gantt chart a timeline?

Ans:- A Gantt chart is an upgraded version of a project timeline and project
calendar. It can do everything they can do, plus a whole lot more. For example,
with a Gantt chart timeline, you can easily find openings in your project
schedule for additional work.

3. What are the Advantages of Gantt Charts?

Ans:- Following Advantage of Gantt Charts :-
• It creates a picture of complexity. I am quite a fan of diagrams and charts.
We think in pictures. Therefore, if we can see complex ideas as a picture,
this will help our understanding.
• It organizes your thoughts. I am also a big fan of the concept of dividing
and conquering. A big problem is conquered by dividing it into
component parts. A Gantt chart will force you to do this.
• It demonstrates that you know what you’re doing. When you produce a
nicely presented Gantt chart with high level tasks properly organized and
resources allocated to those tasks, it speaks volumes about whether you
are on top of the needs of the project and whether the project will be
successful.
• It (should) help you to set realistic time frames. The bars on the chart
indicate in which period a particular task or set of tasks will be
completed. This can help you to get things in perspective properly. And
when you do this, make sure that you think about events in your
organization that have nothing to do with this project that might consume
resources and time.
• It can be highly visible. It can be useful to place the chart, or a large
version of it, where everyone can see it. This helps to remind people of the
objectives and when certain things are going to happen. It is useful if
everyone in your enterprise can have a basic level of understanding of
what is happening with the project even if they may not be directly
involved with it.
 PRATICAL:-15

Prepare SQA plan that facilitates various attributes of quality of

process.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions

1. What is software quality plan?

Ans:- Software quality assurance (SQA) is a process which assures that all
software engineering processes, methods, activities and work items are
monitored and comply against the defined standards. These defined standards
could be one or a combination of any like ISO 9000, CMMI model, ISO15504,
etc. SQA incorporates all software development processes starting from
defining requirements to coding until release. Its prime goal is to ensure quality.
 2. Explain different steps to develop SQA plan.
Ans:-
Step 1) Identify the role and responsibilities of SQA team.
Step 2) List of the work products that the SQA auditor will review and audit.
Step 3) Create the schedule to perform the SQA tasks.
 PRATICAL: -16

Prepare SQA plan that facilitates various attributes of quality of

product.

➢ Resources Required:

Sr. No. Name of Resources Specification Quantity

One computer
Any desktop with basic
1 Computer System system for each
configuration
Student

Windows 7/ Windows 8/
2 Operating System Windows 10/ LINUX or
any other

3 Software Tool Any UML Tool

Practical Related Questions:

1. What are the activities of quality assurance?
Ans:- Quality assurance (QA) activities are those actions the project team takes
to inspect quality requirements, audit the results of control measurements and
analyze quality performance in order to ensure that appropriate quality
standards and procedures are appropriately implemented within the project.
 2. What is difference between process and product?
Ans:-

Sr.NO Product Process

While process is a set of sequence steps

Product is the final production
1 that have to be followed of create a
of the project.
project.

A product focuses on the final Whereas the process is focused on

2
result. completing each step being developed.

In case of product, the firm In contrast, the process constantly

3
guidelines are followed. follows guidelines.

A product is tend to be short Whereas the process is tend to be long

4
term. term.

The main goal of the product is While The purpose of the process is to
5 to complete the work make better the quality of the project.
successfully.