0% found this document useful (0 votes)
11 views

Module1-Assignment1-IEEE_Unicode

The document outlines the Software Requirements Specifications for a Unicode Converter Application, detailing its purpose, scope, and specific functionalities. It emphasizes the need for a universal code page to support various languages and scripts, particularly in the context of globalization. The document also includes sections on user characteristics, performance requirements, and software system attributes to ensure reliability, availability, security, maintainability, and portability of the application.

Uploaded by

simnaashraf7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views

Module1-Assignment1-IEEE_Unicode

The document outlines the Software Requirements Specifications for a Unicode Converter Application, detailing its purpose, scope, and specific functionalities. It emphasizes the need for a universal code page to support various languages and scripts, particularly in the context of globalization. The document also includes sections on user characteristics, performance requirements, and software system attributes to ensure reliability, availability, security, maintainability, and portability of the application.

Uploaded by

simnaashraf7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Software Requirements Specifications

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

Name Date Reason for change Version


Simna Ashraf 13-08-22 Initial Version V.01
1. Introduction
1.1 Purpose
The purpose of this document is to give a detailed description of the requirements
for the Unicode Converter Application. It will illustrate the purpose and complete
declaration for the development of the system. It will also explain system
constraints, interface and interactions with other external applications. This
document is primarily intended to assist users for converting Text to Unicode and
decimal and vice versa while you type.

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.

Unicode is superset of existing character sets. This is an international encoding


standard for use with different languages and scripts, by which each letter, digit, or
symbol is assigned a unique numeric value that applies across different platforms
and programs. Unicode® 14.0 Versioned Charts Index are also available

1.3 Definitions, acronyms, and abbreviations


 UTF-8: It is a variable-width character encoding used for electronic
communication.
 UTF-16: 16- bit Unicode Transformation Format is a standard method of
encoding Unicode character data.
 Unicode: an international encoding standard for use with different
languages and scripts, by which each letter, digit, or symbol is assigned a
unique numeric value that applies across different platforms and
programs.
 Hex: Hexadecimal is a numbering system with base 16.
 URI: Uniform Resource Identifier, which is a character sequence that
helps identify a logical or physical resource connected to the internet.

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.

2.1.1 System interfaces


A Web user interface or Web app allows the user to interact with content or
software running on a remote server through a Web browser. The content or Web
page is downloaded from the Web server and the user can interact with this content
in a Web browser, which acts as a client.

2.1.2 User interfaces


The user interface shall be web-based, allowing users to remotely access
the system via several applications. Users will be able to use the software
through applications such as Microsoft Internet Explorer, Mozilla, etc. Each
part of the user interface intends to be as user friendly as possible. The fonts
and buttons used will be intended to be very fast and easy to load on web
pages. The pages will be kept light in space so that it won’t take a long time
for the page to load.

2.1.3 Hardware interfaces


Since the application must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system.
As for eg: Modem, WAN – LAN, Ethernet Cross-Cable.
2.1.4 Software interfaces
During our system development, we have to design both static and dynamic
website interfaces, create website functions and a database system, edit photos
and pictures, and print out reports, so it has a set of software requirements.
The following are needed requirements.
Web browser - Microsoft Internet
PHP, Java
XAMPP application
MySQL Database server

2.2 Product functionality


Unicode, formally The Unicode Standard is an information technology standard for
the consistent encoding, representation, and handling of text expressed in most of
the world's writing systems.

 It is a global standard for encoding.


 It has support for the mixed-script computer environment.
 The encoding has space efficiency and hence, saves memory.
 A common scheme for web development.
 Increases the data interoperability of code on cross platforms.
 Saves time and development cost of applications.

2.3 User characteristics


A code point is an integer value that uniquely identifies the given character.
Unicode characters can be encoded using different encodings, like UTF-8 or UTF-
16. These encodings specify how each character's Unicode code point is encoded,
as one or more bytes. Each encoding will represent the characters as bytes
according to their own scheme.
Most of the time you will probably want to drop the text to be converted into the
field with the green background and hit the associated Convert button. This will
convert all escapes to characters, then convert those into each of the forms listed
against the boxes below.

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.

The Extract button strips away everything but the escapes.

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.

2.5 Assumptions and dependencies


Unicode's development is motivated by the need to encode characters in all
languages without conflicts between the encodings for different languages.
Obviously, the achievement of this goal is fraught with technical and political
complexities. Unicode has several different encodings. In the case that the project
is delayed, there are some requirements that could be transferred to the next
version.

3. Specific requirements
This section specifies the detailed requirements which the system shall meet

3.1 External interfaces


This section provides a detailed description of all inputs into and outputs from the
system. All user interfacing is done through a web UI.
Unicode converter to code points is a utility which converts your Unicode input
data to code point values. Each Unicode character is associated with a non-
negative integer called a code point.
A single number is assigned to each code element defined by the Unicode
Standard. Each of these numbers is called a “code point” and, when referred to in
text, is listed in hexadecimal form following the prefix "U". For example, the code
point "U+0041" is the hexadecimal number "0041" (equal to the decimal number
"65"). It represents the character "A" in the Unicode Standard which
is named “LATIN CAPITAL LETTER A”.

3.2 Functional requirements


Implementation is the stages of project when the theoretical design is turned into a
working system. If the implementation stage is not properly planned and
controlled, it can cause chaos. Thus, it can be consider to be most crucial stage in
achieving successful new system and in giving the users confidence that the new
system will work and be effective. Normally this stage involves setting up a co-
ordination committee, which will act as a sounding board of ideas, complaints and
problems. The first task is implementation planning i.e., of the methods and time
scale to be adopted. Apart from planning, the two major task of repairing for
implementation are education and training of administrator and testing of the
system. After the implementation phase is completed and the user staff adjusted to
the changes created by the candidate system, evaluation and maintenance is
continue to bring the new system standards. The activities of the implementation
phase can be summarized as;
 Implementation planning
 Education and training
 system training

3.3 Performance requirements


Maximum possible quick response to the conversions is required, also should
provide fast updation of records. The changes if any made should be
reflected automatically in the next screens.

3.4 Design constraints


The design constraints are that the browser at each place may not follow similar
screen resolutions, browsers etc. This can lead to the website not having the
impact it is planned to have.

3.5 Software system attributes


The necessary qualities of software products are

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.

You might also like