Post on 04-Nov-2015
description
transcript
Software Requirements Specification
CBIT STUDENTS FINANCE SYSTEM Bhaskar Y 1601-12-733-097Charan M 1601-12-733-098 Jitendra K 1601-12-733-099 Mukund K- 1601-12-733-100
CSE-23rd Year, II Semester
TABLE OF CONTENTS
1.0. Introduction
1.1. Scope
1.2. Product features
1.3. User characteristics
1.4. Constraints
1.5. Assmptions and dependencies
2.0. Overall description
2.1. Functional requirements 2.2. Non-functional requirements
3.0. Requirement specifications
3.1. External interface specifications
3.1.1. Hardware interfaces 3.1.3. Software interfaces
3.1.4. Communication interfaces
1. INTRODUCTION
1.1 SCOPE
The purpose of cbit student finance system is to collect funds from alumni and present students. This funds will be allocated for various events conducted in college, which includes technical and cultural events. It can also be used for renovations. 1.2 PRODUCT FEATURES
Maintenance of Students database. Collecting funds from students.
Store the details of the students who paid the fund. Maintaining the information like amount required for college events and for renovation. Allocating funds for the events according to the amount required by them. To coordinate all events of the college.1.3 USER CHARACTERISTICS ~ The Student of the college ~ The Coordinator of the college ~ The Finance Manager of the college ~ The DataBase Manager of the college1.4 CONSTRAINTS The product is developed using ASP
The database is SQL server
1.5 ASSUMPTIONS AND DEPENDENCIES MICROSOFT SQL to store database ASP to develop the software2. OVERALL DESCRIPTION
2.1 FUNCTIONAL REQUIREMENTSSTUDENT-
Personal details report Pays the fund Educational background
Store the names of students who paid the fund. Conduct events from the funds collected.2.2 NON FUNCTIONAL REQUIREMENTS
The executable software or module must fit on a 1.4 MB floppy disk The operating system used can be Windows XP/VISTA3. REQUIREMENT SPECIFICATIONS3.1 EXTERNAL INTERFACE SPECIFICATIONS
3.1.1 HARDWARE INTERFACES
Interfaces between the software and hardware components like touch tablet3.1.2 SOFTWARE INTERFACES Database, legacy system, web server
3.1.3 COMMUNICATION INTERFACES
Hyper Text Transfer Protocol (HTTP)
DATA MODELS :USECASE DIAGRAM
CLASS DIAGRAM:
SEQUENCE DIAGRAM :
COLLABORATION DIAGRAM :
ACTIVITY DIAGRAM:
DEPLOYMENT DIAGRAM:
COMPONENT DIAGRAM:
OBJECT DIAGRAM:
STATE-CHART DIAGRAM: