.net

A
PROJECT REPORT
On
INDEED LEARNING
at TECHPILE TECHNOLOGY PVT. LTD., LUCKNOW
Submitted Towards Partial Fulfillment of
Fourth-Year of Bachelors in
Computer Science & Engineering
Under the supervision of

Mr. Rahul Soni
SUBMITTED TO: SUBMITTED BY:
Ashutosh Mall
(SR Institute of Management and Technology)
Session 2024-2025
1
Enroll No.: Techpile-ST240895
COMPLETION CERTIFICATE
This is to certify that Ashutosh Mall of B.TECH (Computer Science & Engineering) from
Government Girls Polytechnic Meja Prayagraj (Institute/University) was working on the project
entitled “Indeed Learing” developed on ".Net 'MVC’" in Techpile Technology Pvt. Ltd. She was
engaged with us during 5 August to 20 September for a period of 60 days.
He has done an excellent job during his engagement with the Software Development & Testing
Division of the company. He has completed his project during the training tenure. His performance has
been good and satisfactory.
I would like to take this opportunity to express my appreciation to Ashutosh Mall for his work and
wish him all the very best for his future endeavors.
Regards,
Divya Rai
PROJECT MANAGER
Techpile Technology Pvt. Ltd.
Lucknow (U.P.) Signature
2
PREFACE
Summer training is an important part of the engineering curriculum. The B.Tech course summer
training helps a student in getting acquainted with the manner in which His knowledge is being
practically used outside His institute and this is normally different from what He has learnt from
books. Hence, when the student switches from the process of learning to that of implementing his
knowledge, He finds an abrupt change. This is exactly why summer training session during the B.Tech
curriculum becomes all the more important. Summer training is prescribed for the student of Technical
College as a part of the three-year degree course of engineering by the BTEUP. We are required to
undergo summer training for a period of 60 days after the completion of the 3rd year.
This training report describes in detail the training after the 3rd year session, which I completed at the
Techpile Technology Pvt. Ltd... This report also gives the information about the organization and it’s
working along with the project undertaken in the training period.
The fundamental step used in SDLC process is based on the ISO 9001 guidelines. My aim was to
follow the ISO guidelines and develop a perfect system.
The system development was organized into 5 major parts:

1. Requirement Gathering
2. Documentation/Design
3. Development
4. Coding
5. Testing
3
ACKNOWLEDGEMENT
Apart from my effort, the success of the project depends largely on the encouragement and guidelines
of many others. We take this opportunity to express our gratitude to the people who express have been
instrumental in the successful completion of this project.
I would like to express my deep and sincere gratitude to my supervisor Mr. Rahul Soni Sir (Techpile
Technology Pvt. Ltd.), who gave me his full support and encouraged me to work in an innovative and
challenging project for Educational field. His wide knowledge and logical thinking gave me right
direction all the time.
I am deeply grateful my project coordinator for his help and support provided at every step of the
project.
Last but not the least, I thank to all employees of Techpile Technology Pvt. Ltd. for their support and
co-operation.
ASHUTOSH MALL
4
DECLARATION
This is to certify that the project report entitled “Indeed Learning” is done by me is an authentic work
carried out for the partial fulfillment of the requirements for the award of the B.Tech in “(Information
Technology& Engineering)”under the guidance of Mr. Rahul Soni. The matter embodied in this
project work has not been submitted earlier for award of any degree or B.Tech to the best of my
knowledge and belief.
ASHUTOSH MALL
5
INDEX
PAGE
1. Introduction……………………………………………………………………10-13
1.1. Overview of Organization……………………………………………………………………..10-10
1.2. Project Introduction……………………………………………………………………………10-11
1.3. Objectives……………………………………………………………………………………...11-11
1.4. Problem Definition…………………………………………………………………………….11-13
2. System Analysis..................................................................................................13-22
2.1. Objective………………………………………………………………………………………13-13
2.2. SDLC Phases……………………………………………………………………..……………13-13
2.2.1. Preliminary Investigation…………………………………………………….….………....…..13-15
2.2.2. System Analysis…………………………………………………………………..…………...15-15
2.2.3. System Design…………………………………………………………………..…………...…15-15
2.2.4. Coding…………………………………………………………………………..…………...…15-15
2.2.5. Testing…………………………………………………………………………………………15-16
2.2.6. Implementation………………………………………………………………………………...16-16
2.2.7. Maintenance……………………………………………………………………………………16-16
2.3. Process Description…………………………………………………………………………….17-17
2.4. Project Model Used……………………………………………………………………………..17-18
2.5. ER-Diagram……………………………………………………………………………………19-20
2.6. Data Flow Diagram…………………………………………………………………………….21-22
3. Software Hardware Requirement Specification……………………………..23-24

3.1. Hardware Requirement…………………………………………………………………………23-23
3.2. Server side Software Requirement……………………………………………………………..23-23
3.3. Client side Software Requirement……………………………………………………………...23-23
3.4. Support Maintenance…………………………………………………………………………...24-24
6
4. System Design Approach………………………………………………………24-24
4.1. Top-Down Designing……………………………………………………………………………24-24
4.2. Bottom –Up Designing…………………………………………………………………………25-25
4.3. Following Approach…………………………………………………………………………….25-25
5. Backend Design…………………………………………………………………26-26
5.1 Description of Classes and Methods (model.py)………………………………………………26-26
5.2 Defined URLs (urls.py)………………………………………………………………………...26-26
6. Data Modeling…………………………………………………………………..27-30
6.1. List of Tables

6.2. Structure of Tables
7. Testing……………………………………………………………………………31-35
8. Input-Output Forms……………………………………………………………..36-68
8.1. Project Screenshot………………………………………………………………………………..36-38
8.2. Project Coding……………………………………………………………………………………36-38
9. Future Scope…………………………………………………………………..…68-68
10. Conclusion……………………………………………………………………….68-68
7
LIST OF TABLES
PAGE
1. Group Table……………..………………………………………………………...27
2.Student Table……………..………………………………………………………...27
3.Batch Table...............…………………………………………………..…………..28
4......................................................................................Contact Table
....................…………………………………………………………..……….….29
5....................................................................... VideoCategory info
....................………………………………………………………………...30
6..................................................................................... Videos Table
................………………………………………………………………………..30
7............................................................................Assignment Table
.....................……………….……………………..………………….……….31
8...................................................................Submittedtask Table
......................……………………………………………………………...32
8
LIST OF FIGURES&SCREENSHOTS
PAGE
1. SOFTWARE DEVELOPMENT LIFE CYCLE……………………………….…16

2. DEVELOPMENT PHASES…………………………………………………….….18
3. E-R DIAGRAM………………………………………………………………….….20
4. ZERO LEVEL DATA FLOW DIAGRAM…………………………………….….22
5. ONE LEVEL DATA FLOW DIAGRAM…………………………………….……22
6. TOP-DOWN DESIGNING…………………………………………………………24
7. BOTTOM-UP DESIGNING………………………………………………………..24
8. ASSIGNMENT DETAILS………………………………………………………….28
9
1. INTROUCTION
1.1. Overview of Organization

Techpile is founded by some young engineers who have mastered the IT sector, whose objective is to
achieve the highest position in the IT sector across the country, who are trying to achieve this
objective by cooperating in various fields.
Techpile is an organization working in both software development and software training, which aims
to make all the specials of its client successful through their coding as well as to make students more
competent to work with a well reputed organization.
We are proud of our high-quality standards. These standards allow us to provide our customers with
reliable and error-free software applications, regardless of complexity. Our top-notch developers use
the latest software methodologies and technologies. This means that they can concentrate on our
clients' business goals and keep them involved in every stage through the entire project. Our
meticulous approach has helped us build our excellent track record with no failed or aborted projects.
We are in the business of change, managing complexity with an unparalleled insight, looking beyond
the horizon of IT with resources focused on solutions. Becoming successful is a skill but one cannot
perfect it without practice.
1.2. PROJECT INTRODUCTION:--
Assignment management system is a software that helps the teachers to schedule tasks and assign
them to the respective students.
Assignment management is one of the fundamental activities in education.
All the assignment and project are assigned with a start and end date, student update the task on
completion. Teachers can view status of task and reports are being generated after evolution . By using
our assignment management portal admin/teachers can upload the assignment to a specific group of
students. Students can be download and read the uploaded assignment. There is a facility to upload the
respective document after completion.
10
1.3. OBJECTIVE
 It is time saving and energy saving.
 Person can easily login to site while sitting on home.
 Person can buy more than one product without going anywhere.
 The transactions are executed in off-line mode, hence on-line data for Shopping, Internet
capture and modification is not possible.
 Manage the information of Internet
 Shows the information and description of the Shopping.
 To increase efficiency of managing the Shopping
 It deals with monitoring the information and transactions of Bills.
1.4. PROBLEM DEFINITION

In this section we shall discuss the limitation and drawback of the existing system that forced us to
take up this project. Really that work was very typical to manage the daily errors free records and
adding or removing any node from server. This problem produces a need to change the existing
system. Some of these shortcomings are being discussed below: -
 Low Functionality
With the existing system, the biggest problem was the low functionality. The problem faced
hampered the work. For small task like adding any new node to server or deleting a node or keeping
daily record we have to appoint minimum two or three employee.
 Erroneous Input and Output
In the existing system, humans performed all the tasks. As in the human tendency, error is also a
possibility. Therefore, the inputs entered by the person who is working in the Company, in the
registers may not be absolutely foolproof and may be erroneous. As a result of wrong input, the
output reports etc. Will also be wrong which would in turn affect the performance.
 Portability Problem
System that existed previously was manual. As a result, the system was less portable. One has to
11
carry the loads of many registers to take the data from one place to another. A big problem was that
the system was less flexible and if we wanted to calculate yearly or monthly maintenance report or
efficiency report, then it was a big headache.
 Security-
Security concerns were also one of the motives of the Company for the need of software. In the
registers, the data is not secure as anybody can tamper with the data written in the registers. While in
this software, just a password makes it absolutely secure from the reach of unauthorized persons.
 Data Redundancy
In the case of manual system, the registers are maintained in which, a lot of data is written.
 Processing Speed
In manual system maintaining a register and performing the necessary calculation has proved to be a
troublesome job, which takes a lot of time and may affect the performance of the Company. But
with this software we can have all the tasks performed in a fraction of second by a single click thus
making the troublesome job much easier.
 Manual Errors
When a number of tough tasks are prepared by the humans like preparation of reports, performing
long calculation then some human error are obvious due to a number of factors like mental strain,
tiredness etc. But as we all know that computer never get tired irrespective of the amount of work it
has to do. So this software can nullify the probability of manual error that improve the performance.
 Complexity in Work
In manual system whenever a record is to be updated or to be deleted a lot of cutting and overwriting
needs to be done on the registers that are concerned that are deleted or updated record, which makes
the work very complex.
2. SYSTEM ANALYSIS
12
2.1. Objective:
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a
system into its components.
System analysis is conducted for the purpose of studying a system or its parts in order to identify its
objectives. It is a problem solving technique that improves the system and ensures that all the
components of the system work efficiently to accomplish their purpose.
Analysis specifies what the system should do.
2.2. SDLC Phases:

System Development Life Cycle (SDLC) mainly consists of the following 7 phases which can be
detailed: -
2.2.1. Preliminary Investigation: -
This is the first phase of the system development life cycle. In this phase we tend to find out the
needs of the client –what exactly does the client want? Before the development of any system the
important point is to know the needs, objectives and scope of the system.
 Feasibility Study: -
Feasibility study is the step of preliminary study of the system development life cycle. Things are
always easy at the beginning in any software process. In fact nothing is in feasible with unlimited
time and resources. But it is not the fact. So, practically we have to do in limited resources in a
restricted time margin. So for the system to be feasible, following points we have to consider.
The feasibility study is conducted to check whether the candidate system is feasible. The system
which is selected to be the best against the criteria is there after designed and developed. The
feasibility study takes in to consideration, the risks involved in the project development beforehand.
Therefore in this phase we have to do feasibility study which is the test of the website according to its
work ability, impact on the organization, ability to meet user need and effective use of resources. We
do the feasibility study for website to analyze the risks, costs and benefits relating to economics,
technology and user organization. There are several types of feasibility depending on the aspect they
cover. Import of these includes:
13
Technical Feasibility:
This is an important outcome of preliminary investigation. It comprise of following questions:-
 Can the work of project bed one with the current equipment, existing software and available
man power resource?
 If Technology is required what are the possibilities that it can be developed?
Economic Feasibility:
It deals with question related to the economy. It comprise of the following questions:-
 Are there sufficient benefits in creating the system to make the cost acceptable?
 Are the costs of not creating the system so great that the project must be undertaken?
Legal Feasibility:
It deals with the question related to the legal issues. It comprise of the following questions: -
 Contract Signing
 Software License agreement
 Issues related to cyber laws.
 Legal issues relating to the man power contract.
Operational Feasibility:
The operational feasibility consists of the following activity:
 Will the system be useful if it is developed &implemented?
 Will there be resistance from employee?
Social & Behavioral Feasibility:

It deals with the various issues related to the human behavior like: -
 Whether the user be able to adapt a new change or not?
 Whether the ambiance we are providing suits the user or not?
14
 Request Approval: -
Request approval is the preliminary investigation phase of system development lifecycle. Request
approval is the phase in which all the requirements which would be provide in the system are stated.
The request approval is a sort of agreement between the client and the company which is building
this software.
Both the parties should be mutually agreed on the stated requirements.
2.2.2. System Analysis:-

System analysis is the phase following the phase of the request approval. In this phase we tend to
analyze the overall system which we have to build. System analysis is the crucial part in SDLC.
2.2.3. System Design:-

System design means the designing of the system. The System can be done in either of the following
two ways:-
 Logical System Design
 Physical System Design

2.2.4. Coding:-
Coding is the phase in which a developer codes using any programming languages. Coding
constitutes only 20% of the whole project and which is easier to write. The coding work is also done
in the teams; development of the system is usually done under the modular programming style, which
can be either top-down approach or bottom-up approach.
2.2.5. Testing:-
Testing is the phase in which the system that has been developed is tested. Testing comprises of the
60% of the overall development of the system. Testing of the system is important because testing
aims to uncover the different errors in the system. There are various different testing techniques that
can be used for the testing of the system.
2.2.6. Implementation:-
Implementation process involved the installation of software on user’s side. Implementation process
actually depends on type of a system & various. Opting for suitable conversion approach is a step
implementation. The conversion processes are as follows:-
15
 Parallel Conversion
 Direct Conversion Approach
 Pilot Conversion Approach
 Phase In Conversion Approach
2.2.7. Maintenance: -
Merely developing the system is not important but also maintenance is important. The company that
has built the system provides for some time free of cost maintenance to the client and after that
period it is usually a paid service.
2.3. Process Description

Gantt charts mainly used to allocate resources to activities. The resources allocated to activities
include staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful
for resource planning. A Gantt chart is special type of bar chart where each bar represents an activity.
The bars are drawn along a timeline. The length of each bar is proportional to the duration of the time
planned for the corresponding activity.
16
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by
coloring each milestone when completed. The project will start in the month of January and end after
4 months at the beginning of April.
2.4. PROJECT MODEL USED
Iterative Enhancement Model
 This model has the same phases as the waterfall model, but with fewer restrictions. Generally
the phases occur in the same order as in the waterfall model, but they may be conducted in several
cycles.
 Useable product is released at the end of the each cycle, with each release providing additional
functionality. Customers and developers specify as many requirements as possible and prepare a SRS
document. Developers and customers then prioritize these requirements. Developers implement the
specified requirements in one or more cycles of design, implementation and test based on the
definedpriorities.
The procedure itself consists of the initialization step, the iteration step, and the Project Control List.
The initialization step creates a base version of the system. The goal for this initial implementation is
to create a product to which the user can react. It should offer a sampling of the key aspects of the
problem and provide a solution that is simple enough to understand and implement easily. To guide
the iteration process, a project control list is created that contains a record of all tasks that need to be
performed. It includes such items as new features to be implemented and areas of redesign of the
existing solution. The control list is constantly being revised as a result of the analysisphase.
The iteration involves the redesign and implementation of iteration is to be simple, straightforward,
and modular, supporting redesign at that stage or as a task added to the project control list. The
level of design detail is not dictated by the iterative approach. In a light-weight iterative project the
code may represent the major source of documentation of the system; however, in a
critical iterative project a formal Software Design Document may be used. The analysis of
iteration is based upon user feedback, and the program analysis facilities available. It involves
analysis of the structure, modularity, usability, reliability, efficiency, & achievement of goals. The
project control list is modified in light of the analysis results.
PHASES:
17
Incremental development slices the system functionality into increments (portions). In each
increment, a slice of functionality is delivered through cross- discipline work, from the requirements
to the deployment. The unified process groups increments/iterations into phases: inception,
elaboration, construction, and transition.
Inception identifies project scope, requirements (functional and non-functional) and risks at a high
level but in enough detail that work can be estimated.
Elaboration delivers a working architecture that mitigates the top risks and fulfills the non-
functional requirements.
Construction incrementally fills-in the architecture with production-ready code produced from
analysis, design, implementation, and testing of the functional requirements.
Transition delivers the system into the production operating environment.
2.5. ER-Diagram
Introduction: -
In software engineering, an entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modeling is a database modeling method, used to produce
a type of conceptual schema or semantic data model of a system, often a relational database, and
18
its
19
requirements in a top-down fashion. Diagrams created by this process are called entity-relationship
diagrams, ER diagrams, or ERDs. ER Diagrams depicts relationship between data objects. The
attribute of each data objects noted in the entity-relationship diagram can be described using a data
object description. Entity relationship diagram is very basic, conceptual model of data and it is
fundamental to the physical database design. This analysis is then used to organize data as relations,
normalizing relations, and obtaining a Relational database.
The entity-relationship model for data uses three features to describe data. These are:
1. Entities which specify distinct real-world items in an application.
2. Relationship, which connect entities and represent meaningful dependencies between them.
3. Attributes which specify properties of entities &relationships.
E-R Diagram
ABOUT
DASHBOARD
DASHBOARD CONTACT
US
FAQs US
MANAGE BATCH
VIDEOLECTURE
STUDENT HOME ADMIN MANAGE ASSIGN

NOTES
ADD ASSIGN
LOGOUT
COURSES
MANAGEVIDEO
SOFTWARE KIT
TASK
MANAGESTUDENT
MANAGESTUDENT
VIDEO
LOGOUT
MANAGEENQUIRY
MANAGEVIDEOCOTEGORY
20
2.6. Data Flow Diagram
Introduction:-
DFD is an acronym for the word Data Flow Diagram. DFD is p pictorial representation of the system.
DFD is a graphical representation of the ―flow of data through the information system. DFD are
also used for the visualization of data processing (structured design). ADFD provides no information
about the timings of the process, or about whether process will operate in parallel or sequence. DFD is
an important technique for modeling system’s high-level detail by showing how input data is
transformed to output results through a sequence of functional transformations. DFD reveal
relationships among between the various components in a program or system. The strength of DFD
lies in the fact that using few symbols we are able to express program design in an easier manner.
ADFD can be used to represent the following:-
External Entity sending and receiving data. Process that change the data.
Flow of data within the system. Data Storage locations.
Uses of DFD:-
The main uses of data flow diagrams are as follows: -
DFD is a method of choice for representation of showing of information through a system because of
the following reasons:-
DFDs are easier to understand by technical and non-technical audiences.

DFDs can provide a high level system overview, complete with boundaries and connections to other
system.
DFDs can provide a detailed representation of system components.
21
updates
22
3. SOFTWARE HARDWARE REQUIREMENT SPECIFICATION
A requirements specification for a software system is a complete description of the behavior of a
system to be developed and it includes a set of use cases that describe all the interactions the users
will have with the software. In addition to use cases, the SRS also contains non-functional
requirements.
Non-functional requirements are requirements which impose constraints on the design or

implementation (such as performance engineering requirements, quality standards, or design
constraints).Requirements are a sub-field of software engineering that deals with the elicitation,
analysis, specification, and validation of requirements for software.
The software requirement specification document enlists all necessary requirements for project
development. To derive the requirements, we need to have clear and thorough understanding of the
products to be developed. This is prepared after detailed communications with project team and the
customer.
3.1. SERVER-SIDE HARDWARE REQUIREMENT:
 AMD Althorn 64 with processor speed 2.8 or more

 256 DDR Ram
 40 GB Hard disks
 Network Interface card
 IIS
 CD-Drive
3.2.SERVER-SIDE SOFTWARE REQUIREMENT:

 Windows
 Visual Studio 2022
 MSSQL
23
CLIENT-SIDE HARDWARE REQUIREMENT:
 Processor Dual core-based computer
 2 GB Minimum RAM
 20 GB HDD
 100 Mbps LAN
 Web Browser
3.3. SUPPORT AND MAINTENANCE: -

One-year free support for rectifying system bugs including front end and beck end will be
provided. During warranty period Software Engineers will be responsible for removing bugs and improving it. After
one year support can be extended @ 20% of the total product deployment cost.
4. SYSTEM DESIGN APPROACH
4.1. Top – Down designing:

The top - down designing approach started with major components of the system. It is a stepwise
refinement which starts from an abstract design, in each steps the design is refined two or more
concrete levels until we reach a level where no – more refinement is possible or not needed.
24
25
4.2. Bottom – Up designing:
In bottom – up designing the most basic and primitive components are designed first, and we proceed to
higher level components. We work with layers of abstractions and abstraction are implemented until the
stage is reached where the operations supported by the layer is complete.
4.3. Following Approach:
In this project we are following Mixed Approach i.e. A combination of top – down and bottom – up.
We are developing some of the components using top – down designing approach (e.g. the WebPages)
and the some components in bottom – up designing approach (e.g. the middle tier classes).
26
5. BACKEND DESIGN
5.1. DBMANAGER.CS
create table tbl_notes
(
sr int primary key identity(1,1),
title varchar(100),
description text,
uploadedby varchar(100),
notesfile varchar(100),
batch int foreign key references tbl_batch(sr),
date datetime
)
5.2. ROUTECONFIG.CS
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<appSettings>
<add key="webpages:Version" value="3.0.0.0" />
<add key="webpages:Enabled" value="false" />
<add key="ClientValidationEnabled" value="true" />
<add key="UnobtrusiveJavaScriptEnabled" value="true" />
</appSettings>
<system.web>
<compilation debug="true" targetFramework="4.7.2" />
<httpRuntime targetFramework="4.7.2" />
</system.web>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Antlr3.Runtime" publicKeyToken="eb42632606e9261f" />
<bindingRedirect oldVersion="0.0.0.0-3.5.0.2" newVersion="3.5.0.2" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Web.Infrastructure" publicKeyToken="31bf3856ad364e35" />
<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
<dependentAssembly>
<assemblyIdentity name="System.Web.Optimization" publicKeyToken="31bf3856ad364e35" />
27
<dependentAssembly>
<assemblyIdentity name="WebGrease" publicKeyToken="31bf3856ad364e35" />
<dependentAssembly>
<assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
<dependentAssembly>
<assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
</assemblyBinding>
</runtime>
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs"
type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider,
Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default
/nowarn:1659;1699;1701" />
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider,
Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008
/define:_MYTYPE=\"Web\" /optionInfer+" />
</compilers>
</system.codedom>
</configuration>
5.3. HOMECONTROLLER.CS
using System;
using System.Collections.Generic;
using System.Data;
using System.Data.SqlClient;
using System.Linq;
using
System.Security.Cryptography.X509Certificates
;
using System.Web;
using System.Web.Mvc;
namespace LMS.Controllers
{
28
public class HomeController : Controller
{
SqlConnection con = new
SqlConnection("Data Source=ANANT\\
MSSQLSERVER01;Initial Catalog=LMS;Integrated
Security=True;");
// GET: Home
public ActionResult Index()
{
//select batch &select catagory
string query = "select * from
tbl_batch order by sr desc";
SqlDataAdapter sda = new
SqlDataAdapter(query, con);
DataTable dt = new DataTable();
sda.Fill(dt);
ViewBag.table1 = dt;
return View();
}
//save data of student in table on click
of submit button of registration form
public ActionResult saveuser(string
txt_name, string txt_email, long txt_mobno,
HttpPostedFileBase file_profile, string
ddl_course, string ddl_year, int ddl_batch,
string txt_password)
{
string query = $"insert into
tbl_student values('{txt_name}',
{txt_mobno},'{txt_email}','{txt_password}','{
ddl_course}','{ddl_course}','{ddl_year}','{fi
le_profile.FileName}','{ddl_batch}',0,'{DateT
ime.Now.ToString("yyyy-MM-dd")}')";
SqlCommand cmd = new SqlCommand(query,
con);
con.Open();
int result = cmd.ExecuteNonQuery();
con.Close();
if (result > 0)
29
{
file_profile.SaveAs(Server.MapPath("/Content/
profilepic/" + file_profile.FileName));
return Content("<script>alert('You
have registered successfully you will receive
confimation from admin via
email');location.href='/home/index'</script>"
);
}
else
{
return Content("<script>alert('Try
again');location.href='/home/index'</script>"
);
}
}
[HttpPost]
public ActionResult Login(string email,

string password)
{
string query = $"select * from
tbl_student where emailid='{email}' and
password='{password}'";
sda.Fill(dt);
if (dt.Rows.Count > 0)
{
if (Convert.ToInt32(dt.Rows[0]
["status"]) == 1)
{
Session["name"] = dt.Rows[0]
["name"];
Session["email"] = dt.Rows[0]
30
["emailid"];
Session["batch"] = dt.Rows[0]
["batch"];
Session["picture"] =
dt.Rows[0]["picture"];
return
Content("<script>alert('Welcome');location.hr
ef='/student/dashboard'</script>");
}
else
{
return
Content("<script>alert('You are not authorize
by
admin');location.href='/home/index'</script>"
);
}
else
{
return
Content("<script>alert('Invalid Id or
password');location.href='/home/index'</scrip
t>");
}
}
public ActionResult Adminlogin()
{
return View();
}
[HttpPost]
public ActionResult adminsignin(string
email, string password)
{
if (email.Equals("techpile@gmail.com")
&& password.Equals("123"))
{
31
Session["admin"] = email;
return
ef='/admin/dashboard'</script>");
}
else
{
return
password');location.href='/home/adminlogin'</
script>");
}
}
}
}
5.4. ADMINCONTROLLER.CS
using System;
using System.Data;
using System.Linq;
using
System.Security.Cryptography.X509Certificates
;
using System.Web;
{
public class HomeController : Controller
{
Security=True;");
// GET: Home
{
32
//select batch &select catagory
tbl_batch order by sr desc";
sda.Fill(dt);
ViewBag.table1 = dt;
return View();
}
//save data of student in table on click
of submit button of registration form
public ActionResult saveuser(string
txt_name, string txt_email, long txt_mobno,
HttpPostedFileBase file_profile, string
ddl_course, string ddl_year, int ddl_batch,
string txt_password)
{
tbl_student values('{txt_name}',
{txt_mobno},'{txt_email}','{txt_password}','{
ddl_course}','{ddl_course}','{ddl_year}','{fi
le_profile.FileName}','{ddl_batch}',0,'{DateT
ime.Now.ToString("yyyy-MM-dd")}')";
con);
con.Open();
con.Close();
if (result > 0)
{
file_profile.SaveAs(Server.MapPath("/Content/
profilepic/" + file_profile.FileName));
return Content("<script>alert('You
have registered successfully you will receive
confimation from admin via
email');location.href='/home/index'</script>"
);
33
}
else
{
return Content("<script>alert('Try
again');location.href='/home/index'</script>"
);
}
}
[HttpPost]
public ActionResult Login(string email,

string password)
{
tbl_student where emailid='{email}' and
password='{password}'";
sda.Fill(dt);
if (dt.Rows.Count > 0)
{
if (Convert.ToInt32(dt.Rows[0]
["status"]) == 1)
{
Session["name"] = dt.Rows[0]
["name"];
Session["email"] = dt.Rows[0]
["emailid"];
Session["batch"] = dt.Rows[0]
["batch"];
Session["picture"] =
dt.Rows[0]["picture"];
return
ef='/student/dashboard'</script>");
}
34
else
{
return
Content("<script>alert('You are not authorize
by
admin');location.href='/home/index'</script>"
);
}
else
{
return
password');location.href='/home/index'</scrip
t>");
}
}
public ActionResult Adminlogin()
{
return View();
}
[HttpPost]
public ActionResult adminsignin(string
email, string password)
{
if (email.Equals("techpile@gmail.com")
&& password.Equals("123"))
{
Session["admin"] = email;
return
ef='/admin/dashboard'</script>");
}
else
{
return
35
password');location.href='/home/adminlogin'</
script>");
}
}
}
}
5.5. STUDENTCONTROLLER.CS
using System;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Mvc.Ajax;
{
public class StudentController : Controller
{
Security=True;");
// GET: Student
{
return View();
}
public ActionResult Dashboard()
{
return View();
}
public ActionResult Courses()
{
tbl_category order by sr desc";
36
sda.Fill(dt);
ViewBag.cat = dt;
return View();
}
public ActionResult Softwarekit()
{
return View();
}
public ActionResult Task()
{
int batchid =
Convert.ToInt32(Session["batch"]);
tbl_assignment left join tbl_submittedtask on
tbl_assignment.sr=taskno where
batch={batchid} order by tbl_assignment.sr
desc";
SqlDataAdapter sda=new
sda.Fill(dt);
ViewBag.task = dt;
return View();
}
public ActionResult Notes()
{
string batch =
Session["batch"].ToString();
tbl_notes where batch={batch} order by Sr
desc";
SqlDataAdapter adapter = new
adapter.Fill(dt);
37
ViewBag.notes = dt;
return View();
}
public ActionResult VideoLecture(int?
catid)
{
if (catid.HasValue)
{
int batchid =
Convert.ToInt32(Session["batch"]);
tbl_video where batch={batchid} and
category={catid} order by sr";
SqlDataAdapter (query, con);
sda.Fill (dt);
ViewBag.video =dt;
return View();
}
else
{
return
Content("<script>alert('please select video
category');location.href='/student/courses'</
script>");
}
return View();
}
public ActionResult ChangePassword()
{
return View();
}
public ActionResult logout()
{
Session.RemoveAll();
return
38
Content("<script>location.href='/home/index'<
/script>");
}
[HttpPost]
public ActionResult submittask(int?
taskno, string email, HttpPostedFileBase
taskfile)
{
tbl_submittedtask
values({taskno},'{email}','{taskfile.FileName
}','{DateTime.Now.ToString("yyyy-MM-
dd")}',0,'')";

con);
con.Open();
con.Close();
if (result > 0)
{
taskfile.SaveAs(Server.MapPath("/Content/answ
erfile/" + taskfile.FileName));
return
Content("<script>alert('file uploaded
successfully');location.href='/student/task'<
/script>");
}
else
{
return
Content("<script>alert('file not
submitted');location.href='/student/task'</sc
ript>");
}
// return Content(taskno + email +

39
taskfile);
}
[HttpPost]
public ActionResult changepass(string
opasswd,string npasswd,string cpasswd)
{
if (npasswd.Equals(cpasswd))
{
string email =
Session["email"].ToString();
string query = $"update
tbl_student set password='{npasswd}' where
emailid='{email}' and password='{opasswd}'";
SqlCommand cmd = new
SqlCommand(query, con);
con.Open();
int result =
cmd.ExecuteNonQuery();
con.Close();
if (result > 0)
{
return
Content("<script>alert('Password
change');location.href='/home/index'</script>
");
}
else
{
return
Content("<script>alert('Not change old
password not
match');location.href='/student/changepasswor
d'</script>");
}
}
else
{
return Content("<script>alert('New
40
password and confirm password should
match');location.href='/student/changepasswor
d'</script>");
}
}
}
}
6. DATA MODELING
6.1. LIST OF TABLES:

6.1.1. Notes Table:
create table tbl_notes
(
title varchar(100),
description text,
uploadedby varchar(100),
notesfile varchar(100),
date datetime
)
6.1.2. Contact Table:
create table tbl_contact
(
sr int primary key identity (1,1),
name varchar(100),
mobno bigint,
emailid varchar(100),
subject varchar(200),
message text,
enqdate datetime
);
6.1.1. Group Table

create table tbl_batch
(
batch varchar(100),
status bit
);
create table tbl_student
(
name varchar(100) not null,
41
mobno bigint,
emailid varchar(100) primary key,
password varchar(100),
course varchar(30),
branch varchar(50),
year varchar(50),
picture varchar(100),
status bit,
regdate datetime
);
create table tbl_category
(
catname varchar(100),
thumbnail varchar(100),
date datetime
);
create table tbl_video
(
title varchar(100),
category int foreign key references tbl_category(sr),
description text,
linl varchar (100) not null,
thumbnail varchar(100),
date datetime
);
create table tbl_assignment
(
subject varchar(100),
title varchar(200),
description text,
taskfile varchar(100),
teacher varchar(100),
lastdate date,
date datetime,
status bit
);
create table tbl_submittedtask

(
taskno int foreign key references tbl_assignment(sr),
userid varchar(100)foreign key references tbl_student(emailid),
answerfile varchar(100),
date datetime,
marks int,
remark text
);
42
6.2. STRUCTURE OF TABLES:
6.2.1. Group Table
PASTE SCREENSHOT(remove yellow highlights with this text after pasting screenshot)
ADD STRUCTURE OF TABLES AS PER YOUR PROJECT
HOME:
43
ADMIN LOGIN
44
ADMIN DASHBOARD
MANAGE BATCHES
45
MANAGE VIDEO CATEGORY
MANAGE VIDEO
46
ADD ASSIGNMENT
MANAGE ASSIGNMENT
47
MANAGE STUDENT
NOTES
48
STUDENT DASHBOARD
VIDEO LECTURE
49
ASSIGNMENT
SOFTWARE KIT
50
CHANGE PASSWORD
51
7. TESTING
Testing is the integral part of any System Development Life Cycle insufficient and interested
application tends to crash and result in loss of economic and manpower investment besides user’s
dissatisfaction and downfall of reputation.
“Software Testing can be looked upon as one among much process, an organization performs, and that
provides the last opportunity to correct any flaws in the developed system. Software Testing includes
selecting test data that have more probability of giving errors.” The first step in System testing is to
develop the plan that all aspect of system .Complements, Correctness, Reliability and Maintainability.
Software is to be tested for the best quality assurance, an assurance that system meets the specification
and requirement for its intended use and performance.
System Testing is the most useful practical process of executing the program with the implicit
intention of finding errors that makes the program fail.
Types of Testing:
Black Box (Functional) Testing:
Testing against specification of system or component. Study it by examining its inputs and related
outputs. Key is to devise inputs that have a higher likelihood of causing outputs that reveal the
presence of defects. Use experience and knowledge of domain to identify such test cases. Failing this a
systematic approach may be necessary. Equivalence partitioning is where the input to a program falls
into a number of classes,
52
e.g. positive numbers vs. negative numbers. Programs normally behave the same way for each member
of a class. Partitions exist for both input and output. Partitions may be discrete or overlap. Invalid data
(i.e. outside the normal partitions) is one or more partitions that should be tested.
Internal System design is not considered in this type of testing. Tests are based on requirements and
functionality.
This type of test case design method focuses on the functional requirements of the software, ignoring
the control structure of the program. Black box testing attempts to find errors in the following
categories:
 Incorrect or missing functions.
 Interface errors.
 Errors in data structures or external database access.
 Performance errors.
 Initialization and termination errors.
White Box (Structural) Testing:
Testing based on knowledge of structure of component (e.g. by looking at source code). Advantage is
that structure of code can be used to find out how many test case need to be performed. Knowledge of
the algorithm (examination of the code) can be used to identify the equivalence partitions. Path testing
is where the tester aims to exercise every independent execution path through the component. All
conditional statements tested for both true and false cases. If a unit has n control statements, there will
be up to 2npossiblepathsthroughit.Thisdemonstratesthatitismucheasiertotestsmall
53
program units than large ones. Flow graphs are a pictorial representation of the paths of control
through a program (ignoring assignments, procedure calls and I/O statements). Use flow graph to
design test cases that execute each path. Static tools may be used to make this easier in programs that
have a complex branching structure. Tools support. Dynamic program analysers instrument a program
with additional code. Typically this will count how many times each statement is executed. At end
print out report showing which statements have and have not been executed. Problems with flow graph
derived testing:
 Data complexity could not take into account.
 We cannot test all paths in combination.
 In really only possible at unit and module testing stages because beyond that complexity is too
high.
This testing is based on knowledge of the internal logic of an application’s code. Also known as a
Glass Box Testing .Internal software and code working should be known for this type of testing. Tests
are based on coverage of code statements, branches, paths, conditions.
Unit Testing:
Unit testing concentrates on each unit of the software as implemented in the code. This is done to
check syntax and logical errors in programs. At this stage, the test focuses on each module
individually, assuring that it functions properly as a unit. In our case, we used extensive white-box
testing at the unit testing stage.
A developer and his team typically do the unit testing do the unit testing is done in parallel with
coding; it includes testing each function and procedure.
Incremental Integration Testing:
Bottom up approach for testing i.e. continuous testing of an application as new functionality is
added; Application functionality and modules should be independent enough to test separately done
by programmers or by testers.
54
Integration Testing:
Testing of integration modules to verify combined functionality after integration

.Modules are typically code modules, individual applications, client and server and distributedsystems.
Functional Testing:
This type of testing ignores the internal parts and focus on the output is as per requirement or not
.Black box type testing geared to functionality requirements of an application.
System Testing:
Entire system is tested as per the requirements. Black box type test that is based on overall requirement
specifications covers all combined parts of a system.
End-to-End Testing:
Similar to system testing ,involves testing of a complete application environment in a situation that
mimics real-world use, such as interacting with a database ,using network communications, or
interacting with hardware, applications, or system if appropriate.
Regression Testing:
Testing the application as a whole for the modification in any module or

functionality.Difficult to cover all the system in regression testing so typically automation tools are
used for these testing types.
55
Acceptance Testing:
Normally this type of testing is done to verify if system meets the customer specified requirements.
User or customers do this testing to determine whether to accept application.
Performance Testing:
Term often used interchangeably with “stress” and “load” testing, To check whether system meets
performance requirements, Used different performance and load tools to do this.
Alpha Testing:
In house virtual user environment can be created for this type of testing. Testing is done at the end of
development .Still minor design changes may be made as a result of such testing.
Beta Testing:
Testing typically done by end-users or others. This is final testing before releasing application for
commercial purpose.
56
8. Input-output Forms(SCREENSHOTS AND CODING)
8.1. Project Screenshot
8.1.1. SIGNIN
PASTE SCREENSHOT(remove yellow highlights with this text after pasting screenshot)
(In the same way you have to paste screenshot as per your project)
8.2. project Coding
8.2.1. Signin.html
PASTE CODING(remove yellow highlights with this text after pasting Coding)
(In the same way you have to paste coding as per your project)
9. FUTURE SCOPE
Following modifications or upgrades can be done in the system.

1. More than one company can be integrated through this software.
2. Web services can be used to know the exact donation status of packets.
3. Client can check their donation delivery status online.
10. CONCLUSION:
At the last the Conclusion of project is to develop a web-application which the help programmer to
get help from the site, so that they can develop their project and application Different Technologies
and make a group of programmer. A Group is a social unit of any size that shares common values,
ideas and code and queries. The portal doesn’t have to be expensive. It supports multiple programmer
goals. Indeed Learning is not only a web portal; it is a live product of board of technical education.
In future we will add more and more features on it.
57

.net

Uploaded by

Copyright:

Available Formats

.net

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

.net

Uploaded by

Copyright:

Available Formats

A

Submitted Towards Partial Fulfillment of

Under the supervision of

(SR Institute of Management and Technology)

Techpile Technology Pvt. Ltd.

Lucknow (U.P.) Signature

The system development was organized into 5 major parts:

3. Software Hardware Requirement Specification……………………………..23-24

5.2 Defined URLs (urls.py)………………………………………………………………………...26-26

6.1. List of Tables

8.1. Project Screenshot………………………………………………………………………………..36-38

8.2. Project Coding……………………………………………………………………………………36-38

1. SOFTWARE DEVELOPMENT LIFE CYCLE……………………………….…16

5. ONE LEVEL DATA FLOW DIAGRAM…………………………………….……22

1.1. Overview of Organization

1.2. PROJECT INTRODUCTION:--

Assignment management is one of the fundamental activities in education.

1.4. PROBLEM DEFINITION

 Erroneous Input and Output

Analysis specifies what the system should do.

2.2. SDLC Phases:

2.2.1. Preliminary Investigation: -

 Software License agreement

 Issues related to cyber laws.

 Legal issues relating to the man power contract.

Social & Behavioral Feasibility:

2.2.2. System Analysis:-

2.2.3. System Design:-

 Physical System Design

 Direct Conversion Approach

 Pilot Conversion Approach

 Phase In Conversion Approach

2.3. Process Description

2.4. PROJECT MODEL USED

Iterative Enhancement Model

3. Attributes which specify properties of entities &relationships.

STUDENT HOME ADMIN MANAGE ASSIGN

DFDs are easier to understand by technical and non-technical audiences.

Non-functional requirements are requirements which impose constraints on the design or

3.1. SERVER-SIDE HARDWARE REQUIREMENT:

 AMD Althorn 64 with processor speed 2.8 or more

3.2.SERVER-SIDE SOFTWARE REQUIREMENT:

3.3. SUPPORT AND MAINTENANCE: -

4. SYSTEM DESIGN APPROACH

4.1. Top – Down designing:

4.3. Following Approach:

public ActionResult Login(string email,

public ActionResult Login(string email,

SqlCommand cmd = new SqlCommand(query,

// return Content(taskno + email +

6.1. LIST OF TABLES:

6.1.1. Group Table

create table tbl_submittedtask

Black Box (Functional) Testing:

 Incorrect or missing functions.

 Errors in data structures or external database access.

 Initialization and termination errors.

White Box (Structural) Testing:

Incremental Integration Testing:

Testing of integration modules to verify combined functionality after integration