03-05-2013, 02:20 PM
A PROJECT REPORT ON EXAMINATION SEATING PLAN
EXAMINATION SEATING.docx (Size: 310.33 KB / Downloads: 203)
OBJECTIVE OF THE PROJECT
The objective of this Examination seating plan is to give a detail description about the requirement and need for the proposed system. This report focuses on the objectives to create a new system and identifies the necessary reasons for the change in present system with the new system. This report also explains the scope and functionality of the proposed system. The main Advantage of this system to reduce the work. Simply help to plan for seating the all students in the examination rooms.
INTRODUCTION OF PROJECT
The purpose of this examination seating planning is to describe all the requirements for the Examination in charge .The intended audience include in the potential system. These include, but are not necessarily limited to, the following: Exam center, date sheet, roll list and room list. We are consult this examination seating planning and its revisions as the only source of requirements for the project. They should not consider any requirements statements, written or verbal as valid until they appear in this document or its revision.
The examination management and its team members should use this document and its revisions as the primary means to communicate confirmed requirements to the development team. The development team expects many face-to-face conversations that will undoubtedly be about requirements and ideas for requirements. Please note that only the requirements that appear in this document or a future revision, however, will be used to define the scope of the system.
PROBLEM DEFINITION AND REQUIREMENT SPECIFICATION:
Problem Definition
The problem is to design a new application system for a Examination Seating Planning in college which has working requirements of recording their Seating plans center name, date sheet, roll list, room list and students records, teachers records.
The need of the organization is to get a system which is automated and easy to use and efficient in recording to all students seating plan.
Software Requirement Specification
This document is a Software Requirements Specification (SRS) for examination sitting planning .It describes the functions, goals and tasks that the system can perform. Software Team Development will use this document to describe the scope of the project and to plan for the system’s design and eventual implementation. The document lists the following features as the high-level requirements that the Examination sitting planning will satisfy:
• Examination center – assigning college for students and teachers to university.
• Date sheet- assigning for students and teachers to university.
• Roll list- provide by university for students.
• Room list-provide by college.
• Floor- in college may be many floors.
The document also presents a number of requirements that can be classified into two Categories functional and non-functional requirements. Non-functional requirements can be used to improve the functioning of the computer system, but not the Planning of Seating in Examination as a whole. For these requirements, Software Team Development recommends that the Examination Seating planning System a set of experts from their computer department and their legal department to formally accept the requirements. The primary areas of concern Are performance, security and user-interface. Functional requirements, on the other hand, are Requirements directly related to the Examination Sitting Planning Software Team Development Inc.
ANALYSIS:
Scenario
The present working of the organization is outdated the methodologies used in the working of organization is traditional and is not efficient. Presently the organization is recording all its all information of sitting planning on paper documents and books which is old method of recording of all information. The present system is slow and involves too much clerical and official work which is prone to errors and unorganized manner of recording college data the present system do not support updating and edition to the existing system the whole work is to be carried again in case of any changes to be made.
Design Pattern:-
Designing is the most important part of the software development. It requires a careful planning and logical thinking on the system designer. Designing a software means to plan how the various parts of the software are going to achieve the desired goal. It should done with the utmost care because if this phase contains any errors then that will be going to affect the performance of the system, as a result it may take more processing time, more coding, extra work load etc.
As the software is to be designed in SQL Server, the concept of the database is must for quality designing. It will be designing of the database, designing of forms, designing of reports.Separate tables have been created for each entity of the system. In order to make the response time negligible, all the tables have been created in the Memory File System. Moreover indexes have been created on the tables in the number of records have been made random.
IMPLEMENTATION OF PROPOSED SYSTEM
The proposed system is to design an application program for the Examination Sitting Planning System. This is required to make the working process of the organization easy and fast. The proposed system is really going to prove a helpful tool for recording all information of the college in a systematic manner all the records can be stored in a tabular form through tables which enables ease of retrieval of data and information.The proposed system is much better in working and efficiency than the current system.
FEATURES OF RDBMS SERVER
SQL Server is one of the leading database management systems (DBMS) because it is the only Database that meets the uncompromising requirements of today’s most demanding information systems. From complex decision support systems (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry in both performance and capability SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous operation and support for every database
Distributed Data Sharing
MS Access networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was stored on a single local computer. You can store data where system requirements such as performance, security or availability dictate Unmatched Performance.The most advanced architecture in the industry allows the MS Access DBMS to deliver unmatched performance.
No bottlenecks
MS Access fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, MS Access commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential writes triple transactions. Data read by typically group commit the transaction remains as shared memory so that other transactions may access that data without reading it again from disk. Since fast commits write all data necessary to the recovery to the log file, modified blocks are written back to the database independently of the transaction commit, when written from memory to disk.
Requirement Analysis
Requirement analysis is done in order to understand the problem the software system is to solve. The problem can be automating an existing manual process ,developing a new automated system or a combination of these two .For a large system that have many features and that need to perform major task .The emphasis in requirement analysis is on identifying what is needed from the system and how the system will its achieve goal. This task is completed by the fact that there are often at least two parties involved in software development, a client and a developer. A developer has to develop the system to satisfy the client’s need.
The developer usually does not understand the client’s problem domain and the client often does not understand. The technical issues involved in the system development .this causes a combination which has to be bridge during requirement analysis. The most software projects the requirement analysis phase ends with a document describing all the requirement .In other word the goal of requirement specification phase is to produce the software requirement specification (SRS) document >the person responsible for requirement analysis is called the analyst .
Coding
Once the design is complete most of the major decision about the system has to be made. However ,many of the details about coding and designs which often depends on the programing language chosen are not specify during design .The goal of the coding phase is to translate the design of the system in to code in a given programing language .
The coding phase product affects later phases like testing and maintenance A well return code can reduce the testing and maintenance effort. Because the testing and maintenance cost are much higher than coding cost .The goal of coding is to reduce the testing and maintenance efforts .Hence during coding the focus should be on developing program that are easy to understand .Simplicity and clarity should be there in coding phase.
Testing
Testing a program consist of providing the program with asset of test inputs or test cases as expecting .Testing is a quality measure used during software development .Its basic function is to detect errors in software .During requirement analysis and design ,the output is a document i.e. usually textual or not executable .After the coding phase computer programs are available that can be executed for testing purpose it means the testing not only has to uncover error during coding but also errors introduced during previous phases. The starting point of testing is unit testing. is this a module is tested separately and is often perform by the programmer himself simultaneously along with the coding of module. After this the modules are gradually integrated into subsystems which are again integrated to form the entire system.
Maintenance
Once the software is delivered it enters the maintenance phase. Software needs to be maintain not because some of its components wear out and need to be replaced but because there are often some of errors remaining in the system that must beremoved as they are delivered . These errors once discovered need to be remove leading to the software getting changed, this type of maintenance is called corrective maintenance.
Even without errors the software frequently undergoes changing. The main reason is that the software must be upgraded to introduce more features and provides more services. This also requires modification of the software. The changed software then changes the environment which in turn requires further changes. This phenomenon is called law of software evolution and maintenance due to its phenomenon is called adaptive maintenance. Like any system, there is an aging process that requires periodic maintenance of hardware & software. If new information is inconsistent with design specifications, then changes have to be made. Hardware also requires periodic maintenance to keep in tune with design specifications. Often the need arises to capture additional data for storage in a additional database or perhaps when it is necessary to add error detection features to prevent system users from inadvertently taking an unwanted action. The importance of maintenance is to continue to bring the new system to standards.
Automatic memory management
Java uses an automatic garbage collector to manage memory in the object lifecycle. The programmer determines when objects are created, and the Java runtime is responsible for recovering the memory once objects are no longer in use. Once no references to an object remain, the unreachable memory becomes eligible to be freed automatically by the garbage collector. Something similar to a memory leak may still occur if a programmer's code holds a reference to an object that is no longer needed, typically when objects that are no longer needed are stored in containers that are still in use. If methods for a nonexistent object are called, a "null pointer exception" is thrown.
One of the ideas behind Java's automatic memory management model is that programmers can be spared the burden of having to perform manual memory management. In some languages, memory for the creation of objects is implicitly allocated on the stack, or explicitly allocated and deallocated from the heap. In the latter case the responsibility of managing memory resides with the programmer. If the program does not deallocate an object, a memory leak occurs. If the program attempts to access or deallocate memory that has already been deallocated, the result is undefined and difficult to predict, and the program is likely to become unstable and/or crash. This can be partially remedied by the use of smart pointers, but these add overhead and complexity. Note that garbage collection does not prevent "logical" memory leaks, i.e. those where the memory is still referenced but never used.