Networking in the form of online social networks is second nature for college students and aspiring young professionals today. The main purpose of creating Social Networking Site for College Students is for meeting worldwide college students and sharing knowledge, education related information’s, etc. It contains standard social network content, like profiles, pictures, email and groups, and video sharing, articles, etc. Student can create a profile, browse locations worldwide, share and collect knowledge, education related tutorials, etc.

This social networking site will only allow members who are college students. This social networking for college students can help you maintain existing relationships with people and share pictures and messages, and establish new ones by reaching out to people you’ve never met before, an also using this site user can share Knowledge’s, education related books, question/answer, and any other information.

This project is developed using PHP and MySQL Server. 

Features:

Profile detail:  It holds student profile information.

Education detail:  It has education articles, tutorials, videos ,photos  and any other information.

Upload detail: It holds uploaded images, videos, tutorials and any other  information’s .

Functional decompositions:

• Student profile.
• Education profile.
• Education articles.
• Images, videos, etc..
• Quiz, question-answers etc.

Type – Web Application

Front End – PHP

Back End – MySQL Server

 Download project code:

Project documents:

System Design

Testing report

Database design

This project is tested by professionals. This social networking Project can be used university standard for submission of final year project for BE, ME, B Tech, BCA, MCA, MBA, BSc-IT, MS, BIT, Diploma, Computer science, IGNOU, etc.

The post Social Networking Site for College Students appeared first on Free Student Projects.

This page covers System design of College Network System. When the requirements document for the software to be developed is available the design activity begins. The main aim of design process is to produce a model or representation of the system, which can be used later to bind the system. The produced model is called design of the system. A system design is a top down approach to minimize complexity and make a problem manageable by subdivided it into smaller segments.

The most changing phase of the system development of life cycle is system design. It refers to the technical specification that will be applied in implementing the candidate system. The design phase is a translation from user oriented document to document oriented to programmers. The potential objects are thoroughly analyzed. Class hierarchies are to check whether the system is behaving the way it has to. There after the classes are individually tested and subsequently they are integrated from the overall system. This level focuses on deciding which modules are needed for system the specifications for those modules and how these modules are that interconnected.

Logical Design:

A logical data flow diagram shows the flow of data through a transaction processing system without regard to the time period when the data flows or the processing procedures occur.

Physical Design:

The physical design maps out the details of physical systems, plans the system implementations, device a test and implementation plan and specifies any new hardware and software.

Objective of the system:

The main purpose of creating Campus Networking Site is for meeting worldwide college students and sharing knowledge, education related information’s, etc. It contains standard social network content, like profiles, pictures, email and groups, and video sharing, articles, etc. Student can create a profile, browse locations worldwide, share and collect knowledge, education related tutorials, etc.

 2.Applicable document:

Profile detail:  It holds student profile information.

Education detail:  It has education articles, tutorials, videos ,photos  and any other information.

Upload detail: It holds uploaded images, videos, tutorials and any other  information’s .

Functional decompositions:

• Student profile.
• Education profile.
• Education articles.
• Images, videos, etc..
• Quiz, question-answers etc..

Functional components and design assumptions.

The Campus network can help you maintain existing relationships with people and share pictures and messages, and establish new ones by reaching out to people you’ve never met before, an also using this site user can share Knowledge’s, education related books, question/answer, and any other information.

Description of the program

The customer switch diagram for online campus networking is shown in the figure below. The input and output of this section is shown in the diagram, however no of details about the function of the online campus networking system is given here. Using this as a starting point, a logical DFD of the system is developed.

Context flow diagram:

The environment in which the software used is depicted in this picture. The CFD shows the external entity action on the software is shown here in CFD as a single process.

Top level DFD:

Top level DFD shows the functional component in the software package. each component shown in the top level DFD.

Description of the components

Functional component 1: Student Profile

Input- Student adds profile information and education details .

Process-  System checks previous student account and education details.

Output-  Student can view education detail and profile details.

Functional component 2: Tutorials

Input-  Student uploads education articles,tutorials,images,videos ..etc.

Process-  System uploads education articles,tutorials,images,videos to database.

Output-  Student can view uploaded education articles,tutorials,images,videos ..etc..

Functional component 3: Admin

Input- Admin can upload and share video tutorials,question papers,books..etc.

Process- System uploads education tutorials,question papers,books to database.

Output- Student can view uploaded tutorials,question papers,books..etc..

The post System design of College Network System appeared first on Free Student Projects.

This document covers Database design of College Network System. A database is an inherent collection of data with some inherent meanings, designed, built, and populated with data for a specific purpose. The following guidelines are been followed during the database design:

• Descriptive names for the tables, columns and indexes
• Singular names for tables and columns
• Proper data type for each column

This document describes the tables that are used to design the software, its attributes, data type, constraints, and relationship among these tables. The relationships among tables are defined via E-R Diagram (Entity-Relationships). A diagrammatical representation of relationships between an entity and its attributes is referred to as E-R model. ER model concentrates on the structure of the database and design of the database. ER model is mainly used in the design of the conceptual schema in database design. An entity may be an object with physical or conceptual existence. The properties that are used to describe the entity are called attributes. Entities that do not have key attributes of their own are called weak entity type. The relationship type that relates a weak entity to its owner is called identifying relation of the weak entity type. A weak entity type always has a total participation constraint with respect to its identifying relation.

Database name: Collegenetworking

Table name:- college

Database name: Collegenetworking

Table name:- college

Table name:- image

Table name:- pracdemo

Table name:- questionanswer

Table name:- questionpaper

Table name:- studentaccount

The post Database design of College Network System appeared first on Free Student Projects.

This document contains Campus Networking testing report. Testing is the process of running a system with the intention of finding errors. Testing enhances the integrity of a system by detecting deviations in design and errors in the system. Testing aims at detecting error-prone areas. This helps in the prevention of errors in a system. Testing also adds value to the product by conforming to the user requirements.

The main purpose of testing is to detect errors and error-prone areas in a system. Testing must be thorough and well-planned. A partially tested system is as bad as an untested system. And the price of an untested and under-tested system is high.

The implementation is the final and important phase. It involves user-training, system testing in order to ensure successful running of the proposed system. The user tests the system and changes are made according to their needs. The testing involves the testing of the developed system using various kinds of data. While testing, errors are noted and correctness is the mode.

 OBJECTIVES OF TESTING:

The objectives of testing are:

• Testing is a process of executing a program with the intent of finding errors.
  • A Successful test case is one that uncovers an as- yet-undiscovered error.

The various types of testing on the system are:

1. Unit Testing.

2. Integration Testing

3. System testing

4. User Acceptance Testing

Unit Testing:

Unit testing focuses efforts on the smallest unit of software design. This is known as module testing. The modules are tested separately. The test is carried out during programming stage itself. In this step, each module is found to be working satisfactory as regards to the expected output from the module.

Integration Testing:

Data can be lost across an interface. One module can have an adverse effect on another, sub functions, when combined, may not be linked in desired manner in major functions. Integration testing is a systematic approach for constructing the program structure, while at the same time conducting test to uncover errors associated within the interface. The objective is to take unit tested modules and builds program structure. All the modules are combined and tested as a whole.

System Testing:

System testing is the stage of implementation. This is to check whether the system works accurately and efficiently before live operation commences. Testing is vital to the success of the system. The candidate system is subject to a variety of tests: on line response, volume, stress, recovery, security and usability tests. A series of tests are performed for the proposed system is ready for user acceptance testing.

User Acceptance Testing:

User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for the user acceptance by constantly keeping in touch with the prospective system users at the time of developing and making changes whenever required.

Validation:

At the culmination of the integration testing, Software is completely assembled as a package. Interfacing errors have been uncovered and corrected and a final series of software test begin in validation testing. Validation testing can be defined in many ways, but a simple definition is that the validation succeeds when the software functions in a manner that is expected by the customer. After validation test has been conducted, one of the three possible conditions exists.

a)     The function or performance characteristics confirm to specification and are accepted.

b)    A deviation from specification is uncovered and a deficiency lists is created.

c)     Proposed system under consideration has been tested by using validation test and found to be working satisfactory.

Output Testing:

After performing the validation testing, the next step is output testing of the proposed system, since no system could be useful if it does not produce the required output in a specific format. The output format on the screen is found to be correct; the format was designed in the system design time according to the user needs. For the hard copy also; the output comes as per the specified requirements by the user. Hence output testing did not result in any correction for the system.

Login:

Registration:

Edit Profile:

Scrap:

Question and Answers:

Photos:

Videos:

Tutorials:

Articles:

The post Campus Networking testing report appeared first on Free Student Projects.

The main objective of the Library Management system project is discipline of the planning, organizing and managing the library tasks. Our project aims at making the task of library easy. Library Management is entering the records of new book and retrieving the details of book available in the library. We can issue book to the library member and maintain their records and can also checks how many book are issued and stock available in the library. In the project we can maintain the late fine of library member who return the issued book after the due date. This Library management system project in JAVA and MS SQL server.

Project title:

Library management system /

Library management system project in JAVA

Project category :

RDBMS

Language and software tool used :

• Front End : Java
• Operating System : Window 7
• Back End : Microsoft SQL Server 2005

Structure of the project:

Proposed System:

In the proposed system, we assume that each member will be having a identity card which can be used for the library book issue, fine payment etc. whenever library member wish to take a book, the book issued by the library authority will be check both the book details as well as the student details and store it in library database. In case of retrieval of book much of human intervention can be eliminated.

Module Description:

         1. User Module:

In this module student can check availability of the book…

The following are the sub module in the user module.

• Book return: Here student will return the books  to the library…

2. Administrator Module:

This is the main module in the proposed project. The administrator can read and write information about any member. The administrator can also update, create and delete the record of membership as per requirement and implementation plans.

The following are the sub module in the administrator module.

• Register student: Allow the administrator to register new student and update the student records.

• Book details: Allow administrator to entered book details.

• Book issue: Here administrator issues the books to the student from library.

Future scope of the project:

We can consider much future scope to this application. The following are some of there.

• Online use of the library can be good feature for the Library Management system.
• Advanced fine payment system can be added.
• Inventory system can be used to maintain the books of the library.

Hardware requirement :

• Operating system: Window 7
• Hard disks: 40GB
• RAM: 256 MB

Software requirement :

• Java language
• Net beans IDE 7.0.1
• MS SQL server 2005

Download project reports

• Download synopsis of Library management system project in JAVA
• Library management system project SRS document
• System design of Library Management System
• Library Management System database design
• Detailed design document for library management system
• Test cases for Library management system

The post Library management system project in JAVA appeared first on Free Student Projects.

This page contains Library management system project SRS document. A development process consist of various phases, each phase ending with a defined output. The main reason for having a phased process is that it breaks the problem of developing software into successfully performing a set of phases, each handling a different concern of software development. This ensures that the cost of development is lower than what it would have been if the whole problem was tackled together. Furthermore, a phased process allows proper checking for quality and progress at some defined points during the development (end of process).Without this one would have to wait until the end to see what software has been produced.

Any problem solving in software consist of these steps:-

• Requirement  Analysis  :

Requirement Analysis is done in order to understand the problem the software system is to solve.

There are two major activities in this phase:  problem understanding or analysis and requirement specification. In problem analysis, the aim is to understand the problem and its context, and the requirements of the new system that is to be developed. Once the problem is analyzed and the essentials understood, the requirements must be specified in the requirement specification document. The requirements document must specify all functional and performance requirements; the formats of inputs and outputs etc.

• Software  Design :

The purpose of design phase is to plan a solution of the problem Specified by the requirements document. This phase is the first step in moving from the problem domain to solution domain.

The design activity often results in three separate outputs: architecture design, high level design and detailed design.

• Coding  :

The main goal of coding phase is to translate the design of the System into code in a given programming language. The coding phase affects both testing and maintenance profoundly. The goal of coding should be to reduce the testing and maintenance effort, hence during coding the focus should be on developing programs that are easy to read and understand.

• Testing  :

The function of testing is to detect the defects in the Software. The main goal testing is to uncover requirement, design and coding errors in the programs.

The main goal of the requirement phase is to produce the software requirement specification (SRS), which accurately capture the client’s requirements. SRS is A document that describes what the software should do. The basic purpose of SRS is to bridge the communication gap between the clients, the end  users  and the Software developers. Another purpose is helping user to understand their own needs.

Purpose:

The SRS typically contains the brief description of the project. The purpose of the requirement document is to specify all the information required to design, develop and test the software.

• The purpose of this project is to provide a friendly environment to maintain the details of books and library members.
• The main purpose of this project is to maintain easy circulation system using computers and to provide different reports.

Scope:

The document only covers the requirements specifications for the Library Management System. This document does not provide any references to the other component of the Library Management System. All the external interfaces and the dependencies are also identified in this document.

Feasibility study: The overall scope of the feasibility study was to provide sufficient information to allow a decision to be made as to whether the Library Management System project should proceed and if so, its relative priority in the context of other existing Library Management Technology.

The feasibility study phase of this project had undergone through various steps which as describe as under:

• Identity the origin the information at different level.

• Identity the expectation of user from computerized system.

• Analyze the drawback of existing system(manual system)

Definition, Acronyms, Abbreviation:

• JAVA  -> platform independence
• SQL    -> Structured query Language
• DFD   -> Data Flow Diagram
• CFD    -> Context Flow Diagram
• ER      -> Entity Relationship
• IDE     -> Integrated Development Environment
• SRS    -> Software Requirement Specification

Reference:

• An Integrated Approach Software Engineering Third Edition by Pankaj Jalote.

• Java :- Balaguru swamy

• SQL :- JosephL Jorden

Overview:

The implementation of Library Management starts with entering and updating master records like book details, library information. Any further transaction like book issue, book return will automatically update the current books.

Overall Description :

Product Perspective:

The proposed Library Management System will take care of the current book detail at any point of time. The book issue, book return will update the current book details automatically so that user will get the update current book details.

Product function:

• The main purpose of this project is to reduce the manual work.
• This software is capable of managing Book Issues, Returns, and Calculating/Managing     Fine. Generating various Reports for Record-Keeping according to end user requirements

User characteristics:

We have 2 levels of users

• User module: In the user module, user will check the availability of the books.
  • Book return

• Administration module: The following are the sub module in the administration module.
  • Register user
  • Entry book details
  • Book issue

General Constraints:

Any update regarding the book from the library is to be recorded to have update & correct values.

Assumption and dependencies:

All the data entered will be correct and up to date. This software package is developed using java as front end which is supported by sun micro system. Microsoft SQL server 2005 as the back end which is supported by Window 7.

Specific Requirement:

External Interface Requirement:

                The user should be simple and easy to understand and use. Also be an interactive interface .The system should prompt for the user and administrator to login to the application and for proper input criteria

User Interface:

The software provides good graphical interface for the user any administrator can operate on the system, performing the required task such as create, update, viewing the details of the book.

• Allows user to view quick reports like Book Issues/Returned etc in between particular time.
• Stock verification and search facility based on different criteria.

Hardware interface:

• Operating system : window
• Hard disk :40 GB
• RAM : 256 MB
• Processor : Pentium(R)Dual-core CPU

Software interface :

•  Java language
• Net beans IDE 7.0.1
• MS SQL server 2005

 Communication interface:

Window

Functional requirements:

• Book entry: In this module we can store the details of the books.
• Register student: in this module we can keep the details of the new student.
• Book issue: This module is used to keep a track of book issue details.
• Book return: This module enables to keep a track of return the books.

Performance requirements:

The capability of the computer depends on the performance of the software. The software can take any number of inputs provided the database size is larger enough. This would depend on the available memory space.

Design constraints :

Each member will be having a identity card which can be used for the library book issue, fine payment etc. whenever library member wish to take a book, the book issued by the library authority will be check both the book details as well as the student details and store it in library database. In case of retrieval of book much of human intervention can be eliminated.

 System attributes :

• Maintainability: There will be no maintained requirement for the software. The database is provided by the end user and therefore is maintained by this user.
• Portability: The system is developed for secured purpose, so it is can’t be portable.
• Availability: This system will available only until the system on which it is install, is running.
• Scalability: Applicable.

Other requirements:

There are no other requirements.

Download Library management system project SRS document

The post Library management system project SRS document appeared first on Free Student Projects.

The purpose of design phase is to plan a solution for problem specified by the requirements. System design aims is to identify the modules that should be in the system the specification of these modules and how they interact with each other to produce the desired result. The goal of the design process is to produce a module or representation of a system which can be used later to build that system. The produced model is called design of the system.

The most important phase of the software of the system is designing the different modules. The accurate planning and proper interconnections with the modules will give a good output in the implementation part.

Application documents :

As the project is user-friendly, it can be applied to large database with more information. This software can be used by Library Management System to make the work simple. They can get information quickly as possible. It can handle large volume of data and present the report whenever required. In this project, we use SRS as the applicable documents.

Function decomposition :

Functional decomposition refers broadly to the process of resolving the functional relationship into constituent parts in such a way that original function can be reconstructed (i.e. recomposed) from those parts by function composition. In general, this process of decomposition is undertaken either for the purpose of gaining insight into the identity of constituent components (which may reflect individual physical processes of interest, for example) or for the purpose of obtaining a compressed representation of global function, a task which is feasible only when the constituent processes possess a certain level of modularity (i.e. independence or non-interaction).

Functional component and assumption :

• Register user: New user can register.
•  Book issue: Here the books will issue to the user.
•  Book return: Here the books are returned.
• Search/view book details: It is used to search and view the books.
• Update book details: Here the details of the books will be updated.
• Payment: Here payment should be done in manual.

Description program :

Context Flow Diagram:

A Context Flow Diagram is 0^th level DFD. It only contains one process node that generalizes the functions of the entire system in relationship to external entities. In Context Flow Diagram the entire system is treated as a single process and all its input, output sinks and source are identified and shown.

Data Flow Diagram:

A Data Flow Diagram is a graph showing the flow of data values from their source in  objects through process that transform them to their destination in other objects.

DFD also knows as “Bubble charts” has the purpose of clarifying the system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design phase that functionally decomposes the requirements specifications down to the lowest level of details. A DFD consist s of a series of bubbles joined by lines.

DFD use a number of symbols to represent system. Most data flow modeling methods use 4 kinds of symbols to represent 4 kinds of system components: processes, data stores and external entities

Description of component:

Function component 1:

Registration: New user can register.

Input: user details.

Process definition: Processing information and stored in the database.

Output: User details updated in the database.

Function component 2:

Book issue: Here the books will issue to the user.

Input: Book ID.

Process definition: Searching books.

Output: Search and retrieving book information.

Function component 3:

Book return: Here the books will return.

Input: Book ID.

Process definition: Checking book details.

Output: Book is returned.

Function component 4:

Search/view book details: It is used to search and view the details of the book.

Input: Book ID.

Process definition: Searching books.

Output: Details of the book will be shown.

Function component 5:

Update book details: New book entry can be added.

Input: Book ID.

Process definition: Processing the information.

Output: Update in database

Function component 6:

Payment: Here payment is done.

Input: User ID.

Process definition: Checking user account details.

Output: Book will be issued.

The post System design of Library Management System appeared first on Free Student Projects.

This page contains information of Library Management System database design. The database is a collection of information and is systematically stored in tables in the form of rows and columns. The table in the database has unique name that identifies its contents. The database in turn is further described in detail giving all the fields used with the data types, constraints available, primary key and foreign key.

Database design is used to manage large of information. In this database we describe the entire 4 table available in the software, which are used to store all the records.

2. Data types and its description:

Fields in database table have a data type used in database table are explained below.

1. Integer: one optional sign character (+ or -) followed by at least one digit (0-9). Leading and trailing blanks are ignored. No other character is allowed.
2. Varchar:  It is used to store alpha numeric characters. In this data type we can set the maximum number of characters up to 8000 ranges by defaults SQL server will set the size to 50 characters range.
3. Data/time: Data/time data type is used for representing date or time.

Database Name: bookdetails

Database Name: student

Database Name: issue

Database Name: return

Entity Relationship Diagram:

Entity Relationship Diagram is used in modern database software engineering to illustrate logical structure of database. It is a relational schema database modeling method used to

Model a system and approach. This approach commonly used in database design. The diagram created using this method is called ER-diagram.

The ER-diagram depicts the various relationships among entities, considering each object as entity. Entity is represented as rectangle shape and relationship represented as diamond shape. It depicts the relationship between data object. The ER-diagram is the notation that is used to conduct the data modeling activity.

Entity: Entity is the things which we want to store information. It is an elementary basic building block of storing information about business process. An entity represents an object defined within the information system about which you want to store information. Entities are distinct things in the enterprise.

Relationship: A relationship is normal connection or association between entities used to relate two or more entities with some common attributes or meaningful interaction between the object.

Attributes: Attributes are the properties of the entities and relationship descriptor of the entity. Attributes are elementary pieces of information attached to an entity.

Download this documentation

Download synopsis of Library management system project in JAVA

Library management system project SRS document

The post Library Management System database design appeared first on Free Student Projects.

This page covers Detailed design document for library management system. Detailed design starts after the system phase and system has been certified through the review. The goal of this phase is to develop internal logic of each of the modules identified during system design. In the system design, the focus is an identifying the modules, whereas during the detailed design the focus is on designing the logic for the modules. In other words in system design attention is on what components are needed, while in the detailed design how the component can be implemented in the software is the issue.

The design process for software system has two events. At the first level focus is on deciding which modules are needed for the system, the specification of these modules and how the modules should be interconnected. This is called system design or top level design. In the specification of the module can be satisfied is decided. This design level is often called detailed design or logic design, because the detailed design is extension of system design, system design controls the major structural characteristics of the system. The system design has a major impact testability and modifiability of a system and impacts its efficiency much of the design efforts for the designing software are spent creating the system design.

Applicable documents:

The detailed design refers the system documents hence the first application documents here is system design, also we are referring the data structure. Hence second application document here is database design

Structure of software package:

The software package consists of following functional components.

• Functional component 1: Registration.
• Functional component 2: Book issue.
• Functional component 3: Book return.
• Functional component 4: Search/view book details.
• Functional component 5: Update book details.
• Functional component 6: Payment (Fine).

Structure charts:

It is graphics representation of the control logic of processing function or module representation of the system. It is one of the most common methods used for system design. In a structure charts each program module is represented by a rectangle box, modules at the top level of the structure charts call the modules at the lower level. The connection between modular are represented by lines between the rectangular boxes. The connection describes the data flows between the called and calling modules.

Module Decomposition:

Student details:

In this form the users have to enter the details about the student like name, regno, course…etc. If the proper details are not entered at the same time error message will be displayed and record will not be stored…And if the entered register number is already exist then the details can’t be stored and error message will be displayed.

Delete student details:

In this case admin can delete individual student details by entering his register number .If the Register no is not entered at same time message will be displayed and record will not be stored…And if the entered number is already deleted then it will be giving the message.

Book issue:

In this form the Liberian can issue the books to the student. If the books are already distributed to students then Liberian can’t issue those particular books.

Book return:

Here the user must return the book on given date… Otherwise fine will be calculated…

Calculate fine:

In this case we can maintain the late fine of library member who return the issued book after the due date…

Download Detailed design document for library management system

The post Detailed design document for library management system appeared first on Free Student Projects.

This software explains Test cases for Library management system. Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. Testing presents an interesting of a system using various test data. Preparation of the test data plays a vital role in the system testing. After preparation the test data, the system under study is tested those test data. Errors were found and corrected by using the following testing steps and corrections are recorded for future references. Thus, series of testing is performed on the system before it is already for implementation.

The development of software systems involves a series of production activities where opportunities for injection of human errors are enormous. Errors may begin to occur at the very inception of the process where the objectives may be erroneously or imperfectly specified as well as in later design and development stages. Because of human in ability to perform and communicate with perfection, software development is followed by assurance activities.

Quality assurance is the review of software products and related documentation for completeness, correctness, reliability and maintainability. And of course it includes assurances that the system meets the specification and the requirements for its intended use and performance. The various levels of quality assurance are described in the following sub sections.

System Testing

Software testing is a critical element of software quality assurance and represents the ultimate review of specifications, design and coding. The testing phase involves the testing of system using various test data; Preparation of test data plays a vital role in the system testing. After preparation the test data, the system under study is tested.

Those test data, errors were found and corrected by following testing steps and corrections are recorded for future references. Thus a series testing is performed on the system before it is ready for implementation.

The various types of testing on the system are:

• Unit testing
• Integrated testing
• Validation testing
• Output testing
• User acceptance testing

Unit testing

Unit testing focuses on verification effort on the smallest unit of software design module. Using the unit test plans. Prepared in the design phase of the system as a guide, important control paths are tested to uncover errors within the boundary of the modules. The interfaces of each of the modules under consideration are also tested. Boundary conditions were checked. All independent paths were exercised to ensure that all statements in the module are executed at least once and all error-handling paths were tested. Each unit was thoroughly tested to check if it might fall in any possible situation. This testing was carried out during the programming itself. At the end of this testing phase, each unit was found to be working satisfactorily, as regarded to the expected out from the module.

Integration Testing

Data can be across an interface one module can have an adverse effect on another’s sub function, when combined may not produce the desired major function; global data structures can present problems. Integration testing is a symmetric technique for constructing tests to uncover errors associated with the interface. All modules are combined in this testing step. Then the entire program was tested as a whole.

Validation Testing

At the culmination of integration testing, software is completely assembled as a package. Interfacing errors have been uncovered and corrected and final series of software test-validation testing begins. Validation testing can be defined in many ways, but a simple definition is that validation succeeds when the software functions in manner that is reasonably expected by the consumer. Software validation is achieved through a series of black box tests that demonstrate conformity with requirement. After validation test has been conducted, one of two conditions exists.

• The function or performance characteristics confirm to specification that are accepted.
• A validation from specification is uncovered and a deficiency created.

Deviation or errors discovered at this step in this project is corrected prior to completion of the project with the help of user by negotiating to establish a method for resolving deficiencies. Thus the proposed system under consideration has been tested by using validation testing and found to be working satisfactorily.

Output Testing

After performing the validation testing, the next step is output testing of the proposed system, since a system is useful if it does not produce the required output in the specific format required by them tests the output generator displayed on the system under consideration. Here the output is considered in two ways: – one is onscreen and the other is printed format. The output format on the screen is found to be correct as the format was designed in the system design phase according to the user needs. As far as hardcopies are considered it goes in terms with the user requirement. Hence output testing does not result any correction in the system.

User Acceptance Testing

User acceptance of the system is a key factor for success of any system. The system under consideration is tested for user acceptance by constantly keeping in touch with prospective system and user at the time of developing and making changes whenever required.

TEST RESULT: UNIT TESTING

LOGIN FORM:

BOOK ENTRY FORM:

 USER ACCOUNT FORM:

BOOK ISSUE FORM:

BOOK RETURN FORM:

 Download test cases

The post Test cases for Library management system appeared first on Free Student Projects.

This main objective of the Hospital Management System is to computerize the maintenance of the patient details and billing section in the hospital. This system has been developed to form whole management system including Employees, Doctors, Nurses, Patients, Bills, and Complains etc. It also includes the details about the laboratory checkups.

LANGUAGE AND SOFTWARE TOOL USED:

Front End: Java

Operating System: Windows XP

Back End: SQL SERVER 2005

STRUCTURE OF THE PROJECT:

Proposed System:-

In the proposed system, the administrator can insert, delete and modify the patient records as per the requirements. The laboratory reports and billing details can be easily maintained in this system. This project will help to smoother the process of the hospital activities.

Module Description

Administration Module:-

This is the main module in the proposed project. The administrator can read and write information about any member such as patient, doctors and staff of the hospital. They can also update, create and delete the record of members as requirement and implementation plan.

Patient Module:-

This module contains the patient records. The sub modules are

Inpatient:-

It contains details of patients who are admitted.

Outpatient:-

The outpatient module contains details of the patient who came for checkups.

Lab Module:-

Lab module is used to generate laboratory reports.

Billing Module:-

The bill payment report of the patient.

FUTURE SCOPE OF THE PROJECT

This project will enhance the patients and the hospital to serve more quickly and efficiently. This software is developed in order to computerize the activities which take more time, if done manually.

Hospital billing system will enable the patient and hospital staff to make things faster and can get information quickly. If we want any information about patient, we can access it quickly.

HARDWARE REQUIREMENT

OS-Windows

Hard Disk-80 GB

RAM-1 GB

SOFTWARE REQUIREMENT

Java language

Net Beans IDE 6.9.1

SQL server 2005.

Find the below web page to download JAVA based Hospital Management System

Project reports:

Download Hospital management System project Synopsis:

SRS documentation for Hospital Management System

System analysis design hospital management system

The post Hospital Management System in JAVA appeared first on Free Student Projects.

This page contains SRS documentation for Hospital Management System. The SRS is produced at the culmination of the analysis task. The function and performance allocated to software as part of the system engineering and refined by establishing a complete information description, a detailed functional description, a representation of system behavior, indication of performance requirements and design constrains, appropriate validation criteria and the other information related to requirements.

The SRS is technical specification of requirement of Hospital Management system. This specification describes what the proposed system should do without describing how it will do it. It also describes complete external behavior of proposed system.

Purpose:-

The main purpose of our system is to make hospital task easy and is to develop software that replaces the manual hospital system into automated hospital management system. This document serves as the unambiguous guide for the developers of this software system.

Scope:-

The document only covers the requirement specification for the hospital management system. This document does not provide any references to the other component of the hospital management system. All the external interfaces and the dependencies are also identified in this document.

Feasibility Study:-

The overall scope of the feasibility study was to provide sufficient information to allow a decision to be made as to whether the hospital management system project should proceed and so, its relative priority in the context of the other existing hospital management system.

The feasibility study of this project had undergone through various steps which as describe as under:

a)   Identify the origin of the information at different level.

b)  Identify the expectation of user from computerized system.

c)   Analyze the drawback of existing system.

Definition,Acronyms,Abbreviations:- 

CFD: – Context Flow Diagram

DFD: – Data Flow Diagram

IDE: – Integrated Development Environment

Java:-PlatformIndependent,Object_orientedprogramming language

SQL: – Structured Query Language

SRS: – Software Requirement Specification.

Reference:-

1) An integrated approach to software engineering, Third edition by Pankaj jalote

2) Java – Balaguruswamy

3) SQL server 2005 – JosephL Jordan

Overview:-

Hospital Management System is a process of implementing all the activities of the hospital in a computerized automated way to fasten the performance.

This project is to maintain the patient details, lab reports and to calculate the bill of the patient. You can also manually edit any patient details and issue bill receipt to patient within few seconds.

OVERALL DESCRIPTION

     Product perspectives:-

This project gives the procedural approach how a patient gets treatment, details about date of treatment and finally depending on different criteria like room allocated, lab reports, treatment and medicine taken…..etc,how billing is calculated. During billing health card facility is also considered.

Product Function:-

The data represented in hospital management application will perform the following major function:-

• Patient Details: – It includes inpatient and outpatient details.
• Lab reports
• Billing Details

This software will help to calculate the bill much quicker and simpler way. This enables the organization to keep the information in efficient and systematic way.

User Characteristics:-   

This software is developed such that total appearance of the product to make it more user friendly. The operator will be provided with loginid and password. General users with basic computer skills can use this software.

General Constraints:-

Any update regarding the patients information from the hospital are to be recorded to have updated and correct values.

Assumption and Dependencies:-

All the data entered will be correct and up_to_date.This software package is developed using java as front end which is supported by sun micro system, MS SQL server 2005 as the back end which is supported by Microsoft windows xp.

Functional Requirements:-

• Administration module
• Patient module
• Inpatient module
• Outpatient module
• Lab module
• Billing module

The post SRS documentation for Hospital Management System appeared first on Free Student Projects.

This page contains System analysis design of hospital management system. The purpose of design phase is to plan a solution for problem specified by the requirements. System design aims to identify the modules that should be in the system, the specification of those modules and how they interact with each other to produce the result. The goal of the design process is to produce a model or representation of a system can be used later to build that system. The produced model is called design of the system.

Applicable Document

As the project is user friendly, it can be applied to large database with more information. This software can be used by hospital management to make the work simple. They can get information quickly as possible. It can handle large volume of data and present the report whenever required. In this project, we use SRS as the applicable document.

Functional Component and Assumptions

Administration module:-

Administrator can view all the details of the hospital record.

Inpatient module:-

This module is used to store details of patients who are admitted.

Outpatient module:-

The outpatient module contains details of the patient who are came for check_ups.

Lab module:-

Lab module is used to generate laboratory reports.

Billing module:-

Billing module is used to calculate the bill of the patient.

Description of the Program

   Context Flow Diagram:- 

A context flow diagram is a 0^th level DFD.It only contains one process node that generalizes the functions of the entire system in relationship to external entities.

Data Flow Diagram

1st level DFD

2nd Level and 3rd level DFD

Description of Component

Administration module:-

Input: – User Name, Password

Process Definition: – Login to the system

Output:-If login is successful then administrator can view and update the records.

Inpatient module:-  

Input: – Inpatient detail

Process Definition: – Information about the treatment given to the patients who are admitted.

Output: – Information about the patient.

Interface with other module: – The inpatient details are necessary for lab reports and billing.

 Outpatient module:- 

Input: – Outpatient detail

Process Definition: – This module has the information about the treatment given to the patient who are came to check up.

Output: – Information about the patient.

Interface with other module: – The outpatient details are necessary for lab reports and billing.

 Lab module:-

Input: – Patient ID, Category

Process Definition:-Laboratory reports of the patient.

Output: – Lab report and charge.

Interface with other module: – This module requires information from inpatient and outpatient modules.

Billing module:-

Input: – Patient ID

Process Definition:-Calculates bill and deduct amount if any card facility is available.

Output: – Bill.

Interface with other module: – Billing module requires information from inpatient and outpatient modules.

Download System design of hospital management system

Find the below web page to download JAVA based Hospital Management System

The post System analysis design hospital management system appeared first on Free Student Projects.

Hospital management system database design is uploaded in this page. A database is a collection of information and is systematically stored in tables in the form of rows and columns. The table in the database has unique name that identifies its contents. The database in turn is further described in detail giving all the fields used with the data types, constraints available, primary key and foreign key.

Database design is used to manage large bodies of information. In this database we describe all the 4 tables available in the software, which are used to store all the records.

Data types and its description:   

Fields in database table have a data type. Some of the data types used in database table are explained below.

a)   Integer:-

One optional sign character (+ or -) followed by atleast one digit (0-9). Leading and trailing blanks are ignored. No other character is allowed.

b)  Varchar:-

It is used to store alpha numeric characters. In this data type we can set the maximum number of characters upto 8000 ranges by default SQL server will set the size to 50 characters large.

a)   Date/Time:-

Date/Time data type is used for representing data or time.

Patient Table:

Doctor Table:

Lab Table:

Inpatient Table:

Outpatient Table:

Room Table:

Bill Table:

E-R Diagram

Entity relationship diagram is used in modern database software engineering to illustrate logical structure of database. It is a relational schema database modeling method used to model a system and approach. This approach commonly used in database design. The diagram created using this method is called E-R diagram.

Download Hospital management system database design with ER diagram:

Hostel Management system synopsis>>

SRS documentation for Hospital Management System>>

Hospital management system DFD, CFD, System design

SRS documentation for Hospital Management System>>

The post Hospital management system database design appeared first on Free Student Projects.

Project Office automation system (oas) aims at creating an application which will automate the processes in college office. Using this it is possible to keep a database of college information like information about the students studying in various courses, employee information in various departments, staff and non staff details etc. Transaction involving fee and salary is also stored. Fees receipts are generated for students. Reports are maintained for future usage. Search engine is used to search required information.

Project title: Office automation system

Use of Office automation system

The purpose of this project is to automate the office work. The current system in the office is a manual system which includes paper document. In such a system its very difficult to keep track of all the records. Our project aims at creating an application which will automate the processes in a college office.

The Office automation system consists of the following modules:

• Master
• Student
• Employee
• Transaction
• Search
• Report
• Exit

Software Interface

The software requires the support of the following software for the database and other requirements.

• VB.NET feature of the Microsoft Visual Studio 2008 for the front end.
• SQL server 2008 for the database

FUNCTIONAL REQUIREMENTS

MODULE 1: ATTENDENCE

In this module the user is required to enter Staff ID,name and Password and click the RegisterAttenence button to indicate his presence for that day.

MODULE 2: ATTENDENCE VIEW

This module shows the yearly and monthly attendance of the Staff.

MODULE 3: COURSE

This module enables the user to manipulate and view the course details- Departmentwise  and Description.

MODULE 4: DEPARTMENTENTRY

This module enables the user to manipulate and view the department details – Department  and Description.

MODULE 5 : DESIGNATION

This module enables the user to manipulate and view the designation details – Designation and Description.

MODULE 6 : DONATION

This enables the user to manipulate and view the donation details that have been made

• Department wise
• Course wise
• Semester wise.

MODULE 7 : EXAM DETAILS

This enables the user to manipulate and view the exam details

• Subject name
• Date when the exam is held
• Total marks
• Pass marks

MODULE 8 : FEES DETAILS

This enables the user to manipulate and view the fees details like

• Tution fees
• Exam fees
• Donation fees

MODULE 9 : FEES PAYMENT

This enables the user to manipulate and view the fees payment details which are

• Fees amount
• Concession
• Fees paid
• Balance amount
• Donation fees

MODULE 10 : MAIN PAGE

When the user logs in, the user goes to this module which contains a menu strip that has 7 menu items.

• Master

When the user clicks the Master menu item, a dropdown list appears that contains

• Department
• Course
• Designation
• Subject details
• Examination details
• Fees details
• Donation and tuition
• Scholarship
  • Student

When the user clicks the Student menu item, a dropdown list appears that contains

• Profile entry
• Other details
• Result entry
  • Employee

When the user clicks the Employee menu item, a dropdown list appears that contains

• Staff entry
• Attendance
  • Transaction

When the user clicks the Transaction menu item, a dropdown list appears that contains

• Student transaction
•  Employee transaction
• Report

Download SRS:

http://www.docstoc.com/docs/131804940/SOFTWARE-REQUIREMENT-SPECIFICATION

The post Office automation system appeared first on Free Student Projects.

Chennemane is a traditional folk game. It is played on a wooden board with two parallel rows of pits. Nowadays all the games are computerized but Chennemane is left out. So we are implementing this in computer to spread over the world.

Front end tool- C#.NET 2005

Back end tool- SQL 2005

Hardware Requirements

• PC with Dual core
• Key board and mouse
• Speaker

Download project:

Brief Description

1. On his turn a player distributes the contents of one of his holes in the ensuing holes, one by one, in a counterclockwise direction. If the last seed falls into an occupied hole and the next hole is empty, the contents of the succeeding hole are lifted. Now another player gets the opportunity to play. If he gets only one seed, it is called “Puyinka” else it’s known as “Bule”.

2. If the last seed in hand is placed into a murte, its contents become wanasu (“meal”), that is, all four seeds are captured and put in the player’s store.

3. Afterwards the player continues his move by distributing the seeds of the following hole.

4. The move ends when the last seed is placed in an empty hole, when the hole following a wanasu is empty or after an atappe play.

5. The game is played until a player can demonstrate at his turn that in four consecutive draws he does not have to place a seed in one of his opponent’s holes. That player wins the seeds that are still remaining on the board.

6. The player who captured more seeds has won the round.

7. The successive rounds are played by filling the holes on the player’s side with his winnings.

8. The game is over when at the end of three rounds. The winner will be the one who captures more number of seeds. The phrase to claim victory is poli maipunu (“plunder”).

The game is for two players.
1. The object of the game is to give each player 28 manjutti beads.

2. The first player, who wins the toss puts in each circular hole (‘mane’ or ‘home’) even number (say 4) of beads at a time and continue till u run out of your beads.

3. And then if you are left with odd numbers of beads in one of the holes those beads go to your opponent player and vice versa.

4. The person ends with all the opponents’ beads or more number of beads is the winner!

 Chennemane Gaming Software video Demonstration:

Download this BCA Project:

• Download Project Synopsis
• Download Project Code
• Download Database and Documentation of Database design
• Download Chennemane Game SRS

The post Chennemane Gaming Software appeared first on Free Student Projects.

This page contains Chennemane Game system design. System design is a process of art of defining the architecture, components, modules, interfaces and data for a system to satisfy specified requirements. One could see it as the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering.

Functional components:

This section identifies the functional components of the software package.

Modules used in this project are:

Login Module: In this module, when a new user wants to become a    member then he can registration.

Player selection: In this module, a logged in player has to select his opponent by selecting another user who is logged into the game.

Game selection: Here, a logged in player can select the mode of game (i.e.; single end mode or LAN game mode).

Playing: This module has the main functioning controls to play the game.

Score: Score module is used to manipulate the score scored by each player.

Result: Result module is used to display the result of each and every game.

Alert: This module is used to send the alerts to the player about his achievements.

Description of components

Functional component 1:

 Login: In this module, when a new user wants to become a member                                           then he can make registration.        

Input: Username and Password

Process Definition: Authentication

Output: If Login is successful then it transfers to Homepage. If not, then it will back to Login page.

Interface with other Functional components:    All the modules will be affected as   the result of this module.

Functional component 2:

  Player selection: In this module, a logged in player has to select his opponent by selecting another user who is logged into the game.

Input: selection of players

Definition: Authentication

Output: the game will be played between two players.

Interface with other Functional components:  All the modules will be affected as the result of this module.

Functional component 3:

Game selection: Here, a logged in player can select the mode   of game (i.e.; training mode or game mode).

Input: training mode and play mode           

Process Definition: user or player will get instructions from training mode and he can play using play mode

Output: player plays the game.

Functional component 4:

Score: Score module is used to manipulate the score scored by each player.

Result: Result module is used to display the result of each and        every game.

Input: score/result

Process definition: score/result of the game will be generated

Output: score is generated and the result of the user will be defined                                        

Functional component 5:

 Alert: This module is used to send the alerts to the player about his achievements.

Input: Item code and item name and Quantity

Process Definition: high score will be generated

Output: User who scored highest score will be sent a sms alert.

Download System Design Documentation:

The post Chennemane Game system design appeared first on Free Student Projects.

This page contains Chenne Mane Game Detailed design. Detailed Design is the second level of the design process. Detailed design essentially expands the system design and the database design to connect a more detailed description of the processing logic and data structure so that the design is sufficiently for coding.

The software package contain of following functional components

• Functional component 1:Login
• Functional component 2:Player selection
• Functional component 3:Game selection
• Functional component 4:Score/result
• Functional component 5:Alert

Main page

Description- This page is the home page which includes the options for the players to select the mode of game (LAN or Single), learn the game, view the rules and regulations about the game.

 If has selected the mode of game as Single end, then he can directly start playing the game on the next form. But if he selects the other option i.e.; LAN, he has to register (for new player) and then sign in to play the game with another player through Local Area Network.

Sign-in page

Description- this page allows the players to log in to play the game (if the role is selected as ‘user’). If the role is selected as admin, then he has to enter the keyword to identify the admin power. If a new player wants to register, he can click the link available below the role combo box.

Register page

Description- Here a new player can register by entering his details. This data will be stored in the database. After this, he has to sign in to on the previous page to play the game.

Forgot password

Description- If a user forges his password, he has to click the ‘forgot password’ button. In this, he has to enter his user name. After this, a SMS is sent to his cell phone which displays his password.

Selection page

Description- When a player logs in, he has to select the opponent player from the list which contains the players who have logged in through LAN. By clicking against to their names, a message will be sent to them. If they accept, the real mode (playing mode) will start.

Play page (LAN)

Description- This page provides the two logged in players to play against each other. Player 1 will be the one who sends the request to another player. And the one who accepts the invitation will be the second player. The game will end at the end of three rounds. The player who conquers more number of seeds will be declared as the winner. The score and result of every match will be stored on the database. When a player creates a record of highest scorer, a SMS alert will be sent to the one whose record had beaten. This will force him to play again and re-conquer his high scoring position.

Play page (single end)

Description- This works similar to the above page, but one will not have to log in to play on single end mode. The match begins when two players enter their names on the textboxes. Then the match will be carried out on three rounds. This provides the way to play on one system, without the aid of the LAN.

Download complete Chenne Mane Game Detailed design

The post Chenne Mane Game Detailed design appeared first on Free Student Projects.

The Travel Management System is a software application developed using C#.net Language. This project is using to book Air ticket, Flight ticket and Bus tickets. It contains Travel module, Payment module, Traveler and Employee module, Accounting and Report module. This is simple project coding and very easy to use.

Front End: C#.NET

Back End: SQL Server 2005

Download Travel Management System:

The post Travel Management System appeared first on Free Student Projects.

This main objective of the Hospital Management System is to computerize the maintenance of the patient details and billing section in the hospital. This system has been developed to form whole management system including Employees, Doctors, Nurses, Patients, Bills, and Complains etc. It also includes the details about the laboratory checkups.

LANGUAGE AND SOFTWARE TOOL USED:

Front End: Java

Operating System: Windows XP

Back End: SQL SERVER 2005

STRUCTURE OF THE PROJECT:

Proposed System:-

In the proposed system, the administrator can insert, delete and modify the patient records as per the requirements. The laboratory reports and billing details can be easily maintained in this system. This project will help to smoother the process of the hospital activities.

Module Description

Administration Module:-

This is the main module in the proposed project. The administrator can read and write information about any member such as patient, doctors and staff of the hospital. They can also update, create and delete the record of members as requirement and implementation plan.

Patient Module:-

This module contains the patient records. The sub modules are

Inpatient:-

It contains details of patients who are admitted.

Outpatient:-

The outpatient module contains details of the patient who came for checkups.

Lab Module:-

Lab module is used to generate laboratory reports.

Billing Module:-

The bill payment report of the patient.

FUTURE SCOPE OF THE PROJECT

This project will enhance the patients and the hospital to serve more quickly and efficiently. This software is developed in order to computerize the activities which take more time, if done manually.

Hospital billing system will enable the patient and hospital staff to make things faster and can get information quickly. If we want any information about patient, we can access it quickly.

HARDWARE REQUIREMENT

OS-Windows

Hard Disk-80 GB

RAM-1 GB

SOFTWARE REQUIREMENT

Java language

Net Beans IDE 6.9.1

SQL server 2005.

Find the below web page to download JAVA based Hospital Management System

Project reports:

Download Hospital management System project Synopsis:

SRS documentation for Hospital Management System

System analysis design hospital management system

The post Hospital Management System in JAVA appeared first on Free Student Projects.