This document describes a summer industrial training project to develop an online SQL forum. It includes sections on functional and system requirements, hardware and software specifications, data modeling diagrams, use cases, screen shots, testing approaches, future enhancements, and references. A group of students developed the online application to allow users to ask and answer SQL questions, with an admin able to moderate content.

1. Summer Industrial Training
Presented By –
Name – SUBRATA DAS , Reg. ID. - AC/SVT/SLT-482
Name – SWARNENDU ROY, Reg. ID. –AC/SVT/SLT-275
Name- SUSANTA KUNDU, Reg. ID. – AC/SVT/SLT-276
Name – UTSAB BHANDARY, Reg. ID. –AC/SVT/SLT-484
Name – SNEHASISH KARMAKAR, Reg. ID.- AC/SVT/SLT-378

2. Table of Contents
 ABSTRACT
 INTRODUCTION
 FUNCTIONAL REQUIREMENTS
 SYSTEM REQUIREMENTS
 HARDWARE REQUIREMENT SPECIFICATION
 SOFTWARE REQUIREMENT SPECIFICATION
 E-R DIAGRAM/DATA FLOW DIAGRAM/CLASS DIAGRAM/SEQUENCE DIAGRAM
 USE CASE DIAGRAM
 SCREEN SHOTS
 TABLE
 FUTURE SCOPE
 CONCLUSION
 REFERENCES

3. Abstract
 This project is aimed at developing an
online forum that is of importance to any
kind of users. The system is an online
application that can be accessed by
everyone. This system can be used as a
knowledge/information for the anyone.
Users logging in should be able to upload
any kind of Sql questions. Users logging in
may also access/search any information
put up by others. Admin can edit users’
information and their posts if necessary.

4. Introduction
A person should be able to
An admin should be able to
 Search documents from the
first page (only read
access)
 Register with SQL page
 Login to the SQL page
 Upload documents
 Browse documents
 View document
 Login to the the SQL
page
 Approve uploads
 Remove uploads
 Suspend document
 Browse documents
 View document

5. Functional Requirements
 Functional Requirements are those that
refer to the functionality of the system, i.e.,
what services it will provide to the user.
Nonfunctional (supplementary)
requirements pertain to other information
needed to produce the correct system and
are detailed separately.

6. SYSTEM REQUIREMENTS
Hardware Requirement Specification
Client Machine Server Machine
HDD 80GB
Processor Pentium 4
Memory 2 GB
HDD 500 GB
Processor Dual Core
Memory 4GB

7. Software Requirement
Specification
Client Machine Server Machine
Browser Google Chrome
browser with C#
interpreter
Client side mark
up / scripting
languages
HTML, CSS,C#
Software VISUAL
STUDIO2013
Database
Management
System Software
SQL server
Specification ASP

8. E-R DIAGRAM

9. USE CASE DIAGRAM

10. DATA FLOW DIAGRAM
 Level 0

11. Level 1

12. SCREEN SHOT

13. SCREEN SHOT

14. SCREEN SHOT

15. ALL_POSTS
SCREEN SHOT

16. SCREEN SHOTS

17. SCREEN SHOTS

18. SCREEN SHOT

19. SCREEN SHOT

20. SCREEN SHOT

21. SCREEN SHOT

22. SCREEN SHOT

23. SCREEN SHOT

24. SCREEN SHOT

25. SCREEN SHOT

26. SCREEN SHOT

27. SCREEN SHOT

28. SCREEN SHOT

29. user my activities
SCREEN SHOT

30. SCREEN SHOT

31. SCREEN SHOT

32. SCREEN SHOT

33. SCREEN SHOT

34. Table: ANSWERS

35. Table: QUESTIONS

36. Table: UPLOADED

37. Table: USERS

38. Unit Testing
Unit Testing is done at the source or code level for language-specific
programming errors such as bad syntax, logic errors, or to test
particular functions or code modules. The unit test cases shall be
designed to test the validity of the programs correctness.
White Box Testing
In white box testing, the UI is bypassed. Inputs and outputs are
tested directly at the code level and the results are compared against
specifications. This form of testing ignores the function of the
program under test and will focus only on its code and the structure
of that code. Test case designers shall generate cases that not only
cause each condition to take on all possible values at least once, but
that cause each such condition to be executed at least once. To
ensure this happens, we will be applying Branch Testing. Because
the functionality of the program is relatively simple, this method will
be feasible to apply.

39. Black Box Testing
Black box testing typically involves running through every possible
input to verify that it results in the right outputs using the software as
an end-user would. We have decided to perform Equivalence
Partitioning and Boundary Value Analysis testing on our application.
System Testing
The goals of system testing are to detect faults that can only be
exposed by testing the entire integrated system or some major part of
it. Generally, system testing is mainly concerned with areas such as
performance, security, validation, load/stress, and configuration
sensitivity. But in our case well focus only on function validation and
performance. And in both cases we will use the black-box method of
testing.

40. FUTURE SCOPE
SQL forum has lot of enhancement options. In
future documents may be classified category-wise.
It may try to analyze the user behavior and
preferences and accordingly suggest document
categories.

41. CONCLUSION
While learning from experience is powerful thing, it is an
expensive pedagogical technique in the business world. It is
therefore helpful to understand the different types of
mistakes that users usually make while constructing the
DFD model of systems.

42. REFERENCES
Programmer’s Heaven C#
school(ebook)- Faraz Rasheed
http://www.w3schools.com/aspnet
/aspnet.asp

43. THANK YOU