NAME: JUILI MARUTI KADU

TE A ROLL NO: 19
UID: 118CP1102B
SUB: SOFTWARE ENGINEERING

Experiment No. 1

Aim: To write a Problem Statement for CODERS HELPMATE Project.

Problem Statement:
The purpose of the project entitled as “CODERS HELPMATE” to develop
webapplication which is user friendly, simple and fast. As a beginner a person
dont have knowledge about how to start learning programming languages ,
from where to start . So we have come up with this project , here we have
tried to bring course material under one roof which is need for learning
programming language . We have used Django framework to develop this
application. Here user need to first register himself into website and after that
he would be able to access our website. We have put tutorial, documentation
,video for better understanding . For register we have use email authentication
.
.

Conclusion: The problem statement of project was written successfully by

following the steps
described above.

Questionnaire:
1.What does RAD stand for?

Ans: The Rapid Application Development (or RAD)

2. What software development model is not suitable for accommodating any
change?
Ans: Waterfall Model

3. What is software engineering?

Ans: Software engineering is an engineering branch associated with
development of software product using well-defined scientific principles,
methods and procedures.

4. What is problem statement?

Ans: A problem statement is a clear description of the issue (s), it includes a
vision, issue statement, and method used to solve the problem.

5. What is the most important phase of spiral model ?

Ans: Risk analysis is the most important stage of the spiral model.

6. What is incremental model?

Ans: Incremental Model is a process of software development where
requirements are broken down into multiple standalone modules of software
development cycle.

7. What is agile methodology?

Ans: Agile is a software development methodology to build a software
incrementally using short iterations of 1 to 4 weeks so that the development is
aligned with the changing business needs .

8. What is prototype model?

Ans: The Prototyping Model is a Systems Development Methodology (SDM)
within which a paradigm output (or an early approximation of a final system or
product) is constructed, tested, and then reworked.
9. What is evolutionary model?
Ans: Evolutionary model is a combination of Iterative and Incremental model
of software development life cycle.

10. Which development model is best when user requirements are not clear?
Ans: The Prototyping Model should be used when the requirements of the
product are not clearly understood or are unstable.
 EXPERIMENT NO : 02

Aim: To write SRS in IEEE format for Coders Helpmate.

Introduction :
"CODERS HELPMATE" is an online platform where students can come learn the
basics of programming language and how to get started in this field through
online . As a beginner a person dont have knowledge about how to start
learning programming languages , from where to start . So we have come up
with this project , here we have tried to bring course material under one roof
which is need for learning programming language . We have used Django
framework to develop this application. Here user need to first register himself
into website and after that he would be able to access our website. We have
put tutorial, documentation ,video for better understanding . For register we
have use email authentication .

❖ Software requirement:
1. Operating system: Windows 7 is used as the operating system as it
is stable and supports more features and is more user friendly.
2. Front end:
• Html
• Css
• Bootstrap
3. Backend :
• Python Django
• SQlite(database)

❖ Hardware requirement:
1. RAM – 4GB
2. Monitor
3. Mouse
 4. Keyboard
5. Processor- INTEL

Conclusion: Thus SRS( Software Requirement Specification) document in

IEEE (Institute of Electrical and Electronics Engineers) format for Coder’s
Helpmate project is designed successfully.

Questionnaire:

1. What is SRS document?

A software requirements specification (SRS) is a document that describes what
the software will do and how it will be expected to perform. It also describes
the functionality the product needs to fulfill all stakeholders (business, users)
needs.

2. What are the components of SRS document?

Functional Requirements, Performance Requirements (Speed Requirements),.
Design Constraints ETC.

3. What is functional requirement?

The purposeful requirements part discusses the functionalities needed from
the system, The system is taken into account to perform a group of high- level
functions Fi.

4. What are non-functional requirements?

Non-functional necessities accommodate the characteristics of the system
which may not be expressed as functions – like the maintainability of the
system, movability of the system, the usability of the system, etc.

5. What are different types of constraints in developing the software?

Policy constraint, people constraint, market constraint, paradigm constraint
and equipment constraint.

6. What is the significance of SRS document?

This gives the purpose of the SRS document, not the software itself. It also
states how much of the software is covered by the document, particularly
saying whether it describes the entire software system or only a part of it. It
also states the intended readers of the document.

7. What are different requirement gathering techniques?

Document analysis, focus group, interface analysis, brainstorming etc.

8. What is the difference between requirement analysis & requirement

specification ?
The difference is that requirement is an analysis artifact. The specification is a
design artifact.
In a final as-built documentation, you will typically find the word
"specification", instead of "requirement", since the requirements have been
converted to specifications.

9. Time limit of a software is functional requirement or non-functional

requirement?
Non- functional.
 Experiment No : 3

Aim: Use project management tool to schedule project plan.

Conclusion:Thus Project Management tool has been used to estimate &

schedule the CODER HELPMATE project.

Questionnaire:
1. What is software project management?
➢ Software Project Management (SPM) is a proper way of planning and
leading software projects. It is a part of project management in which
software projects are planned, implemented, monitored and controlled.

2. What are different types of designs in a software project?

➢ Designing is to think of how you will structure your project: what
subsystems, components, modules, but also what classes, functions and
variables it will consist of. Software design is a process of problem
solving and planning for a software solution.

3. What are the activities of project management?

➢ Software project management comprises of a number of activities,
which contains planning of project, deciding scope of software product,
estimation of cost in various terms, scheduling of tasks and events, and
resource management. Project management activities may include:
Project Planning, Scope Management, Project Estimation.

4. What is project breakdown structure?

➢ The work breakdown structure (WBS) is a vehicle for breaking an
engineering project down into subproject, tasks, subtasks, work
 packages, and so on. Whereas the WBS has been widely used in many
other engineering applications, it has seemingly only rarely been
formally applied to software projects, for various reasons.

5. What is risk analysis?

➢ In Software Testing, risk analysis is the process of identifying the risks in
applications or software that you built and prioritizing them to test.
After that, the process of assigning the level of risk is done. The
categorization of the risks takes place, hence, the impact of the risk is
calculated.

6. What is COCOMO model?

➢ Cocomo (Constructive Cost Model) is a regression model based on LOC,
i.e number of Lines of Code. It is a procedural cost estimate model for
software projects and often used as a process of reliably predicting the
various parameters associated with making a project such as size, effort,
cost, time and quality. It was proposed by Barry Boehm in 1970 and is
based on the study of 63 projects, which make it one of the best-
documented models.

7. How to estimate efforts?

➢ The Estimation Process. 1- Scoping. You need first to scope the project
even if you do not have the full detailed requirements but you can
assume some of them or add margins later. 2- Decomposition. 3- Sizing.
4- Expert and Peer Review. 5- Estimation Finalization.

8. What are different cost estimation methods?

➢ Methods for estimation in software engineering include these
principles:Analysis effort method, Parametric Estimating, The Planning
Game.

9. What is empirical estimation method?

➢ Empirical estimation is a technique or model in which empirically
derived formulas are used for predicting the data that are a required and
essential part of the software project planning step. In this technique, an
educated guess of project parameters is made. Hence, these models are
based on common sense.
 Experiment No : 4

Aim: RMMM (Risk Mitigation, Monitoring & Management) plan for the
CODERS HELPMATE project.

Results:

Description:
• Database is updated frequently.
• Higher complexity.
• Need to be updated as technique gets updated.
Refinement/ Context:
• Reduced efficiency because of network congestion during peak hours (Eg:- During
offers/festivals)
• Due to higher complexity of database it is harder to find the exact problem.
Mitigation/Monitoring:
• Consistency of database needs to be maintained.
• Testing of each module should be done .
Contingency plan and Trigger:
• As computed the risk exposure to be Rs30,000,000.
• Experts and technicians should be available 24*7 .

Status/Date
• Description step analyzed.
• Refinement step initiated.

Components category Performance Support Cost Schedule

Failure results in increse cost and

Failure to meet the requirement
1 schedule delays with expected values
would result in mission failure
in excess of $500k

Catastrophic Significant
significant
degredation to Nonresponsive or
finiancial shortages
2 non achievement Unsupportable Unachivable IOC
budget overrun
of technical software
likely
performance
 Failure to meet the requirement
Failure results in operational delays
would degrade systeam performance
1 and/or increase cost with expected
to a point where mission sucess is
value of $100k to $500k
Critical questionable

Some reduction Minor delays in Some shortages of

possible slippage
2 in technical sftware financial resources,
in IOC
performance modification possible overruns

Failure to meet the requiremnt would Cost impacts and/or recoverable

1 result in degredation of secondary schudele slips with expected value of
mission $1k to $100k
Marginal Minimal to small
Realistic
reduction Responsive Sufficient finiancial
2 achievable
intechnical software support resources
schedule
performance

Failure to meet the requirement Error results in minor cost and/or

1 would create inconvinance or schedule impactwith expected value
nonoperational impact of less than $1k
Negligible
Easily
No reduction in Possible Budget Early achivable
2 supportable
technical performance underrun IOC
software

Risks Category Probablity Impact

Size estimate may be significantly low PS 60% 2

large number of users than planned PS 30% 3

less reuse than plan PS 70% 2

enduser resist system BU 40% 3

delivery deadline will be tightened BU 50% 2

funding will be lost CU 40% 1

customer will chang requirements PS 80% 2

technology will not meet expection TE 30% 1

lock og training on tools DE 80% 3

staff inexperienced ST 30% 2

staff turnover will be high ST 60% 2

 Impact values : 1-Catastrophic ,2-Critical,3-Marginal,4-Negligible

Conclusion: Thus Risk Mitigation, Monitoring and Management Plan has been
prepared successfully for the coder’s helpmate project.

Questionnaire:

1. What is full form of RMMM?

➢ RMMM-Risk Management, Mitigation and Monitoring.

2. What is risk mitigation?

➢ Risk mitigation planning is the process of developing options and actions
to enhance opportunities and reduce threats to project objectives [1].
Risk mitigation implementation is the process of executing risk
mitigation actions.

3. What is risk management?

➢ A software project can be concerned with a large variety of risks. In
order to be adept to systematically identify the significant risks which
might affect a software project, it is essential to classify risks into
different classes. The project manager can then check which risks from
each class are relevant to the project.

4. What is risk monitoring?

➢ Risk monitoring is the process which tracks and evaluates the levels of
risk in an organisation. As well as monitoring the risk itself, the discipline
tracks and evaluates the effectiveness of risk management strategies.
The findings which are produced by risk monitoring processes can be
 used to help to create new strategies and update older strategies which
may have proved to be ineffective.

5. What is risk projection?

➢ Risk projection, also called risk estimation, attempts to rate each risk in
two ways the likelihood or probability that the risk is real and the
consequences of the problems associated with the risk, should it occur.

6. What is slack time?

➢ Slack time is an interval that occurs when there are activities that can be
completed before the time when they are actually needed. The
difference between the scheduled completion date and the required
date to meet the critical path is the amount of slack time available.

7. What is cost slippage?

➢ In project planning, a slippage is the act of missing a deadline. It can be
an arbitrary milestone put in place to help track progress. To avoid
slippage, one must plan his or her projects (especially research) carefully
to avoid delays in schedule.

8. Which software development model does handle risks effectively?

➢ For most software development projects, we can define five main risk
impact areas: New, unproven technologies.
User and functional requirements . Application and system architecture.
Performance. Organizational

9. What are different risk mitigation technologies?

• New, unproven technologies.
• User and functional requirements.
• Application and system architecture.
• Performance.
• Organizational
 Experiment No : 5

Aim: To Design Data Flow Diagrams for CODERS HELPMATE.

Results:

Conclusion: Thus Data Flow Diagram for the CODERS HELPMATE System is
drawn successfully.

Questionnaire:

1.What is DFD?
Ans: Data flow diagrams are used to graphically represent the flow of data in a
business information system. DFD describes the processes that are involved in
a system to transfer data from the input to the file storage and reports
generation.

2.What is context diagram?

Ans: A context diagram (CD) in engineering is a diagram that defines the
boundary between the system, or part of a system, and its environment,
showing the entities that interact with it. This diagram is a high level view of a
system.

3.Compare between data flow & control flow?

Ans: Control Flow:
a.Process is the key: precedence constraints control the project flow based on
task completion, success or failure.
b.Task 1 needs to complete before task 2 begins.
c.Smallest unit of the control flow is a task.
d.Control flow does not move data from task to task.
Data Flow:
a.Unlink control flow, multiple components can process data at the same time.
b.Smallest unit of the data flow is a component.
c.Data flows move data, but are also tasks in the control flow, as such, their
success or failure effects how your control flow operates.
d.Data is moved and manipulated through transformations.

4.What are different symbols used in DFD?

Ans: Data Flow Diagram symbols are standardized notations, like
rectangles, circles, arrows, and short-text labels, that describe a system
or process' data flow direction, data inputs, data outputs, data storage points,
and its various sub-processes.
5.What is 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 entities.

6.What is the difference between data flow & control flow?

Ans: Control Flow:
a.Process is the key: precedence constraints control the project flow based on
task completion, success or failure.
b.Task 1 needs to complete before task 2 begins.
c.Smallest unit of the control flow is a task.
d.Control flow does not move data from task to task.
Data Flow:
a.Unlink control flow, multiple components can process data at the same time.
b.Smallest unit of the data flow is a component.
c.Data flows move data, but are also tasks in the control flow, as such, their
success or failure effects how your control flow operates.

7.What is the significance of DFD?

Ans: The objective of a DFD is to show the scope and boundaries of a system as
a whole. It may be used as a communication tool between a system analyst
and any person who plays a part in the order that acts as a starting point for
redesigning a system.

8.Which symbol is used to store data in DFD?

Ans: Data stores is represented with an arrow symbol, which indicates the
direction of flow.
 Experiment No : 6

Aim: To Design A Use Case Diagrams for CODERS HELPMATE.

Results:

Conclusion: Thus use case diagrams for CODERS HELPMATE drawn

successfully.

Questionnaire:

1. What is use case ?

➢ A use case is a list of actions or event steps typically defining the
interactions between a role (known in the Unified Modeling
Language (UML) as an actor) and a system to achieve a goal.

2. What are different symbols used in use case diagram?

➢ a. System Domain Box.

b. Actor Figure.
c. Goal Oval.
d. Actor Initiator Arrow.
e. Actor Connector Line.

3. What is an actor?

➢ An actor can be a person, an organization, or an outside system that

interacts with your application or system.

4. What is use case?

➢ A use case is a list of actions or event steps typically defining the

interactions between a role (known in the Unified Modeling
Language (UML) as an actor) and a system to achieve a goal.

5. What is the need of use case diagram?

➢ Use case diagram is one of them and its specific purpose is to gather
system requirements and actors. Use case diagrams specify the events
of a system and their flows

6. What is UML?

➢ UML short for Unified Modeling Language, is a standardized modeling

language consisting of an integrated set of diagrams, developed to help
 system and software developers for specifying, visualizing, constructing,
and documenting the artifacts of software systems, as well as for
business modeling and other non-software systems.

7. Which symbol is used to represent the relationship between use case &
actor?

➢ The Goal Oval represents the user's goal or the reason for the
primary actor's interaction with the system domain.

8. What are different types of relationships?

• Association between actor and use case.

• Generalization of an actor.
• Extend between two use cases.
• Include between two use cases.
• Generalization of a use case.

9. What is use case?

➢ A use case is a list of actions or event steps typically defining the

interactions between a role (known in the Unified Modeling
Language (UML) as an actor) and a system to achieve a goal.

10. What are different symbols used in use case diagram?

➢ a.System Domain Box.

b.Actor Figure.
c. Goal Oval.
d. Actor Initiator Arrow.
e. Actor Connector Line
11.What is an actor?

➢ An actor can be a person, an organization, or an outside system that

interacts with your application or system.

12.What is use case?

➢ A use case is a list of actions or event steps typically defining the

interactions between a role (known in the Unified Modeling
Language (UML) as an actor) and a system to achieve a goal.

13.What is the need of use case diagram?

➢ Use case diagram is one of them and its specific purpose is to gather
system requirements and actors. Use case diagrams specify the events
of a system and their flows

14.What is UML?

➢ UML short for Unified Modeling Language, is a standardized modeling

language consisting of an integrated set of diagrams, developed to help
system and software developers for specifying, visualizing, constructing,
and documenting the artifacts of software systems, as well as for
business modeling and other non-software systems.

15.Which symbol is used to represent the relationship between use case &
actor?
➢ The Goal Oval represents the user's goal or the reason for the
primary actor's interaction with the system domain.

16.What are different types of relationships?

o Association between actor and use case.

o Generalization of an actor.
o Extend between two use cases.
o Include between two use cases.
o Generalization of a use case.
 Experiment No: 7

Aim: To design a State chart Diagrams for CODERS HELPMATE.

Result:

Conclusion: Thus State chart diagram has been prepared successfully for the
CODERS HELPMATE.

Questionnaire:

1. Mention the essential of the sequential diagram

➢ It mainly describes the method calls from one object to another, and this
is also the actual scenario when the system is running.

2. What is the purpose of the Interaction diagram?

➢ The purpose of interaction diagrams is to visualize the interactive
behavior of the system. Visualizing the interaction is a difficult task.
Hence, the solution is to use different types of models to capture the
different aspects of the interaction.

3. Define Object.
➢ An object can be a variable, a data structure, a function, or a method, and
as such, isa value in memory referenced by an identifier.

4. What are the two types of Interaction diagram?

➢ Two types of interaction diagrams in UML.
a. The sequence diagram captures the time sequence of the message flow
from one object to another.
b. the collaboration diagram describes the organization of objects in a
system taking part in the message flow

5. Define Message.
➢ A message specifies a sender and receiver, and defines the kind of
communication that occurs between lifelines.
 Experiment No : 8

Aim: To Design Sequence Diagrams for CODERS HELPMATE.

Result:
Conclusion: Thus Sequence diagram has been prepared successfully for the
CODERS HELPMATE.

Questionnaire:

1. Mention the essential of the sequential diagram?

➢ The sequence diagram is a good diagram to use to document a system's
requirements and to flush out a system's design. The reason the
sequence diagram is so useful is because it shows the interaction logic
between the objects in the system in the time order that the
interactions take place.

2. What is the purpose of the Interaction diagram?

➢ The purpose of interaction diagrams is to visualize the interactive
behavior of the system. Visualizing the interaction is a difficult task.
Hence, the solution is to use different types of models to capture the
different aspects of the interaction.

3. Define Object.
➢ An object is a software bundle of variables and related methods. You can
represent real-world objects using software objects. Everything that the
software object knows (state) and can do (behavior) is expressed by the
variables and methods within that object.

4. What are the two types of Interaction diagram?

➢ We have two types of interaction diagrams in UML. The sequence
diagram captures the time sequence of the message flow from one
object to another and the collaboration diagram describes the
organization of objects in a system taking part in the message flow.

5. Define Message.
➢ A message is the way that one program object requests an action from
another object. A message specifies the name of the object to which the
request is made, the action (or method ) to be performed, and any parameter
or value that needs to be specified for this request.
 EXPERIMENT NO : 10

Aim: Develop test cases for white box testing.

TEST CASES:

Sr. Pre Steps Input Actual Status

Test Expect
no Test case Requisite data result
case ed
Objectiv e
ID result

1 TC-1 To Valid 1)valid User Should Logged Pass

verify user usernam nam Log in in
the login name e 2)enter e& successf success
function & valid pass ully fully
ality of passwo passwor word
login rd d
page

2 TC-2 A-z 1)userna Usern There Logged Pass

To
0-9 me ame should be in
check that
Special 2)passwor &pass No null success
null
charact d word value fully
values Are
ers
not
accepte
d

3 TC-3 To check Proper Internet On Should Pass

internet the Inter
proper should be have
connecti intern net
internet on proper
on et conn
connecti internet
ected
vity connect
succe
ivity
ssfull
y
4 TC-4 To check Authori Proper Should not Login Failed
Enter
only zed users registra login for failed
name
authorize tion unauthori for
no,
d user before zed users unaut
login in id horize d
should be
,pass users
able to
word
login then
click
on to
save
butto
n

5 TC-5 To check Proper Enter Data Data Pass

account register proper 1)Ente Should be saved
created or ation details r saved and
not name And accou
2)Ente accoun nt
r pwd t create
3)ente should be d
r created
addre
ss 4)
enter
mobil
e no

Questionnaire:

1. What is white box testing?

➢ White Box Testing is a software testing method in which the
internal structure/ design/ implementation of the item being
tested is known to the tester.

2. What is cyclomatic complexity?

➢ Cyclomatic complexity is a software metric used to indicate the
complexity of a program. It is a quantitative measure of the
number of linearly independent paths through a program's source
code.

3. What is path coverage?

➢ Path testing is a structural testing method that involves using the
source code of a program in order to find every possible executable
path. It helps to determine all faults lying within a piece of code. ...
In order to reduce the redundant tests and to achieve maximum
test coverage, basis path testing is used.

4. What is the significance of white box testing?

➢ White box testing is useful for component, integration and
system testing and enables identification of errors in code
syntax, logic, data flow and conditions.

5. What is a test case?

➢ A test case is a set of conditions under which a tester will
determine whether an application, software system or one of its
features is working as it was originally designed to.

6. Compare White box & Black box testing

Black box testing White box testing

 Black Box Testing is a software White Box Testing is a software
testing method in which the internal testing method in which the
structure/ design/implementation of internal structure/
the item being tested is NOT known design/implementation of the
to the testerAlso called behavioural item being tested is known to
testing the tester.Also called glass box
testing

Mainly applicable to higher levels Mainly applicable to lower levels

of testing: of testing:
- Acceptance Testing - Unit Testing
- System Testing - Integration Testing

Generally, independent Software Generally, Software Developers

Testers

Not Required Required

7. How to calculate number of independent paths in a module?

➢ There are then three equations that you can use to calculate the
independent paths.

1. Independent Paths = Edges – Nodes + 2.

2. Independent Paths = Regions + 1.
3. Independent Paths = Decisions + 1.

8. What is boundary value analysis ?

➢ Boundary value analysis is a process of testing between the
extreme ends or boundaries of input values. The basic idea of
selecting the boundary testing is selecting the input values at
 their Minimum, just above the Minimum, a nominal value, just
below the maximum, a maximum.

9. What is statement coverage?

➢ Statement Coverage is a white box testing technique in which all
the executable statements in the source code are executed at
least once. It is used for calculation of the number of statements
in source code which have been executed. ... Based on the input
to the program, some of the code statements may not be
executed.