Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sanjaysah101/yatra-android-app
https://github.com/sanjaysah101/yatra-android-app
Last synced: 19 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/sanjaysah101/yatra-android-app
- Owner: sanjaysah101
- Created: 2022-09-03T18:21:58.000Z (about 2 years ago)
- Default Branch: master
- Last Pushed: 2022-11-09T17:47:05.000Z (about 2 years ago)
- Last Synced: 2024-01-01T10:23:56.535Z (11 months ago)
- Language: Java
- Size: 29.8 MB
- Stars: 11
- Watchers: 1
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Yatra Android App
## Group No: 47
### Project Title: Krishi Yatra
Members Name
Enrollment No.
Bibek Kumar Sah
20SOECE11097
Sanjay Kumar Sah
20SOECE11111
Shikat Eftakhar Mahumud
20SOECE11088
Dheeraj Prajapati
20SOECE11113
# Introduction
## Purpose
SCM provides centralized control for the planning, design, manufacturing, inventory, and distribution phases required to produce and sell a company's products.
This project is developed to facilitate supply chain management to automate its operations of keeping records and storing them further facilitating easy access. The software is capable enough to allow the concerned person to store and retrieve any type of record with just a single click of the mouse. The software allows an Interactive, Self-describing User Interface environment where even standalone users can work very comfortably and efficiently. Data redundancy will be removed and will require a one-time investment only.
A goal of supply chain management is to improve efficiency by coordinating the efforts of the various entities in the supply chain. This can result in a company achieving a competitive advantage over its rivals and enhancing the quality of the products it produces, both of which can lead to increased sales and revenue.
## Document Conventions
Times New Roman font has been used with a font size of 12 as the standard or typographical convention while typing this SRS.
## Intended Audience and Reading Suggestions
This document is intended for the developers, project managers, users, testers, and documentation writers. This document contains the purpose, scope, perspective, functions, operating environment, various constraints and interfaces, system features and requirements, diagrams, and other rules.
## Product Scope
This document represents specification of the SCM system requirements. It serves as the baseline document on which the subsequent software development life cycle phases are built.
# Android App View
# Admin View
## Definitions, Acronyms and Abbreviations
Term Description
SYSTEM Supply Chain Management Software.
RKU RK University
SCM Supply Chain Management
STD State Transition Diagram
SRS Software Requirements Specification
ERP Enterprise Resource Planning
## Overview
This SRS document is organized as flows:
Overall description of SCM includes product perspective, product functions, SCM’s user characteristics, constraints, assumptions & dependencies, and apportioning of requirements.
Specific Requirements include interface requirements, functional requirements, performance requirements, logical database requirements, design constraints, and software system attributes.
Change management process.
# Overall Description
## Product Perspective
The perspective of product conduct in delivering Yatra company products like vegetables, IT products, Business Consultation, and other IT services in a fast way and less cost than another alternative way. There are other well-known SCM systems from Oracle and SAP, they are used in big companies and connect with other systems but with the same main functionality that is provided by our SCM. Our system scope is limited by Yatra and their requests.
## Product Functions
### Yatra SCM will:
- Provide a simple Customer service management process
- Determine mutually satisfying goals between the organization and customers
- Establish and maintain customer rapport
- Produce positive feelings in the organization and the customers
- Maintain Procurement process
- Manage Product development and commercialization
- Coordinate with customer relationship management to identify customer-articulated needs
- Select materials and suppliers in conjunction with procurement
- Develop production technology in manufacturing flow to manufacture and integrate into the best supply chain flow for the product/market combination.
- Maintain Manufacturing flow management process
- Manage Physical distribution
- Maintain Outsourcing and Partnerships
- Maintain Measurement Performance
- Maintain Cost Performance
- Maintain Customer Service Performance
- Maintain Productivity measures Performance
- Maintain Asset measurement Performance
- Maintain Quality Performance
### Functionalities Provided by Yatra:
- Logistic Management
- Transportation Details
- Material Management
- Warehousing
- Cold Storage Details
- Contracting Details
- Inventory Management for Retailers
- Role-Based Access for Retailers, Farmers, Dealers
- Data Backup
- Notification System
- Payment Reminder
# User Classes and Characteristics
The users are Yatra’s employees, customers, Companies, and suppliers.
## Operating Environment
- The device must be of Android Operating System.
- Android Smart Phones and Tablets with minimum version 5.1 and above
## Design and Implementation Constraints
The system has many constraints. For example, the system must be android, and all tools must be compliant with android technologies, i.e., We must use Android and java as a programming language and Firebase, and SQL Lite as DBMS. We are also constrained by Yatra's framework and the system will later be integrated with the other two modules in the framework. Yatra has some programming standards that we must commit to.
## User Documentation
Any user of the software system is the target audience for user documentation generated about the software system. A range of short document types (e.g., guidelines, tutorials, frequently asked questions) in Hypertext Markup Language (HTML) and/or Portable Document Format (PDF) format must describe the use of the software system.
## Assumptions & Dependencies
We assume that the server machine of the system has a suitable Android OS. The system must have a connection to the internet and device must be of Android Operating System.
# External Interface Requirements
## User Interfaces
The system is an Android App based system so, it will interact with its users with a device components interface. The users move through pages containing activities or directions to some other activities.
The system interface will look like following:
## Hardware Interfaces
- The system has no hardware interface requirements till -et.
- For billing it will require somehow hardware interfaces -or bill scanning and all, but right now we haven’t used any -ardware interfaces.
- Mobile’s Camera
## Software Interfaces
Name
Menomonics
Version
Source
Fire Base
FB
30.4.1
https://firebase.google.com/support/release-notes/android#latest_sdk_versions
Android Studio
AS
2.1.16
https://developer.android.com/studio
SQL Lite
SQL Lite
3.39.3
https://www.sqlite.org/download.html
Java
Java
8.0
https://www.java.com/en/download/help/version_manual.html
### Communications Interfaces
The SCM system will use TCP/IP as the main communication protocol through the internet/network.
Also, it might communicate with external systems in the future, such as customer relationship management systems and HR systems. The scope of our system does not require us to interact with other interfaces, but it can be customized.
### System Features
This section of the SRS describes the requirements for the system’s features. Specifically, requirements for component functionality, data curation, and software system administration are defined.
### Volatile Data Stream
The VDS component of the software system must comply with all enumerated requirements for an application to execute an MTConnect Agent (Data Exchange Between Shop Floor equipment and a software application used for monitoring and data analysis) in the standard.
### Query-able Data Repository
The QDR component of the software system must retrieve data from an indexed database based on a user-defined query request via an app user interface, an endpoint query, and/or an API call.
- The QDR must provide the administrator with the ability to predefine queries for use by non-administrator users.
- The QDR must enable the administrator to limit query results by date ranges and/or several records.
- When configured in a query by the administrator, the QDR must provide the user with a list of all available devices in the database and all available associated data elements for that device.
- The user may be provided the ability to select what data elements to retrieve via the predefined query.
- The user must have the ability to select the time range and/or several records for the data to retrieve via the query.
- The user must have the ability to retrieve and view data as formatted ASCII, CSV, JSON, Pdf, or XML.
### Data Curation
This subsection of the SRS describes the requirements for data curation within the software system.
- The software system must provide a function to store and manage data in a database according to a data-structure template (e.g., schema, ontology).
# Other Non-functional Requirements
## Performance Requirements
The system must handle concurrent users and their operations. The system must accomplish of transactions. This is due to the nature of data, which is only text information that does not usually exceed 50 KB per transaction.
## Safety Requirements
There are no requirements for Mean Time between Failures (MTBF) or Mean Time to Failures (MTTF) for this version of the software system defined in this SRS. However, in accordance with industry recommended practices, the software system should undergo feature testing, load testing, and regression testing are prior to releasing and/or deployment.
## Availability Requirements
Reasonable efforts should be made to ensure the software system is available with an uptime of 95%. The uptime is calculated as the percentage of time during the year in which the software system was available to the public. A 95% uptime percentage allows for an average of 18.25 days per year, 36 hours per month, or 8.4 hours per week of downtime.
## Security Requirements
The software system defined in this SRS must follow industry-recommended practices for secure software development. At a minimum, the software development must practice the principle of least privilege for defining access-level requirements of the software system and its associated services. The production-release version of the software system must pass an automated dynamic application security testing tool.
The system has only three roles for coordinators (Admin), suppliers, and customers only that make our system secure access online and these authentications will prevent and illegal access.
## Maintainability Requirements
The architecture, design, implementation, and documentation of the application must minimize the maintenance costs of the software system. The maximum person-time required to fix a security defect (including regression testing and documentation update) must not exceed two person days. Otherwise, the software system must be taken offline or the offending feature disabled. The average person-time required to make a minor enhancement (including testing and documentation update) must not exceed one person per week.
The system is designed in modules where errors can be detected and fixed easily. This makes it easier to install updates and new functionality if required.
## Portability
The system can operate in any of the latest Android operating systems with the latest version. Due to the nature of the system, the host machine must also have Android installed.
## Business Model
The system must have at least a Super-User role and a user role defined for accessing and interacting with the system. Additional roles may be defined for the system if the business rules for the administrator and user roles are satisfied. At a minimum, the Super-User role must account for the data explorer, data curator, and administrator account type requirements described in Section.
At a minimum, the User role must account for the data explorer account-type requirements described in Section.
The following business rules must apply to the administrator and user roles.
### Super-User Role Business Rules
- Superuser Role/001 Maintains all VDS and QDR back-end system configurations
- Superuser Role/002 Maintains all VDS and QDR schemas and templates
- Maintains all user groups and user accounts
- Maintains all QDR predefined queries
### User Role Business Rules
- Connects to and retrieves and reads data from VDS and QDR in conformance with the maintained VDS and QDR schemas and templates.
### Other Requirements
- Up to now there is not any legal requirements from government.
Appendix: