PREFACE

Prerequisites It is very simple & easy to use software. For using the software one should have the knowledge of English language & Computer. This is complete menu based software i.e. one just have to select appropriate menu & by selecting the menus associated work will be performed. Content of this report The report is organized into major topics. Introduction: This topic gives the introduction about the project, the need of making this project. The uses of this project & the function performed by project. System Analysis: Before software can be engineered the system in which it resides must be understood. To accomplish this overall objective of the system must be determined; the role of hardware, software, people, procedures & other system elements must be identified. System analysis all the activities & is covered in this topic. System Design: Designing is a meaningful engineering representation of something that is to be built. The model used to build this project is discussed in this topic.

REQUIREMENT ANALYSIS
Hardware Requirements:
Hardware is required for computing, interconnection between devices that are enable flow of data. Hardware used in this project is as much as that it can support the software and other requirement of project.

Processor with Dual Core. RAM -->128 MB.

Printer.

Software Requirements:
Software is a computer program, data structure and related documentation that serves to affect the logical method, procedure or control that is required. Software requirements specification states the goal and objective of the software. Operating System: DOS, WINDOWS 98.

Language used: C++

Documentation: Microsoft Word.

INTRODUCTION TO SYSTEM DESIGN

System design is a solution, a how to approach to the creation of the new system. This important phase is composed of the several steps. It provides the understandings and procedural details necessary for implementing the system recommended in feasibility study. Emphasis is on translating the performance requirements into design specification. Design goes through logical and physical stages of development. Logical designs reviews the present physical system, prepares input and output specification, make edit security and control specification, details the implementation plan and prepares a logical design walkthrough. The physical design makes out the details of the physical system, plans the system implementation devices a test and implementation plan and specifies any new hardware and software. Implementation, planning, system test preparation, system interfaces specification and user documentation. 1. Data Base Design: - This activity deals with the design of the physical database. A key is to determine how the access paths are to be implemented. A physical path is derived from a logical path. 2. Programs Design: - In conjunction with the database design is a decision on the programming language to be used and the flowcharting and debugging procedure prior to conversion. 3. Systems and Programs Test Preparation: - Each aspect of the system has a separate test requirement.

PHASES OF SDLC
The development of a system has been divided into various stages. Through these stages or activities are sequenced but actually they overlap and are highly interrelated. For e.g. while evaluation of an existing operation the System Analyst may think about or come up with an alternative way that would improve the system. Following are the stages of System Development. (A) Initial Investigation: The initiation of the development of a system begins with the improvement of information system or a procedure. This recognition is necessary for the improvement of information system or a procedure. These stages involve preliminary survey or initial investigation. The impetus for change may come from within or outside the organization. This phase mainly focuses on identification of users real problem form its symptoms. The initial investigation results into a statement of scope and objective. (B) Feasibility Study:-Feasibility Study considers the economic, technical, and behavioral factors in system development. In feasibility study the development of system flowcharts is done that identifies the characteristics of candidate system. The feasibility study involves the evaluation of existing system and procedures, analysis of alternative candidate system and cost estimates. It highlights the users demonstrable needs and whether the problem is worth solving or not. The result of this study is technical, behavioral feasibility, cost/benefit analysis and software specification. (A) Economic Feasibility: - Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. If benefits outweigh costs, then the decision is made to design and development of system. Otherwise further justification or alternation in the proposed system will have to be made.
1

Technical Feasibility: - Technical feasibility center on the existing computer system and to what extent it can support the proposed addition.
4

2Behavioral Feasibility: - People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have toward the development of computerized system. (C)Analysis: This phase involves the detailed evaluation of the present system and collection of data through interviews, questionnaires, on-site observation, procedures, manuals, etc. This leads to collection of acts. Logical model of system i.e., data dictionary and data flow diagram are prepared. (D)System Design:In this design phase the analyst prepares general and detailed. Design specification of input formats. Output formats, data files, structures and procedures, considering the existing computer hardware e.g. any. After finalization of software requirement, the Hardware specifications are finalized if it not already exists. After this coding for the various procedures is done. i. ii. iii. The process and stages of system design. Input/Output and Form design. File organization and data base design.

DEVELOPMENT ACTIVITIES:Several development activities are carried out during structured design. Those are following:1

Process of design The design phase focuses on the detail implementation of the system recommended in the feasibility study. Emphasis is on translating the performance specifications into design specifications. The design phase is a transition from a user-oriented document to a document oriented to the programmers or data base personnel.
5

2 Requirements of form design i. Identification and wording. ii. Maximum readability and use. iii. Physical factor. iv. Order of data items. v. Ease of data entry. vi. Size and arrangement forms. vii.Use of instructions.

FILE ORGANIZATION AND DATABASE DESIGN

After designing the input and output, the designer begins to concentrate on table designing or how data should be organized around user requirements. How data are organized depends on the data and responses requirements that determines hardware configurations table organization may be sequential, indexed sequential, inverted list or random. An integrated approach to table design is the database. The general theme is to handle the information as an integrated whole, with a minimum redundancy and improve performance. Software languages are used to data entry operation can be controlled by input design. Input design is the process of converting user-oriented inputs to computer-based format. In the system design phases, expanded DFD the logical data flows, data store, sources and destination. A system flow chart specifies master tables; transaction and computer program input data are collected and organized into groups of similar data. Ones identified appropriate input media are selected for processing.

1. Output Design: Computer outputs are most important and direct source of information to the user. Efficient, intelligible output design should improve the systems relationship with the user and help in decision making. A major form of output in a hard copy from the printer. Printout should be designed around the output requirement of the user.
2. Form design:-

The data, the forms carry come from people and the informational output the system goes to the people. The physical carrier of data of information. It also can constitute authority for action.

Testing:No system design is ever perfect. A system is tested for online response, volume of transaction, stress, recovery from failure and usability. System testing requires a test plan that consists of several key activities and steps for programs, string, system and user acceptance testing. Testing is the process to check the system to find out any error that many cause the system some trouble or hamper the integrity of the data. PREPERATION OF THE TEST PLAN Software testing is the process of executing a program with the intent of finding an error. A good test has a high probability of finding a yet undiscovered error. The test data was prepared keeping in mind the user requirement and expectation. METHOD USED TO TEST DATA Test data was keened in through the data entry screen in the database. Input/output was carried to ensure proper functioning of the system. It was confirmedthat all the required validation and check are performed by giving invalid data input. Testing for suitable error message/messages was done in case of invalid data entry. Testing for proper report layout.

TESTING METHOD
1 UNIT TESTING :- This type of testing involve individual testing of programs with

respect to the desired expected output proper care is taken when entering the data checks were made to see that the data entered is correct and not of the specified bond(s), proper error message are flashed when an error occurs.
2 SYSTEM TESTING: - In this phase the system as a whole is tested. This testing

phase will check the integrity of the data while it was transferred from one process to another. The interaction between the modules was checked to see whether a module procedure the required output, which would be needed as input of another one.
e. Implementation: -

This is crucial phase of system development .It involves introduction of new system into operation. This involves creating computer awareness on to job, training, installation of hardware, terminal if does not exist, client communication equipment before the system is up and made operational. User manuals are prepared and user is trained in its use. Bore implementation system was working manually. Few people were developed to run the computerized system. Data was fed at regular interval and monitories on basis of report and output. All the possible errors were recorded rectify and rested. The system after proper security and satisfaction was stepped in to next phase employees were given adequate training, about how to handle the system.
f. Post-implementation and Maintenance:-

After the installation phase is completed and the user staff is adjusted to the changes created by the candidate system, the evaluation and maintenance begin. Like any system, there is an aging process that requires periodic maintenance of Hardware & Software. If the new information is inconsistent with the designed specification then changes have to be incorporated in the Software. Hardware also requires periodic maintenance to keep in tune with designed specification.
9

Project Description
Introduction about Student Information System
Student information system (SIS) is a software application for education establishments to manage student data. Student information systems for entering student testa school, college or university. Also known as student information management system (SIMS), student records system (SRS), student management system (SMS), campus system (SMS) he SIS is equivalent to an Enterprise Resource Planning or ERP system for a corporate customer. As such, many of the issues with ERP System Selection Methodology, implementation, and operation of an ERP system apply to Functions These systems vary in size, scope and capability, from packages that are implemented in relatively small organizations to cover student records alone, to enterprise-wide solutions that aim to cover most aspects of running large multi-campus organizations with significant local responsibility. Many systems can be scaled to different levels of functionality by purchasing add-on "modules" and can typically be configured by their home institutions to meet local needs. Until recently, the common functions of a student records system are to support the maintenance of personal and study information relating to:

management

system (CMS)

or school

management

Handling inquiries from prospective students Handling the admissions process Enrolling new students and storing teaching option choices Automatically creating class & teacher schedules Handling records of examinations, assessments, marks, grades and academic Maintaining records of absences and attendance
10

progression

Recording communications with students Maintaining discipline records Providing statistical reports Maintenance boarding house details Communicating student details to parents through a parent portal Special Education / Individual Education Plan (IEP) services Human resources services Accounting and budgeting services Student health records

In larger enterprise solutions that have student data at their core, further functions include Student financial aid management and more may be customized by the developer. Where national or government systems exist for student finance or statistical return purposes, student records system often provide functionality that caters for this, by way of modules or core elements that handle the production of required files, or deal with the formatted transfer of information. Examples are the FAFSA (Free Application for Federal Student Aid) process in the United States, the United Kingdom's Student Loans Company processes (SSAR, SSAC and ATFEE file processing), the UCAS (Universities and Colleges Admissions Service) in the United Kingdom, or the HESA and HESES student statistical returns in the United Kingdom. In the past, universities and large school districts in particular have created their own bespoke student record systems. One such example is the ROSI system at University of Toronto. With growing complexity in the business of educational establishments, most organizations now choose to buy customizable software, and increasing numbers are buying software as a service (SAAS). Most student information systems in use today are server-based, with the application residing on a central computer server, and being accessed by client applications at various places within and even outside the school. But student information systems have been moving to the web since the late 1990s and that trend is accelerating as institutions replace older systems.
11

SOFTWARE USED
ABOUT OPERATING SYSTEM WINDOWS XP
In order to understand the application development process, it is helpful to understand some of the key concepts upon which Visual Basic is build because Visual Basic is a windows development language, so some familiarity with the Windows environment is necessary. A complete description of the inner working of Windows would require an entire book. A simplified working of the Windows involves three key concepts:1 Windows 2 Events 3 Messages Windows can be thought of simply as a rectangular region with its own boundaries. There are several different types of Windows: 1 An explorer window in Windows 98 2 A document window within our word processing program OR 3 A dialog box that pops up of remind us of an appointment Icons, Text boxes, Option buttons and menu bar all Windows. The Microsoft Windows O .S manages all of these many windows by assigning each one a unique ID no. the system continually monitors each of these windows for sign of activity or events. Events can occur through user action such as a mouse click or a key press, through programmatic control, or events as a result of another window action.

12

Language Used & Why:

We are using the C/C++ language because of the following advantages. C: It is convenient for hardware programming. C++: C++ is an Object Oriented Programming Language (named initially C with

classes), was developed by Bjarne Stroustrup at AT&T Bell Laboratories in Murray Hall, New Jersy USA, in the early 80s. The other comparative advantage are C++ has best of two languages, i.e. Simula 67 & C. C++ is superset of C. The three most important facilities that C++ adds on to C are Classes, Function Overloading, &Operator Overloading. These features enable us to create abstract data type, inherit properties from existing data type and support polymorphism, thus making C++ truly Object Oriented. It offers benefits to Program Designer & User. OOPs promises greater programmer productivity, better quality of software & less maintenance cost. We can build programs from the standard working modules that communicate with one another rather than having to start from scratch. This leads to saving of Development time and Higher Productivity.

PLATFORM:

MS DOS. / Windows98.

13

OPERATIONAL REQUIREMENTS
In this section we will discuss about the functions used & there respective header files. HEADER FILES USED: #INCLUDE<STDIO.H> Sentences that begin with a pound sign (#) are directives for the preprocessor. They are not executable code lines but indication for the compiler. In these case the sentence #INCLUDE<STDIO.H> tells the compilers preprocessor to include the Standard input/output function to be included. #INCLUDE<CONIO.H> Sentences that begin with a pound sign (#) are directives for the preprocessor. They are not executable code lines but indication for the compiler. In these case the sentence #INCLUDE<CONIO.H> tells the compilers preprocessor to include The CONIO Standard header file. This specific file include the declarations of CLRSCR (), GETCH () library in C++., and it is included because it use program. #INCLUDE<GRAPHICS.H> Sentences that begin with a pound sign (#) are directives for the preprocessor. They are not executable code lines but indication for the compiler. In these case the sentence #INCLUDE<.GRAPHICS.H> tells the compilers preprocessor to include the graphics standard header file. This specific file includes declarations of set color (), outtextxy (), circle () library in C, and it is included because its functionality is used in the program. #INCLUDE<IOSTREAM.H> Sentences that begin with a pound sign (#) are directives for the preprocessor. They are not executable code lines but indication for the compiler. In these case the sentence #INCLUDE< IOSTREAM.H> tells the compilers preprocessor to include the IOSTREAM Standard header file. This specific file includes the declarations of Cout, Cin library in C++. And it is included because its functionally is used in the program.

14

SCREEN SHOT

15

1. First Form

16

2.Second form

17

TESTING
What is Testing?
Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation. Once source code has been generated, software must be tested to uncover and correct as many errors as possible before delivery to the customer. Our goal is to design a series of test cases that have a likelihood of finding errors. Thats where software-testing techniques come into the picture. These techniques provide systematic guidance for designing tests that: Exercise the internal logic of software components and Exercise the input and output domains of the program to uncover errors in program function, behavior and performance. Testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. Testing also provides a good indication of software reliability &software quality as a whole. The results of the different phases of testing are evaluated and then compared with the expected results. If the errors are uncovered, they are debugged and corrected. A strategic approach to software testing has the generic characteristics: Testing begins at the module level and works outwards towards the integration of the entire computer based system. Different testing techniques are appropriate at different points of time. Testing and Debugging are different activities, but debugging must be accommodated in the testing strategy. A strategy for the software testing must accommodate low level tests that are necessary to verify that a small source code segment is performing correctly according to the customers requirements and that of developers expectations.

18

Testing objectives: Testing is the process of executing process for finding errors. A good test builds a high probability of finding an as yet undiscovered error. A successful test uncovers yet unfound errors. If testing is successful, it will uncover errors in software. It demonstrates that software functions appear to be working as specified and that performance requirements appear to have met. Data collected as testing is conducted provides a good indication of software reliability and quality. The objectives of software testing are: Testing is a process of executing a program with intend of finding an error. A good test case is one that has a high probability of finding an as-yet undiscovered error. A successful test is one that uncovers an as-yet undiscovered error. These objectives imply a dramatic change in viewpoint. They move counter to the commonly held view that a successful test is one in which no errors are found. Our objective is to design tests that systematically uncover different classes of errors and to do so with a minimum amount of time and effort. If testing is conducted successfully (according to the objectives), then it will uncover errors in the software. As a secondary benefit, testing demonstrates that software functions appear to be working according to specification, that behavioral and performance requirements appear to have been met. In addition, data collected as testing is conducted provide a good indication of software reliability and some indication of software quality as a whole. But testing cannot show the absence of errors and defects, it can show only that software errors and defects are present. It is important to keep this statement in mind as testing is being conducted.

Testing methods and Strategies: White Box Testing: It is also called Glass Box Testing. It is a test case design method that uses control structure of the procedural design to derive test cases. Using White Box Testing methods, the software engineer can derive test cases that:
19

Guarantee that all independent paths within a module have been exercised at least once. Exercised all routes at their boundaries and within their operational bounds. Exercised all logical decisions on their true and false sides. Exercised internal data structures to assure their validity.

Black Box Testing: Black Box Testing focuses on the functional requirements of the software. That is, Black Box Testing enables the software Engineer to derive sets of input conditions that fully exercise all functional requirements for a program. Black Box Testing is not an alternative to White Box Testing. Rather, it is a complementary that is likely to uncover a different class of errors than White Box Testing. Black Box Testing attempts to find errors in the following categories: In-correct or missing functions. Interface errors and Performance errors Errors in data structures or external database access. Initialization and termination errors. We are using Basis path testing method to assess our software. The basis path method enables the test case designer a logical complexity measure of a procedural design & uses this measure as a guide for defining a basis set of execution paths. Test cases derived to exercise the basis set are guaranteed to execute every statement in the program at least time during testing.

20

Goal Size and Performance Goals

a. Speed: Computerization of the system will lead to the speedy retrieval of the

data.
b. Accuracy: It gives accurate and precise results.

c. Efficiency: Computer definitely scores over humans in terms of efficient

handling of large amount of data.

d. Consistency: The results we obtain are consistent and do not vary with

different methods of access.

e. Errors: On line validation of relevant data prevents incorrect or duplicate

entries.
f. Centralization: Centralization of data is provided so as to allow multiple

accesses at a time.
g. Easy to Understand: It is developed in such a way that user requires no

special training for understanding the flow of the system.

h. Easy Configuration: It can be configured as and when required to user

application. User friendly as usage of combos and popup make it easy to operate. 2. Quality Goals The project is made according to the current business needs of the concerned organization but it can be changed in future according to the changing business trends and according to the needs of organization.
21

BIBLIOGRAPHY
Let Us C By: Yashwant Kanetkar. By: Yashwant Kanetkar. By: Robert Lafore. By: Balaguru Swami. By: David Perkson. By: Herbert Shild. By: Sumita Arora.

Let Us C++

Turbo C++

Object Oriented Programming Object Oriented Programming Complete Reference C++ Teach Yourself C++

22