Documentos de Académico
Documentos de Profesional
Documentos de Cultura
1.1. EDUCATION DECISION SUPPORT SYSTEM INTRODUCTION OF THE PROJECT :Education is the building block of the nation if provided correctly it builds a nation strong and the foundation of a strong nation is a Child so the decision about their education should be done properly. The future of a child is like clay and it takes its form in the manner it is molded or given shape. Our system is providing various alternatives to student to choose a best career so that they can make their dreams come true. The real problem arises when they are on the way to make their future and they are not having proper channels or medium through which they can have proper guidance about their career. So, they get confused in their decision and they have no chance to show their capabilities and leave them in disguise. It has been estimated that most persons make as many as 1,000 decisions per day. Most of these decisions are trivial but some may be momentous. Helping students become better decision makers when faced with dilemmas is one of the desired outcomes of education in colleges. Employers often attest to the high level of technical knowledge possessed by graduates, but these employers frequently cite lack of confidence and experience in integrating and applying knowledge in the process of making decisions as a weakness in contemporary higher education. Education plays the vital role in human life and every person wants a type of education which will improve his inner most skills. Further more an appropriate decision taken by a person affects him for a long time. If decision is regarding the education then it will affect him throughout his life. So a best decision is depend on the appropriate information. So, here we are developing a decision support system which is related to the education. EDUCATION DECISION SUPPORT SYSTEM will provide better options to make a decision for the students carrier. These options are based on a set of information, which are related to the education. This system is also very helpful to the management for taking a decision for the betterment of their institutions. This is also working as a MANAGEMENT INFORMATION SYSTEM (MIS).
Information is the basis for interaction between the user and an analyst. Information system may be defined as a set of devices, procedures and operating system. These are designed around user based criteria to produce information and communication it to the user for planning and to control the performance. Management information system is a prime issue in any existing information system. Computer based management system is the need of present scenario. The information should reveal to the user by accessing to solve their thrust to knowledge and making decision. MIS is a highly integrated grouping of information processing function designed to provide management with a comprehensive picture of specify operation. It is a combination of various information for decision making and planning, initiating, organizing, staffing, directing, coordinating, reporting, budgeting and controlling the operation of the subsystem of the firm/institution and to provide a synergistic organization in the process. The purposed system is simply a decision support system (DSS). EDSS represent both a philosophy and a set of tool .At the philosophical level; it is the next stage evolution of MIS. MIS emphasized the value added component of data namely information .
1.2.OBJECTIVE
The objective of this system is to provide the information to the management in the regarding of the betterment of the institution. From this information they generate the policy for the next year. They take the decision about the any personnel of the institution. In this system we maintain information about the students, from this information we can provide better career counseling to students. In brief following functions are performed: The personal details of the teacher are stored in the teacher master table The details of class and subject are stored in the class master table and subject master respectively. The student details are stored in student registration table and STUDENT ID is provided for all the relevant information about the student. Provide the feedback about the student by student feed back form and provide the feedback about the teacher by teacher feedback form.. Here we maintain the record of the activities of the student for a particular session. We will evaluate academic performance of a student and provide the suggestion for choose the stream after the tenth class which is very difficult for the student. We provide the carrier guideline for the student for his better future. Generate the mark sheet for the student. Relative study of the various institutes will be provided by our system, which is a mile stone in the success of any institute. Enhancement of Reliability of the system. Increases the efficiency and effectiveness Remove the Redundancies Security of data
institute/school in a summarized manner for taking the right decision about their organization. The manual system suffers from the problem of reliability when procedures work some but not all of the time, or when use of the same procedure leads to different results. Sometimes it produces invalid results are often most troublesome to users and system managers. They worked well but almost draw incorrect conclusions. The manual system is inaccurate when processing is error prone. This system might suffer from the problem of economy and timeliness when the existing methods are costly and the information cannot be retrieved when and where it is needed.
1.4.2.PRELIMINARY INVESTIGATION
The first step in the system development life cycle is the preliminary investigation. It is the collecting of information that helps the team members in evaluating the merits of the project request and thus make an informed judgment about the feasibility of the proposed project. For this proposed system we have done some preliminary investigation and gathered data through primary methods.
ON SITE OBSERVATIONS
In this process we monitored the office environment, the workload of the system and the users, methods of work and the facilities provided by the organization to the users. The purpose of on site observation is to get as specific as possible to the real system being studied. In this method, we observe the activities of the system directly.
CONDUCTING INTERVIEWS
Written documents and the on site observation techniques tell us how the system should operate, but they do not include enough details for a decision to be made. We prepared a questionnaire for the users of the proposed system to learn more about the nature of the project request and the depth to which users may retrieve information from it. Sometimes we Galgotias College Of Engineering And Technology, Gr.Noida 8
also conducted interviews to provide details that further explained the project and show whether assistance is merited economically, operationally and technically.
2. FEASIBILITY STUDY
Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called a feasibility study. This type of study determines if a project can and should be taken. Many feasibility studies are disillusioning for both users and analysts. The feasibility studies may be carried out in three phases: (i) (ii) (iii) Technical Feasibility Operational Feasibility Economic Feasibility
i. TECHNICAL FEASIBILITY
During technical analysis the technical merits of the system concept are evaluated, at the same collecting additional information about performance, reliability, maintainability and produce-ability. In some cases, it also includes a limited amount of research and design. Technical analysis begins with an assessment of the technical viability of the proposed system. What technologies are required to accomplish system function and performance? What new methods, algorithms or processes are required, and what is their development risk? How will these technology issues affect Cost? The tools available for technical analysis are derived from mathematical modeling and optimization techniques, probability and statistics, queuing theory and control theory. Technical Feasibility is frequently the most difficult area to assess at this stage of the product engineering process. Because objectives, functions and performance are somewhat hazy, anything seems possible if the right assumptions are made. It is essential that the process of analysis and definition to be conducted in parallel with an assessment of technical feasibility. The considerations that are normally associated with technical feasibility Include: Development Risk: can the system element to design so that necessary function and performance are achieved within the constraints uncovered during analysis? Resource Availability: Are skilled staff available to develop the system element in question? are other necessary resources (hardware and software)available to build the system?
10
Technology: Has the relevant technology progressed to a state that will support the system? During an evaluation of technical feasibility, a cynical, if not pessimistic, attitude should prevail .The consideration that are normally associated with technical feasibility include development risk, resource availability and technology.
11
COST-BENEFIT ANALYSIS
Cost-benefit analysis is complicated by criteria that vary with the characteristics of the system to be developed, the relative size of the project, and the expected return on investment desired as part of a companys strategic plan. In addition many benefits derived from computer-based systems are ignitable (e.g. better design quality through iterative intimation, increased customer satisfaction through programmable control, and better business decisions through reformatted and pre-analyzed sales data). Direct quantities comparisons may be difficulty to achieve. In a nutshell the following steps are to be followed: (i) (ii) (iii) (iv) (v) (vi) To study the existing system. To define the scope of the proposed system. To study the strengths and weakness of the existing system. To study various alternatives. To carry out feasibility studies. To get the management approvals.
OTHER FEASIBILITY
Like Social, Management, Legal and Time Feasibility of the proposed system has also been checked to find the above aspect of the system.
12
13
Firstly we collect all the academic record of the student such as marks of the all class activity grade of all the years for each student. Teachers evaluate all the record of the student and provide suggestion to choose the stream. There is a problem in the selecting career after completion the school studies for this problem we collect all the student performance and provide different career guideline schemes. Operator feed all the marks of the student. Teacher gives the feed back for the student. Student give the feed back to the teacher Management checks details of student and teacher such as marks sheet of the student and feedback of the teacher. Management checks the desired report for taking the right decision about the organization.
FRONT END
MICROSOFT VISUAL STUDIO 2010
BACK END
SQL SERVER
TOOLS
Active-X, Data Object (ADO) Text Tool, Label Tool, Data Control, Shape Tool Combo box, List Box, Command Button, List View
An overview of DBMS :DBMS is the acronym for the relational database management system. The concept of relational database is known since 1980 the idea of database management system is quit old. The most famous RDBMS packages are ORACLE, SYBASE, and INFORMIX etc. For this software we preferred Oracle -8 as our backend tool. What Is Database Management System? A database management system is essentially a collection of interrelated data and set of programs to access this data. The collection of data is called DATABASE. The primary objective of DBMS is to provide a convenient environment to retrieve and store database information. Database system supports single user and multi-user. While DBMS let only one person to access data. A Database consists of two parts namely the database management and the database application. Database management systems the programs that organize and maintain the information whereas the database application is the program that let us view, retrieve and update information stored in DBMS. DBMS has to protect database against unintentional that could be caused by the users and application like disk crack etc and in case of multi-user system, it must be capable of notifying any database change to the other user
Characteristics of A Database Management System: It represents complex relationship between data. Keep a tight control of data redundancy. Enforces user-defined rules to ensure the integrity of table data. Has centralized data dictionary for the storage of information pertaining to data and its manipulation Ensures that data can be shared across authorization.
15
Enforces data access authorization. Has automatic, intelligent back up and recovery procedures for data. Have different interfaces which users can manipulate data.
Data Maintenance: It checks whether each record has fields containing all
16
17
The SQL SERVER parallel server product. Disk mirroring. Fast and simple recovery mechanisms. SQL now offers most of the features that most operating systems have had for years Account disablement after a specified number of failed attempts. Password expiration and forced password changes. Password history maintenance to prevent users from reusing previous passwords. Complex password enforcement that forces users to choose passwords which cannot easily be guessed by potential intruders.
Primary Key
This constraint avoids duplication of rows and does not allow NULL values, when enforced in a column or set of columns. As a result it is used to identify a row. If primary key constraints are assigned to a combination of columns, it is said to be a Composite key, which can contain a maximum of 16 columns.
Index
We create indexes explicitly to speed up SQL statement on a table. The index points directly to the location of the rows containing the values. We create an index on a column or a combination of columns using CREATE INDEX command.
Foreign Key
This constraint helps to understand the relationship between tables.
18
Insert Command
Once the table is created, INSERT command of Data Manipulation Language (DML) is used to insert records into the table. The values are separated by commas and must be entered in the same order as they are defined in the table. The syntax of INSERT command is as follows:
INSERT into <table-name> values (list of data values); Example Insert into student_master values (STU00001, GAURAV, M, 23, MEERUT); If a user wants to enter 100 records then he has to write insert statement 100 times. He can avoid this by making use of substitution variable. To understand this, use the following insert command: INSERT into TEC_MASTER values (&TEC_ID, &Name, &Sex, &Age, &Address); If you want to insert another records in the same table just write run or type / Run command is used for executing previous command.
Select Command
Select command is used to retrieve records from the table The syntax of SELECT command is as follows: SELECT column_name1, column_name2.......from table_name..........; To select specific row from a table we include a Where clause in the select command. We can retrieve only the rows, which satisfy the Where, condition. To arrange the displayed rows according to some predefined order we can use the order by clause. The order by clause should be the last clause in a select command. The syntax for SELECT command along with the WHERE clause is given below: SELECT column1, column2 ...from table_name1 ...WHERE conditions [order by];
19
20
ADO Hierarchy
The ADO hierarchy comprises of seven independent objects.
Connection
Represents a unique session with a data source. You can use this object to connect to a data source such as Oracle, SQL Server or Access or even Microsoft Excel spreadsheet. A Connection Object is created using the create Object method of the Server object. Set con = New ADODB.Connection Here, ADODB.Connection is the Application/Class string. Connection object allows commands to be executed using the Execute method. The Execute command returns a Recordset object.
21
Recordset
The Recordset object is used to browse through data returned from the Execute method of the Connection object, like this: Set RSTEMP = con.execute (Select TEC_ID, Name from TEC_MASTER) Here RSTEMP is a Recordset object that contains all the record from the table TEC_MASTER and only the TEC_ID and Name fields from that table. The Recordset is made up of the Beginning of File (BOF) region, the records themselves, and End of File (EOF) region. Fields Collection and Fields Object: These items provide a way to access the data in the columns or fields of a Recordset. You can access fields object only from a Recordset object.
4. SYSTEM DESIGN
Galgotias College Of Engineering And Technology, Gr.Noida 22
System Design sits in the technical kernel of the software engineering process and is applied regardless of the software process model that is used. System design involves creating a sufficiently detailed description of the products to be designed based on the analysis model that it could subsequently be covered into the final product. The design process determines the shape of the software. Software design is an iterative process through which requirements are translated into a Blue Print for constructing the software. Initially, the blue print depicts a holistic view of software. That is, the design is represented at a high level of abstraction level that can be directly traced to specific data, functional, and behavioral requirements. It should be modular. A good design is one in which there is tight internal binding within modules and loose coupling between the various modules. This facility reuses and de-couples the software so that an error in one part of the software has less chance of flowing over to and affecting other parts of the software. The designers goal is to produce a model or representation of an entity that will later be built. The process by which the model is developed combines intuition and judgment based on the experience in building similar entities , a set of principles and/or heuristic that guide the way in which the model evolves ,a set of criteria that enables quality to be judged ,and a process of iterations that ultimately leads to final design representation.
Input Design
Inaccurate input data are the most common cause of errors in data processing. Errors can be controlled while input design. The goal of designing input data is to make data entry as easy, logical and error free as possible. While designing the forms where the user inputs the data care should be taken about the following points. The allocated space for each field. Only a single dot can be accepted in amount type fields Field sequence that must match that in the source document. The format in which the data fields are entered; for example:-filling out the date field is required through the edited format MM-DD-YY
23
INFORMATION DESCRIPTION
Here we give the primary data objects to be processed by the system. The composition of each data object and what attributes describe the object. Where do the objects currently reside. What are the relationships between each object and other objects? What are the relationships between the objects and processes that transform them? All this is done making use of entity relationship diagram.
DATA MODEL
The data objects are:
Administrator
Operator
Teacher
student
24
The attributes and the relationships are shown in the subsequent Entity Relationship diagram
25
Feed Suggestion for the Student such as Career Guide Line and Subject Suggestion
26
Does Registration
Operator rrrrrr
Student
27
Operator Teacher
Report
28
School
N Teacher N
Teacher
Management
Participate
Activity
1
Student
Subject
29
3. Operator Module
Does the registration of the student. Fee evaluation of the student. Marks feed of the student. Maintaining the past year record of the student. Provide the desired report for the management. Maintain the past year record of the student.
4. Teacher Module
Generate the marks sheet for the student. Evaluate the student academic performance. Evaluate the activity performance of the student. Provide the subject suggestion for the student. Provide the suitable carrier guide line for the student. View the feed back from student. Give the feedback for the student.
5. Student Module
Give the feedback for the teacher. Galgotias College Of Engineering And Technology, Gr.Noida 30
View the result. View the performance of elf and others. View the suggestion from the teacher.
6. Report Module
31
Break Down Information into Separate entities Get a piece of paper or a database design tool and break down the collected data items, collected into separate entities. An entity is a distinct object in the database .Each entity becomes its own table. Assigning Attributes to each Entity When you have created separate entities for each object, assign attributes to each entity. An attribute is a property or characteristic of the object, such as its name, address etc. Each attribute becomes the fields in the table. Identify a Unique Identifier for each entity A row in a relational database needs to be uniquely identified so you can retrieve that row and only one row. Select one or more attributes that are uniquely identified a single row in the entity. This unique identifier is called Primary Key. Establish Relationship Among Entities Determine the types of relationship that exists among your entities. There are three types of relationship in relational database design: 1. One-to-One 2. One-to-Many 3. Many-to-Many One-to-One A One-to-One relationship is one in which each row in one table represented by a single row in another table. One-to-Many A One-to-Many relationship is one in which a row in one table may be represented by many rows in another table. Many-to-Many A Many-to-Many relationship is one in which arrow from one entity may be represented by one or many row in another table and a row from second table may be represented by one-to-Many row in the first table.
33
4.5.TABLE DESIGN
Any Programming environment to create containers, to manage human data, can be conceptualized as Data Management System. Traditionally, the block of human data being managed is called a Database. Hence, in very simple terms these programming environments can be conceptualized as database management system. All Database Management Systems allow users to create containers for data storage and management. These containers are called Field. The minimum information that has to be given to the DBMS for a suitable container to be constructed which can hold free from human data is 1. Field Name 2. Field Length 3. The type of data that can be placed in to the Field Field Name: When we wish to view the contents of the field later all we need to do is to tell the programming environment the field name. The programming environment is intelligent enough to fetch for us contents of the field. Field Length: This is the manner we Rigidize free from human data. We create container of a predetermined length into which we will store Free Form human data for management .We will have to try our best and decide the longest name we wish to manage and decide on the container length accordingly.
34
Human data is mainly of two type character or numeric if numbers then we can have whole number or floats. We would then have to inform the programming environment which is creating field for us, what kind of data we will store in the field when it is being used . The simplest reason being that we would have to separate character and number data types. We would imagine that each field was an object created us by the RDBMS .Then the fields create for us in the same horizontal plane would be another distinct object created for us by RDBMS. Multiple field placed in the same horizontal plane is an object called Record by RDBMS several records of equal length placed one below the other to enable user to continue to store data is called Table. Here we are using a relational database management system ORACLE-8i to handle database design. 1.Student_ master 2.Student _transaction 3.Tec_master 4.Tec_activity 5.School_performance 6.School policy 7.Parent_suggestio 8.class_ master 9.Activitygrade 10.Fee_master 11.Student_marks 12.student_activity 13.Subject_master 14.Stream_submaster 15.Tec_feedback 16.Student_feedback 17.Student_subjectsuggestion 18.Student_carrier 19.user
35
36
Width 10 12 12 50 12
Width 10 10 10 10
37
Field Name S_ID S_Name S_Add S_phone S_site S_Email S_Activity S_Session S_Grade S_per
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Char Varchar2
Width 10 20 2 20 3
38
Width 20 5 5 20 5 5
Description
39
Width 10 8 2 3 10
Width 10 10 12 3 15 3
40
Width 10 10 12 2000 10
41
Session
Varchar2
10
42
Width 10 2000 10 10
Foreign Key
43
Optimizations though do not provide any additional checks to the software however it provides that the software be made functional to its desired efficiency consistency with recurred standard. In this software project optimizations been achieved for the following laid down aspects: SPEED OF PROGRAM EXECUTION It has been ensured that the procedure adopted/design/coding done is optimized and superfluous details omitted to meet the requirements. By ensuring this, the speed of execution is enhanced which has future initiated similar reaction in other sub modules CPU OVERHEADS By optimization the CPU overheads is reduced to increase the system throughput and reaction time, waiting period is reduced accordingly. PROPER BALANCING OF CPU & I/O BOUND INSTRUCTION By optimizing, CPU & I/O bound instruction are streamline. Therefore reducing the corresponding load on CPU as well as on memory/other system resources. Crash Recovery It has been ensured that the crash recovery is automatic to avoid undue delay is giving direct instruction at the time of crash. Other security and protection like auto backup, protection form unauthorized access and normalization of database tables has been ensured to achieve the recurred efficiency.
VALIDATION CHECKS
This is the most important section of the software requirement specification. Different classes of tests are conducted to validate function, performance and constraints. This section demands a thorough understanding of software requirements. We have given proper time and attention by validating data and database as far as possible. Validation as the name suggests validate the requirement and act as a rider to ensure that the design software is utilized to its thresh-hold without any error. In the above software project the requirement of validity checks arises to ensure that the various input data endorse by the user is entered in correct form and design. These validation checks in this system have been included to ensure its correctness and desired accuracy. Few of them are given as under:Galgotias College Of Engineering And Technology, Gr.Noida 44
STUDENT ID: Validation proved that the details of Student ID be entered on the correct field and format, any discrepancy to the proposed format will show the error and the user can correct the data accordingly DATE: Likewise date has to be entered in the correct field/format i.e. DD-MM-YY and any variation to the above will show an error to the user. AMOUNT: Amount has to be entered in the correct format i.e. only numeric value and any variation to the above will show an error to the user, otherwise it would be problematic to further calculation. The proposed software can be used to its organization and desired accuracy can be insured as proposed. These validation checks have been provided in all the modules so that the software may be run for its laid down standard.
45
Software testing is critical element of software quality assurance and represents the ultimate review of specification, design and coding. It is used to detect errors. Testing is a dynamic method for verification and validation, where the system to be tested is executed and the behavior of the system is observed.
TESTING OBJECTIVES:
1) Testing is a process of executing a program with the intent of finding an error. 2) A good test case is one that has a high probability of finding an as-yet-undiscovered error. 3) A successful test is one that uncovers an as-yet-undiscovered error. The above 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 do so with a minimum amount of time and effort. If testing is conducted successfully (according to the objectives stated above), it will uncover errors in the software. Testing cannot show the absence of defects, it can only show that software errors are present.
6.2.TESTING TECHNIQUES
The techniques followed throughout the testing of the system are as under 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 will fully exercise all functional requirements for a program. Black Box Testing is not an alternative to whitebox techniques. Rather, it is a complementary approach that is likely to uncover a different class of errors than white-box methods. Black-Box Testing attempts to find errors in the following categories: (1) Incorrect or missing functions.
46
(2) Interface errors. (3) Errors in data structures or external data base access. (4) Performance errors. (5) Initialization and termination errors. Unlike White Box Testing, which is performed early in the testing process, Black Box Testing tends to be applied during later stages of testing. Because Black Box Testing purposely disregards control structure, attention is focused on the information domain. Tests are designed to answer the following questions: How is functional validity tested? What classes of input will make good test cases? Is the system particularly sensitive to certain input values? How are the boundaries of a data class isolated? What data rates and data volume can the system tolerate? What effect will specific combinations of data have on system operation? By applying black box techniques, we derive a set of test cases that satisfy the following criteria: 1) Test cases that reduce, by a count that is greater than one, the number of additional test cases that must be designed to achieve reasonable testing, and 2) Test cases that tell us something about the presence or absence of classes of errors, rather than errors associated only with the specific test at hand. WHITE-BOX TESTING: White Box Testing knowing the internal workings of a product tests can be conducted to ensure that internal operations are performed according to specifications and all internal components have been adequately exercised. Using white box testing methods the test cases that can derived are: 1) All independent paths with in a module have been exercised at least once. 2) Exercise all logical decisions on their true and false sides. 3) Execute all loops at their boundaries and within their operational bounds.
47
48
It is useful for selecting test paths of a program containing nested if and loop statement. This approach is effective for error detection. However, the problems of measuring test coverage and selecting test paths for data flow testing are more difficult than the corresponding problems for condition testing.
TESTING STRATEGIES
A strategy for software testing integrates software test case design methods into a well planned series of steps that result in the successful construction of software. A software testing strategy should be flexible enough to promote a customized testing approach. UNIT TESTING Unit testing focuses verification efforts on the smallest unit of software design. It is white box oriented. Unit testing is essentially for verification of the code produced during the coding phase and hence the goal is to test the internal logic of the module. A module is considered for integration and use by others only after it has been unit tested satisfactorily. 1) The module interface is tested to ensure that information properly flows in and out of program. 2) Local data structure is examined to ensure that data stored temporarily maintain its integrity. 3) Boundary conditions are tested to ensure that modules operate properly at boundary limits of processing. 4) All independent paths are exercised to ensure all statements in a module have been executed at least once. 5) All error-handling paths are tested. NTEGRATION TESTING Integration testing focuses on design and construction of the software architecture. For example: - We followed a systematic technique for constructing the program structure that is putting them together- interfacing at the same time conducting tests to uncover errors. We took unit tested components and build a program that has been dictated by design.
49
VALIDATION TESTING
It is achieved through a series of Black Box tests. An important element of validation process is configuration review. It is intended for all the elements are properly configured and cataloged. It is also called AUDIT. SYSTEM TESTING The last high-order testing step falls outside the boundary of software engineering and into tile broader context of computer system engineering. Software, once validated, must be combined with other system element (e.g., hardware, people, and database). System testing verifies that all elements mesh properly and that overall system function/performance is achieved. It is a series of different tests whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose all work to verify that system elements have been properly integrated and perform allocated functions.
50
7. IMPLEMENTATION
After the system, has been certified by the user, it comes to be stage of implementation. It involves many issues like preparation for the change over the new system and then the actual change over. Preparation of the site and installation of the facilities, training of the staff, preparation of data files etc. are the various steps involved which might require the involvement of the system analyst, the user as well as the operational management. Depending on the size of the organization that will be involved in using the application and the risk involved in its use, systems developers may choose to test the operation in only one area of the firm with only one or two persons. Sometimes, they will run both old and new system in parallel way to compare the results.
EVALUATION
After implementing the application in the organization we evaluated the system to identify its strength and weaknesses. We evaluated along the following dimensions: 1) Operational evaluation: We assessed the manner in which the system functioned, including ease of use, response time, overall reliability and level of utilization. 2) User Admin Assessment We evaluated the attitudes of admin within the organization as well as the end-users.
51
MAINTENANCE
This is an ongoing exercise after the system has been implemented. The real life would never static. It is necessary to eliminate errors in the working system during its working life and to tune the system to any variations in its working environment. System planners must always plan for resource availability to carry out these maintenance functions. Its requirements and objectives keep changing. So shall be the system, which has been designed primarily to meet those objectives. Thus the system analyst has to keep on carrying out changes and modification into the system, a stage called normally as system maintenance. Once the software is delivered and developed, it enters in the maintenance phase. After implementation systems need maintenance. Beyond monkey testing during software development some errors may not appear. During its usage by the end-user with actual data certain errors may disclose. Therefore some residual errors or bugs remain in the system that must be removed as they are discovered. Many of these surfaces only after the system have been in operation sometimes for a long time. These errors once discovered need to be removed on an urgent basis for the smooth running of the system, leading to the software getting changed. Though maintenance is not a part of software development, it is an extremely important activity in the life of a software product. Maintenance involves understanding the existing software ( code and related documents), understanding the effects of change, making the changes-to both the code and document-testing the new parts and retesting the old part. For successful and smooth running of the system, maintenance is the prominent part of the project. Any error, which hinders the functioning of any part of the project, may lead to bad impression of the developer. There are two types of errors: Compilation error and Runtime errors. Compilation errors during coding and is to be taken care by the developer during development process. Runtime errors are those which occur during of the program. Whenever there is an occurrence of error an Error Window opens INS the middle of the screen displaying the type of error, Error Number and the nearest possible reason as to why the error has occurred. With the occurrence of this Error Window the operator should note the type of error, the error number and the description of the error and should immediately report the concerned Developer or Administrator. For example an error window which has appeared during the runtime process. Now comes the role maintenance personals. After knowing the entire details form the end-user like where or at which screen does this error occurred or what type of data was feed by the user or the point of malfunctioning. Considering this error as the main reason for the malfunctioning the programmer now re-examines all the possible factors which act behind the particular screen where error has occurred.
52
After debugging the required error the programmer itself tests the same screen or process with dummy data. Only after getting completely satisfied with problem rectification the programmer compiles and runs the program.
CORRECTIVE MAINTENANCE:
This pertains to the changes the software to correct defects.
ADAPTIVE MAINTENANCE:
Overtime, the original environment for which the web application was developed is likely to change. This maintenance results in modification to the software to accommodate changes to its external environment.
ENHANCEMENT:
As software is used, the customer/user will recognize additional functions that will provide benefit. Perfective maintenance extends the software beyond its original functional requirements.
53
8. CONCLUSION
The application can be used in different departmental stores, which manage the Customers Database, Royalty Database, Discount Calculations Database and report generation. It is useful to maintain Customers information, royalty and discount calculations, stock and control daily activities of the departmental stores like insertion of new Customer record and modifications in existing record, calculation of discount, stock maintenance and report generation etc. With small alteration we can use this system in any departmental stores based on the theme of civil canteens to maintain and control the activities of the departmental store.
54
BIBLIOGRAPHY
SR/NO. 1 2 3 4 5 6 7 8 TITLE An Introduction to Database System Software Engineering The complete reference Visual Basic 6 Programming Black Book Visual Basic Software Engineering Learn Structure Query Language Visual Basic Hand Book AUTHOR Bipin C. Desai Pressman Ivan Barose Dreamtech Press MSDN Jalote B.B.P SSI Press
55