1.1 INTRODUCTION
Now we are in the age of automation. In this age, we feel the importance of automation in all steps of daily jobs. We are trying to develop an automation system which will provide lots of facilities to our University. The total automation system divided into many modules, here our parts is “Library Management System” .This is a small part of total automation System but The Library Management System will provide an environment which facilitate teachers & students easy to access the library information.
The Aim of this project is to help our student, Library administrator and Teacher to access our library in a computerized way. Or search Books via Internet. We found that if our Library Management system is automated or computerized then it it will be very easy to search any book. It saves our time and our total Library Management system become very easy.
1.2 OBJECTIVES:
It will help student or library administrator to access library easily
To reduce people’s haphazard.
Searching process of a book becomes very easy.
Maintenance of these books becomes very easy.
To assure the information of the library such as book types, copy number of books, authors name, availability of particular book etc.
To make secured data storage of library information.
Manage the library as a systematic way.
Huge information can be stored.
1.3 METHODOLOGY:
An important aspect of modeling is its role as a communication tool in determining requirements. For users what they require, and is the current system satisfying their requirements. As we go though the project, we find out three types of user in this project. They are student, teacher & library supervisor. We visit them in different time to collect their requirements. Though all of the requirements are not same but we tried out to make an interface among their requirements.
1.4 Project Life Cycle
The project life cycle includes various development phases that occur in the life of project starting right from the inception of the project to its final development at the client’s end. The three development phases in a project life cycle are:-
• Project initiation
• Project execution
• Project deployment
1.4.1 Project initiation:
The project initiation phase is fist phase of life cycle. This phase involves creating a complete plan for the project, specifying various activities that will be performed and assigning responsibilities to team members on the basis of their skill set.
1.4.2 Project execution:
After the project plan is made and the responsibilities assigned, the actual development of the project starts. The phase in which the actual development of the project takes place is known as the project execution phase. This is the most crucial phase of any project and is subdivided into the following phases:-
A. system analysis
• Initial study
• Information gathering
• Feasibility study
B. System design
• Design standard
• High level design & design tools
• Database design
• Logical design
• Construction
3. System implementation
• Integration & testing
• Post implementation
1.4.3 Project development:
After the project execution phase, the final phase of a project life cycle is the project development phase. In this phase, the deployed at the client side. This phase also involves providing customer support to the client for some specified period of time.
When project is built it may possibly remain error les of more, because several type of modification can take place several times. So for the very first time when we run the database web site we found few problems in tools potions. We fixed this problem including some minor problems immediately, and afterwards the application runs properly.
Chapter 2
Project Execution and Analysis
2.1 Introduction of System Analysis
System analysis is a detailed study of the various operation performed by a study and their relationships within the meeting members of the system. A key question is what must be done. One aspect on analysis is defining the boundaries of the system and determining whether or not a candidate system should consider other related system. During analysis, data are collected on available files, decision, points, and transactions handled by the present system.
System analysis is conducted with the following objectives in mind:
• Identify the end users.
• Evaluate the system concept for feasibility.
• Perform economic and technical analysis.
• Allocate functions to hardware, software, meeting members, database, and other system elements.
• Establish cost and schedule constraints.
• Create a system definition that forms the foundation for all subsequent engineering works.
2.1.1 Initial Investigation
The first phase of the software engineering development life cycle is initial investigation. In this stage, the analyst (system engineer) meets with organizer and the end user. The end user would be access of this system, the academic and other department of the analyst's in this system.
It depends on three tasks:
• Defining the problem and deciding whether to be proceed.
• Analyzing the current system of the problem.
• Selecting the best solution.
So, initial investigation identify that what will do top to bottom of the system.
2.1.2 Feasibility Study
Feasibility study is the preliminary investigation into the system to evaluate the possibility of a computer system and estimate costs and benefits where quality and time also involve. This is the most effective method of solution.
Feasibility and risk analysis are related in many ways. If project risk is great, the feasibility of producing quality software is reduced.
There are eight steps in feasibility study:
• Form a project team and appoint a project leader.
• Prepare system flow chart
• Enumerate potential candidate system
• Describe an identify characteristic of the candidate system
• Determine and evaluate performance and cost effectiveness of candidate system
• Weight system performance and cost data
• Select the best candidate system
• Prepare and report project directive to management
Three key considerations are involved in feasibility study:
2.1.3 Economic feasibility
Economic feasibility usually known as cost analysis; determines whether the adoptions of a system can be cost justified. Economic justification is generally the "bottom-line" consideration for most system [1]. Economic justification includes cost-benefit analysis, long-term corporate income strategies, impact on other profit centers or products, cost of resources needed for development, and potential system growth to survive the system into automation in a profitable manner.
2.1.4 Technical feasibility
Technical feasibility is the most difficult area to access for the automation system engineering process. Some considerations for technical feasibilities are:
• Development risk
• Resource availability.
• Technological risk
• Technical management
2.1.5 Behavioral/ Legal feasibility
Behavioral feasibility determines how much effort will go into educating, managing, training the user staff for the system. The organizer and the end user will be supported in this system.
2.2 Library Management System
A Library Management System is a system where a user can access a library automatically. Here automatically stands for computerized way. In a manual system when we go a library, we see a lot of books are in self by self. There is no member, no serial of these books. It is difficult to find out a certain book for a certain writer. To reduce these haphazard we decide to make this LMS system automated. In this system a user easily get which books are in the library. How many copies have of them, the name of the writer of the book etc?
2.3 Existing System:
The system we have currently is a poor manual library system. There is a lot of book in library but no serial number of them. Different writers have different books but no chart of them. Our library supervisor maintains only a register chart. Where there is no information about the book lender. So it is difficult to find out the book lender in next time. And it is risky too to give a book. Students are not able to lend a book from the library because library supervisor has no sufficient information about them that she/he can search out the lender.
Our existing library management system is a manual system. The whole system is manually defined and it has some problems. The problems of existing systems are as follows:
• It is very slow and takes many times.
• It is very difficult to maintain.
• It is not error free.
2.4 Propose System:
But now we want to do it automatically. Which will be so easier for Whole University and it has some advantages as follows:-
• Dynamic System
• Error free
• User Friendly
2.5 Strategy for Determining Requirement Information:
For the requirement analysis we use the key strategies for determination of requirements of the user.
• Getting information from the existing system.
• Interview.
• Questionnaires.
• Hardware & software requirements
2.5.1 Getting Information from the Existing System:
In this stage we simply ask the personnel of meeting management information section- what information are currently received and what other information are required. From this stage we find that the meeting members of the university are recording manually their personal information in the member register.
2.5.2 Interview:
Why do we conduct interviews during system analysis, the reasons are these:
We need to gather information about the behavior of a current system or the requirements of a new.
We need to verify our own understanding as system analyst of the behavior of a current system or the requirements of a new system. This understanding was probably acquired through previous interviews together with independently gathered information.
We need to gather information about the current system and/or system in order to carry out cost-benefit meeting between a system analyst and an end user.
We took the interview of the teacher, student, and Library Supervisor. As interview is the most common and most satisfactory way of obtaining information, particularly to obtain information about objectives constraints, allocation of details and problems and failures in the existing system.
After the interview all notes are read through and expanded to make them intangible. As the data are in random order, they were revised into a more useful order before the next work is commenced.
2.5.3 Questionnaires:
As the last phase of requirement analysis we distributed a form of fact finding that were used with great caution, because designing questionnaires is a specialization within the general subject of form design. It required considerable skill and field testing are required to avoid confuse and misinformation.
When we were designing the questionnaires, we bear the mind its purpose, its recipients and its timing. The questionnaires were carefully phrased so as not be ambiguous, not to lead the recipient to false answer and not to prevent relevant answer from been included.
Questionnaires for Library Supervisor:
What is the system of current library?
What are the aspects of them from the library?
What are the limitations of the library?
How library information are storing?
How lenders are find out?
What is the process for book searching?
How many books are in library?
What is the system of lending book?
How the information of a member are stored?
What is your expectation from Automated LMS?
Questionnaires for Members:
How you borrow a book from Library?
Do you think the current library system helpful for you?
How you search a book from in the library?
Do you prefer online based LMS?
What is your expectation from the Automated LMS?
2.5.4 Hardware & software requirements
Software Requirements:
Any Operating System.
Internet Explorer
Hardware Requirements:
Component Minimum Maximum
Process speed 233 MHz Higher ( P4)
Ram 64 MB Higher
Graphic Card AGP 32 MB Higher
Monitor Any Color Monitor Higher
CD Rom Any 16X Higher
Table 1: Hardware Requirement Table
2.6 Project Phase analysis:
2.6.1 Project phases
We divided our whole work of the project into the following developing phases.
2.6.2 Analysis the requirements of the project.
In this phase we basically analysis the requirements and develop our knowledge on demand. We will sort out all the necessary tools that will be needed. We will grow up the technological background to make workable the software in all environments.
2.6.3 The method of collecting requirements:
Reading books & related reference book.
Internet Browsing.
Talking with the students, our friends who are interested to help us by giving information about Library management System.
Talking with our supervisor & other teacher who are experienced to make Library and working with the automation.
Talking with Programmer or experienced people who are working this type of related sector.
2.6.4 Phase 2: Module Analysis
In this phase we will analyses our module and fragment the overall module in some small modules. Which help us to complete total system easily.
2.6.5 Phase3: Develop Modules
We will make the task flow and code flow of each module in this phase. We will write the row code to build up the modules.
2.6.6 Phase 4: Integrate Modules
In this phase we will integrate all modules. The backbone of the software will stand up in this phase and the software will be useable.
2.6.7 Phase5: Test, bug finding and bug fixing
We will test the overall features of the software. By testing the features we will find out the bugs. After that all the bugs will be solved.
2.6.8 Phase 6: Use of the software
This software will be use for Our University Automation System for Library management.
Chapter 3
Design of a system model
3.1 System Design Model:
In our Routine Management System there are three types of User models are shown
These are:
• Normal User
• Administrator
• registered user
3.1.1 Normal User:
A regular user is any kind of user like students, teachers or any body who uses the system and can see the online library and get information.
3.1.2 Administrator:
An admin user is a selected user who has the permissions to create a new admin or edit update delete operation. The admin users also perform the book function like book borrow, book lending book return etc.
3.1.3 Registered user
It means that, only our students, teacher, & employee are permitted to registration. These type of people have to has perform book borrow, return function.
3.2 Use case model
Overview of the use cases model of our proposed system” Library Management System”.
Fig: 3.1.a Use case diagram of proposed Routine Management System.
Fig: 3.1.b Use case diagram of proposed Routine Management System.
Fig: 3.1.c Use case diagram of proposed Routine Management System.
3.3 DATA FLOW DIAGRAM OF THE LIBRARY SYSTEM:
DFD show the flow of data from external entities into the system, showed how the data moved from one process to another, as well as its logical storage. DFD figure presents DFD of the project. There are only four symbols:
Squares representing external entities, which are sources or destinations of data.
Rounded rectangles representing processes, which take data as input, do something to it, and output it.
Arrows representing the data flows, which can either, be electronic data or physical items.
Open-ended rectangles representing data stores, including electronic stores such as databases and physical stores.
Figure:
Request for book
Request for Information
Requested Result
Request for Book
Requested Result
Fig 3.2: Data Flow Diagram of Library Management System
3.4 CRITICAL ANALYSIS
Figure:
Fig 3.3: Critical System
3.4.1 Dependability:
It should be include the following content:
Availability
Reliability
Safety
Security
Library System is a part of Automation System. So this library system depends the following category.
3.4.2 Availability:
Availability of our library system is the probability that it will be arriving and able
to deliver useful service at any given time.
3.4.3 Reliability:
In our module we will try to remove all most error so that our system dose not hangs frequently & it will give result perfectly. And it will be more reliable to access the library system.
3.4.4 Safety:
At the time of module develop we will ensure our system safety. On the other hand university authorities take action for system safety. So that any unauthorized people cannot touch the system.
3.4.5 Security:
System will want password to ensure legal access & block illegal or unauthorized access.
Chapter 4
work plan
4.1 Work plan:
We are trying our best to complete our task within three months and complete the total task as follows:
Table 2: Work Plan
4.2 Tools:
The software will be developed using PHP and HTML as Front End and MySQL as Back End. HTML, CSS, JavaScript and PHP are used for module design.
4.2.1 Apache
Apache HTTP Server is an open source HTTP web server for UNIX platforms
(BSD, Linux and UNIX systems), Microsoft Windows, and other platforms. The
Name was initially chosen as a catchy name in order to be original, but the most
Widespread interpretation (which almost immediately surfaced) is that the name
Comes from the fact that when it was developed in early 1995, it consisted of
Changes in the code to the most popular HTTP server of the time, NASA HTTP
1.3 And was therefore “a patchy” server.
4.2.2 MySQL
MySQL is a multithreaded, multi-user SQL database management system (DBMS)The MySQL database has become the world's most popular open source database because of its consistent fast performance, high reliability and ease of use
Not only is MySQL the world's most popular open source database, it's also become the database of choice for a new generation of applications built on the LAMP stack (Linux, Apache, MySQL, PHP / Perl / Python.) MySQL runs on more than 20 platforms including Linux, Windows, OS/X, HP-UX, AIX, Netware, giving you the kind of flexibility that puts you in control.
Its popularity as a web application is closely tied to the popularity of PHP, which is often combined with MySQL PHP. MySQL is used in a wide range of applications, including data warehousing, e-commerce, Web databases, logging applications and distributed applications.
4.2.3 PHP
PHP is a reflective programming language originally designed for producing dynamic web pages. PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications.
PHP generally runs on a web server, taking PHP code as its input and creating Web pages as output, however it can also be used for command-line scripting and client-side GUI applications. PHP can be deployed on most web servers and on almost every OS platform free of charge. The PHP Group also provides the complete source code for users to build, customize and extend for their own use.
4.2.5 HTML
HTML stands for Hypertext Markup Language.
• Hypertext is ordinary text that has been dressed up with extra features, such as formatting, images, multimedia, and links to other documents.
• Markup is the process of taking ordinary text and adding extra symbols. Each of the symbols used for markup in HTML is a command that tells a browser how to display the text.
HTML, short for Hypertext Markup Language, is the predominant markup language for the creation of web pages. It provides a means to describe the structure of text-based information in a document — by denoting certain text as headings, paragraphs, lists, and so on — and to supplement that text with interactive forms, embedded images, and other objects.
HTML is written in the form of labels (known as tags), surrounded by less-than (<) and greater-than signs (>). HTML can also describe, to some degree, the appearance and semantics of a document, and can include embedded scripting language code which can affect the behavior of web browsers and other HTML processors.
4.3 Conceptual model of our proposed Library Management system:
Fig 3.3: Conceptual Model
Chapter 5
Analyzing & Specification
5.1 Analyzing & Specification
We have found we have three library in three different buildings in an average each library has 5000 books. Different department has different library in a separate building
Library administrator maintains a khata to keep information about the book no student could lend any book or even couldn’t see what the books in the library are.
To reach our project goals our LMS system must has to provide following features:-
Student could see book list
Student could lend book from library
Administrator has to have the option add edit delete remove the booklist.
Administrator & student could see the borrowed the book list
The total system should be internet based.
5.2 DESIGNE PHASE
Home Page
Home Page is our main page of our Library Management System.
Our LMS system is developed by php & mysql . We take sevent database table to develop this LMS. Those tables are
i. Admin table
ii. Employee table
iii. Requirement table
iv. Booklist table
v. Defaulter table
vi. Book Borrow table
vii. Book information table
5.2.1 Admin table
Admin table has two fields one is admin id and other is password. Admin table only access by administrator.
Work for Administrator:
An administrator has four categories to work. Those are
• User
• Maintenance
• Books
• Searching
User
User Category has four options.
User Registration:
This option is for User (Student, teacher) registration. A User has to go the LMS administrator with his or her id card. Then Administrator will register him/her as a member of LMS. To help administrator we keep four fields for member registration. These are member id, Student id, Password and e-mail. Member id will provide by LMS administrator and other information will be taken form the user ID card.
Access with user
This option provide user accessing the library books , borrow , lend etc.
Add employee
Add employee provide employee management table. Here we have to need employee id, name email, phone. Also add, edit update, delete option are available.
Create new Admin
It will provide a new administration form. We have to need here admin id, employee id, previous password & email address.
After fulfill this item we will create a new administrator.
Maintenance
It has two parts such as
o New book entry
o Finding requirements
New book entry:
It provides book management table.
Finding requirements:
It will provide list of required book.
Books
It has three parts
o Book borrow function
o Returning book
o Renew book
Change Administrator:
This option will allow administrator to change his or her administrative password. It consist three field Admin id, Old password and new password. After entering Admin id and old password an admin could enter new password and able to change his/her password.
5.2.2 Employee Table
In LMS sometime we might have need to create new admin user. Create New User id allows us to do that. Creating a new admin user we have four fields. Those are admin id, Employee id password and email address.
5.2.3 Requirements table:
This table allows us to send request for any book. Suppose we need a book of PHP. But it is not in the library. Now if any students send any request REQUIREMENTS TABLE will save that request and later on Admin could act according to the request.
It has five fields. After filing these fields a user can send his requirements.
5.2.4 Booklist table
To search any book we will use this table. It has a drop down menu which consist five categories to search any book. It has also a field which will allow user to fid book by entering book name, author name, book id etc.
According to the user requirements the result will shown as a table with all of the book information.
5.2.5 Defaulter table:
This table is for defaulter list. An admin could search a defaulter by accessing this table. Every day this table will updated automatically.
The defaulter list will show as a table with book id, member id, and returns date of book and also department of a student.
5.2.6 Book borrow Table
Returning Books
Renew books
By this option a borrower could extend his/her book return date.
5.2.7 Book Information Table
Searching
It has three parts
o Searching by Book name
o Searching by Author
o Searching by Subject
Searching by Book name
We could search a book by its name.
Searching by Author
By Choosing Author in the Drop down menu and writing the writer’s name, we could search a book.
Searching by subject
This option allows us to search any book as subject wise. Suppose
We need to find out JAVA book. We will write JAVA in the search book id and select subject in the drop down menu.
Chapter 6
Bibliography
References:
[01] IAN SOMMERVILLE, Software Engineering: Software process, (2001)
[02] Ashish Wifred, Meeta Gupta and Bhatnagar, PHP Professional Projects: Handling Data Storage, Using PHP with SQL databases (MySQL), (2002)
[03] Roger S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw-Hill, (1992)
[04] Roger S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw-Hill,
(1992) [DAV 95]
[05] D.L Division and Graefe, Memory contention Responsive Hash Joins, proceedings of
the of the International conference on very large data bases, September 1994.
[06] Abrahim Silberschatz, Henry F.Korth, S. Sudarshan, Database System Concept,
Thw McGraw-Hill Companies, Inc.(1997).
[07] Bruce, Philip and Sam M. Pederson, The Software Development Project: Plan and
Management, Addison-Wesley Publishing Company,(1995).
[08] Roger S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw-Hill,
(1992)
[09] William E Lewis, Software Testing and Continuous Quality Implement,.CRS Press,
(2000)
[10] D.L Division and Graefe, Memory contention Responsive Hash Joins, proceedings of the of the International conference on very large data bases, September 1994.
Conclusion:
We are very much proud to be a part of University Automation. It was challenging task. We tried our best to accomplish it. But we think here is still some opportunity to improve. We hope that the thesis will continue in this topic. And we are always ready to help our next generation.
We would like to thanks our Project supervisor Miss Tareen Wali for her cordial help. We are regretful to all of our teacher and students for their help. We would also like to thanks them.
Thursday, January 8, 2009
Routine Management System
Chapter 1
1.1 Introduction:
Computer, the blessing of the modern world has been casing our day-to-day work in various ways. The new inventions of cutting-edge hardware making the computer system more powerful and computer software are utilizing this power to make things easier for modern world. With this flow of development and with the recent advent of the Internet and World Wide Web various institutions have promoted new technology to do their daily tasks. For this reasons our institution “University Of development Alternative (UODA)” want to make software, which is “University Automation for UODA”.
Now we are in the age of automation. In this age, we feel the importance of automation in all steps of daily jobs. We are trying to develop an automation system which will provide lots of facilities to our University. The total automation system divided into many modules , here our parts is “Routine Management Section” .This is a small part of total automation System but The Routine Management Section creates an environment which facilitate teachers, students and everybody by the management of time scheduling.
With the flow of development we are going to introduce an on line Routine Management System that can be helpful for our University. This online “Routine Management system” intended to be our final year project of University Of Development Alternative (UODA) under the integrated project name “University automation for UODA” in care of Mrs. Kazi Tareen Wali, lecturer, department of CSE, faculty of Engineering.
1.2 Project Life Cycle:
The project life cycle includes various development phases that occur in the life of project starting right from the inception of the project to its final development at the client’s end. The three development phases in a project life cycle are;
• Project initiation
• Project execution
• Project deployment
1.2.1 Project initiation:
The project initiation phase is fist phase of life cycle. This phase involves creating a complete plan for the project, specifying various activities that will be performed and assigning responsibilities to team members on the basis of their skill set.
1.2.2 Project execution:
After the project plan is made and the responsibilities assigned, the actual development of the project starts. The phase in which the actual development of the project takes place is known as the project execution phase. This is the most crucial phase of any project and is subdivided into the following phases;
1. system analysis
• Initial study
• Information gathering
• Feasibility study
2. System design
• Design standard
• High level design & design tools
• Database design
• Logical design
• Construction
3. System implementation
• integration & testing
• post implementation
1.2.3 Project development:
After the project execution phase, the final phase of a project life cycle is the project development phase. In this phase, the deployed at the client side. This phase also involves providing customer support to the client for some specified period of time.
When project is built it may possibly remain error les of more, because several type of modification can take place several times. So for the very first time when we run the database web site we found few problems in tools portions. We fixed this problem including some minor problems immediately, and afterwards the application runs properly.
1.3 Objective of the Module:
To make a proper time schedule for each of the department of our University, Which is very much helpful for our teachers, students and all of the facilities?
To make a fully dynamic Routine.
To make a dynamic routine which is faster then the manual routine system?
We tried to make a dynamic routine which is error free.
We tried to make a dynamic routine which is user friendly.
Understand ethical & professional issues, which are important for software engineering.
To learned methods of producing software in organized way.
Understand the concept of software process & software process module.
Understand in outline, process module for software modules for software requirements engineering, software development, testing & evolution.
Understand why project planning is essential in all software projects.
Student can understand how can a software is developing in industrial environment
1.4 Methodology:
Methodology is a collection of procedure, techniques, tools and documentation aids that help the system development in their effort to implement a new information system.
The proposed methodology is planned to meet the objective of online Routine Management System of UODA in an effective way.
Chapter 2
Project Execution and Analysis
2.1 System Analysis:
In this part we discuss all of the query and problem of the routine Management system and try to finding the solution.
2.1.1 What is Routine Management?
Routine management simply means the proper management of any type of work or resource used in an organization, that means which way the organization run, which protocol it maintain and why, what is its time schedule etc.
Each and every Organization must follow a routine because, to complete their total tasks in a sequential way .This process make all types of work so much easier because it maintain a schedule. It makes all types of work faster.
2.1.2 Existing System:
Our existing routine management system is a manual system. The whole system is manually defined and it has some problems. The problems of existing systems are as follows:
1. It is very slow and takes many times.
2. It is very difficult to make a routine.
3. It is not error free.
2.1.3 Propose System:
But now we want to do it automatically. Which will be so easier for Whole University and it has some advantages as follows:
1. Dynamic System
2. Error free
3. User Friendly
2.1.4 Reasons of the changes and major expected benefits:
In our university the courses are fixed, it is not easy to make a routine properly because this process is done manually so it is not well developed and it is very slow, and lost many time to make a routine. And in this manual system we must consider all the information about our students, teachers and classrooms etc but when we try to get the information instantly about any thing like classroom availability or teacher’s availability is not easy.
So present Routine Management system has many obligations and it cannot be easy and time consume. If we can establish automation for Routine management system we can able to remove most of the problem.
2.2 Fact Finding Technique:
In order to develop the process model of the new system at first the system analysis the requirement analysis of the proposed system had to be done. During system analysis and requirement analysis of our Routine Management System we have taken the following fact finding Techniques
1. Interviewing
2. Questionnaires
3. Observation
2.2.1 Interviews Structures:
Our goal is to implement to a new system and to overcome the drawbacks of the existing system. That’s way we have to go through an interview process which will give necessary information about the project requirements and help to solve a problems as well as fulfill in the user requirements
For this purpose we have to select the project to be interviewed as an interviewer we must give priority to the users those who are involved with our Routine Management System. In this regard, we discussed with them about our proposed Routine Management System and wanted to know about the problems of existing Routine Management System. We will also try to collect their opinions about the development of our system, which will help us including new system or add new features.
2.2.2 Questionnaires:
Questionnaires provide an alternative to interviews for finding out information about a system. We would like to add following questions for gathering requirements:
What is your present system?
1. What kind of system you use at present?
Manual Automatic
2. Are you satisfied with your present system?
Yes No
3. Do you have any Paper or Document related to your present System with respect to your University?
Yes No
4. If there is no system then what kind of system you want?
Manual Automatic
5. If the system is Automatic then which one is used?
Static Dynamic
6. If the system is static then what kind of problem you face?
7. If the existing system is dynamic then how it works?
Direct upload to the web page First type the document or information, and then upload to the web page
8. If you want static, then why?
9. If the page upload automatically then what will be the file extension?
.pdf .doc .ppt .pdf & .ppt .doc & .ppt
10. Who will update the page?
Authority Teacher Student Both
11. Upcoming Routine Management System and short description will be mentioned or not?
Yes No
12. Published Routine Management System can be updated after publishing or not?
Yes No
13. Will there any option to search the Routine Management System or not?
Yes No
14. How would you like to see the Routine Management System?
World Wide Web (www) Internal network
2.2.3 Observation:
AS the student of UODA we were already familiar with some existing procedure. Yet we communicated with the administrative level personnel to know all the specific activities as stated.
• How the information are stored
• How the teacher information are stored
• How the subject information are stored
• How they store multiple tasks information’s
• What type of permission exist among the relations
2.3 Project Phase analysis:
Project phases
We divided our whole work of the project into the following developing phases.
2.3.1 Phase 1: Analysis the requirements of the project.
In this phase we basically analysis the requirements and develop our knowledge on demand. We will sort out all the necessary tools that will be needed. We will grow up the technological background to make workable the software in all environment and network facilities.
2.3.1.1 Requirement Analysis:
We should need to analyze for the routine management the following things—
• A teacher can take only one class at a time.
• We must need to know the number of student for the individual Batch or Semester
• We need to consider how many class rooms are there and we must need to know the capacity of the room.
• We should need to arrange some common class which are similar for both (CSE & ETE)
• We should need to conscious about individual subjects credits which is not equal for the different subjects. (Such as 3 credit course, 2 credit course, 1 credit course).
• The time duration of the different class will be different for their varying different credit hours
2.3.1.2 The method of collecting requirements:
Reading books & related reference book.
Internet Browsing.
Talking with the students, our friends who are interested to help us by giving information about routine.
Talking with our supervisor & other teacher who are experienced to make routine and working with the automation.
Talking with Programmer or experienced people who are working this type of related sector.
2.3.2 Phase 2: Module Analysis
In this phase we will analyses our module and fragment the overall module in some small modules. Which help us to complete total system easily.
2.3.3 Phase3: Develop Modules
We will make the task flow and code flow of each module in this phase. We will write the row code to build up the modules.
2.3.4 Phase 4: Integrate Modules
In this phase we will integrate all modules. The backbone of the software will stand up in this phase and the software will be useable.
2.3.5 Phase5: Test, bug finding and bug fixing
We will test the overall features of the software. By testing the features we will find out the bugs. After that all the bugs will be solved.
2.3.6Phase 6: Use of the software
This software will be use for Our University Automation System for routine management
Chapter: 3
3.1 System Design Model:
In our Routine Management System there are two types of User models are shown
These are:
1. Normal User
2. Administrator
3.1.1 Normal User:
A regular user is any kind of user like students, teachers or any body who uses the system and can see the routine and get some information about the routine or time schedule.
3.1.2 Administrator:
An admin user is a selected user who has the permissions to create a new routine or edit the routine. The admin user also viewing the routine and get some information.
3.2 Use case model
Overview of the use cases model of our proposed system” Routine Management System”.
Fig: 3.1 Use case diagram of proposed Routine Management System.
Chapter 4
Database Design
4.1 Normalization:
Data structure is refined through a process called normalization. Data are grouped in the simplest way possible so that later changes can be made with a minimum of impact on the data structure. When too many attributes are grouped together to from entities, some attributes are found to be entities themselves. Further Normalization of these entities into attributes linked by common data elements to from relationship improves the effectiveness of the DBMS.
We have decided to use MySql data base. Our database name is “result”. It consists of the following tables:
1. Routine
2. Department
3. Teacher
4. Subject
5. Login table
6. Room
4.2 Contents of the table:
4.2.1 Routine table:
It contains the several fields in routine table. These are:
• Department
• Semester
• Course code
• Teacher id
• Starting time of the class
• Ending time of the class
**In this table the above all fields are included for the routine format
Field Type Attributes Null Default
dept varchar(30) No
sem varchar(15) No
ccode varchar(15) No
teac_id int(11) No 0
teac_name varchar(40) No
st time No 00:00:00
et time No 00:00:00
room_no varchar(30) No
day varchar(20) No
Fig: 4.1 Fields of Routine Table
4.2.2 Department table:
In this table it contains only the department name.
Field Type Null Default
dept_name varchar(40) Yes NULL
Fig: 4.2 Field of Department Table
4.2.3 Subject table:
Subject table contains the following things. These are:
• Department
• Semester
• Subject name
• Credit
• Course code
**The subject table arrange with the above things
Field Type Null Default
dept_name varchar(40) Yes NULL
sem varchar(10) Yes NULL
sub_name varchar(40) Yes NULL
credit int(11) Yes NULL
ccode varchar(15) Yes NULL
Fig: 4.3 Fields of Subject Table
4.2.4 Teacher table:
Teacher table contains the following things. These are:
Teacher name
Teacher id
Department name
**The function of the teacher table is arranging the schedule of the teacher with their teacher id
Field Type Null Default
teac_name varchar(40) Yes NULL
id int(11) Yes NULL
dept_name varchar(40) Yes NULL
Fig: 4.4 Fields of teacher Table
4.2.5 Room table:
Room table contain the following parts: these are
Student Numbers
Room number
Field Type Attributes Null Default
std_no int(11) Yes NULL
room_no varchar(30) Yes NULL
Fig: 4.5 Fields of room Table
4.2.6 Log in table:
The login table contains
• User id
• Password
Field Type Null Default
id Varchar(30) No
pass Varchar(70) No
Fig: 4.6 Field of log in Table
Chapter 5
5.0 Work plan:
**We are trying our best to complete our task within three months and complete the total task as follows:
Task ID Task Name Resources
01 Analysis the requirements of the project. Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
02 Module Analysis Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
03
Develop Modules Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
04 Integrate Modules
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
05 Testing, bug finding and bug fixing
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
06 Release the software and Reserve Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
Fig: 5.1 Complete task Table
5.1 Tools for design, analysis and Programming:
5.1.1 Design Tools Used:
HTML, HTML Editor, Browser (Internet Explorer, Netscape Navigator, Mozilla etc).
• Client Side and Server Side Scripting :
o PHP
o Javascript
o HTML
• Database Used as Back End:
o MySQL
• Web Server Used:
o Apache
5.1.2 About the Design Tools
5.1.2.1 What is PHP?
• PHP stands for PHP: Hypertext Preprocessor
• PHP is a server-side scripting language, like ASP
• PHP scripts are executed on the server
• PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.)
• PHP is an open source software (OSS)
• PHP is free to download and use
5.1.2.2 What is a PHP File?
• PHP files may contain text, HTML tags and scripts
• PHP files are returned to the browser as plain HTML
• PHP files have a file extension of ".php", ".php3", or ".phtml"
5.1.2.3 What is MySQL?
• MySQL is a small database server
• MySQL is ideal for small and medium applications
• MySQL supports standard SQL
• MySQL compiles on a number of platforms
• MySQL is free to download and use
5.1.2.4 PHP + MySQL
• PHP combined with MySQL are cross-platform (means that you can develop in Windows and serve on a Unix platform)
5.1.2.5 Why PHP?
• PHP runs on different platforms (Windows, Linux, UNIX, etc.)
• PHP is compatible with almost all servers used today (Apache, IIS, etc.)
• PHP is FREE to download from the official PHP resource: http://www.php.net/
• PHP is easy to learn and runs efficiently on the server side
5.1.2.6 What is Apache?
Apache is an HTTP server, originally designed for UNIX systems. This is the version of Apache for Microsoft Windows 2000, NT, 98, and 95 systems. Like the UNIX version, it includes many frequently requested new features, and has an API that allows it to be extended to meet users' needs more easily. It also allows limited support for ISAPI extensions.
Apache performs best, and is still most reliable on Unix platforms. Over time the performance, reliability and security for the Apache Win32 port has improved, and continues to improve. Folks doing comparative reviews of web server performance are still asked to compare against Apache running on a Unix platform such as Solaris, FreeBSD, or Linux.
5.1.2.7 What Is HTML?
The explosive growth of the World Wide Web is relatively unprecedented, although it resembles the desktop publishing revolution of the early and mid-1980s. As personal computers became more common in homes and offices, people began to learn to use them for document creation and page layout. Although early word processing programs were not terribly intuitive and often required memorizing bizarre codes, people still picked them up fairly easily and managed to create their own in-house publications.
Suddenly, the same kind of growth is being seen as folks rush to create and publish pages of a different sort. To do this, they need to learn to use something called the Hypertext Mark-up Language (HTML).
The HTML standard is maintained and debated by a group called the HTML Working Group, which, in turn, is a creation of the Internet Engineering Task Force. The Working Group was charged in 1994 with the task of defining the HTML standard that was in widespread use on the Web at the time (known as HTML 2.0), and then submitting proposals for future standards, including the HTML 3.0 standard.
5.2 Conceptual model of our proposed Routine Management system:
Fig: 5.2 Conceptual model of Routine Management System .
5.3 Consideration For essential factors:
With the respect of dependability the critical analysis is consists of the following parts:
1. Availability
2. Reliability
3. Time Scheduling
4. Teacher Schedule
5. Rooms facilities
6. Safety & Security
The critical analysis of Routine Management System is described below:
5.3.1 Availability: Though our system is fully an online system and automatic. That why any student and any person can see the system any time from any where by using internet.
5.3.2 Reliability: We will gather all the information’s by separating into different categories. All the advices will be discussed by the experts. So, users can get full reliability.
5.3.3 Teacher Schedule: We should need to maintain the all teacher schedule of his/her class in the proper way
5.3.4 Time Scheduling: When we start to make the Routine this time we should be sincere about the Teacher time schedule and the duration of the class.
5.3.5 Room’s facilities: We need the clear idea about every room accommodation and its capacities for distribute the proper class in the proper room.
5.3.6 Safety & Security: We will use the languages My SQL, HTML and PHP. The security level of our project-Routine Management System is very high. Because in this project the normal user only can see the routine of different semester and gather some information about our teachers that means anybody can see the teacher’s personal routine from module but they can’t change or update anything. But the administrator can do any thing. Administrator is the only person who can add department, add semester, add teachers, add subject and add rooms. He can also delete everything. Only he can create the new routine and drop update the routine.
Chapter 6
6.0 Software layout:
In this portion we describe the using process of the software.
6.1 How to Use
There are several options for using this web system
RMS Home page:
Inputs and Outputs
The Input and Output of the various pages on this web based project are given bellow:
1. LogIn
2. Category Search
3. Insert information
4. Update Information
5. Log out
6.2 LogIn
Input page:
6.2.1 Output page (if login success):
6.2 Steps: How to Use
6.2.1 Step 1:
After Signing in the administrator option the admin can do all type of access for editing or updating the routine.
6.2.1.1 Add Department:
Web Page for adding new Department
This page will be display when we want to add new Department in the database.
6.2.1.2 Add Subject:
Web Page for adding new subject:
This page will be display when we want to add new subject in the database.
6.2.1.3 Add new Teacher:
Web Page for adding Teacher:
This page will be display when we want to add new Teacher in the database.
6.2.1.4 Add new Room:
Web Page for adding new Room:
This page will be display when we want to add new Room in the database.
5.2.2 Step 2:
5.2.2.1 Make new Routine:
After completing the input Data an administrator easily can make a routine what he/she wants.
In this part the administrative user select those data which essential for particular department and particular semester which already inserted in data base.
And then submit the data. After submitting a routine will be shown below:
Show Routine:
5.2.3 Step 3:
In step 3 if the administrator thinks in the database there are some unnecessary information he/she can delete the information from the database by using the following steps:
5.2.3.1 Delete Subject:
Web Page for Delete Subject:
This page will be display when we want to delete subject from the database.
5.2.3.2 Delete Teacher:
Web Page for Delete teacher:
This page will be display when we want to delete teacher from the database
5.2.3.3 Delete Room:
Web Page for Delete Room:
This page will be display when we want to delete Room from the database
5.2.4 Step 4:
In this part if the administrators think there is some problem in any routine he/she easily can drop the routine for particular day or whole routine at a time.
5.2.4.1 Drop Routine:
Web page for drop routine:
After selecting the information what we want to drop from the routine then it will be show this page:
In this page there are two options for dropping routine one for dropping particular subject routine for particular day and another for dropping full routine
Chapter 6:
Chapter 7:
7.1 Limitation:
**We think There Are few limitation in our software
These are follows:
• We can’t divide the large semester
• We can’t make exam routine
• In our software we use Teachers id which will be difficult to remember
7.2 Post implementation
After implementing and testing the database web site we found that it almost fulfilled all of the requirements of our abstract and system designing considerations. The application is working smoothly for all its users, such as see the routine of any department for particular semester. Adding teacher information. In further we will try to solve our limitation and we are hopeful next time it will be a complete dynamitic Routine generating Software.
7.3 Discussion
To write discussion phase we should make on thing clear at the very beginning-although the l structure of a routine system is very complex, we took a professional approach, and designed the project in the best possible way so that it could be used instantly by any interested organization.
7.4 Conclusion
Website development is a continuous process. In near future there is a plan that this site will be a complete dynamic routine generating system. Ultimate destination for the user to get information about routine very easily.
At the end of this project we hardly request to the faculties of Computer Science and Engineering (CSE) to approve our project.
1.1 Introduction:
Computer, the blessing of the modern world has been casing our day-to-day work in various ways. The new inventions of cutting-edge hardware making the computer system more powerful and computer software are utilizing this power to make things easier for modern world. With this flow of development and with the recent advent of the Internet and World Wide Web various institutions have promoted new technology to do their daily tasks. For this reasons our institution “University Of development Alternative (UODA)” want to make software, which is “University Automation for UODA”.
Now we are in the age of automation. In this age, we feel the importance of automation in all steps of daily jobs. We are trying to develop an automation system which will provide lots of facilities to our University. The total automation system divided into many modules , here our parts is “Routine Management Section” .This is a small part of total automation System but The Routine Management Section creates an environment which facilitate teachers, students and everybody by the management of time scheduling.
With the flow of development we are going to introduce an on line Routine Management System that can be helpful for our University. This online “Routine Management system” intended to be our final year project of University Of Development Alternative (UODA) under the integrated project name “University automation for UODA” in care of Mrs. Kazi Tareen Wali, lecturer, department of CSE, faculty of Engineering.
1.2 Project Life Cycle:
The project life cycle includes various development phases that occur in the life of project starting right from the inception of the project to its final development at the client’s end. The three development phases in a project life cycle are;
• Project initiation
• Project execution
• Project deployment
1.2.1 Project initiation:
The project initiation phase is fist phase of life cycle. This phase involves creating a complete plan for the project, specifying various activities that will be performed and assigning responsibilities to team members on the basis of their skill set.
1.2.2 Project execution:
After the project plan is made and the responsibilities assigned, the actual development of the project starts. The phase in which the actual development of the project takes place is known as the project execution phase. This is the most crucial phase of any project and is subdivided into the following phases;
1. system analysis
• Initial study
• Information gathering
• Feasibility study
2. System design
• Design standard
• High level design & design tools
• Database design
• Logical design
• Construction
3. System implementation
• integration & testing
• post implementation
1.2.3 Project development:
After the project execution phase, the final phase of a project life cycle is the project development phase. In this phase, the deployed at the client side. This phase also involves providing customer support to the client for some specified period of time.
When project is built it may possibly remain error les of more, because several type of modification can take place several times. So for the very first time when we run the database web site we found few problems in tools portions. We fixed this problem including some minor problems immediately, and afterwards the application runs properly.
1.3 Objective of the Module:
To make a proper time schedule for each of the department of our University, Which is very much helpful for our teachers, students and all of the facilities?
To make a fully dynamic Routine.
To make a dynamic routine which is faster then the manual routine system?
We tried to make a dynamic routine which is error free.
We tried to make a dynamic routine which is user friendly.
Understand ethical & professional issues, which are important for software engineering.
To learned methods of producing software in organized way.
Understand the concept of software process & software process module.
Understand in outline, process module for software modules for software requirements engineering, software development, testing & evolution.
Understand why project planning is essential in all software projects.
Student can understand how can a software is developing in industrial environment
1.4 Methodology:
Methodology is a collection of procedure, techniques, tools and documentation aids that help the system development in their effort to implement a new information system.
The proposed methodology is planned to meet the objective of online Routine Management System of UODA in an effective way.
Chapter 2
Project Execution and Analysis
2.1 System Analysis:
In this part we discuss all of the query and problem of the routine Management system and try to finding the solution.
2.1.1 What is Routine Management?
Routine management simply means the proper management of any type of work or resource used in an organization, that means which way the organization run, which protocol it maintain and why, what is its time schedule etc.
Each and every Organization must follow a routine because, to complete their total tasks in a sequential way .This process make all types of work so much easier because it maintain a schedule. It makes all types of work faster.
2.1.2 Existing System:
Our existing routine management system is a manual system. The whole system is manually defined and it has some problems. The problems of existing systems are as follows:
1. It is very slow and takes many times.
2. It is very difficult to make a routine.
3. It is not error free.
2.1.3 Propose System:
But now we want to do it automatically. Which will be so easier for Whole University and it has some advantages as follows:
1. Dynamic System
2. Error free
3. User Friendly
2.1.4 Reasons of the changes and major expected benefits:
In our university the courses are fixed, it is not easy to make a routine properly because this process is done manually so it is not well developed and it is very slow, and lost many time to make a routine. And in this manual system we must consider all the information about our students, teachers and classrooms etc but when we try to get the information instantly about any thing like classroom availability or teacher’s availability is not easy.
So present Routine Management system has many obligations and it cannot be easy and time consume. If we can establish automation for Routine management system we can able to remove most of the problem.
2.2 Fact Finding Technique:
In order to develop the process model of the new system at first the system analysis the requirement analysis of the proposed system had to be done. During system analysis and requirement analysis of our Routine Management System we have taken the following fact finding Techniques
1. Interviewing
2. Questionnaires
3. Observation
2.2.1 Interviews Structures:
Our goal is to implement to a new system and to overcome the drawbacks of the existing system. That’s way we have to go through an interview process which will give necessary information about the project requirements and help to solve a problems as well as fulfill in the user requirements
For this purpose we have to select the project to be interviewed as an interviewer we must give priority to the users those who are involved with our Routine Management System. In this regard, we discussed with them about our proposed Routine Management System and wanted to know about the problems of existing Routine Management System. We will also try to collect their opinions about the development of our system, which will help us including new system or add new features.
2.2.2 Questionnaires:
Questionnaires provide an alternative to interviews for finding out information about a system. We would like to add following questions for gathering requirements:
What is your present system?
1. What kind of system you use at present?
Manual Automatic
2. Are you satisfied with your present system?
Yes No
3. Do you have any Paper or Document related to your present System with respect to your University?
Yes No
4. If there is no system then what kind of system you want?
Manual Automatic
5. If the system is Automatic then which one is used?
Static Dynamic
6. If the system is static then what kind of problem you face?
7. If the existing system is dynamic then how it works?
Direct upload to the web page First type the document or information, and then upload to the web page
8. If you want static, then why?
9. If the page upload automatically then what will be the file extension?
.pdf .doc .ppt .pdf & .ppt .doc & .ppt
10. Who will update the page?
Authority Teacher Student Both
11. Upcoming Routine Management System and short description will be mentioned or not?
Yes No
12. Published Routine Management System can be updated after publishing or not?
Yes No
13. Will there any option to search the Routine Management System or not?
Yes No
14. How would you like to see the Routine Management System?
World Wide Web (www) Internal network
2.2.3 Observation:
AS the student of UODA we were already familiar with some existing procedure. Yet we communicated with the administrative level personnel to know all the specific activities as stated.
• How the information are stored
• How the teacher information are stored
• How the subject information are stored
• How they store multiple tasks information’s
• What type of permission exist among the relations
2.3 Project Phase analysis:
Project phases
We divided our whole work of the project into the following developing phases.
2.3.1 Phase 1: Analysis the requirements of the project.
In this phase we basically analysis the requirements and develop our knowledge on demand. We will sort out all the necessary tools that will be needed. We will grow up the technological background to make workable the software in all environment and network facilities.
2.3.1.1 Requirement Analysis:
We should need to analyze for the routine management the following things—
• A teacher can take only one class at a time.
• We must need to know the number of student for the individual Batch or Semester
• We need to consider how many class rooms are there and we must need to know the capacity of the room.
• We should need to arrange some common class which are similar for both (CSE & ETE)
• We should need to conscious about individual subjects credits which is not equal for the different subjects. (Such as 3 credit course, 2 credit course, 1 credit course).
• The time duration of the different class will be different for their varying different credit hours
2.3.1.2 The method of collecting requirements:
Reading books & related reference book.
Internet Browsing.
Talking with the students, our friends who are interested to help us by giving information about routine.
Talking with our supervisor & other teacher who are experienced to make routine and working with the automation.
Talking with Programmer or experienced people who are working this type of related sector.
2.3.2 Phase 2: Module Analysis
In this phase we will analyses our module and fragment the overall module in some small modules. Which help us to complete total system easily.
2.3.3 Phase3: Develop Modules
We will make the task flow and code flow of each module in this phase. We will write the row code to build up the modules.
2.3.4 Phase 4: Integrate Modules
In this phase we will integrate all modules. The backbone of the software will stand up in this phase and the software will be useable.
2.3.5 Phase5: Test, bug finding and bug fixing
We will test the overall features of the software. By testing the features we will find out the bugs. After that all the bugs will be solved.
2.3.6Phase 6: Use of the software
This software will be use for Our University Automation System for routine management
Chapter: 3
3.1 System Design Model:
In our Routine Management System there are two types of User models are shown
These are:
1. Normal User
2. Administrator
3.1.1 Normal User:
A regular user is any kind of user like students, teachers or any body who uses the system and can see the routine and get some information about the routine or time schedule.
3.1.2 Administrator:
An admin user is a selected user who has the permissions to create a new routine or edit the routine. The admin user also viewing the routine and get some information.
3.2 Use case model
Overview of the use cases model of our proposed system” Routine Management System”.
Fig: 3.1 Use case diagram of proposed Routine Management System.
Chapter 4
Database Design
4.1 Normalization:
Data structure is refined through a process called normalization. Data are grouped in the simplest way possible so that later changes can be made with a minimum of impact on the data structure. When too many attributes are grouped together to from entities, some attributes are found to be entities themselves. Further Normalization of these entities into attributes linked by common data elements to from relationship improves the effectiveness of the DBMS.
We have decided to use MySql data base. Our database name is “result”. It consists of the following tables:
1. Routine
2. Department
3. Teacher
4. Subject
5. Login table
6. Room
4.2 Contents of the table:
4.2.1 Routine table:
It contains the several fields in routine table. These are:
• Department
• Semester
• Course code
• Teacher id
• Starting time of the class
• Ending time of the class
**In this table the above all fields are included for the routine format
Field Type Attributes Null Default
dept varchar(30) No
sem varchar(15) No
ccode varchar(15) No
teac_id int(11) No 0
teac_name varchar(40) No
st time No 00:00:00
et time No 00:00:00
room_no varchar(30) No
day varchar(20) No
Fig: 4.1 Fields of Routine Table
4.2.2 Department table:
In this table it contains only the department name.
Field Type Null Default
dept_name varchar(40) Yes NULL
Fig: 4.2 Field of Department Table
4.2.3 Subject table:
Subject table contains the following things. These are:
• Department
• Semester
• Subject name
• Credit
• Course code
**The subject table arrange with the above things
Field Type Null Default
dept_name varchar(40) Yes NULL
sem varchar(10) Yes NULL
sub_name varchar(40) Yes NULL
credit int(11) Yes NULL
ccode varchar(15) Yes NULL
Fig: 4.3 Fields of Subject Table
4.2.4 Teacher table:
Teacher table contains the following things. These are:
Teacher name
Teacher id
Department name
**The function of the teacher table is arranging the schedule of the teacher with their teacher id
Field Type Null Default
teac_name varchar(40) Yes NULL
id int(11) Yes NULL
dept_name varchar(40) Yes NULL
Fig: 4.4 Fields of teacher Table
4.2.5 Room table:
Room table contain the following parts: these are
Student Numbers
Room number
Field Type Attributes Null Default
std_no int(11) Yes NULL
room_no varchar(30) Yes NULL
Fig: 4.5 Fields of room Table
4.2.6 Log in table:
The login table contains
• User id
• Password
Field Type Null Default
id Varchar(30) No
pass Varchar(70) No
Fig: 4.6 Field of log in Table
Chapter 5
5.0 Work plan:
**We are trying our best to complete our task within three months and complete the total task as follows:
Task ID Task Name Resources
01 Analysis the requirements of the project. Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
02 Module Analysis Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
03
Develop Modules Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
04 Integrate Modules
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
05 Testing, bug finding and bug fixing
Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
06 Release the software and Reserve Jashim Uddin
Palash Chandra Das
Syed Samsuzzoha
Fig: 5.1 Complete task Table
5.1 Tools for design, analysis and Programming:
5.1.1 Design Tools Used:
HTML, HTML Editor, Browser (Internet Explorer, Netscape Navigator, Mozilla etc).
• Client Side and Server Side Scripting :
o PHP
o Javascript
o HTML
• Database Used as Back End:
o MySQL
• Web Server Used:
o Apache
5.1.2 About the Design Tools
5.1.2.1 What is PHP?
• PHP stands for PHP: Hypertext Preprocessor
• PHP is a server-side scripting language, like ASP
• PHP scripts are executed on the server
• PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.)
• PHP is an open source software (OSS)
• PHP is free to download and use
5.1.2.2 What is a PHP File?
• PHP files may contain text, HTML tags and scripts
• PHP files are returned to the browser as plain HTML
• PHP files have a file extension of ".php", ".php3", or ".phtml"
5.1.2.3 What is MySQL?
• MySQL is a small database server
• MySQL is ideal for small and medium applications
• MySQL supports standard SQL
• MySQL compiles on a number of platforms
• MySQL is free to download and use
5.1.2.4 PHP + MySQL
• PHP combined with MySQL are cross-platform (means that you can develop in Windows and serve on a Unix platform)
5.1.2.5 Why PHP?
• PHP runs on different platforms (Windows, Linux, UNIX, etc.)
• PHP is compatible with almost all servers used today (Apache, IIS, etc.)
• PHP is FREE to download from the official PHP resource: http://www.php.net/
• PHP is easy to learn and runs efficiently on the server side
5.1.2.6 What is Apache?
Apache is an HTTP server, originally designed for UNIX systems. This is the version of Apache for Microsoft Windows 2000, NT, 98, and 95 systems. Like the UNIX version, it includes many frequently requested new features, and has an API that allows it to be extended to meet users' needs more easily. It also allows limited support for ISAPI extensions.
Apache performs best, and is still most reliable on Unix platforms. Over time the performance, reliability and security for the Apache Win32 port has improved, and continues to improve. Folks doing comparative reviews of web server performance are still asked to compare against Apache running on a Unix platform such as Solaris, FreeBSD, or Linux.
5.1.2.7 What Is HTML?
The explosive growth of the World Wide Web is relatively unprecedented, although it resembles the desktop publishing revolution of the early and mid-1980s. As personal computers became more common in homes and offices, people began to learn to use them for document creation and page layout. Although early word processing programs were not terribly intuitive and often required memorizing bizarre codes, people still picked them up fairly easily and managed to create their own in-house publications.
Suddenly, the same kind of growth is being seen as folks rush to create and publish pages of a different sort. To do this, they need to learn to use something called the Hypertext Mark-up Language (HTML).
The HTML standard is maintained and debated by a group called the HTML Working Group, which, in turn, is a creation of the Internet Engineering Task Force. The Working Group was charged in 1994 with the task of defining the HTML standard that was in widespread use on the Web at the time (known as HTML 2.0), and then submitting proposals for future standards, including the HTML 3.0 standard.
5.2 Conceptual model of our proposed Routine Management system:
Fig: 5.2 Conceptual model of Routine Management System .
5.3 Consideration For essential factors:
With the respect of dependability the critical analysis is consists of the following parts:
1. Availability
2. Reliability
3. Time Scheduling
4. Teacher Schedule
5. Rooms facilities
6. Safety & Security
The critical analysis of Routine Management System is described below:
5.3.1 Availability: Though our system is fully an online system and automatic. That why any student and any person can see the system any time from any where by using internet.
5.3.2 Reliability: We will gather all the information’s by separating into different categories. All the advices will be discussed by the experts. So, users can get full reliability.
5.3.3 Teacher Schedule: We should need to maintain the all teacher schedule of his/her class in the proper way
5.3.4 Time Scheduling: When we start to make the Routine this time we should be sincere about the Teacher time schedule and the duration of the class.
5.3.5 Room’s facilities: We need the clear idea about every room accommodation and its capacities for distribute the proper class in the proper room.
5.3.6 Safety & Security: We will use the languages My SQL, HTML and PHP. The security level of our project-Routine Management System is very high. Because in this project the normal user only can see the routine of different semester and gather some information about our teachers that means anybody can see the teacher’s personal routine from module but they can’t change or update anything. But the administrator can do any thing. Administrator is the only person who can add department, add semester, add teachers, add subject and add rooms. He can also delete everything. Only he can create the new routine and drop update the routine.
Chapter 6
6.0 Software layout:
In this portion we describe the using process of the software.
6.1 How to Use
There are several options for using this web system
RMS Home page:
Inputs and Outputs
The Input and Output of the various pages on this web based project are given bellow:
1. LogIn
2. Category Search
3. Insert information
4. Update Information
5. Log out
6.2 LogIn
Input page:
6.2.1 Output page (if login success):
6.2 Steps: How to Use
6.2.1 Step 1:
After Signing in the administrator option the admin can do all type of access for editing or updating the routine.
6.2.1.1 Add Department:
Web Page for adding new Department
This page will be display when we want to add new Department in the database.
6.2.1.2 Add Subject:
Web Page for adding new subject:
This page will be display when we want to add new subject in the database.
6.2.1.3 Add new Teacher:
Web Page for adding Teacher:
This page will be display when we want to add new Teacher in the database.
6.2.1.4 Add new Room:
Web Page for adding new Room:
This page will be display when we want to add new Room in the database.
5.2.2 Step 2:
5.2.2.1 Make new Routine:
After completing the input Data an administrator easily can make a routine what he/she wants.
In this part the administrative user select those data which essential for particular department and particular semester which already inserted in data base.
And then submit the data. After submitting a routine will be shown below:
Show Routine:
5.2.3 Step 3:
In step 3 if the administrator thinks in the database there are some unnecessary information he/she can delete the information from the database by using the following steps:
5.2.3.1 Delete Subject:
Web Page for Delete Subject:
This page will be display when we want to delete subject from the database.
5.2.3.2 Delete Teacher:
Web Page for Delete teacher:
This page will be display when we want to delete teacher from the database
5.2.3.3 Delete Room:
Web Page for Delete Room:
This page will be display when we want to delete Room from the database
5.2.4 Step 4:
In this part if the administrators think there is some problem in any routine he/she easily can drop the routine for particular day or whole routine at a time.
5.2.4.1 Drop Routine:
Web page for drop routine:
After selecting the information what we want to drop from the routine then it will be show this page:
In this page there are two options for dropping routine one for dropping particular subject routine for particular day and another for dropping full routine
Chapter 6:
Chapter 7:
7.1 Limitation:
**We think There Are few limitation in our software
These are follows:
• We can’t divide the large semester
• We can’t make exam routine
• In our software we use Teachers id which will be difficult to remember
7.2 Post implementation
After implementing and testing the database web site we found that it almost fulfilled all of the requirements of our abstract and system designing considerations. The application is working smoothly for all its users, such as see the routine of any department for particular semester. Adding teacher information. In further we will try to solve our limitation and we are hopeful next time it will be a complete dynamitic Routine generating Software.
7.3 Discussion
To write discussion phase we should make on thing clear at the very beginning-although the l structure of a routine system is very complex, we took a professional approach, and designed the project in the best possible way so that it could be used instantly by any interested organization.
7.4 Conclusion
Website development is a continuous process. In near future there is a plan that this site will be a complete dynamic routine generating system. Ultimate destination for the user to get information about routine very easily.
At the end of this project we hardly request to the faculties of Computer Science and Engineering (CSE) to approve our project.
Income Tax System
1.1 Introduction:
Every year we have to fill up a huge number of Income Tax Return Forms in our country. But we face many problems and waste our valuable time to fill up this form. Now a day, people are very busy. So, people want to do this work within a second. To do this work computer is very essential. Now only computer but also we need computer based program. But in our country there is no software to do this bothered work easily. So for reducing these suffering of the people, we have to decide to make suitable software for this type of work properly, where the people do not suffer more problems and they can save their valuable time. With this flow of development and with the recent advent of the Internet and World Wide Web various institutions have promoted new technology to do their daily tasks. For this reasons we are the student of “University Of development Alternative (UODA)” want to make software, which is “BANGLADESH INCOME TAX SYSTEM”.
Now we are in the age of online, we feel the importance to do our daily jobs computerize system. We are trying to develop software which will provide lots of facilities to collect tax in a synchronized way. The tax collecting system divided into many modules and income Tax system creates an environment which facilitates both tax collectors and tax assesses.
With the flow of development we are going to introduce an on line income Tax System that can be helpful for our National board of revenue. This online “income Tax System” intended to be our final year project under the integrated project name “BANGLADESH INCOME TAX SYSTEM” in care of Mrs. Kazi Tareen Wali, lecturer, department of CSE, faculty of Engineering.
1.2 Project Life Cycle:
The project life cycle includes various development phases that occur in the life of project starting right from the inception of the project to its final development at the client’s end. The three development phases in a project life cycle are.
· Project initiation
· Project execution
· Project development
1.2.1 Project initiation:
The project initiation phase is fist phase of life cycle. This phase involves creating a complete plan for the project, specifying various activities that will be performed and assigning responsibilities to team members on the basis of their skill set.
1.2.2 Project execution:
After the project plan is made and the responsibilities assigned, the actual development of the project starts. The phase in which the actual development of the project takes place is known as the project execution phase. This is the most crucial phase of any project and is subdivided into the following phases.
1. system analysis
· Initial study
· Information gathering
· Feasibility study
2. System design
· Design standard
· High level design & design tools
· Database design
· Logical design
· Construction
3. System implementation
· integration & testing
· post implementation
1.2.3 Project development:
After the project execution phase, the final phase of a project life cycle is the project development phase. In this phase, the deployed at the client side. This phase also involves providing customer support to the client for some specified period of time.
When project is built it may possibly remain more or less errors, because several type of modification can take place. So for the very first time when we run the database web site we found few problems in tools portions. We fixed this problem including some minor problems immediately, and afterwards the application runs properly.
1.3 Objective of this Project:
v To fill up the income tax return from easily.
v Any people could gather his/her information about income tax through this system easily.
v Try to reduce the suffering of the people.
v Maintenance will become easier and efficient for the people.
v Develop a system to save time and money.
v To make secured data storage.
v This system provides quick service for people.
1.4 Methodology:
Methodology is a collection of procedure, techniques, tools and documentation aids that help the system development in their effort to implement a new Income tax system.
The proposed methodology is planned to meet the objective of Online Income Tax System of UODA in an effective way.
Methods are simply techniques that we apply to accomplish something. Methods include guidelines, techniques and tools for building a software system. In order to develop Computer based Information system we need a methodology. Since there is a huge plan for further work. Methodology-Proposed System, Process of Work, Requirements, Output, feasibility, Time Scheduling, Design (DFD, Database Dictionary & Design, ERD), Implementation, Testing, Evaluation.
Our total project will be evaluation project.
Project Execution and Analysis
2.1.0 System Analysis:
In this part we discuss all of the query and problem of the Income Tax system and try to finding the solution.
2.1.1 What is Income Tax System?
Income tax system is the process which is related to proper management and synchronized way for collecting tax by filling up return form and getting Tax Identification Number (TIN).Here our Government can get the thorough information of income and expenditure for any single people who pay taxes.
At present in our country there is no software for Income Tax System, to complete National Board of Revenue to do their total tasks in a sequential way .This process makes all types of work so much easier because it maintains a schedule. It makes all types of work faster.
2.1.2 Existing System:
In our country the existing Income Tax system is a manual system. If the whole system is manually defined, there are some problems. The problems of existing systems are as follows:
1. It is very slow and takes many times.
2. It is very difficult to make a system.
3. It is not error free.
2.1.3 Propose System:
But now we want to do it automatically. Which will be so easier for
1. Dynamic System
2. Error free
3. User Friendly
2.1.4 Reasons of the changes and major expected benefits:
In our country it is not easy to pay tax system swiftly because this process is done manually so it is not well developed and it is very slow, and lost many time to make a tax system even not easy to get the TIN number. So many people not get eager to pay their tax regarding on income. On the other hand there are many people who don’t want to pay taxes.
Bui in this system we must consider all the information about our assesses income and their expenditure.
So it is easy for government to find out them who is not paying their tax and can get the information instantly.
2.2 Fact Finding Technique:
In order to develop the process model of the new system at first the system analysis the requirement analysis of the proposed system had to be done. During system analysis and requirement analysis of our Income Tax System we have taken the following fact finding Techniques
1. Interviewing
2. Questionnaires
3. Observation
2.2.1 Interviews Structures:
Our goal is to implement to a new system and to overcome the drawbacks of the existing system. That’s way we have to go through an interview process which will give necessary information about the project requirements and help to solve a problems as well as fulfill in the user requirements.
For this purpose we have to select the project to be interviewed as an interviewer we must give priority to the users those who are involved with our Income Tax System. In this regard, we discussed with them about our proposed Income Tax System and wanted to know about the problems of existing Income Tax System. We will also try to collect their opinions about the development of our system, which will help us including new system or add new features.
2.2.3 Observation:
AS the student of UODA we were already familiar with some existing procedure. Yet we communicated with the administrative level personnel to know all the specific activities as stated.
· How the information are stored
· How the assesses details are stored
· How the income and expenditure information are stored
· How the law of paying taxes are stored
· What type of permission exist among the relations
2.3 Project Phase analysis:
Project phases:
We divided our whole work of the project into the following developing phases.
2.3.1 Phase 1: Analysis the requirements of the project.
In this phase we basically analysis the requirements and develop our knowledge on demand. We will sort out all the necessary tools that will be needed. We will grow up the technological background to make workable the software in all environment and network facilities.
2.3.1.1 Requirement Analysis:
We should need to analyze for the Income Tax the following things—
- Users of the Income Tax Return Forms.
- Forms and documents which are used for collecting the Income Tax.
- Various reports used in Income Tax Function. In our system we collect report from income tax office and law chamber.
- How is the current working procedure managed?
- What are the current problems that you are facing?
- Do you think any additional requirement can improve the current process?
- By taking opinion from the user that, how the system can be easier to access for the user?
2.3.1.2 The method of collecting requirements:
v Reading books & related reference book for developing knowledge about Income Tax System.
v Internet Browsing.
v Talking with the students, our friends who are interested to help us by giving information about Income Tax System.
v Talking with our supervisor & other teacher who are experienced to make tax system and working with the automation.
v Talking with Programmer or experienced people who are working this type of related sector.
2.3.2 Phase 2: Module Analysis
In this phase we will analyses our module and fragment the overall module in some small modules. Which help us to complete total system easily.
2.3.3 Phase3: Develop Modules
We will make the task flow and code flow of each module in this phase. We will write the row code to build up the modules.
2.3.4 Phase 4: Integrate Modules
In this phase we will integrate all modules. The backbone of the software will stand up in this phase and the software will be useable.
2.3.5 Phase5: Test, bug finding and bug fixing
We will test the overall features of the software. By testing the features we will find out the bugs. After that all the bugs will be solved.
2.3.6Phase 6: Use of the software
This software will be use for national board of revenue for Online Income Tax System.
2.3.7phase 7:Tools and methods used in this software is mentioned below:
We have used PHP (hypertext preprocessor) and Mysql with innodb and mylsam engine to share information smoothly, which help to fetch information with the databases stored. We have used php 5.0, apache 1.3.14 and Mysql 4.1.9 Information through internet helped us to develop this software. Encryption method used in this software to provide security. JavaScript and CSS (Cascade Style Sheet) used in this software to provide beautiful look.
2.3.8phase 8 : Software Engineering Process
Fig 3.1: Software Engineering Software
System engineering process required developing software properly. It is important to understand the steps of system engineering. It helps to design a software develop a software properly.
2.3.9phase 9(SDLC) Software development life cycle.
A Software Development Life Cycle (SDLC) is an abstract description of the structured end methodological development and modification process applied to the main stages of producing and developing software.
Software engineering is an area of software development in which computer scientists and engineers study methods and tools that facilitate the efficient development of correct, reliable, and robust computer programs. Research in this branch of computer science considers all the phases of the software life cycle, which begins with a formal problem specification, and progresses to the design of a solution, its implementation as a program, testing of the program, and program maintenance. Software engineers develop software tools and collections of tools called programming environments to improve the development process. For example, tools can help to manage the many components of a large program that is being written by a team of programmers.
A Software Development Life Cycle (SDLC) is an abstract description of the structured end methodological development and modification process applied to the main stages of producing and developing software.
REQUIREMENT ANALYSIS
3.1.1 Requirements
The needs of users are called requirements. To make these requirements computerized into software, we need to specify the basic needs & wishes of users. To do this, we have to think about the problem domain of the system that user requests. At last one more thing to say that, we have some techniques, processes to do this, this is Requirement Engineering
3.1.2 Requirement Engineering
Requirement Engineering is that activity transforms the needs and wishes of customers and potential users of computerized systems, usually incomplete and expressed in informal terms into complete, precise consistence specifications, preferably written in formal notations.
Transfer
Partitioning
Abstraction
Fig 3.1:2 Requirement Engineering
3.2.1 System Design Model:
In our Income Tax System there are two types of User models are shown
These are:
1. Normal User (Assesses/Browser)
2. Administrator
3.2.2 Normal User:
A regular user is any kind of assesses who need to pay their taxes can see the tax system and get some information about the Income Tax.
3.2.3 Administrator:
An admin user is a selected user who has the permissions to create a new tax system or edit the tax system. The admin user also viewing the tax system and get some information.
3.3.1 Use case model
Overview of the use cases model of our proposed system” Income Tax”.
Fig: 3.3.1 Use case diagram of proposed Income Tax System.
5.0 Work plan:
**We are trying our best to complete our task within three months and complete the total task as follows:
| Task ID | ||
| 01 | ||
| 02 | ||
| 03 | ||
| 04 | ||
| 05 | ||
| 06 |
Fig: 5.1 Complete task Table
5.1 Tools for design, analysis and Programming:
5.1.1 Design Tools Used:
HTML, HTML Editor, Browser (Internet Explorer, Netscape Navigator, Mozilla etc).
- Client Side and Server Side Scripting :
- PHP
- JavaScript
- HTML
- CSS (Cascade Style Sheet)
- Database Used as Back End:
- My SQL
- Web Server Used:
- Apache (For Local host)
5.1.2 about the Design Tools
5.1.2.1 What is PHP?
· PHP stands for PHP: Hypertext Preprocessor
· PHP is a server-side scripting language, like ASP
· PHP scripts are executed on the server
· PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.)
· PHP is an open source software (
· PHP is free to download and use
5.1.2.2 What is a PHP File?
· PHP files may contain text, HTML tags and scripts
· PHP files are returned to the browser as plain HTML
· PHP files have a file extension of ".php", ".php3", or ".phtml"
5.1.2.3 What is My SQL?
· My SQL is a small database server
· My SQL is ideal for small and medium applications
· My SQL supports standard SQL
· My SQL compiles on a number of platforms
· My SQL is free to download and use
5.1.2.4 PHP + My SQL
- PHP combined with My SQL are cross-platform (means that you can develop in Windows and serve on a Unix platform)
5.1.2.5 Why PHP?
- PHP runs on different platforms (Windows, Linux, UNIX, etc.)
- PHP is compatible with almost all servers used today (Apache, IIS, etc.)
- PHP is FREE to download from the official PHP resource: http://www.php.net/
- PHP is easy to learn and runs efficiently on the server side.
5.1.2.6 What is Apache?
Apache is an HTTP server, originally designed for UNIX systems. This is the version of Apache for Microsoft Windows 2000, NT, 98, and 95 systems. Like the UNIX version, it includes many frequently requested new features, and has an API that allows it to be extended to meet users' needs more easily. It also allows limited support for ISAPI extensions.
Apache performs best, and is still most reliable on Unix platforms. Over time the performance, reliability and security for the Apache Win32 port has improved, and continues to improve. Folks doing comparative reviews of web server performance are still asked to compare against Apache running on a UNIX platform such as Solaris, FreeBSD, or Linux.
5.1.2.7 What Is HTML?
The explosive growth of the World Wide Web is relatively unprecedented, although it resembles the desktop publishing revolution of the early and mid-1980s. As personal computers became more common in homes and offices, people began to learn to use them for document creation and page layout and memorizing bizarre codes.
Suddenly, the same kind of growth is being seen as folks rush to create and publish pages of a different sort. To do this, they need to learn to use something called the Hypertext Mark-up Language (HTML).
The HTML standard is maintained and debated by a group called the HTML Working Group, which, in turn, is a creation of the Internet Engineering Task Force. The Working Group was charged in 1994 with the task of defining the HTML standard that was in widespread use on the Web at the time (known as HTML 2.0), and then submitting proposals for future standards, including the HTML 3.0 standard.
7.1 Limitation:
**We think There Are little limitation in our software
These are follows:
- We can’t divide the large Income Tax System
- We can’t use this system available place
- In our software we use TIN Number which will be difficult to remember.
7.2 Post implementation
After implementing and testing the database web site we found that it almost fulfilled all of the requirements of our abstract and system designing considerations. The application is working smoothly for all its users, such as see the tax system of any people. In further we will try to solve our limitation and we are hopeful next time it will be a complete dynamitic income tax generating Software.
7.3 Discussion
To write discussion phase we should make on thing clear at the very beginning-although the l structure of a routine system is very complex, we took a professional approach, and designed the project in the best possible way so that it could be used instantly by any interested organization.
7.4 Conclusion
Website development is a continuous process. In near future there is a plan that this site will be a complete dynamic tax system .Ultimate destination for the user to get information about income tax system very easily.
At the end of this project we hardly request to the faculties of Computer Science and Engineering (CSE) to approve our project.
Subscribe to:
Posts (Atom)