Embed Size (px)
Citation preview
AProject Report
On
StudySpace (E-Learning)
B Tech- Sem VIII
Prepared By
Parmar Ajay c. (IT) Bariya Arpankumar (IT) Upadhya Rajkumar (IT)
DEPARTMENT OF INFORMATION TECHNOLOGYGUJARAT INSTITUTE OF TECHNICAL STUDIS
NH8, HIMMANTNAGAR HIGHWAY,PRANTIJ- 383605
December-2014
AProject Report
On
StudySpace (E-Learning)
B-Tech-Sem VIII
In partial fulfillment of requirements for
Bachelor of Technology
In
Information Technology
Under the Guidance of
Prof. Tushar sir
DEPARTMENT OF INFORMATION TECHNOLOGYGUJARAT INSTITUTE OF TECHNICAL STUDIS
NH8, HIMMANTNAGAR HIGHWAY,PRANTIJ- 383605
December-2014
CANDIDATE’S DECLARATION
I declare that pre-final semester report entitled “StudySpace E-Learning” is My own
work conducted under the supervision of the guide Prof.Tushar Sir. I further declare
that to the best of our knowledge the report for B-Tech. VII semester does not
contain part of the work which has been submitted either in this or any other
university without proper citation.
Signature
Name: Tushar Sir.
Student ID: 12ITUOD023
Submitted To:
Prof.Tushar Siri,
Department of Information Technology,
Gujarat Institute of Technical Studis,
NH8, Himmatnagar, Prantij -383605,
Gujarat.
ACKNOWLEDGEMENT With immense pleasure and commitment we would like to present the project
assignment. The nature of project on the development of StudySpace(E-Learning)
wide opportunity to think, implement and interact with various aspects of
management skills swells the new emerging facilities and the technology used in
architecture and the enhancements given to the students with a boon of spirit
quality and curricular activities.
Every work the tone complete successfully stand on the constants encouragement,
good will and support of the people around. We here by avail this opportunity to
express our gratitude to number of people who extended their valuable time, full
support and cooperation in developing this project.
We express deep sense of gratitude toward sour project guide Prof.Tushar Shih
Chuhan towards the innovative suggestion sand effort sot make project as success.
It is their sincerity that prompted us throughout the project to do hard work using
the industry adopted technologies.
We are sincerely thankful to Head of IT department, Prof. Tushar shih chuhan for the
unconditional and an unbiased support during the whole session of study and
development.
We are also thankful to University for providing us with this opportunity.
Table of Contents
1. INTRODUCTION 1
1.1 PROJECT DEFINITION 2
1.2 PURPOSE 2
1.3 OBJECTIVE & SCOPE 3
1.4 TECHNOLOGY AND LITERATURE REVIEW 3
2. PROJECT MANAGEMENT 4
2.1 FEASIBILITY STUDY 5
2.1.1 Operational Feasibility 5
2.1.2 Technical Feasibility 5
2.1.3 Economic Feasibility5
2.1.4Implementation Feasibility 5
2.1.5 Time Feasibility 6
2.2 PROJECT PLANNING6
2.2.1 Project Development approach and Justification 6
2.2.2Project Plan 6
2.2.3 Milestones and Deliverables 6
2.3 PROJECT SCHEDULING 6
Project Scheduling Chart6
2.4 PRODUCT PERSPECTIVE 7
2.5 PRODUCT FUNCTIONS 7
2.6 USER CLASSES AND CHARACTERISTICS 7
2.7OPERATING ENVIRONMENT 8
2.8DESIGN AND IMPLEMENTATION CONSTRAINTS 8
2.9 ASSUMPTIONS AND DEPENDENCIES 8
3. SYSTEM REQUIREMENTS STUDY 9
3.1 STUDY OF CURRENT SYSTEM 10
3.2 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM 1
3.3 USER CHARACTERISTICS 10
3.4 HARDWARE AND SOFTWARE REQUIREMENTS 10
4. SYSTEM ANALYSIS 11
4.1 SYSTEM REQUIREMENTS(SRS) 12
4.2 USE CASE DIAGRAM 14
4.3 ACTIVITY DIAGRAM 15
4.4 SEQUENCE DIAGRAM 21
5. SYSTEM DESIGN 28
5.1 SYSTEM ARCHITECTURE DESIGN 29
5.1.1 Component Diagram 29
5.1.2 Deployment Diagram 30
5.2 DATABASE DESIGN 32
5.2.2 Data Dictionary 32
6. IMPLEMENTATION PLANNING 36
6.1 IMPLEMENTATION ENVIRONMENT 37
6.2 CODING STANDARDS 37
6.3 SECURITY FEATURES 37
7. TESTING 38
7.1 TESTING PLAN 39
7.2 TESTING STRATEGY 39
7.3 TESTING METHODS 40
7.4 TEST CASES 42
8: USER MANUAL 43
9: LIMITATION & FUTURE ENHANCEMENT 51
9.1 LIMITATION 52
9.2 FUTURE ENHANCEMENT 52
10: CONCLUSION & DISCUSSION 53
10.1CONCLUSION & FUTURE ENHANCEMENT 54
10.2DISCUSSION 54
11: REFERENCES 55
INTRODUCTION
CHAPTER 1
INTRODUCTON
G.I.T.S (IT) 1
INTRODUCTION
1.1 Project Definition: StudySpace E-learning is web application designed for Information Technology
department of Gujarat Institute Of Technology.
Using this application all registered students can access the system. The users of
the system can access the required learning materials and related video.
All registered student, admin can upload learning materials for Language.
The system makes it possible for the student to access all learning materials from
home and interact with the professors and clarify their doubts on different
subjects.
Student must be unsatisfied any learning material this time create blog to get
material related answer.
Not only student access this system but any web designer must be access and
improve this application.
User can upload any material to admin are clarify then after upload in
application for user material and video.
1.2 Purpose:
Only registered student and professors can access the system.
Student can view and download all learning materials (pdf , docx).
Student can view pdf of topics which help them to grasp the topic easily.
Admin and user can upload all learning materials.
Admin can upload all learning related video.
.
G.I.T.S (IT) 2
INTRODUCTION
1.3 Objective and Scope:
The proposed StudySpace e-learning system is simple to use for both professors and
students. The proposed system includes the following.
Web based access:
All user who have internet system facility can access the system whenever and
wherever they wish.
Document Management:
System allows uploading and downloading of documents (pdf ,word
documents,ppt).
Media management:
System allows uploading and downloading of ppts and pdf files.
1.4 TECHNOLOGY AND LITERATURE REVIEW
The Microsoft® .NET platform provides all of the tools and technologies
That you need to build distributed Web applications. The .NET platform fully supports
The Internet’s platform neutral, standards-based technologies, including HTTP,
Extensible Markup Language (XML), and Simple Object Access Protocol (SOAP).
G.I.T.S (IT) 3
PROJECT MANAGEMENT
CHAPTER 2
PROJECT MANAGEMENT
G.I.T.S (IT) 4
PROJECT MANAGEMENT
2.1 FEASIBILITY STUDY
Feasibility study is the study of the system to check whether the system made is
feasible or not. It is very Useful to check whether the system work as per the requirement
or not. It is undertaken to determine the possibility of the probability of developing
completely new system.
2.1.1 Operational Feasibility
It covers mainly two aspects. It determines that how the proposed system will fit in the
current operation and what if the job retraining and restructuring may be needed at the
end of the implementation of the system. The operational feasibility checks whether user
who is going to use the system as able to work with the software with which the system is
coded!
2.1.2 Technical Feasibility
It determines that work for the project be done with the present equipments and existing
software technology.
Necessary all things is easily feasible for the project. Necessary technology, documents,
reports are also available. Technical guarantee of accuracy, reliability and security are also
provided.
2.1.3Economic Feasibility
Fortunately, most of the work has to be done by the software in this application, so only the
expected operational costs matter. The app is affordable by a normal user as the user is not
charged of anything extra. The only cost that may incur is of buying a domain to host files
for the backend if we want no constraints on the amount of storage space and other time
related constraints for the domain.
G.I.T.S (IT) 5
PROJECT MANAGEMENT2.1.4 Implementation Feasibility
This systemisbuiltin.net Technology’s a Web Application .we Cannot find any
problem while implementing the project in this Technology .subsystems feasible
for implementing.
2.1.5 Time Schedule Feasibility
The Project hassimple workingand thebasic requirement canbe satisfied within
allotted time periodsothethe time developmentfeasibility issatisfied.
2.2ProjectPlanning.
2.2.1ProjectDevelopmentapproachandjustification.
SPIRAL MODEL
2.2.2ProjectPlan.
• Gather the moduledefinition.
• Checking thetime schedule feasibility.
• Requirementgatheringfor module.
• Analysis on gathered reuirement.
• Designing.
• Coding.
• Testing.
• Management
2.2.3MilestoneandDeliverables.
• Feasibilityanalysis phase :1 week
• Requirementanalysis andspecificationphase :1 week
• DesigningPhase : Approximately2 week
• CodingPhase : Approximately4 week
• Testing Phase : Appriximately1 week
G.I.T.S (IT) 6
PROJECT MANAGEMENT
2.3ProjectScheduling.
Scheduling Chart
Weeks Week 1 Week 2 Week 3 Week 4
1st
Month*Project Defection assigned
* Overview of project
* Discussion on the project
* Preparing SRS
* Study Visual Studio 2012&ASP.Net with C#
* Study of SQL server
* Project planning Started
2nd
Month* Designing of UML Diagrams& System Flow
*Database Design for Initial Modules
*Design of Related Forms started
*Changes In system flow from User side
*Further Detail study of System
3rd
Month*Redesigning of Database with needed Changes
* Development of Forms
* Development of Forms
* Development of Forms
4th
Month* Development of Forms
* Development of Forms
* Integration of modules
* Testing
* Documentation
*Testing
* Documentation
G.I.T.S (IT) 7
PROJECT MANAGEMENT
2.4PRODUCT PERSPECTIVE
The application will be using C# Backend for its functioning. It will be an
autonomous system. This has two sections the web application and the
database section.
The .CS files will serve as a connector between these two entities. The .CS
files will be used to save the data from the mobile application to the remote
database and to fetch the data from the database into the application. Hence
there will be a two way flow.
2.5PRODUCT FUNCTIONS
The main screen of the application will show all the functionalities in form of
Large Icons. User can access these functionalities by simply clicking them.
2.6USER CLASSES AND CHARACTERISTICS
The User classes of the Application and their characteristics are as defined
below:
2.6.1 Head of Department
• Admin login and change her login password.
• Add new Student and professors.
• Add new Subject to Semester.
• Assign the subject to professors.
2.6.2Professors
• Add new topic and its related document and ppt and videos.
• Solve student doubts online.
• Give grad to student depend upon their assignments.
2.6.3Students
• Learn subject and its topic online
• Download study materials (ppt, notes,pdf).
• Discuss their doubts on forms.
• Submit assignment to professors.
G.I.T.S (IT) 8
PROJECT MANAGEMENT
2.7 OPERATING ENVIRONMENT
The main background of the project will depend on the .CS files and .aspx files which
are used for designing. This application uses inbuilt SQL server for database. The
purpose of that is just easy implementation.
2.8DESIGN AND IMPLEMENTATION CONSTRAINTS
2.8.1 The following is the compilation of limitations and constraints on the system:
1. The current API we are using is feasible only for visual studio 2010 and higher
version of it.
2. Inbuilt SQL server is used for Database entries. No external software is
required for connectivity.
3. It will executable of any browser compatible with it.
2.8.2 The following is the compilation of implementation aspects of the system:
1. C# language is used for the in-App coding and designing Algorithms for
managing data and other stuffs of the Application.
2. SQLqueries are used to save and load data from the database.
2.9 ASSUMPTIONS AND DEPENDENCIES
The database of Businessmen of the application and their user id and passwords are
generated by the admin and that cannot be changed by the users. It can only be
changed by after confirmation of registration. Also the data about various products
are supplied by the businessmen , Customers have nothing to do with it.
G.I.T.S (IT) 9
System Requirement Study
CHAPTER 3
SYSTEM REQUIREMENTS STUDY
G.I.T.S (IT) 10
System Requirement Study
3.1 USER CHARECTRISTICS
• System is designed in such a way that most of task are just Click
away.
• User must have to follow the flow of the System in order to use effectively.
• It should run on all the machine as is designed for public use only.
• The GUI is very Simple and understandable for any nontechnical person.
• It is easy with this software to maintain there cords of notices ineffective
manner.
3.2 HARDWARE AND SOFTWARE REQUIREMENTS
3.4.1 Hardware Requirements
1. Pentium IV 1.6 GHZ or compatible
2. 500 MB RAM (minimum) / 256 MB RAM (recommended)
3. 80GB HDD
4. Screen resolution minimum
5. Internet connection
3.4.2 Software Requirements
1. Front end: Visual Studio 2008/2005.
2. Back end: My SQL 2005/2007.
3. Any web browser(Internet Explorer,Mozilla..etc)
4. Toolkit:Ajax Toolkit
G.I.T.S (IT) 11
SYSTEM ANALYSIS
CHAPTER 4
SYSTEM ANALYSIS
G.I.T.S (IT) 12
SYSTEM DESIGN4.1 SYSTEM REQUIREMENTS (SRS)
R.1: Admin
R.1.1: Registration
Input: User Details
Output: Username and Password
R.1.2: Add language category
Input: category
Output: User Name and Password for admin
R.1.3: Add tutorial
Input: Study material
Output: User Name and Password for Student
R.1.4: Add video
Input: language related video
Output: user name and password for student/user
R.1.5: Manage Student/user
Input: profile change for user side
Output: user name and password for student/user
R.2: user/student
R.2.1: Login
Input: Username and Password
Output: Home Page [Successful login]
R.2.2: view all information on this site
Input: view
Output: all information and access for menu
R.2.3: view tutorial
Input: view and download
Output: download to permission in username and password
R.2.4: create blog
Input: particular subject
Output: blog show
G.I.T.S (IT) 13
SYSTEM DESIGN
R.2.5: create comment
Input: for learning material
Output: commented
R.2.6: Solve question for student/ user
Input: Answer of admin and student
Output: Display Answer to Student [Database update]
R.2.7: view video
Input: view video
Output: grad to Student
R.2.8: upload video for particular material related
Input: must be access only authorized user
Output: and view
G.I.T.S (IT) 14
SYSTEM DESIGN
Zero Level DFD
G.I.T.S (IT) 15
SYSTEM DESIGN
Second Level DFD
G.I.T.S (IT) 16
SYSTEM DESIGN
Third Level DFD
G.I.T.S (IT) 17
SYSTEM DESIGN
4.2 USE CASE DIAGRAM
G.I.T.S (IT) 18
SYSTEM DESIGN
4.3 ACTIVITY DIAGRAM
Login Activity [for h.o.d/lecturer/Student]
G.I.T.S (IT) 19
SYSTEM DESIGN
View Topic Details [for Student]
G.I.T.S (IT) 20
SYSTEM DESIGN
Give grad To Student’s Assignments [for Lecturer]
G.I.T.S (IT) 21
SYSTEM DESIGN
Submit Assignments [for Student]
G.I.T.S (IT) 22
SYSTEM DESIGN
Add Student Lecturer And Subject [For Admin]
G.I.T.S (IT) 23
SYSTEM DESIGN
Ask question [for Student]
G.I.T.S (IT) 24
SYSTEM DESIGN
4.4 SEQUENCE DIAGRAM
G.I.T.S (IT) 25
SYSTEM DESIGNAdmin
ADD LECTURER
DELECT LECTURER
G.I.T.S (IT) 26
SYSTEM DESIGN
Lecturer
G.I.T.S (IT) 27
SYSTEM DESIGNADD TOPIC IN SUBJECT
ADD TOPIC DETAILS
G.I.T.S (IT) 28
SYSTEM DESIGN
GIVE ANSWER OF STUDENT
G.I.T.S (IT) 29
SYSTEM DESIGN
GIVE GREAD TO STUDENT OF ASSIGNENTS
G.I.T.S (IT) 30
SYSTEM DESIGN
STUDENT
ASK QUSTION
G.I.T.S (IT) 31
SYSTEM DESIGN
SUBMIT ASSIGMENT
G.I.T.S (IT) 32
SYSTEM DESIGN
CHAPTER 5
G.I.T.S (IT) 33
SYSTEM DESIGN
SYSTEM DESIGN
5.1 SYSTEM ARCHITECTURE DESIGN
G.I.T.S (IT) 34
SYSTEM DESIGN
5.1.1 Component Diagram
5.1.2 Deployment Diagram
G.I.T.S (IT) 35
SYSTEM DESIGN
G.I.T.S (IT) 36
SYSTEM DESIGN
5.2 Database Design
5.2.1Data Dictionary
1. Student_tabelPrimary key:s_idForeign key:login_idField name Data type Field Size ConstraintS_id integer Not NullS_name varchar 50 Not NullS_e_no varchar 12 Not NullS_sem varchar 25 Not NullS_email varchar 50 Not NullS_gender varchar 10 Not NullS_joinigdate date Not NullLoginid varchar 50 Not null
2. faculty_tabelPrimary key:f_idForeign key:login_idField name Data type Field Size Constraintf_id integer Not Nullf_name varchar 50 Not Nullf_id_no varchar 12 Not NullF_post varchar 25 Not Nullf_email varchar 50 Not Nullf_gender varchar 10 Not Nullf_joinigdate date Not NullLoginid varchar 50 Not null
3. login_tabel
G.I.T.S (IT) 37
SYSTEM DESIGNPrimary key:l_idField name Data type Field Size Constraintl_id integer Not Nulll_username varchar 50 Not Nulll_password varchar 50 Not NullL_rolltype varchar 25 Not NullLoginid varchar 50 Note null
4. Subject_tabelPrimary key:s_idField name Data type Field Size ConstraintS_id integer Not NullS_sem_no varchar 50 Not NullS_subject varchar 50 Not NullSession varchar 50 Not null
5. sub_allocte_lecPrimary key:sal_idForeign s_idForeign key:f_idField name Data type Field Size ConstraintSal_id integer Not NullS_id varchar 50 Not NullF_id varchar 12 Not NullSession varchar 25 Not Null
6. Topic_tabelPrimary key:t_idForeign key:f_idForeign key:tm_idField name Data type Field Size ConstraintT_id integer Not NullT_name varchar 50 Not Nullf_id integer Not NullT_details varchar 25 Not Null7. Topic_imagePrimary key:tm_idss
G.I.T.S (IT) 38
SYSTEM DESIGNForeign key:t_idField name Data type Field Size ConstraintTm_id integer Not NullT_id varchar 50 Not NullImage image Not nullVideo Allow nullPpt Allow null
8. Assigment_tabelPrimary key:ass_idForeign key:s_idForeign key:f_idField name Data type Field Size ConstraintAss_id integer Not Nullass_name varchar 50 Not NullS_id integer Not NullSub_id varchar 25 Not NullF_id
9. partical_tabelPrimary key:par_idForeign key:s_idForeign key:f_idField name Data type Field Size Constraintpar_id integer Not Nullpar_name varchar 50 Not NullS_id integer Not NullSub_id varchar 25 Not NullF_id integer Not null
10. Ass_Gread_tabelPrimary key:ag_idForeign key:s_id
G.I.T.S (IT) 39
SYSTEM DESIGNForeign key:f_idField name Data type Field Size Constraintag_id integer Not NullAss_id varchar 50 Not NullS_id integer Not NullSub_id varchar 25 Not NullF_id integer Not nullGrad integer 10 Not null
11. partical_Gread_tabelPrimary key:pg_idForeign key:s_idForeign key:f_idField name Data type Field Size Constraintpg_id integer Not Nullpar_id varchar 50 Not NullS_id integer Not NullSub_id varchar 25 Not NullF_id integer Not nullGrad integer 10 Not null
G.I.T.S (IT) 40
IMPLEMENTATION PLANNING
CHAPTER 6
IMPLEMENTATION PLANNING
G.I.T.S (IT) 41
IMPLEMENTATION PLANNING
6.1IMPLEMENTATION ENVIRONMENT
.net ProgrammingLanguage.
.net Platform independent.
web browser.
6.2 CODING STANDARDS
The front-end of the project is based on Visual studio. The GUI standards
includes followingspecifications.
The sized of components like buttons, textboxes, grid-views , list etc.
All the authority is given to only administrator.
The coding standard provides the guideline for coding a module during
development. When these standards are strictly followed the code becomes
more readable and understandable making the process of debugging easy.
Specifications for coding loops and other control structures.
Specifications for defining the variables etc. and defying the functions.
NamingConventionsarefollowedasin.net framework.
It is case-sensitive.
The code is organized into hierarchical namespaces andclasses
6.3SecurityFeatures.
The Seurityissuesare less inthe Systemas this is for public useonly.
Only registered/ Login customers or businessmencan use this soitcannot create
aproblem and customers also can access this web site so they can easily view the
products.
G.I.T.S (IT) 42
TESTING
CHAPTER 7
TESTING
G.I.T.S (IT) 43
TESTING
7.1 TESTING PLAN
What is software Testing?
Testing involves operation of a system or application under controlled conditionsand
evaluating the results. The controlled conditions should include both normal
andabnormal conditions. Testing should intentionally attempt to make things go
wrongto determine if things happen when they don’t happen when they should. It
isoriented to ‘detection’.
The need for Testing:
No matter how good a programmer is, no application will ever be one
hundredpercent correct. Testing was important to us in order to ensure that the
applicationworks as efficient as possible and conforms to the needs of the
system.Testing was carried out throughout the development of the application, not
justthe application has been developed, as at this stage it took a great deal of
effortto fix any bugs or design problems that were occurred.
7.2 TESTING STRATEGY
When our application was configured and customized in the system, the test
wasobserved that this configuration or customization does not cause any
improper processing or violation. The following care was taken when the
application was developed at the local machine.
The interface may have something not proper, which can be tested by this
checklist:
Number of input parameter equal to number of argument?
Parameter and argument attributes match?
Number of arguments transmitted to called forms equal to number
ofparameters?
G.I.T.S (IT) 44
TESTING
o Attributes of arguments transmitted to called forms to attributes
ofparameters?
o Number attributes and order of arguments to built-in functions
correct?
o The local data structures for a form are common source of errors.
Thefollowing types of errors should be searched for,
o Improper or inconsistent typing
o Erroneous initialization or default values
o Incorrect (misspelled or truncated) variables names
o Inconsistent data types
o Underflow, overflow and addressing exception
o As far as unit testing is concerned we did it at the time of coding in
aninformal but extensive way, so as to reduce number of problems
arising outof incorrect syntax, incorrect variable, function names etc.
o Close the database connection when not required.
o Care was taken to check for any infinite loop that exists in code
beforeexecuting the code.
7.3 TESTING METHODS
White Box Testing
Also known as glass box, structural, clear box and open box testing. A
softwaretesting technique whereby explicit knowledge of the internal
workings of the itembeing tested are used to select the test data. Unlike
black box testing, white box testinguses specific knowledge of programming
code to examine outputs. The test is accurateonly if the tester knows what
the program is supposed to do, it means that he must becompletely aware
that for particular input a particular output must be obtained.The main
benefit of this type of testing is Tester can see if the program diverges fromits
intended goal.This test concentrates on the examination of the code rather
G.I.T.S (IT) 45
TESTING
than the specification. Wehave included three different forms of white box
testing.
Statement Coverage Criterion:
This is the simplest coverage criterion. We are checking in it that each statement of
the program was executed “at least once”.
Branch Coverage Criterion:
An improvement over statement is Branch Coverage. In that we are running a series
of test to ensure that all branches are tested at least once.
Path Coverage Criterion:
There are many errors which were not detected by statement or branch testing. The
reason is that some errors are related to some combination of branches and it may
be not check in other test. We are checking in this test is all path of programs are
executed or not.
Black Box Testing
Black-box and white-box are test design methods. Black-box test design treats the
system as a "black-box", so it doesn't explicitly use knowledge of the internal
structure.Black-box test design is usually described as focusing on testing functional
requirements. Also known as behavioural, functional, opaque-box, and closed-
box.Black Box Testing was helpful us to find error such as:
Interface error
Incorrect or missing functions.
Errors in data structures or external database access.
Performance Errors.
Unit Testing
Unit testing is a method of testing the correctness of a particular module of
sourcecode. The idea is to write test cases for every non-trivial function or method in
themodule so that each test case is separate from the others if possible. The
G.I.T.S (IT) 46
TESTING
developers mostly do this type of testing.In this method of testing we test all
individual components to ensure that they operatecorrectly. Each component are
tested independently without other system components.
Integration Testing
It is the phase of software testing in which individual software modules we
are combined and tested as a group. It follows unit testing and precedes
system testing.The purpose of Integration testing is to verify functional,
performance and reliability requirements placed on major design items.It
takes as its input modules that have been checked out by unit testing, groups
them inlarger aggregates, applies tests defined in an Integration test plan to
those aggregates, and delivers as its output the integrated system ready for
system testing.
7.4 TEST CASES
Test Case Id
Description Prerequisite Expected Output
Result Output
Pass/Fail
1.1 Login/Signup
The username and password must be currect.
Successful establishment of connection
Successful Login
Pass
1.2 Give grad Assignments must be available for grad
Assign grad Successful Assign grad Pass
1.3 Update information
User must be Logged in the application
The user should be able to set his desired personal details
The user is able to set his details Pass
G.I.T.S (IT) 47
USER MANUAL
Test Object
CHAPTER 8
USER MANUAL
G.I.T.S (IT) 48
USER MANUAL
8. USER MANUAL
A user guide or user's guide, also commonly known as a manual, is a technical Communication
document intended to give assistance to people using a particular
System. It is usually written by a technical writer, although user guides are written by
programmers, product or project managers, or other technical staff, particularly in
smaller companies.
User guides are most commonly associated with electronic goods, computer hardware
and software.
Our user guides contain both a written guide and the associated images. In the case of
our application, it is usual to include screenshots of how the program should look. The
language used is matched to the intended audience.
We have prepared our user manual according to various user roles and module wise, so a novice
user can understand system very quickly.
G.I.T.S (IT) 49
USER MANUAL
Login
Successful login
G.I.T.S (IT) 50
USER MANUAL
Detect Student
Assign Subject to Faculty
G.I.T.S (IT) 51
USER MANUAL
View subject
Faculty/student login page
G.I.T.S (IT) 52
USER MANUAL
Faculty home page
Upload document
G.I.T.S (IT) 53
USER MANUAL
See faculty’s all posted topic
View posted topic
G.I.T.S (IT) 54
USER MANUAL
Post a topic
Student home page
G.I.T.S (IT) 55
LIMITATION & FUTURE ENHANCEMENT
CHAPTER 9
LIMITATION & FUTURE ENHANCEMENT
G.I.T.S (IT) 56
LIMITATION & FUTURE ENHANCEMENT
9.1 LIMITATION
OnlyRegistered Student can access all study Martials.
Only those professors can upload note or study Martials which has to assign those
subjects.
Student can access only his semester’s subject study Martials.
9.2 FUTURE ENHANCEMENT
The system fulfills all most of the requirements currently, but to make it more dynamic and up
to the mark of reality, some extensions are necessary, which were not possible due to time
constraints.
Online examition
G.I.T.S (IT) 57
CONCLUSION AND DISCUSSION
CHAPTER 10
CONCLUSION AND DISCUSSION
G.I.T.S (IT) 58
CONCLUSION AND DISCUSSION
10.1 CONCLUSION AND FUTURE ENHANCEMENT
The Collage E-learning System is intended to Learns topic Details online for
student. And professors able to post topic and its related document and discuss between
student and professors. Student submits their assignments to professors and gain grad
from professors.
10.2 DISCUSSION
10.2.1 Self-Analysis of Project Viabilities
According to me, this project is completed with the primary functionalities as specified
earlier but then again there is lot more than this which can be done. The project is well
capable to handle the given job for some particular task but not all of them. So then it is a
challenge to further develop it in to well flagged software as it was challenge to develop
up to this very stage.
10.2.2 Problem Encountered and Possible Solutions
There were many problems encountered during the design and the development phase
of the project.
Sometimes Notifications of student’s question is not displayed to according its
topic or subject to professors.
10.2.3 Summary of Project work
We have completed my project work using software engineering and system Analysis and
design approach. I have done work with pre-planned scheduling related with time
Constrains and result oriented program.
G.I.T.S (IT) 59
REFERENCES
CHAPTER 10
REFERENCES
G.I.T.S (IT) 60
REFERENCES
REFERENCES Asphepls.com ASP.NET 2.0 by wrox publication Asphepls.com Microsoft MSDN Slideshare.com wikipedia.org
G.I.T.S (IT) 61
