CAEHS WEBSITE

1. INTRODUCTION

CAEHS WEBSITE

1. INTRODUCTION
1.1 Project Summary
CAEHS Website is the web based and LAN based product which being created in Visual Basic Technology. This project is targeted to college Information the college modules from any place through online or within college and make the system transparent.

Internet has been for a long time, favored and accepted as a simple yet effective tool to reach out to people across the globe. CAEHS Website uses the same approach to fulfill its intentions.

Basically, we have developed this project for our college, which will be used for intranet as well as on internet initially and after than it can be completely hosted on internet. CAEHS Website project will become very useful for the college to avoid very tedious, time consuming paper work and maintain history more efficiently. The web application offers a distinguishing factor from many others, an amenity that just sets the purpose right. The main intention of the system is to automate the functionalities that at present are done manually at the college.

1.2 Major Activities

This system concentrates on the following agendas:

Registration of a new Student or Faculty.

This module will help to bind all the records of different student and employees of the college.

College Education Forum.

CAEHS WEBSITE This web module is basically used to share the information and frequently ask question within college environment.

CAEHS WEBSITE

1.3 Purpose of the Project

Goals and Objectives of the project

Purpose of CAEHS Website is to manage the college resources more efficiently.

CAEHS Website web and LAN base application for college staff and student to use various functionality with optimum use of resources.

As name suggest College Resource is contain various functionality that handled by paper work as now some of them been implemented in our project by us.

Provides fast and efficient way to store and search the data.

Subject wise average attendance can be generated by filtering the date range and also can have hard copy of that report.

Student records can be filtered easily.

Alumni student can be grouped easily by sending mail to authorized student.

There is so many good objectives available within this project which never been realistic in past. (As per our knowledge).

CAEHS WEBSITE

1.4 Scope of the Project

Software Scope describes the data and control to be processed, function, performance, Constraints, interface and reliability. FUNCTIONS

Functions described in statement of the scope are evaluated and in some cases refined to provide more details prior to the beginning of the estimation.

PERFORMANCE

Performance consideration encompasses processing and response time consideration.

CONSTRAINTS

Constraints identify limit placed on the software by external hardware, available memory or other existing system. INTERFACE

Interface includes the hardware that executes the software, software that already exists, people that make use of the software and procedures that precede or succeed the software as sequential series of operation. RELIABILITY

CAEHS WEBSITE It measures at how many point the system fails. The lesser the failure, the more is the reliable system. The system we have built is suitable for todays fast life as people dont get time to spend on things that are less essential.

The system built is advantageous in many ways, after studying the requirements of the system and knowing the problems faced by the user the scope of proposed system is as follows.

For the marketing of the current system company appoints the executives through the limited states. So the scope of the current system is lower and now this system become online and LAN based as well as transparent by this project so the scope of this application will be higher.

CAEHS WEBSITE

1.5 Project Deliverable (What it can do?)

It helps the student to check the attendance reports. It will also provide the student to share his/her knowledge through college educational forum.

CAEHS Website can be used by faculty by updating student attendance day by day and to remain in touch with past students through alumni module.

Attendance report is the key functionality of this project and we can generate subject wise average attendance report of any student.

The Project Deliverables are results that are delivered to the customer. Below is a list of the deliverables for this Project:

Software Requirements Specification Document Project Management Plan Design Analysis Test Plan Document Test Report Final Report

What it can't do? This project cannot generate attendance report of last semester attendance records because database would be refreshed after every semester as every semester contains approximate 50000 records in the database.

CAEHS WEBSITE

2. PROJECT PLANNING AND SCHEDULING

CAEHS WEBSITE

2. PROJECT PLANNING AND SCHEDULING

2.1Process Model
The software development model, adopted for the proposed system, is waterfall model (Iterative model).

2.1.1

Project Plan

ANALYSIS PHASE Requirement Engineering Object Modeling Dynamic Modeling Functional Modeling

DESIGN PHASE Subsystem Design Reusable Component Design Database Design UI Design Object Design Architecture & Deployment Design File System Structure Design Test Case Design

IMPLEMENTA TION PHASE Database Creation Prototype Creation UI Component Development UI Development Core class Development Remote Service Development

TESTING PHASE Unit Testing Integration Testing Test Reports

Figure 2.1 Iterative Waterfall Model

CAEHS WEBSITE Reason for choosing the Waterfall Model:

Waterfall model stipulates that the requirements should be completely specify before the rest of the system development is preceded. In the proposed system, the requirements are fixed and known beforehand and hence this model is suitable and adopted for the development of the proposed system. The systems services constraints and goals are established by consultation with system users. They are then defined in a manner is understandable by both users and developers. The system design process partitions the requirements to either hardware or software system. It establishes overall system architecture. Software design involves representing the software system functions in a form that may be transformed into one or more executable programs.

Analysis Phase

This phase involves detailed study of the system using different tools like OMT and UML. First Using conventional requirement collection and engineering technique user and system requirements are explored. This gives the very detailed knowledge of the system. OMT includes Object Modeling, Dynamic Modeling and Function Modeling. Design Phase

As conventional design method and according to OMT, as first step of design Subsystems of the system are identified. This phase also includes Architecture design, Deployment Design, File system Structure design and UI design. Implementation Phase

Implementation phase includes development of UI components, creating prototypes of each core classes, development of core classes, UI development and remote service creation.

10

CAEHS WEBSITE Testing Phase

In testing phase each method of the classes are checked during development phase as unit testing. Then each class is integrated and they are tested for integration testing. Ultimately test cases are tested to ensure that there are no bugs in the code.*/

OMT

It is primarily used by system and software developers supporting full life-cycle development, targeting object-oriented implementations. Because of its simple core notation, OMT has proven easy to understand, to draw, and to use. It continues to be successful in many application domains: telecommunication, transportation, compilers, etc. The popular Object Modeling Technique (OMT) has been used in many real-world problems.

Key Benefit:

The object-oriented paradigm using the OMT spans the entire development process, so there is no need to transform from one type of model to another.

2.2Project Plan
Months March ( 1-17 ) March (18-25) March (25-30) April (1-30) Plan Customer Communication Planning Risk Analysis Engineering Construction &

Release/Documentation May (1-15) Testing/Documentation

11

CAEHS WEBSITE May(16-31) Customer Evaluation/Documentation

2.3Schedule Representation

Project Profile Submission Evaluation

Customer Communicatio n Documentation

Analysis

Logical Design

Testing

Code Implementation

*Note: This is only a Case Study of existing project.

May(16-31) May(1-15) April(1-30) March(25-30) February(18-25) Mar-12 0 1 2 3 4 5 Work Done Work Left

Figure2.3 Schedule Representation

12

CAEHS WEBSITE

2.4 Risk Management

2.4.1 Risk Identification

Risk identification is a systematic attempt to specify threats to the projects plan by identifying known and predictable risks. Risks are about events that, when triggered, cause problem. Hence risk identification can start with the source of problems or the problem itself.

There are three main categories of risks which can affect a software project: Project Risks Technical Risks Business Risks

Project Risks:

Project risks concern various forms of budgetary, schedule, personnel, resource and customer related problems.

Miscommunication: It leads to misunderstanding, delay, frustration, lack of coordination amongst the team members and client.

Time shortage: It leads to delay in the delivery of the product.

Personal conflicts between team members: It leads to unnecessary delay in each and every phase of software cycle and loss of direction.

Illness or absence of team members: Absence of a team member increases the load of the project on other team members. 13

CAEHS WEBSITE

Lack of expertise to fulfill certain tasks: Lack of knowledge in some areas leads to insignificant delay.

Technical Advisor not available when needed: Due to the absence of a technical advisor there was a delay in understanding the database.

Unavailability of customer

Technical Risks:

Technical risks concern potential design, implementation, interfacing, and testing and maintenance problems.

Too many planned features lead to infeasible design

Design errors: Due to lack of experience design errors are bound to happen.

The customer changes the requirements: The scope of our project keeps changing as per users requirements

The customer disapproves of the prototype: The customer may find the developed prototype unsuitable to his requirements

Business Risks:

Business risks threaten the viability of the software to be built. Business risks often jeopardize the project or the product.

Market risk: Building a excellent product or system that no one really wants. 14

CAEHS WEBSITE

Strategic risk: Building a product that no longer fits into the overall business strategy for the company. Management risk: Losing the support of senior management due to a change in focus or a change in people.

Product is not put in service

2.4.2 Risk Analysis Personnel Shortfalls:

They may cause the developmental delays and would cause a change in the working strategy due to developmental dependencies of the functional modules. Unrealistic Schedule:

It may cause the developers to give unrealistic commitments to the users and so lose their faith when the deliverables are not produced as per schedule. Developing wrong Software functions:

It can be caused due to wrong requirement analysis or wrong programming method used to automate the requirements. It may cause the system to fail and not be implemented at all. Developing wrong User Interface:

It may be caused due to lack of user acceptance and user involvement during development.

15

CAEHS WEBSITE The probability of the risk might be assessed as very low (<10%), low (10-25%), moderate (20-25%), high (50-75%) or very high (>75%).

16

CAEHS WEBSITE Table 2.4.2 Risk Analysis Sr No. 1 Organizational financial problem force Low Catastrophic Risk Probability Effect

reduction in the product budget 2 3 Required knowledge is not available High Catastrophic Serious

Change to requirement which require major Moderate design of rework

Organization is restructured so that different High management are responsible for project

Serious

The time required to develop software is High underestimated

Serious

User

fail

to

understand

the

impact

of Moderate

Tolerate

requirement change 7 8 9 The rate of defect repair is underestimated The size of software is underestimated Misuse of the system Moderate High High Tolerate Tolerate Serious

2.4.3Risk Planning

Once risks have been identified and assessed, all techniques to manage the risk fall into one or more of these four major categories:

Tolerate (Retention) Treat (Mitigation) Terminate (Elimination) Transfer (Buying insurance)

Ideal use of these strategies may not be possible. Some of them may involve trade-offs that are not acceptable to the organization or person making the risk management decision. 17

CAEHS WEBSITE

Risk Avoidance:

It involves method that would not perform an activity that could carry risk. Avoidance may seem the answer to all the risks, but avoiding risks also means losing out on the potential gain that accepting the risk may have allowed.

Risk Reduction:

It involves methods that reduce the severity of the loss. We have used RAD Model so, we have developed project module wise that means develop one module and test it then start other module. So, project can limit effort wasted to a single iteration.

Risk Retention:

It involves methods that accept the loss when risk occurs. Risk retention is a viable strategy for small risks where the cost of insuring against the risk would be greater over time than the total losses sustained. All risks that are not avoided or transferred are retained by default

Risk Transfer:

It involves method, which causes another party to accept the risk, typically by constructs or by hedging.

18

CAEHS WEBSITE

SYSTEM REQUIREMENTS STUDY

19

CAEHS WEBSITE

3. SYSTEM REQUIREMENTS STUDY

3.1 User Characteristics

The project when looked into minutely for all the aspects can be designed for four kinds of users: Admin User:-Admin is the central controller of this system and has all the rights and authorities to view as well as to modify and update the system whenever required. Staff Users: - Staff user is responsible for enters the data like student records, fill student attendance& applications in the system. Student Users:-Student enters his personal data to view his/her attendance records and to access education forum. Guest User:-Guest user meant for the students guardian. He/she can check student attendance by entering roll no into the application. Guest user cannot system. There are two types of the users who are dealing with the system. Administrator Clients TABLE 3.1.1 Sr. no. 1 User Name Administrator Work Area Having modules database. 2 Clients of the company Having access to whole application through the access and to all modify the

supervise

online process. Client Group: Head of Department Lecturer 20

CAEHS WEBSITE Student Alumni Student Students guardian

The rights that are given to above users are given in table below: View Filter Record Administrator HOD Lecturer Student Alumni Student Students Guardian Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N Y Y Y N N N Y N N N N N Modify Print User creation

21

CAEHS WEBSITE

SYSTEM ANALYSIS:
Identification Of Problem:
The old manual system was suffering from a series of drawbacks. Since whole of the system was to be maintained with hands the process of keeping, maintaining and retrieving the information was very tedious and lengthy. The records were never used to be in a systematic order. there used to be lots of difficulties in associating any particular transaction with a particular context. If any information was to be found it was required to go through the different registers, documents there would never exist anything like report generation. There would always be unnecessary consumption of time while entering records and retrieving records. One more problem was that it was very difficult to find errors while entering the records. Once the records were entered it was very difficult to update these records. In present, work done in the electricity board is performed manually which is a great headache for the department .The reason behind it is that there is lot of information to be maintained and have to be kept in mind while running the business .For this reason we have provided features Present system is partially automated (computerized), actually existing system is quite laborious as one has to enter same information at three different places. Following points should be well considered-: Documents and reports that must be provided by the new system: there can also be few reports, which can help management in decision-making and cost controlling, but since

22

CAEHS WEBSITE these reports do not get required attention, such kind of reports and information were also identified and given required attention. Details of the information needed for each document and report. The required frequency and distribution for each document. Probable sources of information for each document and report. With the implementation of computerized system, the task of keeping records in an organized manner will be solved. The greatest of all is the retrieval of information, which will be at the click of the mouse. So the proposed system helps in saving the time in different operations and making information flow easy giving valuable reports.

23

CAEHS WEBSITE

Feasibility Study:
Feasibility study is the phase in which the analyst checks that the candidate system is feasible for the organization or not. This entails identification, description & evaluation of the system. Feasibility study is done to select the best system that meets the performance requirement. If the feasibility study is to serve as a decision document, it must answer key questions. 1. Is there a new and better way to do the job that will benefit the user? 2. What are the costs and savings of the alternatives? 3. What is recommended? The most successful system projects are not necessarily the biggest or most visible in the business but rather those truly meet users expectations. Feasibility considerations Three key considerations are involved in the feasibility study. They are as follows:Economic Feasibility: Economic analysis is the most frequently used method for evaluating the effectiveness of the candidate system. We analyze the candidate system (computerized system) is feasible as than the manual system because it saves the money, time and manpower. It also feasible according to cost benefits analysis.

24

CAEHS WEBSITE Technical Feasibility: Technical feasibility centers around the technology used. It means the candidate system is technically feasible i.e. it dont have any technical fault and work properly in the given environment. Our system is technically feasible; it is providing us required output. Behavioral Feasibility: Behavioral feasibility is the analysis of behavior of the candidate system. In this we analyze that the candidate system is working properly or not. If working than it communicating proper with the environment or not. All this matters are analyzed and a good candidate system is prepared. Due to the change of system what is the change in behavior of the users, this factors are also analyzed.

25

CAEHS WEBSITE

SYSTEM DEVELOPMENT ENVIRONMENT:

System development environment shows the hardware and software requirement, which is necessary for developing the software. Necessary software and hardware requirement, which are necessary for making this software are as follows:

26

CAEHS WEBSITE

ANALYSIS
The present manual system in commercial field is a tedious one, still today there are many places where manual system is used. A person gets completely exhausted while holding about system. He gets so fed up with the heavy calculation that time because of tiredness he commits not only error but also blunders of course. Introduction of computerized calculation has made this job a bit easy. But to tell you, this process becomes very difficult. The accuracy part is also greatly affected. At present time a man who doesnt know even ABCD of this topic can not find the result of it and it becomes a great problem.

In the present time the life of a human being has become busy and hectic day by day. He needs some sort of entertainment for refreshment also. We all need to give rest to our mind as we the human being get tired after working few hours. Now days Multiplexes also play an important role in our life. Since the multiplexes are very large in size the user cant be able to visit each and every corner of multiplex.

Our project is like an information brochure which is very helpful to provide complete information about each and every corner of Multiplex problem for him.

27

CAEHS WEBSITE

Software Requirement:
Software requirement for developing this project is as follows: Microsoft Visual Basic 6.0 Microsoft -Access XP or higher version. Windows XP or higher version.

28

CAEHS WEBSITE

Hardware Requirement:
Hardware requirement for developing this project is as follows: 1.Intel Pentium Processor 2.512 MB RAM or higher 3.80 GB Hard Disk or greater. 4.Video Display Unit. 5.Keyboard. 6.Mouse. 7.One Printer for printing the electricity bill.

29

CAEHS WEBSITE

INTRODUCTION TO TOOLS:

Introduction of Visual Basic:

Over past few years visual basic 6.0 (front end) the relational data base management system has been fine-tuning it is offering a large complex application in the relational market. Visual basic 6.0 is a front end (i.e. uses graphical user interface) visual basic 6.0 uses windows environment. It may use any DBMS or RDBMS as a back-end through ODBC (open database connectivity). For our purpose of development, in our project we used Visual Basic 6.0 because visual basic 6.0 has following outstanding features and qualities. Advantages Of Visual Basic: 1. Visual Basic applications are event driven. Event driven means the user is in Control of the application. 2. Visual Basic supports the principle of object-oriented design. 3. Visual Basic is a complete window application development system. 4. Visual Basic is infinitely extensible through the use of active x controls dynamically linked libraries (dll's) and adds dins.

The Fast Track To Windows Development Visual Basic is primarily a visual design environment. We can create a VB application by designing the form and that make up the user interface. Adding visual basic application code to the form and the objects such as buttons and text boxes on them and adding any required support code in additional modular. 30

CAEHS WEBSITE Friendly Environment Creating a form, adding controls to form and writing code behind the form are all managed within a friendly environment. Graphical User Interface Application developed in DOS environment has to include its own set of video, keyboard and printer drivers. in other words many DOS programs provided virtually no user interface at all. Since windows is preferable over DOS and Visual Basic is windows based hence millions of users can use applications with no documentation or training: The graphical user interface provides a graphical environment to user as front-end for their operating system through graphical objects and therefore screen looks very attractive and almost has three-dimensional qualities. The point and shoot use of a GUI (Graphical User Interface) make use of the operating system and programming easy. Visual basic 6.0 connect to number of back-end DBMS and RDBMS such as SQL, FoxPro, Sybase, Oracle etc. Open Database Connectivity Visual basic 6.0 connects to any back-end DBMS system whose DBMS cores follow the open database connectivity rules and this connectivity is established by open database connectivity. The data storage may belong to any DBMS engine specifically supported by visual basic 6.0 driver or any DBMS that supported open database connectivity. The data entry and validation screens are created in visual basic 6.0 connects with whichever engine is specified at the time of screen was created and manipulated data within that engine.

31

CAEHS WEBSITE Client server computing and visual basic 6.0: The client / server programming is also a distributed application processing and cooperating application processing. It has three distinct components, each focusing on specific job. The three components are: 1. Client application 2. A Database Server 3. A network for connecting the first two components.

32

CAEHS WEBSITE 1. Client Application: Client application (i.e. front end) is the part of the system that users employ to interact with data. The work of client is requesting and receiving information forms a database server (back-end). Client application can be developed rapidly using visual basic 6.0.

2. A Database Server: A Database server focuses on efficiently managing resources such as the table in which data lies. The servers primary job is to manage the data tables optimall y among multiple clients that concurrently request server for same resources. Visual basic can connect to a number of RDBMS that are in trend.

3. Network for connecting the first two components: A network and communication software are the vehicle that transports the data between the clients and the server. The system both client and server run communication software that allow them to talk across a network. Object Oriented Programming Approach: The visual basic 6.0 uses the OOPS approach. In OOPS, a table is treated as also object and the data being attached to as user specified parameters the forms also treated as objects for this windows object for this window object. The firing of code shippers based on events occurring such as clicking on a button via a mouse.

33

CAEHS WEBSITE Visual Basic Libraries: When we create commercial application we create object such as windows, data windows, menus etc. these objects that you create using an appropriate visual basic pointer are stored in libraries files. When application has to run visual basic there objects from their libraries and visual basic gives you a library painter to help you manage your libraries. Events in Visual Basic: Visual basic commercial applications are event driven. The user of the application Controls the flow of the application by the action they take. Visual Basics Debugging tool: To distribute application created in visual basic we create an executable i.e. an exe file, also there is a distribution kit to distribute the application. Features of Visual Basic: 1. Visual basic provides a GUI which and therefore screen looks very attractive. 2. Work on client / server computing model. 3. Object Oriented programming approach. 4. Visual basic provides several tool bars, which make working quick and easy. 5. It is front end and DBMS as a back end so it uses all the features of RDBMS like referential integrity foreign key etc. 6. It uses a micro help line, which visual basic uses to display starters to display information through the session.

34

CAEHS WEBSITE Feel Of Windows Environment Microsoft Windows environment is built-in to Visual Basic application. No need to work with any windows compatible hardware since windows provides drivers for thousand of different printers video adapter, modems and other peripherals.

35

CAEHS WEBSITE

Introduction of MS-Access
Over the past several years, relational database management system have become the most widely accepted way to manage data relational system often benefits such as: 1. Easy access to all data. 2. Flexibility in storage and modeling. 3. Reduced data storage and redundancy. 4. Independence of physical storage & logical data designs. 5. A high-level data manipulation language (SQL). 6. Tables & table operations are well defined because relational theory is founded in set theory, relational algebra & relational calculus.

Our of this the reason for introducing relational model is to increase the productivity of the application programmer by eliminating the need to change application programs when a change is made to the database. As the technologies associated with RDBMS have grown rapidly in recent years, the appeal of relational databases has become apparent to a much wider audience. The phenomenal growth of the relational technology has led to more demand for RDBMS in environments ranging from personal computer to large highly secure CPU with users ranging from very casual to very sophisticated. Microsoft Access 2000 is a powerful relational database application with which a desktop user can efficiently create and manipulate database systems. Access targets the desktop category and works best for individuals and workgroup

36

CAEHS WEBSITE Managing megabytes of data for multi-user access to the same database. Access uses Fileserver architecture, rather than client-server architecture. Access is included in the professional and developer editions of Microsoft office. As a leader in the desktop database category, Microsoft Access makes it easy for users to find and manage their data to make better business decision. With strong integration with Microsoft Office, Access offers a similar appearance and functionality to that found in the popular Microsoft word and Excel applications for general business users, Access provides easy to use wizards throughout, such as the database wizard for getting up and running quickly and the simple query wizards for easily finding information from the data. The combination of ease of use and power in access makes it the top choice among developers who frequently use Access as a front end in a client server scenario. The only problem with MS-ACCESS is that it cannot provide strong security features. But in front of its fast execution features this drawback can be neglected as the firm does not need any type of security whether it is operational, database, or any other security. But in application development some restriction are made of some places so that our database cannot be corrupted. MS-ACCESS is therefore used for its fast execution speed and also due to its fast connectivity. Importance of database: Growth in the usage of Computers in Business and Industrial sector initiated development of modern Database Software. Database softwares offers a number of potential advantages over traditional file-processing system; some of them are as follows: Program-Data Independence

37

CAEHS WEBSITE The separation of data descriptions (metadata) from the application programs that use the data is called data-independence. With the database approach, data descriptions are stored in a central location called repository. This property of the database systems allows an organizations data to change and evolve without changing the application programs that process that data. Minimal Data-Redundancy The design goal with database approach is that previously separate and redundant data files are integrated into a single, logical structure. Each primary fact is recorded in only one place in the database. The database approach does not eliminate redundancy entirely, but it allows the designers to carefully control the type and amount of redundancy. Data Consistency By controlling data redundancy, we greatly reduce the opportunities for inconsistency. In database approach updating data values is greatly simplified when each value is stored in one place only. Finally we avoid the wasted storage space that results from redundant data storage. Data Sharing Primary advantage of database approach is sharing of data. A database is designed as a shared resource. Authorized users are granted permission to use the database and each user is provided one or more user views to facilitate this use. A user view is a logical description of some portion of database that is required by the user to perform some task. Enforcement of Standards

38

CAEHS WEBSITE When the database approach is implemented with full management support, the database administration function should be granted single point authority and responsibility of establishing and enforcing data standards. These standards will include naming conventions, data quality standards and uniform procedures for accessing, updating and processing data. The data repository provides database administrators with powerful tools for developing and enforcing such standards. Reduced Program Maintenance Stored data must be changed frequently for a variety of reasons: new data item types are added; data formats ate changed and so on. In file processing environment, the description of data formats and access methods inevitably result in the need to modify application programs. As a result in the change of data formats and access methods inevitably results in the need to modify application programs. In a database environment, data are more independent of application programs that use them. Within limits, we can change either the data or the application programs that use the data without necessitating the change in other factors.

39

CAEHS WEBSITE

PRELIMINARY DESIGN OF PROPOSED SYSTEM:

Data Design:
In most situations, many physical database design decisions are implicit or eliminated when we choose the database management technologies to use with the information system we are designing. Since many organizations have standard for operating systems, database management system and data access languages, we must deal only with those choices not implicit in the given technologies. The primary goal of database design is data processing efficiency. Objective Of Database Design: i) To decide on the organization of the database in computer storage and define the physical structure of the database management system. ii) To outline the program to process transactions and to generate anticipated management information and decision support reports. Designing Fields: system software Choosing Data Types: A data type is a detailed coding schema recognized by the system software, such as a DBMS, for representing organizational data.
Selecting a data type involves four objectives that will have different relative importance for different applications: i.) Minimized Storage Space

A field is the smallest unit of application data recognized by

40

CAEHS WEBSITE HARDWARE /SOFTWARE REQUIREMENTS Hardware Requirements Color Monitor Keyboard Mouse RAM 256 Mb Hard disk minimum 2Gb Pentium 4 2.0 hertz

Software Requirements Operating System Win 2000 , XP Language Used Visual Basic 6.0 Data Base used MS-Access

41

CAEHS WEBSITE

ESTIMATION

42

CAEHS WEBSITE

4. ESTIMATION
4.1 Effort Estimation
Project Estimation proper evaluation of the system and to get the estimation of the project, it was needed to do some metrics calculation for this project. Software project metrics are the way to do this task efficiently. Project metrics allow knowing the size and complexity of the project and helping us on the planning and cost estimation.

For this project, function-oriented metrics were used to get the size of the project at the abstract level (without taking the language in consideration). For that purpose, Function Points (FP) was used.

Function Points can be counted using the following information domains:

Number of external inputs (EIs) inputs given by a user or another system. Number of external outputs (EOs) outputs derived within the system or given to another system.

Number of external inquiries (EQs) as an online input that results in generation of some immediate software response in the form of an on-line output.

Number of internal logical files (ILFs) logical grouping of within the applications boundary and is

data

that

resides

maintained via external inputs.

Number of external interfaces files (EIFs) - logical grouping of data that resides external to the application but provides data that may be of use to the application.

Table 4.1 Information Domain Values

43

CAEHS WEBSITE Measurement Parameters Count Simple Average Complex Total

Number of user inputs Number of user outputs Number of user inquiries Number of files Number interfaces Count=Total of

4 4 5 20

X X X X X

3 4 3 7 5

4 5 4 10 7

6 7 6 15 10

= = = = =

16 20 20 200 28

external 4

284

Question 1. Does the system require reliable backup and recovery? 2. Are data communications required? 3. Are there distributed processing

functions? 4. Is performance critical? 5. Will the system run in an existing, heavily utilized operational environment? 6. Does the system require on-line data entry? 7. Does the on-line data entry require the input transaction to be built over multiple screens or operations? 8. Are the master file updated on-line? 9. Are the inputs, outputs, files, or inquiries complex? 10. Is the internal processing complex? 11. In the code designed to be reusable?

44

CAEHS WEBSITE 12. Are conversion and installation included in the design? 13. Is the system designed for multiple installations in different organizations? 14. Is the application designed to facilitate change and ease of use by the user? Total
36

Formula = count x [0.65+0.01 x SUM [fi]] The Function Point is: 286.84

Programming Language Assembly Language C COBOL Fortran Pascal Ada Object-Oriented Languages Fourth Generation Languages (4GLs) Code Generators Spreadsheets Graphical Languages (icons) LOC/FP = 50 Software Project LOC Approx Student 15000 3.00 30000 Effort Rs

LOC/FP (average) 320 128 105 105 90 70 50 20 15 6 4

Select

Paper work 150

Errors

Defects People

250

29

45

CAEHS WEBSITE Management and attendance Student Education forum and alumni 80000 3.00 20000 90 200 25 3

4.2 Cost Analysis

Error per person= total error/total people = 64/3 = 21.33 LOC per person= total LOC/total people = 23000/3 = 7666.66 0.5 rupee per paper of documentation = total Rs. = 100 Total cost of project (in rupees) = sum of Rs = 60000 Other expense = 50000

Total project cost = 60000+50000 = 110000

4.3 Use Case Estimation

Unadjusted Actor Weight
Actor simple average complex weight 1 2 3 6 How many? 1 1 1 product 1 2 3

UAW

Unadjusted Use Case Point UUCP = UAW + UUCW 206

46

CAEHS WEBSITE

0-5 Technical Factor distributed system performance requirements end user efficiency internal processing reusability of code installation ease usability requirements portability requirements changeability requirements Concurrency security requirements direct access to third party user training facility TF weight 2 1 1 1 1 0.5 0.5 2 1 1 1 1 1 Value 1 1 1 1 1 0 0 1 1 1 1 1 1 11

Technical complexity factor (TCF) 0.6 + 0.01 * TF Environmental complexity factor (EF) 1.4 0.03 * ENVF 1.34 0.71

Adjusted Use Case Point (AUCP) UUCP * TCF * EF

195.9884

Table: 4.3.1 Use Case Estimation

Unadjusted Use Case Weight

47

CAEHS WEBSITE
Use Case simple <= 3 transactions average 4-7 transactions complex > 7 transactions weight 5 10 15 200 how many? 5 10 5 Product 25 100 75

UUCW

0-5 Environmental factor familiarity with project application experience OO experience lead analyst capabilities motivation stability of requirements part-time staff programming lang. difficulty ENVF weight 1.5 0.5 1 0.5 1 2 -1 -1 Value 1 0 1 0 0 0 0 0 2

Person-Hours per AUCP Effort in Days AUCP * P-H / 7 Cost per Day in $

25 699.9585714 400

Total estimated cost

279983.43

Table: 4.3.1 Use Case Estimation

48

CAEHS WEBSITE

5. SYSTEM ANALYSIS

49

CAEHS WEBSITE

5. SYSTEM ANALYSIS
5.1 Study of Current System
In the past before site is organized following difficulties are coming towards user.

First Look In current system clerks are doing paper work to maintain students records and employees records and that record may be frequently used in any terms, Like student records used to search any student or to update the student attendance day by day and employee records can be frequently used in this environment. Second Look

Generate the attendance report of class wise, student wise and subject wise. Manages the alumni student record in excel sheet and there is no facility about the student education form from where student can asked any question and share their knowledge towards the college environment.

It is complicated to manage all the record through paper and not easy to search any particular record within less time But after developing this project its been easy to maintain and search students and employee records and to generate the attendance reports. Alumni student can easily get registered in to the alumni section and mail to be send

5.2 Problem and Weakness of Current System

All the documentation work can be done by hard copy and complicated to make various reports. After implementing this project above work can be done easily by giving some extra efforts like to update attendance.

50

CAEHS WEBSITE User cannot sing up directly to use this system for that he or she has to visit to admin. Admin can register the new used to use the system. All the users have different access criteria as per their designation.

5.3 Requirements of New System

In this portion we discover all the functionality of our system according to user needs his/her requirements. and

Workflow Oriented Requirements The system is designed to enable the users in performing day-to-day operations by prompting the tasks to be done. Instead of waiting for the users to perform the activities, system lists the activities for the user. Pro-Active Workflow of the System Already decided to do List

Robustness& Security

System provides for: Layered Security To Protect Unauthorized Access Role Based Access Control (HOD, Admin, Lecturer and Student have diff access) Superior Technology for Faster and Secured Access

Friendly Features Some of the friendly features of this software are as follows: Towards Paperless College System Efficient Monitoring of Activities Automated Assessment Features To Eliminate Manual Scheduling Errors Promotes Effective Utilization of Resources Facility To Track Realization & Growth 51

CAEHS WEBSITE Tracking of Interest of People for the Upcoming Activities.

Extendibility After implementing the whole system, if any type of suggestion and any new ideas are allowed. According to that it is possible to extend the system for more convenient. User Friendliness Some of the features that make the software user friendly are as follows: User friendly design Easy to access all the accessible modules.

5.4 Feasibility Study

In the history of CAEHS Website it happened first time to use this kind of web an Lan based application and its feasible to implement within a less time and money.

5.4.1 Operational Feasibility

Performance Our system provides adequate throughout and its response time is very quick. Because when any user sees the application for searching the data, it will search form the database and display the output.

Information The system provides records to end users with timely, accurate and usefully formatted information. When any user or administrator wants the

information about system, he or she will just log into system. And get their desire information.

Economy 52

CAEHS WEBSITE No we are not jumping into economic feasibility. The question here is does the system offer adequate service level & capacity reduce the burden of manual work of the college.

Efficiency Does the system make maximum use of available resources including Manual Work of Administrator, time, and flows of forums, minimum processing delays & the like?

In the matter of efficiency, our system is totally computerized, so no need for any person to explain anything regarding our system, and its very easy to understand as well as operate.

Each and every information is given very briefly and well known to user so user is able to do the work without any Administrators help. Here also only few persons are required for moderating and controlling the system, so with the help of very less human resource and manual work system will work.

All the forms are well designed as well as developed so user can easily deal with system like every form is designed as per the lecturers requirements.

5.4.2 Technical Feasibility

It is a measure of practically of a specific technical solution and the availability of technical resource and expertise.

The analyst must find out whether current technical resources, which are available in the system is capable of handling the users requirements or not. If not, then the analyst with the help of developers should confirm whether the technology is available and capable or not.

53

CAEHS WEBSITE As per the availability of the technical resources we could make this project of student and attendance management.

Q-1

Do we currently posses the necessary technology?

Ans : Yes, The technology & software that we are going to use are available with us. The technology which we have used is easily available in the market today.

Q-2

Do we have necessary technical expertise?

Ans : Yes, We do have necessary technical expertise so that development would be compatible with the schedule. But certain kind of training is required for the particular technology but it will not make an adverse effect on the development schedule.

Factor considering

Here we have to consider those tools, which will be requiring for developing the project. The tools which are available and the tools, which will be required, have to take in account. As far as basic knowledge is concerned we have studied we have basic knowledge of C# and SQL server. Various technical books, e-books etc are available. Dealing with database is the main issues in our system. Using SQL server as backend provided this functionality. But we have used MY SQL.

5.4.3 Schedule Feasibility:

Schedule feasibility corresponds to whether sufficient time is available to complete the project. 54

CAEHS WEBSITE

Factor considered

Schedule of the project was around 3 months Time by which the project has to be completed. Reporting must be completed within this time period.

By considering all above factors it was decided that we have sufficient time and we decide to start the project. By marinating the schedule we were able to complete the project on time.

5.4.4 Economic Feasibility

For declaring that the system is economically feasible, the benefits obtained from the system we have to be rated against the cost incurred to actually develop the system. The benefits must equal or below the cost for development. The basic resources to consider are: Management time. Time spent by the system analysis team. Cost of doing full system study. Estimated cost of hardware. Estimated cost of software and /or software development.

The following are benefits that would be derived from the proposed system: The application is developed using C# and MYSQL server technology. Application does not increase hardware cost as minimal configuration required for developing code. In this way developing application does not generate any overhead costs. 55

CAEHS WEBSITE As this application has no overhead in development and installation but economically this application will be beneficial to maintain student records.

5.5 Requirements Validation

As our project is to build a dynamic web site and lan based, there is criteria such as windows authentication but still some security must be provided in essence of making the rights of certain entity to be limited to them. Certain validation criteria that are needed listed below.

In our system, some functionality like view the employee and college records are restricted to the admin and college employee only. So, we have to apply validation for the login functionality for the authentication.

Our system generates the student attendance report from the web services as per the users search criteria. So to produce the best match we have to apply validations on the input controls.

In the page of Personal Detail of alumni student, student has to enter his/her contact information (Email Id) in order form which he/she get mail when he/she fill that form our college gave him user name and password to access site. So, we have to apply validation on the field of Email Id.

56

CAEHS WEBSITE

5.6 Functions of System

Student Registration and Attendance Use Case

cheak validation for student employee

<<extend>>

registation for alumini

maintain student attendance teching * nonteching *

<<include>>

generale attendance report

raise question * ** * ans. the question faculty *

student

* over all student deatail

login

student section(clerk)

insert student detail

clu <<in

de>>

<<extend>>

maintain & updation of student detail

<< i

nc

lu

de >>
hod check student attendance report set min limt of attendance

Attendance Management / project Diary module Online examination. Used student record for attendance project dairy, other activity.

57

CAEHS WEBSITE

5.7 Data Modeling

5.7.1 Class Diagram/E-R Diagram Student Registration and Attendance Part A

SM_G extension no SM_ G ga dd full n udian a me SM_ Gg SM _G occu audian patio ci t n y
_p SM

co u SM_

pstate SM_ ith on w relati SM_ stud. ntry

te da _b e SM ag

SM_mo.no

SM_ppin

pcity SM_

SM_ccity

SM_ Gpm

ste

a _c SM

SM_ G off ice a

o. no

as

S M

_G

of fic

ce

.n o

_p m S ho to _M M S na

pdis SM_

lac eo fb irth

PART-A

SM_resi.no

p SM_ add

SM_Cadd

bc

u _s SM

_G

S M

SM _H SC c co de ente r
SM_ m

_c

er

ti 1

S M

SC si t no SM_ ark o H SC b btain ord SM_ pri quali vious SM_out o ficati f mark on
Student_Master A1

SM _H

e _c SM

n nt sig stude SM_ SM_application

SM_sign of gaurdion SM_Branch

SM_HSC year SM_meat marks SM_addminision year

Id SM_ m SM_

cata SM_ o erit n

gory
ISA 1

SM_ Em

ail
Link to Part c realationship R17

Insert_Update_Stude nt_Record R4

Studing Student A2

Passout Student A3

Link to Part D Entity C8 Link to Part B Relationship R8 Link to Part B Relationship R8 Link to Part B Relationship R5 Link to Part D Entity C8 Validate_Passout_St udent R3 SAL_Id SAL_Cource Link to Part B Entity C4 LT_Id SAL_Cource Login_Type_Mast er A6 SAL_Designat ion SAL_Compan yname Student_Alumini_ Master A4 SAL_Studing SAL_Collegen ame Registration_For_Alu mini R1

SAL_Cource

Login_Master A5

SAL_Cource Link to Part C Entity C1

LT_Type Request_To_Login R16

Add_Login_Type R15

58

S M _c
rti i4 e rt _c SM 5 certi SM_ 3

er

ti 2

m S _g

M S

na e _F m M S r de m e

n _L

en

am e

Sm_Cpin

CAEHS WEBSITE

AM_Lecno AM_Lecno Save_Attendance _Record R10 Attendance _Transction _master B2 AM_Lecno

PART-B

AM_Lecno

Link to part C to ISA 3

AM_Id

AM_Lecno Update_Student_ Attendance R9 CLS_Id

Aggregation
Lecture C4

SUB_Id EM_Id

Attendance _Master B1

Link to Part A Entity A2 Link to Part C Entity C5

Check_Attendanc e_Report R8

Set_Category_Qu estio R7 MCM_Name MCM_Id Main_Catag ory_Master B3 SCM_Name MCM_Id Sub_Catego ry_Master B4 Set_Category_Que stio R7

SCM_Id

QRM_Questi on FTM_Id

QRM_Date QRM_Attend ance Raise_Question R5 SCM_Id

Link to Part A Entity A2

Question_R aise_Master _B5

SCM_Id MCM_Id

FANS_Answ er LM_Id

FANS_Attac hment FANS_Date Give_Ans_Of_Que R2

Link to Part A Entity A1

Answer_Ma ster B6

QRM_Id FANS_Id FTM_Id FTM_Type Forum_Typ e_Master B7 Set_Forum_Categ ory R17

59

CAEHS WEBSITE Part C

EM_gaurdiation_Name

PART-C
EM_gaurdiation_no

DS G_ Id

BM_ Id

EM _d o

cdis EM_

_c Em sta te

EM_ph.no

ci _c EM ty

ag

SU B_ Id

EM _W o rk

loa

u _q EM re a _A EM
te

ali

a fic

n tio

_p EM e at st

_j o

in

in

EM EM _p _P ci t ad y d EM _M

of

h _p EM

da

oto

m _e Em

ail

na

me

EM _L

na

me

EM_Fname EM_Id Em_mo.no

o Area Em_ f int in

EM

_p Em pi n

EM a _c dd st _p EM di

Past EM_ nce rie e p ex

C1 Employee master

Link to part A entityR16

C Em_

ISA 2

c2 teaching

c3 Non-teaching

ISA 3

ISA 4

peon

Link to part B entityC4

principle

Link to part D entityC8

Link to part B entityR8

HOD

Link to part A entityA1

R16 Check Student detaile

60

CAEHS WEBSITE

Part D
PART-D
C M _N

Link to part C ISA 4

am e

CM_Id

clerk

R14 Update catagory

Category Master d1
_I d

BM_ID

Link to partA relationship R4

Link to part A realationship R3

R13 Update Branch record

Branch Master d2

CM_ CBM _Id

id

BM _I d

BM

BM_ Nam

_h e

ad

ad _Id he e_ EM ne i a _tr BM

NO M_ CB

of

s si t

R12 Update No of sits / branch

Category branch Master d3

SLM _ SM_ Id SLM _ Id

Date
SL lea M_ ve

re s

on

R11 Update Leaved Student From study

Student Leave Master d4

Overview of All Part 61

CAEHS WEBSITE
PART B PART A

A1

R8

B1 B2
*

A2

R8 C4

A3

R5 B3

A4

R8 B4

A5 R4 A6
*

B5 B6 B7

R17 R16
PART C ISA 4

PART D

C1 C8 C2 D1 C3 D2 C5 C6 C7
ISA 3

R8 D3

D4

62

CAEHS WEBSITE 5.7.2 System Activity or Object Interaction Diagram Student Registration and Attendance

Usel Login

START

User Validation

View Student Management Form

Authorization

Check if student record available

Yes

Update Record

No
Insert Student Record

Transfer to view Record

Maintain Student Recoed View Student Record

Shutdown Record fully Updated Validation Failed Close Record

STOP

63

CAEHS WEBSITE Alumni and Educational Forum

General login start

Reg for alumini view alumini form

seccessful

Validate student

register for alumini

user login

User validation

succers

Check student type

view student attendance form Update attendance update student attendance

validation failed

To view record

view attendance record

Alumini student

To view report maintain attendance record view attendence report

generate student attendance report check circular for alumini student

Close attendance report Close attendance form

shutdown Alumini validation failed & stop

stop

64

CAEHS WEBSITE

5.8 Function and Behavioral Modeling

5.8.1 Context Diagram Student Registration, Attendance & Education Forum
Online discusion with Student or faculty Online discusion With student

student

Login

Answer the raised question Raise the question Fill project diary Information sharing College Resource planning

Online discussion with faculty Online discussion with Student or faculty Generate attendance report Update student attendance Generate timetable Apply for leave Update,insert,delete Student detail/record

Login

Report to admin for Invalid or fake information Action taken for invalide info Info.sharing employee

65

CAEHS WEBSITE

5.8.2 Data Flow Diagram Student Registration, Attendance & Educational Forum

66

CAEHS WEBSITE
Check student record clerk Insert,update,delete Studenr record Employee master 1.1 Student management
att en Che da c nc k er ep ort

hod

Employee master

Employee master

Generate attendance report by given criteria lecturer Update student attendance 1.2 Student attendance

Check attendance report

student

attendance master

Attendance trajection master Que. raised master

student master

Online discussion with faculty Ans.the raised qus. Raise the qus. Online discussion with Student/ faculty Student / faculty Info. Sharing Action taken agains invalidInfo.

Upload circular for pass Out student Validate Check the registered student

in m ad . o t t r fo or fo d in ep li va In

Ans. master Online disccussion with student

1.3 Student Education forum

ans.Raise the qus. Raise the qus. Online discussion with Student/ faculty Info. Sharing

1.4 Student Alumini

Register for alumni Provide username & passward

Pass out student

Passout master

67

CAEHS WEBSITE 5.8.3 Control Flow Diagram

Visual Studio server Request to raise question

t to c e es dan n qu R e a tte a te d Up

Visual Studio 2008

Request to Insert student record

Requ est r

egis

te r

Used New Question ans.

Update attendance

Insert Student record

Update Studentn record

Modify Student redord

Insert Alumini record

qu e s to s t to re

Request to validate

Store Student record Store Student Attendance record Answer the raised question Store Alumini record Validate records

Resp onse Stud ent r ecor upda d te

t to es qu e Re stor

Re se on sp d Re ecor te r da up R att equ en est da nc toVi e r ew eq us t St Rep ud en onc ta ef tte or nd an ce

View student attendance

se on ate sp pd Re ini u m Alu

Store Question Ans.

MySql database

Response of data Re Of spo alu nse rec mi ord ni

Retrive Student record

View student record

r fo r d st co ue i re eq n R mi lu A
View alumini record

e qu Re

to st

re s to

Re

ra e.o qu d e e s r on sto sp

.is ns

68

CAEHS WEBSITE

5.9 Main Modules of New System

The Main module is used to manage all other modules present in this project and it is the Heart of our data logger.In our project student registration, employee registration and fill attendance module can be considered as the main module because other all the modules like attendance report cannot be work without this module

5.10 Selection of Hardware and Software and Justification

Software The software selected for the modules are Visual Basic(Asp), MYSQL. This software has been selected for this module for the following reasons: Visual Basic is selected for this module because it supports multiple languages. Visual Basic provides many built in functionality so we choose to develop our project in Visual Basic MYSQL is used as database as it easier to build database in it and connect. MYSQL is used as database, because as stated earlier MYSQL is Open source there is no need to purchase license for that. Hardware

PROCESSOR: Pentium IV. RAM MEMORY : 1GB. : 80 GB HDD SPACE.

I have used the above mentioned hardware specification in order to obtainoptimized performance. 69

CAEHS WEBSITE

OUTPUT

70

CAEHS WEBSITE

71

CAEHS WEBSITE

72

CAEHS WEBSITE

73

CAEHS WEBSITE

74

CAEHS WEBSITE

75

CAEHS WEBSITE

6. TESTING

6. TESTING
76

CAEHS WEBSITE

Errors are more common, more pervasive and more troublesome in software than with other technologies Software Testing has a dual function; it is used to establish the presence of defects in program and it is used to help judge whether or not the program is usable in practice. Thus software testing is used for validation and verification, which ensure that software conforms to its specification and meets the need of the software customer.

Developer resorted Alpha testing, which usually comes in after the basic design of the program has been completed. The project scientist will look over the program and give suggestions and ideas to improve or to correct the design. They also report and give ideas to get rid of around any major problems. There is bound to be a number of bugs after a program have been created. Software Inspection

Analyze and check system representations such as the requirements document, design diagrams and the program source code. They may be applied at all stages of the process.

6.1 Testing Plan

The Testing Process

Developer tests the software process activities such as Design, Implementation, and Requirement Engineering, because design errors are very costly to repair once system has been started to operate. Therefore, it is quite obvious to repair them at early stage of the system. So analysis is the most important process of any project. Requirements Tractability

77

CAEHS WEBSITE As most interested portion is whether the system is meeting its requirements or not, for that testing should be planned so that all requirements are individually tested. Developer checked the output of certain combination of inputs, which gives desirable results, or not. Strictly stick to your requirements specifications, give you the path to get desirable results from the system.

Tested Items

Our tested items are like database object reading/writing, skin object manipulation, view of containers and skins in different browsers. Testing Schedule

Developer has to test each procedure back-to-back so that errors and omissions can be found as early as possible. Once the system has been developed.

6.2 Testing Strategy

Unit Testing Module Testing

In this testing individual components and modules are tested to ensure that they operate correctly. We had tested each and every module such as login details, upload details, to maintain information for all the features and finally the generation of the reports. For this we have checked the database for particular entry for validation. Integrated Testing

This testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. All the modules 78

CAEHS WEBSITE testing in the unit testing are integrated and are tested for their interdependency. This system mainly works on the integration of all the departments. Validation Testing - Alpha Testing A customer conducts alpha testing at the developers site. The customer check by entering the live data. If any errors occur in the system than they directly contact us. Security Testing

This testing is done to confirm that the software allow only authorized users to access and use the system. There are two levels of security in this system. We have tested entering the username and password for all the security levels to show them the information pertaining to their work only.

Human Factor Testing

The user cannot do anything if after submitting the screen goes blank while the data are being processed. They may not take the action the analyst wanted or expects instead responding in unusual ways.

6.3 Testing Methods

Testing methods Involves executing an implementation of the software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required.

6.3.1 Statistical Testing

79

CAEHS WEBSITE Used to test the programs performance and reliability and to check how it works under operational conditions. Tests are reflecting the actual user inputs and their frequency.

The stages involved in the static analysis for this system are as follows: Control flow analysis

Unreachable code Unconditional branches into loops

Data use analysis

Variable used before initialization Variables declared but never used Variables assigned twice but never used between assignments Possible array bound violations Declared variables

Interface analysis

Parameter type mismatches Parameter number mismatches Non-usage of the results of functions Uncalled functions and procedures

Storage management faults analysis

Images not stored in resources Out of bound -> programs non-volatile memory.

80

CAEHS WEBSITE 6.3.2 Defect testing

Defect testing intended to find inconsistencies between a program and its specification. These inconsistencies are usually due to program faults or defects.

6.3.3 White-box Testing

White-box testing, often 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 within a module have been exercised at least once, (2) Exercise all logical decisions on their true and false seeds, (3) Execute all loops at their boundaries and within their operational bounds, and (4) Exercise internal data structures to ensure their validity.

6.3.4

Black-box Testing

Input

Output

We have tested our functions of component to check the specification of our components. We selected input set to test the components like in query process we gave the different kinds of inputs to examine their output. We test software with sequence that have only a single value. We used different sequences of different sizes in different test. 81

CAEHS WEBSITE Derived tests so that the first, middle and last elements of the sequences and accessed to reveal the problems at partition boundaries. Structural Testing

We have done path testing to exercise every independent execution path through a component or program. If every independent execution path is executed then all statements in the components must have been executed at least once.

Integration Testing

After our individual modules were tested out we go to the integrated to create a complete system. This integration process involves building the system and testing the resultant system for problems that arise from component interactions.

We have applied top-down strategy to validate high-level components of a system before design and implementation have been implemented. Because our development process started with high-level components and we worked down the component hierarchy.

Performance Testing

Performance testing is designed to test the runtime performance of the system within the context of the system. These tests were performed as module level as well as system level. Individual modules were tested for required performance.

In performance testing we counted the processing time and response from the system with respect to request. We also checked out the total-execution time, which takes 10 to 15 seconds for loading.

Condition Testing

82

CAEHS WEBSITE Condition testing is the test case design method that exercise the conditions contained in a program module. If the condition is incorrect then, at least one component of the condition is incorrect. It may include

Boolean variable error String index out of bound error Null pointer assignment Input output connection exception Parsing (conversion) errors Arithmetic expression error

Interface Testing

Interface testing is integral part on Integration testing. Therefore we checked for

Interface misuse Interface misunderstanding We examined the code to be tested and explicitly list each call to an external component. In the system, standard tests for GUIs have been performed, which are as follows:The position and related labels for all controls were checked. Name of the form is also given appropriately. All menu functions and sub functions were verified for correctness. Validations for all inputs were done. Each menu function was tested, whether it invokes the properly. Pull down controls was verified for proper functionality. Whether the non-editable text control is disabling and it was also Verified that it doesnt exceed the maximum allowed length. corresponding functionality

83

CAEHS WEBSITE Whether the system prompts the user with appropriate message as And when invalid information is entered.

Stress Testing

Stress testing is to test the system for emergent properties such as performance and reliability. Performance tests have to be designed to ensure that the system can process its intended load.

Object Testing

Object testing is to test objects as individual components, which are often larger than single functions. Here following activities have taken place.

Testing the individual operations associated with objects. Testing individual object classes. Testing clusters of object. Testing the object-oriented system.

84

CAEHS WEBSITE

7. TEST CASES

85

CAEHS WEBSITE

7. TESTCASES
It means executing an implementation of software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required. There are different types of tests for verification of software.

7.1 Testing
It is intended to find inconsistencies between a program and its specification. These inconsistencies are usually due to program faults or defects. In order to perform defects test we have generates some test cases. The results of these tests are as following: We have tested each of the form in the system for its correct functioning. We have used test case based on equivalence partitioning in our project.

Equivalence partitioning:

Valid input

System

Valid output

86

CAEHS WEBSITE FIG 5.1

Equivalence partitioning is set of data where all of the set member should process in an equivalent way. Output equivalence partitions are program output that has common characteristics so can be considered as a distinct class.

Using the program specification of user documentation may identify the equivalence partitioning and by the tester using experience to product which classes of input value are likely to detect error. Deriving equivalence partitioning from the system specification there are various testing cases that can also be used. These test cases are below: Test software with sequence that has only single value. Different sequence of different size in different tests. These decrease the chance that program with defect will accidentally produce a correct output because of some accidental characteristic of the input. Derive test so that the first, middle, and last element of the sequence are accessed this approach reveals problems at partition boundaries.

Purpose

The purpose of the test cases is to test the various input and see the output produce any error or not. There are different test cases according to the system. It is tested with different types of value like single value multiple value and see it can generate expected output or no Required Input and Expected Result.

87

CAEHS WEBSITE

7.2 Test Cases

Test Case No: Name: Description: 1 Login page In this page client must enter the User Name and Password to access the system. Test Data Used: The data about user name and password from the Database.

Expected Output: If proper status and user name and password match then allow to login otherwise not allow Actual Output: If proper status and user name and password match then allow to login otherwise not allow Pass/Fail? Pass

Test Case No: Name: Description:

2 Check on the Browser capability Here checking about that this online system will work on the different browsers or not like (internet explorer, firebox etc.

Test Data Used:

The data about user name and password from the Database.

Expected Output: If user name and password match then allow to login otherwise not allow Actual Output: If proper status and user name and password match then allow to login otherwise not allow Pass/Fail? Pass

Test Case No: Name: Description:

3 Check Multi-user availability Here check that at a same time more than one user can access the system with User name and password.

Test Data Used:

User name and password from the database.

88

CAEHS WEBSITE Expected Output: At a time system will allow, multi user should access the user name and password Actual Output: At a time system will allow, multi user can access the system by their own user name and password Pass/Fail? Pass

Test Case No: Name: Description:

4 View all student records Here after logged into the system user can see the entire student records.

Test Data Used:

Student related data from the student_master tables from the database

Expected Output: User should see the details of all the student after logged in to the system Actual Output: User can see the details of all the student after logged in to the system Pass/Fail? Pass

Test Case No: Name: Description:

5 Only specific student record search Here after logged into the system user can see the any specific student details by only its authority.

Test Data Used:

Student related data specially student name from the student_master tables from the database

Expected Output: User should see the details of the specific act after logged in to the system only by selecting only branch, sem and class

89

CAEHS WEBSITE Actual Output: User can easily see the details of the specific student after logged in to the system only by selecting branch, sem and class Pass/Fail? Pass

Test Case No: Name: Description:

6 Student lab allocation Here after logged into the system user can see the any specific lab by only selecting branch, sem and class

Test Data Used:

Student related data specially student enrollment no from the student_master tables from the database

Expected Output: User should see the specific module of the specific input given to the system after logged in to the system by selecting branch, sem, class and lab batch Actual Output: User should see the specific module of the specific input given to the system after logged in to the system by selecting branch, sem, class and lab batch Pass/Fail? Pass

Test Case No: Name: Description:

7 Combination of Name and Password Here after logged into the system user can see the any specific details of the specific Designation.

Test Data Used:

Act related data specially act name and password from the act related tables from the database

Expected Output: User should see the details of the specific data of the specific act after logged in to the system by selecting act name and password. Actual Output: User can see the details of the specific data of the specific act

90

CAEHS WEBSITE after logged in to the system by selecting act name and password. Pass/Fail? Pass

Test Case No: Name: Description:

8 Only by Surname search in student alumni Here after logged into the system user can search the student only by surname.

Test Data Used:

Related data specially search by surname from related tables from the database

Expected Output: User should see the details of the specific surname after logged in to the system by selecting only surname. Actual Output: User cannot see the details of the specific rule after logged in to the system without entering surname. Error message is there by only selecting not the surname. Pass/Fail? Fail

Test Case No: Name: Description:

9 Only Student Attendance search Here after logged into the system user can see the details of the attendance of different subject.

Test Data Used:

Related data of enrollment number ,search from tables from the database

Expected Output: User should see the details of the specific data after logged in to the system by selecting only from date To date. Actual Output: User cannot see the details of the specific data after logged in to the system without selecting any subject name. Error message will be generate. Pass/Fail? Fail

91

CAEHS WEBSITE Test Case No: Name: 10 Student search his/her registration detail of its enrollment number and update specific detail. Description: Here after logged into the system user can see the details of its registration. Test Data Used: Related data find from related tables from the database

Expected Output: User should see the details of the registration and update selected detail. Actual Output: User should see the details of the registration and update selected detail. Pass/Fail? Pass

Test Case No: Name: Description:

11 Faculty wise student attendance search Here after logged into the system user can see the details of the attendance of different subject filled by faculty

Test Data Used:

Related data of enrollment number and attendance records from attendace_master tables from the database

Expected Output: User should see the details of the specific data after logged in to the system by selecting only from date To date. Actual Output: User cannot see the details of the specific data after logged in to the system without selecting any subject name. Error message will be generate. Pass/Fail? Pass

Test Case No: Name: Description:

12 Class wise student attendance search Here after logged into the system user can see the details of the attendance of different subject filled by faculty

Test Data Used:

Related data of enrollment number and attendance records

92

CAEHS WEBSITE from attendace_master tables from the database Expected Output: User should see the details of the specific data after logged in to the system by selecting only from date To date. Actual Output: User cannot see the details of the specific data after logged in to the system without selecting any subject name. Error message will be generate. Pass/Fail? Pass

Test Case No: Name: Description:

13 Average subject wise student attendance search Here after logged into the system user can see the details of the attendance of different subject filled by faculty

Test Data Used:

Related data of enrollment number and attendance records from attendace_master tables from the database

Expected Output: User should see the details of the specific data after logged in to the system by selecting only from date To date. Actual Output: User cannot see the details of the specific data after logged in to the system without selecting any subject name. Error message will be generate. Pass/Fail? Pass

Reliability of the System

There are three approaches to reliability of the system.

Error Avoidance

Error Avoidance is impossible in any system, as it points to prevention of errors from occurring in system. In our system, we cannot prevent occurrence of errors because, if user does not call methods properly and does not input appropriate parameters, we are unable to avoid errors. 93

CAEHS WEBSITE

Error Detection and Correction

Error Detection corresponds to reorganization of errors when they are encountered. In the system, developer use alert message to prompt errors to users. We also use try-catch structure to prompt errors. Alert message shown to users are in well-understood forms. System prompts various error messages like file does not exist, whenever the user tries to open any other file instead of image file. However, system does not support correction of errors; it is user's responsibility to take appropriate action.

Error Tolerance

Error Tolerance refers to reorganization of errors when they occur, but enables system to keep running through degraded system. In system will never shutdown automatically due to errors, but it is possible that because of errors it may not work efficiently. For example, if invalid image is given then system will prompt error and it will not shut down. Furthermore, if user does not add image file, in that case, that layer is not displayed nor activated and any further operations are not done. Finally theres only one amazing statement that means everything in itself

Testing never ends, it just gets transmitted from you to your customer, every time your customer uses the software, and a test is being conducted

94

CAEHS WEBSITE

SUMMARY

95

CAEHS WEBSITE

8. SUMMARY
Our project wasto create a CAEHS Website which could be useful for college.This portal has many features such as good interactivity, ease of use, proper GUI, simple navigation, effective and accurate results and good security. The main objective is to build a system that assists the end user in finding aany type of record he wants provided he has proper authority. For this system, there are 4 types of users: they are Admin,Staff,Student and Guest users.

8.1Overview
This project aims to eliminate extra work that is associated with finding a company to develop a software project. Previously the customers had to make a field study about the software companies that would build their software product and have to perform a lot of paper work. Now they can simply post a software proposal and interested software companies bid on those software proposals. This way the interaction between the customers and development companies will become easy and simple. This is an online bidding system consisting of mainly three types of users: namely customers, software development companies and administrator. The project also allows software developers and customers to give feedback to each other for a particular project.This website helps the customers and software developers to interact easily and share information effectively in a secured manner. It works as a bridge between the customers and software developers.

8.2Specification and Project Plan

8.2.1 Requirements specification

The software requirements specification document contained information about the project such as objectives and goals of developing the software product. It also contained the information about the target environment, various types of requirements such as functional, nonfunctional and domain requirements. Moreover, the requirements document also had some 96

CAEHS WEBSITE details about the users of the system, major functions performed by the system as well as the risks associated with the system. And finally the deliverables of the system. More information can be obtained from the software requirements specification document.

8.2.2 Project Plan document

The project plan document contained information about the project, process model used for building the project, team organization, deliverables of the project and risks associated with the project. It also focuses on the project schedule, project estimates, control plan and project resources. For more information on project plan see project plan document.

Team

Overview

The members of the team were: Madhu Shukla. Viral Parekh. Dipalee Rathod. Manisha Valera.

Team Structure

Our team is a Democratic Decentralized (DD) team. Instead of having a team leader, each member in the team was responsible for some specific task. The decisions were made by conducting meetings and discussions. The team as a whole was accountable for the outcomes of its decisions and actions. All the members of the team performed some specific functions such as requirements gathering and reviews were done by all the team members while you can see the details of the tasks that each person performed from the task sheet.

97

CAEHS WEBSITE Advantages

As our team structure was Democratic Decentralized (DD) we did not have any team leader. All the members took the decisions by reaching a consensus. No decision was forced on anyone and hence there no clashes for anything. There were no ego problems and the working in the team went off very smoothly. Everyone got equal opportunity to share and implement their ideas. No member of the team faced any problem working with others and everything went off very smoothly.

Disadvantages

The only problem we faced sometimes was staying on schedule. So if there was a team leader, then he would force us to finish the work on a specific date so that we do everything on time. Also sometimes we had a hard time to decide what we should do next and in what time, so this was an issue.

Doing things differently

We could have developed system with different suited model and as following centralized structure to comple it earlier than the time taken. Also it could be implemented on different environment than Visual Basic to make it cost effective using OPEN SOURCE software.

Process

Overview 98

CAEHS WEBSITE

We used Iterative Model. So With incremental yield is intended that all requirements to be fully described. Then the system iterative phases. The first definition phase study is performed once. Work is done in phases. And also increments of the product can be made with enhance features as time passes.

Advantages Risks can be better managed by smaller pieces to be developed. Bottlenecks are so quick to light. Complex systems are clearer and less complex to implement it step by step to a comprehensive income working without the need of a complete design is created. At the end of each iteration, a useful product, even if the development is discontinued put. In a linear method would often never made use perch. Changes in organization can be quickly incorporated into the development process. Disadvantages

There are obvious disadvantages. Some disadvantages: Because during the development process needs to be adapted and refined, it may be that the original purpose fades. It can happen that it continues to change and it never finished. This is called Scope Creep. Project managers who are accustomed to linear development can be confused by the strong dynamics. The rapid development has the potential to draw a bill on the organization and resources of the great dynamics. Inexperience with the way of working can lead to misunderstandings and disappointments.

99

CAEHS WEBSITE Conclusion

We used iterative model and hence we needed to develop the requirement on hand as a core product. Team structure used was Democratic Decentralized which again benefited us as member with expertise in different field leaded at different phase of time. Also further development can be made in the system it can be enhanced as well as can be converted as web based system.

Future Implementation 1) Message service is most accentual services so it can be added in future for circular and other curriculum activities. 2) CAEHS Website can be converted into a web based application for fully web based functionality. 3) It can be used in Online Examination also.

100

CAEHS WEBSITE

Scope and Future Applications

This project has many future applications like it can be used in any of the medical or pharma store.

This project was build keeping in mind all the requirements of these outlets and they can be implemented in any such type of organization with very few modification.

101

CAEHS WEBSITE

BIBLIOGRAPHY

The Waite Groups Visual Basic 6.0 How-To, Brierley, Price & Rinanldi.

Mastering Visual Basic 6.0 Evangelos Petroutsos.

Doing Object in Visual Basic 6.0 Sams Techmedia.

Visual Basic 6 Programming Bible Eric A. Smith, Valor Whistler & Hank Marquis.

Chapman Developing Secure Applications With Visual Basic Sams Tech Media

Inside SLQ Server 7.0 Soukup Delaney Microsoft

Microsoft Oracle 8.0 7.0 Survival Guide Sams Techmedia

Beginning Oracle 8.0 7.0 for Visual Basic Developers, Thearon Willis.

102