Students Academic Performance System

Version 1.0 Prepared by Group Name: Lakshya

Software Requirements Specification for

Vikas Kumar Verma Manish Kumar Singh Vedanuj Goswami

09-1-5-052 09-1-5-057 09-1-5-049

[email protected] <e-mail> <e-mail>

Instructor: Sushil Kumar

Course: Software Engineering Date: 24/September/2012

Software Requirements Specification for Students Academic Performance System Page ii

Contents
<IN THIS TEMPLATE YOU WILL FIND TEXT BOUNDED BY THE <> SYMBOLS. THIS TEXT APPEARS IN ITALICS AND IS INTENDED TO GUIDE YOU THROUGH THE TEMPLATE AND PROVIDE EXPLANATIONS REGARDING THE DIFFERENT SECTIONS IN THIS DOCUMENT. THERE ARE TWO TYPES OF COMMENTS IN THIS DOCUMENT. THESE COMMENTS THAT ARE IN BLACK ARE INTENDED SPECIFICALLY FOR THAT COURSE. THESE COMMENTS THAT ARE IN BLUE ARE MORE GENERAL AND APPLY TO ANY SRS. PLEASE, MAKE SURE TO DELETE ALL OF THE COMMENTS BEFORE SUBMITTING THE DOCUMENT. ................................III THE EXPLANATIONS PROVIDED BELOW, DO NOT COVER ALL OF THE MATERIAL, BUT MERELY, THE GENERAL NATURE OF THE INFORMATION YOU WOULD USUALLY FIND IN SRS DOCUMENTS. IT IS BASED ON THE IEEE REQUIREMENTS AND WAS ADAPTED SPECIFICALLY FOR THE NEEDS OF SOFTWARE ENGINEERING 3K04/3M04 COURSES. MOST OF THE SECTIONS IN THIS TEMPLATE ARE REQUIRED SECTIONS, I.E. YOU MUST INCLUDE THEM IN YOUR VERSION OF THE DOCUMENT. FAILURE TO DO SO WILL RESULT IN MARKS DEDUCTIONS. OPTIONAL SECTIONS WILL BE EXPLICITLY MARKED AS OPTIONAL. IF YOU HAVE ANY QUESTIONS REGARDING THIS DOCUMENT PLEASE REFER TO THE MINITHERMOSTAT SRS EXAMPLE ON THE COURSE WEB-SITE.>.......................................................III 1 INTRODUCTION...........................................................................................................................................................1 2 OVERALL DESCRIPTION..........................................................................................................................................5 3 SPECIFIC REQUIREMENTS.....................................................................................................................................7 4 OTHER NON-FUNCTIONAL REQUIREMENTS.................................................................................................9 5 OTHER REQUIREMENTS.......................................................................................................................................10

Revisions
Version Draft Type and Number Primary Author(s) Full Name Description of Version Information about the revision. This table does not need to be filled in whenever a document is touched, only when the version is being upgraded. Date Completed 00/00/00

Software Requirements Specification for Students Academic Performance System Page iii

<In this template you will find text bounded by the <> symbols. This text appears in italics and is intended to guide you through the template and provide explanations regarding the different sections in this document. There are two types of comments in this document. These comments that are in black are intended specifically for that course. These comments that are in blue are more general and apply to any SRS. Please, make sure to delete all of the comments before submitting the document. The explanations provided below, do not cover all of the material, but merely, the general nature of the information you would usually find in SRS documents. It is based on the IEEE requirements and was adapted specifically for the needs of Software Engineering 3K04/3M04 courses. Most of the sections in this template are required sections, i.e. you must include them in your version of the document. Failure to do so will result in marks deductions. Optional sections will be explicitly marked as optional. If you have any questions regarding this document please refer to the MiniThermostat SRS example on the course web-site.>

Software Requirements Specification for Students Academic Performance System

Page 1

1 Introduction
<TO DO: Please provide a brief introduction to your project and a brief overview of what the reader will find in this section.>

1.1 Document Purpose

The purpose of the Software Requirements Specification (SRS) is to give the customer a clear and precise description of the functionality of the assessment-support software to be developed and to eliminate ambiguities and misunderstandings that may exist. For the customer, the SRS will explain all functions that the software should perform. For the developer, it will be a reference point during software design, implementation and maintenance. The SRS divides the system requirements into two parts, behavioural and non-behavioural requirements. The behavioural requirements describe the interaction between the system and its environment. Non-behavioural requirements relate to the definition of the attributes of the product as it performs its functions. This includes the level of security, efficiency, reliability, maintainability, portability, capacity, and the standards of compliance of the product. This document serves as an agreement between both parties regarding the product to be developed.

1.2 Product Scope

The Students Academic Performance System is a package that has been designed to maintain the details of the performance of students in an academic session which provides the students proper information. This application has been coded using JAVA.

1.3 Definitions, Acronyms and Abbreviations

The definitions in this section are given in the context of the product being developed. This intention is to assist the user in their understanding of the requirements for the system. TERM A-K Accreditation Archive Assessment DEFINITION Program outcomes defined by ABET Engineering Criteria 2000. Please refer to [1] for a complete list. Process of determining whether colleges or departments meet a set of standards as set forth by an accrediting agency, such as ABET. To maintain data in a designated repository; in CACQI, data will be maintained in the central database. The systematic and periodic evaluation of whether students are achieving the learning outcomes associated with a given course.

Software Requirements Specification for Students Academic Performance System

Page 2

Assessment instrument

a) The tool used to assess students skills and knowledge in a course, e.g, test, quiz, report, observation. b) An assessment instrument is composed of one or more assessment instrument parts. An assessment instrument unit or a set of assessment instrument parts. An element of an assessment instrument for which grades may be assigned and that maps to a single outcome, e.g., a question on an exam. A course request number The intersection of a row and a column in a spreadsheet. An Oracle relational database maintained by the College of Engineering to store course data from all departments. The systematic pursuit of excellence and satisfaction of the needs of constituencies, in a dynamic and competitive environment. Identifier assigned by the university that names a course when used with a subject identifier. A course identified with a course request number. Measurable statements of the knowledge, skills, attitudes, and habits of mind that students are equipped with when graduating from an educational program; also called objectives in some communities. Unique, five-digit identifier assigned by the university to identify each course. Transferring data files from a main source to a secondary source. The alteration of data so that it is meaningful only to the intended receiver. An Oracle relational database stored on one or more machines at the departmental level. The linkages of two objects, e.g., an outcome to an assessment unit. A hierarchical representation of a tree in which each successor node is indented to the right of its predecessor node and all nodes at the same level are uniformly indented. The general user that defined a new course is considered the owner of the course. A set of skills, knowledge, attitudes, and habits of mind that students are equipped with when they graduate from an engineering educational program, e.g., computer science or civil engineering. A list of properties or attributes associated with an object; in CACQI this is a list of login names of the users who can access course data and the list is associated with a

Assessment instrument part Assessment instrument unit Call Number Cell Central database Continuous Quality Improvement Course number Course section Course-section outcome

Course Request Number Download Encrypt Local database Mapping Navigation tree

Owner Program outcomes

Property list

Software Requirements Specification for Students Academic Performance System

Page 3

course section. Ranking Section number Server Spreadsheet Subject identifier Targeted competency University database User User profile Weight 1.3.1 Acronyms ACRONYM AI AIP AIU BNF CACQI (pronounced Khaki) CQI CRN DBMS DFD GUI OMT SRS TBD UTEP 1.3.2 Abbreviations ABBREVIATION e.g. MEANING For example MEANING Assessment Instrument Assessment Instrument Part Assessment Instrument Unit Backus Naur Form Classroom Assessment for Continuous Quality Improvement Continuous Quality Improvement Course Request Number Database Management System Data Flow Diagram Graphical Use Interface Object Modeling Technique Software Requirements Specification To Be Determined The University of Texas at El Paso The level of importance of an outcome. A 3-digit field that corresponds to a course. The main computer in a network. A central computer that connects and services those computers (clients) attached to it. The work area for entering grades that appears as a table with rows and columns. A 4-character field that corresponds to a subject. A quantitative reference for student performance on a particular outcome; quantifies how well students are expected to perform. An Oracle relational database, maintained by the university, that stores student and course information. A person who provides the data for a computer system, updates the data, and uses reports from the system in his or her daily work. User characteristics maintained by the system A factor used to adjust a value.

Software Requirements Specification for Students Academic Performance System

Page 4

id i.e. info.

Identification Such as Information

1.4 References
[1] ABET Homepage: Accreditation Board of Engineering and Technology. December 15, 2000. Online Posting. Available: http://www.abet.org/
[2] [3] [4] [5]

Gates, A., Requirements Definition, CS4310 Handout, September 6, 2000. Gates, A., Memorandum RE: ABET CQI Project, e-mail message dated 11/12/2000, 2:31 p.m. Gates, A., Message from Dr. Lush, e-mail message dated 11/14/200, 5:58 p.m. International Software Development, OmegaSoft Development, Renaissance Software Developers, Strategic Engineering Team, Strategy X, Utopia Software, Interview Report. September 2000. International Software Development, OmegaSoft Development, Renaissance Software Developers, Strategic Engineering Team, Strategy X, Utopia Software, Feasibility Report, September 2000.

[6]

Software Requirements Specification for Students Academic Performance System

Page 5

2 Overall Description
2.1 Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. In this part, make sure to include a simple diagram that shows the major components of the overall system, subsystem interconnections, and external interface. In this section it is crucial that you will be creative and provide as much information as possible. TO DO: Provide at least one paragraph describing product perspective. Provide a general diagram that will illustrate how your product interacts with the environment and in what context it is being used.>

2.2 Product Functionality

<Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, will be effective. TO DO: 1. Provide a bulleted list of all the major functions of the system 2. (Optional) Provide a Data Flow Diagram of the system to show how these functions relate to each other.>

2.3 Users and Characteristics

<Identify the various users that you anticipate will use this product. Users may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. TO DO: 1. Describe the pertinent characteristics of each user. Certain requirements may pertain only to certain users. 3. Distinguish the most important users for this product from those who are less important to satisfy.>

2.4 Operating Environment

<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist. In this part, make sure to include a simple diagram that shows the major components of the overall system, subsystem interconnections, and external interface TO DO: As stated above, in at least one paragraph, describe the environment your system will have to operate in. Make sure to include the minimum platform requirements for your system. >

Software Requirements Specification for Students Academic Performance System

Page 6

2.5 Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These might include: hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customers organization will be responsible for maintaining the delivered software). TO DO: In this section you need to consider all of the information you gathered so far, analyze it and correctly identify at least 5 constraints.>

2.6 User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards. TO DO: You will not actually develop any user-manuals, but you need to describe what kind of manuals and what kind of help is needed for the software you will be developing. One paragraph should be sufficient for this section.>

2.7 Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project. TO DO: Provide a short list of some major assumptions that might significantly affect your design. For example, you can assume that your client will have 1, 2 or at most 50 Automated Banking Machines. Every number has a significant effect on the design of your system. >

Software Requirements Specification for Students Academic Performance System

Page 7

3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
<Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., Cancel) that will appear on every screen, error message display standards, and so on. Define the software components for which a user interface is needed. TO DO: The least you can do for this section is to describe in words the different User Interfaces and the different screens that will be available to the user. Those who will be able to provide optional Graphical User Interface screenshots, will be rewarded by extra marks.>

3.1.2 Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware. You are not required to specify what protocols you will be using to communicate with the hardware, but it will be usually included in this part as well. TO DO: Please provide a short description of the different hardware interfaces. If you will be using some special libraries to communicate with your software mention them here. In case you have more than one hardware interface divide this section into subsections.>

3.1.3 Software Interfaces

<Describe the connections between this product and other specific software components (name and version), including databases, operating systems (Windows? Linux? Etc), tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint. TO DO: The previous part illustrates some of the information you would usually include in this part of the SRS document. To make things simpler, you are only required to describe the specific interface with the operating system.>

3.1.4 Communications Interfaces

<Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms. TO DO: Do not go into too much detail, but provide 1-2 paragraphs were you will outline the major communication standards. For example, if you decide to use encryption there is no need to specify

Software Requirements Specification for Students Academic Performance System

Page 8

the exact encryption standards, but rather, specify the fact that the data will be encrypted and name what standards you consider using. >

3.2 Functional Requirements

< Functional requirements capture the intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform. This section is the direct continuation of section 2.2 where you have specified the general functional requirements. Here, you should list in detail the different product functions with specific explanations regarding every function. TO DO: Brake the functional requirements to several functional areas and divide this section into subsections accordingly. Provide a detailed list of all product operations related to these functional areas.

3.3 Behaviour Requirements

3.3.1 Use Case View
<A use case defines a goal-oriented set of interactions between external actors and the system under consideration. Since sometimes we will not be able to specify completely the behaviour of the system by just State Diagrams, we use use-cases to complete what we have already started in section 3.3.1. TO DO: Provide a use case diagram which will encapsulate the entire system and all possible actors. Do not include detailed use case descriptions (these will be needed when you will be working on the Test Plan), but make sure to include a short description of what every use-case is, who are the actors in your diagram. For more information please refer to your UML guide and the MiniThermostat SRS example file.>

Software Requirements Specification for Students Academic Performance System

Page 9

4 Other Non-functional Requirements

4.1 Performance Requirements
<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features. TODO: Provide at least 5 different performance requirements based on the information you collected from the client. For example you can say 1. Any transaction will not take more than 10 seconds, etc>

4.2 Safety and Security Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the products design or use. Define any safety certifications that must be satisfied. Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. TODO: Provide at least 3 different safety requirements based on your interview with the client or, on your ABM related research, and again you need to be creative here. Describe briefly what level of security is expected from this product by your client and provide a bulleted (or numbered) list of the major security requirements.>

4.3 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning. TODO: Use subsections (e.g., 4.3.1 Reliability, 4.3.2 Portability, etc) provide requirements related to the different software quality attributes. Base the information you include in these subsections on the material you have learned in the class. Make sure, that you do not just write This software shall be maintainable Indicate how you plan to achieve it, & etcDo not forget to include such attributes as the design for change. Please note that you need to include at least 2 quality attributes, but it is the mere minimum and it will not receive the full marks.>

Software Requirements Specification for Students Academic Performance System

Page 10

5 Other Requirements
<This section is Optional. Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Software Requirements Specification for Students Academic Performance System

Page 11

Appendix A Data Dictionary

<Data dictionary is used to track all the different variables, states and functional requirements that you described in your document. Make sure to include the complete list of all constants, state variables (and their possible states), inputs and outputs in a table. In the table, include the description of these items as well as all related operations and requirements.>

Software Requirements Specification for Students Academic Performance System

Page 12

Appendix B - Group Log

<Please include here all the minutes from your group meetings, your group activities, and any other relevant information that will assist the Teaching Assistant to determine the effort put forth to produce this document>