Scribd
Upload
58 views

MCS-014 Solved Assignment

The document provides a software requirements specification for a student admission system according to the IEEE standard template. It includes sections on introduction, overall description, specific requirements, and appendix. The SRS covers the entire student admission process from application submission to admission confirmation.

Uploaded by

md7481920
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
58 views

MCS-014 Solved Assignment

The document provides a software requirements specification for a student admission system according to the IEEE standard template. It includes sections on introduction, overall description, specific requirements, and appendix. The SRS covers the entire student admission process from application submission to admission confirmation.

Uploaded by

md7481920
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

-

Q.1 - Develop SRS for Student Admission System. SRS should be as per IEEE
standard SRS template. Make necessary assumptions.
ANS.- Software Requirements Specification (SRS) for Student Admission System
1. Introduction
2. 1.1 Purpose The purpose of this document is to provide a detailed
Software Requirements Specification (SRS) for the Student Admission
System. This system aims to streamline and automate the student
admission process in educational institutions, facilitating efficient
management of admission applications and ensuring a smooth and
transparent process for both students and administrators.
1.2 Scope The Student Admission System will cover the entire student
admission process, from the submission of applications to the final selection
of candidates. It will include modules for application submission, document
verification, merit list generation, fee payment, and admission confirmation.
1.3 Definitions, Acronyms, and Abbreviations
• SRS: Software Requirements Specification
• GUI: Graphical User Interface
• DBMS: Database Management System
1.4Assumptions and Dependencies
• It is assumed that the institution already has the necessary infrastructure
in place, including hardware and a reliable network.
• The system will be web-based, and users will require a modern web
browser to access the application.
• The Student Admission System will be integrated with an existing student
database, where necessary data (such as courses offered, faculty
information, etc.) is already available.
• Users (both students and administrators) are assumed to have basic
computer literacy.
• The system development team will use a widely accepted web
development framework and relational database management system.

2. Overall Description
2.1 Product Perspective The Student Admission System will be a standalone
web application, interacting with the institution's existing databases for
relevant information. It will be developed using a client-server architecture,
where the client (users) interacts with the server (application) through a web
browser.
2.2 Product Features The key features of the Student Admission System
include:
• Student Registration: Prospective students can create accounts and
provide their personal details and academic history.
• Application Submission: Students can submit their admission
applications online for the desired courses.
• Document Verification: The system will verify the submitted documents
to ensure their authenticity.
• Merit List Generation: Based on predefined selection criteria, the system
will generate
Merit lists for each course.
• Fee Payment: Selected candidates can pay their admission fees through
the system.
• Admission Confirmation: Students can confirm their admission status
through the system.
• 2.3 User Classes and Characteristics The Student Admission System will
have the following user classes:
• Prospective Students: They will apply for admission to various courses
and view their application status.

• Admission Officers: They will be responsible for verifying documents and


managing the admission process.
• Administrators: They will have overall system administration rights,
managing user accounts and system settings.
2.4 Operating Environment The system will be accessible through modern web
browsers such as Google Chrome, Mozilla Firefox, and Microsoft Edge. It will be
developed using technologies like HTML, CSS, JavaScript, and will be hosted on
a web server.
• The system will ensure data security and privacy compliance, protecting
sensitive student information.
• It will be designed with a user-friendly interface to enhance usability for
all user classes.
• The system will be scalable to accommodate a growing number of
admission application
3. Specific Requirements
3.1 External Interface Requirements 3.1.1 User Interfaces The system will have
an intuitive and responsive Graphical User Interface (GUI) accessible via web
browsers. It will include pages for registration, login, application submission,
fee payment, and admission status.
3.1.2 Hardware Interfaces The system will be accessible through devices with
internet connectivity, such as desktop computers, laptops, tablets, and
smartphones.
3.1.3 Software Interfaces The Student Admission system will interact with the
existing student database to fetch relevant information during the admission
process.
3.2 Functional Requirements
1. User Registration
• Prospective students can create accounts by providing essential details.
THE
• The system shall validate and store the registration information.
2. Application Submission
• Students will be able to select the desired course and submit the
admission application along with necessary documents.
• The system shall store the application and associated documents
securely.
3. Document Verification
• Admission officers can access and verify the submitted documents.
• The system shall mark the verification status for each application.
4. Merit List Generation
• The system will apply predefined criteria to generate a merit list for each
course.
• The merit list shall be made available to students and administrators.
5. Fee Payment
• Selected candidates will be able to view the admission fee details and
make payments securely through the system.
• The system shall provide payment confirmation to the students.
6. Admission Confirmation
• Students can check their admission status and confirm their acceptance
through the system.
• The system shall update the student's admission status accordingly.
3.3 Non-Functional Requirements
1. Performance
• The system shall handle a minimum of 500 concurrent users without
significant performance degradation.
• Response times for critical operations shall be within 2 seconds.
2. Security
• User authentication shall be performed securely with proper encryption
mechanisms.
3. Usability
• The GUI shall be intuitive and user-friendly, requiring minimal training for
users.
• Error messages shall be clear and informative to assist users in correcting
input mistakes.
4. Reliability
• The system shall have regular backups of data to prevent data loss in
case of system failures.
5. Scalability
• The system architecture shall be designed to accommodate a growing
number of admission applications
4. Appendix (Include any additional information that may be relevant to the
SRS)
This SRS document provides a comprehensive overview of the Student
Admission System's requirements. The development team will use this
document as a blueprint to design, implement, and test the system to meet the
institution's admission process needs.

Q.2 - Draw the DFD upto 3rd level for Student Admission System.
ANS.- Data Flow Diagrams
A DFD can be categorized in the following forms:
Context diagram: An overview of an organizational system that shows the
system boundaries, external entities that interact with the system and the
major information flows between the entities and the system. In this diagram,
a single process represents the whole system.
First level DFD: A data flow diagram that represents a system's major
processes, data flows, and data stores at a high level of detail.
Draw the DFDs upto 2nd level for Online Examination System.
Figure:- Level 0

Figure:- Level 1
Figure:- Level 2
Q.3 - Draw ERD for Online Admission System for a University. Make
necessary assumptions.
ANS.-
ER Diagram
Notations for the components of ERD:
Entities: An entity is something about which the business needs to store
data. An entity is a class of persons, places, objects, event or concepts about
which we need to capture and store data. An entity instance is a 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. It is also known as a 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.
Draw ERD for Online Examination System. Make necessary assumptions.
Figure:- ERD

You might also like