PROJECT REPORT ONLINE CAMPUS INFORMATION SYSTEM [28-JAN-2012] Project Guide: K i r a n S u r e s h k u m a r J i v n a n i , M C A f r o m G u j a r a t u n i v . Submitted at: IETE CENTER BY:JYOTI JOSEPH
~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~ A Project Report Online Campus Information System ~~~~~~~~~~~~~~~~~~~~~~~~~
●PROJECT● ●(AT-69)● DEC-2011
Project Guide:Ms.Kiran sureshkumar jivnani Submitted at: I.E.T.E, Ahmedabad
JYOTI JOSEPH AMIETE (Information Technology stream)
Page 2
INDEX 1)
2)
Introduction………………………………………....………………04 Objective & Scope of the project Theoretical Background Definition of Problem
Working Environment………………………………………….....06 ASP.NET and .NET Framework Common Language Runtime ASP.NET Controls Master Pages Code Behind Pages
3) METHODOLGY………………………………………………….12 4)
Functional Requirement…………………………………...............16 User console modules of projects Nonfunctional requirement
5)
Design…………………………………………..................................20 System Design Specification Module description
6)
Coding Standards……………………..…………………................22
6)
Documentation………………………………………………………27
7)
Snapshots…………………………………………………….............29
Page 3
8)
Conclusion &Bibliography…………….............................................37
INTRODUCTION
Page 4
Objective & Scope of the Project Objectives describe what the prospective users of the system want from system. Being an important part of the system development process, preparation of the requirement specification has been done after studying the existing procedure and personal interaction with prospective users. The Purpose of this document is to outline the requirements for the eCommerce (Business to Customer) Products. The project aim is to design an online system through which individual can get the latest information about the students and staffs. This generic application designed for assisting the students of an institute regarding information on the courses, subjects, classes, assignments, grades and timetable. Scope Scope of this project is to provide the details of all the marks obtained by the students in studying in various year’s.
Theoretical Background In a typical campus scenario, the access for a student to details such as his/her internal marks, monthly attendance reports etc. is available only through notice board. The main aim of our system is to make this information accessible through out the campus LAN. Problem Definition We are going to design an application that provides the facility of viewing the marks obtained by the students in various subjects. The main aim of this is to provide detail information about what going in college, to know student
Page 5
details etc.
WORKING ENVIRONMENT
Page 6
ASP.NET and the .NET Framework ASP.NET is part of the Microsoft .NET Framework. To build ASP.NET pages, you need to take advantage of the features of the .NET Framework. The .NET Framework consists of two parts: the Framework Class Library and the Common Language Runtime.
Understanding the Framework Class Library The .NET Framework contains thousands of classes that you can use when building an application. The Framework Class Library was designed to make it easier to perform the most common programming tasks. Here are just a few examples of the classes in the framework: . File class—Enables you to represent a file on your hard drive. You can use the File class to check whether a file exists, create a new file, delete a file, and perform many other file-related tasks. . Graphics class—Enables you to work with different types of images such as GIF,PNG, BMP, and JPEG images. You can use the Graphics class to draw rectangles, arcs, ellipsis, and other elements on an image. . Random class—Enables you to generate a random number. . SmtpClient class—Enables you to send email. You can use the SmtpClient class to send emails that contain attachments and HTML content.
Understanding Namespaces There are almost 13,000 classes in the .NET Framework. This is an overwhelming number. If Microsoft simply jumbled all the classes together, then you would never find anything. Fortunately, Microsoft divided the classes in the Framework into separate namespaces. A namespace is simply a category. For example, all the classes related to working with the file system are located in the System.IO namespace. All the classes for working a Microsoft SQL Server database are located in the System.Data.SqlClient namespace. Before you can use a class in a page, you must indicate the namespace associated with the class. There are multiple ways of doing this. Page 7
Understanding the Common Language Runtime The second part of the .NET Framework is the Common Language Runtime (CLR). The Common Language Runtime is responsible for executing your application code.When you write an application for the .NET Framework with a language such as C# or Visual Basic .NET, your source code is never compiled directly into machine code. Instead, the C# or Visual Basic compiler converts your code into a special language named MSIL (Microsoft Intermediate Language). MSIL looks very much like an object-oriented assembly language. However, unlike a typical assembly language, it is not CPU specific. MSIL is a low-level and platform-independent language. When your application actually executes, the MSIL code is “just-in-time” compiled into machine code by the JITTER (the Just-In-Time compiler). Normally, your entire application is not compiled from MSIL into machine code. Instead, only the methods that are actually called during execution are compiled. In reality, the .NET Framework understands only one language: MSIL. However, you can write applications using languages such as Visual Basic .NET and C# for the .NET Framework because the .NET Framework includes compilers for these languages that enable you to compile your code into MSIL. You can write code for the .NET Framework using any one of dozens of different languages, including the following: • . Ada • . Apl • . Caml • . COBOL • . Eiffel • . Forth • . Fortran • . JavaScript The vast majority of developers building ASP.NET applications write the applications in either C# or Visual Basic .NET. Many of the other .NET languages in the preceding list are academic experiments.
Understanding ASP.NET Controls ASP.NET controls are the heart of the ASP.NET Framework. An ASP.NET control is a .NET class that executes on the server and renders certain content to the browser. For example, in the first ASP.NET page created at the beginning of this chapter, a Label control was used to display the current date and time. The ASP.NET framework includes over 70 controls, which enable you to do everything from displaying a list of database records to displaying a randomly rotating banner advertisement. Page 8
Overview of ASP.NET Controls The ASP.NET Framework contains over 70 controls. These controls can be divided into eight groups: Standard Controls—The standard controls enable you to render standard form elements such as buttons, input fields, and labels. We examine these controls in detail in the following chapter, “Using the Standard Controls.” Validation Controls—The validation controls enable you to validate form data before you submit the data to the server. For example, you can use a RequiredFieldValidator control to check whether a user entered a value for a required input field. Rich Controls—The rich controls enable you to render things such as calendars, file upload buttons, rotating banner advertisements, and multi-step wizards. Data Controls—The data controls enable you to work with data such as database data. For example, you can use these controls to submit new records to a database table or display a list of database records. Navigation Controls—The navigation controls enable you to display standard navigation elements such as menus, tree views, and bread crumb trails. Login Controls—The login controls enable you to display login, change password, and registration forms. HTML Controls—The HTML controls enable you to convert any HTML tag into a server- side control.
Designing Websites with Master Pages A Master Page enables you to share the same content among multiple content pages in a website. You can use a Master Page to create a common page layout. For example, if you want all the pages in your website to share a three column layout, you can create the layout once in a Master Page and apply the layout to multiple content pages. You also can use Master Pages to display common content in multiple pages. For example, if you want to display a standard header and footer in each page in your website, then you can create the standard header and footer in a Master Page. Page 9
By taking advantage of Master Pages, you can make your website easier to maintain, extend, and modify. If you need to add a new page to your website that looks just like the other pages in your website, then you simply need to apply the same Master Page to the new content page. If you decide to completely modify the design of your website, you do not need to change every content page. You can modify just a single Master Page to dramatically change the appearance of all the pages in your application. Loading Master Pages dynamically is useful when you need to co-brand one website with another website, or when you want to enable individual website users to customize the appearance of your website.
Creating Master Pages You create a Master Page by creating a file that ends with the .master extension. You can locate a Master Page file any place within an application. Furthermore, you can add multiple Master Pages to the same application.
Using Code-Behind Pages The ASP.NET Framework (and Visual Web Developer) enables you to create two different types of ASP.NET pages. You can create both single-file and two-file ASP.NET pages. All the code samples in this book are written as single-file ASP.NET pages. In a single-file ASP.NET page, a single file contains both the page code and page controls. The page code is contained in a <script runat=”server”> tag. As an alternative to a single-file ASP.NET page, you can create a two-file ASP.NET page. A two-file ASP.NET page is normally referred to as a code-behind page. In a codebehind page, the page code is contained in a separate file. NOTE
Page 10
Using the Page.IsPostBack Property The Page class includes a property called the IsPostBack property, which you can use to detect whether the page has already been posted back to the server. Because of View State, when you initialize a control property, you do not want to initialize the property every time a page loads. Because View State saves the state of control properties across page posts, you typically initialize a control property only once, when the page first loads. In fact, many controls don’t work correctly if you re-initialize the properties of the control with each page load. In these cases, you must use the IsPostBack property to detect whether or not the page has been posted.
Page 11
METHODOLOGY
Page 12
CLASSICAL WATERFALL MODEL
Software is developed during this phase and at the end of life cycle the product becomes ready to deliver to customer. 1.feasibility study Its main aim is to determine whether it is physically and technically feasible or not. it involves analysis of problems and collection of all relevant information. collected data are analyzed to arrive at following. -an abstract problem definition -format of different strategies for solving problem. -evaluation of different solution strategies. Thus during this this phase very high level decisions are made. 2.Requirement Analysis Its aim is to understand exact requirement of customer and to document them properly. There are two activities involved here.
i.
Requirement gathering &analysis
First requirements are gathered and then analyzed. All relevant information is then collected from customers to clearly understand needs. Then analysis is done to remove incompleteness and inconsistency.
Page 13
ii.
Requirement specification
Requirements from above stage are organized into software requirement specification document (SRS). SRS to be reviewed and approved by customer. It forms basis of all carrying out all development activities. 3. Design Its goal is to transform requirement specified in SRS into structure suitable for implementation in programming language. in traditional design approach there are two activities. i.
Structure analysis prepare detail analysis of different function to be supported by system and identification of data flow. each function is sub divided and decomposed into sub function.
ii.
Structure design consist of architectural design. where system is decomposed into modules. data structure & algorithms are designed and documented.
4. coding &testing Its aim is to translate software design into source code. to write good programs coding standards are formulated. it indicating standard ways of laying out program codes, communicating naming conventions ,templates for function and modules etc. so each component is implemented as a program module. -next each module is unit tested. each module is tested from isolation of other modules then debugging and documenting it. the correct working of each module is determined individually.
Page 14
5.Integration &System testing Different modules are integrated in planned manner. this is done incrementally over number of steps. during each steps previously planned modules are added to partially integrated system. it includes 3 kind of activities i. α –testing: performed by development team. ii.
β –testing: done by friendly set of customers.
iii.
Acceptance testing: done by customer himself.
6. maintenance It involves performing following activities. i.
Corrective maintenance Correcting errors not discovered during
developing product. ii.
Perfective maintenance
Improving the implementation and enhance the functionality of the system as per customer needs. iii.
Adaptive maintenance Required for parting the software to work in
new environment.
Page 15
FUNCTIONAL REQUIREMENT
Page 16
Software Environment: • Server Need: Operating System: Windows XP, Windows7,Windows Vista Application Server: Internet Information Server DBMS: Sqlserver 2005 IDE: MS Visual Studio 2010 •
Client Need: Browser: Internet Explorer, Google chrome.
Hardware Environment • Server Need: Pentium 4 Processor 40 GB HDD or Higher 128 MB RAM or higher
Constraints: It requires minimum 256MB RAM to be loaded or run. It requires IIS to browse the application.
Non-Functional Requirement:Reliability: a) System will be completely user friendly, so the users can access the required information by selecting the appropriate option. b) It is capable of maintaining database of related students information and to update the marks of the students.
Page 17
c) It provides the details of all the marks obtained by the students d) The system gives us information, about contact no., name of person, E-mail id and website of the company, address etc.
Maintainability: The functions provided are efficient and less ambiguous. The system is made such a way one can easily maintain it. Extensibility: As per the user requirement the system should is extensible. More function can be add later on w/o any faults.
Functional Oriented Design Data Flow Diagrams
Context Level Diagram:
student
User
login
guest
Online Campus information System
requesting
Services response
Student details
Page 18
results
View Of Database: The database mainly contain the table named Login Database, csdetails Database, itdetails Database, csresult Database,itresult Database.
Assumptions and dependencies a) Assumptions The end users like Administrator, Client users are well versed with the computers. b) Dependencies The updating and modification in the database depends upon the information supplied by various client users using database. The administrator will regularly update the site.
System Features : Student a) Login Introduction:-The user has to login only when he has to view his/her result, personal details and timetable etc. Input: - Fill the Login id and password. Processing: - verification of Login id & password is done. Output: - If Login id and password is correct then his own profile is opened and he/she can view his details etc.
Page 19
DESIGN
Page 20
Software Requirement Specification Introduction
System design is a solution to the creation of raw system. This is important phase is composed of several steps to provide the understanding and Procedural details to implement the system. Design goes through a logical & physical task of developed. Logical design reviews the present physical system, purpose, inputs or outputs specification, make audit, security and control specification, database implementation plans & prepare a logical design walkthrough physical design makes out the details of physical system, plans the system implementation, plan is specifies any new hardware and software products.
Purpose The purpose of SDS is to present the design concept for the project “ONLINE CAMPUS INFORMATION SYSTEM”. It includes the project system architecture, detailed description of component relationship & design decision trade off.
Scope The Project aim is to design an Online Campus Information system. We are providing a system through which any student can view his or her marks obtained, timetable and respective teachers detail who going to take the lecture, fees, their personal details etc. Decomposition description:
It includes Modules decomposition, Process decomposition and Data decomposition.
Page 21
CODING STANDARDS
Page 22
CODING STANDARDS The best applications are coded properly means that the code not only does its job well, but is also easy to add to, maintain and debug as well as it is easily understood by anybody. Naming Convention Guideline Do use descriptive names for types, variables and parameters.
In doing so avoid using single character
names // Good
string firstName int count; // Not good string fname; int x; For the Control’s naming, please user the proper name for
the control with suffix Specifies the control type. Button - UserNameBtn or UserNameButton
Page 23
Follow the following table for the naming conventions: Camel Case A word with the first letter lowercase, and the first letter of each subsequent word-part capitalized. Example: customerName Pascal Case A word with the first letter capitalized, and the first letter of each subsequent word-part capitalized. Example: CustomerName
Models of Testing There are different Models of testing. On the basis of testing methods there are two types of testing: 1. Black-box testing. 2. White-box testing Black-box tests are used to demonstrate that software functions are operational, that input is properly accepted and output is correctly produced, and that integrity of external information is maintained. White-box tests are used to examine the procedural details. It checks the logical paths by test case. It can also checks the conditions, loops used in the software coding. It checks that loops are working correctly on defined boundary value.
Page 24
TEST PLAN The testing process Developer tests the software process activities such as Design, Implementation, and Requirement Engineering. Because, design errors are very costly to repair once system has been started to operate. Therefore, it is quite obvious to repair them at early stage of the system. So analysis is the most important process of any project. Requirement Tractability As most interested portion is whether the system is meeting its requirements or not, for that testing should be planned so that all requirements are individually tested. Developer checked the output of certain combination of inputs, which gives desirable results, or not. Strictly stick to your requirements specifications, give you the path to get desirable results from the system.
Acceptance Testing Acceptance testing can mean one of two things: A
smoke test
is used as an acceptance test prior to introducing a build to
the main testing process. Acceptance testing performed by the customer is known as user acceptance testing (UAT).
Page 25
Regression Testing Regression testing is any type of software testing that seeks to uncover software
regressions.
Such
regressions
occur
whenever
software
functionality that was previously working correctly stops working as intended. Typically regressions occur as an
unintended consequence
of
program changes. Common methods of regression testing include rerunning previously run tests and checking whether previously fixed faults have re-emerged.
Page 26
DOCUMENTATION
Page 27
MANUALS Home page is common to all users. The category of users – Students and Guests.
STUDENT: STUDENT have to give student id and password to view his own marks and he/she can also see the timetable of respective semester and the faculty whose taking the particular lecture.
Page 28
SNAPSHOTS
Page 29
Homepage
Page 30
Page 31
Student Homepage
Page 32
Page 33
Registration Form
Page 34
Timetable Semwise
Page 35
Page 36
CONCLUSION & BIBLIOGRAPHY
Page 37
Conclusion: Information Technology plays a vital role not only in a particular field, it provides various kinds of solutions and services to the various problems prevailing in many fields. Online campus information system exploits Information Technology at the minimum extent. It uses the information technology in an efficient way for providing better services.
BIBLIOGRAPHY:
• C# and .net platform, Andrew troelsen, dreamtech press. • C# 2008 programming with .net, black book, dreamtech. • “Pl-sql” by ivan bayross • “software engineering,a practitioners approach” tata macraw hill publishing company limited.by roger s.pressman
Website Refer: The following links were searched and exploited extensively for the project development:
• www.seminarprojects.com • www.scribd.com • www.msdn.microsoft.com • www.dotnetspider.com Page 38
Page 39
