Anatomic Therapy 2bf55

FUNCTIONAL REQUIREMENT DOCUMENT

Version: version number Prepared by:R.B.Pradeep

TABLE OF CONTENTS

1. Introduction ................................................................................................................................................. 1 1.1

Purpose....................................................................................................................................................... 1

1.2

Intended Audience .................................................................................................................................... 2

1.3

Project Scope ............................................................................................................................................. 2

1.4

Design and Implementation Constraints ............................................................................................... 2

1.5Assumptions…………………………………………………………………………………………1 2. System Features ......................................................................................................................................... 2 2.1

System Features ....................................................................................................................................... 2

3. External Interface Requirements ............................................................................................................. 4 3.1

Interfaces .......................................................................................................................................... 4

3.2

Hardware Interfaces .................................................................................................................................. 4

3.3

Software Interfaces ................................................................................................................................... 4

3.4

Communications Interfaces ..................................................................................................................... 5

4. Other Nonfunctional Requirements ........................................................................................................ 5 5. References ................................................................................................................................................... 6

1. INTRODUCTION 1.1 PURPOSE

Anatomic Therapy

1

This documents functional approach to external Interface to the system the intent of the group is to have external Dependencies and to Provides brief overview of the System commenting such as Real time use, Security consideration, Concurrency of s etc. 1.2 INTENDED AUDIENCE

This Document will be a ready for the development, SIT, UAT, and can be shared with the end s and for any management teams to have the hawk eye view of the requirement . 1.3 PROJECT SCOPE

This group who are in the market for more than a decade who are specialized Anatomic therapy foundations a non-religious and non-profitable trust, does service to the public on various aspects like Physical health, Mental health, Law of attraction, Law of nature, soul consciousness, Education, Nature food, etc. Design and Implementation Constraints 1.4 ASSUMPTIONS

Reference Architecture would take an n-Tier,Client-Server Model as its model as its basis and stste that the Persistence layer would be implemented through a number of Standard API calls to a Particular database System. whose outcomes influence the success of a project.

2. SYSTEM FEATURES

This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product. 2.1 SYSTEM FEATURES

Prior to proceeding with the functional requirements, the below signoff’s needs to be approved in order to proceed with the proposed change. 1. Business approval – Approval to be sought for the head of business team in mail. 2. Change Manager – Change manager review the document and provide his signoff. Include the desired system features in the table below. Record the related functional requirements associated with the functional requirements with assigned priorities Anatomic Therapy

2

Title of System Feature

Description

Priority

Functional Requirements

Reset Services

Reset Services

High

“Reset Services”

General No Changes Required

App

App General No Changes Required

Need to maintain the configurable Servicing Content, Audio and Video( Serviced only For Android and Web)

High

        

Front End Website

Android App

Android App

General No Changes Required

“ App”

High



can Post Image Video ( YouTube and MP4) Audio Image PDF Live Stream YouTube New Updates send Notifications to App Update Front Scrolling Image

      

Front Scrolling Image Categories Video ( YouTube ) Audio Image Events With Image Static Pages

“Android App”

       

Anatomic Therapy

Front Scrolling Image Image Video ( YouTube and MP4 ) – ing Option Audio – ing Option Image – ing Option Live Stream YouTube Static Pages Events 3



Notifications to App

3. EXTERNAL INTERFACE REQUIREMENTS 3.1 INTERFACES

Describe the logical characteristics of each interface between the software product and the s. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a interface is needed. Details of the interface design should be documented in a separate interface specification. 3.2 HARDWARE INTERFACES

Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the ed device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.

3.3 SOFTWARE INTERFACES

1. Reset Services 

Google App Engine



Cloud Storage Blob Storage



Firebase Notification

-- Java 7

2. App 

Google App Engine

Anatomic Therapy

-- Java 7 4



Cloud Storage Blob Storage



Firebase Notification

3 .Front End Website 

Google App Engine –Java 7



HTML 5 CSS and BootStrap 4

4.Android App 

Android SDK



Firebase Notification SDK



Java 8



Youtube SDK

5.IOS APP 

X Code 9



Swift 4



Firebase Notofication SDK 

Youtube SDK

3.4 COMMUNICATIONS INTERFACES

To be filled. 4. OTHER NONFUNCTIONAL REQUIREMENTS # 1

2

Type of Requirement

Details

Performance Requirements

Need to be Discussed

Technical Definitions

Specific attention will also have to be placed in the Choice of language for the Implementation of the system  Google App Engine –Java 8  Google Cloud Storage – JDO –2

Anatomic Therapy

5

3 4 5

Security Requirements Training Requirements

 Android App Store –Java 7  Firebase  Bootstrap 4 and HTML 5  IOS –Swift 4 TBU post discussion with infrastructure teams Android 6.0 and Above Versions Workshop to be conducted to both the business teams to help them understand the change.

5. References

These may include interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location

Anatomic Therapy

6