Software Requirement Specification free essay sample

The description and overview of everything included in this SRS document is explained here. Also, the purpose for this document is described and a list of abbreviations and definitions is provided. 1. 1 Purpose The purpose of this document is to give a detailed description of the requirements for the †Department Attendance and CPE Management† software. It will illustrate the purpose and complete declaration for the development of system. This document is primarily intended to be proposed to the CSE department’s office staff and the staff-in-charge for CPE management. Scope The †Department Attendance and CPE Management† is a Computer based software system which is capable of the following : 1) The CPE management system has in it the details about the conferences that are organised in the college, the conferences attended by the students or staff from SSN and also the details of the Guest Lectures that took place. 2) It keeps track of the conference title, the type of conference, the type of participants, sponsor and resource person of conferences organised in the college. We will write a custom essay sample on Software Requirement Specification or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page On demand, the system can generate details such as number of workshops organised within a period, number of conferences organised for students/ staff/ both and other required reports. 4) The attendance system monitors the attendance record of all the students in the department period wise. The system also maintains period wise accumulation of attendance of all students in each subject. 5) This system keeps track of marks obtained by students in each of the Unit Tests in all subjects. The records are maintained for all three Unit Test cycles. The system includes features that can generate reports such as class wise Unit Test mark sheets, period wise accumulation of attendance on demand. 1. 3 Definitions, acronyms, and abbreviations Term Definition Admin/Administrator System administrator who is given specific permission for managing and controlling the specific part of the system. CPE Management Keeping track of different conferences, workshops and guest lectures attended or organized by staff and students Student Attendance The attendance and mark details of each student in the department DACM system Department Attendance and CPE Management 1. 4 References [1]IEEE Software Engineering Standards Committee, â€Å"IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications†, October 20, 1998. [2] Pressman, Roger (2010). Software Engineering: A Practitioners Approach. Boston: McGraw Hill. 1. 5 Overview A general description, including characteristics of the users of this project, the products hardware, and the functional and data requirements of the product is portrayed in the Overview. General description of the project is discussed in section 2 of this document. Section 3 gives the functional requirements, data requirements and constraints and assumptions made while designing the system. Section 3 also gives the specific requirements of the product, external interface requirements and gives detailed description of functional requirements. 2. Overall description An overview of the whole system is given here. The system is explained in its context to show how the system interacts with other systems and introduce the basic functionality of it. It will also describe what type of stakeholders who will use the system and what functionality is available for each type. 2. 1. Product perspective This Department Attendance and CPE Management system will be a package used by the Department of CSE to improve the efficiency in maintaining the attendance and mark database of the students and facilitating in keeping track of conferences, workshops and guest lectures attended and organised by staff or students. 2. 1. 1. User interfaces The DACM system will be placed available to the office staff and the staff-in-charge with separate login so as not to end up in chaos. There will be a login page which will prevent unauthorized use. 2 An interface for managing and updating student marks and attendance will be available to the office staff after authentication. Reports can also be generated via the interface. 3 The CPE management system to be managed by the staff-in-charge after authentication will have an interface to update details about conferences organized by the department, conferences attended by staff and guest lectures delivered by staff. Reports can be generated periodically via the interface. 2. 1. 2. Hardware interfaces The DACM system is intended to be platform independent. Therefore no specific hardware is excluded. But it will at least work on x86 systems without any additional porting efforts. There is a necessity of a printer if a hard copy of the reports is needed. Moreover, no special hardware is needed for software operation. 2. 1. 3. Software interfaces The DACM system is intended to be operating system independent. Therefore no specific operating system is excluded. Databases would be configured using SQL and the front end will be designed using Java. Memory constraints This DACM system is expected to use no more than 512 MB of RAM and 100 MB of external storage. 2. 2. Product functions With this software system, the management of student attendance and mark details by the department’s office and the CPE management by the staff-in-charge will be hassle-free. Updates are done on a button-click and the reports are available instantly. Any sort of information can be gathered with a great ease. 2. 3. User characteristics There are two types of users who use this system. Staff-In-Charge :The department staff who uses this system to keep track of the events organized and attended by staff and students of the department and generates reports for a particular period. 2 Office Staff:The office staff who inputs the system with the student details, Unit Test marks and periodical attendance and generates reports for a particular period. 2. 4. Constraints The Network connection is a constraint for the application. Since the application fetches data from the database over the same network, it is crucial that there is a network connection preferably a LAN connection for the application to function. Further the capacity of the database also affects the system since the database is shared between both applications it may be forced to queue incoming requests and therefore increase the time it takes to fetch data. 3. Specific Requirements The functional and quality requirements of the system are described here. It gives a detailed description of the system and all its features. 3. 1 External interface requirements The DACM system will use the standard input/output devices for a personal computer. This includes the following: Keyboard Mouse Monitor Printer 3. 2 Functional Requirements Functional requirements define the fundamental actions that system must perform. The functional requirements for the system are divided into two main categories 1 Department Attendance Management: a The system after authentication can collect information of students such as i Student Register Number ii Student Name iii Student Class (Semester) and Section iv Subjects v Unit Test Marks vi Attendance b The office staff will also be capable of updating these details especially, the marks and attendance. Required type of reports for each class or student can be generated depending on the constraints specified by the office staff. 2 CPE management: a The staff-in-charge after authentication can enter information about the conferences, seminars and workshops organised in the college. b The staff-in-charge can then add entries whenever staff have attended these events in other institutions or have delivered guest lectures in other institutions. c Provisions for generating periodic reports based on staff and students are also available. 3. 3 Non Functional Requirements Non Functional requirements define the needs in terms of performance, logical database requirements, design constraints, standards compliance, reliability, availability, security, maintainability, and portability. 3. 3. 1 Performance Requirements Performance requirements define acceptable response times for system functionality. The system developed must comply with the following non-functional requirements: 1 The load time for user interface screens shall take no longer than two seconds. 2 The log in information shall be verified within five seconds. 3 Queries shall return results within five seconds. Software Quality Attributes. The graphical user interface of the DACM system is to be designed with usability as the first priority. The application will be presented and organized in a manner that is both visually appealing and easy for the user to navigate. There will be feedbacks and visual cues such as notifications to inform users of updates. 3. 3. 3 Fault Tolerance The system is designed to tolerate faults to certain extent. Improper data such as wrong username or password is acceptable up to 3 times after which the system will be locked for 10 minutes. 3. 3. Security Requirements Security of the system is guarded primarily through proper authorization. The system is resistant to hackers as it cannot be hacked through brute-force and such other attacks. 3. 3. 5 Platform constraints The DACM system shall run in any Microsoft Windows/Linux environment that contains Java Runtime and the SQL database. 3. 3. 6 Logical Database requirements Since this system handles voluminous data for numerous students, the database plays a major role in determining the system security and performance. SQL database will be used to store and retrieve the information. Software Requirement Specification free essay sample Students to several process modeling techniques for representing business processes. Although this chapter focuses primarily on data flow diagramming, brief overviews of functional hierarchy modeling and Oracle’s process modeler are given. After a brief introduction to process modeling, data flow diagramming techniques are introduced in a section called â€Å"Data Flow Diagramming Mechanics. † This section demonstrates the basic DFD symbols, definitions, and rules. The authors use the Gane and Sarson symbol set throughout the book, and these symbols are explained in this section. Hoosier Burger, the food ordering system first mentioned in Chapter 2, is used to illustrate basic data flow diagramming concepts. This section also includes explanations of decomposition and balancing. Chapter 8’s third major section introduces four different types of DFDs: current physical, current logical, new logical, and new physical. Hoosier Burger’s inventory control system (which is manual) is used to illustrate the first three types of DFDs. Current practice in using DFDs indicates that very little time should be spent on the current physical DFD. We will write a custom essay sample on Software Requirement Specification or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page The fourth major section in this chapter, â€Å"Using Data Flow Diagramming in the Analysis Process,† introduces guidelines for drawing and using DFDs. This is different from the mechanical rules presented earlier. Topics include completeness, consistency, timing, iterative development, primitive DFDs, and analyzing DFDs for system inefficiencies and discrepancies among DFDs that are supposed to be modeling the same system. A Hoosier Burger example helps illustrate these guidelines. The â€Å"Oracle’s Process Modeler and Functional Hierarchy Diagrams† section introduces students to two other process modeling tools. These tools are Oracle Designer’s process modeler and functional hierarchy modeling, a tool found in several CASE products. In this section, the authors show how to prepare basic process models and functional hierarchy diagrams. Additionally, the authors compare and contrast Oracle’s process models to data flow diagramming. In the last section of this chapter, the authors’ overview process modeling for Internet-based electronic commerce applications. As they explain, process modeling for Internet-based electronic commerce applications does not differ from more traditional applications development projects. Instructional Objectives Specific student learning objectives are included at the beginning of the chapter. From an instructor’s point of view, the objectives of this chapter are to: 1. Show how to logically model processes with data flow diagrams. 2. Teach students data flow diagram symbols and the mechanical rules necessary to create accurate, well-structured process models. 3. Show students how to decompose data flow diagrams into lower-level diagrams. For people who are not familiar with data flow diagrams, the students should find that it is relatively easy to show them that data flow diagrams are a better way to model processes. Chances are that this person’s original picture already has many of the elements of a standard data flow diagram anyway. Research has found that process modeling is a very natural activity for most people, even when they are not formally trained in this technique.