The document describes 12 use cases for an e-commerce mobile app's admin and customer accounts. The use cases cover functions like login, managing products/orders/suppliers, browsing/searching products, adding products to cart, checkout, order details, and logout. The use cases specify actors, goals, pre/post conditions, and success scenarios for each account functionality to ensure secure and efficient user experiences.
The document discusses common issues with broken authentication and authorization in web applications.
It provides several case studies of authentication bypass vulnerabilities, including misusing authentication tokens, cookie manipulation, failing to invalidate sessions after password resets, and account takeover through password reset functionality.
It also examines cases of broken authorization and privilege escalation, such as updating boolean or role-based privileges, bypassing client-side checks, directly accessing privileged pages, allowing low-privileged users to perform privileged actions, and deleting resources through IDOR.
Remediation strategies are proposed, such as strengthening authentication tokens and sessions, implementing server-side access controls, and preventing debugging information leaks.
- The document discusses common issues with broken authentication and authorization in web applications, providing several case studies as examples. It covers topics like authentication bypass through misuse of auth tokens, cookie manipulation, and session invalidation. It also discusses authorization bypass through privilege escalation via role changes and direct access to privileged pages. The document concludes with recommendations on how to properly implement authentication, authorization, and access controls to prevent such issues.
This document contains the milestone five report for the customer contact database system development project. It includes planning documents like the system request and proposed solution. It also includes analysis documents like functional and non-functional requirements, use cases, and UML diagrams. The design section includes CRC cards, sequence diagrams, a class diagram, and class relationships table.
Opening Our Platform to Developers: PayPal's New Application Model and Develo...PayPalX Developer Network
Some of PayPal's new integration methods allow access previously unavailable in PayPal or any other development platform. In this session, we'll discuss how you get access to these methods. We’ll also walk through our brand-new developer portal built just for you. Don’t miss out on this chance to explore the new x.com portal.
MCA Final Year Internship Project Presentation
Project Name : ToolTrade.com
Project Description:
This is country-specific website build especially for Australia.
As the name suggest, it deals in variety of tools, machinery and consumables and provide different privileges for different kinds of members.
Technology Stack:ASP.NET using C#,HTML,CSS
This document provides an agenda and details for an e-marketplace project presentation. The summary includes:
1. The project presentation covers the company profile, introduction, proposed system, scope, hardware/software requirements, UML diagrams, database design, user screens/forms, future enhancements, and conclusion.
2. The proposed e-marketplace system would allow vendors to set up online shops and customers to browse, purchase, and receive products online without visiting physical shops.
3. Key system modules include administration, shop owners, employees, and customers to manage the online marketplace.
The document describes a car showroom management system project submitted by Muhammad Shoaib, Hamza Chaudhry, and Sheryar Abbasi. The project aims to develop a software application to help manage customers, sales, company inventory, and vehicle details for a luxury car dealership. Key features include online and manual booking of vehicles, searching vehicle information, updating or canceling orders, and admin functions like user registration, vehicle registration, and booking operations. Testing will use black-box testing methods like equivalence partitioning.
The document discusses common issues with broken authentication and authorization in web applications.
It provides several case studies of authentication bypass vulnerabilities, including misusing authentication tokens, cookie manipulation, failing to invalidate sessions after password resets, and account takeover through password reset functionality.
It also examines cases of broken authorization and privilege escalation, such as updating boolean or role-based privileges, bypassing client-side checks, directly accessing privileged pages, allowing low-privileged users to perform privileged actions, and deleting resources through IDOR.
Remediation strategies are proposed, such as strengthening authentication tokens and sessions, implementing server-side access controls, and preventing debugging information leaks.
- The document discusses common issues with broken authentication and authorization in web applications, providing several case studies as examples. It covers topics like authentication bypass through misuse of auth tokens, cookie manipulation, and session invalidation. It also discusses authorization bypass through privilege escalation via role changes and direct access to privileged pages. The document concludes with recommendations on how to properly implement authentication, authorization, and access controls to prevent such issues.
This document contains the milestone five report for the customer contact database system development project. It includes planning documents like the system request and proposed solution. It also includes analysis documents like functional and non-functional requirements, use cases, and UML diagrams. The design section includes CRC cards, sequence diagrams, a class diagram, and class relationships table.
Opening Our Platform to Developers: PayPal's New Application Model and Develo...PayPalX Developer Network
Some of PayPal's new integration methods allow access previously unavailable in PayPal or any other development platform. In this session, we'll discuss how you get access to these methods. We’ll also walk through our brand-new developer portal built just for you. Don’t miss out on this chance to explore the new x.com portal.
MCA Final Year Internship Project Presentation
Project Name : ToolTrade.com
Project Description:
This is country-specific website build especially for Australia.
As the name suggest, it deals in variety of tools, machinery and consumables and provide different privileges for different kinds of members.
Technology Stack:ASP.NET using C#,HTML,CSS
This document provides an agenda and details for an e-marketplace project presentation. The summary includes:
1. The project presentation covers the company profile, introduction, proposed system, scope, hardware/software requirements, UML diagrams, database design, user screens/forms, future enhancements, and conclusion.
2. The proposed e-marketplace system would allow vendors to set up online shops and customers to browse, purchase, and receive products online without visiting physical shops.
3. Key system modules include administration, shop owners, employees, and customers to manage the online marketplace.
The document describes a car showroom management system project submitted by Muhammad Shoaib, Hamza Chaudhry, and Sheryar Abbasi. The project aims to develop a software application to help manage customers, sales, company inventory, and vehicle details for a luxury car dealership. Key features include online and manual booking of vehicles, searching vehicle information, updating or canceling orders, and admin functions like user registration, vehicle registration, and booking operations. Testing will use black-box testing methods like equivalence partitioning.
Flipkart Software requirements specification SRS for an e commerce online Web store. It contains actual format and contents for a SRS Synopsis. How Flipkart manages online store.
The document provides details of a term project final report for developing an eCommerce system for StopNSave convenience stores. It includes an executive summary, revisions made, system architecture design, 8 use scenarios describing key customer and owner tasks, interface structure design, test plan, recommendations and appendices with the original proposal and deliverable. The system will allow online ordering and delivery or pickup of StopNSave's product assortment to expand the customer base and increase sales.
On-demand grocery app development has gained significant popularity in recent years, especially in the wake of the COVID-19 pandemic, where people have increasingly preferred to order groceries online for convenience and safety. Building an on-demand grocery app involves several steps, and this guide will take you through the entire process. Let's break it down step by step:
The document provides details about a student project to develop an online university admission application. It includes the student's name and ID, their university and department, as well as information about the project overview, problems it aims to address, objectives, use case diagram, activity diagrams, entity relationship diagram, test cases, software requirements specification, project schedule, and interface details. The application will allow students to apply for admission to multiple public universities online, track admission test schedules, and communicate with teachers.
This Document Contains All DFDs, Uml Diagrams, Test Cases, Functional Requirements, Non-Functional requirements, Database Design and User Interface Diagrams. Hope it helps
Objectiver is a requirements engineering tool that uses structured modeling to identify project requirements and generate documentation. It includes goal, responsibility, object, and operation models to define goals, assign responsibilities, identify domain objects, and describe required behaviors. A demonstration of the tool modeling a user login process showed defining high-level security goals, assigning the user and system as responsible agents, and specifying operations like requesting and verifying login details. Resources provided a link to download a free trial of Objectiver along with installation and licensing instructions.
The document describes the Smart Food Court System (SFCS) project. The project aims to allow customers to order food digitally without going directly to food stalls. It features touchscreen kiosks and a mobile app for ordering, notifying customers when orders are ready, making payments through digital wallets, and allowing managers and vendors to manage operations and menus. The document outlines the login use case, describing the normal flow of logging in with an existing account or registering a new account, as well as alternative flows for incorrect login details.
This document outlines a project to develop a smart vision Android app using image recognition. The app allows users to take a photo of a product and receive information about it, including the option to buy the product. It will use Eclipse as the front-end tool and Java, JSON, and SQLite for the back-end. Requirements, feasibility, design diagrams, and screenshots are provided. The goal is to create a high quality app that gives users a futuristic way to shop using their device's camera.
This document provides a software requirements specification for the E-Smart Shopping mobile application and backend server. It describes the purpose, scope, user classes and requirements of the system. The key features include a budget tracker, product navigation, product recommendations, barcode scanning, halal product identification, and translation capabilities. The interfaces and architecture are also specified, including interactions between the mobile app and backend server via APIs and a real-time database. Non-functional requirements around performance, security and quality are also outlined.
This document outlines the business plan and progress for developing an e-commerce shopping website using Django. It describes two versions - basic and professional. The basic version allows users to order items, maintain a basket and profile, and includes online payment and admin controls. The professional version adds enhanced sales management tools. The document also discusses use cases, entity relationship diagrams, testing approach, and technologies used like Python, Django, and Subversion for version control. It provides an update on components already implemented including the model, admin panel, and user registration.
20190110 LeanKanban Meetup Story Splitting and Automated TestingCraeg Strong
Kanban Intersections with XP practices
Lean and Kanban are not ends in themselves; they are great for shining a light on bottlenecks and enabling an efficient flow of work to deliver business value. But how do we deal with those bottlenecks, anyway? How can we prevent them in the first place? How can we analyze our requirements better so we can understand the business value that we are supposed to be delivering?
This is where good XP Practices come in!
We will talk about story splitting and test automation.
With lots of examples and lessons learned to share, we hope to spark a lively discussion.
This is our minor presentation on ONLINE REAL ESTATE BUSINESS SYSTEM.
we are done in 5 days this project..If anybody interested in this project then please give a feedback of this project.
If anybody want this type of presentation in any topic then contact us on facebook or mobile we will help you to make your presentation.
my facebook id -
www.facebook.com/narayank45
contect no-8602464665
In April 2019 WebAuthn was officially released to the world as a new standard for authentication. WebAuthn enables a rich set of authentication solutions to be built, but knowing how to enable these solutions, is a major key in building a future where we no longer rely on passwords or phishable technologies. This session will dive into the journey of adopting WebAuthn, the components in the architecture of this modern authentication solution and how this new protocol touches not only every stage of an account lifecycle but creates a new phase that must be supported. This session will not only help you understand how to deploy authentication solutions internally but also how to build great solutions for your customers.
Tour guidance srs (Software Requirements Specification)Akalanaka Liyanage
The document provides a software requirement specification for a mobile framework that generates tour plans to adaptively guide tourists in Sri Lanka. It describes the functional and non-functional requirements of the framework, including use cases for admins to manage users and view feedback, and for users to login, register preferences, get trip suggestions, make payments, and provide feedback. ER and class diagrams are also included to model the business domain.
This document outlines a proposal for an Online Auction Management System project. The project will allow users to browse products in different categories, place bids on products, and enable administration of the auction process. The goals of the system are to sell and bid on products online across Pakistan. Key components will include user registration and authentication, product listing and details, an online bidding system, and an admin panel to manage the auction process. The project will use a three-tier architecture and be developed as a web-based and Android application using technologies like PHP and MySQL.
visit--- http://bit.ly/onlineshopping_javaproject For the complete project + CODE.
visit ------- javaprojects.tutoriallearners.in for other Java Projects
Nimap infotech has been in iOS and android development since a decade now and have successfully developed various applications that are running all over the world with popularity. Mobile commerce app maker for mobile sites and native iPhone, iPad and Android M-Commerce shopping cart apps.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
Flipkart Software requirements specification SRS for an e commerce online Web store. It contains actual format and contents for a SRS Synopsis. How Flipkart manages online store.
The document provides details of a term project final report for developing an eCommerce system for StopNSave convenience stores. It includes an executive summary, revisions made, system architecture design, 8 use scenarios describing key customer and owner tasks, interface structure design, test plan, recommendations and appendices with the original proposal and deliverable. The system will allow online ordering and delivery or pickup of StopNSave's product assortment to expand the customer base and increase sales.
On-demand grocery app development has gained significant popularity in recent years, especially in the wake of the COVID-19 pandemic, where people have increasingly preferred to order groceries online for convenience and safety. Building an on-demand grocery app involves several steps, and this guide will take you through the entire process. Let's break it down step by step:
The document provides details about a student project to develop an online university admission application. It includes the student's name and ID, their university and department, as well as information about the project overview, problems it aims to address, objectives, use case diagram, activity diagrams, entity relationship diagram, test cases, software requirements specification, project schedule, and interface details. The application will allow students to apply for admission to multiple public universities online, track admission test schedules, and communicate with teachers.
This Document Contains All DFDs, Uml Diagrams, Test Cases, Functional Requirements, Non-Functional requirements, Database Design and User Interface Diagrams. Hope it helps
Objectiver is a requirements engineering tool that uses structured modeling to identify project requirements and generate documentation. It includes goal, responsibility, object, and operation models to define goals, assign responsibilities, identify domain objects, and describe required behaviors. A demonstration of the tool modeling a user login process showed defining high-level security goals, assigning the user and system as responsible agents, and specifying operations like requesting and verifying login details. Resources provided a link to download a free trial of Objectiver along with installation and licensing instructions.
The document describes the Smart Food Court System (SFCS) project. The project aims to allow customers to order food digitally without going directly to food stalls. It features touchscreen kiosks and a mobile app for ordering, notifying customers when orders are ready, making payments through digital wallets, and allowing managers and vendors to manage operations and menus. The document outlines the login use case, describing the normal flow of logging in with an existing account or registering a new account, as well as alternative flows for incorrect login details.
This document outlines a project to develop a smart vision Android app using image recognition. The app allows users to take a photo of a product and receive information about it, including the option to buy the product. It will use Eclipse as the front-end tool and Java, JSON, and SQLite for the back-end. Requirements, feasibility, design diagrams, and screenshots are provided. The goal is to create a high quality app that gives users a futuristic way to shop using their device's camera.
This document provides a software requirements specification for the E-Smart Shopping mobile application and backend server. It describes the purpose, scope, user classes and requirements of the system. The key features include a budget tracker, product navigation, product recommendations, barcode scanning, halal product identification, and translation capabilities. The interfaces and architecture are also specified, including interactions between the mobile app and backend server via APIs and a real-time database. Non-functional requirements around performance, security and quality are also outlined.
This document outlines the business plan and progress for developing an e-commerce shopping website using Django. It describes two versions - basic and professional. The basic version allows users to order items, maintain a basket and profile, and includes online payment and admin controls. The professional version adds enhanced sales management tools. The document also discusses use cases, entity relationship diagrams, testing approach, and technologies used like Python, Django, and Subversion for version control. It provides an update on components already implemented including the model, admin panel, and user registration.
20190110 LeanKanban Meetup Story Splitting and Automated TestingCraeg Strong
Kanban Intersections with XP practices
Lean and Kanban are not ends in themselves; they are great for shining a light on bottlenecks and enabling an efficient flow of work to deliver business value. But how do we deal with those bottlenecks, anyway? How can we prevent them in the first place? How can we analyze our requirements better so we can understand the business value that we are supposed to be delivering?
This is where good XP Practices come in!
We will talk about story splitting and test automation.
With lots of examples and lessons learned to share, we hope to spark a lively discussion.
This is our minor presentation on ONLINE REAL ESTATE BUSINESS SYSTEM.
we are done in 5 days this project..If anybody interested in this project then please give a feedback of this project.
If anybody want this type of presentation in any topic then contact us on facebook or mobile we will help you to make your presentation.
my facebook id -
www.facebook.com/narayank45
contect no-8602464665
In April 2019 WebAuthn was officially released to the world as a new standard for authentication. WebAuthn enables a rich set of authentication solutions to be built, but knowing how to enable these solutions, is a major key in building a future where we no longer rely on passwords or phishable technologies. This session will dive into the journey of adopting WebAuthn, the components in the architecture of this modern authentication solution and how this new protocol touches not only every stage of an account lifecycle but creates a new phase that must be supported. This session will not only help you understand how to deploy authentication solutions internally but also how to build great solutions for your customers.
Tour guidance srs (Software Requirements Specification)Akalanaka Liyanage
The document provides a software requirement specification for a mobile framework that generates tour plans to adaptively guide tourists in Sri Lanka. It describes the functional and non-functional requirements of the framework, including use cases for admins to manage users and view feedback, and for users to login, register preferences, get trip suggestions, make payments, and provide feedback. ER and class diagrams are also included to model the business domain.
This document outlines a proposal for an Online Auction Management System project. The project will allow users to browse products in different categories, place bids on products, and enable administration of the auction process. The goals of the system are to sell and bid on products online across Pakistan. Key components will include user registration and authentication, product listing and details, an online bidding system, and an admin panel to manage the auction process. The project will use a three-tier architecture and be developed as a web-based and Android application using technologies like PHP and MySQL.
visit--- http://bit.ly/onlineshopping_javaproject For the complete project + CODE.
visit ------- javaprojects.tutoriallearners.in for other Java Projects
Nimap infotech has been in iOS and android development since a decade now and have successfully developed various applications that are running all over the world with popularity. Mobile commerce app maker for mobile sites and native iPhone, iPad and Android M-Commerce shopping cart apps.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
The chapter Lifelines of National Economy in Class 10 Geography focuses on the various modes of transportation and communication that play a vital role in the economic development of a country. These lifelines are crucial for the movement of goods, services, and people, thereby connecting different regions and promoting economic activities.
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
1. Fully DressedStyle
Admin Account
Use case 1:Login
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to login the account Very efficiently and fast
Pre-condition: Admin wants their login secure and Authenticated
Post-condition: Login is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Admin override entered by swiping an override login
information through password
Main Success Scenario: Admin wants to login their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 2:Registration
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to registered there self in this book shop App
Pre-condition: Admin wants to registered their self
Post-condition: Admin is registered
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Registered account can have secure and authenticated.
Main Success Scenario: Admin wants to registered their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 3:Manage Categories
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the categories that the customer want
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the categories is managed thorough
database
2. Main Success Scenario: Admin login there account all the categories must be managed
for the customer
Customer easily select the category and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 4:Manage Products
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the products that the customer want
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Admin login there account all the products must be managed
for the customer
Customer easily select the product and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 5:Manage Orders
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the orders that the customer said
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the order is managed thorough
database
Main Success Scenario: Admin login there account all the orders must be managed for
the customer
Admin easily select the order and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 6:Manage Sale
Scope: Android App
Level: User Goal
Primary Actor: Admin
3. Stake holder and interest: Admin manage all the sales
Pre-condition: Admin wants Fulfill customers sale
Post-condition: Admin fulfill customer sale
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the sale is managed thorough
database
Main Success Scenario: Admin login there account all the sale must be managed for
the customer
Admin easily select the sale and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 7:Manage Suppliers
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the suppliers that they want
Pre-condition: Admin supplies all the suppliers as they want
Post-condition: Admin fulfill the suppliers
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Suppliers is managed thorough
database
Main Success Scenario: Admin login there account all the suppliers must be managed
for the customer
Admin easily select the supplier and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 8:Settings
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the Settings
Pre-condition: Admin wants Fulfill their settings
Post-condition: Admin is fulfill their settings
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Settings is managed Through
App
Main Success Scenario: Admin login there account all the Settings must be managed
for their self
Admin easily select the setting and change it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 9: Logout
4. Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to logout there account very efficiently and fast
Pre-condition: Admin wants their logout in secure and Authenticated form
Post-condition: Logout is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Admin override entered by swiping an override logout
information through password
Main Success Scenario: Admin wants to logout their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Logout their Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
CustomerAccount
Use Case 1:Login
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to login there account very efficiently and
fast
Pre-condition: Customer wants their login secure and Authenticated
Post-condition: Login is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Customer override entered by swiping an override login
information through password
Main Success Scenario: Customer wants to login their account insufficient and
effectively manner
Customer wants authorized account. Security must be
preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 2:Browse Products
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Browse their products well mannered and
fast
Pre-condition: Customer wants to Browse their product in secure and
Authenticated
5. Post-condition: Browse product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Browse the products insufficient and
effectively manner
When customer Browse the products it used feasible options.
Browse product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 3:SearchProducts
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Search their products well mannered and
fast
Pre-condition: Customer wants to Search their product in secure and
Authenticated
Post-condition: Search product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Search the products insufficient and
effectively manner
When customer Search the products it used feasible options.
Search product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 4:SelectProducts
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Select their products well mannered and
fast
Pre-condition: Customer wants to Select their product in secure and
Authenticated
Post-condition: Select product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Select the products insufficient and
effectively manner
When customer Select the products it used feasible options.
6. Select product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 5:Add to Cart
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Add to cart their products.
Pre-condition: Customer wants to Add to Cart their product in secure and
Authenticated
Post-condition: Add to cart product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Add to cart the products insufficient and
effectively manner
When customer Add to cart the products it used feasible
options.
Product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 6:View Cart
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to View their cart .
Pre-condition: Customer wants to View their cart in secure and
Authenticated
Post-condition: Customer view cart is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the carts that customer sold is
managed through database
Main Success Scenario: Customer wants to View their cart insufficient and
effectively manner
When customer view their it used feasible options.
Customer view cart is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 7:Place Order
7. Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Place their order in well mannered and
fast
Pre-condition: Customer wants to Place their order in secure and
Authenticated
Post-condition: Place order is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Order is managed thorough
database
Main Success Scenario: Customer wants to Place their order insufficient and
effectively manner
When customer place their order it also see it
Place order is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 8:CashPay
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Cash their payment on delivery well
mannered and
fast
Pre-condition: Customer wants to Cash their payment on delivery in secure
and Authenticated
Post-condition: Cash payment on delivery is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Payment is managed thorough
database
Main Success Scenario: Customer wants to Cash their payment on delivery
insufficient and effectively manner
When customer Cash their payment on delivery it used
feasible options.
Cash their payment on delivery is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 9:Confirm Order
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Confirm their order well mannered and
fast
Pre-condition: Customer wants to Confirm their order in secure and
Authenticated
Post-condition: Confirm order is Authenticated and secure
Special Requirements: Performance Should be quick and High response
8. Attractive or user convenient interface
Technology and data variation list: When login the account all the order is managed thorough
database
Main Success Scenario: Customer wants to Confirm their order insufficient and
effectively manner
When customer Confirm their order it also see it
Confirm Order is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor
Use Case 10:Order Details
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to see order details well mannered and
fast
Pre-condition: Customer wants to see order details in secure and
Authenticated
Post-condition: Order detail is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the order detail is managed
thorough database
Main Success Scenario: Customer wants to see their order details insufficient and
effectively manner
When customer Select the products it used feasible options.
Select product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 11:Profile Setup
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer manage all the Settings
Pre-condition: Customer wants Fulfill their settings
Post-condition: Customer is fulfill their settings
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Settings is managed Through
App
Main Success Scenario: Customer login there account all the Settings must be
managed for their self
When customer Confirm their order it also see it.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
9. Use Case 12: Logout
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to logout there account very efficiently and
fast.
Pre-condition: Customer wants their logout in secure and Authenticated form.
Post-condition: Logout is Authenticated and secure.
Special Requirements: Performance Should be quick and High response.
Attractive or user convenient interface.
Technology and data variation list: Customer override entered by swiping an override logout
information through password.
Main Success Scenario: Customer wants to logout their account insufficient and
effectively manner.
Customer wants authorized account. Security must be
preferable.
Then Logout their Account.
Frequency of concurrence: Must be nearly Continuous.
Offstage Actor System
Supporting Actor User