Continue<\/a><\/p>\nThe SaveName.jsp saves the user’s name in the session, and puts a link to another page, NextPage.jsp.
\nNextPage.jsp shows how to retrieve the saved name.<\/p>\n
Hello, <%= session.getAttribute( “theName” ) %><\/p>\n
If you bring up two different browsers (not different windows of the same browser), or run two browsers from two different machines, you can put one name in one browser and another name in another browser, and both names will be kept track of.
\nThe session is kept around until a timeout period. Then it is assumed the user is no longer visiting the site, and the session is discarded.<\/p>\n
My SQL
\nIntroduction
\nMy SQL is an application used to create computer databases for the Microsoft Windows family of server operating systems. It provides an environment used to generate databases that can be accessed from workstations, the web, or other media such as a personal digital assistant (PDA). MY SQL is probably the most accessible and the most documented enterprise database environment right now. This also means that you can learn it a little quicker than most other database environments on the market<\/p>\n
To start, you must have a computer that runs an appropriate operating system like Microsoft Windows >= XP Home Edition: that includes Windows XP Home Edition, Windows XP Professional, Windows 2000 Professional, or any version of Windows Server 2003. In this case, you must install MY SQL Yog.<\/p>\n
What is SQL Used for:<\/p>\n
Using SQL one can create and maintain data manipulation objects such as table, views, sequence etc. These data manipulation objects will be created and stored on the server’s hard disk drive, in a tablespace, to which the user has been assigned.
\nOnce these data manipulation objects are created, they are used extensively in commercial applications.
\nDML, DCL, DDL:<\/p>\n
In addition to the creation of data manipulation objects, the actual manipulation of data within these objects is done using SQL.<\/p>\n
The SQL sentences that are used to create these objects are called DDL’s or Data Definition Language. The SQL sentences used to manipulate data within these objects are called DML’s or Data Manipulation Language. The SQL sentences, which are used to control the behavior of these objects, are called DCL’s or Data Control Language.<\/p>\n
Data Type
\nBuilt-in data types
\nIn My Sql, each object (such as column, variable, or parameter) has a related data type, which is an attribute that specifies the type of data that the object can hold.
\nMy SQL ships with 27 built-in (system) data types. They are:
\nData Types Description
\nbigint Integer data from -2^63 through 2^63-1
\nint Integer data from -2^31 through 2^31 \u2013 1
\nSmallint Integer data from -2^15 through 2^15 \u2013 1
\ntinyint Integer data from 0 through 255
\nbit Integer data with either a 1 or 0 value
\nDecimal Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
\nnumeric Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
\nmoney Monetary data values from -2^63 through 2^63 – 1
\nsmallmoney Monetary data values from -214,748.3648 through +214,748.3647
\nfloat Floating precision number data from -1.79E + 308 through 1.79E + 308
\nreal Floating precision number data from -3.40E + 38 through 3.40E + 38
\ndatetime Date and time data from January 1, 1753, through December 31, 9999,
\nwith an accuracy of 3.33 milliseconds
\nsmalldatetime Date and time data from January 1, 1900, through June 6, 2079,
\nwith an accuracy of one minute
\nchar Fixed-length character data with a maximum length of 8,000 characters
\nvarchar Variable-length data with a maximum of 8,000 characters
\ntext Variable-length data with a maximum length of 2^31 – 1 characters
\nnchar Fixed-length Unicode data with a maximum length of 4,000 characters
\nnvarchar Variable-length Unicode data with a maximum length of 4,000 characters
\nNtext Variable-length Unicode data with a maximum length of 2^30 – 1 characters
\nbinary Fixed-length binary data with a maximum length of 8,000 bytes
\nvarbinary Variable-length binary data with a maximum length of 8,000 bytes
\nimage Variable-length binary data with a maximum length of 2^31 – 1 bytes
\ncursor A reference to a cursor
\nsql_variant A data type that stores values of various data types,
\nexcept text, ntext, timestamp, and sql_variant
\nTable A special data type used to store a result set for later processing
\ntimestamp A database-wide unique number that gets updated every time
\na row gets updated
\nuniqueidentifier A globally unique identifier
\nSome of these data types (bigint, sql_variant, and table) are only available in MY SQL 0, while some were supported under the previous My SQL r versions.
\nUser-defined data types
\nMy SQL supports user-defined data types too. User-defined data types provide a mechanism for applying a name to a data type that is more descriptive of the types of values to be held in the object. Using user-defined data type can make it easier for a programmer or database administrator to understand the intended use of any object defined with the data type. The user-defined data types are based on the system data types and can be used to predefine several attributes of a column, such as its data type, length, and whether it supports NULL values. To create a user-defined data type, you can use the sp_addtype system stored procedure or you could add one using the Enterprise Manager. When you create a user-defined data type, you should specify the following three properties:
\n\u2022 Data type’s name.
\n\u2022 Built-in data type upon which the new data type is based.
\n\u2022 Whether it can contain NULL values.
\nThe following example creates a user-defined data type based on money data type named cursale that cannot be NULL:
\nEXEC sp_addtype cursale, money, ‘NOT NULL’
\nGO
\nBoth system and user-defined data types are used to enforce data integrity. It is very important that we put forth a lot of effort while designing tables: the better you design
\nyour tables, the more time you can work without any performance problems. In an ideal case, you never will update the structure of your tables.<\/p>\n
ENVIRONMENT \/ OPERATING SYSTEM<\/p>\n
The age of standalone computing is long gone and it is now a world of networks. In this context, it is imperative for users to understand issues involved in working in a multi-user environment. Windows NT today is the most sought after Multi-user Operating System in the world. This is a 32-bit, powerful, user friendly and robust network operating system from Microsoft.
\nWindows NT is a big step up from Windows 95 both in terms of price and in terms of capabilities. NT Server is a well-built, fully functional, multi-user, multitasking operating system.
\nThe release of NT Server 4 adds the popular Windows 95 user interface, the Internet Information Server (IIS) \u2013 capable of running Web, FTP, and Gopher services – a search engine called Index Server, the FrontPage HTML authoring package, and the Internet Explorer, all of which make Windows NT server a tough act to beat as a robust, capable web server.
\nThe suggested Operating System for the server computer is Windows NT Server and for client computer is Windows 95.<\/p>\n
2.1 PRELIMINARY INVESTIGATION<\/p>\n
System development, a process consisting of two major steps of system analysis and design, start when management or sometimes system development personnel feel that a new system or an improvement in the existing system is required. The system development life cycle is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. The system development life cycle consists of the following activities:<\/p>\n
\uf0d8 Preliminary investigation
\n\uf0d8 Determination of system requirements
\n\uf0d8 Design of system
\n\uf0d8 Development of software
\n\uf0d8 System testing
\n\uf0d8 Implementation, evaluation, and maintenance
\nA request to take assistance from information system can be made for many reasons, but in each case someone in the organisation initiates the request is made, the first system activity the preliminary investigation begins. This activity has three parts:
\n1) Request clarification
\n2) Feasibility study
\n3) Request approval<\/p>\n
Request clarification: Many requests from employees and users in the organizations are not clearly defined, Therefore it becomes necessary that project request must be examined and clarified properly before considering systems investigation.<\/p>\n
2.2 SYSTEM DEVELOPMENT LIFE CYCLE<\/p>\n
Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, The subject System Analysis and Design (SAD), mainly deals with the software development activities.<\/p>\n
DEFINING A SYSTEM<\/p>\n
A collection of components that work together to realize some objective forms a system. Basically there are three major components in every system, namely input, processing and output.<\/p>\n
In a system the different components are connected with each other and they are interdependent. For example, human body represents a complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demand that some output is produced as a result of processing the suitable inputs.<\/p>\n
SYSTEM LIFE CYCLE<\/p>\n
System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required for developing a system.<\/p>\n
System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.
\nFollowing are the different phases of software development cycle:<\/p>\n
\u2022 System study
\n\u2022 Feasibility study
\n\u2022 System analysis
\n\u2022 System design
\n\u2022 Coding
\n\u2022 Testing
\n\u2022 Implementation
\n\u2022 Maintenance<\/p>\n
The Different Phases Of Software Development Life Cycle Are Shown Below.<\/p>\n
A system analysis is a separation of a substance into parts for study and their implementation and detailed examination.<\/p>\n
Before designing any system it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination provides the specific data required during designing in order to ensure that all the client’s requirements are fulfilled. The investigation or the study conducted during the analysis phase is largely based on the feasibility study. Rather it would not be wrong to say that the analysis and feasibility phases overlap. High-level analysis begins during the feasibility study. Though analysis is represented as one phase of the system development life cycle (SDLC), this is not true. Analysis begins with system initialization and continues until its maintenance. Even after successful implementation of the system, analysis may play its role for periodic maintenance and up gradation of the system.
\nOne of the main causes of project failures is inadequate understanding, and one of the main causes of inadequate understanding of the requirements is the poor planning of system analysis.
\nAnalysis requires us to recall the objectives of the project and consider following three questions:<\/p>\n
\u2022 What type of information is required?<\/p>\n
\u2022 What are the constraints on the investigation?
\n\u2022 What are the potential problems that may make the task
\nmore difficult?<\/p>\n
Keeping the above questions in mind and considering the survey conducted to determine the need of the system, the total system was deigned and can be described as under:
\nThe three major parts of the system are:
\n\uf0d8 Providing Information:<\/p>\n
The system is effectively used to provide large variety of information to the interested customer. The major purpose of the site is to easily provide access to records of various automobile such as car with quick update to latest modifications in the records. This thing is not at all possible in printed material, which are updated only once a few weeks. It also gives information about the general usage of the system for first time visitors. The system itself works as a information provider for automobile organization.<\/p>\n
2.3 FEASIBILITY STUDY<\/p>\n
The feasibility study proposes one or more conceptual solution to the problem set of the project. In fact, it is an evaluation of whether it is worthwhile to proceed with project or not.<\/p>\n
Feasibility analysis usually considers a number of project alternatives, one that is chosen as the most satisfactory solution. These alternatives also need to be evaluated in a broad way without committing too many resources. Various steps involved in feasibility analysis are:<\/p>\n
1. To propose a set of solution that can realize the project goal. These solutions are usually descriptions of what the new system should look like.<\/p>\n
2. Evaluation of feasibility of such solutions. Such evaluation often indicates shortcomings in the initial goals. This step is repeated as the goals are adjusted and the alternative solutions are evaluated.<\/p>\n
Steps in feasibility Analysis are:<\/p>\n
1. Identify deficiency by pinpointing, missing functions, unsatisfactory performance,
\nExcessive cost of operations.<\/p>\n
2. Set goals to remove these deficiencies.<\/p>\n
3. Goals must be quantified, realizable within the constraints of an organization,broken
\ndown into sub goals agreeable to all concerned.<\/p>\n
4. Set goals not only to remove deficiencies but also to effectively meet competition.
\nFor instance, goals must be based on what competitors do.<\/p>\n
2.4 ECONOMIC FEASIBILITY
\nEconomic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost \/ benefit analysis; in this procedure we determine the benefits and savings that are expected from a proposed system and compare them with costs. We found the benefits outweigh the costs; we take a decision to design and implement the new proposed system.
\nDuring the feasibility phase, broad alternatives solutions are examined. For each alternate solution the cost and benefits have to be examined before designing one of the alternative.
\nBroad solutions will consist of:<\/p>\n
1. Specifications of information to be made available by the system.
\n2. Description of what will be done manually and what the computer will do.
\n3. Specification of new computing equipment needed or specification of
\nexpansion of an existing computer.<\/p>\n
COST AND BENEFIT ANALYSIS<\/p>\n
Developing an IT application is an investment. Since after developing that application it provides the organization with profits. Profits can be monetary or in the form of an improved working environment. However, it carries risks, because in some cases an estimate can be wrong. And the project might not actually turn out to be beneficial.<\/p>\n
Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It usually involves comparing alternate investments.
\nCost benefit determines the benefits and savings that are expected from the system and compares them with the expected costs.<\/p>\n
In performing cost and benefit analysis it is important to identify cost and benefits factors. Cost and benefits can be categorized into the following categories:<\/p>\n
1. Development Costs \u2013 Development costs is the costs that are incurred during the development of the system. It is one time investment.
\n2. Operating Costs \u2013 Operating Costs are the expenses required for the day to day running of the system. Examples of Operating Costs are Wages, Supplies and Overheads.
\n3. Hardware\/Software Costs \u2013 It includes the cost of purchasing or leasing of computers and it\u2019s peripherals. Software costs involves required S\/W costs.
\n4. Personnel Costs \u2013 It is the money spent on the people involved in the development of the system.
\n5. Facility Costs \u2013 Expenses that are incurred during the preparation of the physical site where the system will be operational. These can be wiring, flooring, acoustics, lightning, and air-conditioning.
\n6. Supply Costs \u2013 These are variable costs that are very proportionately with the amount of use of paper, ribbons, disks, and the like.<\/p>\n
\uf071 BENEFITS<\/p>\n
We can define benefits as<\/p>\n
Profit or Benefit = Income \u2013 Costs<\/p>\n
Benefits can be accrued by:<\/p>\n
\uf0d8 Increasing income, or
\n\uf0d8 Decreasing costs, or
\n\uf0d8 Both<\/p>\n
2.5 TECHNICAL FEASIBILITY
\nToday, very little is technically impossible. Consequently, technical feasibility looks at what is practical and reasonable. Technical feasibility addresses three major issues:
\n1. Is the proposed technology or solution practical?
\n2. Do we currently possess the necessary technology?
\n3. Do we possess the necessary technical expertise, and is the schedule reasonable?<\/p>\n
Is the Proposed Technology or Solution Practical?<\/p>\n
The technology for any defined solution is normally available. The question whether that technology is mature enough to be easily applied to our problems. Some firms like to use state-of-the-are technology, but most firms prefer to use mature and proven technology. A mature technology has a larger customer base for obtaining advice concerning problems and improvements.
\nDo We Currently Possess the Necessary Technology?
\nAssuming the solution’s required technology is practical, we must next ask ourselves, is the technology available in our information systems shop? If the technology is available, we must ask if we have the capacity. For instance, will our current printer be able to handle the new reports and forms required of a new system?
\nIf the answer to any of these questions is no, then we must ask ourselves, Can we get this technology? The technology may be practical and available, and, yes, we need it. But we simply may not be able to afford it at this time. Although this argument borders on economic feasibility, it is truly technical feasibility. If we can’t afford the technology, then the alternative that requires the technology is not practical and is technically infeasible!<\/p>\n
3.1 IMPORTANCE OF COMPUTERIZED<\/p>\n
There are several attributes in which the computer based information works. Broadly the working of computer system is divided into two main groups:<\/p>\n
\u2022 Transaction System
\n\u2022 Decision Support System<\/p>\n
Transaction System:<\/p>\n
A transaction is a record of some well-defined single and usually small occurrence in a system. Transactions are input into the computer to update the database files. It checks the entering data for its accuracy. This means that numeric data appears in numeric field and character data in character field. Once all the checks are made, transaction is used to update the database. Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are entered and updated into the database almost instantaneously. In batch mode, transactions are collected into batches, which may be held for a while and inputted later.<\/p>\n
Decision Support System:<\/p>\n
It assists the user to make analytical decision. It shows the various data in organized way called analysis. This analysis can be made to syrdy preferences and help in making decisions.<\/p>\n
Computer system works out best with record maintenance. It will tell you which customer would get how much pending\/reports statements. It will also help to search the information about a particular person by simply entering his telephone number. User can store information as per requirement, which can be used for comparison with other reports.<\/p>\n
DEFINETION, ACRONYMS & ABBREVIATIONS<\/p>\n
Log-In-Id: When user logs in to the \u201cCollege Management System\u201d then user is requested to fill in the login provided to him by he administrator. It acts as a security mechanism to prevent unauthorized access.<\/p>\n
Password: When a user will try to login in to the site to access record, the user will be requested to fill in the password. This check the validity of the user.<\/p>\n
USER CHARACTERISTICS:-<\/p>\n
\uf0a7 Software uses graphical interface and also at every step user is guided well to avoid confusion if any.
\n\uf0a7 User authentication is tested through login and password facility
\n\uf0a7 It is the responsibility of the user to enter the records genuinely and correctly and with utmost accuracy as far as possible to avoid discrepancies.<\/p>\n
ASSUMPTIONS & DEPENDENCIS:-<\/p>\n
\uf0a7 The software uses vb.Net therefore the terminal it is to be run trust support Visual.Net studio 2003.
\n\uf0a7 It is assumed that the user is intelligent enough that he\/she will not repeat information again & again.<\/p>\n
SPECIFIC REQURIMENTS:-<\/p>\n
New records are entered through the graphical user interface i.e the forms and at the click of a button they are entered into the database, so that they can be retrieved for future use or any enquiry.<\/p>\n
[
\nEXTERNAL INTERFACE REQUIREMENTS:-<\/p>\n
User Interface: \u201cCollege Management System\u201d provides complete graphical user interface which will make software more interactive & convenient to use.<\/p>\n
Hardware Interface: \u201cCollege Management System\u201d will interact with almost all types of hardware available at college management.<\/p>\n
Software Interface: Software uses JSP for forms designing and to provide good graphical user interface. My SQL is used at the backend to store data.<\/p>\n
NON FUNCTIONAL REQUIREMENT:<\/p>\n
Performance Requirement: Using JSP with My SQL enhances the performances of project as both are Microsoft products therefore front and backend have been chosen such that the performance increases.<\/p>\n
Software Quality Attributes: \u201cCollege Management System\u201d with stands following quality attributes: correctness in terms of number of computational errors, Robustness.<\/p>\n
3.2 FUNCTIONAL REQIREMENTS<\/p>\n
Functional Module 1: To login and password facility has been provided to authenticate the user.
\nInput: password provided by administrator.
\nProcess: designing the login form.<\/p>\n
Functional Module 2: User enters the data through forms the database.
\nPurpose: Data is required for later use by the college also to keep records of student\u2019s performance.
\nInput: student that come for courses or training in the college register themselves.
\nProcess: designing the forms and entering data into database.<\/p>\n
Functional Module3: To enter and maintain projects being made t college.
\nInput: Input for these forms is provided to user by the group leader and guide of the project.
\nProcess: Designing the project record entry form.<\/p>\n
Functional Module4: To enable user to edit data
\nPurpose: Data or information changes with time therefore records need to be updated.
\nInput: monthly assessment of each student
\nProcess: Updating database with new records<\/p>\n
Functional Module5: To delete records that is no more required
\nPurpose: Saving space and memory requirements and thus increasing accessibility and retrieval of data faster.
\nInput: Roll no of student or primary key of the table.
\nProcess: updating database.<\/p>\n
Functional Module6: Retrieval of data
\nPurpose: user needs for future planning or for studying a student\u2019s performance graph.
\nInput: primary key of tables from which we want to extract data.
\nProcess: generating reports.<\/p>\n
Functional Module7: Fee Details
\nPurpose: Student, Parents needs to get their updated student\u2019s Fee Details. Administrator add these details.
\nInput: primary key of tables from which we want to extract data.
\nProcess: generating reports.<\/p>\n
Functional Module8: Holiday Details
\nPurpose: Student, Parents, Teachers needs to get updated holidays approval list. Administrators add these details.
\nProcess: generating reports.<\/p>\n
Functional Module9: Uploading
\nPurpose: This module is for Students and Teachers. Teachers can upload notes and assignments that students can download, Students can upload there resumes that teachers can download.<\/p>\n
Functional Module110: Feedback
\nPurpose: Students, Teachers and Parents can give their feedbacks.<\/p>\n
DETAILED DECOMPOSITION<\/p>\n
Module Description<\/p>\n
MODULE 1: User Authentication Module<\/p>\n
This module verifies whether the user is valid or not. Basically, purpose of this module is to distinguish between two types of users one i.e. those who can view and manipulate records that is the administrative staff members & the other who have no right to view this information.<\/p>\n
Module 2: A New Records Being Entered<\/p>\n
Purpose of this module is to edit\/ update the records previously entered for example the monthly attendance record of the student needs to be updated, similarly fee record updating after the due fees has been deposited.<\/p>\n
MODULE 3: Deleting the Records<\/p>\n
Students who have completed their Industrial Training or course or students who have done their training submit their ID back to the college before leaving and correspondingly certificate is issued to them for their successful completion of course etc, these students records needs to be deleted as they are no more part of the organization.<\/p>\n
MODULE 4 Retrieving Records<\/p>\n
The user of the software is the administrative person of the organization therefore he\/she needs to access the records as when required like enquiring the fee status, attendance status of a student, or it may be generating a notice for notice board enlisting students who are short of attendance etc.
\nPROCESS DECOMPOSITION
\nThe main module of the project \u2019College Management System\u2019 are as follows:-
\n1. Login
\n2. Forms
\n3. Reports
\n4. Window
\nMain Description of the module \u2018Login\u2019 are:-
\nFor this the user should give the correct user name and password.
\nThe different types of users are
\n1. Admin
\n2. Student
\n3. Employee<\/p>\n
Main Description of the module \u2018Forms\u2019 are:-
\nThis module consists of the following sub modules
\n1. Student Registration Form
\n2. Student Fee Form
\n3. Student Marks Form
\n4. Student ID Form
\n5. Employee Detail Form
\n6. Employee Salary Form
\n7. Employee ID Form
\n8. Course Detail Form
\n9. Library Form<\/p>\n
The \u2018Student Registration Form\u2019 is designed for registering the new student details and course details.
\nThe \u2018Student Fee Form\u2019 is used to enter the student\u2019s fee details.
\nThe \u2018Student Marks Form\u2019 is designed for submitting the semester or exam marks of the students for a particular course or an individual student.
\nThe \u2018Student Id Form\u2019 is used to create the identity number for each student for different course.
\nThe \u2018Employee details Form\u2019 is designed for entering the staff details and other relevant details.
\nThe Employee Id used to create the identity number for each student for different course.
\nThe \u2018Salary Form\u2019 is used to derive the salary for employees
\nThe \u2018Course details Form\u2019 is designed for entering the different course available in the campus and other relevant details.
\nThe \u2018Library module\u2019 is used for the data process of library and book accessing for students and staffs.<\/p>\n
Main Description of the module \u2018Reports\u2019 are:-
\nAll the above mentioned data are stored in the back end and can be retrieved as reports with filtering options.
\nThe following are the reports can be taken from this system
\n1. Student Report
\n2. Employee Report
\n3. Course Detail Report
\n4. Book Detail Report
\n5. Issued Book Report
\n6. Fee Detail Report
\n7. Marks Detail Report
\n8. Generate Pay Slip<\/p>\n
3.3 DATA DESCRIPTION<\/p>\n
Data entity 1:<\/p>\n
First thing is the login and the password facility, it has been provided to authenticate the user that is other than administrative staff like students etc should not have access to the records as they may try to change the records like fee and attendance status.<\/p>\n
Data entity 2:<\/p>\n
Second important information is registration form, fee record form, attendance form and lastly the accessories form. These forms appear again for different category of students at college that allows i.e. one, who come for industrial training\/ project in their final semesters, secondly those who join college with purpose of doing the courses offered by it, in this case one student can opt for more than one course thus he has been categorized as new and existing.<\/p>\n
Data Entity 3:<\/p>\n
Third important entity is the data retrieval forms that take input as user parameters for the search and generate report for the same.<\/p>\n
DEPENDENCY DESCRIPTION<\/p>\n
Module Dependency:<\/p>\n
All the modules are interrelated as editing; deletion and retrieval can be performed only after successful execution of the data entry module, same way unless and until login and password form is executed user cannot enter the options page.<\/p>\n
Process Dependency:<\/p>\n
Interdependence of validation process, entering records process, edit, delete and retrieval process & all its sub processes. All the processes are dependent upon the validation process as in if a user does not surpasses this process the user will not be able to move onto other processes.<\/p>\n
Data Dependency:<\/p>\n
String of characters entered as password, allows user to move to other page, & options are displayed. Thus, validation module, basically deals with data i.e. password. Registration form entries act as input to databases that keep record of new & existing students. Information like name of student, data of birth etc entered by user is entered in database all this data is the part of edit, delete & retrieve module of Web Based College .<\/p>\n
Test Data:<\/p>\n
The user at the time of login, if enters wrong password then appropriate message will be flashed & user stays on the same form.<\/p>\n
E.g. Say password is \u201cCollege Management System\u201d & if user enters some other string then error will be displayed as invalid password. If wrong data is entered in text boxes during the filling of Registration form then as the user clicks \u201cOK\u201d button valid types will appear & invalid fields will be made to fill again.<\/p>\n
4. SYSTEM DESIGN<\/p>\n
The design document that we will develop during this phase is the blueprint of the software. It describes how the solution to the customer problem is to be built. Since solution to complex problems isn\u2019t usually found in the first try, iterations are most likely required. This is true for software design as well. For this reason, any design strategy, design method, or design language must be flexible and must easily accommodate changes due to iterations in the design. Any technique or design needs to support and guide the partitioning process in such a way that the resulting sub-problems are as independent as possible from each other and can be combined easily for the solution to the overall problem. Sub-problem independence and easy combination of their solutions reduces the complexity of the problem. This is the objective of the partitioning process. Partitioning or decomposition during design involves three types of decisions: –
\nDefine the boundaries along which to break;
\nDetermine into how money pieces to break; and<\/p>\n
Identify the proper level of detail when design should stop and implementation should start. Basic design principles that enable the software engineer to navigate the design process suggest a set of principles for software design, which have been adapted and extended in the following list:<\/p>\n
Free from the suffer from “tunnel vision.” A good designer should consider alternative approaches, judging each based on the requirements of the problem, the resources available to do the job. The design should be traceable to the analysis model. Because a single element of the design model often traces to multiple requirements, it is necessary to have a means for tracking how requirements have been satisfied by the design model. The design should not repeat the same thing. Systems are constructed using a set of design patterns, many of which have likely been encountered before. These patterns should always be chosen as an alternative to reinvention. Time is short and resources are limited! Design time should be invested in representing truly new ideas and integrating those patterns that already exist.
\nThe design should “minimize the intellectual distance” between the software and the problem as it exists in the real world. That is, the structure of the software design should (whenever possible) mimic the structure of the problem domain.<\/p>\n
The design should exhibit uniformity and integration. A design is uniform if it appears that one person developed the entire thing. Rules of style and format should be defined for a design team before design work begins. A design is integrated if care is taken in defining interfaces between design components.<\/p>\n
The design activity begins when the requirements document for the software to be developed is available. This may be the SRS for the complete system, as is the case if the waterfall model is being followed or the requirements for the next “iteration” if the iterative enhancement is being followed or the requirements for the prototype if the prototyping is being followed. While the requirements specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain. Design is essentially the bridge between requirements specification and the final solution for satisfying the requirements.<\/p>\n
The design of a system is essentially a blueprint or a plan for a solution for the system. We consider a system to be a set of components with clearly defined behavior that interacts with each other in a fixed defined manner to produce some behavior or services for its environment. A component of a system can be considered a system, with its own components. In a software system, a component is a software module.<\/p>\n
The design process for software systems, often, has two levels. At the first level, the focus is on deciding which modules are needed for the system, the specifications of these modules, and how the modules should be interconnected. This is what is called the system design or top-level design. In the second level, the internal design of the modules, or how the specifications of the module can be satisfied, is decided. This design level is often called detailed design or logic design. Detailed design essentially expands the system design to contain a more detailed description of the processing logic and data structures so that the design is sufficiently complete for coding. Because the detailed design is an extension of system design, the system design controls the major structural characteristics of the system. The system design has a major impact on the testability and modifiability of a system, and it impacts its efficiency. Much of the design effort for designing software is spent creating the system design.<\/p>\n
The input to the design phase is the specifications for the system to be designed. Hence, reasonable entry criteria can be that the specifications are stable and have been approved, hoping that the approval mechanism will ensure that the specifications are complete, consistent, unambiguous, etc. The output of the top-level design phase is the architectural design or the system design for the software system to be built. This can be produced with or without using a design methodology. A reasonable exit criteria for the phase could be that the design has been verified against the input specifications and has been evaluated and approved for quality.<\/p>\n
A design can be object-oriented or function-oriented. In function-oriented design, the design consists of module definitions, with each module supporting a functional abstraction. In object-oriented design, the modules in the design represent data abstraction (these abstractions are discussed in more detail later). In the function-oriented methods for design and describe one particular methodology the structured design methodology in some detail. In a function- oriented design approach, a system is viewed as a transformation function, transforming the inputs to the desired outputs. The purpose of the design phase is to specify the components for this transformation function, so that each component is also a transformation function. Hence, the basic output of the system design phase, when a function oriented design approach is being followed, is the definition of all the major data structures in the system, all the major modules of the system, and how the modules interact with each other.<\/p>\n
Once the designer is satisfied with the design he has produced, the design is to be precisely specified in the form of a document. To specify the design, specification languages are used. Producing the design specification is the ultimate objective of the design phase. The purpose of this design document is quite different from that of the design notation. Whereas a design represented using the design notation is largely to be used by the designer, a design specification has to be so precise and complete that it can be used as a basis of further development by other programmers. Generally, design specification uses textual structures, with design notation helping in understanding.<\/p>\n
The final deliverable from system analysis is a document containing an unambiguous statement of the client’s requirements from the new system and what the development project will have to deliver in order to be considered a success.<\/p>\n
The functional specification is the starting point for designing, which depends to a large extent on the accuracy and thoroughness with which the analysis has been carried out. Understanding of the business, appreciation of the client’s problems and documentation of requirements provide the foundation on which the designing is based. A key factor in this approach is the use of the structured techniques. Analysis ends with a description of what the new system must do to fulfill the requirements of the organization, while design specifies how this will be done by selecting one of the many ways of doing it.<\/p>\n
The structured techniques used during the analysis which provide this logical view are:<\/p>\n
\u2022 Data flow diagrams – representing the process, which manipulate the data as it passes through the system.<\/p>\n
\u2022 Entity model – showing the relationship within the data items held within the system.<\/p>\n
\u2022 A data dictionary – providing an overall consistent definition of the data used during the system development. This definition includes the content of the data stores, data flows and the process shown on the data flow diagrams, and the entities that make up the entity model.<\/p>\n
DESIGN OBJECTIVES AND CONSTRAINTS:<\/p>\n
Flexible \u2013
\nThe design would enable future requirements of the organization to be incorporated without much difficulty. Often the organizational needs and objectives change over time and hence such a design enables the system to reflect these changes.<\/p>\n
\u2022 Maintainable –
\nA good design is easy to maintain and this reduces the client’s maintenance cost, which usually represents a proportion of the lifetime of the system.<\/p>\n
\u2022 Portable –
\nA client for whom the software was developed may wish to change the hardware on which the system run. A good design is portable – in other words it is capable of being transferred from one machine environment to another with minimum amount of effort.<\/p>\n
\u2022 Easy to use –
\nWith increasing number of general users having exposure to computers and access to web sites, expectations of computer applications in term of their ease of use are also increasing. A good design will result in a system which is `user – friendly’ – easy to understand, not difficult to learn how to use and straightforward to operate.<\/p>\n
\u2022 Reliable –
\nThe system designed must be secure against human error, deliberate misuse or machine failure, and which the data will be stored without corruption.<\/p>\n
4.1 PHYSICAL DESIGN<\/p>\n
The design phase focuses on the detailed implementation of the system recommended in the feasibility. Emphasis is on translating performance specifications into design specifications. The design phase is a transition from user-oriented document to a programmer-oriented document.<\/p>\n
4.1.1 Design Methodology:-<\/p>\n
Design Methodology is a way to transform the “art” of system analysis and design into an “engineering – type” discipline. It explains the relationship amongst various modules and programs within the system. It standardizes the approach to analysis and design, simplifies design by segmentation, improves documentation and subsequent maintenance and enhancements.<\/p>\n
The following structured diagram can appropriately represent the relationship between various modules.<\/p>\n
4.1.2 Design Overview:-<\/p>\n
In analyzing the present system a great deal of information was collected during the investigation and feasibility phases through list of problems and requirements, interview reports, questionnaires, onsite observations, manuals and determining potential solutions. It is important to record this information in an unambiguous, concise manner which will be clear and accessible to others, and which can be used by other analysts and designers involved in developing the system. Structured techniques help us to record the information in this way, using diagrams and minimum amount of the text.<\/p>\n
Structured analysis is a set of techniques and graphical tools that allow the analyst to develop a new kind of system specification that are easily understandable to the user. The traditional approach of organizing data through flowcharts support future developments and simplify communication with the user but focus on the cost\/benefit and feasibility analysis, project management, hardware and software selection, and personal considerations. In contrast, structured analysis considers new goals and structured tools for analysis, which provide the basis for design and implementation.<\/p>\n
4.1.3 Process Modeling:-<\/p>\n
System design goes through two phases of development: logical and physical. Logical implementation represented by Data Flow Diagram shows the logical flow of a system and defines the boundaries of the system it describes the input (source), outputs (destinations), data bases (data stores), and procedures (data flows) – all in the format that meets the user’s requirements. The logical implementation of the whole project can be represented as under through Data Flow Diagrams (DFD).<\/p>\n
4.2 ER DIAGRAMS<\/p>\n
4.3 DATA FLOW DIAGRAM<\/p>\n
Data flow diagrams (DFD) are part of a structured model in the development of software. They are a graphical technique that depicts information flow and the transforms that are applied as data move from input to output. Basically, the function of DFDs is to show the user a graphical analysis of a software system. It is like a flowchart, except DFDs show the flow of data throughout the system.
\n\uf0d8 The rectangle represents an external entity. The external entity is a producer or consumer of information that resides outside the bounds of the system to be modeled.
\n\uf0d8 The circle (process) is a transformer of information that resides within the bounds of the system. The line with an arrow (data item) is a single item, or a collection of data items. The arrow head represents the directions of the data.
\nThe Parallel line (data store) represents a repository of data that is to be stored for use by one or more processes; maybe as simple as a buffer or a queue or as sophisticated as a relational database.<\/p>\n
DFD Context\/0 Level diagram<\/p>\n
DFD 1st Level diagram<\/p>\n
DFD 2nd Level diagram<\/p>\n
Verify Availability<\/p>\n
DFD 2nd Level diagram<\/p>\n
ENROLMENT OF STUDENT<\/p>\n
4.4 PROCESS LOGIC FOR EACH MODULE<\/p>\n
In the first module, validity of password is checked against a particular user.<\/p>\n
In the second module, whenever a new entity is entered it should be checked for the duplicate data.<\/p>\n
In the third and fourth module, just like the first module it should have the proper checks for every entity being modified or updated.<\/p>\n
In the fifth and sixth module, again the validation checks are made and the different reports are generated to ease the business processes and decision making.<\/p>\n
In the seventh to twelve modules are related to admin, payment, stock, order, invoice ,distributor etc.<\/p>\n
4.5 DATA MODELING<\/p>\n
Data Structure Requirements according to the modules:<\/p>\n
\uf0d8 Identify The Various Tables Required.<\/p>\n
\uf0d8 Fields for These Tables.<\/p>\n
\uf0d8 The Various Key Fields (for example Primary key and foreign key).<\/p>\n
\uf0d8 Identify The Various Constraints like Not Null, Unique etc.<\/p>\n
Describing Data Elements:
\nData modeling defines primary data objects, composition of each data object, and attributes of the object, relationships between each object and other objects and between objects and the processes.<\/p>\n
List of Tables:
\n1. Login
\n2. Students
\n3. Courses
\n4. Fee
\n5. Books
\n6. Issue
\n7. Circular
\n8. Employee
\n9. Pay Slip
\n10. Marks Obtained
\nTables<\/p>\n
Login Table<\/p>\n
Field Data Type Constraint Description
\nUsername Char(30) Primary Key Username
\nId Char(30) Not Null Student\/Emp or admin ID
\nEmail Char(50) Not Null Email
\nPassword Char(30) Not Null Password<\/p>\n
Student Table: To store students details<\/p>\n
Field Data Type Constraint Description
\nStudent_id Char(30) Primary Key Student Id
\nStudent Nmae Char(30) Not Null Student Nmae
\nAddress Char(50) Not Null Address
\nCity Char(80) Not Null City
\nState Char(50) Not Null State
\nPhone Number(10) Not Null Phone No
\nBooks_issue_id Number(1) Not Null Books Issued
\nStudy Center Char(30) Not Null Study Center
\nCourse Char(30) Not Null Course
\nCode Char(30) Not Null Course Code
\nEmail Char(30) Not Null Email<\/p>\n
Course Table: To store course Details
\nField Data Type Constraint Description
\nCourse_ID Char(30) Primary Key Course id
\nCourse Char(30) Not Null Course name<\/p>\n
Fee Table
\nField Data Type Constraint Description
\nStudent_id Char(30) Primary Key Student Id
\nStudent_name Char(30) Not Null Student Nmae
\nCourse_name Char(50) Not Null Address
\nSem Char(80) Not Null Semeister
\nAmount Amount(5) Not Null Amount
\nDate Number(10) Not Null Date<\/p>\n
Books Table: To store details of the books available in library.
\nField Data Type Constraint Description
\nBooks_id Char(30) Primary Key Books id
\nBooks_name Char(30) Not Null Books name
\nAuthor Char(50) Not Null Author Name
\nCategory Char(80) Not Null Category
\nTotal_copies Char(30) Not Null Total_copies
\nAvailability Char(30) Not Null Availibility<\/p>\n
Issue table: To store details of the books issued.
\nField Data Type Constraint Description
\nBooks_id Char(30) Primary Key Books id
\nStudent_id Char(30) Not Null Student ID
\nIssue_date Date Not Null Issue date
\nRet_date Date Not Null Return Date
\nFine Number(5) Not Null Fine amount<\/p>\n
Circular Table: To store circular details
\nField Data Type Constraint Description
\nCir_no Char(30) Primary Key Circular Number
\nDate_of_cir Char(30) Not Null Date of circular
\nComment Char(30) Not Null Comment<\/p>\n
Emp Table: To store employee details
\nField Data Type Constraint Description
\nEmp_id Char(30) Primary Key Employee id
\nName Char(30) Not Null Employee name
\nDesign Char(30) Not Null designation
\nDepartment Char(30) Not Null Department
\nDate_of_join Date Not Null Date of joining
\nEmail Char(30) Not Null Email
\nSpecialization Char(30) Not Null Specialization
\nSalary Number Not Null Salary
\nPhone Number Not Null Conatct No<\/p>\n
Pay Slip
\nField Data Type Constraint Description
\nEmp_id Char(30) Primary Key Employee id
\nName Char(30) Not Null Employee name
\nDesignation Char(30) Not Null designation
\nDepartment Char(30) Not Null Department
\nBasic Date Not Null Basic
\nPf Number(5) Not Null Number
\nDa Number(5) Not Null Number<\/p>\n
Marks<\/p>\n
Field Data Type Constraint Description
\nId Char(30) Not Null Student ID
\nMarks obt Char(30) Not Null Marks obtained
\nTotal_marks Char(30) Not Null Total Marks
\nStatus Char(30) Not Null Status
\nDescr Char(200) Not Null Description<\/p>\n
4.6 SCHEDULING<\/p>\n
Scheduling of a software project does not differ greatly from scheduling of any multi- task engineering effort. Therefore, generalized project scheduling tools and techniques can be applied with little modification to software projects.
\nProgram evaluation and review technique (PERT) and critical path method (CPM) are two project scheduling methods that can be applied to software development. Both techniques are driven by information already developed in earlier project planning activities.<\/p>\n
Estimates of Effort<\/p>\n
\uf0d8 A decomposition of the product function.
\n\uf0d8 The selection of the appropriate process model and task set.
\n\uf0d8 Decomposition of tasks.
\nInterdependencies among tasks may be defined using a task network. Tasks, sometimes called the project Work Breakdown Structure (WBS) are defined for the product as a whole or for individual functions.
\nBoth PERT and CPM provide quantitative tools that allow the software planner to (1) determine the critical path-the chain of tasks that determines the duration of the project; (2) establish “most likely” time estimates for individual tasks by applying statistical models; and (3) calculate “boundary times” that define a time window” for a particular task.
\nBoundary time calculations can be very useful in software project scheduling. Slippage in the design of one function, for example, can retard further development of other functions. It describes important boundary times that may be discerned from a PERT or CPM network: (I) the earliest time that a task can begin when preceding tasks are completed in the shortest possible time, (2) the latest time for task initiation before the minimum project completion time is delayed, (3) the earliest finish-the sum of the earliest start and the task duration, (4) the latest finish- the latest start time added to task duration, and (5) the total float-the amount of surplus time or leeway allowed in scheduling tasks so that the network critical path maintained on schedule. Boundary time calculations lead to a determination of critical path and provide the manager with a quantitative method for evaluating progress as tasks are completed.
\nBoth PERT and CPM have been implemented in a wide variety of automated tools that are available for the personal computer. Such tools are easy to use and take the scheduling methods described previously available to every software project manager.<\/p>\n
5.1 SOURCE CODE<\/p>\n
Home.jsp<\/p>\n
<%@ page language=”java” %>
\n<%@ page session=”true” %><\/p>\n
Welcome Page<\/p>\n
<\/p>\n