You are on page 1of 60

A Project Report on

CYBERTEL SOFTWARE LIMITED
Submitted in partial fulfillment of the requirements for the award of degree of BACHELOR OF TECHNOLOGY IN INFORMATION TECHNOLOGY By ABHISHEK BHARDWAJ D.NASARA REDDY H.N BHADRI NATH N.UDAY T. SAI KIRAN 08C91A1202 08C91A1220 08C91A1223 08C91A1233 08C91A1250

Under the Esteemed Guidance of

MR.B.NARSIMHA Asst. Professor

DEPARTMENT OF INFORMATION TECHNOLOGY HOLYMARY INSTITUTE OF TECHNOLOGY AND SCIENCE
(Approved by AICTE New Delhi, Affiliated to jntu, Hyderabad) BOGARAM (V), KEESARA (M), RR DISTRICT-501301 2011-12

HOLY MARY INSTITUTE OF TECHNOLOGY & SCIENCE
(COLLEGE OF ENGINEERING) (HOLY TRINITY EDUCATIONAL SOCIETY) (Approved by A.I.C.T.E., New Delhi, Affiliated to JNTU, Hyderabad) Bogaram (Village), Keesara (Mandal), R.R.Dist. Pin – 501 301.
Phones: 08415 – 325953, 08415 – 325958, 08415 – 329583 FAX: 040 – 23813102

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that the project entitled ―CYBERTEL SOFTWARE LIMITED‖ is being submitted BY ABHISHEK BHARDWAJ (08C91A1202), D.NASARA REDDY

(08C91A1202), H.N BHADRI NATH (08C91A1223), N.UDAY (08C91A1233), T.SAI KIRAN (08C91A1250) in the partial fulfillment for the award of the Bachelor of Technology in Information Technology to Jawaharlal Nehru Technological University is a record if Bonafide work carried out by them.

INTERNAL GUIDE

HEAD OF DEPT

MR.B.NARSIMHA Asst. Professor

Prof. V.KRISHNA

EXTERNAL EXAMINER

ACKNOWLEDGEMENT

An endeavor of a long period can be successful only with the advice of many well wishers. We take this opportunity to express my deep gratitude and appreciation to all those who encouraged me for successfully completion of the project work. We wish to express my sincere gratitude to Dr.N.Subhash Chandra, Principal of Holy mary Institute of Technology and Sciences, Bogaram for his consistent help and encouragement to complete the project work. Our special thanks to Prof. V.Krishna, Head of information technology Department, for his timely suggestions and help during the progress of project work inspite of his busy schedule. We are thankful to my Guide Sri. B. narasimha, Assistant Professor in IT. Department, Holy Mary Institute of Technology and Science for his valuable guidance and suggestions in analyzing and testing throughout the period till the end of project work completion. Finally, we would like to express my sincere thanks to faculty members of IT department, batch-mates, friends, and lab technicians, one and all who have helped me to complete the project work successfully. As a gesture of respect for my family members and for the support we received from them we are dedicating this work to them.

By ABHISHEK BHARDWAJ (08C91A1202) D.NASARA REDDY (08C91A1220) H.N BHADRI NATH (08C91A1223) N.UDAY (08C91A1233) T.SAI KIRAN (08C91A1250)

CONTENTS
CHAPTER Page Number

Abstract……………………………………………………………..…i List of figures………………………………………………………….ii List of tables…………………………………………………………...iii List of screens…………………………………………………………..iv 1. INTRODUCTION…………………………………………………. 1 1.1 Motivation ………………………………………………………1 1.2 Problem definition……………………………………………....1 1.3 Objective of Project……………………………………………. 1 1.4 Limitations of Project………………………………………….. 2 2. LITERATURE SURVEY…………………………………………..3 2.1 Introduction……………………………………………………..3 2.2 Existing System……………………………………………….. .3 2.3 Proposed System………………………………………………. 3 2.4 Features of the project…………………………………………. 4 3. ANALYSIS………………………………………………………… 5 3.1 Introduction……………………………………………………. 5 3.2 Requirement Specification…………………………………….. 9 3.2.1 User requirement……………………………………….. 10 3.2.1.1 Functional requirements………………………....10 3.2.1.2 Non-functional requirements…………………... 13 3.3 Context diagrams ……………………………………………... 15 4. DESIGN…………………………………………………………… 16 4.1 Introduction……………………………………………………. 16 4.1.1 Object Oriented System………………………………... 16 4.1.2 Object Oriented Analysis……………………………… 17 4.1.3 Object Oriented Design……………………………….. 11 4.2 UML diagrams………………………………………………… 18 4.2.1 Class…………………………………………………… 18 4.2.2 Use case……………………………………………….. 20 4.2.3 Sequence………………………………………………. 22 4.2.4 Collaboration………………………………………….. 24 4.3 Module Design and Organization…………………………….. 25 4.4 Tables………………………………………………………….. 27

5. IMPLEMENTATION……………………………………………… 32 5.1 Introduction……………………………………………………. 32 5.2 Key Function…………………………………………………… 32 5.3 Method of Implementation…………………………………….. 34 5.3.1 Output Screen………………………………………….. 36 5.4 Technical Specification………………………………………….42 6. TESTING, VALIDATION AND RESULTS……………………… 45 6.1 Introduction……………………………………………………. 45 6.2 Testing Methodologies………………………………………… 45 6.3 Design For Test Case and Scenario……………………………. 47 6.4 Validation………………………………………………………. 48 6.5 Test Cases……………………………………………………… 49 7. CONCLUSION……………………………………………………. 50 7.1 Conclusion…………………………………………………….. 50 7.2 Future Enhancement…………………………………………… 50 8. BIBLIOGRAPHY…………………………………………………. 51

ABSTRACT
This Software project is aimed at automation of process of training Institute. The Objective of the project is to develop customized software package for IT / Non-IT Training Institutes. This technology enables the management feel easy in maintaining their daily operations effectively and instantly. And at the same time students who are enrolled for various courses, they can get instant response for their queries. And also it takes care of Employees pay roll and Students fee payments. And it also helps the Marketing Executives/ Counselors by getting each day‘s follow-ups to the desktop. Institutes will be offering different courses with different durations. There will be employees working in the institute with different designations. There will be students undergoing training in different courses. The current project is to automate the overall institute management. This also can be used to process the pay roll of the employees. And at the same time if any user who want to know about last year placement detail course detail, faculty detail, course duration, fee, batch timing. The user can get the all information through particular web site. And also it takes care of Employees pay roll and student fee payment. And it also helps the Marketing Executives Counselors by getting each day‘s followups to the desktop

i

List Of figures

Figures

Page Number

1. Class Diagram ………………………………………………………18 2. Use Case Diagram…………………………………………………...20 3. Sequence Diagram…………………………………………..……….22 4. Collaboration Diagram………………………………………………24

ii

List of Tables

Tables

Page Number
38 39 40 41 42

1. Course.......................................................................................... 2. Faculty......................................................................................... 3. Placement.................................................................................... 4. Feed Back.................................................................................... 5. Contact............................................................................…………..

iii

List of Screens

Screens

Page Number

1. Main Page………………………………………………………….. 62 2. Available Course…………………………………………………… 63 3. Contact…………………………………………………………….. 64 4. Admin Home……………………………………………………….. 65 5. Delete Faculty……………………………………………………… 66

iv

1. INTRODUCTION
1.1 MOTIVATION
CYBERTEL Software Limited (CTSL) is an IT Solution Provider for a dynamic environment where business and technology strategies converge. Our approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organization's current IT assets. We work with large global corporations and new generation technology companies - to build new products or services and to implement prudent business and technology strategies in today's environment.

1.2 PROBLEM DEFINITION
Cybertel range of expertise includes:  Software Development Services  Engineering Services  Systems Integration  Customer Relationship Management  Supply Chain Management  Product Development  Electronic Commerce  Consulting  IT Outsourcing

1.3 OBJECTIVE OF THE PROJECT
We apply technology with innovation and responsibility to achieve two broad objectives.  Effectively address the business issues our customers face today

1

 Generate new opportunities that will help them stay ahead in the future

This approach rests on:

 A strategy where we Architect, Integrate and Manage technology services and
solutions — we call it AIM for success.  A robust offshore development methodology and reduced demand on customer resources  A focus on the use of reusable frameworks to provide cost and time benefits We combine the best people, processes and technology to achieve excellent results consistently.

1.4 ORGANISATION OF DOCUMENTATION
In this project documentation we have initially put the definition and objective of the project as well as the design of the project which is followed by the implementation and testing phases. Finally the project has been concluded successfully and also the future enhancements of the project were given in this documentation.

2

2. LITERATION SURVEY
2.1 INTRODUCTION
Software Limited (CTSL) is an IT Solution Provider for a dynamic environment where business and technology strategies converge. Our approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organization's current IT assets.

2.2 EXISTING SYSTEM
 The Administrator should be able to add/modify/delete the details of courses and their fees structures.  Counselors should be able to maintain each day‘s enquiries about various courses.  They should be able to get each day‘s follow-ups.

2.3 PROPOSED SYSTEM
 The aim of this system is to take care of Faculties and their Batch details.  The Administrator should be able to add/modify/delete the placement detail of the student and their minimum and maximum package according to their course for every year.  The user should be able to give his feedback about institution.  The administrator should also be able to see the feedback of the user.  The user can get the information about placement, faculty, course duration and batch time

3

2.4 FEATURES OF THE PROJECT
Speed: We understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps in jump-start projects. Tried and tested methodology ensures that we follow a predictable, low-risk path to achieve results. Our track record is testimony to complex projects delivered within and even before schedule Expertise: Our teams combine cutting edge technology skills with rich domain expertise. What's equally important — we share a strong customer orientation that means we actually start by listening to the customer. We're focused on coming up with solutions that serve customer requirements today and anticipate future needs. A Full Service Portfolio: We offer customers the advantage of being able to Architect, Integrate and Manage technology services. This means that they can rely on one, fully accountable source instead of trying to integrate disparate multi-vendor solutions.

4

3. ANALYSIS
3.1 INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking as well as understanding of existing system is also difficult. Improper understanding of present system can lead diversion from solution. Analysis Model The model that is basically being followed is WATER FALL Model which states that the phases are organized in a linear order. First of all, the feasibility study is done. Once that part is over, the requirement analysis and project planning begins. If system exists as a whole but modification and addition of new module is needed, analysis of present system can be used as basic model. The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are:  Requirement Analysis  Project Planning  System Design  Detail Design  Coding  Unit Testing  System Integration & Testing

Here the linear ordering of these activities is critical. At the end of the phase, the output of one phase is the input to other phase. The output of each phase should be consistent with the overall requirement of the system. Some of the qualities of spiral model are also incorporated
5

like after the people concerned with the project review completion of each of the phase the work done. WATER FALL Model has been chosen because all requirements were known before and the objective of our software development is the computerization/automation of an already existing manual working system.

6

Study of the system GUI‘S For flexibility, the User Interface has been developed with a graphics concept in Mind, Associated through a browser interface. The GUI‘S at the top level have been categorized as:  Administrative User Interface.  The Operational/Generic User Interface.

The ―Administrative User Interface‖ concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. This interface helps the administration with all the transactional states like Data Insertion, Data Deletion and Data Updating along with the extensive Data Search capabilities. The ―Operational/Generic User Interface‖ helps the users upon the system in transactions through the existing data and required services. The Operational User Interface also helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities. Project Instructions Based on the given requirements, conceptualize the Solution Architecture. Choose the domain of your interest otherwise develop the application for ultimatedotnet.com. Depict the various architectural components, show interactions and connectedness and show internal and external elements. Design the web services, web methods and database infrastructure needed both and client and server. Provide an environment for up gradation of application for newer versions that are available in the same domain as web service. Feasibility Report Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:  Technical Feasibility
7

 Operation Feasibility  Economical Feasibility

Technical Feasibility The technical issue usually raised during the feasibility stage of the investigation includes the following:  Does the necessary technology exist to do what is suggested?  Do the proposed equipments have the technical capacity to hold the data required  To use the new system?  Will the proposed system provide adequate response to inquiries, regardless of the  Number or location of users?  Can the system be upgraded if developed?  Are there technical guarantees of accuracy, reliability, ease of access and data  Security?

Earlier no system existed to cater to the needs of ‗Secure Infrastructure Implementation System. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The database‘s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.

8

Operational Feasibility Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization‘s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following:  Is there sufficient support for the management from the users?  Will the system be used and work properly if it is being developed and implemented?  Will there be any resistance from the user that will undermine the possible application Benefits? This system is targeted to be in accordance with the above-mentioned issues. The wellplanned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status. Economic Feasibility A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain.

3.2 SOFTWARE REQUIREMENT SPECIFICATION
Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the
9

basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. The developer is responsible for:  Developing the system, which meets the SRS and solving all the requirements of the system?  Demonstrating the system and installing the system at client's location after the  Acceptance testing is successful.  Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.  Conducting any user training that might be needed for using the system.  Maintaining the system for a period of one year after installation.

3.2.1 User Requirements  User name and Password for the website for the purpose of Job Search  Administrator.  Internet connection

3.2.1.1 Functional Requirements Output Design Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs in general are:  External Outputs whose destination is outside the organization.  Internal Outputs whose destination is within organization and they are the user‘s main interface with the computer.  Operational outputs whose use is purely within the computer department.  Interface outputs, which involve the user in communicating directly with system.

10

Output Definition The outputs should be defined in terms of the following points:  Type of the output.  Content of the output.  Format of the output.  Location of the output.  Frequency of the output.  Volume of the output.  Sequence of the output. It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable. For Example  Will decimal points need to be inserted  Should leading zeros be suppressed. Output Media In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:  The suitability for the device to the particular application.  The need for a hard copy.  The response time required.  The location of the users  The software and hardware available. Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are: The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.

11

Input Design Input design is a part of overall system design. The main objective during the input design is as given below:  To produce a cost-effective method of input.  To achieve the highest possible level of accuracy.  To ensure that the input is acceptable and understood by the user. Input Stages The main input stages can be listed as below:  Data recording  Data transcription  Data conversion  Data verification  Data control  Data transmission  Data validation  Data correction Input Types It is necessary to determine the various types of inputs. Inputs can be categorized as follows:  External inputs, which are prime inputs for the system.  Internal inputs, which are user communications with the system.  Operational, which are computer department‘s communications to the system?  Interactive, which are inputs entered during a dialogue. Input Media At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to:  Type of input  Flexibility of format  Speed
12

 Accuracy  Verification methods  Rejection rates  Ease of correction  Storage and handling requirements  Security  Easy to use  Portability Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive. As Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device. Error Avoidance At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled. Error Detection Even though every effort is make to avoid the occurrence of errors, still a small Proportion of errors is always likely to occur; these types of errors can be discovered by Using validations to check the input data. Data Validation Procedures are designed to detect errors in data at a lower level of detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data. Whenever an invalid data is keyed in, the system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct. Validations have been included where necessary. The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user. The system has been designed with popup menus.

3.2.1.2Non-Functional Requirements Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement
13

specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use. The requirement specification for any system can be broadly stated as given below:  The system should be able to interface with the existing system  The system should be accurate  The system should be better than the existing system

14

3.3 CONTEXT DIAGRAMS

Faculty details

Placement details follow
Course offered

context

Faculty details Admin

Admin module

Placement Follow details details Specific Follow Person details user number

Company Name package Course details enquiry Enquiry details course Enquiry details

Course/ placement details

Institution details

15

4. DESIGN
4.1 INTRODUCTION
Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects. Each object represents some entity of interest in the system being modeled, and is characterized by its class, its state (data elements), and its behavior. Various models can be created to show the static structure, dynamic behavior, and runtime deployment of these collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling Language (UML). Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD on how the system does it. Object-oriented system is an composed of objects. The behavior of the system results from the collaboration of those objects. Collaboration between objects involves those sending messages to each other. Sending a message differs from calling a function in that when a target object receives a message, it itself decides what function to carry out to service that message. The same message may be implemented by many different functions, the one selected depending on the state of the target object. The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the objects being communicated with. 4.1.1 Object Oriented Systems: An object-oriented system is composed of objects. The behavior of the system is achieved through collaboration between these objects, and the state of the system is the combined state of all the objects in it. Collaboration between objects involves those sending messages to each other. The exact semantics of message sending between objects varies depending on what kind of system is being modeled. In some systems, "sending a message" is the same as "invoking a method". In other systems, "sending a message" might involve sending data via a socket.
16

4.1.2. Object-Oriented Analysis: Object-oriented analysis (OOA) looks at the problem domain, with the aim of producing a conceptual model of the information that exists in the area being analyzed. Analysis models do not consider any implementation constraints that might exist, such as concurrency, distribution, persistence, or how the system is to be built. Implementation constraints are dealt with during object-oriented design (OOD). Analysis is done before the Design. The sources for the analysis can be a written requirements statement, a formal vision document, and interviews with stakeholders or other interested parties. A system may be divided into multiple domains, representing different business, technological, or other areas of interest, each of which are analyzed separately. The result of object-oriented analysis is a description of what the system is functionally required to do, in the form of a conceptual model. That will typically be presented as a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also include some kind of user interface mock-up. 4.1.3. Object Oriented Design: Object-Oriented Design (OOD) is an activity where the designers are looking for logical solutions to solve a problem, using objects. Object-oriented design takes the conceptual model that is the result of object-oriented analysis, and adds implementation constraints imposed by the environment, the programming language and the chosen tools, as well as architectural assumptions chosen as basis of design. The concepts in the conceptual model are mapped to concrete classes, to abstract interfaces in APIs and to roles that the objects take in various situations. The interfaces and their implementations for stable concepts can be made available as reusable services. Concepts identified as unstable in object-oriented analysis will form basis for policy classes that make decisions, implement environment-specific or situation specific logic or algorithms. The result of the object-oriented design is a detail description how the system can be built, using objects.

17

4.2 UML:
The Unified Modeling Language (UML) is a standardized specification language for object modeling. UML is a general-purpose modeling language that includes a graphical notation used to create an abstract model of a system, referred to as a UML model. 4.2.1 Class Diagram 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, and the relationships between the classes. It is the main building block in object oriented modeling. It is being used both for general conceptual modeling of the systematic of the application, and for detailed modeling translating the models into programming code. The classes in a class diagram represent both the main objects and interactions in the application and the objects to be programmed. In the class diagram these classes are represented with boxes which contain three parts:  The upper part holds the name of the class.  The middle part contains the attributes of the class, and  The bottom part gives the methods or operations the class can take. In the conceptual design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the statically relations between those objects. With detailed modeling, the classes of the conceptual design are often split in a number of subclasses.

18

19

4.2.2 Use case Diagram A Use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are Performed for which actor. Roles of the actors in the system can be depicted. Actors: An actor portrays any entity (or entities) that perform certain roles in a given system. The different roles the actor represents are the actual business roles of users in a given system.

20

open

course

faculty details user

placement details

feed back

contact

home

update course/faculty details

update placem ent Admin

view/check feedback

login logout

21

4.2.3 Sequence Diagram A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner. Object: A concrete manifestation of abstraction; an instance of a class.

22

user

home

admin

open

login

open course details

open faculty details modify faculty & course details

open placement details

modify placement deatils

send feedback view/check feed back

view contact

logout

close

23

4.2.4 Collaboration Diagram A Collaboration Diagram is an interaction Diagram that emphasizes the structural organization of the objects that send and receive messages. It shows a set of objects, links among those objects and messages sent & received by those objects.

1: open 3: open cours e details 4: open faculty details 6: open placem ent details 8: s end feedback 10: view contact 12: clos e us er home

2: login 5: modify faculty & cours e details 7: modify placem ent deatils 9: view/check feed back 11: logout

admin

24

4.3 MODULES DESIGN AND ORGANIZATION
1. User Module 2. Admin Module

User Module
In this module there are 5 sub modules that are Available Course  Faculty  Placement  Feed Back  Contact

Available Course In this module user can able to see details of the entire available course. Faculty In this module user can able to see details of the faculty.

Feed Back The module allows you to create and conduct surveys to collect feedback. Unlike the Survey tool it allows you to write your own questions, rather than choose from a list of prewritten questions and unlike the Quiz tool, you can create non-graded questions. The Feedback activity is ideal for the likes of course or teacher evaluations.

Admin Module
In this module there are 5 sub modules that are  View Feed Back  View User Profile  Delete User
25

View Feed Back In this module admin can able to view the feedback given by the user and according to the user requirement admin can change the modifications. View User Profile In this module admin can able to see the details of the user which are displayed and admin can‘t edit the details, and admin will match the user profile with the job openings. Delete User In this module admin can delete the user who are not accessing site for long time.

26

4.4 DATA BASE TABLES Course Table

Name CID CNAME

Type NUMBER(5)

Constraint Primary Key

VARCHAR2(15) Represents the name of the course NUMBER(6) Total fee

TOTFEE DURATION

VARCHAR2(10) Duration Of Course

LANGUAGE

NUMBER(6)

Language

27

Faculty Table

Name
FID FNAME

Type
NUMBER(5) VARCHAR2(15)

Constraint
Primary Key Represents the name of the faculty Basic salary Designation Address of faculty

BASIC DESIGNATION ADDRESS

NUMBER(6) VARCHAR2(15) VARCHAR2 (6)

28

Placement Table
Name CID CNAME Type NUMBER(5) VARCHAR2(15) Constraint Primary Key Represents the name of the faculty Basic salary

Years

NUMBER(6)

NO.OF SELECTION Language MIN package Max package

VARCHAR2(15) Varchar(6) Number(5) Number(5)

Designation Address of faculty salary salary

29

Feed Back Table

Name
Fname LNAME

Type
varchar5)

Constraint
Primary Key

VARCHAR2(15) Represents the name of the course varchar(6) number(10) varchar(6) Total fee Duration Of Course Language

Email Phone no Post comment

30

Contact table

Name name Designation

Type Varchar(5)

Constraint Primary Key

VARCHAR2(15) Represents the name of the course varchar(6) number(10) varchar(6) Total fee Duration Of Course Language

Email Phone no fax

31

5. IMPLEMENTATION AND RESULTS
5.1 INTRODUCTION
The implementation part is the most important phase of the project. In this phase, we code the entire project in the chosen software according to the design laid during the previous phase. The code has to be in such a way that the user requirements are satisfied and also not complicated for the user i.e., the user interface or GUI has to be easy to navigate. The code should be efficient in all terms like space, easy to update, etc. In this manner, we can complete the coding part of the project and later it can be sent for testing before being delivered to the customer.

5.2 EXPLANATION OF KEY FUNCTIONS
Database Connectivity using jdbc The following code gives the database connectivity using jdbc i.e., the way the My SQL database is synchronized with the project which is developed using Java. Sample Coding For Data Base Connection <%@page contentType="text/html" pageEncoding="UTF-8"%> <! DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title>

</head>
32

<body> <%@include file="Db_Conn.jsp" %> <% String Cid=request.getParameter("cid"); String Cname=request.getParameter("Cname"); String Years=request.getParameter("years"); String Noofselection=request.getParameter("noselection"); String Language=request.getParameter("languge"); String Minpackage=request.getParameter("minpackage"); String Maxpackage=request.getParameter("maxpackage"); int b = Integer.parseInt(Minpackage); int m = Integer.parseInt(Maxpackage); int no = Integer.parseInt(Noofselection); String s = "update placement set CNAME='"+Cname+"',YEARS='"+Years+"',NO_OF_SELECTION="+no+",LANGUA GE='"+Language+"',MIN_PACKAGE="+b+",MAX_PACKAGE="+m+" where CID='"+Cid+"'"; int k = stmt.executeUpdate(s); if(k >0){ out.println("Update Successfully"); } else{ out.println("Update Fail"); } </body> </html>
33

%>

5.3 METHOD OF IMPLEMENTATION
Installing Software First of all install Java 1.6 and then Tomcat Apache 5.1 by specifying port number as 8080. After that install oracle database in your system. After installing oracle, you can install an IDE like Net Beans ECLIPSE or an Edit Plus editor to write Java programs (optional). You can even write them in notepad also. Enable Path Settings Now the path settings have to be enabled so that your system will be able to recognize the above installed software‘s. Note that correct path have to be given otherwise it may raise an error. The following picture depicts the method of setting path:

(Right click on My Computer)

(Select Advanced tab and Environment variables)

34

(Setting User Variables)

(Setting System Variables)

35

5.3.1 Output Screen Main Page

36

Available Course

37

Contact

38

Admin Home

39

Add Faculty

40

Delete Faculty

41

5.4 TECHNOLOGY SPECIFICATION
One of the most difficult tasks is that, the selection of the software, once system requirement is known is determining whether a particular software package fits the requirements. After initial selection further security is needed to determine the desirability of particular software compared with other candidates. Initially the language was called as ―oak‖ but it was renamed as ―Java‖ in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices.  Java is a programmer‘s language.  Java is cohesive and consistent.  Except for those constraints imposed by the Internet environment, Java gives the programmer, full control.  Finally, Java is to Internet programming where C was to system programming. Java Virtual Machine (JVM) Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code that‘s has been generated by the compiler will not corrupt the machine that it‘s loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code.

42

JAVA SERVER PAGES Introduction: Jsp technology enables you to mix regular static html with dynamically generated content from servlets. Separating the static html from the dynamic content provides a number of benefits over servlets alone. Why use Jsp: Jsp is easy to learn and allows developers to quickly produce wed sites and application in an open and standard way. Jsp is based on java, an object-oriented language. Jsp offers a robust platform for web development. Java Data Base Connectivity (JDBC) “Most of the web based application programs need to interact with database management systems (DBMS). These DBMSs are repositionaries of the information used by applications.” Database Management: A database is a collection of related information and a DBMS is software that provides you with a mechanism to retrieve, modify, and add data to the database. Database Connectivity: For an application to communicate with the database, it needs to have the following information:  The RDBMS/DBMS product using which the database is created.  The location of the database.  The name of the database.

43

JDBC API: JDBC provides a database-programming API for Java programs. Java Soft created the JDBCODBC bridge driver that translates the JDBC API to the ODBC API. It is used with ODBC drivers. JDBC Driver Manager: The JDBC driver manager is the backbone of JDBC architecture. Its function is to connect a Java application to the appropriate driver specified in the Java program. JDBC-ODBC Bridge: As a part of JDBC, Sun Microsystems provides a driver to access ODBC data sources from JDBC. This driver is called the JDBC-ODBC Bridge. Connecting To a Database: The java.sql package contains classes that help in connecting to a database, sending embedded SQL statements to the database, and processing query results. The connection Object: The connection object represents a connection with a database. To establish a connection with a database, you need to register the ODBC-JDBC driver by calling the for Name () method from the Class and then calling the get Connection () method from the Driver Manager class. ABOUT ORACLE DATABASE A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, and Oracle. These systems allow users to create, update and extract information from their database.

44

6. TESTING AND VALIDATION
6.1 INTRODUCTION
Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. In fact, testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. A strategy for software testing integrates software test case design methods into a wellplanned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small-scale systems. The following are the Testing Objectives:  Testing is a process of executing a program with the intent of finding an error.  A good test has a high probability of finding an as yet undiscovered error.  A successful test is one that uncovers an as yet undiscovered error.

6.2 TESTING METHODOLOGIES
There are two test case design methods. They are:
 Black Box Testing  White Box Testing

Black Box Testing Knowing the specified function that a system has been designed to perform, tests can be conducted that demonstrates each function is fully operational, at the same time searching for errors in each function. Block-box testing is not an alternative to white-box testing. Rather, it is complimentary approach that is likely to uncover a different class of errors than white-box testing.
45

Black-box testing attempts to find errors in the following categories: 1. Incorrect missing function. 2. Interface errors 3. Errors in data structures or external data base access 4. Performance errors, Initialization and Termination errors. Unlike white-box testing, which is performed early in the testing process, black-box testing tends to be applied during later stages of testing. Because black-box testing purposely disregards control structure, attention focused on the information domain.

White Box Testing White box testing, sometimes called glass-box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Using white box testing methods, the software engineer can derive test cases that 1. Guarantee that all independent paths with in a module have been exercised at least once. 2. Exercise all logical decisions on their true and false sides. 3. Execute all loops at their boundaries and within their operational bounds. Logical errors and incorrect assumptions are inversely proportional to the probability that a program path will be executed. Errors tend to creep into our work when we design and implement function, conditions or control that is out of main stream. Every day processing tends to be well understood while ―special case‖ processing tends to fall into the cracks.

.

46

6.3 DESIGN OF TEST CASES & SCENARIO
The objective is to design tests that systematically uncover different classes of errors and do so with a minimum amount of time and effort. Testing cannot show the absence of defects, it can only show that software defects are present. Unit Testing  Interface  Number of input parameters should be equal to number of arguments.  Parameter and argument attributes must match.  Parameters passed should be in correct order.  Global variable definitions consistent across module. If module does I/O  Open/Close statements must be correct  Buffer Size should match record size.  Files should be opened before use.  End of file condition should be handled.  I/O errors should be handled.  Any textual errors in output information must be checked. Error noted does not correspond to error encountered.  Error condition handled by system run-time before error handler gets Control.  Exception condition processing incorrect.

Integration Testing Modules integrated by moving down the program design hierarchy. Can use depth first or breadth first top down integration verifies major control and decision points early in design process. Top-level structure tested most. Depth first implementation allows a complete function to be implemented, tested and demonstrated and does depth first implementation of critical functions early. Top down integration forced (to some extent) by some development tools in programs with graphical user interfaces.
47

6.4 VALIDATION TESTING
Validation testing is aims to demonstrate that the software functions in a manner that can be reasonably expected by the customer. This tests conformance the software to the Software Requirements Specification.

Validation Test Criteria A set of black box test is to demonstrate conformance with requirements. To check that all functional requirements satisfied, all performance requirements achieved, documentation is correct and ' human-engineered', and other requirements are met (e.g. compatibility, error recovery, and maintainability). When validation tests fail it may be too late to correct the error prior to scheduled delivery. Need to negotiate a method of resolving deficiencies with the customer. Configuration Review An audit to ensure that all elements of the software configuration are properly developed catalogued and has all the necessary detail to support maintenance. System Testing: System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to verify that all system elements have been properly integrated to perform allocated functions. Security Testing: Attempts to verify the protection mechanisms built into the system. Performance Testing: This method is designed to test runtime performance of software within the context of an integrated system.

48

6.5 TEST CASES
Test Case Name Check Services Test Procedure Pre Conditio n Expected Result Outpu t(resul t) Succes s Specificatio n document Check\ Services

Sl. no 1.

Enter the url of cybertel software limited Select available course

Display User home page

2.

Check Services

-

Display view file page

Succes s

Check\ Services

3

Check Services

Select faculty details

-

Display faculty details

Succes s

Check\ Services

4

Check Services

Select placement details

-

Display placement details

Succes s

Check\ Services

5

Check Services

Select feedback file

User must enter details before give feed back

Display View File Succes page s

Check Services

6

Login perform

Enter the Admin no and password and click submit button Add, Delete, Edit placement details Admin must be logged in

Display Admin home page

Succes s

Test Login

7

Check Services

Query message is File inserted successfully

Succes

Query insertion

49

7. CONCLUSION
7.1 CONCLUSIONS
The “INSTITUTE MANAGEMENT” has been successfully completed. The goal of the system is achieved and problems are solved. Final reports are generated as per the specification of the client. The package is developed in a manner that it is user friendly and required help is provided at different levels. The project can be easily used in the process of decision making. Different types of reports can be generated which help the management to take correct decision and reduce the time delay which automatically increases the company‘s work standards as well as the economical state of the company. This system never decreases the manpower but helps the development of available manpower and optimizes the manpower by which company‘s standards and capabilities can be scaled to higher dimensions.

7.2 FURTHER ENHANCEMENTS
We can also add a new Sub module i.e. Registration, the user can directly login and ask Queries to the Faculty. User can also get the job information according to his course.. The user can also get the guide line from Faculty about his particular subject.

50

8. BIBLIOGRAPHY
References:The following books were referred during the analysis and execution phase of the project ORACLE 8 THE COMPLETE REFERENCE By Oracle Press SOFTWARE ENGINEERING By Roger.S.Pressman SQL FOR PROFESSIONALS By Jain CORE JAVA 2 (VOL 1 and VOL 2) By Cay S. Hortsman. JAVADOC By Sun Microsystems.

51