SRS"Children Learning System
1
Introduction:
Here is the
introduction of all the aspects required of children’s learning system. It include
all those factors that lead to development of the software requirements
specification of children learning system type software.
1.1
Purpose:
This SRS will try to cover all the
requirements which are needed to develop a desktop type or net based software
where small aged group children can play and have fun mean while something
to learn. If you are a develop and want to work on a system which should
benefit children
than you are on right place. We have given almost all the requirements in this
SRS necessary to
build a software for children.
1.2
Document Conventions:
Text style is
Calibri. Priority shown for a high-level requirement is inherited by all its
detailed requirements.
1.3
Intended Audience and Reading Suggestions:
This Software Requirements Specification (SRS) is intended for use of the Children learning system
developers and primarily myself. It is also for use by users and auxiliary
developers of children learning system as background reference material.
1.4
Project Scope:
The name of the system for which this SRS is
written is “Children’s Learning System”. As the name implies that this is going
out to be system for children and specifically for learning. It will learn them basic English letters, names of
colors, names of different daily life objects which have most interaction with
children, counting to almost 50 or 100. These all basics thing that a child go
through before going to KG school. So we thought why not to provide basic
simple software that covers all these things.
1.5
References:
Children play & learn (available on windows 8.1 store
App).
Children Learn & Play (Available on
Microsoft Windows 8.1 Store App).
Kids Learning (available on Windows 8.1
store App).
2.
Overall Description:
Here we will try to cover all those general
factors that may affect our final product and its requirements. So here we will
talk about product perspective, product functions, user characteristics, constraints,
assumptions and dependencies and apportioning of requirements. So the detail of
all of these general factors is described below.
2.1
Product Perspective:
This system is
totally independent of any other software. We shall try to develop a desktop
simple user friendly software that any kid would love to play and have ease of
access.
2.2
Product Features:
We are developing a quite simple system. Basic
functionalities that this system is going to cover are creating a learning
environment for children, Help parents to involve their children in productive
things without too many efforts. Help children to have fun playing on PC. Help
parents to their office work while their little babies indulged in playing
adductive learning software.
2.3
User Classes and Characteristics:
Our software is too easy to
operate anyhow user should have at least idea how to start a PC, how to run any
software, how to install, download and operate a basic software like net
browser for example. User should run the software and make it available for
their child to play with this software. PC mouse will be handed to child, who
by random clicks on software interface will learn and play as well.
2.4 Operating Environment:
It’s a desktop application. It can be run on
any PC. However, the primary operating systems we'll be any Microsoft Window 8.
User should enter its name and he/she can use this application. Software
components or applications with which the system must peacefully coexist.
2.5
Design and Implementation Constraints:
To
run the software, at least windows 8 installed No. other operating environment is
accepted to run the software. Memory requirements are at least 2 GB with
processing power of Dual Core at least.
2.6
User Documentation:
It includes user manuals, online help, and tutorials.
2.7
Assumptions and Dependencies:
As child learning system is a
self-contained project, the only explicit dependencies are those stated in the
Design and Implementation Constraints.
One SRS reader might assume that product
will conform to a particular user interface convention. The user must
have Microsoft Windows. The user must enter his/her name before using.
3.
System Features:
3.X System Feature X:
Counting,
alphabet, complete the missing words, +, * , / operation. Chose the picture
that given name. chose color of pictures,
3.
X.1 Description and Priority:
1. counting.
2.
Alphabet.
3. complete missing words.
3. X.2 Stimulus/Response Sequences:
When User log in through putting his account id & password then
access his account. After the accessing, user start the playing by selecting
features. When one level complete then high score display and give
congratulation and award some to the learner, move to the next level.
3. X.3 Functional Requirements:
When User log in through putting his account id & password then
access his account. After the accessing, user start the playing by
selecting features. When one level complete then high score display and give
congratulation and award some to the learner, move to the next level.Counting, alphabet, complete the missing words, +, * ,
/ operation. Chose the picture that given name. chose color of pictures, are
includes.
4.
External Interface Requirements:
The system
shall run on Microsoft Windows 7/8/8.1. The system shall not support any other operating
environment. The hardware required for system is not having any priority. Any
system with at least 512 MB of RAM and Pentium 4 at least can run our system.
We are developing the system in .NET so latest version of .NET Frame Work
should be installed on the system, Currently available version of .NET frame
work available in market is .NET 4.2.1. The system is stand alone software and
so not dependent on any other software or requirements of hardware excepted mentioned.
4.1
User Interfaces:
References to GUI standards or product
family style guides that are to be followed. Standards for fonts, icons, button
labels, images, color schemes, field tabbing sequences, commonly used controls,
and the like. Screen layout or resolution constraints. Standard buttons,
functions, or navigation links that will appear on every screen, such as a help
button. Layout standards to facilitate software localization. Accommodations
for visually impaired users.
4.2 Hardware Interfaces:
The system
shall run on Microsoft Windows 7/8/8.1.The system shall not support any other operating
environment. The hardware required for system is not having any priority. Any
system with at least 512 MB of RAM and Pentium 4 at least can run our system.
4.3
Software Interfaces:
.NET Frame Work should be installed on the system, currently
available version of .NET frame work available in market is .NET 4.2.1. The
system is stand alone software and so not dependent on any other software
except that is mention.
4.4 Communications
Interfaces:
As
the children learning system is desktop app so no communication interface is
required.
5.
Other Nonfunctional Requirements:
|
Availability
|
|
Efficiency
|
|
Flexibility
|
|
Integrity
|
|
Interoperability
|
|
Reliability
|
|
Robustness
|
|
Usability
|
5.1
Performance Requirements:
State specific performance
requirements for various system operations. Explaination their rationale to
guide the developers in making appropriate design choices. For instance,
stringent database response time demands might lead the designers to mirror the
database in multiple geographical locations or to demoralize relational
database tables for faster query responses. Specify the number of transactions
per second to be supported, response times, computational accuracy, and timing
relationships for real-time systems. You could also specify memory and disk
space requirements, concurrent user loads, or the maximum number of rows stored
in database tables. If different functional requirements or features have
different performance requirements, it's appropriate to specify those
performance goals right with the corresponding functional requirements, rather
than collecting them all in this one section.
5.2
Safety Requirements:
The system shall terminate any operation within 1
second .The
system remain pen only through continuous computer control. The shield shall
automatically fall into place if computer control is lost for any reason.
5.3
Security Requirements:
Specify
any requirements regarding security, integrity, or privacy issues that affect
access to the product, use of the product, and protection of data that the
product uses or creates. Security requirements normally originate in business
rules, so identify any security or privacy policies or regulations to which the
product must conform. Alternatively, you could address these requirements
through the quality attribute called integrity. Log in system
5.4
Software Quality Attributes:
One way to classify attributes distinguishes
those characteristics that are noticeable at run time.
Another approach
is to separate qualities that are primarily significant to technical staff and
primarily important to the users.
The latter indirectly contribute to customer
satisfaction by making the product easier to change, correct, verify, and
migrate to new platforms.
6.
Other Requirements:
Appendix
A: Glossary:
Appendix
B: Analysis Models:
Appendix
C: Issues List:
