Software Requirements Specification. CS 4350 Project. for. Version 1.0 approved. Prepared by Alvaro Juban Jr. Tejon Ranch Conservency

Transcription

1 Software Requirements Specification for CS 4350 Project Version 1.0 approved Prepared by Alvaro Juban Jr. Tejon Ranch Conservency Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

2 Software Requirements Specification for <Project> Page ii Table of Contents Table of Contents... ii Revision History...ii 1. Introduction Purpose Document Conventions Intended Audience and Reading Suggestions Product Scope References Overall Description Product Perspective Product Functions User Classes and Characteristics Operating Environment Design and Implementation Constraints User Documentation Assumptions and Dependencies External Interface Requirements User Interfaces Hardware Interfaces Software Interfaces Communications Interfaces System Features System Feature System Feature 2 (and so on) Other Nonfunctional Requirements Performance Requirements Safety Requirements Security Requirements Software Quality Attributes Business Rules Other Requirements... 5 Appendix A: Glossary...5 Appendix B: Analysis Models... 5 Appendix C: To Be Determined List... 6 Revision History Name Date Reason For Changes Version

3 Software Requirements Specification for CS 4350 Page 1 1. Introduction 1.1 Purpose The purpose of this project is to work with a client and create an application for them. Our client is the Tejon Ranch Conservancy. This mobile application will help visitors or staff identify one of the many flowers that inhabit Tejon. 1.2 Document Conventions Created using Open Office and exported into a.pdf file. 1.3 Intended Audience and Reading Suggestions Intended for client of Tejon Ranch Conservancy and other developers. 1.4 Product Scope Application created for Tejon Ranch Conservancy in order to let users identify one of the many flowers that inhabit Tejon. 1.5 References 2. Overall Description 2.1 Product Perspective This is a brand new application for Tejon Ranch Conservancy. Although the concept of identifying a flower has been done before, this application is made specifically users traversing Tejon Ranch. 2.2 Product Functions The major function of this application is identifying a flowers. This is done by asking the user a series of questions in order filter out all the flowers that can be found in Tejon Ranch. Once answers have been provided our application will give the user the results of what flower they have identify. Another function would be browsing, which allows the user to scroll through the flowers that can be found in Tejon Ranch and see where they can be located. The application will also provide an interactive map and a the history of Tejon Ranch.

4 Software Requirements Specification for CS 4350 Page User Classes and Characteristics The knowledge of the programming language Java including the use of creating an application in Android Studio. 2.4 Operating Environment Developed using android studio and emulation with genymotion. For this application we have been using android KitKat which happens to use an API 19. This app has been tested with Nexus 5 emulator and a physical Samsung Galaxy phone. 2.5 Design and Implementation Constraints This application is made specifically for use within Tejon Ranch and may not be applicable to identify flowers found outside of Tejon Ranch. Application must be fast and simple to use. The actual application must have information available within app because reception is not reliable inside of Tejon Ranch. The customer must provide the information of the flowers in order to help us create the flower identifier. 2.6 User Documentation User will be able to find a manual located within the applications settings option. This manual will describe functions of the app including how to use said functions. 2.7 Assumptions and Dependencies Must be sure that all information is correct and photos that are used are credited to its rightful owners. Application must meet the needs of customer and features may be added or change if need be. 3. External Interface Requirements 3.1 User Interfaces GUI will be easy to navigate through and will provide a pleasant and engaging experience. Such as fast and smooth transitions between the applications many different features. 3.2 Hardware Interfaces This application was created and intended to be used in an android environment. Mostly made for the use of android cellphones and also android tablets. 3.3 Software Interfaces Application has been created for android platforms using android studio. Which means that this the use of java is being used heavily. No uses for online databases or the use of gps due to limitations. A simple local database will be use to access the information and photos of each flower.

5 Software Requirements Specification for CS 4350 Page Communications Interfaces Instead of pulling information through gps or internet, all information will be available to the user through the application. This choice was chosen because reception isn t consistent within the grounds of Tejon Ranch. 4. System Features 4.1 Identify a Flower Description and Priority This is feature is of high priority and is the main purpose of this application. Will help the user identify an unknown flower by asking the user a series of questions. Based on the answers provided the application will show the results of the potential flower they have described Stimulus/Response Sequences The user will only need to answer the questions as best they can by tapping the answer that best describes the flower in front of them. From there they will click next and will be asked another question. This will be done until the app has decided what flower has been described Functional Requirements In order to carry out this function we need a database of flowers that can be found at Tejon Ranch. We also need specific features of each flower such as what color and how many petals each one has. REQ-1: REQ-2: Must be simple and easy for the user to navigate through. Must provide all information be located within application rather then an online database. 4.2 Browse the Flowers Description and Priority This feature is of the high priority. With this feature the user will be able to browse through the flowers that can be found within Tejon Ranch Stimulus/Response Sequences This feature will look similar to an image gallery. The user will simply be able to scroll through the different flowers. When they want to learn more they can simply tap the photo and will be able to see the picture, name, bio, and location of the flower Functional Requirements The requirements of this feature would require the data that has been gathered by the customer themselves. Mainly for the short descriptions of each flower and possibly photos too. REQ-1: REQ-2: Must be fast and snappy when scrolling through the different flowers. Provide the location of current flower being browsed.

6 Software Requirements Specification for CS 4350 Page 4 5. Other Nonfunctional Requirements 5.1 Performance Requirements This application is made solely for the use on a mobile device, specifically an android device. Must be able to run on android kitkat and above. That way anyone can use the application and will not be limited by their system firmware. 5.2 Safety Requirements The user must be aware of surroundings when using this within Tejon Ranch because of unpredictable wildlife and environmental hazards around them. 5.3 Security Requirements Information of flowers will be provided by the customer and belongs solely to the customer. So we must protect this by restricting access by outside users. 5.4 Software Quality Attributes Application will be able to adjust its display to any android firmware and phone screen size. Basically dynamic rescaling of the app for any platform such as phones and larger tablets. 5.5 Business Rules Must not use information and photos within application without crediting owners of said content. 6. Other Requirements <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.> Appendix A: Glossary <Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.> Appendix B: Analysis Models <Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

7 Software Requirements Specification for CS 4350 Page 5 Appendix C: To Be Determined List <Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.>