Module1-Assignment1-IEEE_Unicode
Module1-Assignment1-IEEE_Unicode
for
Unicode Converter Application
Table of Contents
Revision History........................................................................................................3
1. Introduction.........................................................................................................4
1.1 Purpose..........................................................................................................4
1.2 Scope.............................................................................................................4
1.3 Definitions, acronyms, and abbreviations.....................................................4
1.4 References.....................................................................................................5
1.5 Overview.......................................................................................................5
2. Overall description..............................................................................................5
2.1 Product perspective.......................................................................................5
2.1.1 System interfaces....................................................................................6
2.1.2 User interfaces........................................................................................6
2.1.3 Hardware interfaces................................................................................6
2.1.4 Software interfaces.................................................................................7
2.2 Product functionality.....................................................................................7
2.3 User characteristics.......................................................................................8
2.4 Constraints....................................................................................................8
2.5 Assumptions and dependencies....................................................................9
3. Specific requirements..........................................................................................9
3.1 External interfaces........................................................................................9
3.2 Functional requirements..............................................................................10
3.3 Performance requirements..........................................................................10
3.4 Design constraints.......................................................................................10
3.5 Software system attributes..........................................................................11
3.5.1 Reliability.............................................................................................11
3.5.2 Availability...........................................................................................11
3.5.3 Security.................................................................................................11
3.5.4 Maintainability......................................................................................11
3.5.5 Portability.............................................................................................12
Revision History
1.2 Scope
In a computer system, one code page can be supported in clean manner. But due to
globalizations, universal code page is required to support all characters of all
languages. All the major operating systems, browsers, editors, word processors and
applications and tools are supporting Unicode so it is necessary to use Indian
languages and scripts in the Unicode environment, which will resolve the
compatibility issue.
1.4 References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software
Requirements Specifications IEEE Computer Society, 1998
1.5 Overview
The remaining sections of this document provide a general description,
including characteristics of the users of this project, the product's hardware,
and the functional and data requirements of the product: Section 2 gives an
overall description of the software. It gives what level of proficiency is
expected of the user, some general constraints while making the software
and some assumptions and dependencies that are assumed. Section 3
gives specific requirements which the software is expected to deliver.
Functional requirements are given by various use cases. Some
performance requirements and design constraints are also given.
2. Overall description
This section will give an overview of our system, Unicode converter web
application. It Unicode Converter helps you convert between Unicode character
numbers, characters, UTF-8 and UTF-16 code units in hex, percent escapes, and
Numeric Character References. All the major operating systems, browsers, editors,
word processors and applications and tools are supporting Unicode so it is
necessary to use Indian languages and scripts in the Unicode environment, which
will resolve the compatibility issue.
2.1 Product perspective
Unicode Converter Web Application contain Online Unicode tools which is a
collection of useful browser-based utilities for manipulating Unicode text. All
Unicode tools are simple, free and easy to use. In text processing, Unicode takes
the role of providing a unique code point—a number, not a glyph—for each
character. In other words, Unicode represents a character in an abstract way and
leaves the visual rendering (size, shape, font, or style) to other software, such as a
web browser or word processor.
If your text contains bare numbers that you also want to convert, use the select
control to the right. (Be aware, however, that in this case something like 'ab' could
be interpreted as a hex number.)
Note, also, that the escapes \n, \t, \b, and \" etc, are recognised by default. If you
check the box next to Convert \n etc they will be ignored. For full CSS behaviour
here, use the CSS input field.
It currently doesn't recognise escapes such as \n, \t, etc. Nor does it recognise
character entities, such as á.
If you have selected Hex code points or Dec code points in the adjacent select
control, it will also leave behind hex or decimal numbers. It only detects numbers
if they are preceded and followed by a space, a particular set of punctuation marks,
or the start/end of the text. It treats UTF-8 and UTF-16 code units as hex code
point numbers.
Special use: If you only want to convert a specific type of escape and leave all
others untouched, paste the text into one of the other (grey) boxes and hit its
associated Convert button.
Checkboxes: Several of the output fields have checkboxes that allow you to
slightly alter the results of a conversion. If an output field already contains a result
when you click on a checkbox, you'll often see a change happen as you click. In a
couple of cases, however, this doesn't happen, since it is not possible to produce
good results.
Invoking via URL: You can also pass a string to the page using the q parameter in
the URI. For example, http://r12a.github.io/app-conversion/?q=Crêpes. You can
also pass a string with escapes in it. You will need to be careful to percent-escape
characters such as &, + and # which affect the URI syntax.
2.4 Constraints
The Internet connection is also a constraint. It is crucial that there is an
Internet connection for the website to function.
Check if you are using the correct code page. If the code page is correct,
check if the selected font supports the characters you want to display.
Check if you have entered these characters by mistake or if you really want
to save the characters in the source. In the first case, remove the faulty
characters and save the source. In the second case, save the source in UTF-8
format.
The dialog editor, which is provided with Natural for Windows, and dialog-
based runtime is not Unicode-enabled.
3. Specific requirements
This section specifies the detailed requirements which the system shall meet
3.5.1 Reliability
The system provides storage of all databases on redundant computers with automatic
switchover. The reliability of the overall program depends on the reliability of the
separate components. The main pillar of reliability of the system is the backup of the
database which is continuously maintained and updated to reflect the most recent
changes. Thus the overall stability of the system depends on the stability of
container and its underlying operating system.
3.5.2 Availability
The system should be available at all times, meaning the user can access it using a
web browser, only restricted by the down time of the server on which the system
runs. In case of a of a hardware failure or database corruption, a replacement page
will be shown. Also in case of a hardware failure or database corruption, backups of
the database should be retrieved from the server and saved by the administrator.
Then the service will be restarted. It means 24 X 7 availability.
3.5.3 Security
The application is password protected and also any updation of new product
entries and order processing is done by only privileged users.
3.5.4 Maintainability
The application is to be designed so that it is easily maintained. Also, it should
allow incorporating new requirements in any module of system.
3.5.5 Portability
The application will be easily portable on any window-based system.