Poon ey Tou Sry HeLree UBLICATIO Sumi Poowia 22 purpose: ‘The purpose of this document is to provide a detailed Software Requirements Specification (SRS) for the Student Admission ‘System. This system aims to automate and streamline the student admission process in educational institutions, making it efficient andconverient for bth applicants and administrate tat 4), Student Admission System Supports the student admission and registration process, the maintenance of student personal, academic and fee related data 2). Database maintained by this system usually contains the student's personal, academic and its fee related information. it focuses on storing and processing (insertion, updation) by using web pages 3). Generates student information in formatted html tables, generates the fees invoice. 4). Generate Student's Academic Detail Report. 3H cepe fae cel foot Z 6). Generate Student's Fee Deposition Status Report. 4 7). Generate Student's al student's currently deposited their fees. 8). It Stores Merit list provided by University, 1.3 Scope: ‘The Student Admission System will handle the entire admission process, starting from the submission of applications to the final selection of students. It will include features such as application submission, document verification, ment list generation, interview scheduling (if required), and final admission confirmation. + Amapplication Software it will work for‘n institute conducting a professional course like MCA/MBA under 2 governing university. SAS Manages student (personal, academic, fees) Details. Students are admitted according to the college allotted by university according to their merit in examination and their choice of college. * Activities like Updation, Creations done in the system by the System Operator will be maintained in the form of tables for auditing and maintaining the integrity of the system. 1.4 Project Requirements: + Automate manual paper work done at the time’of student's admission (Tees deposition) inthe institute, + Eliminate paper work. * Efficiently manage the student (academic, personal, fee) details. 1.5 Software Required: © Operating System: Microsoft Windows XP * Front End tools: HTML, ASP.NET ‘© Back End tools: MS Access, SQL Server 1.6 Hardware Required: sruny + CPU: Pentium Vi processor fey + RANESI2 MB ey * HDD: 40GB a * Keyboard, Monitor, Mouse, Printer Ignou Study Helper : Sunil Poonia Page 2ONL cfs Toueu ST HeLPee Peo > ts) Sumi Poowa 2. Overall Description 2.1 Feasibility Study: Itis to serve as a decision document. It has three questions to answer. Since, the present system is manual all the work is done in papers and ink by hand so it is much costly and difficult to use and to operate and it is also time consuming. So our automated computerized student admission system is much feasible, in ost, time, and efforts as compare tothe previous ‘asc epson, Ite Seamer fete, Ww ony sequin cng xe tx peat the pers whe eapeit for entering the dts ino the database vie a unetintertice provided to Mer Who nso ele to show al he data in hind tabular form soto provide intormaton requests: Mlb diigensaton iission orto tke ssn, nos requires only a single person to operate the whole system thus reduces the cost to operate the system. It is technically feasible, since the whole system is designed into the latest technologies like ASP.NET and MS Access and SQL Server which are the most recent technologies to develop web based systems and design databases. It uses the latest hardware technologies like P4 Systems so easy to operate. It is Behavioural feasible, since the system is providing a attractive user interface to the operator/end user, so he feel very easy to work onto it. Response to operator/end user is very fast and very good. Since, as we mentioned above that it requires much less amount of cost, it uses computer work So itis very fast to parte andi Ugaal for usar to wort oi) 2.2 Working of Present System: {In present, all workis done manually by hand in bulk of files which is hard to operate and hard to maintain the reports of the student presently, took admission in institute. mer 1. When the student comes in college. f 2. First of all, he/she takes admission form from reception, — - 3. Fills it and submits it into office. ‘on 4. Filled form is first checked with documents like merit ist and details ame from university and verified by an official person, if there is any mistake then itis corrected. 5. At the time of submission of it the fees is deposited by the Candidate. 6. At the time of submission of admission form enrolment no. is assigned to the candidate by the institute. 7. Candidate gets the receipt of fees deposition. 2.3 Disadvantages of Present System 4. Require much man power i.e. much éfferts, much cOst and hard to Sperate ard maintai 2. Since, all the work is done in papers so it is very hard to locate a particular student record when itis required. 2.4 Proposed System: 1. Itis automated computerized web based software system. 2. Ituses latest technologies like ASP.NET and SQL Server. 3. tis easy to operate. 4. Attractive User Interface 3. Specific Requirements 3.1 External Interfaces: List all external interfaces, such as user interfaces, hardware interfaces, and communication interfaces. 3.2 Functional Requirements: 3.2.1 User Registration and Authentication Ignou Study Helper : Sunil Poonia Page 3Joon See Tou St Here UBLICATIONS. Net Sum Poowa Course Code : MCS-014 Course Title : Systems Analysis and Design Assignment Number : 014/Assignment/2023-24 sw Maximum Marks : 100 www.pooniapublication.com fe fe s Weghage:22% won igrostecom aa Last Dates for Submission: 3st October, 2023 (For July 2023 Session aa? : 20th April 202 (For Jnuary 2024 Session) ‘Note: Ths assignment only for students, not For cll or e-upload Srv mada oF website: All reserve to "IGNOU Study Helper Ws legal io share or reupload tf anything like this found, then appropriate action wl be taken and apply copyright ACT to you. You willbe responsible for legal work, So don't shareand upload on any media, QL. Develop SRS for Student Admission System. SRS should be as per IEEE standard SRS template. Make necessary assumptions. Ans. INDEX 1. Introduction 1.1 Problem Definition 1.2 Purpose 1.3 Scope 1.4 Project Requirements 1.5 Software Requirements 1.6 Hardware Requirements 2. Overall Description 2.1 Feasibility Study 2.2 Working of Present System 2.3 Disadvantages of Present System 2.4 Proposed System 3. Specific Requirements 3.1 External interfaces 3.2 Functional Requirements 3.3 Non-Furctional Requirements 3.4 FO Diagram 3.5 Entity- Relationship Diagram. 4. Supporting Information 5. Constraints/Queries/Doubts/if a stor 6. Glossary fey : 4. Introduction Ney 1.1 Problem Definition: Today all the work at the time of admission of the students is done manually by ink and paper, which is very slow and consuming much efforts and time. It is required to Design of a Computerized Automated Student ‘Admission System, to speed up and make it easy to use system. Ignou Study Helper : Sunil Poonia Page 1ONL et Touby Sry Heres Peo ts) Sumi Poowia © Thesvsten shal allo ecminiirator, tlt and commits members tree and ereshe user accaun © Each user shall have a unique username and password for authentication purposes. ‘© Passwords shall be securely hashed and stored in the database. 3.2.2 Application Submission ‘+ Applicants shalll be able to create accounts and submit admission applications through the system. © The application form shall capture essential information such as personal details, educational background, and preferred courses. 3.2.3 Document Verification ‘© Admission staff shall verify the documents submitted by applicants and update the appliation status accordingly. 3.2.4 Application Review and Evaluation © Admission committee members shall be able to access and evaluate the applications assigned to them. ‘© Evaluation criteria and weightages shall be configurable by administrators. 12500 fet & ‘+ The'system shall generate a ment list based on the evaluation scores of applicants. # Merit list generation rules shall be defined by the admission committee. 3.2.6 Admission Decision © The admission committee shall review the Metitlist andi make admission decisions. ‘+ Applicants accepted or rejected stall be notified through the system. 3.2.7 Reporting * The system shall provide vatious reports ineluiding application status, merit list, and admission statistics ‘Administrators shall be able to export reports in common formats such as POF or Excel. 3.3 Non-Functional Requirements 3.3.1 Performance ‘© The system shall handle a minimum of 1000 concurrent users without significant performance degradation. ‘© Response tines for common tasks shall be within acceptable limits. 3.3.2 Security * User passwords nd sensitive data shall be encrypted in transit and at rest. * Role-based access contro! shall be implemented to restrict user access to authorized functionalities. 3.3.3 Reliability ‘The system shall have a robust backup and recovery mechanism to ensure data integrity and availability. 3.3.4 Usability © The user interface shall be intuitive and user-friendly, requiring minimal train tasks. for users to navigate and perform 3.3.5 Scalability ‘©The system architecture shall be designed to accommodate future growth and potential expansion to support multiple institutions. Ignou Study Helper : Sunil Poonia Page 4Poon Teuoy Stvey Here UBLICATIONS. Sumi Poowa 4. Supporting Information ‘© The system will be developed using [programming languages/technologies]. The database management system [DBMS] willbe used to store application and applcant information. © The application will be hosted on [hosting platform/infrastructure]. * The system will comply with relevant data protection and privacy regulations. 5. Constraints * The development process must adhere to the predefined budget and timeline. ‘© The system should be compatible with common web browsers and devices. Any specific hardware or software dependencies should be clearly outlined. 8. Glossary © Provide definitions for technical terms and acronyms used throughout the document. ‘Q2. Draw the DFDs upto 3” level for Student Admission System. ‘Ans. In Software engineering DFD (data flow diagram) can be drawn to represent the system of different levels of abstraction. Higher-level DFOs are partitioned into low levels-hacking More information and functional elements, Levels in DFO are numbered 0, 1, 2 or beyond. Here, we will see mainly'3 levels in the data flow diagram, which are: O-level DFO, 1- evel DFO, and 24evel DFD. O-tevel DFD: Itis also known as @ context diagram, It’s designed to be an abstraction view, showing the system asa single process with its relationship to external entities It represents the entire system as a single bubble with input and output data indicated by incoming/outgoing arrows. Registration Student Student Admission System Course Details Admin Admission Procedure ‘Study Centre are Manager Z, stuny, 44 anaiora ene eit Ignou Study Helper : Sunil Poonia Page 5Poon Teuoy Stvey Here UBLICATIONS Sum POONIA 1-tevel DFD: In L-level DFD, the context diagram is decomposed into multiple bubbles/processes. In this level, we highlight the main functions of the system and breakdown the high-level process of 0-level DFD into subprocesses. Create Profile store ~€ Regisration Admission Maste Admission Procedure Payment system Course Master see pd perform login od Admin ‘Admin system mudysentredetails ‘Studéut Zone Manager Student zoné manager First Level DFD (Data Flow Diagram) Ignou Study Helper : Sunil Pooni Page 6Reon Som Rota ail bea at ne step deeper into parts of 1-level DFD. It can be used to plan or record the specific/necessary detail about the system’s functioning.Poon ‘t+ Tone STVDY HeLPeR UBLICATIONS Sumi Poowia 3Hevel DFD: Hevel DFD goes one step deeper into parts of 2-level DFO. It can be used to specific/necessary detail about the system’s functioning, ‘Seder 8 Admission opproval dont hist Apply for adigsion Cousa 68 comme A08 C00 ‘gy l bal 1 sudent jp] BRT Stem \ aad Sac “Sunject DB rks entry Third Level DFD (Data Flow Diagram) Ignou Study Helper : Sunil Poni Page 8ON 5.13 Zouey Spy HeLPEe UBLICATIONS. of Sumi Poomia Q3. Draw ERD for a Student Admission System. Make necessary assumptions. Ans. ER Diagram $$ Ignou Study Helper : Sunil Poonia Page 9Poon 1 Touy STV HeLa UBLICATION Sumie Poon ‘Student Admission System entities and their attributes: ‘Registration Management: Attributes of registration management are Sudent_id, Pin, Passward, Image, Address. Admission Master Entity: Attributes of admission master are Enroll, C_id, $_id, Pay_id, Document. + Payment System Entity: Attributes of payment system are Pay_is, $_id, Date, Amount. + Student Zone Master Entity: Attributes of student zone master are Ad_id, S_id, Date, Query Type. © Study Center Details Entity: Attributes of study center details are Study_id, Course, Address, Student_Name, Phone_No. + Admin Entity: Attributes of admin are Ad_id, Pa * Course Master: Attributes of course master are C_| sor Sid, C id, Name, fey E.Name, Duration, Fee. 4 SESay ¢ \oms Entities: An entity is something about which the business needs to store data. An entity i a class of persons, places, objects, events or conceats about which we need to capture and store data. An entity instance isa single occurrence of an entity. Attribute: An attribute is a descriptive property or characteristic of an entity. Synonyms include element, property and field. ‘A compound attribute is one that actually consists of other attributes. Its also known asa composite attribute. An attribute “Address” is the example of compound attribute as shown in the following illustration. Relationships: A relationship is a natural business association that exists between one or more entities. The relationship may represent an event that links the entities. Cardinality: defines the minimum and maximum number of occurrences of one entity that may be related to a single ‘occurrence of the other entity. Because all relationships are bidirectional, cardinality must be defined in both directions for every relationship. Ignou Study Helper : Sunil Poonia Page 10