Se Diagrams

GANTT-CHART:
0 4 8 12 16 20 24 28 32
Project Approval
Title, Intro, Functional and Non-Functional Requirements & Literature Review
Initial Coding
Midterm Evaluation
Research Methodology, Use Case & ERD
Prototyping
Budgeting
FYP # 2
Data Gathering & Cleaning
Feature Selection, Model Building & Prediction Service
Queing system, Prediction Worker & Authentication Service
Front-End Designing
Input Screen Designing, Response via Email or Real Time Processing
Testing
ERD-DIAGRAM:
UML (USE CASES AND CLASS DIAGRAM):
1. Use Case
1. SIGNUP:
USE CASE FOR SIGNUP
Use Case Name: Signup
ID: Signup
Actors Involved: Customer
Brief Description Customer click on the signup button, on the signup page
enters the details like first name, last name, email,
password,
contact, company, name.
Pre-Conditions Starting the services
Post-Conditions Authentic user created
Normal Flow of Actor Action System Response

Events:
1. Customer clicks the 1. Unique customer id is
Signup button. created in the database.
2. Enters his details. 2. The entered details are

3. Clicks on the submit stored in database.
button.
3. New customer register and
is notified about being
registered.
2. USER LOGIN
USE CASE FOR LOGIN:
Use Case Name: Login
ID: Login
Actors Involved: Customer, Admin
Brief Description Customer and admin enter the email address and password
to login.
Pre-Conditions Use Case ID: signup
Post-Conditions Authentic user logged in.

Events:
1. Enter email address 1. System displays the home

and password. page on successful login.
2. Clicks the Login 2. System displays error

button. message on invalid login.
3. UPLOAD FILE
USE CASE FOR UPLOAD FILE:
Use Case Name: Upload File
ID: upload file
Brief Description Customer is given the option to upload their data file.
Pre-Conditions Use Case ID: login
Post-Conditions Analysis sent to user through email

Events:
1. Upload file. 1. If the file is too big customer
notified that the results will be
given via email.
2. System starts processing the

request.
2. Clicks the start analysis
button.
4. REAL TIME
USE CASE FOR REAL-TIME:
Use Case Name: Real Time
ID: real-time
Brief Description When customer enters the data in the text box real time
processing of the data takes place.
Pre-Conditions Use Case ID: login
Post-Conditions Analysis shown on screen in real-time.

Events:
1. Customer enters text 1. Real time analysis is
in the text box and clicks performed.
the start analysis button.
5. API:
Use Case for API:
Use Case Name: API
ID: API
Brief Description An API request would be sent
Pre-Conditions Request sent
Post-Conditions Analysis returned

Events:
1. API request would be 1. If the request is successful, it
sent thorough API client will get a JSON object. If the
on a URL. request is unsuccessful, it will
return an error as JSON format.
6. USAGE METRIC:
USE CASE FOR USAGE METRIC:
Use Case Name: Usage Metric
ID: usage_metric
Brief Description Customer can see the statistics of the data they are
processing on the menu and admins can see information of
the customers that how much processing they have done
using which model.
Pre-Conditions
Post-Conditions

Events:
1. A usage menu will be 1. The system shows the
seen and on clicking, the statistics of all the mentioned
customer will be able to
see that how many details.
requests he has sent
using which modes and
the amount of data that
has been processed.
7. MANAGE PREDICTION MODEL
USE CASE FOR PREDICTION MODEL:
Use Case Name: Manage Prediction Model
ID: Mpm
Actors Involved: Admin
Brief Description Admin has the right to change the working model performing
analysis at the backend, customer will never know about this
transition.
Pre-Conditions Current running model
Post-Conditions Model updated

Events:
1. Admin will be able to 1. The system will pick new
change the prediction model and will load in its
model at the backend memory.
coding.
8. MANAGE CUSTOMER:
USE CASE FOR MANAGE CUSTOMER:
Use Case Name: Manage Customer
ID: manage_customer
Actors Involved: Admin
Brief Description The admin has all the rights to cancel a customer’s
registration and can also view how many custome4rs are
registered in the database.
Pre-Conditions User can log in.
Post-Conditions User is not authentic.

Events: 1. Admin selects a 1. The customer is deleted from
customer and deletes its the database.
data from the database.
2. Click’s option to view

2. The database with customer
present customer list with
information is shown.
details.
DATA/DATA-SET DETAILS:
Entity Entity Column name Data Type Length Primary Null
Name Description Key able
customer Having customer_id integer 10 true false

information of
first_name varchar 255 false false
clients.
last_name varchar 255 false false
Email varchar 255 false false
Contact integer 50 false false
company_name varchar 255 false false
created_date varchar 255 false false
password varchar 255 false false
Usage Having customer_id integer 10 false false

information of
request_id integer 1000 false false
statistics of
data request_type varchar 255 false false
instance_count varchar 255 false false
model_id integer 10 false false
Status varchar 255 false false
delivery_method varchar 255 false false
Model Contains model_id integer 10 true false

information
Score varchar 255 false false
about the
model being created_date varchar 255 false false
Accuracy varchar 255 false false
Version varchar 50 false false

implemented
in the Location varchar 255 false false
background.
Admin Contain admin_id integer 10 true false
information of
first_name varchar 255 false false
admins.
last_name varchar 255 false false
Email varchar 255 false false
Contact integer 50 false false
company_name varchar 255 false false
created_date varchar 255 false false
password varchar 255 false false
TEST CASES:
1. TEST CASE 1:
Requirement Reference 1 Project Name Sentiment Analysis
Test Case Id 1.1 Test Type GUI
Test Case Description Login window for users
Test Steps Click on login button to login the website.
Expected Result The user will login with correct credentials.
Actual Result The user login successfully.
Pass/Fail Pass
Date Prepared
Date Run
Prepared By
Tested By
2. TEST CASE 2:
Test Case Description Signup windows for users
Test Steps  Click on signup button to sign up.
Expected Result The user will sign up with correct credentials.
Actual Result The user signs up successfully.
Pass/Fail Pass
Date Prepared
Date Run
Prepared By
Tested By
3. TEST CASE 3:
Test Case Description Dashboard and user profile after logging in.
Test Steps  Click on login button to proceed to dashboard and profile.

Expected Result The user will login with correct credentials.
Actual Result The user login successfully.
Pass/Fail Pass
Date Prepared
Date Run
Prepared By
Tested By
4. TEST CASE 4:
Test Case Description Usage and stats for user after logging in.
Test Steps  Click on usage button on the dashboard to proceed to this page
Expected Result The user can view their stats for the services used.
Actual Result The page is empty.
Pass/Fail Fail
Date Prepared
Date Run
Prepared By
Tested By
5. TEST CASE 5:
Test Case Description Window for uploading data
Test Steps Click on upload data button to upload csv file for analysis
Expected Result The user receive notification that file has been uploaded.
Pass/Fail Fail
Date Prepared
Date Run
Prepared By
Tested By
6. TEST CASE 6:
Test Case Description Real-time prediction
Test Steps Click on upload data button to upload sentence for prediction for
analysis in real time.
Expected Result The user receive prediction in real time for sentence that has been uploaded.
Pass/Fail Fail
Date Prepared
Date Run
Prepared By
Tested By
7. TEST CASE 7:
Test Case Description Real-time prediction
Test Steps Click on upload data button to upload sentence for prediction for
analysis in real time.
Expected Result The user receive prediction in real time for sentence that has been uploaded.
Actual Result Shows real-time prediction.
Pass/Fail Pass
Date Prepared
Date Run
Prepared By
Tested By
8. TEST CASE 8:
Test Case Description The user receives prediction through API

Test Steps Click on upload data button to upload csv file for prediction for analysis
through email.
Expected Result The user receives prediction through confirmation email.
Actual Result Email received with analysis
Pass/Fail Pass
Date Prepared
Date Run
Prepared By
Tested By

Se Diagrams

Uploaded by

Copyright:

Available Formats

You might also like

Se Diagrams

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Se Diagrams

Uploaded by

Copyright:

Available Formats

GANTT-CHART:

Title, Intro, Functional and Non-Functional Requirements & Literature Review

Research Methodology, Use Case & ERD

Data Gathering & Cleaning

Feature Selection, Model Building & Prediction Service

Queing system, Prediction Worker & Authentication Service

Input Screen Designing, Response via Email or Real Time Processing

USE CASE FOR SIGNUP

Use Case Name: Signup

Actors Involved: Customer

contact, company, name.

Pre-Conditions Starting the services

Post-Conditions Authentic user created

Normal Flow of Actor Action System Response

2. Enters his details. 2. The entered details are

USE CASE FOR LOGIN:

Use Case Name: Login

Actors Involved: Customer, Admin

Pre-Conditions Use Case ID: signup

Post-Conditions Authentic user logged in.

Normal Flow of Actor Action System Response

1. Enter email address 1. System displays the home

2. Clicks the Login 2. System displays error

USE CASE FOR UPLOAD FILE:

Use Case Name: Upload File

ID: upload file

Actors Involved: Customer

Pre-Conditions Use Case ID: login

Post-Conditions Analysis sent to user through email

Normal Flow of Actor Action System Response

2. System starts processing the

USE CASE FOR REAL-TIME:

Use Case Name: Real Time

Actors Involved: Customer

Pre-Conditions Use Case ID: login

Post-Conditions Analysis shown on screen in real-time.

Normal Flow of Actor Action System Response

Use Case for API:

Use Case Name: API

Actors Involved: Customer

Brief Description An API request would be sent

Pre-Conditions Request sent

Post-Conditions Analysis returned

Normal Flow of Actor Action System Response

USE CASE FOR USAGE METRIC:

Use Case Name: Usage Metric

Actors Involved: Customer

Normal Flow of Actor Action System Response

USE CASE FOR PREDICTION MODEL:

Use Case Name: Manage Prediction Model

Actors Involved: Admin

Pre-Conditions Current running model

Post-Conditions Model updated

Normal Flow of Actor Action System Response

USE CASE FOR MANAGE CUSTOMER:

Use Case Name: Manage Customer

Actors Involved: Admin