College Management Android App Projects
Table of Contents
ABSTRACT 2
CHAPTER 1 –INTRODUCTION 3
1.1 Objectives 7
1.2 System Specifications 7
CHAPTER 2 – LITERATURE REVIEW 8
CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM 12
3.1 Module Description 12
CHAPTER 4 – DESIGN 15
4.1UML Diagrams: 15
4.1.1Usecase Diagrams: 16
4.1.2 Sequence Diagram: 17
4.1.3 Collaborate Diagram: 18
CHAPTER 5 - OUTPUT SCREENSHOTS 22
CHAPTER 6 – IMPLEMENTATION DETAILS 23
6.1 Introduction to Html Framework 23
6.2 Cascading Style Sheets (CSS) 26
6.3 MYSQL Server 34
6.4PHP 35
6.5 ANGULAR JAVA SCRIPT 38
CHAPTER 7- SYSTEM STUDY 41
CHAPTER 8-TECHNICAL FEASIBILITY 42
CHAPTER 9-SYSTEM TESTING 45
CHAPTER 10– CONCLUSIONS 50
CHAPTER 11- REFERENCES 51
ABSTRACT
An Android application for college is an application that can be accessed throughout the organization and especially by students well with proper login provided when needed. This application can be used by students using their smart phones. Using this application students will able to stay updated with their college events, circular notices, exam time table. An android based college campus to share the college campus activities application will provide updates to the students of their respective departments, notices regarding the recruiting company, campus interview date and other placement activities.
CHAPTER 1 –INTRODUCTION
The software facilitates the administrators to know the present status of a student of the college. The software gives the information such as student personal data, student fees details, results etc. Generating the print reports of student personal, fee as well as result details…. Hence android app project conclude that the present system (CMS for Colleges) would definitely help the user by saving time and effort by reducing the processing time and volume of errors. The efficiency of the work done would be improved and work satisfaction on the part of the employees after computerization would definitely on high. The customer satisfaction would be definitely higher when compared to the old manual system
The existing system which we using in our college is traditional process is a complete manual process. Now-a-days, education is playing very significant role in the society. Day-by-day, the percentage of illiterates are decreasing and the percentage of literates is increasing. Education will change the society in all the aspects and everyone wants to study higher professional degrees. Admissions are increasing day by day so there by ratio of establishment new colleges and schools are also increasing. But the actual challenge is starting from now. Most of the schools and colleges are maintain student information in records. When the number of records increased, it is difficult to maintain the information of each student in the old manual system. Maintaining the records manually leads to error prone and required more man power and it consumes more time for processing the records.
The main objective of developing the current project entitled “COLLEGE MANAGEMENT SYSTEM FOR COLLEGES” is to build effective system which is fast, accurate, consistency, reliable and flexible enough so that it can incorporate any future enhancements.
By automating the system using computers, sophisticated technology can be used for making the information more flexible, accurate, and secure and user friendly.
Time and man power can be more effectively utilized and online information can be easily available to the user and at the same time we can maintain higher level of security. Every user such as student, staff and administration can able to see the information of each student through online from anywhere and anytime. These types of CMS are already available in our markets, but it does not have the feature that we are providing to our college. android app ideas for college project of the companies are improving this project on the platform .NET. that seems to be complicated and to use The main functionality such as ENTERING AND RETRIVING of the attendance in the CMS will not be provided by the companies who had developed this project earlier. We are going to introduce our project on a special platform JAVA which is very user friendly. Here we will provide the high permissions to the Admin so he can handle the complete college for better security and maintenance. There will be different permissions to the admin and faculty.
Until recently the place of the College Management System (CMS). Now-a-days, education is playing very significant role in the society. Day-by-day, the percentage of illiterates are decreasing and the percentage of literates is increasing. Education will change the society in all the aspects and everyone wants to study higher professional degrees. Admissions are increasing day by day so there by. Ratio of establishment new colleges and schools are also increasing. But the actual challenge is starting from now. Most of the schools and colleges are maintain student information in records. When the number of records increased, it is difficult to maintain the information of each student in the old manual system.
Maintaining the records manually leads to error prone and required more man power and it consumes more time for processing the records.
While virtual learning environments have been available in some capacity since 1960, “the PLATO system featured multiple roles, including students who could study assigned lessons and communicate with teachers through on-line notes, instructors, who could examine student progress data, as well as communicate and take lessons themselves, and authors, who could do all of the above, plus create new lessons” (Wikipedia, 2006a, 1960s section,). Learning management systems have only been available, in roughly their present form, since the 1990s (Vollmer , 2003), with Blackboard and WebCT being broadly adopted in universities and colleges by early 2000 (Online, 2006). Initial versions of an LMS focused on organizing and managing course content and learners.
As with many organizations, higher education was unsure about the role of technology in the educational process. The rapid penetration of learning management systems as key tools for learning occurs in a vacuum of solid research as to their effectiveness in increasing learning—or even indication of best practices for technology implementation. Pedagogy is generally a secondary consideration to student management; some researchers attempted to bridge research from face-to-face environments to technology spaces (Chickering & Ehrmann, 1996)—a practice that may be convenient, but errs in assuming that the online space is an extension of physical instruction, not an alternative medium with unique affordances. Learning management systems became the default starting point of technology enabled learning in an environment largely omitting faculty and learner needs. Learning Circuits’ (n.d.) publication,
A Field Guide to Learning Management Systems, revealed the nature of most LMS decisions at committee levels (an experience paralleled in academic environments): “an LMS should integrate with other enterprise application solutions used by HR and accounting, enabling management to measure the impact, effectiveness, and overall cost of training initiatives”. The value of an LMS is ensconced in language of management and control—notions that most academics would perceive as antagonistic to the process of learning. Most LMS options, features, and comparisons (LMS Options, 2006) focus on tools included in a suite, not on how to foster and encourage learning in relation to an organization’s definition of “what it means to learn.” Discussions of features are divorced from emphasis on learning opportunities. Learning Management Systems (LMS) are often viewed as being the starting point (or critical component) of any elearning or blended learning program. This perspective is valid from a management and control standpoint, but antithetical to the way in which most people learn today. Learning management systems like WebCT, Blackboard, and Desire2Learn offer their greatest value to the organization by providing a means to sequence content and create a manageable structure for instructors/administration staff. The “management” aspect of a learning management system creates another problem: much like we used to measure “bums in seats” for program success, we now see statistics of “students enrolled in our LMS” and “number of page views by students” as an indication of success/progress. The underlying assumption is that if we just expose students to the content, learning will happen.
1.1 Objectives
This document is the Software Requirement Specification (SRS) for the College Management System for College (CMS) project .The purpose of this document is to describe the functionality, requirements and general interface of the CMS.
1.2 System Specifications
Hardware Requirements:-
Android
Software Requirements: -
Operating System : Android OS
Front-End : HTML, CSS, and JS
Back-End : Angular JS, PHP, MYSQL
Tool : Cordova
CHAPTER 2 – LITERATURE REVIEW
This project is based on COLLEGE MANAGEMENT SYSTEM. It manages the college information, student information, placement information, various different types of event going on in our college. It also keeps track records of all the information regarding students those who are placed in the various organizations. It has a notice board which contains information about various cultural or technical or any sports which is supposed to be held soon. With the help of this project, you can view the previous videos with the help of internet connection.
This College Management System project developed using PHP programming language. The main aim of this project is to develop an online website which covers all the details of college i.e.; Student attendance details, Event details, Students fees transaction details, Marks details, Photo gallery, etc. Admin is the Super user of this project. All the record stores in MySQL Database. The proposed software will also reduce the cumbersome paperwork, manual labor as well as communication cost.
This paper is aimed at developing an Online Intranet College Management System (CMS) that is of importance to either an educational institution or a college. The system (CMS) is an Intranet based application that can be accessed throughout the institution or a specified department. This system may be used for monitoring attendence for the college. Students as well as staffs logging in may also access or can be search any of the information regarding college. Attendance of the staff and students as well as marks of the students will be updated by staff. This system (C.M.S ) is being developed for an engineering college to maintain and facilitate easy access to information. For this the users must be registered with the system after which they can access as well as modify data as per the permissions given to them. CMS is an intranet based application that aims at providing information to all the levels of management with in an organization. This system can be used as a knowledge/information management system for the college. For a given student/staff (technical/Non-technical) can access the system to either upload or download some information from the database.
The title of the project is “COLLEGE MANAGEMENT SYSTEM FOR COLLEGE” (CMS). CMS is defined as an application based on Intranet that aims to all the levels of management providing information within an organization. This system can be used as a information management system for the college. For a given student/staff (Technical / Non-technical) the Administrator creates login id & password, using these student/ staff (Technical / Non-technical) can access the system to either upload or download some information from the database. The front-end will be HTML pages for client side validation with Java Script where as all business logics will be in Java reside at middle layer. third layer of database will be interacted with these layers, which would be Oracle database. The web server would be Tomcat 5.5 version. Server have Tomcat5.5 as web server is required to start working on this project environment like Java Runtime Environment (JRE) as development environment and Oracle10g as database The project is divided into 6 scenarios; each scenario can be developed independently. And knowledge of Java with oracle10g is desirable to execute this project.
Access/ Search information.
Login to the system through the first page of the application
Change the password after logging into the system
View/change his/her details
Can get help through the help option to view different features of the system.
Students can give feedback on college/staff/any other student.
An admin login should be present who can read as well as remove any uploads
This document describes the product and its requirements and constraints. It provides a primarily non-technical description of the project targeted towards external audiences. This section includes information such as data requirements, functional requirements, and a general description of the product and its interaction with users from the perspective of the client. Section 3 provides specific technical requirements as the team understands them at this time and is intended for an internal audience. This section includes information such as external interface requirements, performance requirements, and any other technical requirements needed to design the software.
The main objective of college management system is to automate all functionalities of a college or university. Using this system you can manage all college management work like admission, fees submission, time table management and result declaration. Using this college management system you can view or update data and information about students and staff easily. This system helps in managing the activity like student admission, student registration, fees submission. Admin can also retrieve information of employee student.
The COLLEGE MANAGEMENT SYSTEM can be used to store student information like attendance, fees, and student result etc. admin can create report regarding any student any time using this system. Using this system you can register new student and their course details. You can submit students fees and can check fees details anytime. You can create exam result and submit in this system. Student can check their result online by logging to the system. You can also add new employee in the system and can check details of the employee easily. Student can also check course detail online from this system.
Using this system you can manage all information of all aspects of a college, its students, faculties, Departments, marks and other curricular activities. College management system provides the easiest way to manage all functionalities of a college. This system facilitates colleges to maintain the functionality related to college employees and their students.
College Management System can store and manage all data of the various departments of a college like Administration, Attendance, Staff details etc. using this system user can retrieve any information related to student, teacher and fees. Using this system teacher can check student attendance anytime. This system also help teacher to announce the result. College administration can also manage college work easily. Admin can check leave, salary and other details of teacher any time. They can also create time table of classes from this system. The Library module is used for the data process of library and book accessing for students and staffs.
Existing Solution:
Its manual process for earlier system.
Its more time consume for all process.
Need for more resources.
Its chance to lose our record or data.
Proposed Solution:
The proposed system consists of three modules: admin panel, Student module. Admin can post their notification about collage, update staff details, student details and collage event details. Students can view all details including staff details.
CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM
3.1 Module Description
An android based college campus to share the college campus activities application will provide updates to the students of their respective departments, notices regarding the recruiting company, campus interview date and other placement activities.
3.2 System Features
In the life of the software development, problem analysis provides a base for design and development phase. The problem is analyzed so that sufficient matter is provided to design a new system. Large problems are sub-divided into smaller once to make them understandable and easy for finding solutions. Same in this project all the task are sub-divided and categorized.
System Modules:
1. Admin (Web Interface):
Log in:
In log in page, admin can only view the shared information. They can’t update or edit any information.
Sign in and Sign up:
The staff will be having an account to update the college information because students know who update the information. In sign up, Staff adds the following details,
o Staff name:
o Department:
o Mobile no:
o Password:
o Confirm password:
Add Students Details and View details:
Admin creates the students details with following requirements,
o Student name
o Register number
o Department
o Year
o Password (Date of birth)
o Gender
Events:
• Sports:
o Game name
o Department Vs
o Date & Time
• Conference:
o Conference Name
o Conducted by
o Department participated
o Place
o Date & Time
• Cultural:
o Date & Time
Placement Details:
o Company Name
o Eligible Candidates (CGPA mark %)
o Skills
o Job Description
o Date & Time
o Place
o Eligible Department
Circular & Other notices:
Any other information are updated this site with specific departments or all departments.
Gallery:
Admin updates any images in this site with specific departments.
2. Students (Android Interface)
Log in:
Students log in with their register number and date of birth (password).
Notification:
Students can get the notification of all new information updated in the application.
View:
Students can only view the information updated in the application, gallery and also view their own details.
Contact:
Students can also view the staff details. In contacts, Staff’s mobile number shows which are updated by staffs.
Offline:
Students can also view the details in offline.
CHAPTER 4 – DESIGN
Design is the first step in the development phase for any techniques and principles for the purpose of defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves three technical activities - design, coding, implementation and testing that are required to build and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions ultimately affecting the success of the software implementation and its ease of maintenance are made. These decisions have the final bearing upon reliability and maintainability of the system. Design is the only way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through which requirements are translated into a representation of software. Software design is conducted in two steps. Preliminary design is concerned with the transformation of requirements into data.
4.1UML Diagrams:
UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and documenting the system. This is the step while developing any product after analysis. The goal from this is to produce a model of the entities involved in the project which later need to be built. The representation of the entities that are to be used in the product being developed need to be designed.
There are various kinds of methods in software design:
• Use case Diagram
• Sequence Diagram
• Collaboration Diagram
4.1.1Usecase Diagrams:
Use case diagrams model behavior within a system and helps the developers understand of what the user require. The stick man represents what’s called an actor.Use case diagram can be useful for getting an overall view of the system and clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between the use case and actors.
• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system
4.1.2 Sequence Diagram:
Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An interaction diagram shows an interaction, consisting of set of objects and their relationship including the messages that may be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering of messages. Graphically a sequence diagram is a table that shows objects arranged along the X-axis and messages ordered in increasing time along the Y-axis.
4.1.3 Collaborate Diagram:
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML).
DFD Diagram
Student
Admin
CHAPTER 5 - OUTPUT SCREENSHOTS
CHAPTER 6 – IMPLEMENTATION DETAILS
6.1 Introduction to Html Framework
Hyper Text Markup Language, commonly referred to as HTML, is the standard markup language used to create web pages. Along with CSS, and JavaScript, HTML is a cornerstone technology used to create web pages, as well as to create user interfaces for mobile and web applications. Web browsers can read HTML files and render them into visible or audible web pages. HTML describes the structure of a website semantically along with cues for presentation, making it a markup language, rather than a programming language.
HTML elements form the building blocks of HTML pages. HTML allows images and other objects to be embedded and it can be used to create interactive forms. It provides a means to create structured documents by denoting structuralsemantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as
HTML can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages. HTML markup can also refer the browser to Cascading Style Sheets (CSS) to define the look and layout of text and other material.
HyperText Markup Language (HTML) is the standard markup language for creating web pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a triad of cornerstone technologies for the World Wide Web.[1] Web browsers receive HTML documents from a webserver or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and other objects, such as interactive forms, may be embedded into the rendered page. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as
HTML can embed programs written in a scripting language such as JavaScript which affect the behavior and content of web pages. Inclusion of CSS defines the look and layout of content. The World Wide Web Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.[2]
In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped ENQUIRE, a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo proposing an Internet-based hypertext system.[3] Berners-Lee specified HTML and wrote the browser and server software in late 1990. That year, Berners-Lee and CERN data systems engineer Robert Cailliau collaborated on a joint request for funding, but the project was not formally adopted by CERN. In his personal notes[4] from 1990 he listed[5] "some of the many areas in which hypertext is used" and put an encyclopedia first.
The first publicly available description of HTML was a document called "HTML Tags", first mentioned on the Internet by Tim Berners-Lee in late 1991.[6][7] It describes 18 elements comprising the initial, relatively simple design of HTML. Except for the hyperlink tag, these were strongly influenced by SGMLguid, an in-house Standard Generalized Markup Language (SGML)-based documentation format at CERN. Eleven of these elements still exist in HTML 4.[8]
HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visual or audible web pages. Default characteristics for every item of HTML markup are defined in the browser, and these characteristics can be altered or enhanced by the web page designer's additional use of CSS. Many of the text elements are found in the 1988 ISO technical report TR 9537 Techniques for using SGML, which in turn covers the features of early text formatting languages such as that used by the RUNOFF command developed in the early 1960s for the CTSS (Compatible Time-Sharing System) operating system: these formatting commands were derived from the commands used by typesetters to manually format documents. However, the SGML concept of generalized markup is based on elements (nested annotated ranges with attributes) rather than merely print effects, with also the separation of structure and markup; HTML has been progressively moved in this direction with CSS.
Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the first proposal for an HTML specification, the "Hypertext Markup Language (HTML)" Internet Draft by Berners-Lee and Dan Connolly, which included an SGML Document Type Definition to define the grammar.[9][10] The draft expired after six months, but was notable for its acknowledgment of the NCSA Mosaic browser's custom tag for embedding in-line images, reflecting the IETF's philosophy of basing standards on successful prototypes.[11] Similarly, Dave Raggett's competing Internet-Draft, "HTML+ (Hypertext Markup Format)", from late 1993, suggested standardizing already-implemented features like tables and fill-out forms.[12]
After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML Working Group, which in 1995 completed "HTML 2.0", the first HTML specification intended to be treated as a standard against which future implementations should be based.[13]
Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained, with input from commercial software vendors, by the World Wide Web Consortium (W3C).[14] However, in 2000, HTML also became an international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with further errata published through 2001. In 2004, development began on HTML5 in the Web Hypertext Application Technology Working Group (WHATWG), which became a joint deliverable with the W3C in 2008, and completed and standardized on 28 October 2014.[15]
6.2 Cascading Style Sheets (CSS)
CSS is a style sheet language used for describing the presentation of a document written in a markup language. Although android mini project topics used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG andXUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.
CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts. This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content, such as semantically insignificant tables that were widely used to format pages before consistent CSS rendering was available in all major browsers. CSS makes it possible to separate presentation instructions from the HTML content in a separate file or style section of the HTML file. For each matching HTML element, it provides a list of formatting instructions. For example, a CSS rule might specify that "all heading 1 elements should be bold", leaving pure semantic HTML markup that asserts "this text is a level 1 heading" without formatting code such as a
<bold>
tag indicating how such text should be displayed.
This separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser orscreen reader) and on Braille-based, tactile devices. It can also be used to display the web page differently depending on the screen size or device on which it is being viewed. Although the author of a web page typically links to a CSS file within the markup file, readers can specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author has specified. If the author or the reader did not link the document to a style sheet, the default style of the browser will be applied. Another advantage of CSS is that aesthetic changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in one file, rather than by a laborious (and thus expensive) process of crawling over every document line by line, changing markup.
The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a document written in a markup language.[1] Although most often used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG and XUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.[2]
CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts.[3] This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content.
Separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (via speech-based browser or screen reader), and on Braille-based tactile devices. It can also display the web page differently depending on the screen size or viewing device. Readers can also specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author specified.
Changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in the CSS file they use, rather than by changing markup in the documents.
The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998). The W3C operates a free CSS validation service for CSS documents.
In CSS, selectors declare which part of the markup a style applies to by matching tags and attributes in the markup itself.
Selectors may apply to:
all elements of a specific type, e.g. the second-level headers h2
elements specified by attribute, in particular:
id: an identifier unique within the document
class: an identifier that can annotate multiple elements in a document
elements depending on how they are placed relative to others in the document tree.
Classes and IDs are case-sensitive, start with letters, and can include alphanumeric characters and underscores. A class may apply to any number of instances of any elements. An ID may only be applied to a single element.
Pseudo-classes are used in CSS selectors to permit formatting based on information that is not contained in the document tree. One example of a widely used pseudo-class is :hover, which identifies content only when the user "points to" the visible element, usually by holding the mouse cursor over it. It is appended to a selector as in a:hover or #elementid:hover. A pseudo-class classifies document elements, such as :link or :visited, whereas a pseudo-element makes a selection that may consist of partial elements, such as ::first-line or ::first-letter.[5]
Selectors may be combined in many ways to achieve great specificity and flexibility.[6] Multiple selectors may be joined in a spaced list to specify elements by location, element type, id, class, or any combination thereof. The order of the selectors is important. For example, div .myClass color: red; applies to all elements of class myClass that are inside div elements, whereas .myClass div color: red; applies to all div elements that are in elements of class myClass.
CSS information can be provided from various sources. These sources can be the web browser, the user and the author. The information from the author can be further classified into inline, media type, importance, selector specificity, rule order, inheritance and property definition. CSS style information can be in a separate document or it can be embedded into an HTML document. Multiple style sheets can be imported. Different styles can be applied depending on the output device being used; for example, the screen version can be quite different from the printed version, so that authors can tailor the presentation appropriately for each medium.
The style sheet with the highest priority controls the content display. Declarations not set in the highest priority source are passed on to a source of lower priority, such as the user agent style. This process is called cascading.
One of the goals of CSS is to allow users greater control over presentation. Someone who finds red italic headings difficult to read may apply a different style sheet. Depending on the browser and the web site, a user may choose from various style sheets provided by the designers, or may remove all added styles and view the site using the browser's default styling, or may override just the red italic heading style without altering other attributes.
CSS was first proposed by Håkon Wium Lie on October 10, 1994.[16] At the time, Lie was working with Tim Berners-Lee at CERN.[17] Several other style sheet languages for the web were proposed around the same time, and discussions on public mailing lists and inside World Wide Web Consortium resulted in the first W3C CSS Recommendation (CSS1)[18] being released in 1996. In particular, Bert Bos' proposal was influential; he became co-author of CSS1 and is regarded as co-creator of CSS.[19]
Style sheets have existed in one form or another since the beginnings of Standard Generalized Markup Language (SGML) in the 1980s, and CSS was developed to provide style sheets for the web.[20] One requirement for a web style sheet language was for style sheets to come from different sources on the web. Therefore, existing style sheet languages like DSSSL and FOSI were not suitable. CSS, on the other hand, let a document's style be influenced by multiple style sheets by way of "cascading" styles.[20]
As HTML grew, it came to encompass a wider variety of stylistic capabilities to meet the demands of web developers. This evolution gave the designer more control over site appearance, at the cost of more complex HTML. Variations in web browser implementations, such as ViolaWWW and WorldWideWeb,[21] made consistent site appearance difficult, and users had less control over how web content was displayed. The browser/editor developed by Tim Berners-Lee had style sheets that were hard-coded into the program. The style sheets could therefore not be linked to documents on the web.[22] Robert Cailliau, also of CERN, wanted to separate the structure from the presentation so that different style sheets could describe different presentation for printing, screen-based presentations, and editors.[21]
Improving web presentation capabilities was a topic of interest to many in the web community and nine different style sheet languages were proposed on the www-style mailing list.[20] Of these nine proposals, two were especially influential on what became CSS: Cascading HTML Style Sheets[16] and Stream-based Style Sheet Proposal (SSP).[19][23] Two browsers served as testbeds for the initial proposals; Lie worked with Yves Lafon to implement CSS in Dave Raggett's Arena browser.[24][25][26] Bert Bos implemented his own SSP proposal in the Argo browser.[19] Thereafter, Lie and Bos worked together to develop the CSS standard (the 'H' was removed from the name because these style sheets could also be applied to other markup languages besides HTML).[17]
Lie's proposal was presented at the "Mosaic and the Web" conference (later called WWW2) in Chicago, Illinois in 1994, and again with Bert Bos in 1995.[17] Around this time the W3C was already being established, and took an interest in the development of CSS. It organized a workshop toward that end chaired by Steven Pemberton. This resulted in W3C adding work on CSS to the deliverables of the HTML editorial review board (ERB). Lie and Bos were the primary technical staff on this aspect of the project, with additional members, including Thomas Reardon of Microsoft, participating as well. In August 1996 Netscape Communication Corporation presented an alternative style sheet language called JavaScript Style Sheets (JSSS).[17] The spec was never finished and is deprecated.[27] By the end of 1996, CSS was ready to become official, and the CSS level 1 Recommendation was published in December.
Development of HTML, CSS, and the DOM had all been taking place in one group, the HTML Editorial Review Board (ERB). Early in 1997, the ERB was split into three working groups: HTML Working group, chaired by Dan Connolly of W3C; DOM Working group, chaired by Lauren Wood of SoftQuad; and CSS Working group, chaired by Chris Lilley of W3C.
The CSS Working Group began tackling issues that had not been addressed with CSS level 1, resulting in the creation of CSS level 2 on November 4, 1997. It was published as a W3C Recommendation on May 12, 1998. CSS level 3, which was started in 1998, is still under development as of 2014.
In 2005 the CSS Working Groups decided to enforce the requirements for standards more strictly. This meant that already published standards like CSS 2.1, CSS 3 Selectors and CSS 3 Text were pulled back from Candidate Recommendation to Working Draft level.
6.3 MYSQL Server
MySQL is an open-source relational database management system (RDBMS);[6] in July 2013, it was the world's second most widely used RDBMS, and the most widely used open-source client–server model RDBMS. It is named after co-founder Michael Widenius's daughter, My. The SQL acronym stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedishcompany MySQL AB, now owned by Oracle Corporation. For proprietary use, several paid editions are available, and offer additional functionality.
SQL Server Management Studio (SSMS) is a software application first launched with Microsoft SQL Server 2005 that is used for configuring, managing, and administering all components within Microsoft SQL Server. The tool includes both script editors and graphical tools which work with objects and features of the server.[1]
A central feature of SSMS is the Object Explorer, which allows the user to browse, select, and act upon any of the objects within the server.[2] It also shipped a separate Express edition that could be freely downloaded, however recent versions of SSMS are fully capable of connecting to and manage any SQL Server Express instance. Microsoft also incorporated backwards compatibility for older versions of SQL Server thus allowing a newer version of SSMS to connect to older versions of SQL Server instances.
Starting from version 11, the application was based on the Visual Studio 2010 shell, using WPF for the user interface.
In June 2015, Microsoft announced their intention to release future versions of SSMS independently of SQL Server database engine releases.[3].
6.4PHP
PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. Originally created by RasmusLerdorf in 1994, the PHP reference implementation is now produced by The PHP Group. PHP originally stood for Personal Home Page, but it now stands for therecursive backronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with various web template systems, web content management system and web frameworks. PHP code is usually processed by a PHPinterpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface(CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system andplatform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.
PHP is a server-side scripting language designed primarily for web development but also used as a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994,[4] the PHP reference implementation is now produced by The PHP Development Team.[5] PHP originally stood for Personal Home Page,[4] but it now stands for the recursive acronym PHP: Hypertext Preprocessor.[6]
PHP code may be embedded into HTML or HTML5 code, or it can be used in combination with various web template systems, web content management systems and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. android based projects combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface (CLI) and can be used to implement standalone graphical applications.[7]
The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.[8]
The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.[9]
PHP development began in 1995 when Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C,[10][11][12] which he used to maintain his personal homepage. He extended them to work with web forms and to communicate with databases, and called this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.
PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page Tools (PHP Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi on June 8, 1995.[13][14] This release already had the basic functionality that PHP has as of 2013. This included Perl-like variables, form handling, and the ability to embed HTML. The syntax resembled that of Perl but was simpler, more limited and less consistent.[5]
Lerdorf did not intend the early PHP to become a new programming language, but it grew organically, with Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any intent to write a programming language […] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way."[15] A development team began to form and, after months of work and beta testing, officially released PHP/FI 2 in November 1997.
The fact that PHP lacked an original overall design but instead developed organically has led to inconsistent naming of functions and inconsistent ordering of their parameters.[16] In some cases, the function names were chosen to match the lower-level libraries which PHP was "wrapping",[17] while in some very early versions of PHP the length of the function names was used internally as a hash function, so names were chosen to improve the distribution of hash values.[18]
6.5 ANGULAR JAVA SCRIPT
AngularJS (commonly referred to as "Angular" or "Angular.js") is an open-source web application framework mainly maintained by Google and by a community of individuals and corporations to address many of the challenges encountered in developing single-page applications. It aims to simplify both the development and the testing of such applications by providing a framework for client-side model–view–controller (MVC) and model–view–viewmodel(MVVM) architectures, along with components commonly used in rich Internet applications.
The AngularJS framework works by first reading the HTML page, which has embedded into it additional custom tag attributes. Angular interprets those attributes as directives to bind input or output parts of the page to a model that is represented by standard JavaScript variables. The values of those JavaScript variables can be manually set within the code, or retrieved from static or dynamic JSON resources.
According to JavaScript analytics service Libscore, AngularJS is used on the websites of Wolfram Alpha, NBC,Walgreens, Intel, Sprint, ABC News, and approximately 8,400 other sites out of 1 million tested in July 2015.
AngularJS is the frontend part of the MEAN stack, consisting of MongoDB database, Express.js web application server framework, Angular.js itself, and Node.js runtime environment.
AngularJS is an open source web application framework. It was originally developed in 2009 by Misko Hevery and Adam Abrons. It is now maintained by Google. Its latest version is 1.4.3.
Definition of AngularJS as put by its official documentation is as follows −
AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template language and lets you extend HTML's syntax to express your application's components clearly and succinctly. Angular's data binding and dependency injection eliminate much of the code you currently have to write. And it all happens within the browser, making it an ideal partner with any server technology.
Features
AngularJS is a powerful JavaScript based development framework to create RICH Internet Application(RIA).
AngularJS provides developers options to write client side application (using JavaScript) in a clean MVC(Model View Controller) way.
Application written in AngularJS is cross-browser compliant. AngularJS automatically handles JavaScript code suitable for each browser.
AngularJS is open source, completely free, and used by thousands of developers around the world. It is licensed under the Apache License version 2.0.
Overall, AngularJS is a framework to build large scale and high performance web application while keeping them as easy-to-maintain.
Core Features
Following are most important core features of AngularJS −
Data-binding − It is the automatic synchronization of data between model and view components.
Scope − These are objects that refer to the model. They act as a glue between controller and view.
Controller − These are JavaScript functions that are bound to a particular scope.
Services − AngularJS come with several built-in services for example $https: to make a XMLHttpRequests. These are singleton objects which are instantiated only once in app.
Filters − These select a subset of items from an array and returns a new array.
Directives − Directives are markers on DOM elements (such as elements, attributes, css, and more). These can be used to create custom HTML tags that serve as new, custom widgets. AngularJS has built-in directives (ngBind, ngModel...)
Templates − These are the rendered view with information from the controller and model. These can be a single file (like index.html) or multiple views in one page using "partials".
Routing − It is concept of switching views.
Model View Whatever − MVC is a design pattern for dividing an application into different parts (called Model, View and Controller), each with distinct responsibilities. AngularJS does not implement MVC in the traditional sense, but rather something closer to MVVM (Model-View-ViewModel). The Angular JS team refers it humorously as Model View Whatever.
Deep Linking − Deep linking allows you to encode the state of application in the URL so that it can be bookmarked. The application can then be restored from the URL to the same state.
Dependency Injection − AngularJS has a built-in dependency injection subsystem that helps the developer by making the application easier to develop, understand, and test.
CHAPTER 7- SYSTEM STUDY
7.1 FEASIBILITY STUDY
The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
• ECONOMICAL FEASIBILITY
• TECHNICAL FEASIBILITY
• SOCIAL FEASIBILITY
ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.
CHAPTER 8-TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.
SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.
8.1Non Functional Requirements
Non-functional requirements are the quality requirements that stipulate how well software does what it has to do. android app project ideas are Quality attributes of any system; these can be seen at the execution of the system and they can also be the part of the system architecture.
8.2 Accuracy:
The system will be accurate and reliable based on the design architecture. If there is any problem in the accuracy then the system will provide alternative ways to solve the problem.
8.3 Usability:
The proposed system will be simple and easy to use by the users. The users will comfort in order to communicate with the system. The user will be provided with an easy interface of the system.
8.4 Accessibility:
The system will be accessible through internet and there should be no any known problem.
8.5 Performance:
The system performance will be at its best when performing the functionality of the system.
8.6 Reliability:
The proposed system will be reliable in all circumstances and if there is any problem that will be affectively handle in the design.
8.7 Security:
The proposed system will be highly secured; every user will be required registration and username/password to use the system. The system will do the proper authorization and authentication of the users based on their types and their requirements. The proposed system will be designed persistently to avoid any misuse of the application.
CHAPTER 9-SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub-assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.
TYPES OF TESTS
Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.
Integration testing
Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined.
System Test
System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without considering how the software works.
9.1 Unit Testing:
Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.
Test objectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
Features to be tested
• Verify that the entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page
9.2 Integration Testing
Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects.
The task of the integration test is to check that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
9.3 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
CHAPTER 10– CONCLUSIONS
The project entitled as College Management System is the system that deals with the issues related to a particular institution. This project is successfully implemented with all the features mentioned in system requirements specification. The application provides appropriate information to users according to the chosen service. The project is designed keeping in view the day to day problems faced by a college.
CHAPTER 11- REFERENCES
1. Drucker, Peter, F., 1981. Management: Tasks, Responsibilities and Practices, Allied Publishers, New Delhi.
2. Hodgets, Richard M., 1986, Management Theory: process and Practice, Academic Press, London.
3. Stoner, James. A.F. and Freeman.E.R., 1989. Management, Prentice Hall of India, New Delhi.
4. Katz R.L., 1974. Skills of an Effective Administrator, Harvard Business Review, 52(5) 90- 102.
5. Newman, William Hsummer, Charles E. and Warren, E, 1974. The Process of Management: Concepts, Behaviour and Practice, Prentice Hall of India; New Delhi.
</bold>
ABSTRACT 2
CHAPTER 1 –INTRODUCTION 3
1.1 Objectives 7
1.2 System Specifications 7
CHAPTER 2 – LITERATURE REVIEW 8
CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM 12
3.1 Module Description 12
CHAPTER 4 – DESIGN 15
4.1UML Diagrams: 15
4.1.1Usecase Diagrams: 16
4.1.2 Sequence Diagram: 17
4.1.3 Collaborate Diagram: 18
CHAPTER 5 - OUTPUT SCREENSHOTS 22
CHAPTER 6 – IMPLEMENTATION DETAILS 23
6.1 Introduction to Html Framework 23
6.2 Cascading Style Sheets (CSS) 26
6.3 MYSQL Server 34
6.4PHP 35
6.5 ANGULAR JAVA SCRIPT 38
CHAPTER 7- SYSTEM STUDY 41
CHAPTER 8-TECHNICAL FEASIBILITY 42
CHAPTER 9-SYSTEM TESTING 45
CHAPTER 10– CONCLUSIONS 50
CHAPTER 11- REFERENCES 51
ABSTRACT
An Android application for college is an application that can be accessed throughout the organization and especially by students well with proper login provided when needed. This application can be used by students using their smart phones. Using this application students will able to stay updated with their college events, circular notices, exam time table. An android based college campus to share the college campus activities application will provide updates to the students of their respective departments, notices regarding the recruiting company, campus interview date and other placement activities.
CHAPTER 1 –INTRODUCTION
The software facilitates the administrators to know the present status of a student of the college. The software gives the information such as student personal data, student fees details, results etc. Generating the print reports of student personal, fee as well as result details…. Hence android app project conclude that the present system (CMS for Colleges) would definitely help the user by saving time and effort by reducing the processing time and volume of errors. The efficiency of the work done would be improved and work satisfaction on the part of the employees after computerization would definitely on high. The customer satisfaction would be definitely higher when compared to the old manual system
The existing system which we using in our college is traditional process is a complete manual process. Now-a-days, education is playing very significant role in the society. Day-by-day, the percentage of illiterates are decreasing and the percentage of literates is increasing. Education will change the society in all the aspects and everyone wants to study higher professional degrees. Admissions are increasing day by day so there by ratio of establishment new colleges and schools are also increasing. But the actual challenge is starting from now. Most of the schools and colleges are maintain student information in records. When the number of records increased, it is difficult to maintain the information of each student in the old manual system. Maintaining the records manually leads to error prone and required more man power and it consumes more time for processing the records.
The main objective of developing the current project entitled “COLLEGE MANAGEMENT SYSTEM FOR COLLEGES” is to build effective system which is fast, accurate, consistency, reliable and flexible enough so that it can incorporate any future enhancements.
By automating the system using computers, sophisticated technology can be used for making the information more flexible, accurate, and secure and user friendly.
Time and man power can be more effectively utilized and online information can be easily available to the user and at the same time we can maintain higher level of security. Every user such as student, staff and administration can able to see the information of each student through online from anywhere and anytime. These types of CMS are already available in our markets, but it does not have the feature that we are providing to our college. android app ideas for college project of the companies are improving this project on the platform .NET. that seems to be complicated and to use The main functionality such as ENTERING AND RETRIVING of the attendance in the CMS will not be provided by the companies who had developed this project earlier. We are going to introduce our project on a special platform JAVA which is very user friendly. Here we will provide the high permissions to the Admin so he can handle the complete college for better security and maintenance. There will be different permissions to the admin and faculty.
Until recently the place of the College Management System (CMS). Now-a-days, education is playing very significant role in the society. Day-by-day, the percentage of illiterates are decreasing and the percentage of literates is increasing. Education will change the society in all the aspects and everyone wants to study higher professional degrees. Admissions are increasing day by day so there by. Ratio of establishment new colleges and schools are also increasing. But the actual challenge is starting from now. Most of the schools and colleges are maintain student information in records. When the number of records increased, it is difficult to maintain the information of each student in the old manual system.
Maintaining the records manually leads to error prone and required more man power and it consumes more time for processing the records.
While virtual learning environments have been available in some capacity since 1960, “the PLATO system featured multiple roles, including students who could study assigned lessons and communicate with teachers through on-line notes, instructors, who could examine student progress data, as well as communicate and take lessons themselves, and authors, who could do all of the above, plus create new lessons” (Wikipedia, 2006a, 1960s section,). Learning management systems have only been available, in roughly their present form, since the 1990s (Vollmer , 2003), with Blackboard and WebCT being broadly adopted in universities and colleges by early 2000 (Online, 2006). Initial versions of an LMS focused on organizing and managing course content and learners.
As with many organizations, higher education was unsure about the role of technology in the educational process. The rapid penetration of learning management systems as key tools for learning occurs in a vacuum of solid research as to their effectiveness in increasing learning—or even indication of best practices for technology implementation. Pedagogy is generally a secondary consideration to student management; some researchers attempted to bridge research from face-to-face environments to technology spaces (Chickering & Ehrmann, 1996)—a practice that may be convenient, but errs in assuming that the online space is an extension of physical instruction, not an alternative medium with unique affordances. Learning management systems became the default starting point of technology enabled learning in an environment largely omitting faculty and learner needs. Learning Circuits’ (n.d.) publication,
A Field Guide to Learning Management Systems, revealed the nature of most LMS decisions at committee levels (an experience paralleled in academic environments): “an LMS should integrate with other enterprise application solutions used by HR and accounting, enabling management to measure the impact, effectiveness, and overall cost of training initiatives”. The value of an LMS is ensconced in language of management and control—notions that most academics would perceive as antagonistic to the process of learning. Most LMS options, features, and comparisons (LMS Options, 2006) focus on tools included in a suite, not on how to foster and encourage learning in relation to an organization’s definition of “what it means to learn.” Discussions of features are divorced from emphasis on learning opportunities. Learning Management Systems (LMS) are often viewed as being the starting point (or critical component) of any elearning or blended learning program. This perspective is valid from a management and control standpoint, but antithetical to the way in which most people learn today. Learning management systems like WebCT, Blackboard, and Desire2Learn offer their greatest value to the organization by providing a means to sequence content and create a manageable structure for instructors/administration staff. The “management” aspect of a learning management system creates another problem: much like we used to measure “bums in seats” for program success, we now see statistics of “students enrolled in our LMS” and “number of page views by students” as an indication of success/progress. The underlying assumption is that if we just expose students to the content, learning will happen.
1.1 Objectives
This document is the Software Requirement Specification (SRS) for the College Management System for College (CMS) project .The purpose of this document is to describe the functionality, requirements and general interface of the CMS.
1.2 System Specifications
Hardware Requirements:-
Android
Software Requirements: -
Operating System : Android OS
Front-End : HTML, CSS, and JS
Back-End : Angular JS, PHP, MYSQL
Tool : Cordova
CHAPTER 2 – LITERATURE REVIEW
This project is based on COLLEGE MANAGEMENT SYSTEM. It manages the college information, student information, placement information, various different types of event going on in our college. It also keeps track records of all the information regarding students those who are placed in the various organizations. It has a notice board which contains information about various cultural or technical or any sports which is supposed to be held soon. With the help of this project, you can view the previous videos with the help of internet connection.
This College Management System project developed using PHP programming language. The main aim of this project is to develop an online website which covers all the details of college i.e.; Student attendance details, Event details, Students fees transaction details, Marks details, Photo gallery, etc. Admin is the Super user of this project. All the record stores in MySQL Database. The proposed software will also reduce the cumbersome paperwork, manual labor as well as communication cost.
This paper is aimed at developing an Online Intranet College Management System (CMS) that is of importance to either an educational institution or a college. The system (CMS) is an Intranet based application that can be accessed throughout the institution or a specified department. This system may be used for monitoring attendence for the college. Students as well as staffs logging in may also access or can be search any of the information regarding college. Attendance of the staff and students as well as marks of the students will be updated by staff. This system (C.M.S ) is being developed for an engineering college to maintain and facilitate easy access to information. For this the users must be registered with the system after which they can access as well as modify data as per the permissions given to them. CMS is an intranet based application that aims at providing information to all the levels of management with in an organization. This system can be used as a knowledge/information management system for the college. For a given student/staff (technical/Non-technical) can access the system to either upload or download some information from the database.
The title of the project is “COLLEGE MANAGEMENT SYSTEM FOR COLLEGE” (CMS). CMS is defined as an application based on Intranet that aims to all the levels of management providing information within an organization. This system can be used as a information management system for the college. For a given student/staff (Technical / Non-technical) the Administrator creates login id & password, using these student/ staff (Technical / Non-technical) can access the system to either upload or download some information from the database. The front-end will be HTML pages for client side validation with Java Script where as all business logics will be in Java reside at middle layer. third layer of database will be interacted with these layers, which would be Oracle database. The web server would be Tomcat 5.5 version. Server have Tomcat5.5 as web server is required to start working on this project environment like Java Runtime Environment (JRE) as development environment and Oracle10g as database The project is divided into 6 scenarios; each scenario can be developed independently. And knowledge of Java with oracle10g is desirable to execute this project.
Access/ Search information.
Login to the system through the first page of the application
Change the password after logging into the system
View/change his/her details
Can get help through the help option to view different features of the system.
Students can give feedback on college/staff/any other student.
An admin login should be present who can read as well as remove any uploads
This document describes the product and its requirements and constraints. It provides a primarily non-technical description of the project targeted towards external audiences. This section includes information such as data requirements, functional requirements, and a general description of the product and its interaction with users from the perspective of the client. Section 3 provides specific technical requirements as the team understands them at this time and is intended for an internal audience. This section includes information such as external interface requirements, performance requirements, and any other technical requirements needed to design the software.
The main objective of college management system is to automate all functionalities of a college or university. Using this system you can manage all college management work like admission, fees submission, time table management and result declaration. Using this college management system you can view or update data and information about students and staff easily. This system helps in managing the activity like student admission, student registration, fees submission. Admin can also retrieve information of employee student.
The COLLEGE MANAGEMENT SYSTEM can be used to store student information like attendance, fees, and student result etc. admin can create report regarding any student any time using this system. Using this system you can register new student and their course details. You can submit students fees and can check fees details anytime. You can create exam result and submit in this system. Student can check their result online by logging to the system. You can also add new employee in the system and can check details of the employee easily. Student can also check course detail online from this system.
Using this system you can manage all information of all aspects of a college, its students, faculties, Departments, marks and other curricular activities. College management system provides the easiest way to manage all functionalities of a college. This system facilitates colleges to maintain the functionality related to college employees and their students.
College Management System can store and manage all data of the various departments of a college like Administration, Attendance, Staff details etc. using this system user can retrieve any information related to student, teacher and fees. Using this system teacher can check student attendance anytime. This system also help teacher to announce the result. College administration can also manage college work easily. Admin can check leave, salary and other details of teacher any time. They can also create time table of classes from this system. The Library module is used for the data process of library and book accessing for students and staffs.
Existing Solution:
Its manual process for earlier system.
Its more time consume for all process.
Need for more resources.
Its chance to lose our record or data.
Proposed Solution:
The proposed system consists of three modules: admin panel, Student module. Admin can post their notification about collage, update staff details, student details and collage event details. Students can view all details including staff details.
CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM
3.1 Module Description
An android based college campus to share the college campus activities application will provide updates to the students of their respective departments, notices regarding the recruiting company, campus interview date and other placement activities.
3.2 System Features
In the life of the software development, problem analysis provides a base for design and development phase. The problem is analyzed so that sufficient matter is provided to design a new system. Large problems are sub-divided into smaller once to make them understandable and easy for finding solutions. Same in this project all the task are sub-divided and categorized.
System Modules:
1. Admin (Web Interface):
Log in:
In log in page, admin can only view the shared information. They can’t update or edit any information.
Sign in and Sign up:
The staff will be having an account to update the college information because students know who update the information. In sign up, Staff adds the following details,
o Staff name:
o Department:
o Mobile no:
o Password:
o Confirm password:
Add Students Details and View details:
Admin creates the students details with following requirements,
o Student name
o Register number
o Department
o Year
o Password (Date of birth)
o Gender
Events:
• Sports:
o Game name
o Department Vs
o Date & Time
• Conference:
o Conference Name
o Conducted by
o Department participated
o Place
o Date & Time
• Cultural:
o Date & Time
Placement Details:
o Company Name
o Eligible Candidates (CGPA mark %)
o Skills
o Job Description
o Date & Time
o Place
o Eligible Department
Circular & Other notices:
Any other information are updated this site with specific departments or all departments.
Gallery:
Admin updates any images in this site with specific departments.
2. Students (Android Interface)
Log in:
Students log in with their register number and date of birth (password).
Notification:
Students can get the notification of all new information updated in the application.
View:
Students can only view the information updated in the application, gallery and also view their own details.
Contact:
Students can also view the staff details. In contacts, Staff’s mobile number shows which are updated by staffs.
Offline:
Students can also view the details in offline.
CHAPTER 4 – DESIGN
Design is the first step in the development phase for any techniques and principles for the purpose of defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves three technical activities - design, coding, implementation and testing that are required to build and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions ultimately affecting the success of the software implementation and its ease of maintenance are made. These decisions have the final bearing upon reliability and maintainability of the system. Design is the only way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through which requirements are translated into a representation of software. Software design is conducted in two steps. Preliminary design is concerned with the transformation of requirements into data.
4.1UML Diagrams:
UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and documenting the system. This is the step while developing any product after analysis. The goal from this is to produce a model of the entities involved in the project which later need to be built. The representation of the entities that are to be used in the product being developed need to be designed.
There are various kinds of methods in software design:
• Use case Diagram
• Sequence Diagram
• Collaboration Diagram
4.1.1Usecase Diagrams:
Use case diagrams model behavior within a system and helps the developers understand of what the user require. The stick man represents what’s called an actor.Use case diagram can be useful for getting an overall view of the system and clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction between the use case and actors.
• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system
4.1.2 Sequence Diagram:
Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An interaction diagram shows an interaction, consisting of set of objects and their relationship including the messages that may be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering of messages. Graphically a sequence diagram is a table that shows objects arranged along the X-axis and messages ordered in increasing time along the Y-axis.
4.1.3 Collaborate Diagram:
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML).
DFD Diagram
Student
Admin
CHAPTER 5 - OUTPUT SCREENSHOTS
CHAPTER 6 – IMPLEMENTATION DETAILS
6.1 Introduction to Html Framework
Hyper Text Markup Language, commonly referred to as HTML, is the standard markup language used to create web pages. Along with CSS, and JavaScript, HTML is a cornerstone technology used to create web pages, as well as to create user interfaces for mobile and web applications. Web browsers can read HTML files and render them into visible or audible web pages. HTML describes the structure of a website semantically along with cues for presentation, making it a markup language, rather than a programming language.
HTML elements form the building blocks of HTML pages. HTML allows images and other objects to be embedded and it can be used to create interactive forms. It provides a means to create structured documents by denoting structuralsemantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as
...
surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.HTML can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages. HTML markup can also refer the browser to Cascading Style Sheets (CSS) to define the look and layout of text and other material.
HyperText Markup Language (HTML) is the standard markup language for creating web pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a triad of cornerstone technologies for the World Wide Web.[1] Web browsers receive HTML documents from a webserver or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and other objects, such as interactive forms, may be embedded into the rendered page. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as
...
surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.HTML can embed programs written in a scripting language such as JavaScript which affect the behavior and content of web pages. Inclusion of CSS defines the look and layout of content. The World Wide Web Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.[2]
In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped ENQUIRE, a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo proposing an Internet-based hypertext system.[3] Berners-Lee specified HTML and wrote the browser and server software in late 1990. That year, Berners-Lee and CERN data systems engineer Robert Cailliau collaborated on a joint request for funding, but the project was not formally adopted by CERN. In his personal notes[4] from 1990 he listed[5] "some of the many areas in which hypertext is used" and put an encyclopedia first.
The first publicly available description of HTML was a document called "HTML Tags", first mentioned on the Internet by Tim Berners-Lee in late 1991.[6][7] It describes 18 elements comprising the initial, relatively simple design of HTML. Except for the hyperlink tag, these were strongly influenced by SGMLguid, an in-house Standard Generalized Markup Language (SGML)-based documentation format at CERN. Eleven of these elements still exist in HTML 4.[8]
HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visual or audible web pages. Default characteristics for every item of HTML markup are defined in the browser, and these characteristics can be altered or enhanced by the web page designer's additional use of CSS. Many of the text elements are found in the 1988 ISO technical report TR 9537 Techniques for using SGML, which in turn covers the features of early text formatting languages such as that used by the RUNOFF command developed in the early 1960s for the CTSS (Compatible Time-Sharing System) operating system: these formatting commands were derived from the commands used by typesetters to manually format documents. However, the SGML concept of generalized markup is based on elements (nested annotated ranges with attributes) rather than merely print effects, with also the separation of structure and markup; HTML has been progressively moved in this direction with CSS.
Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the first proposal for an HTML specification, the "Hypertext Markup Language (HTML)" Internet Draft by Berners-Lee and Dan Connolly, which included an SGML Document Type Definition to define the grammar.[9][10] The draft expired after six months, but was notable for its acknowledgment of the NCSA Mosaic browser's custom tag for embedding in-line images, reflecting the IETF's philosophy of basing standards on successful prototypes.[11] Similarly, Dave Raggett's competing Internet-Draft, "HTML+ (Hypertext Markup Format)", from late 1993, suggested standardizing already-implemented features like tables and fill-out forms.[12]
After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML Working Group, which in 1995 completed "HTML 2.0", the first HTML specification intended to be treated as a standard against which future implementations should be based.[13]
Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained, with input from commercial software vendors, by the World Wide Web Consortium (W3C).[14] However, in 2000, HTML also became an international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with further errata published through 2001. In 2004, development began on HTML5 in the Web Hypertext Application Technology Working Group (WHATWG), which became a joint deliverable with the W3C in 2008, and completed and standardized on 28 October 2014.[15]
6.2 Cascading Style Sheets (CSS)
CSS is a style sheet language used for describing the presentation of a document written in a markup language. Although android mini project topics used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG andXUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.
CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts. This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content, such as semantically insignificant tables that were widely used to format pages before consistent CSS rendering was available in all major browsers. CSS makes it possible to separate presentation instructions from the HTML content in a separate file or style section of the HTML file. For each matching HTML element, it provides a list of formatting instructions. For example, a CSS rule might specify that "all heading 1 elements should be bold", leaving pure semantic HTML markup that asserts "this text is a level 1 heading" without formatting code such as a
<bold>
tag indicating how such text should be displayed.
This separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser orscreen reader) and on Braille-based, tactile devices. It can also be used to display the web page differently depending on the screen size or device on which it is being viewed. Although the author of a web page typically links to a CSS file within the markup file, readers can specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author has specified. If the author or the reader did not link the document to a style sheet, the default style of the browser will be applied. Another advantage of CSS is that aesthetic changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in one file, rather than by a laborious (and thus expensive) process of crawling over every document line by line, changing markup.
The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a document written in a markup language.[1] Although most often used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG and XUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.[2]
CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts.[3] This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content.
Separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (via speech-based browser or screen reader), and on Braille-based tactile devices. It can also display the web page differently depending on the screen size or viewing device. Readers can also specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author specified.
Changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in the CSS file they use, rather than by changing markup in the documents.
The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998). The W3C operates a free CSS validation service for CSS documents.
In CSS, selectors declare which part of the markup a style applies to by matching tags and attributes in the markup itself.
Selectors may apply to:
all elements of a specific type, e.g. the second-level headers h2
elements specified by attribute, in particular:
id: an identifier unique within the document
class: an identifier that can annotate multiple elements in a document
elements depending on how they are placed relative to others in the document tree.
Classes and IDs are case-sensitive, start with letters, and can include alphanumeric characters and underscores. A class may apply to any number of instances of any elements. An ID may only be applied to a single element.
Pseudo-classes are used in CSS selectors to permit formatting based on information that is not contained in the document tree. One example of a widely used pseudo-class is :hover, which identifies content only when the user "points to" the visible element, usually by holding the mouse cursor over it. It is appended to a selector as in a:hover or #elementid:hover. A pseudo-class classifies document elements, such as :link or :visited, whereas a pseudo-element makes a selection that may consist of partial elements, such as ::first-line or ::first-letter.[5]
Selectors may be combined in many ways to achieve great specificity and flexibility.[6] Multiple selectors may be joined in a spaced list to specify elements by location, element type, id, class, or any combination thereof. The order of the selectors is important. For example, div .myClass color: red; applies to all elements of class myClass that are inside div elements, whereas .myClass div color: red; applies to all div elements that are in elements of class myClass.
CSS information can be provided from various sources. These sources can be the web browser, the user and the author. The information from the author can be further classified into inline, media type, importance, selector specificity, rule order, inheritance and property definition. CSS style information can be in a separate document or it can be embedded into an HTML document. Multiple style sheets can be imported. Different styles can be applied depending on the output device being used; for example, the screen version can be quite different from the printed version, so that authors can tailor the presentation appropriately for each medium.
The style sheet with the highest priority controls the content display. Declarations not set in the highest priority source are passed on to a source of lower priority, such as the user agent style. This process is called cascading.
One of the goals of CSS is to allow users greater control over presentation. Someone who finds red italic headings difficult to read may apply a different style sheet. Depending on the browser and the web site, a user may choose from various style sheets provided by the designers, or may remove all added styles and view the site using the browser's default styling, or may override just the red italic heading style without altering other attributes.
CSS was first proposed by Håkon Wium Lie on October 10, 1994.[16] At the time, Lie was working with Tim Berners-Lee at CERN.[17] Several other style sheet languages for the web were proposed around the same time, and discussions on public mailing lists and inside World Wide Web Consortium resulted in the first W3C CSS Recommendation (CSS1)[18] being released in 1996. In particular, Bert Bos' proposal was influential; he became co-author of CSS1 and is regarded as co-creator of CSS.[19]
Style sheets have existed in one form or another since the beginnings of Standard Generalized Markup Language (SGML) in the 1980s, and CSS was developed to provide style sheets for the web.[20] One requirement for a web style sheet language was for style sheets to come from different sources on the web. Therefore, existing style sheet languages like DSSSL and FOSI were not suitable. CSS, on the other hand, let a document's style be influenced by multiple style sheets by way of "cascading" styles.[20]
As HTML grew, it came to encompass a wider variety of stylistic capabilities to meet the demands of web developers. This evolution gave the designer more control over site appearance, at the cost of more complex HTML. Variations in web browser implementations, such as ViolaWWW and WorldWideWeb,[21] made consistent site appearance difficult, and users had less control over how web content was displayed. The browser/editor developed by Tim Berners-Lee had style sheets that were hard-coded into the program. The style sheets could therefore not be linked to documents on the web.[22] Robert Cailliau, also of CERN, wanted to separate the structure from the presentation so that different style sheets could describe different presentation for printing, screen-based presentations, and editors.[21]
Improving web presentation capabilities was a topic of interest to many in the web community and nine different style sheet languages were proposed on the www-style mailing list.[20] Of these nine proposals, two were especially influential on what became CSS: Cascading HTML Style Sheets[16] and Stream-based Style Sheet Proposal (SSP).[19][23] Two browsers served as testbeds for the initial proposals; Lie worked with Yves Lafon to implement CSS in Dave Raggett's Arena browser.[24][25][26] Bert Bos implemented his own SSP proposal in the Argo browser.[19] Thereafter, Lie and Bos worked together to develop the CSS standard (the 'H' was removed from the name because these style sheets could also be applied to other markup languages besides HTML).[17]
Lie's proposal was presented at the "Mosaic and the Web" conference (later called WWW2) in Chicago, Illinois in 1994, and again with Bert Bos in 1995.[17] Around this time the W3C was already being established, and took an interest in the development of CSS. It organized a workshop toward that end chaired by Steven Pemberton. This resulted in W3C adding work on CSS to the deliverables of the HTML editorial review board (ERB). Lie and Bos were the primary technical staff on this aspect of the project, with additional members, including Thomas Reardon of Microsoft, participating as well. In August 1996 Netscape Communication Corporation presented an alternative style sheet language called JavaScript Style Sheets (JSSS).[17] The spec was never finished and is deprecated.[27] By the end of 1996, CSS was ready to become official, and the CSS level 1 Recommendation was published in December.
Development of HTML, CSS, and the DOM had all been taking place in one group, the HTML Editorial Review Board (ERB). Early in 1997, the ERB was split into three working groups: HTML Working group, chaired by Dan Connolly of W3C; DOM Working group, chaired by Lauren Wood of SoftQuad; and CSS Working group, chaired by Chris Lilley of W3C.
The CSS Working Group began tackling issues that had not been addressed with CSS level 1, resulting in the creation of CSS level 2 on November 4, 1997. It was published as a W3C Recommendation on May 12, 1998. CSS level 3, which was started in 1998, is still under development as of 2014.
In 2005 the CSS Working Groups decided to enforce the requirements for standards more strictly. This meant that already published standards like CSS 2.1, CSS 3 Selectors and CSS 3 Text were pulled back from Candidate Recommendation to Working Draft level.
6.3 MYSQL Server
MySQL is an open-source relational database management system (RDBMS);[6] in July 2013, it was the world's second most widely used RDBMS, and the most widely used open-source client–server model RDBMS. It is named after co-founder Michael Widenius's daughter, My. The SQL acronym stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedishcompany MySQL AB, now owned by Oracle Corporation. For proprietary use, several paid editions are available, and offer additional functionality.
SQL Server Management Studio (SSMS) is a software application first launched with Microsoft SQL Server 2005 that is used for configuring, managing, and administering all components within Microsoft SQL Server. The tool includes both script editors and graphical tools which work with objects and features of the server.[1]
A central feature of SSMS is the Object Explorer, which allows the user to browse, select, and act upon any of the objects within the server.[2] It also shipped a separate Express edition that could be freely downloaded, however recent versions of SSMS are fully capable of connecting to and manage any SQL Server Express instance. Microsoft also incorporated backwards compatibility for older versions of SQL Server thus allowing a newer version of SSMS to connect to older versions of SQL Server instances.
Starting from version 11, the application was based on the Visual Studio 2010 shell, using WPF for the user interface.
In June 2015, Microsoft announced their intention to release future versions of SSMS independently of SQL Server database engine releases.[3].
6.4PHP
PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. Originally created by RasmusLerdorf in 1994, the PHP reference implementation is now produced by The PHP Group. PHP originally stood for Personal Home Page, but it now stands for therecursive backronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with various web template systems, web content management system and web frameworks. PHP code is usually processed by a PHPinterpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface(CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system andplatform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.
PHP is a server-side scripting language designed primarily for web development but also used as a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994,[4] the PHP reference implementation is now produced by The PHP Development Team.[5] PHP originally stood for Personal Home Page,[4] but it now stands for the recursive acronym PHP: Hypertext Preprocessor.[6]
PHP code may be embedded into HTML or HTML5 code, or it can be used in combination with various web template systems, web content management systems and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. android based projects combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface (CLI) and can be used to implement standalone graphical applications.[7]
The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.[8]
The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.[9]
PHP development began in 1995 when Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C,[10][11][12] which he used to maintain his personal homepage. He extended them to work with web forms and to communicate with databases, and called this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.
PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page Tools (PHP Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi on June 8, 1995.[13][14] This release already had the basic functionality that PHP has as of 2013. This included Perl-like variables, form handling, and the ability to embed HTML. The syntax resembled that of Perl but was simpler, more limited and less consistent.[5]
Lerdorf did not intend the early PHP to become a new programming language, but it grew organically, with Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any intent to write a programming language […] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way."[15] A development team began to form and, after months of work and beta testing, officially released PHP/FI 2 in November 1997.
The fact that PHP lacked an original overall design but instead developed organically has led to inconsistent naming of functions and inconsistent ordering of their parameters.[16] In some cases, the function names were chosen to match the lower-level libraries which PHP was "wrapping",[17] while in some very early versions of PHP the length of the function names was used internally as a hash function, so names were chosen to improve the distribution of hash values.[18]
6.5 ANGULAR JAVA SCRIPT
AngularJS (commonly referred to as "Angular" or "Angular.js") is an open-source web application framework mainly maintained by Google and by a community of individuals and corporations to address many of the challenges encountered in developing single-page applications. It aims to simplify both the development and the testing of such applications by providing a framework for client-side model–view–controller (MVC) and model–view–viewmodel(MVVM) architectures, along with components commonly used in rich Internet applications.
The AngularJS framework works by first reading the HTML page, which has embedded into it additional custom tag attributes. Angular interprets those attributes as directives to bind input or output parts of the page to a model that is represented by standard JavaScript variables. The values of those JavaScript variables can be manually set within the code, or retrieved from static or dynamic JSON resources.
According to JavaScript analytics service Libscore, AngularJS is used on the websites of Wolfram Alpha, NBC,Walgreens, Intel, Sprint, ABC News, and approximately 8,400 other sites out of 1 million tested in July 2015.
AngularJS is the frontend part of the MEAN stack, consisting of MongoDB database, Express.js web application server framework, Angular.js itself, and Node.js runtime environment.
AngularJS is an open source web application framework. It was originally developed in 2009 by Misko Hevery and Adam Abrons. It is now maintained by Google. Its latest version is 1.4.3.
Definition of AngularJS as put by its official documentation is as follows −
AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template language and lets you extend HTML's syntax to express your application's components clearly and succinctly. Angular's data binding and dependency injection eliminate much of the code you currently have to write. And it all happens within the browser, making it an ideal partner with any server technology.
Features
AngularJS is a powerful JavaScript based development framework to create RICH Internet Application(RIA).
AngularJS provides developers options to write client side application (using JavaScript) in a clean MVC(Model View Controller) way.
Application written in AngularJS is cross-browser compliant. AngularJS automatically handles JavaScript code suitable for each browser.
AngularJS is open source, completely free, and used by thousands of developers around the world. It is licensed under the Apache License version 2.0.
Overall, AngularJS is a framework to build large scale and high performance web application while keeping them as easy-to-maintain.
Core Features
Following are most important core features of AngularJS −
Data-binding − It is the automatic synchronization of data between model and view components.
Scope − These are objects that refer to the model. They act as a glue between controller and view.
Controller − These are JavaScript functions that are bound to a particular scope.
Services − AngularJS come with several built-in services for example $https: to make a XMLHttpRequests. These are singleton objects which are instantiated only once in app.
Filters − These select a subset of items from an array and returns a new array.
Directives − Directives are markers on DOM elements (such as elements, attributes, css, and more). These can be used to create custom HTML tags that serve as new, custom widgets. AngularJS has built-in directives (ngBind, ngModel...)
Templates − These are the rendered view with information from the controller and model. These can be a single file (like index.html) or multiple views in one page using "partials".
Routing − It is concept of switching views.
Model View Whatever − MVC is a design pattern for dividing an application into different parts (called Model, View and Controller), each with distinct responsibilities. AngularJS does not implement MVC in the traditional sense, but rather something closer to MVVM (Model-View-ViewModel). The Angular JS team refers it humorously as Model View Whatever.
Deep Linking − Deep linking allows you to encode the state of application in the URL so that it can be bookmarked. The application can then be restored from the URL to the same state.
Dependency Injection − AngularJS has a built-in dependency injection subsystem that helps the developer by making the application easier to develop, understand, and test.
CHAPTER 7- SYSTEM STUDY
7.1 FEASIBILITY STUDY
The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
• ECONOMICAL FEASIBILITY
• TECHNICAL FEASIBILITY
• SOCIAL FEASIBILITY
ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.
CHAPTER 8-TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.
SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.
8.1Non Functional Requirements
Non-functional requirements are the quality requirements that stipulate how well software does what it has to do. android app project ideas are Quality attributes of any system; these can be seen at the execution of the system and they can also be the part of the system architecture.
8.2 Accuracy:
The system will be accurate and reliable based on the design architecture. If there is any problem in the accuracy then the system will provide alternative ways to solve the problem.
8.3 Usability:
The proposed system will be simple and easy to use by the users. The users will comfort in order to communicate with the system. The user will be provided with an easy interface of the system.
8.4 Accessibility:
The system will be accessible through internet and there should be no any known problem.
8.5 Performance:
The system performance will be at its best when performing the functionality of the system.
8.6 Reliability:
The proposed system will be reliable in all circumstances and if there is any problem that will be affectively handle in the design.
8.7 Security:
The proposed system will be highly secured; every user will be required registration and username/password to use the system. The system will do the proper authorization and authentication of the users based on their types and their requirements. The proposed system will be designed persistently to avoid any misuse of the application.
CHAPTER 9-SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub-assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.
TYPES OF TESTS
Unit testing
Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.
Integration testing
Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined.
System Test
System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without considering how the software works.
9.1 Unit Testing:
Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.
Test objectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
Features to be tested
• Verify that the entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page
9.2 Integration Testing
Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects.
The task of the integration test is to check that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
9.3 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
CHAPTER 10– CONCLUSIONS
The project entitled as College Management System is the system that deals with the issues related to a particular institution. This project is successfully implemented with all the features mentioned in system requirements specification. The application provides appropriate information to users according to the chosen service. The project is designed keeping in view the day to day problems faced by a college.
CHAPTER 11- REFERENCES
1. Drucker, Peter, F., 1981. Management: Tasks, Responsibilities and Practices, Allied Publishers, New Delhi.
2. Hodgets, Richard M., 1986, Management Theory: process and Practice, Academic Press, London.
3. Stoner, James. A.F. and Freeman.E.R., 1989. Management, Prentice Hall of India, New Delhi.
4. Katz R.L., 1974. Skills of an Effective Administrator, Harvard Business Review, 52(5) 90- 102.
5. Newman, William Hsummer, Charles E. and Warren, E, 1974. The Process of Management: Concepts, Behaviour and Practice, Prentice Hall of India; New Delhi.
</bold>
