Beruflich Dokumente
Kultur Dokumente
Specification
for
<Project>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
TableofContents
TableofContents...........................................................................................................................
RevisionHistory.............................................................................................................................
1. Introduction..............................................................................................................................
1.1
1.2
1.3
1.4
1.5
Purpose
1
DocumentConventions 1
IntendedAudienceandReadingSuggestions
ProductScope 1
References
1
2. OverallDescription..................................................................................................................
2.1
2.2
2.3
2.4
ProductPerspective
2
ProductFunctions
2
UserClassesandCharacteristics
OperatingEnvironment 2
2.5 DesignandImplementationConstraints 2
2.6 UserDocumentation 2
2.7 AssumptionsandDependencies3
3. ExternalInterfaceRequirements...........................................................................................
3.1
3.2
3.3
3.4
UserInterfaces 3
HardwareInterfaces
3
SoftwareInterfaces
3
CommunicationsInterfaces
4. SystemFeatures.......................................................................................................................
4.1 SystemFeature1
4
4.2 SystemFeature2(andsoon)
5. OtherNonfunctionalRequirements.......................................................................................
5.1
5.2
5.3
5.4
5.5
PerformanceRequirements
SafetyRequirements 5
SecurityRequirements 5
SoftwareQualityAttributes
BusinessRules 5
4
5
6. OtherRequirements................................................................................................................
AppendixA:Glossary....................................................................................................................
AppendixB:AnalysisModels.......................................................................................................
AppendixC:ToBeDeterminedList............................................................................................
RevisionHistory
Name
Date
ReasonForChanges
Version
Introduction
Purpose
Thisdocumentdescribesthehardwarerequirementsforanautomatedremainder
band.Itisintendedforthepeopletoremindabouttheirworktobedonewithinthe
specifictime.
DocumentConventions
Sub Heading: 14, Bold and Left Aligned
IntendedAudienceandReadingSuggestions
<Describe the different types of reader that the document is intended for, such as
developers, project managers, marketing staff, users, testers, and documentation
writers. Describe what the rest of this SRS contains and how it is organized. Suggest a
sequence for reading the document, beginning with the overview sections and
proceeding through the sections that are most pertinent to each reader type.>
ProductScope
The basic aim of this project is to remind about the specific task which to be done on
time. It can be used by teachers, students, businessmen, children as all of us have a busy
hectic schedule.
References
ThefollowingarethereferencesareusedinpreparingSRSdocument
TheSRSsampleandtemplatehttps://web.cs.dal.ca/~hawkey/3130/srs_templateieee.doc.
Wikipedia
OverallDescription
ProductPerspective
In our daily life we get busy with our day to day activities .We forget some of our
important things that we have to do like we forget to take medicine or to do some
work .We need some remainder that can help us to remind about the specific work that
has to be done .Using the remainder alarm we can do our things on time without
forgetting it. It allows users to set an alarm along with the fields of time which will allow
them to set alarm for multiple alarms at different time intervals. The notification system
will send a notification after setting an alarm. The user can activate or deactivate the
notification accordingly
ProductFunctions
It can be used by teachers, students, businessmen, children as all of us have a busy hectic
schedule. Thehardwareprojectisexpectedtoofferfollowingservices:
1.foroffices:
Itremindstheemployeeaboutthemeetingtimewhichhehastoattend.
2.forhospitals:
Itremindsthepatientaboutthemedicinehehastotakeontime.
3.forCollege:
Itremindsthestudentsabouttheclasstimings.
Therearemanyotherapplicationsoftheproject
UserClassesandCharacteristic
The design time constraints are:
In this we can set max 5 alarms which will have different color for each alarm.
More alarms
OperatingEnvironment
The environment in which this application runs are categorized in two category and :they are
Hardware Platform:
512 MB RAM
800MGHz of microprocessor
Software Platform:
DesignandImplementationConstraints
The issues to the developers are at hardware level as well as software i.e., for
developing the exploring the world we need at least 8GB of RAM. The tools which are
used for developing are JDK, ADK, Android Studio (IDE), core JAVA etc.The
Environment requires a lot of resources and works strictly with 64 bit operating systems.
UserDocumentation
The details of analysis ,design and test cases of this software is included.
AssumptionsandDependencies
There are no assumptions made.
ExternalInterfaceRequirements
UserInterfaces
Thedetails
HardwareInterfaces
Hardware Platform:
512 MB RAM
800MGHz of microprocessor
SystemFeatures
OtherNonfunctionalRequirements
OtherRequirements
More alarms can be added with little modifications.
AppendixA: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.>
AppendixB:AnalysisModels
<Optionally, include any pertinent analysis models, such as data flow diagrams, class
diagrams, state-transition diagrams, or entity-relationship diagrams.>
AppendixC:ToBeDeterminedList
<Collect a numbered list of the TBD (to be determined) references that remain in the
SRS so they can be tracked to closure.>