KIDEL

INTRODUCTION 1.1 Current system

Studying for long duration in schools, attending theoretical lectures may be boring for the school students. The kids are not prone to these disciplined lectures they find hard to study in this manner. Therefore many of the kids of young age are not able understand the theoretical things as th ey dont find that study to be interesting at all. There are many websites which provide creative study material for the kids .

1.2 Need of proposed system

All though there are many websites providing theoretical learning to the kids, which may be in a simple manner and can be easily understood my children but there is a need of a website which is different from these concepts providing additional things and including the old one too. Inspite of the study material and word games a kids site must provide things which makes a child well mannered, social and smart too. Including Math, science and Social science there should be behaving tips, tips for parents, test sessions, social life tips, healthy habits.

1.3 Problem Definition

Now a day, Student joins the college for the placement as well as for better training for their future. But there is manual training has going on there might be lot of problem student as well as placement manager has to face. All the transactions are done manually. Fake entries can be there. System is more error - prone & time consuming. Difficulty in managing data of students. Large piles of records are to be maintained. TPOs have to collect the information of various companies who want to recruit students and notify students time to time about them. It is a time consuming activity of managing, updating and informing specific student for specific company requirements.

1 CS Department MITS

KIDEL

2. SYSTEM DEVELOPMENT LIFE CYCLE

The method or approach used for this software design is Incremental model.

Incremental Model
The Incremental model combines elements of the linear sequential model with the iterative philosophy of the prototyping. This model has been explicitly designed to accommodate a product that evolves over time. When an incremental model is used, the first increment is often a core product. The core product is used by the customer or undergoes a detailed review. As a result of use and/or evaluation a plan is developed for the next increment. The plan addresses the modification to the core product to better meet the needs of the customer and delivery of additional features and functionality. Software is constructed in a step-by-step manner. While a software product is being developed, each step adds to what has already been completed. Incremental software development model is applicable to project because: Software Requirements are well defined. The basic software functionality can be achieved early. Flexible Easier to test and debug during a smaller iteration. Easier to manage risk because risky pieces are identified and handled during its iteration.

Advantages of incremental model: Easier to test and debug during a smaller iteration. Easier to manage risk because risky pieces are identified and handled during its iteration. Generates working software quickly and early during the software life cycle. Easier to test and debug during a smaller iteration.

Disadvantages of incremental model: Each phase of an iteration is rigid and do not overlap each other. Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

2 CS Department MITS

KIDEL

Fig. 1: Incremental Life Cycle Model.

3. ANALYSIS 3.1 Requirement analysis

Requirement Analysis is an intermediate phase between engineering and software design. The main purpose of the requirement analysis is to analyze the collection information to obtain a clear understanding of the product to be developed, with a view to remove all the ambiguities, incompleteness, & inconsistencies from the initial customer perception of the problem. There are main types of problems in the requirements that the analyst needs to identify and resolve: Ambiguity: An anomaly is an ambiguity in the requirement. When a requirement is anomalous, several interpretation of that requirement are possible .Any anomaly in the requirements can lead to the development of incorrect system, since an anomalous requirement can be interpreted in the sever ways. Inconsistency: Two requirements are said to be inconsistent, if one of the requirements contradict the other, or two-end users of the system give inconsistent description of the requirement. Incompleteness: An incomplete set of requirement is one in which some requirements have been overlooked. The lack of these features would be realize by the customer much later, possibly while using the product. Often, incompleteness is caused by the inability of the customer to visualize the system that is to be developed and to anticipate all the features that would be required.

3 CS Department MITS

KIDEL

For our project we took a rough idea for designing. In analysis we first gathered all the required information .system analysts collect data pertaining to the product to be developed and analyze the collected data to conceptualize what exactly needs to be done.

3.1

Implementation 3.2.1 Platform Used 3.2.1.1

Processor RAM Monitor HDD Keyboard MODEM Connection

Hardware Platform
Pentium 4 or later version 1GB or higher CGA/VGA with good resolution 100 MB or higher Standard key Board External and Internal-56 kbps High Speed Internet

3.1.1.1
Operating System

Software Platform.
Windows-xp or higher NetBeans 6.5 My SQL 5.0 JDBC & ODBC

Integrated Development Environment Database Connectors

3.1.2

Front End:Back End: -

JAVA 1.6.0 My SQL 5.0

4 CS Department MITS

KIDEL

3.2

Requirement Specification Functional Requirement Login

For using full features of the website one has to use his unique id and password in order to access the website .

User
The person for whom everything is designed is the user. The user has all the privileges to use full features of the website by accessing it with an id and password.

Sign up
It is the page where a new user gives the required information in order to generate an id and password.

Admin
The person who manages, maintain and provide features to the user is the admin or the administrator. The admin can edit, update, delete anything present on the website or in the database.

Non functional requirement Performance Requirements

Response Time: - The Information page should be able to open frequently in a few second. As frequently operator enters into toll plaza software he can frequently generate the recipt or token.

5 CS Department MITS

KIDEL Throughput: - The number of transactions is directly dependent on the number of users. Capacity: - The system should be capable of handling large number of users at a time.

Safety Requirements
The password given by the user for its id should be of maximum 8 characters length. The password should be alphanumeric.

Software Quality Attributes

Our product will possess certain quality attributes built into the work product specified in this document. Reliability: The software will have been thoroughly tested at time of delivery so that computational errors will not occur. It will be written in a modular structure to make modifications as easy as possible. Maintainability: All the modules will be as maintainable as possible so that changes in one module will not produce software errors in another part of the system. Reusability: The product would be able to be reused by any different node and for any different person. Source code of web application must be reusable so that to avoid future hard work over same concept and same things which company may incorporate. Modifiability: The system shall allow for addition or deletion of information in database. Testing: Test of entire code is necessary. For this, proper testing mechanism will be used to avoid run time problems

6 CS Department MITS

KIDEL

4 Use Case Analyses 3.4.1 Use Case Diagrams

A Use Case Diagram is a type of behavioral diagram defined by and created from a Use-case analysis. It is used to identify the primary elements and processes that form the system. The primary elements are termed as "actors" and the processes are called "use cases." The Use case diagram shows which actors interact with each use case. The main purpose of a use case diagram is to show what system functions are performed for which actors.

login

select course

user

feedback

logout

Fig 2: Use Case Diagram.

7 CS Department MITS

KIDEL

login

pictures

admin text

logout

Fig 3: Use Case Diagram

8 CS Department MITS

KIDEL

add

update

admin

delete

Fig 4: Use Case Diagram

3.4.2 Use Case Description

Kidel consist of two actors 1) User. 2) Admin. The use cases are1) User a. Login Brief description The user and the admin both are required to login using an id and password which makes the website secure from intruders. Actor Admin ,User b. Course Brief description

9 CS Department MITS

KIDEL Here the user selects the favorable course from the list provided to him.

Actors User c. Feedback Brief description After using the services and the features of the website ,user can give his valuable suggestions ,opinion and views . Actor User d. Logout Brief description Whenever the user feels to come out from the website and his account ,user can use the logout ,to log out from his account. Actor Admin, User e. Pictures Brief description This use case is used by the admin to introduce pictures to the website for the user. Actor Admin f. Text Brief description This use case is used to add textual material to the website. Actor Admin g. Add Brief description The admin can add any sort of information using this use case. h. Update

10 CS Department MITS

KIDEL Brief description The admin can update any existing information in this use case.

Actor Admin i. Delete Brief description The admin can delete any irrelevant information or the unused ,non popular material in order to improve, adjust, maintain the website. Actor Admin

3.3

Sequence Diagram
The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur.One of the primary uses of sequence diagrams is in the transition from requirements expressed as use cases to the next and more formal level of refinement. Use cases are often refined into one or more sequence diagrams. In addition to their use in designing new systems, sequence diagrams can be used to document how objects in an existing system currently interact.

Fig. 5: Sequence Diagram for Login.

11 CS Department MITS

KIDEL Fig. 6: Sequence Diagram for Admin.

Fig. 7: Sequence Diagram for User.

12 CS Department MITS

KIDEL

4. DESIGN 4.1 System Flow Diagram

13 CS Department MITS

KIDEL

14 CS Department MITS

KIDEL

4.2 Modules identified There are mainly four modules in the Kidel: 1 login page:
In this module the user and the admin can enter through an id and password .

2 user:
This module uses features of the site and provides valuable suggestions regarding the features and services provided

3 admin :
This module provide essential features such as course,tips,information and much more to the user. This module control, manage and maintain everything in kidel.

4 sign up:
This module gives the user some input text field by which a guest user can become a registered user and can access the site with an id and password provided

15 CS Department MITS

KIDEL

4.3 Class Diagram:In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among the classes.

16 CS Department MITS

KIDEL

Fig.8: Class Diagram.

4.3.1 Description
The class diagram for a KIDEL consists of namely classes Admin, User, Course and Admission. The Admin class and User class are the subclass for a more generalized class user. Admin class handles only two attributes Username and password but has various functions that provide a widespread functionality to admin these include login (), add user (), add course() and some update functions. On the other hand User class handles Username, password, name, address, date of birth and some

17 CS Department MITS

KIDEL other attributes elated to User and has functions such as login(),register(),update(),view() etc. The Course class and Admission class had attributes to specify details and does not contain any functions.

4.4 Database Design 4.4.1 E-R Diagram

Entity-Relationship diagram is a graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within database or information systems. An entity is a piece of data-an object or concept about which data is stored. A relationship is how the data is shared between entities.

18 CS Department MITS

KIDEL

Fig. 9: E-R Diagram.

5. CONCLUSION

19 CS Department MITS

KIDEL

5.1 Important Features

There are lot of features in the kidel, some of which are described below:

1. Course:
This feature has many subjects which is selected by the user, the course is a point where a kid can get all the study material which are necessary for building strong basics of the subjects for the upcoming classes. Some of which includes: Alphabets learning: This sub feature gives the knowledge of the alphabets in a simple manner which a kid can understand. Numbers learning: This sub feature gives the knowledge of the numbers. Words learning: how to make words and even sentence using the alphabets are taught here. Simple mathematics: The basic knowledge of digits, adition, subtraction, division, multiplication.

5.2 Limitation
o This project is made for particularly any institute o The limitation with the application can also be looked into and enhancement can be made as per user requirement. All though this project is made only for a particular institute and supports a particular operating system platform, the wide application area of the project surpasses this small drawback. Hence proving its worth.

5.3 Conclusion
From a proper analysis of positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This component can be easily plugged in many other systems. Also the component is user friendly. Generally the TPOs of the Colleges has to face a lot of problems in management of the Students information. This all information has to be managed manually. So, there is a need to develop a system that can solve the mentioned problem. This software comes with just that solution.

REFERENCES

o o

http://www.bing.com http://www.answers.yahoo.com

20 CS Department MITS

KIDEL

http://www.microsoft.com

21 CS Department MITS