logo

Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322

23 Pages3430 Words202 Views
   

Added on  2020-04-13

About This Document

Software Requirements Specification Template CptS 322—Software Engineering 9 February 2005 The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. Development of Student Management System for Willowbrook School Software Requirements Specification Version> Date> Your Name> Lead Software Engineer Prepared for WSU-TC CptS 322—Software Engineering Principles I Instructor: A. Spring 2005 Revision History |Date |Description

Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322

   Added on 2020-04-13

ShareRelated Documents
Software Requirements Specification TemplateCptS 322—Software Engineering9 February 2005The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any modifications to the overall structure of this document.Template Usage:Text contained within angle brackets (‘<’, ‘>’) shall be replaced by your project-specific information and/or details. For example, <Project Name> will be replaced with either ‘Smart Home’ or ‘Sensor Network’.Italicized text is included to briefly annotate the purpose of each section within this template. This text should not appear in the final version of your submitted SRS.This cover page is not a part of the final template and should be removed before your SRS is submitted.Acknowledgements:Sections of this document are based upon the IEEE Guide to Software Requirements Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU, Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing thistemplate for the WSU-TC Spring 2005 CptS 322 course.WSU-TC CptS 322Software Requirements Specification Template
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_1
Development of Student Management Systemfor Willowbrook SchoolSoftware Requirements Specification<Version><Date><Your Name>Lead Software EngineerPrepared forWSU-TC CptS 322—Software Engineering Principles IInstructor: A. David McKinnon, Ph.D.Spring 2005
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_2
Development of Student Management System for Willowbrook SchoolRevision HistoryDateDescriptionAuthorComments<date>Version 1.0<Your Name><First Revision>Document ApprovalThe following Software Requirements Specification has been accepted and approved by the following:SignaturePrinted NameTitleDate<Your Name>Lead Software Eng.A. David McKinnonInstructor, CptS 322Software Requirements SpecificationPage ii
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_3
Development of Student Management System for Willowbrook SchoolTable of ContentsREVISION HISTORY................................................................................................................................................IIDOCUMENT APPROVAL........................................................................................................................................II1. INTRODUCTION.....................................................................................................................................................11.1 PURPOSE...............................................................................................................................................................11.2 SCOPE...................................................................................................................................................................11.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................11.4 REFERENCES.........................................................................................................................................................11.5 OVERVIEW............................................................................................................................................................22. GENERAL DESCRIPTION....................................................................................................................................22.1 PRODUCT PERSPECTIVE........................................................................................................................................22.2 PRODUCT FUNCTIONS...........................................................................................................................................22.3 USER CHARACTERISTICS......................................................................................................................................22.4 GENERAL CONSTRAINTS.......................................................................................................................................22.5 ASSUMPTIONSAND DEPENDENCIES......................................................................................................................33. SPECIFIC REQUIREMENTS................................................................................................................................33.1.1 User Interfaces.............................................................................................................................................33.1.2 Hardware Interfaces....................................................................................................................................33.1.3 Software Interfaces......................................................................................................................................33.1.4 Communications Interfaces.........................................................................................................................33.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................33.2.1 Registration..................................................................................................................................................33.2.2 Attendance Management..............................................................................................................................43.3 USE CASES............................................................................................................................................................43.3.1 Use Case #1.................................................................................................................................................43.3.2 Use Case #2.................................................................................................................................................53.4 CLASSES / OBJECTS..............................................................................................................................................63.4.1 Schedule.......................................................................................................................................................63.4.1.1 Attributes...................................................................................................................................................63.4.1.2 Functions...................................................................................................................................................73.4.2 Student_attendance......................................................................................................................................73.4.1 Schedule.......................................................................................................................................................73.4.1.1 Attributes...................................................................................................................................................73.4.1.2 Functions...................................................................................................................................................73.5 NON-FUNCTIONAL REQUIREMENTS......................................................................................................................73.5.1 Performance.................................................................................................................................................73.5.2 Reliability.....................................................................................................................................................73.5.3 Availability...................................................................................................................................................73.5.4 Security........................................................................................................................................................73.5.5 Maintainability.............................................................................................................................................73.5.6 Portability....................................................................................................................................................73.6 INVERSE REQUIREMENTS......................................................................................................................................83.7 DESIGN CONSTRAINTS..........................................................................................................................................83.8 LOGICAL DATABASE REQUIREMENTS..................................................................................................................83.9 OTHER REQUIREMENTS........................................................................................................................................84. ANALYSIS MODELS..............................................................................................................................................94.1 SEQUENCE DIAGRAMS..........................................................................................................................................94.3 DATA FLOW DIAGRAMS (DFD).........................................................................................................................10Software Requirements SpecificationPage iii
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_4
Development of Student Management System for Willowbrook School4.2 STATE-TRANSITION DIAGRAMS (STD)..............................................................................................................115. CHANGE MANAGEMENT PROCESS..............................................................................................................11BIBLIOGRAPHY.......................................................................................................................................................13A. APPENDICES........................................................................................................................................................15A.1 APPENDIX 1: GLOSSARY....................................................................................................................................15A.2 APPENDIX 2: USER INTERFACE..........................................................................................................................16A) HOME PAGE.........................................................................................................................................................16B) STUDENT LOGIN..................................................................................................................................................17C) Faculty Login......................................................................................................................................................18Software Requirements SpecificationPage iv
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_5
Development of Student Management System for Willowbrook School1. IntroductionThe software requirement specification is created by the project manager for the development ofthe information system and stating the main purpose, scope and limitation of the project. Thedocument is created for including the steps followed for the development of the informationsystem. A SDLC model is used for the development of the project and the requirement iscategorized into functional and nonfunctional requirements for the identification of the needs ofthe information system. Different models such as class diagram, use case, Sequence Diagrams,Data Flow Diagrams (DFD), and State-Transition Diagrams (STD) are used for designing theinformation system. 1.1 PurposeThe main purpose of the software requirement specification document is to make therequirement of the project clear and reduce the chances of errors during the development of theinformation system. The audience of the SRS document are the stakeholders associated with theproject.1.2 ScopeThe software product required for the development of the information system is Microsoft VisualStudio 2012, Microsoft Access 2013, etc. Microsoft Visual Studio is used for building the interface of the information system with propervalidation that would restrict the user to input wrong information into the information system.Microsoft Access is used for the development of the database of the information system andstore the details of the student and the courses inputted by the users.The main purpose of the development of the information system is to allow the administrator tomanage the student information of the school and reduce the error in the management process forincreasing the efficiency of the organization. With the implementation of the information system in the organization the overhead cost can bereduced and the different level of users can use the system for getting the details such as thestudent can access the information system for getting their time tables, exam schedules, teacherscan use it for tracking the record of a student and access the Couse materials, etc.1.3 Definitions, Acronyms, and AbbreviationsFor the development of the student management system the records of the student must behandled and maintenance of the information manually is difficult (Nassif, Capretz & Ho, 2016).The manual management of the information system can cause error and thus there is arequirement for the up gradation of the current operation and develop the information systemaccording to the requirement of the organization. 1.4 ReferencesDavid, F., & David, F. R. (2016). Strategic management: A competitive advantage approach,concepts and casesSoftware Requirements SpecificationPage 1
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322_6

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Software Requirements Specification Template for <Project Name>
|10
|1715
|50

Assignment On Airline Reservation Software Requirement
|27
|3396
|4141

Software Requirements Specification for Online Book Shopping
|35
|9476
|325

Software Requirements Specification Assignment
|22
|4543
|169

Requirements Specifications Document
|19
|1878
|374

Software Requirements Specification for Project
|12
|2850
|26