Student Corner Report

1.INTRODUCTION

1.1 PROJECT SUMMARY:

Student Corner Website is web based application that helps Student to get Assignments, mid timetable, mid result, gtu papers and it`s solution and about events . This website is widely or mostly used for Students. In this website Student can download Assignments, mid timetable, mid result, gtu papers and it`s solution and about events connection, registration of new connection. Using this website, user can get information about events ornganized by college.Student can easily download materials. In this website, faculty can easily upload all types of materials in .pdf format. And Student can see the details of our website. In this website from admin side, faculty can add new assignments, mid sem time table and result,gtu paper and it`s solution , delete and update all information which is add by faculty. Then after adding new information by admin, Student can change his/her information. For update information, every student compulsory need to login in the system.

1.2 PURPOSE :

We the main purpose of this website is to easily get assignments, mid sem time table and result, gtu paper and it`s solution and event news. It makes easy to Register and check information. Student can easily download all types of materials And student can also changing the details of his/her.

1.3 OBJECTIVE:

The Main objectives of this project are:

1. To identify and analyze several rule-based techniques.
2. To easily change details or view it also.
3. To easily get information about study.
4. To easily download all types of materials.

1.4 SCOPE:

      
     This website is mostly used by students only for engineering. Any faculty can put on information in this website.faculty can change any details of all types of materials but he/she cannot download any type of materials.

1.5 TOOLS AND TECHNOLOGY:

The project will require/use following software and software tools:

1. Platform               : Asp.Net with C#

2. Client Authoring  : CSS, XHTML

3. Server Side           : ASP.NET

4. Code Behind         : Visual C#

5. Web Server            : Visual Studio 2008

6. Dev. Tool               : Flash Player

7. A/D/UML              : Edraw Max

8. Database                 : SQL server 2005

2. PROJECT MANAGEMENT

2.1 PROJECT PLANNING:

A project plan is "A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summary or detailed."

Project Plan can also be defined more precisely as:

"A statement of how and when a project's objectives are to be achieved, by showing the major products, milestones, activities and resources required on the project."

At a minimum, a project plan answers basic questions about the project:

• Why? – Into STUDENT CORNER, user can easily registration and download all types of materials.
• What? – Students can easily download all types of materials.
• Who? – We are two developers which developed this system.

How will they be organized?

Following members are involved in this project:

1. Joshi Jaydeep J.:-

In this project, his responsibility is in coding, designer and as well as manage the project.

2. Gujarati Pratik D. :-

In this project, his responsibility is as GUI designer and report creation of system.

1. User:-

Students can easily download all types of materials.

2. Admin:-

Admin can add, delete and update any information.

• When? - What is the project timeline and when will particularly meaningful points, referred to as milestones, be complete?

This project is completed in 3 months and 27 Days.

The topics which we have covered in Project Planning are:

Project development model, Project Plan, Milestones and Deliverables, Roles and Responsibilities, Assumptions and Dependencies.

2.1.1 PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION:

The project development model which we will follow for our project is the “Waterfall Model”. Waterfall Model derives its name due to the cascading effect from one phase to the other as is illustrated in Figure 2.1.1. This model is sometimes referred to as the linear sequence model.

2.1.1 WATERFALL MODEL:

Fig : 2.1 WATERFALL MODEL

• REASONS FOR USING WATERFALL MODEL:
• Processes based on Waterfall Model are widely used for practical system development. In the normal waterfall model the next phase should not start until the previous phase has finished. But in practice, these stages overlap and feed information to each other. During design, problems with requirements are identified, during coding design problems are found and so on. The software process is not a simple linear model but involves of iterations of the development activities.
• Because of the costs of producing and approving documents, iterations are costly and involve significant rework. Therefore, after a small number of iterations, it is normal to freeze parts of the development, such as the specifications and to continue with the later development stages. Problems are left for later resolution, ignored or are programmed around. This premature freezing of requirements may mean that the system won’t do what the user wants. It may also lead to badly structured systems as design problems are circumvented by implementation tricks.
• Thus to use a Waterfall Model with feedback is the best option in such a system where you need to move from one phase to other with the feedback from other stages.

2.1.2 PROJECT PLAN:

PARTICULARS:	DURATION
FEASIBILITY
Technical Schedule Operational	1 day 3 days 2 day
REQUIREMENT GATHERING
Interviews Questionnaires Discussions	4 days 3 days 3 days
SYSTEM REQUIREMENT SPECIFICATION
Product Overview System Features External Interface Requirements Non Functional Requirements	2 days 2 days 5 days 5 days
SYSTEM ANALYSIS
Use Case Diagrams Activity Diagram Sequence Diagram Relationship Diagram Data Dictionary DFD	3 days 3 days 4 days 4 days 3 days 2 days
SYSTEM DESIGN
Database Design UI Design Business Logic Interface Description	3 days 7 days 7 days 3 days

IMPLEMENTATION
Front End Back End Business Logic	14 days 16 days 2 days
TESTING
Unit Test Integration Test System Test User Acceptance Test	1 days 1 days 2 days 2 day
DEPLOYMENT
Installation Training	2 day 2 days
Total	117 days

2.1.3 MILESTONES AND DELIVERABLES:

Sr. No.	Milestone Activities	Start Date	End Date	Deliverable
1.	Requirement Analysis	23/12/2013	16/01/2014	Yes
2.	Planning	17/01/2014	28/01/2014	Yes
3.	System design	29/01/2014	26/02/2014	Yes
4.	Coding	27/02/2014	05/04/2014	Yes
5.	Testing	06/04/2014	17/04/0214	yes

4. ROLES AND RESPONSIBILITIES:

Sr. No	Name	Role	Responsibility
	Mr.Mayur Jani	Co-Guide	To provide required resources for project development and certify the project work weekly.
	Mr.Vishal Kothari	Internal Guide	To take weekly report submissions and give feedback accordingly
	Joshi Jaydeep J.	Team Member	Developer
	Gujarati Pratik D..	Team Member	Flash Designer

2. PROJECT SCHEDULING:

Fig. 2.2.1 Grant chart

3. System Requirements Study:

1. HARDWARE AND SOFTWARE REQUIREMENTS:

Hardware Requirements:

1. Development PCs : Core i-3 Machines with 3 GB RAM,320 GB Hard disk

            2. Server PC : Core i-7 Machines with 4 GB RAM,1 TB Hard disk.

Software Requirements:

1. Platform : Visual Studio 2008
2. Client OS : Windows 2007 Ultimate
3. Server OS : Windows 2007 Ultimate
4. Client Authoring : CSS,XHTML
5. Client Side : -
6. Server Side : ASP.Net
7. Code Behind : C#
8. Dev. Tool : Flash Player
9. Database : SQL server 2005
   
   

CONSTRAINTS:

3.2.1. Hardware Limitations:

Hardware:-

Hard Disk : 10 GB

RAM : 512 MB

Internet connection : Yes

Printer : Yes

3.2.2. Interface to other Applications:

None.

3.2.3. Parallel operations:

None.

3.2.4. Safety and Security Considerations:

When user is forgot the password then compulsory give the answer of question which is fill when registration.

3.4 ASSUMPTIONS AND DEPENDENCIES:

Assumptions:

1. An username will be used to register an individual only once.

Dependencies:

1. Student can not upload any type of materials.
   
   
   
   
   4. SYSTEM ANALYSIS:
   4.1 STUDY OF CURRENT SYSTEM:
   Before create the software when any new data entry is arise then detail will be store by manually or windows base system and it is very difficult when we have to access that detail back also we have to find that data by paper based or particular that computer is needed in which data is store. Now it makes possible using any type of software which works to store data by using web application.
   So for the online Registration we create software which is useful for both Admin as well as end user who want to register count in system. Firstly we think for admin who is responsible for all function of the Registration system like he/she work on collage work as like assignment, paper, paper solution. So that all information admin have to change from some period of time and that will not possible using windows system or paper based system. So this application gives best solution for that problem. So, current system is not for effective output.
   PROBLEM & WEAKNESSES OF CURRENT SYSTEM:
2. In this system user is at a time one Registration.
3. In this system without fill any details and not submit data so it is not Registration of parties.
4. This system is not allowed the same registration is more- Then one time.
5. When we store detail as manually then to retrieve that information is very difficult.
6. It is very difficult to find out where the particular needed detail from dozen of detail in manual work.
7. It is quite difficult to maintain all detail to one person so that person must present to all time.
8. It is time consuming and more critical to save all information.

4.2 REQUIREMENTS OF NEW SYSTEM:

Following are the intended users who will interact with the system. Users are classified and differentiated on the basis of their interaction with the system. Each user will have an access to the system based on the access rights or will able to navigate through the system that are intended for them. Beyond that none will be able to access the features not anticipated for them.

1) USER:

The user is who that accesses this application from outer side it means, as a user they have not all right’s to access this application. User firstly login with account then if they want to get connection and disconnect it also. User easily pay the bill also and change the details.

2) ADMIN:

Admin will be the root user of the system. He will manage database. Admin is who that have all right’s to access this application. Firstly admin can add new user detail then after they can also add also other process. They can delete any particular detail of any user. Admin also can see all report of details. That all database access can do by only admin not any other can do all addition, deletion and updation operation to any details of User. Admin can Change Password also.

From this system requirement of user as well as admin is fulfill. User not has to go personally to the voting and also admin can all activity

4.3 FEASIBILITY STUDY:

A feasibility study was an evaluation of a proposal designed to determine the difficulty in carrying out a designated task. Generally, a feasibility study precedes technical development and project implementation. In other words, a feasibility study is an evaluation or analysis of the potential impact of a proposed project.

A feasibility study is a short, focused study, which aims to answer a number of questions:

       Does the system Contributor to the overall Objectives?

• Can the system be implemented using current technology and within given cost and schedule constraints?
• Can the system be integrated with systems, which are already in place?

Three types of project feasibility we will consider are:

1) Operational feasibility.

2) Technical feasibility.

3) Financial and Economic feasibility.

1. Operational feasibility:

Operational feasibility focuses on whether the system will work when it is develop and installed operationally system feasible.

• There is sufficient support for the project from manager and user. The system is well liked and used to the extent that person will not be able to see reasons for change.

• The proposed system will not cause any harm to its users

• The system will provide to the end users with accurate information about the system.

• The system will provide the security by providing the control on login a valid user by checking his or her User Id and password.

• Validation of data input is taken care of by system not by user.

2. Technical feasibility:

The assessment is based on an outline design of system requirements in terms of Input, Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data, trends, frequency of updating, etc. in order to estimate whether the new system will perform adequately or not. Technological feasibility is carried out to determine whether the company has the capability, in terms of software, hardware, personnel and expertise, to handle the completion of the project.

• Technical feasibility tries to answer the following questions to make the system feasible to develop.

• The software or tools necessary for building or running the application are easily available or not?

Ate help like tool tips wherever required for the user so that he/she can have access of our application easily and conveniently without having many navigation problems.

This will also save time for the user and reduce manual labor.

3. Cost feasibility:

The .NET Framework for running the program is freely downloadable.

Once, the industry get the licensed version of Visual Studio there will be no other cost as compared to the usefulness in programming it provides. The SQL Server is again one of the best ORDBMS, which is one of the best backend options.

This will be a customized product for particular company. The company will provide all the resources which we will require for our project.

Projects seems to be financially and economical feasible as far as for In House project the college budget is concerned.

4.4 REQUIREMENTS VALIDATION:

Is requirement stated clearly?

Is the source of requirement identified?

Does the requirement violate any rule?

What other requirement are related to this requirement? Are they validated?

4.5 ACTIVIYIES/PROCESSES MODULE WISEIN NEW SYSTEM:

Following are features of new system:

• User easily get information.
• User easily download information.
• User access the data through his/her android mobile also.

4.6 FEATURES OF NEW SYSTEM:

Here the system’s right is given to two person user and admin so there is future of this system is given below:

USER:

The user which is firstly user can give instruction and registration is completed. User can give details and create account. User easily manage because it is very simply and easy process. User get easily get information. it also.

ADMIN:

Admin will be the root user of the system. He will manage database. Admin is who that have all right’s to access this application. Admin change the details easily. Admin change Password also. That all database access can do by only admin not any other can do all addition, deletion and updation operation for details. Admin give all information to view details, registration, add mid result, add mid timetable, add paper ,add paper solution, add assignment.

From this system User not has to go personally to the any process and also admin have not to worry about any record which normally store and use all the rights from any activity.

5. LIMITATIONS AND FUTURE ENHANCEMENT

5.1. LIMITATIONS:

• Only .pdf format type files are uploaded by admin.
• Only .pdf format files downloaded by user.
• User cannot download any type of materials without login.
• Admin cannot upload any type of materials without login.
• If user forgot password then required to give answer security question compulsory.
• User cannot upload any type of materials.
• User can upload only registration details.
• If admin forgot password then account cannot accessed.
• Only authorized user download any type of materials.

5.2. FUTURE ENHANCEMENT:

• In this system Administrator can’t give any feedback response we develop some logic to give feedback response to user.

• In future, admin can upload all types of files.
• All courses are including into this website.
• Chat facility include into this website.
• We apply this application on different backend like MY SQL, ORACLE, etc.
• We are trying to more security to transfer information.

6. CONCLUSION

Student Corner is web-site by which we can get all information about Student Corner. It’s a web-based application.

Through this project admin can access his they can add or update all record related to Details Functionality .Admin can declare the result of our functionality. From here student only can facility to change or Forgot password.

Now student can only the view about all types of materials, easily download that materials and create account also.

We conclude that by developing this system. We are learn how to developed actual software and how analyzed system and implements system. We also get knowledge about system analysis and designing and how to developed web based application in .net.

7. APPENDENCIES

7.1 WEBSITE REFERRED:

• www.wikipedia.com
• www.google.com
• www.css.com

7.2 BOOK REFERRED:

• Wrox.Professional.ASP.NET.3.5.In.C.Sharp.and.VB.
• Pro ASP.NET 3.5 in C# (Professional)
• Black Book.