New Software Project Idea.........!!!Part 1

in #software • 7 years ago

In this article I want to describe a Software for Identify Fake product.The system is called Fake Product Review System(FPRS).

Fake Product Review System(FPRS)
1.PNG

Scenario – 01: Customer Want to know about any type of products if it is real or fake product. So at first user should log in (PRS).

  1. Create account
  2. Login
  3. Update profile
  4. View product
  5. Log out
    Use Case (Manage Account)
    2.PNG

Description (Fake Product Review System(FPRS)): Manage account.
Use Case : 1
Use case name: Create Account.
Primary actor: User.
Supporting actor: System.
Stakeholder: user, system.
Pre – condition: Create account by user.
Post condition: System get information and open an account for user.
Success scenario: user create account successfully.
Alternative Scenario: user can not create account.

Use Case: 2
Use case name: log in.
Primary actor: user.
Supporting actor: System.
Stakeholder: user, system.
Pre – condition: Log in in to the system by user.
Post condition: System check information of user.
Success scenario: user log in successfully.
Alternative Scenario: user can not log in.

Use Case: 3
Use case name: Update Profile.
Primary actor: user.
Supporting actor: System.
Stakeholder: user, system.
Pre – condition: Update account by user.
Post condition: Collect update or info from user by system.
Success scenario: user update his account successfully.
Alternative Scenario: user can not update his account.

Use Case: 4
Use case name: View product.
Primary actor: user.
Supporting actor: System.
Stakeholder: user, system.
Pre – condition: user can view the product.
Post condition: System give info of product to the user.
Success scenario: user view the product successfully.
Alternative Scenario: user can not view the product.

Use Case: 5
Use case name: log out.
Primary actor: User.
Supporting actor: System.
Stakeholder: user, system.
Pre – condition: User want to log out from the system.
Post condition: System erase the user id from the site for a certain period, until customer back or log in again.
Success scenario: User log out successfully.
Alternative Scenario: User can not log out.

System Sequence diagram:
Manage Account
3.PNG

Scenario 2:
Use case – Check Product Details
Suppose a customer wants to check products details .

• Log in.
• Select category.
• Show category.
• Select product.
• show details.

Use Case Diagram:
Use case – Check product details
Description:
Use case – Check product details
Use case name – check product details
Scope: System.
Level: Select category
Primary actor : customer
Supporting actor : System.
Stakeholder: Customer, shop owner, shop assistant.
Interest: Customer wants know about product details.
Pre-condition: Customer wants to select a category.
Post condition: The system show category.
Success scenario:

  1. Customer select a category.
  2. The system show category.
    Alternate scenario:
  3. Customer can not select category .
  4. The system cannot show product category .

Use case – Check product details
Use case name – check product details
Scope: System.
Level: show category
Primary actor : customer
Supporting actor : System.
Stakeholder: Customer, shop owner, shop assistant.
Interest: Customer wants know about product details.
Pre-condition: Customer wants to show the category .
Post condition: The system show the category successfully.
Success scenario:

  1. Customer select a category.
  2. The system show category.

Alternate scenario:

  1. Customer can not select category .
  2. The system cannot show product category.

Use case – Check product details
Use case name – check product details
Scope: System.
Level: select product
Primary actor : customer
Supporting actor : System.
Stakeholder: Customer, shop owner, shop assistant.
Interest: Customer wants know about product details.
Pre-condition: Customer should know about the product.
Post condition: Customer should know about product details successfully.
Success scenario:

  1. Customer select a product .
  2. The system show product details.

Alternate scenario:

  1. The system cannot show product category.
  2. Customer cannot select a product.

Use case – Check product details
Use case name – check product details
Scope: System.
Level: show product
Primary actor : customer
Supporting actor : System.
Stakeholder: Customer, shop owner, shop assistant.
Interest: Customer wants know about product details.
Pre-condition: Customer should know about the product.
Post condition: Customer should know about product details successfully.
Success scenario:

  1. Customer select a product .
  2. The system show product details.
  3. Customer see the product details successfully.

Alternate scenario:

  1. The system cannot show product category.
  2. Customer cannot select a product.
  3. The system shows wrong product details.

System Sequence diagram:
Use case – Check product details
5.PNG

Scenario 3:
Use case - Post Comment
When customers will know a fake product or real product they will put the comment in the comment box. Customer will use the serial number to know the product details. User will maintain the steps to post comment.
• Log in.
• Search product.
• Write comment on comment box.
• Submit comment.
• Log out.

Use Case Diagram:
Use case – Post Comment
6.PNG

Description:
Use case – Post Comment
Use case name: log in.
Scope: System.
Level: Enter Username,Password for log in.
Primary actor: User/Customer.
Supporting actor: System.
Stakeholder: User, shop owner, shop assistant.
Interest: User wants to log in his own account to post comment.
Pre – condition: Log in in to the system by User.
Post condition:
• System check information of customer.
Success scenario: Customer log in successfully.
Alternative Scenario: Customer cannot log in.

Use case name: Search product.
Scope: System.
Level: Enter product name and serial number.
Primary actor: User/Customer.
Supporting actor: System.
Stakeholder: User, shop owner, shop assistant.
Interest: User wants to search product.
Pre – condition: Input serial key of the product.
Post condition:
• View details about the product.
Success scenario: Customer or user found product successfully.
Alternative Scenario: Customer or user did not find product successfully.

Use case name – Post Comment
Scope: System.
Level: Write Comment.
Primary actor : User/Customer
Supporting actor: System.
Stakeholder: User, shop owner, shop assistant.
Interest: User wants know about product and to post comment.
Pre-condition: User should know about the product.
Post condition: User should write comment and press submit button.
Success scenario:
• User writes comment.
• User presses submit button.
Alternate scenario:
• User doesn’t know how to post comment.
• User can’t find submit button.

Use case name: log out.
Scope: System.
Level: Press log out button for logging out.
Primary actor: User/Customer
Supporting actor: System.
Stakeholder: User, shop owner, shop assistant.
Interest: User wants to log out his own account to post comment.
Pre – condition: Log in to the system by User.
Post condition:
• System check information of customer.
Success scenario: Customer log out successfully.
Alternative Scenario: Customer cannot log out.

System Sequence diagram:
7.PNG

Scenario 4: Suppose a customer wants to buy a product and he/ she went check this product datils and he/she also wants to know this product. Customer can complain for any product to the authority.

  1. Customer login into the web portal.
  2. Customer search the product.
  3. Customer write complain and submit complain in complain bar.
  4. All process complete then customer logout into the web portal.

Use case: Customer Complain
8.PNG

Use case Description: Customer Complain

Use case name: Log In
Scope: System
Primary Actor: Customer
Stakeholders: Customer: to provide login information.
Pre-Condition: Log in in to the system by Customer.
Post-Condition :System check information of customer.
Success Scenario: 1. Customer log in successfully.
Alternative Scenario: 1. Customer cannot log in.

Use case name: Search Product
Scope: System
Primary Actor: Customer
Stakeholders: Admin: to record product information.
Pre-Condition:Customer search a product.
Post-Condition:Customer successfully search a product.
Success Scenario:
1.Customer search this product.
2.System prefer some product items.
Alternative Scenario:
1.Customer can’t find out searching product.
2.System not working properly.

Use case name :Submit Complain
Scope: System
Primary Actor: Customer
Stakeholders: Customer: to provide complain.
Pre-Condition: Customer submit her complain.
Post-Condition:Customer successfully submit her complain.
Success Scenario:
1.Customer submit her all complain.
2.System successfully recorded complain.
Alternative Scenario:
1.Customer submit complain bar not working.
2.System not record complain and not working properly.

Use case name :Log Out
Scope: System
Primary Actor : Customer
Stakeholders:Customer want to logout web portal.
Pre-Condition: Log out in to the system by Customer.
Post-Condition: System check information of customer.
Success Scenario: Customer log out successfully.
Alternative Scenario: Customer cannot log out.

System Sequence diagram: Use case – Customer Com plain
9.PNG

Scenario 5:
Use case – Apply For Complain
A customer buy a product or become a buyer for any product,He/She buy a product and then finding a problem then he/she complain for that product.Another one is somehow choose a product and find a problem brfore buying. He/She also complaint for those situation

• At first Log into the website.
• Search product which one he/she buy.
• What kinds of problem and write in complain box.
• Submit
• Log out.

Use Case Diagram:
Use case – Check product details
1.PNG

Description:
Use case – Apply For Complains
Use case name –apply for complain
Scope: System.
Primary actor : customer
Supporting actor: System.
Stakeholder: Customer, shop owner, shop assistant.
Interest: Customer wants know complain any kinds of product.
Pre-condition: Customer log into the site and find the product.
Post condition:Customer Write the Complain and submit.
Success scenario:

  1. Customer login the system.
  2. Customer finds the product.
  3. Customer Write the complain in complain box.
  4. Submit .
    Alternate scenario:
  5. Customer can not login the system.
  6. Customer can not find the Complain box.
  7. The system cannot show Complain box
  8. Customer cannot submit.

System Sequence diagram:
Use case – Apply for Complain
2.PNG

#idea #system
7 years ago in #software by
$0.00
    4 votes
    Reply 0