INDEX SNO TOPIC PAGE NO o1 Introduction 01-04 02 A System Requirements and| Specifications 05-07 03 Feasibility Study 08-10 04 Technology 11-12 System design and os {implementation 13-19 06 Outputs And Testing & 20-31 Screen shots 7 Future Scope 32-33 “ Bibliography 34-35INTRODUCTIONINTRODUCTION: This Hostel Management System is developed in favor of the hostel management team which helps them to save, the records of the students about their rooms and other things. It helps them from the manual work from which itis very difficult 10 find the record Of the students and the information about those ones who had left the hostel years before, This solution is developed on the plight of the hostel management team, through this they cannot require so efficient person to handle and manage the affairs of the students in the hostel, all you need to do is to login as administrator and you can see the information of all the students who have obtained and registered their hostel form, click verify to ascertain their cligibility and allocate them to the available hostel, Identification of the problems of the existing hostel management leads to the development of computerized solution that will be compatible to the existing hostel management with the solution which is more users friendly, and more GUI oriented, We can improve the efficiency Of the hostel management, thus overcome the drawbacks of the existing management, Objectives: The main objectives of this project work are that: Student will no longer apply for their hostels manually. © ‘The warden can see and access the student's data, © This also will reduce the manual work of the persons in admin penal © ‘helps the admin to know the number of students that can leave in a room and a block, + To ensure that the number of student staying in a room does not exceed specified limit, « Help the admin to disseminate information to students without calling for a meeting or moving room b room. © 1o know the number of items (e.g. bed) given to student staying in the hostel « To ensure that student remit the hostel property given to them before vacating the hostel, The system helps the admin to: « Allot different students to their different hostels. « Vacate the student from the hostels + Control the status of the hostel fee payment. © Ldith the details of the students and modify the students records © Rufus Giwa Polytechnic has eleven hostels, which consist of five boy's hostels and six girl's hostels. All these hostels at present are managed manually by the hostel officer. Thus, there are a lot Of duplications which cannot be easily avoided Hence, there is lot strains on the hostel management due to the manual processes presently in used.AIM: This Hostel Management System is developed in favour of the hostel management team which helps them to save the records of the students about their rooms and other things. It helps them from the manual work from which it is very difficult to find the record of the students and the information about those ones who had left the hostel years before Advantages: ° ° ° Less error. Strain of manual labor is not needed. High security. Easy to handle. Easy to update data. User friendly. More GUI oriented. Disadvantages: More human error. More strength and strain of manual labor needed. Low security. Difficult to handle. Difficult to update data.SYSTEM REQUIREMENTS AND SPECIFICATIONSYSTEM REQUIREMENTS SPECIFICATION Hardware Specification : For a system to be used efficiently and accurately, all computer software needs certain hardware components or other software resources to be present on a computer. These prerequisites are known as (computer hardware specification) and are often used as a guideline as opposed to an absolute rule. Most software defines two sets of system requirements: minimum and recommended. With increasing demand for higher processing power and resources in newer versions of software, system requirements tend to increase over time. Industry analysts suggest that this trend plays a bigger part in driving upgrades to existing computer systems than technological advancements. A second meaning of the term of System requirements is a generalization of this first definition, giving the requirements to be met in the design of a system or sub-system, Typically,an organization starts with a set of Business requirements and then derives the System requirements from there. The most common set of requirements defined by any operating system or software application is the physical computer resources, also known as hardware, a hardware requirements list is often accompanied by a hardware compatibility list (HCL), especially in case of operating systems. An HCL lists tested, compatible, and sometimes incompatible hardware devices for a particular operating system or application. The following sub-sections discuss the various aspects of hardware requirements for this application software The hardware required includes the following: 1.Hardware Requirements: PC with Intel Dual Core processor. 512 MB RAM or above. 40 GB Hard Disk or above. VGA COLOR MONITOR KEYBOARD MOUSE 2.Software Specification This are requirements specification for a software system, is a description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition, it contains requirements. on-functional requirements impose constraints on the design or implementation such as performance engineering requirements, quality standards Software requirements specification establishes the basis for agreement between customers and contractors or suppliers (in market-driven projects, these roles may be played by the marketing and development divisions) on what the software product is to do as well as what it is not expected to do.Software requirements specification permits a rigorous assessment of requirements before design can begin and reduces later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules. The software requirements specification document enlists enough and necessary requirements that are required for the project development. To derive the requirements, we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software The software components used for this project are listed below: oftware Requirement O Operating system: Windows XP (or latest), © Front end “Cc LANGUAGE © Platform CC LANGUA GE o Backend + C LANGUA GEFEASIBILITY STUDYFeasibility: The feasibility of the project is analyzed that this phase and business proposal is Put forth with a very general plan for the prove and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. is is to ensure that the proposed system is not a burden to the company, For feasibility analysis, some understanding of the requirements for the system is essential. Three key considerations involved in the feasibility analysisare 1, ECONOMICAL FEASIBILITY 2. TECHNICAL FEASIBILITY 3. SOCIAL FEASIBILITY ECONOMICAL FEASIBILITY: This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited, The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.’ TECHNICAL FEASIBILITY: This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.SOCIAL FEASIBILITY: The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism which is welcomed, as he is the final user of the system.TECHNOLOGYOVERVIEW OF TECHNOLOGY: C-LANGUAGE OBJECTS: Programming languages like C++ and Java have built-in support for OOP concepts. However, did you know that you don't need to use an OOP language in order to use OOP style and get some of the benefits of object-oriented programming? In this tutorial, I will explain how we can bring some of the style of object-oriented programming to C, a language without built-in OOP support, Simple, non-polymorphic types: Let us consider a simple class that cannot be overriden (has no virtual methods): There are a number of important points to note about this translation. Firstly, we don't specify the full definition of "Point" in order to achieve encapsulation; we keep "x" and "Y' effectively "private" by defining "Point" fully only in the source file. Secondly, we create functions that correspond to the constructor/destructor plus allocation/deallocation which replace "newt and "delete". Thirdly, all member functions get an explicit "self parameter of the type being operated on (which replaces the implicit "this" parameter). The patterns that apply to simple objects are also applied to other types of objects, but we add some enhancement to address concepts like polymorphism and inheritances Polymorphic types. RELATIONSHIP In a relational database, the data in one table is related to the data in other tables. In general, tables can be related in one of three different ways: one-to-one, one-to-many or many-to-many. The relationship is used to cross reference information between tables. * One-to-One: In a one-to-one relationship each record in one table has at most one related record in another table. © One-to-Many: A one-to-many relationship often referred to as a "master-detail" or “parent- child" relationship. + Many-to-Many: In a many-to-many relationship, a record in Table A can have many matching records in Table B, and a record in Table B can have many matchingSYSTEM DESIGN AND IMPLEMENTATIONSYSTEM DESIGN: Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. Design is the first step in the development phase for any engineered product or system. The designer's goal is to produce a model or representation of an entity that will later be built. Beginning, once system requirement, have been specified and analyzed, system design is the first of the three technical activities -design, code and test that is required to build and verify software, The importance can be stated with a single word “Quality". Design is the place where quality is fostered in software development. Design provides us with representations of software that can assess for quality. Design is the only way that we can accurately translate a customer's view into a finished software product or system. Software design serves as a foundation for all the software engineering steps that follow. Without a strong design we risk building an unstable system — one that will be difficult to test, one whose quality cannot be assessed until the last stage. During design, progressive refinement of data structure, program structure, and procedural details are developed reviewed and documented. System design can be viewed from either technical or project management perspective. From the technical point of view, design is comprised of four activities architectural design, data structure design, interface design and procedural design. E- R Diagrams + The relation upon the system is structure through a conceptual ER-Diagram, which not only specifics the existential entities but also the standard relations through which the system exists and the cardinalities that are necessary for the system state to continue. + The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD is the notation that is used to conduct the date modelling activity the attributes of each data object noted is the ERD can be described resign a data object descriptions. + The set of primary components that are identified by the ERD are > Data object > Relationships > Attributes > Various types of indicators. The primary purpose of the ERD is to represent data objects and their relationships.DATA FLOW DIAGRAMData Flow Diagrams: A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DED is labelled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFD'S is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD. ‘The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail js described for analyst to understand the process. Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design. ‘A DED is also known as a "bubble Chart" has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system. 1.Student account creation Field Name Data Type Description Name Varchar Name of the student Branch Varchar Branch of the student User id int User id of the student Password Varchar Password to useRe type Varchar Repeating It password 2. Administrator Login: Field Name Data Type Description Username Int Username Of the student Pass Varchar Password of the student 3.Application form: Field Name Data Type Description Index No Int ‘A unique no given to student Course Varehar Course of stud Semester Int Semester Of study ‘Course-name Varchar Type of course Date-admit Date Date of course admission Date-end Date End of course Date-host-admit Date Date of hostel admission Local Address Longtext ‘Address of student Permanent Address Longtext |Address of guardian Distance Int Instance om home4.Allotment: Field Name Data Type Description Room no. Int ‘A unique no green to student Name Varehar Name of the student. Index no. Int ‘Age of the student Date admission Date Date of bull of the student Sex Varchar Sex of the student Reservation Varehar caste of the student 5.Vacating and editing: O 7 Field Name Data Type Description Room no. Int A unique no given to student Name Varchar Name of the student. Index no. int ‘Age of the student Date admission’ date Date of birth of the shident Sex Varehal Sex of the student Reservation Varchar Caste of the student6.Notice Board: Field Name Data Type Description Title varchar The title of the notice Contents, varchar It includes the different notice descriptions IMPLEMENTATION: Implementation is the stage where the theoretical design is turned into working system. The most crucial stage in achieving a new successful system and in giving confidence on the new system for the users that it will work efficiently and effectively. The system can be implemented only after thorough testing is done and if it is found to work according to the specification. It involves careful planning, investigaton of the current system and its constraints on implementation, design methods to achieve the change over and an evaluation of change over methods a part from planning. Two major tasks of preparing the implementation are education and training of the users and testing of the system. The more complex the system being implemented, the more involved be the system analysis and design effort required just for implementation.OUTPUT & TESTINGSOURCECODE: Administrator account with Database connectivity =1) Snum=mysql_num rows($res) « If($num>0) $_SESSION['p: $_SESSION{[(‘user’ + Header(“location:admin_home.php”); I else $flag: Smsg="wrong username or password"; JAVASCRIPT VALIDATION CODE function validate(f) If((f.user.value=="")II(f.user.value.length<5)) alert("please enter a valid password"); f.pass.focus(); return false; return true; Editing Student details open(); //accepting values from form and inserting them into database Iffisset($_ REQUEST[‘edit’))) { //receives data from current form Syear=§_REQUEST| ‘year’; Smessage=For”._” Syear.""."Batch"; $table=$year.'r'; $f2=0; $table_a=$year.'a’; SELECT* FROM Stable a”; $result=@mysql_query($sql); Stotal_num=@mysql_num_rows(Sresult); If($total_num<=0) Sf Sresult=@mysql_query($sql); $total_num=@mysqt_num rows(Sresult); If(Stotal_num<=0) { $f2=1; } $s_code=substr(Ssem, 1,1): $stud_num=$_REQUEST[‘stud_num’}; for($i=l;$i<=$stud_num;$i++)$id[SI]-$_POST[‘id."ST]; $roll_no[SI]-S_POST[“roll_no”SI]; $reg_no[SI]-$_POST[“reg_no”SI]; $name{Si]-$_POST|‘name’ $i]; $email[Si]-$_POST[‘email’ Si]; t for(Si=I;Si<=Sstud num;$i++) ( Ssql+"UPDATEStable SET Roll_no=’ {Sroll_no[SI]},reg_no=’ {$reg _nofSi]}’, name {Sname[Si]}””; Email=’ {Semail[SI]}’ WHERE id=" {Sid[SI]}"”; $con- >update($sql); If($f1==0) SET roll_no~’ {Sroll_no[$i]’,name={Sname[Si]}’ WHEREid~’ {Sid$i]}””; Scon->update($sql_i); } } header("location:stud_edit.php?year={Syear}"); } iffisset($_REQUEST[‘delete’])) Svear-S. REQUESTI'years $table=Syear.'r'; $sql="DROPTABLEStable”; @mysql_query($sql); header("location:admin_home.php"); } ?> Storing values from databaseWhile($row=@mysql_fetch_array(Sres ult) { Sid[Si]-Srow[ ‘id’; Sroll_no[$i]-Srow[‘roll_no’]; $reg_no[Sil=Srowl'reg _no']; Sname[Sil=Srow['name’); Semail[$i]=Srow[‘email’}; Including a file WELCOME FUNCTIONS: PHP MY ADMIN: '& running on jecainest - phpMyAdmin 223 - Mesila rete Lo ee Eile Edt View Histery Beokmarks Tock Help @ -c¢ > tmp seater phermyadoin co 2 be Most Visited @ Getting Stated jh Latest Headines eae Welcome to phpMyAdmin 2.2.3 hms (2) + mysql (6) ySQL 3.23.47-max-debug running on localhost as root@ocalhost = test) mysau Phelan * create new Language Engish (en) ~ satane[Docurertion] 5. A amin documentation eae Shaw PHP information ate | ' ‘aca pillar Haciggs Show MySQL rnb Souretorge pop Asren Down Pape Documentation) {ChangeLog} [CVS] [ust Show MySQL system erate PDocerantaen} Show processes Docutenond Retoad nySQL [Decumertatn) * Users [Documentation] " Databases statistics 25Administration: pspewpeeDey. poco) fs mysal (e Se Database hostel - table adm_account rur [Browse | [Select] [loeert) vp {Drop 1 Fleld Type Armiintes Null Detautt Exe Ou we No st jars Dl use varchargo) Ne peer varemareo) Ne 1D pass_+ varchar) Ne Te wa cto o pac Indevar[Documsetaton om Keyname Type Catdinally Aeon Field gY PRIMARY PRIAARY 2 depend Oat 1 coturons (2) = 26PRESes Registration Database 14 nam fathnam —guardisn course yeaduim sex tes pad) peadd dat Delete | {Sram ath nam —(Squard —[Seours {Hyr_admn [Sse [Sese [Sperm ot (Spres_sdd iD a DD (si) Delete Desete 2ait Edit ait Edit Eait Esit ait Edit uit Eait ai Edit eit edit Delete Delete Delete Delete Delote De Dotote Delete Delete Dolote Delete Delete Delete Delete 107 10 112 113 116 Es o ° a a o o o 0 o o o o ° 0 2P°e000 2 foo 000 P2282 00D GG oe ooTESTING Unit Testing: © Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors. © These types of tests are usually written by developers as they work on code (white- box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corer cases or other branches in the code, Unit testing alone cannot verify the functionality of a piece of software, but rather is used to ensure that the building blocks of the software work independently from each other. ® Unit testing is a software development process that involves synchronized application of a broad spectrum of defect prevention and detection strategies in order to reduce software development risks, time, and costs. It is performed by the software developer or engineer during the construction phase of the software development lifecycle. Rather than replace traditional QA focuses, it augments it. Unit testing aims to eliminate construction errors before code is promoted to QA; this strategy is intended to increase the quality of the resulting software as well as the efficiency of the overall development and QA process. @ Depending on the organization's expectations for software development, unit testing might include static code analysis, data-flow analysis, metrics analysis, peer code reviews, code coverage analysis and other software verification practices. Integrated Testing: Integration testing is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. Some different types of integration testing are big-bang, top-down, and bottom-up, mixed and risky- hardest. Other integration patterns are collaboration integration, backbone integration, layer integration, client-server integration, distributed services integration and high-frequency integration. »FUTURE SCOPEFUTURE SCOPE This application avoids the manual work and the problems concern with it. It is an easy way to obtain the information regarding the various account holders. Well | and my team members have worked hard in order to present better bank management system to provide information about the various activities. Still, we found out that the project can be done in a better way. Primarily, when we give the account number of a customer, the account details and transaction will be shown. And next the amount can be transferred between two accounts. The next enhancement that we can add the dates and transfers. We can specify account type and transaction enhancements. And that to the project can be developed in PHP/HTML. These are the two enhancements that we could think of at present. atBIBLIOGRAPHY BIBLIOGRAPHY 1. http://www.researchgate.net> publication 2. http://www.slideshare.net> unsajawaid 3. www.monstercrawler.com (3schools.com 4. ww)