The document provides a software requirements specification (SRS) for a library management system. It includes sections on the purpose and scope of the system, user requirements, system functions, and design constraints. The system will allow librarians to manage the library catalog and user accounts, and allow users to search for books, view their accounts, and borrow books. It will be a web-based system compatible with major browsers that integrates with a Microsoft SQL database. Non-functional requirements like security, performance and error handling are also addressed.
The document is a software requirements specification for a Water Management Portal. It includes sections that provide an introduction and overview, describe the overall system and specific requirements. The introduction describes the purpose of creating a web application to allow users to report water-related issues, view information, and allow city employees to update statuses. The overall description outlines the system interfaces, hardware requirements, communication methods, and constraints. It also includes use case and entity relationship diagrams. The specific requirements section describes use cases for different user types: visitors, administrators, city employees and residents.
The Fruit Bazaar System allows users, administrators, and shipping agents to interact. Users can log in, add items to their cart, and check out to place orders. Administrators can log in with privileges to modify the catalog, maintain user data, and process orders. Shipping agents deliver ordered items from the warehouse to customers.
The document describes a proposed student attendance management system. The system aims to automate and computerize the traditional paper-based process of taking student attendance. Key features include allowing teachers to take attendance digitally by selecting students' names from a displayed list, generating reports on attendance data, and identifying students who are regularly absent or below attendance thresholds. The system is intended to streamline the attendance process and make attendance data more easily accessible and analyzed and reports automatically generated.
The document is a software requirements specification (SRS) for a new online booking system for Cool Ski Resorts. It provides an overview of the project, outlines the system features and user requirements. Key aspects include: allowing customers to book rooms, equipment and classes online; managing inventory, payments and financial reports; and improving work efficiency for staff. The system is intended to digitize current paper-based processes and provide a better experience for customers.
This document describes a proposed library management system. It outlines the purpose of the system as making the existing manual system more efficient and user friendly. It notes some problems with the current system like difficult book tracing and lack of a central database. The aims and objectives of the new system are to eliminate paper work, record all transactions digitally, and have a user friendly interface. Functional requirements include librarian and student login, updating member and book details, and book issue/return. The system will also have non-functional requirements. Use cases and class, sequence, and data flow diagrams are proposed to be created.
The document discusses the development of a web-based hotel management system. It aims to automate the key activities of a hotel like room management, customer admission, room allocation, billing etc. to make the process more efficient. The system will have two types of users - online users who can view information and administrators who can manage the records. The development will follow a waterfall model and use PHP and MySQL. It analyzes the requirements, hardware and software needs, and provides a Gantt chart to plan the project timeline over 17 weeks.
Flipkart Software requirements specification SRS for an e commerce online Web store. It contains actual format and contents for a SRS Synopsis. How Flipkart manages online store.
The document provides a software requirements specification (SRS) for a library management system. It includes sections on the purpose and scope of the system, user requirements, system functions, and design constraints. The system will allow librarians to manage the library catalog and user accounts, and allow users to search for books, view their accounts, and borrow books. It will be a web-based system compatible with major browsers that integrates with a Microsoft SQL database. Non-functional requirements like security, performance and error handling are also addressed.
The document is a software requirements specification for a Water Management Portal. It includes sections that provide an introduction and overview, describe the overall system and specific requirements. The introduction describes the purpose of creating a web application to allow users to report water-related issues, view information, and allow city employees to update statuses. The overall description outlines the system interfaces, hardware requirements, communication methods, and constraints. It also includes use case and entity relationship diagrams. The specific requirements section describes use cases for different user types: visitors, administrators, city employees and residents.
The Fruit Bazaar System allows users, administrators, and shipping agents to interact. Users can log in, add items to their cart, and check out to place orders. Administrators can log in with privileges to modify the catalog, maintain user data, and process orders. Shipping agents deliver ordered items from the warehouse to customers.
The document describes a proposed student attendance management system. The system aims to automate and computerize the traditional paper-based process of taking student attendance. Key features include allowing teachers to take attendance digitally by selecting students' names from a displayed list, generating reports on attendance data, and identifying students who are regularly absent or below attendance thresholds. The system is intended to streamline the attendance process and make attendance data more easily accessible and analyzed and reports automatically generated.
The document is a software requirements specification (SRS) for a new online booking system for Cool Ski Resorts. It provides an overview of the project, outlines the system features and user requirements. Key aspects include: allowing customers to book rooms, equipment and classes online; managing inventory, payments and financial reports; and improving work efficiency for staff. The system is intended to digitize current paper-based processes and provide a better experience for customers.
This document describes a proposed library management system. It outlines the purpose of the system as making the existing manual system more efficient and user friendly. It notes some problems with the current system like difficult book tracing and lack of a central database. The aims and objectives of the new system are to eliminate paper work, record all transactions digitally, and have a user friendly interface. Functional requirements include librarian and student login, updating member and book details, and book issue/return. The system will also have non-functional requirements. Use cases and class, sequence, and data flow diagrams are proposed to be created.
The document discusses the development of a web-based hotel management system. It aims to automate the key activities of a hotel like room management, customer admission, room allocation, billing etc. to make the process more efficient. The system will have two types of users - online users who can view information and administrators who can manage the records. The development will follow a waterfall model and use PHP and MySQL. It analyzes the requirements, hardware and software needs, and provides a Gantt chart to plan the project timeline over 17 weeks.
Flipkart Software requirements specification SRS for an e commerce online Web store. It contains actual format and contents for a SRS Synopsis. How Flipkart manages online store.
A presentation detailing a Library Management System (LMS) Project for a Medical Research Council. The function of the Library is to organize and account for all the materials (Books, Journals, Magazines, Publications and Thesis) in the Library.
The system makes use of a Bar coding system to identify materials; used when checking in items.
Martins Jr.
The document is a software requirements specification (SRS) for a student biometric identification system (BSI). It outlines the system's overall description, user characteristics, and specific functional and non-functional requirements. The BSI will use biometrics like fingerprints to automate student identification at entry/exit points. It will interface with a database and network to identify and log check-ins/outs. The SRS defines requirements for registration, an admin panel to manage users, and reporting of daily entries. It also specifies performance, security, and other non-functional needs.
This document provides a software requirements specification for a login module system with four submodules: login, register, forgot password, and reset password. It includes functional requirements for each submodule, describing how users will interact with the system. The intended audience is developers and other stakeholders. The project scope is to create a reusable login module for authentication and authorization across applications for an ABC Company. The document describes the product features and operating environment, including interfaces and constraints.
Android Project report on City Tourist Location based services (Shuja ul hassan)Shuja Hassan
The aim to design and develop this project is to produce a
tourist guide for Skardu city, which can eefficiently guides the
tourist who visits Skardu. The Android tourist guide can be use in place of professional guide due to many reasons like reduce cost of guide, get more accurate information needed for decision making, giving weather and social networking services.The tourists can use this guide for different purposes like searching a location , calculate distance between two locations,getting basic textual information, pictorial information of location which normally we could not get in default Google maps.The guide uses Google Map API, global
positioning system( GPS), Internet and cellular data to provide
its services.
Shuja ul Hassan
IT Teacher
Android Developer
shuja2good@gmail.com
This document is a project report for an online computer shop management system. It discusses problems with current systems, outlines the proposed system which will allow users and administrators to view products, make purchases, and manage inventory. It also covers requirement collection and analysis, planning, implementation details, testing procedures, and maintenance policies for the new system. The system will be developed using PHP and MySQL to provide an online platform for buying and selling computer products and accessories.
The document provides a software requirements specification for a smart tutor application. It describes the purpose, intended users, product scope and features. The key features allow students to search and message tutors, allow tutors to accept students and update profiles, and allow administrators to manage the user database and verify tutor qualifications. The system will have mobile and web interfaces and use a client-server architecture with a Firebase database.
SRS for student database management systemSuman Saurabh
This document is a software requirements specification for a student management portal being developed for LNMIIT. It outlines the purpose, scope, functions, users and operating environment of the system. The key functions are to maintain student records and grades, allow students to view their information, and give medical officers and coaches access to relevant health and sports data of students. It will be a web-based system built using Java, PHP and MySQL that can be accessed by around 20 staff, 1 administrator and 150 students concurrently.
We have designed this website with the purpose of allowing the students to give exams and view their results. This site is an attempt to remove the existing flaws in the manual system of conducting exams.
Students are provided the flexibility to choose among different types of aptitude and programming language tests.
This document outlines the requirements for an e-learning software system called E-Guru Yantra. It will allow students to access study materials uploaded by teachers, including notes, videos, images and slides. The system will have separate interfaces for students, teachers and administrators. Teachers can upload content and students can download materials. The system is intended to provide virtual education by making all content accessible online through any web browser from anywhere. It aims to reduce costs and make the sharing of content more efficient compared to physical distribution of materials.
The document describes a proposed student information system that would allow institutions to more easily manage student data. It would include functions for recording, searching, modifying, and deleting student records. The system would use a prototyping model since requirements are not yet fully defined. It then provides details on the hardware, software, and functional requirements including use of a SQL database, Windows OS, and securing student data.
The document provides a software requirements specification for an online food delivery system. It outlines the purpose, document conventions, intended audience, product scope, and references. It then provides an overall description of the product perspective, functions, user classes, operating environment, design constraints, user documentation, and assumptions. The document also specifies external interface requirements including user interfaces, hardware interfaces, software interfaces, and communication interfaces. It describes key system features and functional requirements. Finally, it covers non-functional requirements such as performance, security, quality attributes and other requirements.
This document describes a gym management system project created by David O'Connor. The system allows users to manage members, employees, equipment, and fitness classes. It includes domain classes for each entity, collections to store data, a user interface, and functionality to save and load data. Search and sorting algorithms are implemented. Inheritance is used between the person, member, and employee classes. The system provides options for administrators to add, remove, view, search, and sort data for each entity type through the user interface.
Software requirements specification of Library Management SystemSoumili Sen
The document provides requirements for a Library Management System. It includes 3 or less sentences:
The Library Management System aims to computerize library processes like book borrowing and maintain member and book details in a database. It will allow librarians and members to search for books, view member accounts, and generate reports. The system needs to be secure, fast, and compatible with common browsers and operating systems.
In this session will leave with a better understand for the hardware requirements for Windows 10.
Minimum System HW Requirements & Compatibility for Windows Platforms
Paul Reed
Senior Program Manager
A presentation detailing a Library Management System (LMS) Project for a Medical Research Council. The function of the Library is to organize and account for all the materials (Books, Journals, Magazines, Publications and Thesis) in the Library.
The system makes use of a Bar coding system to identify materials; used when checking in items.
Martins Jr.
The document is a software requirements specification (SRS) for a student biometric identification system (BSI). It outlines the system's overall description, user characteristics, and specific functional and non-functional requirements. The BSI will use biometrics like fingerprints to automate student identification at entry/exit points. It will interface with a database and network to identify and log check-ins/outs. The SRS defines requirements for registration, an admin panel to manage users, and reporting of daily entries. It also specifies performance, security, and other non-functional needs.
This document provides a software requirements specification for a login module system with four submodules: login, register, forgot password, and reset password. It includes functional requirements for each submodule, describing how users will interact with the system. The intended audience is developers and other stakeholders. The project scope is to create a reusable login module for authentication and authorization across applications for an ABC Company. The document describes the product features and operating environment, including interfaces and constraints.
Android Project report on City Tourist Location based services (Shuja ul hassan)Shuja Hassan
The aim to design and develop this project is to produce a
tourist guide for Skardu city, which can eefficiently guides the
tourist who visits Skardu. The Android tourist guide can be use in place of professional guide due to many reasons like reduce cost of guide, get more accurate information needed for decision making, giving weather and social networking services.The tourists can use this guide for different purposes like searching a location , calculate distance between two locations,getting basic textual information, pictorial information of location which normally we could not get in default Google maps.The guide uses Google Map API, global
positioning system( GPS), Internet and cellular data to provide
its services.
Shuja ul Hassan
IT Teacher
Android Developer
shuja2good@gmail.com
This document is a project report for an online computer shop management system. It discusses problems with current systems, outlines the proposed system which will allow users and administrators to view products, make purchases, and manage inventory. It also covers requirement collection and analysis, planning, implementation details, testing procedures, and maintenance policies for the new system. The system will be developed using PHP and MySQL to provide an online platform for buying and selling computer products and accessories.
The document provides a software requirements specification for a smart tutor application. It describes the purpose, intended users, product scope and features. The key features allow students to search and message tutors, allow tutors to accept students and update profiles, and allow administrators to manage the user database and verify tutor qualifications. The system will have mobile and web interfaces and use a client-server architecture with a Firebase database.
SRS for student database management systemSuman Saurabh
This document is a software requirements specification for a student management portal being developed for LNMIIT. It outlines the purpose, scope, functions, users and operating environment of the system. The key functions are to maintain student records and grades, allow students to view their information, and give medical officers and coaches access to relevant health and sports data of students. It will be a web-based system built using Java, PHP and MySQL that can be accessed by around 20 staff, 1 administrator and 150 students concurrently.
We have designed this website with the purpose of allowing the students to give exams and view their results. This site is an attempt to remove the existing flaws in the manual system of conducting exams.
Students are provided the flexibility to choose among different types of aptitude and programming language tests.
This document outlines the requirements for an e-learning software system called E-Guru Yantra. It will allow students to access study materials uploaded by teachers, including notes, videos, images and slides. The system will have separate interfaces for students, teachers and administrators. Teachers can upload content and students can download materials. The system is intended to provide virtual education by making all content accessible online through any web browser from anywhere. It aims to reduce costs and make the sharing of content more efficient compared to physical distribution of materials.
The document describes a proposed student information system that would allow institutions to more easily manage student data. It would include functions for recording, searching, modifying, and deleting student records. The system would use a prototyping model since requirements are not yet fully defined. It then provides details on the hardware, software, and functional requirements including use of a SQL database, Windows OS, and securing student data.
The document provides a software requirements specification for an online food delivery system. It outlines the purpose, document conventions, intended audience, product scope, and references. It then provides an overall description of the product perspective, functions, user classes, operating environment, design constraints, user documentation, and assumptions. The document also specifies external interface requirements including user interfaces, hardware interfaces, software interfaces, and communication interfaces. It describes key system features and functional requirements. Finally, it covers non-functional requirements such as performance, security, quality attributes and other requirements.
This document describes a gym management system project created by David O'Connor. The system allows users to manage members, employees, equipment, and fitness classes. It includes domain classes for each entity, collections to store data, a user interface, and functionality to save and load data. Search and sorting algorithms are implemented. Inheritance is used between the person, member, and employee classes. The system provides options for administrators to add, remove, view, search, and sort data for each entity type through the user interface.
Software requirements specification of Library Management SystemSoumili Sen
The document provides requirements for a Library Management System. It includes 3 or less sentences:
The Library Management System aims to computerize library processes like book borrowing and maintain member and book details in a database. It will allow librarians and members to search for books, view member accounts, and generate reports. The system needs to be secure, fast, and compatible with common browsers and operating systems.
In this session will leave with a better understand for the hardware requirements for Windows 10.
Minimum System HW Requirements & Compatibility for Windows Platforms
Paul Reed
Senior Program Manager
Database training for HSC school classes presented by Andrew GeePublicLibraryServices
The document summarizes a database training program provided by Wollongong City Libraries to local high school students in 2013. The program involved library staff delivering presentations and hands-on sessions on using academic databases in 5 schools over 13 sessions, reaching 158 students total. Student feedback was overwhelmingly positive, with 155 comments praising the increased knowledge of how to use databases and 157 students saying they would use databases in the future. The program aimed to promote database resources to students who did not have access through their school libraries.
Seminar Cradle to Cradle® Practical Applications in Area Development - 12:15 - 12:30 - Examples of continuing projects at C2Clab; database & Happy Healthy School - prof. ir. Peter Luscuere (Academic Chair Building Services, Technical University Delft)
Student Information System works in the school as a powerful database management tool for all student affairs with Graphical User Interface. It enables you to take periodic, on demand and push reports. It is affordable, customizable and easy to use. Below are main features of School Manager. The systems is scalable to any size of institute.
This document summarizes a school management system database project created by Muhammad Awais, Hasan Jilani and Hina Mahbob. It includes sections on the purpose, problem statement, solution statement, scope and system overview, systems using the database, relationship to other databases, database information, data dictionary and special instructions for the data process flow.
SOFTWARE REQUIREMENT SPECIFICATION FOR PROJECTAjeet Singh
This document provides a project report on developing a "Gate Point Application" android app to provide exam preparation materials for the GATE exam. The app will provide learning content and practice tests for subjects like computer science and electrical engineering. It will also include a syllabus and latest news about the GATE exam. The report outlines the software requirements, including functional requirements like different home screen buttons and sliding menus, as well as non-functional requirements. It presents data flow diagrams and design approaches like the iterative waterfall model. Gantt and PERT charts are also proposed to track the project schedule and dependencies between tasks.
This document outlines the structure and contents of a project proposal, including chapters on the introduction, general project description, requirements, design, and testing. The introduction defines the project scope and team roles. The general description provides an overview and problem statement. The requirements section specifies functional and non-functional needs, including modules, interfaces, performance, and constraints. The design chapter presents high-level and low-level representations of the system. Testing involves test plans and strategies to validate the project meets requirements.
The document discusses the history and components of airline reservation systems. It describes how the first automated booking systems were developed in the 1940s and 1950s by American Airlines and other major carriers. Over subsequent decades, airlines invested in improving reservation technologies and allowing travel agents to access systems like United's Apollo. Modern systems are computerized and can be accessed globally. Key components include hardware, software, databases, data, and procedures. The systems store and retrieve flight information and allow booking transactions.
The document is a software requirements specification for an online book sales system with mobile SMS notifications. It outlines the purpose, scope, technologies, and overall description of the system. The system will allow customers to browse, search, and purchase books online. It will also send SMS notifications to customers when requested books arrive or new books of interest are added. The document describes the user roles, hardware requirements, interfaces, use cases, and database design for the system.
Software Requirement Specification (SRS) on Result Analysis ToolMinhas Kamal
Software Requirement Specification (SRS) on Result Analysis Tool. Chapters- Inception, Elicitation, Scenario-Based Model, Data Model, Class-Based Model, Flow-Oriented Model and Behavioral Model.
Documented in 3rd year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Find a Demo at: https://github.com/MinhasKamal/ResultAnalysisTool
- Destiny is the library automation software used by the school to search its database from any computer
- Users can create an account to place holds on books and download ebooks
- The library homepage provides access to search the catalog, create an account, view new additions and top titles, and get reading recommendations
AIS, Airline Information System, Pilot ProjectMahesh Panchal
This document outlines the development of a computerized airline reservation system that allows customers to book flights online. It describes the problem of meeting increased customer interest in online booking. The proposed solution is a website built using an incremental model that integrates a user-friendly interface, server-side processing, and a central database to manage reservations and customer accounts. Diagrams are included that layout the database, use cases, and system interactions.
This document proposes creating a relational database to help Mayborn School of Journalism effectively communicate with various stakeholder groups. The database would contain information on current/prospective students, alumni, faculty, donors, and sponsors to allow tailoring messages. Data would be collected from existing sources and updated regularly. The database would support multi-channel communications including direct mail, advertising, public relations, and social media. Success would be measured through analytics tracking engagement, enrollment changes, and surveys. The goal is to promote Mayborn and increase applications/student loyalty through targeted communications.
The document outlines requirements for a railway reservation system. The system would allow customers to view train schedules and availability, reserve tickets, pay for reservations, and cancel tickets. It describes functions for maintaining train data, the reservation process, billing, and cancellation. The system needs to be reliable, available, and secure. Development will use Visual Basic for the front end and MS Access for the back end, with approval required from the Ministry of Railways.
Airline Reservation System - Software EngineeringDrishti Bhalla
The document describes an airline reservation system project created by three students. The objective of the project is to design software that automates major airline operations like online flight booking and ticket reservation. The proposed reservation system allows users to search for flights between cities, book seats, check flight status, manage user accounts, and complete web check-ins. It uses a linear sequential development model and stores data in backend Microsoft Access relations to manage passenger, reservation, flight, and payment information.
introduction of data structure and design and analysis of algorithmYerosanTafesse
The document describes a proposed web-based placement management system for an engineering and technology college. It outlines the system's objectives to streamline the placement process and facilitate efficient department placement for students. Various system models are defined, including use cases, actors, and functional and non-functional requirements. Key aspects of the system include automated student placement based on preferences and criteria, a feedback mechanism for students, and different user accounts for administrators, coordinators, students and more.
introduction of data structure and design and analysis of algorithmYerosanTafesse
The document describes a proposed web-based placement management system for an engineering and technology college. It outlines the system's objectives to streamline the placement process and facilitate efficient department placement for students. Various system models are defined, including use cases, actors, and functional and non-functional requirements. Key aspects of the system include automated student placement based on preferences and criteria, a feedback mechanism for students, and different user accounts for administrators, coordinators, students and more.
The document describes a student result management system that will manage information about users, subjects offered each semester, and marks obtained by students. It will generate reports. The system requirements include maintaining data on students, subjects, marks and user accounts with validation checks. The system will have security, maintainability and portability. Key modules include login, subject info maintenance, marks entry and maintenance of user accounts.
The document describes an online college portal system that was designed to digitize processes like tracking attendance, calculating grades, providing timetables, and sharing notes between students, parents, and faculty. The system aims to reduce workload and errors compared to manual processes. It includes modules for students to view grades and schedules, parents to view their child's progress, and faculty to upload materials and enter attendance and grades. The system uses validation to ensure only authorized users can access the appropriate data and functions. It is intended to streamline sharing of information and records for a more efficient digital college system.
This document outlines requirements for a student result management system. The system will manage student information, subjects offered each semester, and student marks. It will include modules for user login, student data entry, subject data entry, marks entry, and report generation. Key requirements include security through password protection, maintainability to allow new features, and portability. The system will store student, subject, marks, and user data in a database.
IRJET- College Activity Management SystemIRJET Journal
The document proposes the development of a College Activity Management System to manage student data like attendance, marks, course details, and schedules more efficiently compared to a manual system. It aims to create a computerized portal for schools and colleges that allows students and staff to access information like attendance, marks, notices, and library resources online. The proposed system would include modules for students, faculty, notices, exams, placement and an e-library to modernize record keeping and information management at educational institutions.
This document provides a software requirements specification for an Attendance Management System being developed for JSS Academy of Technical Education. It includes sections on introduction and purpose, general description of product functions and users, specific requirements including functional and non-functional requirements, and analysis models including sequence diagrams, data flow diagrams, and state transition diagrams. The system will allow for student registration and management of attendance, and provide reports. It is intended to help streamline administrative tasks for the educational institution.
An Implementation Approach for Advanced Management of Examination SectionEditor IJMTER
The objective of the web based Advanced Management of Exam Section is approach of web
applications into the computing technology has brought a enormous revolution in our social life including
the traditional system of education on examination. Web based Management of Exam Section has a
simple and easy to use web-based centralized user interface and a well-defined database-centric schema
for cumulating, recouping and managing in examination objects, track records need to maintain
information about students a s well as faculties .This information could be student name, enrollment,
semester, branch, address, faculty name, joining date, faculty qualification etc. or specific information
related to departments. Seating Arrangement of students during examinations is distributed and faculties
allotment is specified which is maintained in computerized form rather than manually. In existing system
Exam Section Management in colleges are maintained manually which trifle more time and no safeguard
of data is provided. To overcome this, a system is proffered ’Web Based Advanced Exam Section
Management’.
Student Name CourseCIS339Session (month, year)032019.docxcpatriciarpatricia
Student Name:
Course:
CIS339
Session (month, year):
03/2019
Object-Oriented System Analysis and Design
The School of Prosperity
Student Records System (SRS)
Week1—System Request3
Week2—Use Case Diagram AND Use Cases Descriptions5
Week3—Class Diagram AND CRC Cards9
Week4—Sequence, Communication, and State Machine Diagrams15
Week5—Package Diagram19
Week6—Method Contract AND Method Specification21
Week7—Object-Oriented Application Coding24
Week 1—System Request
1
Use this system request template and complete the SRS system request.
System Request—
Project sponsor:
School of Prosperity (SoP)
Business Need:
The existing desktop system will be upgraded to web-based application and this system will be used to maintain records of students, courses, classes, and student registration and grades.
Business Requirements:
The system is capable of having the following functonalities:
· Accessibility over the Internet
· Maintains records of school students
· Maintains records of courses offered by school
· Maintain records of classes offered of the above courses (both online and face-to-face classes)
· Students registration system is included as well
Business Value:
Conservative estimates of tangible value to the company include:
· The SRS will enable the school to continue the expansion of its student population and to effectively manage the expansion
· Eliminate many school staff hours re-entering paper form student registrations by allowing the students to self-register
· Make the system easy to access from anywhere there is an Internet connection and a web browser
Special Issues or Constraints:
· The SRS must be able to handle both online and face-to-face class offerings
· The system must be accessible over the Internet to both school staff and students each with appropriate permissions
· The SRS must try to integrate with and re-use existing desktop application code and database as much as possible to reduce development cost
2
Validate and verify that your system request addresses the SRS Preliminary Planning Overview.
The business need area explains what the SoP is requiring the system to operate. The business requirements consist of what the system must be able to handle and the expectations of the system (once it’s completed). The business value breaks down the details of information that the new system will save on both staff hours and finances for the school. The issues area give problems that could exist once the system is implemented.
3
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.
I, carefully, read the SRS Preliminary Planning Overview and highlighted the important business needs that the SRS system is to meet. I then started to complete the various sections of the System Request Form and while doing so, I referred back to the SRS overview document to confirm my conclusions and understanding. The result of this iterative process is the current Syste.
This document provides a software requirements specification for a student registration system at Rajarata University of Sri Lanka. It includes use case diagrams and descriptions for the key functions of the system. The system allows super users, administrators, students and guests to access different features. Super users have full control and can manage all user accounts and privileges. Administrators can manage subjects, profiles and registrations. Students can select subjects, view information and edit profiles. Guests can only view limited student profiles. The document also includes activity diagrams, entity relationship diagrams, and requirements for functionality, security, performance and testing.
Student Progress Report, Result Analysis & Time Table GenerationIRJET Journal
The document describes a student progress report, result analysis, and timetable generation software. It includes 3 modules - progress report, result analysis, and timetable generation. For progress report, it imports student details, attendance, and test marks from Excel sheets and stores it in a database. It generates progress reports using Crystal Reports. For result analysis, it imports subject marks and stores in the database. It can analyze results and generate graphs. For timetable generation, it enters staff, subject, class, and time details to generate a timetable without clashes or overlaps. The objectives are to reduce manual work and efficiently generate reports, analyze results, and create timetables.
Scholarship Information System documentationKasi Annapurna
The document describes a scholarship information system that will automate the management of student scholarship details across multiple colleges. The key features of the system include maintaining student, college and scholarship data; identifying eligible students based on criteria like marks, caste and income; allowing students to upload documents; and enabling communication between scholarship officers and students. The system aims to reduce paperwork, improve data accuracy and enable easier information retrieval compared to the existing manual process. It will consist of modules for administrators, scholarship officers and students to manage the scholarship application and award process digitally.
The document outlines a proposed student result management system with the following key points:
1. The system will manage student, subject, and marks information for classes 6-10 and generate tabulation sheets. It will also maintain the institute website.
2. The background discusses similar existing systems used in education sectors.
3. Performance will be evaluated based on user interfaces, validity checks, and software attributes like security, maintainability and portability.
The system aims to simplify and speed up the result preparation and management process for educational institutes.
This document outlines the requirements for a student affairs management system. It will allow colleges to automate admission, enrollment, student information management and examination processes. The system will have three user types - administrators who can view and edit all student data, professors who can add exams/grades and print reports, and students who can view and edit their own information. It will provide functionality for registration, login, profile management, and administrative functions like adding/updating student details. The system aims to improve performance, reliability, availability, security, maintainability and portability.
The document describes the design and implementation of an online examination system using PHP and MySQL. It includes sections on requirements analysis, database design, implementation, and problems encountered. The system has three modules - one for administrators, one for students, and one for a super administrator. Entity relationship diagrams and data flow diagrams are provided to illustrate the database and system design. The goal is to allow students to take exams online and obtain results immediately in a more efficient manner than traditional paper-based exams.
Student Name Daniel RosadoCourseCIS339Session (month, ye.docxemelyvalg9
Student Name: Daniel Rosado
Course:
CIS339
Session (month, year):
01/2016
Object-Oriented System Analysis and Design
The School of Prosperity
Student Records System (SRS)
Week1—System Request3
Week2—Use Case Diagram AND Use Cases Descriptions5
Week3—Class Diagram AND CRC Cards9
Week4—Sequence, Communication, and State Machine Diagrams15
Week5—Package Diagram19
Week6—Method Contract AND Method Specification21
Week7—Object-Oriented Application Coding24
Week1—System Request
1
Use this system request template and complete the SRS system request.
System Request
The School of Prosperity
Student Records System (SRS)
Project sponsor:
The School of Prosperity (SoP)
Business Need:
New Internet-accessible Student Record System that will allow students the capability to handle their own registration and staff to maintain records, courses, and schedule online-face-to-face classes.
Business Requirements:
1.) Online accessible system
2.) Reduce registration time
3.) Handle enrollment increases
Business Value:
1.) Reduction in time spent registering students by 90% from 1000 to 100 hrs.
2.) Increase in staff productivity by 10% resulting in $50,000/yr. in cost savings
3.) Paper/Printer usage reduction resulting in approximately $3,000 in savings/yr.
4.)Staff morale is expected to increase due to increased time available for their projects
5.) Eliminate paper filing/registration errors
Special Issues or Constraints:
1.) Completion in one year
2.) Security; Students access to school files must be addressed/restricted
3.) Possibly integrate with currently used home grown apps/systems
2
I believe that my system request addresses the SRS Preliminary Planning Overview because it addresses the issue of what the customer wants, the specifics it is requiring along with the time frame it is requesting it in.
Here are my five questions that would help clarify some project issues/concerns:
1. Will the project team be responsible for loading all the archived/previous semesters of data of students?
2. What are the levels of permissions/rights that will be required at each level (i.e. Help Desk, Advisor, Dean, etc.)?
3. Does the one year time frame include deployment and training, or is it just delivery of application/system?
4. Who will provide the architecture/infrastructure for this deployment?
5. Is SoP looking for a licensed/supported application or are they interested in a COTS (Custom off the Shelf) application that they own outright?
3I completed my work by reviewing the Preliminary Planning Overview and identifying, the request, sponsor, business need(s), requirement(s), value and issues/constraints. I made the decision to differentiate between what were needs/ requirements and what were requests. The needs/requirements were where the system was accessed (internet accessible), how/who accessed the data/system (security) and when it needed to be in place (in one year).
Week2—Use Case Diagram andUse Cases Descriptions
1
SRS Use Case Diagram
.
IRJET - College Recommendation System using Machine LearningIRJET Journal
The document proposes a college recommendation system using machine learning that would help students select the best suitable colleges for admission based on their details and previous admission data. It describes designing a web application with admin and student modules, where the admin can manage college data and the student can register, view college recommendations and profiles. The system uses a C4.5 decision tree algorithm to accurately predict colleges where a student is likely to gain admission.
Similar to Software Requirements specification for database design of music school management information system (20)
6th International Conference on Machine Learning & Applications (CMLA 2024)ClaraZara1
6th International Conference on Machine Learning & Applications (CMLA 2024) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of on Machine Learning & Applications.
Low power architecture of logic gates using adiabatic techniquesnooriasukmaningtyas
The growing significance of portable systems to limit power consumption in ultra-large-scale-integration chips of very high density, has recently led to rapid and inventive progresses in low-power design. The most effective technique is adiabatic logic circuit design in energy-efficient hardware. This paper presents two adiabatic approaches for the design of low power circuits, modified positive feedback adiabatic logic (modified PFAL) and the other is direct current diode based positive feedback adiabatic logic (DC-DB PFAL). Logic gates are the preliminary components in any digital circuit design. By improving the performance of basic gates, one can improvise the whole system performance. In this paper proposed circuit design of the low power architecture of OR/NOR, AND/NAND, and XOR/XNOR gates are presented using the said approaches and their results are analyzed for powerdissipation, delay, power-delay-product and rise time and compared with the other adiabatic techniques along with the conventional complementary metal oxide semiconductor (CMOS) designs reported in the literature. It has been found that the designs with DC-DB PFAL technique outperform with the percentage improvement of 65% for NOR gate and 7% for NAND gate and 34% for XNOR gate over the modified PFAL techniques at 10 MHz respectively.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
We have compiled the most important slides from each speaker's presentation. This year’s compilation, available for free, captures the key insights and contributions shared during the DfMAy 2024 conference.
3. CodeWar
2Softawre Requirement Specification
Table of Contents
Table of Contents
1 Introduction...................................................................................................3
1.1 Purpose ...................................................................................................4
1.2 Scope ......................................................................................................4
1.3 Definitions, Acronyms, and Abbreviations ...................................................4
1.4 Overview..................................................................................................5
2 Overall Description .........................................................................................5
3 Specific Requirements.....................................................................................6
3.1 Functionality ............................................................................................6
3.1.1 Details of registered students to classes should be maintained................6
3.1.2 Details of available classes and lessons should be maintained. ................6
3.1.3 Details of class allocations for both students and teachers should be
maintained.....................................................................................................6
3.1.4 Administrators should be able to register new students to relevant classes.
7
3.1.5 Students’ attendance should be maintained. ..........................................7
3.1.6 Students’ payments should be maintained.............................................7
3.1.7 Activities and grades of the students must be maintained. ......................7
3.1.8 Students’ progress can be monitored. ...................................................7
3.1.9 Teacher’s attendance and working hours should be maintained...............7
3.1.10 Generate monthly salary for teachers at the end of the month. ................7
3.1.11 Users should be able to have different user based access levels. ..............8
4. CodeWar
3Softawre Requirement Specification
3.2 Non Functional Requirements.....................................................................8
3.2.1 Familiar Interface ................................................................................8
3.2.2 Maintainability....................................................................................8
3.2.3 Security..............................................................................................8
3.2.4 Availability .........................................................................................9
3.2.5 Reliability and Performance..................................................................9
3.2.6 Real Time Feedback.............................................................................9
3.3 Design Constraints....................................................................................9
3.4 Technologies..........................................................................................10
Software Requirements Specification
1 Introduction
“SaRiGaMa” music school requires a complete, comprehensive and integrated
management information system.
5. CodeWar
4Softawre Requirement Specification
1.1 Purpose
The SRS describes the external behavior of the management information system
identified. It also fully describes the functional, non-functional requirements
and design constraints.
1.2 Scope
The scope of the management information system for the “SaRiGaMa” music
school is to;
➢ maintain student records
● student registration
● allocation to classes
● attendance
● progress monitoring
● fee payment
➢ maintain teacher records
● allocation to classes
● attendance
● working hours
➢ generate monthly payments for teachers
➢ provide different user based access levels
1.3 Definitions, Acronyms, and Abbreviations
Student ID - The identification number that each student is given by the Sarigama
musical school.
Instructor ID - The identification number that each records instructor is given.
6. CodeWar
5Softawre Requirement Specification
1.4 Overview
Section 2 contains an overall description of the user’s perspective of the database which describes
the general factors that affect the product and its requirements. Section 3 provides information
about the specific requirements in detail including functional and nonfunctional requirements,
design constraints that are crucial to design the software. The last section includes the supporting
information.
2 Overall Description
The main perspective of the system is to keep track of student data and teacher
details.
This system would be able do the following functions ensuring security and failure
free. Lessons are given via group classes or individual classes. Same student may learn
more than one instrument. Starting from student registration, allocation to classes,
attendance, progress monitoring, fee payment etc will be maintained on the MIS. Also
teacher information and allocation to classes’ attendance and working hours will also
be maintained. Student registration process considers keeping information about
parents and also information about siblings who are students. End of month payments
for teachers will also be generated fromthe system.
7. CodeWar
6Softawre Requirement Specification
Two different access levels should also be provided to the admins and teachers to
access the MIS. Only admins are allowed add new teacher profiles and assign new
resources to the system. They have the right to access the entire application. Teachers
are supposed to track student activities and view their details. students can only
update their profiles, view course contents and do assigned exercises. calculating
teacher payments and progress monitoring will be automated.
3 Specific Requirements
3.1 Functionality
3.1.1 Details of registered students to classes should be maintained.
Details of new students such asstudent id, name, age, address, contactdetails should be maintained
in the database. Other requirements about parents and other siblings who are students should also
be maintained in the database.
3.1.2 Details of available classes and lessons should be maintained.
Details of the classes such as the duration, fee, days, prerequisites, maximum capacity of students,
available capacity of students have to be maintained. These details will have to be checked before
selecting students for particular classes and to update them whenever necessary.
3.1.3 Details of class allocations for both students and teachers should be maintained.
Details of student id, class id (and teacher id, class id) should be maintained in a relationship entity
table to allocate students to classes at the time they register and also to check which student takes
part which classes whenever necessary.
8. CodeWar
7Softawre Requirement Specification
3.1.4 Administrators should be able to register new students to relevant classes.
When registering new students to their preferred classes, administrators will have to access to class
and class allocation details. They will register new students depending on the availability
(vacancies) of particular classes. The classes will be allocating immediately for selected students
at the registration.
3.1.5 Students’ attendance should be maintained.
Attendance on each day for all classes should be maintained in the database.
3.1.6 Students’ payments should be maintained.
Fee payments of the students should be maintaining in the database.
3.1.7 Activities and grades of the students must be maintained.
When an activity is done by a student, the relevant details such as student id, activity id, grade, date
should be maintained in the database.
3.1.8 Students’ progress can be monitored.
Student progress should be generated and displayed from the system based on the details of
students’ activities and grades.
3.1.9 Teacher’s attendance and working hours should be maintained.
3.1.10 Generate monthly salary for teachers at the end of the month.
End of month payments for teachers should also be generated from the system based on the
teacher's’ attendance working hours, and the classes they take part. This will require those details
of relevant classes such as teachers’ allocation to classes etc...
9. CodeWar
8Softawre Requirement Specification
3.1.11 Users should be able to have different user based access levels.
The system should have different access levels to be provided to the admin and teachers to access
the MIS.
3.2 Non Functional Requirements
3.2.1 Familiar Interface
Two different accesslevels will be provided to the admins and teachersto access the
MIS. Teachersmay not be familiar with the automated system. Therefore, new system
should have an interface with necessary optionsfor easy access of information.
3.2.2 Maintainability
Student registration,allocation to classes, progressmonitoring etc.should be
implemented without affecting the other part of the system and should be able to add
new functionality.
3.2.3 Security
End of month paymentsfor teachersshould also be generated from the system and
also payments, attendance, registration etc. should be handle using this new system.
Therefore, system should be use strong authentication mechanism.
10. CodeWar
9Softawre Requirement Specification
3.2.4 Availability
100% of the time available server and enough capacity of database should be needed
to this new MIS.
3.2.5 Reliability and Performance
Less failure of the system, readily available functionality and allow concurrent users.
3.2.6 Real Time Feedback
The new management information system should display the daily attendance,
progressof the students, fee payment etc. and should also show the changesin real-
time as the new entry is added or removed.
3.3 Design Constraints
Domain Integrity
In the SaRiGaMa application’s database attributes will be restricted accordingly with real world
semantics on data. For example,
• Teacher ID, student ID must be unique.
• Teacher’s age should have to be more than 20 years and according to that date of birth attribute
will have some constraints. While it is 11 years (or according to the age given by the Music
school) for the students.
• No zero payments for the teachers
11. CodeWar
10Softawre Requirement Specification
• When registering a student there must be at least one parent or a guardian.
Entity Integrity
• Unique id is given for the student as well as for teachers to recognize them accurately.
• Null values are not accepted for attributes like date of birth, teacher ID, student ID, etc.
Referential integrity
Make sure that there are no orphan records that means there must be a foreign key’s value must be
found in the corresponding entity. For example, consider the following two tables
learned_instrument (student_id, instrument_name)
instrument (instrument_name,[other attributes])
There should be a unique value matched in the instrument table for the foreign key, instrument_name
which is found from the learned_instrument table.
Foreign key rules
Responsible for what will happen for the child rows when the record with the primary key is deleted or
updated. For example,
If a student dropouts from the school the database will not let the student to be deleted if there are other
records such as learned music, attendance,etc. but if there could be found only the registration, deleting
the primary key make the registration record to be deleted (CASCADE)
Cardinality
Focus about the real relationships that the entities possess. For example the relationship between
student and teacher is many to many, student and instrument is many to many likewise focus
on the cardinality.
Concurrent access anomalies
Database is designed accordingly, that two students cannot enroll for one single place for a
particular music lesson.
Atomicity
If a failure occurs this database ensure that the data will restored. Suppose that if a student
unenrolled a music lesson to enroll another music lesson if unenrolling caused a trouble making
the student couldn’t make his/her choice then the state of the data should go back to the
previous state.
Security problems
Not every user of the database system allows to access all the data.
Teachers cannot add or delete the tables. Only the admin can alter or change the tables.
3.4 Technologies
MySQL workbench - to design Entity Relationship diagram