Software Requirements

Purpose This SRS Document contains the complete software requirements for the School Management Sysytem (SMS) and describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support. Scope
The scope of the system is to manage the ℘ Students information and there fees. ℘ To manage Employees and their salaries ℘ To develop registration system ℘ To facilitate School by controlling the timetable and examinations ℘ To facilitate attendance record keeping ℘ To facilitate various report generation The scope of the system is to manage the student information, human resource and fees module Features: ₰ The system is easy to use, have good looks and secure. ₰ Get easy access to student particulars, their schedules, address, parents, disciplinary records, extra-curricular activities, and any reports, anytime


₰ Track your teacher's particulars, residential addresses and other important data ₰ Report cards are fully customizable - you get to have your own grading criteria, grading flow, report card format. You can print beautiful report cards and transcripts. ₰ Teachers will be treated to the simplest interface around for them to enter grades. Grades are also automatically consolidated. ₰ Track daily attendance. Easy to use interface to check off students Attendance. ₰ Fees management. Track the fees of the students. Automatic generation of the fee bills. ₰ Automatic generation of timetable in the system. Teacher and room availability is tracked automatically. ₰ Manage the employees’ data. There information is stored with their types and branches. ₰ Employee attendance is marked in the system. ₰ Employee salaries are calculated in the system automatically. Theses salaries are calculated on the daily attendance. ₰ The system will give the edge for better reporting.


Abbreviation: • HTML: Hypertext Markup Language is a markup language used to design static web pages. • EJB: Enterprise Java Beans. • J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—for developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. • DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications. • WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards. • WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application utilizing EJB’s. This consist of EJB tools , CMP ,data mapping tools & a universal test client that is designed to aid testing of EJB’s. • HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server.

o References: • IEEE SRS Format • Problem Definition (Provided by IBM) • Sample Synopsis (Provided by IBM) • CT Arrington. the suite of communication protocols used to connect hosts on the Internet. Enterprise Java with UML. • TCP/IP: Transmission Control Protocol/Internet Protocol. TCP/IP uses several protocols.• HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).OMG Press. the two main ones being TCP and IP. o Technologies: • J2EE: Application Architecture • DB2: Database • WSAD: Development Tool • WAS: Web Server • Rational Rose: Design Tool • UML: Unified Modeling Language for Object Oriented Modeling Techniques • XML: Extensible Markup Language • AJAX: Asynchronous JavaScript and XML 4 .

Section 3 gives specific requirements which the software is expected to deliver. Now as I got that my organization has adopted manual system comprises of several documents. time consuming and less reliable. the 5 . Functional requirements are given by various use cases. Several checks and considerable drawbacks have been noted. some general constraints while making the software and some assumptions and dependencies that are assumed.Overview The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. registers and man power. It gives what level of proficiency is expected of the user. Some performance requirements and design constraints are also given. Due to huge burden of work and sensitivity of the job. This system is naturally complicated. Overall Description Product perspective Product functions EXISTING SYSTEM First of all the study was conducted to see and determine the needs and requirements regarding the “School Management System” and a solution for problems faced by it was sought.

In the analyzing phenomena. which the organization is facing? • How these difficulties can be removed? • What is like the new computer-based system? • What are the direct and indirect benefits? In order to computerize the system. As a result the system is very much error prone and thus not efficient. STUDYING AND ANALYSING EXISTING SYSTEM The basic aim for developing a computerized system is to establish some objectives. DRAWBACKS OF EXISTING SYSTEM 1. In the existing system there is much data redundancy. Existing system is quite time take because of manual environment. the following points are to be preferred. • What kind of difficulties do the related people face to get required information? • What are the major problems. which the computer based system should satisfied. 2.manual system demands its computerization without further delay. there are various stages and activities that must be covered from the very start till the accomplishment of the project. 6 .

5. 11.3. files. Editing of records is also difficult process. In the existing system. All the information is recorded on paper. The records are not maintained properly. All the desired reports are not generated. 10. Different records are managed by different employees. There is no security else from keeping the records in lock. The existing system is not user friendly because of lengthy procedures. month becomes more 7 . It takes a long time to search a desired record. 8. A large number of files and voluminous register have to maintain for the purpose of handling data and related information which results in worthless efforts as well as wastage of large number of stationary. 6. and because of it. Storage media is another important factor. 4. 14. 12. registers etc that are system. 7. a lot of salary is wasted. The result of the students can be late because of old Reports generated for the attendance at the last of the difficult to manage within the date. all the calculations are carried out manually which cause errors. 9. 13.

2. Need to reduce cost to maintain system. 9. 11. Short and less time consumption in access the data. Due to lake of communication there is often save the records create the problems of inconsistency.liable to be lost or damage. 12. So the existing system is not adequate. Advanced communication ways. Such a way should adopt where user entries should be reduced to avoid errors. 7. 15. Preparation of result reports should handle through new system. Also it required to become economic and smooth. System should be able to reduce cost of man power. 4. REQUIREMENTS OF THE SYSTEM Analysis of existing system as I mentioned above create many problems to gain in time information. 5. Removal of data inconsistency. 13. 8 . which can make a positive effects on the running system and organization can get more advantages than now. Manage the whole records with great security. 8. 6. 3. Avoiding the data duplication. 10. Better preservation of records. Some of the requirements are given below. User put fewer entries in new system. New system should have automatic calculation environment. 1. There is need to improve efficiency of system.

These functions are necessary for the automation of school management system because there will be need of calculator or other methods to calculate the fields.14. delete and update data. This relational database will help us to make complex structure of the database and output reports. INPUT Graphical user interfaced and attractive forms are developed for data inputs. The work through new system should be easy. Also we can normalize tables to reduced data entries. Data conformation reliability. These functions should be implemented in the new system. 9 . It also makes easy to maintain the accuracy. PROPOSED SYSTEM In some of the fields the system required to auto generates the data from other information for example from the class name of the student the system should generate the fee schedule automatically. OVER VIEW OF THE PROPOSED SYSTEM DATABASE As the data stored by the application needs data relativity with each other so relational database management system is used to maintain data into organized form. These forms will help to insert.

2. Much of the huge work of maintaining the files by hand will be eliminated. In accurate up-to-date information will be available on demand at any time. The retrieval of the data will be efficient and time effective. 5.OUTPUT To output the information in form of reports. Thus the database will compact the storage and maintaining the data. The system is controlled so much and perfect that invalid data is almost impossible to record. Crystal Reports is used to output reports of different types which provide the desired output in required format. User characteristics The user should be familiar with the Shopping Mall related terminology like Attendance/Grades etc. The database maintained will help the management to store the information in an efficient manner. eliminating the needs of voluminous paper file or other records. Since machine can retrieve and changed the data faster than a human can. 3. In particular queries can be answered quickly without any need for time consuming manuals or visual search. The user should be familiar with the Internet. 6. BENEFITS OF THE PROPOSED SYSTEM 1. Much of the sheer tedium of maintaining the files by hand will be eliminated. 4. 10 .

Operating System (any) Data Base DB2. Operating System (any) Server: Development WSAD (J2EE. • Admin is created in the system already. Web End: Server. Assumptions and Dependencies • The end user should have the basic knowledge of English and Computer. Java Bean. HTML). • The System should connect with a LAN Network.Constraints There is no maintainability of back up so availability will get affected. No multilingual support Operating environment Client on Web Browser. OS (Windows). Servlets. Web Browser. Operating System (any) Internet: Client on Client Software. Operating System (any) Intranet: Web Server: WAS. DB2. Limited to HTTP/HTTPS. • The Report will be Viewed using Adobe Reader 11 . Java. User Documentation User manuals can be provided for user to interact with software. • The validation and report is generated by admin • The system must contain at least 30 GB disk space and 2 GB RAM.

Hardware Interface: Client Side Processor RAM Pentium 4 GB Quad Core 12 Internet Explorer Disc Space 1 TB . o On the server side web server is for EJB and database server is for storing the information. Communication between customer and server is provided through HTTP/HTTPS protocols. o The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.External Interface Requirements User interfaces o The web pages (XHTML/JSP) are present to provide the user interface on customer client side.

3 GHz Server Side Pentium Quad 4 GB Core at 1. Operating System (any) Internet: Client on Client Software. Java. Servlets.3 GHz Pentium Quad Core at 1 .1 at 1. Java Bean. Web Browser. Client on Intranet will be using TCP/IP protocol. DB2. OS (Windows). Web End: Server.0 Web sphere application server V5. Operating System (any) Server: Development WSAD (J2EE. Operating System (any) Data Base DB2.3GHz 4 GB 2 TB 1TB (Excluding data size) Software Interface: Client on Web Browser.0 DB2 V8. HTML). Communication Interface: Client on Internet will be using HTTP/HTTPS protocol. Operating System (any) Intranet: Web Server: WAS. 13 .9.

• The fee structure becomes clearer to store. • The proposed system has a very interactive throughout its operation. • The database is maintained which is cater for the storage of the information. In order to overcome the problems found in existing system a computerized system is introduced. 14 . • The database is fully normalized to remove redundancy and data inconsistency. for each new student that overcomes the problems of duplication. The main features of the proposed system are stated below. • The system needs the new registration No. • It is so much controlled that a common user with some basic knowledge of computer can easily use it.System features FEATURES OF PROPOSED SYSTEM After studying and analyzing the existing system many severe drawbacks have been pointed out. • The user cannot insert any invalid value into the database. • The system has been divided into different forms to cover all the aspects of school management system.

• The retrieval of the data is speedier according to the existing system and saves the time taken to enter a new record. • As the recording media of the computerized system is the Hard Disk or Magnetic Tapes.  Flexible service based architecture will be highly desirable for future extension. • The output given to the user is more user friendly. User can retrieve the specific information in any way. so a lot of information can be stored on a single entity rather than that of a bundle of files and registers.  Mirror database can be maintained so if any problem occurs the mirror database act as a primary database.• User needs the user friendly environment to work with the system. The forms contain the graphical objects to enter the information and also give the reports in managed form. Other Nonfunctional Requirements Performance Requirements  More than 1000 users concurrently access the system  It is completely automated system the output of one process seamlessly provide an input to another process. • Reports generation is very fast and no extra things are required to point out the important information. 15 .  Better component design to get better performance at peak time. record-by-record or collectively in the form of reports. .

when the system are not used more than 5mins Software Quality Attributes Functionality : All of the operations performed by a software program.  Automatic logout of the system . Flexibility : We can changed easily according to the situation Business Rules  User hierarchy is classified.Safety Requirements  Using deferred update mechanism we can safeguard the transaction from failure occurs by power shut down or by any other network failure.  Admin only operate on Salary dept. Security Requirements  Using Encryption algorithm to safeguard the data from hacking.  Teachers can operate only on Attendance. Usability : It is easier to operate by users Reliability : User id and Password are stored in a secured way Productivity : Reports like Product Status and Raw materials Status Scalabity : It can extend functionality at any time Adaptability : It can easily adapt any extension in software Portability: It is portable we can take anywhere around the world. Robustness : Fault identification and isolation are easy. 16 . Only appropriate user can access their own level.  Online backup will be taken and store in a remote location.

 Better component deign to better performance at peak time. Acronyms. and Abbreviations: • HTML (Hyper Text Markup Language): It is used to create static web pages. • JSP (Java Server Pages): It is used to create dynamic web content.  Flexible service based architecture will be highly desirable for future extension. SSL can be used. 17 . Secure access of confidential data (user’s details). Other Requirements Appendix A: Glossary Definitions.

• XML (Extensible Markup Language): It is a markup language that was designed to transport and store data. • TCP/IP – Transmission control protocol/internet protocol is the communication protocol used to connect hosts on the internet. 18 . distributed object applications-based. which is used for developing and running distributed java applications. • WASCE (WebSphere Application Server Community Edition): It is an application server that runs and supports the J2EE and the web service applications.• Java Script: It is a scripting language used for client side web development. • Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages. • EJB – Enterprise java bean. it is architecture for the development and deployment of transactional. belonging to the Java platform. • HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server. that • HTTPS – Secure hypertext transfer protocol is a hypertext transfer protocol over secure socket layer. • Jquery: It is a lightweight JavaScript library emphasizes interaction between JavaScript and HTML. server-side software components • J2EE (Java 2 Enterprise Edition): It is a programming platform.

• Web 2. • Rational Rose : It is used for preparing design documents such as class. Database schema diagrams and to generate DDL. interoperability. component.0: It is commonly associated with web applications which facilitate interactive information sharing.use case . deployment and state diagram 19 . specify.• WSAD (WebSphere Studio Application Developer ): It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service. package . • UML: Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize. activity .sequence . collaboration . • RAD: Rational Application Developer is a development tool that helps to design web pages and also helps to design the diagrams like ER. construct and document. • DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong "on demand" business applications. user-centered design and collaboration on the World Wide Web.

Appendix A: Analysis Models Use-Case Model Survey Figure 1: User hierarchy 20 .

Figure 2: Use case diagram for Customer & Visitor Figure 3: Use case diagram for Shop owner 21 .

Figure 4: Use case diagram for Employees Figure 5: Use case diagram for Administrator 22 .

♦ Contact and Giving Permission to Vendors: Contact with the vendors and give permission to sell their product under the site after testing the product’s quality. ♦ Register : Sales Manager: 23 . Customers: ♦ Login: Customers must have a valid login id to enter into the site. and details about services provided. as depicted in the above use-case diagrams: Administrator: ♦ Database Management: Control the database and keep track of all records of customers and employee details. ♦ View all details: View the details of all employees and control the whole site. payment details. ♦ Advertising the Site: Responsible for making advertisements for the site. Visitors: ♦ Visiting the Site: Can only visit the site without registration. ♦ View and edit Own Details: Can view/edit his personal details. ♦ Purchasing: Can purchase any product through valid credit card.Given below is an overall picture of the system. ♦ Giving Feedback to Customer Care: Can give feedback to the 24X7 Customer Care Service center about their impression for the site and services. ♦ Choosing and comparing products: Can view all available products and can compare them and make a choice for purchasing products. ♦ Registration: New users can sign up by creating new ID.

Purchase Manager: ♦ Consulting with Administrator: Taking permission from the Administrator for the product to be purchased from vendor. queries and feedback from the customers. ♦ Consulting with Administrator: Consult with the Administrator about the payment details of the customers for the updating of the database. ♦ Consulting with Banks: Responsible for contacting the banks for the validation of the a/c number provided by the customer while purchasing and make the transaction from the given a/c. ♦ Managing Sales to Customers: Responsible for properly allocating the selected product according to the customer’s choice and delivering product to the customer. Customer Care: ♦ Getting Feedback from the Customers: Responsible for receiving complaints. 24 .♦ View customer details: View the personal details of the customer. ♦ Providing Solutions to Customers: Provide feasible solutions to the customers on their complaints and queries. ♦ Contacting with Administrator: Responsible for informing administrator when any product item’s stock goes under the minimum level. Accounts Manager: ♦ Regulating Payments: Keep track of all the payment transactions made by the customers and update the payment information. ♦ View Product Stocks: Keep track of each product item’s stocks for selling purpose. ♦ Product Stock Management: Responsible for managing stocks of each product items.

Class Diagram Class Diagram 25 .

26 .

Sequence Diagram: 27 .

28 .

Data Flow Diagram 29 .

State Transition Diagram 30 .

31 .

In Order_UI Order Orders Item_UI Item Item Cat-Item Bill Category Item_UI Bill_UI Category-Item Bill 32 .Entity Relationship Diagram: Customer 1 1 1 1 has has M Order 1 has M 1 has 1 Bill 1 has M M allow has 1 Suggestion new Item M M Payment M M Item M has 1 Category Discount Structure Item Rate Structure 1 M Define 1 has 1 Manager 1 M 1 has handle M handle 1 has 1 Delivery M 1 has M Employee M 1 has Define 1 Shop owner has 1 Department Architecture Diagram: Application Layer Customer_UI Admin/Shop Emp_UI Business Layer Customer Admin/Shop Emp Data Layer Customers Admin Shop Emp Log In Log In_UI Log .

33 .

Sign up to vote on this title
UsefulNot useful