IEEE830 requirement documentation
HelloWorld123
SRS-UseCase-FinalProject-MAllibalogun1.docx|
SwenCo Comic Website |
Version: 1.0 |
|
Software Requirements Specification |
Date: 03/23/2020 |
|
Yohammed LLC - 001 |
Yohammed LLC
Software Requirements Specification
For SwenCo Comic Website
Version <1.0> Comment by Sheldon Linker: These angle brackets should not be here.
Revision History
|
Date |
Version |
Description |
Author |
|
04/23/2020 |
1.0 |
Initial Documentation |
Mohammed Allibalogun |
|
|
|
|
|
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 5
1.3 Definitions, Acronyms and Abbreviations 5
1.4 References 6
1.5 Overview 6
2. Overall Description 6
2.1 Use-Case Model Survey 6
2.2 Assumptions and Dependencies 8
3. Specific Requirements 9
3.1 Use-Case Reports 9
3.1.1 Create Account 9
3.1.2 Manga Section 10
3.1.3 Comic Book Merchandise 11
3.1.4 Location Tracker 12
3.1.5 Contact Page 13
3.1.6 Non-Comic Book Merchandise in Store 14
3.1.7 Trading System for Second 15
3.1.8 Comic Book Rarity Tracker 16
3.1.9 Rare Merchandise in Stock 17
3.1.10 Daily Comic Books 18
3.1.11 Sell Second-Hand & Non-Comics 19
3.1.12 Employment 20
3.1.13 Order Online 21
3.1.14 Check Order 22
3.1.15 Inventory tracking System 23
3.2 Supplementary Requirements 23
4. Supporting Information
Software Requirements Specification
Introduction
The SwenCo is a small comic book store that’s planning to expend its service through the e-commerce world. The company has already conducted remote trading with its customers and wants to take the advantage of improving those remote trade by creating a website. By adding their presence on an e-commerce platform, SwenCo can not only increase their revenue by having more people accessing their product online, but it also makes their service ubiquitous.
SwenCo and their C.E.O, Captain Maryland, have contacted the Yohammed LLC software development firm to create their online comic book website. This firm is a well renowned software development company that specialized in the development of websites and most importantly ensuring that the stakeholders receive a final product that’s within their budget. Comment by Sheldon Linker: C.E.O. or CEO
The Software Requirement Specification document, also known as SRS, will be the detailed software description that will be implemented to develop the SwenCo comic book store website. This document will provide the summary of all the feature that will be implanted to create this website.
Purpose
This SRS has a very distinct purpose; provide a detailed documentation of requirements that will be use to create this website. The Yohammed LLC software company will follow these instructions to develop the online comic website by a date which will be finalized by the project manager.
The Section 3 in the SRS will provide an illustration for the many Use cases that will be implemented. The Use Case for this project goes as follow:
1. Create Account
2. Manga Section
3. Comic Book Merchandise
4. Location Tracker
5. Contact Page
6. Non-Comic Book Merchandise in Store
7. Trading System for Second
8. Comic Book Rarity Tracker
9. Rare Merchandise in Stock
10. Daily Comic Books
11. Sell Second-Hand & Non-Comics
12. Employment
13. Order Online
14. Check Order
15. Inventory tracking System
Scope
The website aims to create an online comic book store where an actor will be able to perform the same basic function online, like it could do at the physical store. An actor does not need to create an account to browse the site or pay for merchandise, but the option is there. It should be noted that the website will utilize the POS system that the book store as already in place that will allow user to pay online with once a credit or debit card.
Definitions, Acronyms and Abbreviations
Majority of the term used in this SRS documentation are self-explanatory. However, below we provided a list of term and abbreviation that may not be so familiar with the stakeholders and the developers:
· SPOSS – Square point of sale system. Comment by Sheldon Linker: This paragraph has extra leading under it.
· SRS – software requirement specification.
· QR code – information matrix uses to track newer merchandise
· Discord – a software used to communicate over voice, video, and text.
· ISBN – International Standard Book Number.
· CM – Captain Maryland.
References
“SRS Use Case Template”. (n.d.). UMGC. Retrieved on March 10, 2020, from https://learn.umuc.edu/d2l/le/content/444081/viewContent/16971639/View
“Photo Software. Software Requirements Speciation.” (n.d.). UMGC. Retrieved on March 10, 2020, from https://learn.umuc.edu/d2l/le/content/444081/viewContent/16971639/View
“RPG Project (Project 4 – Final Project).” (n.d.). UMGC. Retrieved on April 13, 2020, from https://learn.umuc.edu/d2l/le/content/444081/viewContent/17942538/View
“More from your Customer.” (n.d.). UMGC. Retrieved on April 22, 2020, from https://learn.umuc.edu/d2l/le/content/444081/viewContent/17942580/View
“Free Website Builder: Create a Free Website.” (n.d.). WIX. Retrieved on April 22, 2020, from https://www.wix.com/
Overview
Like many other requirement documentations, the SRS used for this project will be separated in two section. The Overall Description, located under section 2, will present the website design requirement at a High-Level, whereas the Specification Requirement, located on section 3, will define the website design requirements at the Low-Level. Comment by Sheldon Linker: into two sections
Overall Description
The development of this website will allow the SwenCo comic book store to expand their services online, thus making their services more ubiquitous and allow for more revenue to be generated. The primary feature of this website is to allow an actor to browse the site for different categories of comic books and purchase them online. The website does not require for an actor to create an account in order to view the site or make any purchases. However, there will be an option for the user to create an account, which will grant him/her the opportunity to earn store credit.
That credit can’t be rewarded for actor/s who do not have an account. The website will have multiple features; the webpage will have a contact me page that customers can use to contact the staff at the store. There will be a feature that will allow actor to sell the proprietor second-hand comics and no comic items. The website will provide a link for the user to find what non-comic-book merchandise are in store. The Manga and the Comic book Merchandise will have their own separate pages.
Additionally, the web page will have an employment opportunity search engine, a comic book rarity tracker, the rare merchandise that are in stock, and the comic book that the stores gets on a regular basic.
It should also be mentioned that a trending system will be implemented for people who are brining their second-hand comics book to the store.
Use-Case Model Survey
There will be 15 Use Cases that will display as requirement for this website. Section 3 will have a more detailed Use Case.
|
Use Case |
Description |
|
Create Account |
Creates an account for user on the website |
|
Manga Section |
Provides the user a section that’s exclusive related to only Manga books. |
|
Comic Book Merchandise |
Provides a list of comic book merchandise. |
|
Location Tracker |
An internal feature used by the client to find out in where the item is located in the store. |
|
Contact Page |
Page designated to help user get in contact with the proprietor or employees at the store via phone number, email, and address. |
|
Non-Comic Book Merchandise in Store |
Provides a list of non-comic book merchandise in store. |
|
Trading Systems For Second Hand Comics |
An internal system utilizes to conduct the trading for second hand comics from the users to the store. A user can send picture online or come to the come to the store. |
|
Comic Book Rarity tracker |
Feature utilize to track the rarity of a comic book. |
|
Rare Merchandise in Stock |
Provides a list of all rare merchandise in stock. |
|
Regular Comic Books |
Page designated to provides what comics the store gets on a regular basis. |
|
Sell Second-Hand & Non-Comics |
Provides a page where people can submit descriptions and pictures of items, they'd like to sell to the SwenCo comic book. Notify employee via eMail, IM, or Discord |
|
Employment |
User can find employment opportunity through a search engine. |
|
Order Online |
User can order books online which will be sent via mail. |
|
Check Order |
Allows user to check the order status. |
|
Inventory tracking System. |
To manage the overall inventory. |
Assumptions and Dependencies
Some assumption that may need to be consider is the SPOSS will be connected to the inventory tracking system. This will also interact when the actor order book or merchandise online and use the SPOSS to provide their credit card information. For clarification, a user is not required to have an account in order to perform any of the feature provided by the website, however no credit store will be awarded.
Specific Requirements
The specific requirement section in the SRS will provide a Lower-Level design of the SwenCo website implementation. The 15 Use cases will display each feature individually and how will they support the functionality of the website. Additionally, both the internal and external conditions will be presented in this segment as well.
Use-Case Reports
Create Account
|
Use Case ID: |
UC-1 |
|
Use Case Name: |
Create Account |
|
Actor: |
Customer |
|
Description: |
Users will create their accounts on the Application. |
|
Level: |
High |
|
Trigger: |
When the user opens the Application |
|
Normal Flow: |
1. User will open the Web Application 2. At the header, there will be button “Create Account” 3. After Clicking that button, a small box will appear 4. User has to write the details to create the account. |
|
Postconditions: |
Account will be created |
|
Screenshot |
|
Manga Section
|
Use Case ID: |
UC-2 |
|
Use Case Name: |
Manga Section |
|
Actor: |
Customer |
|
Description: |
Provides the user a section that’s exclusive related to only Manga books. |
|
Level: |
Medium |
|
Trigger: |
When the user clicks “Manga” on Navigation bar. |
|
Normal Flow: |
1. User will open the Web Application 2. User will click “Manga” on Navigation Bar Comment by Sheldon Linker: There's going to be a lot of items in each category. You need a way to search or filter. (throughout) |
|
Postconditions: |
Manga Section will be opened. |
|
Screenshot |
|
Comic Book Merchandise
|
Use Case ID: |
UC-3 |
|
Use Case Name: |
Comic Book Merchandise |
|
Actor: |
Customer |
|
Description: |
Provides a list of comic book merchandise. |
|
Level: |
Medium |
|
Trigger: |
When the user clicks “Manga” on Navigation bar. |
|
Normal Flow: |
1. User will open the Web Application 2. User will click “Manga” on Navigation Bar
|
|
Postconditions: |
Comic Book Merchandise section will be opened |
|
Screenshot |
|
Location Tracker
|
Use Case ID: |
UC-4 |
|
Use Case Name: |
Location Tracker |
|
Actor: |
Client |
|
Description: |
An internal feature used by the client to find out in where the item is located in the store. |
|
Level: |
High |
|
Trigger: |
When Client opens the Application |
|
Normal Flow: |
1. User will open the Application 2. The Homepage is this “Location Tracker Page” Comment by Sheldon Linker: In addition to what I pointed out above, how does this data get into the system? |
|
Postconditions: |
A search bar will be available to search any book in the store. |
|
Screenshot |
|
Contact Page
|
Use Case ID: |
UC-5 |
|
Use Case Name: |
Contact Page |
|
Actor: |
Customer |
|
Description: |
Page designated to help user get in contact with the proprietor or employees at the store via phone number, eMail, and address. |
|
Level: |
High |
|
Trigger: |
When user clicks “Contact Us” Button. |
|
Normal Flow: |
1. User opens the Application 2. User will click on “Contact Us” Button on header. |
|
Postconditions: |
A contact us pop-up page will appear, where user can email the employee or get in contact via phone number or address. |
|
Screenshot |
|
Non-Comic Book Merchandise in Store
|
Use Case ID: |
UC-6 |
|
Use Case Name: |
Non-Comic Book Merchandise in Store
|
|
Actor: |
Customer |
|
Description: |
Provides a list of non-comic book merchandise in store. |
|
Level: |
Medium |
|
Trigger: |
When user clicks “Non-Comic Merchandise” |
|
Normal Flow: |
1. User will open the Web Application 2. User will click “Non-Comic Merchandise” on Navigation Bar
|
|
Postconditions: |
Non-Comic Merchandise page will be opened. |
|
Screenshot |
|
Trading Systems For Second Hand Comics
|
Use Case ID: |
UC-7 |
|
Use Case Name: |
Trading Systems For Second Hand Comics |
|
Actor: |
Customer |
|
Description: |
An internal system utilizes to conduct the trading for second hand comics from the users to the store. A user can send picture online or come to the store. |
|
Level: |
High |
|
Trigger: |
User clicks on “Trading for Second Hand Comics” by hovering “others” on Nav Bar. |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Trading for Second Hand Comics Comment by Sheldon Linker: Then what? Obviously the form below appears, but carry this through to what happens after the user clicks on the submit button.
|
|
Postconditions: |
A form will appear for user to fill and then sell their books for trading. |
|
Screenshot |
|
/
Comic Book Rarity tracker
|
Use Case ID: |
UC-8 |
|
Use Case Name: |
Comic Book Rarity tracker |
|
Actor: |
Customer |
|
Description: |
Feature utilize to track the rarity of a comic book. |
|
Level: |
Low |
|
Trigger: |
When user clicks on Rarity Checker which is on the drop-down list of others (on Nav Bar). |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Rarity Checker” Comment by Sheldon Linker: Go on. What appears? How does this data get into the system?
|
|
Postconditions: |
A box will appear to check the rarity of any searched book. |
|
Screenshot |
|
Rare Merchandise in Stock
|
Use Case ID: |
UC-9 |
|
Use Case Name: |
Rare Merchandise in Stock |
|
Actor: |
Customer |
|
Description: |
Provides a list of all rare merchandise in stock. |
|
Level: |
Medium |
|
Trigger: |
User clicks on “Rare Stock” by hovering “others” on Nav Bar. |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Rare Stock”
|
|
Postconditions: |
A list of rare Merchandise will appear for the user. |
|
Screenshot |
|
Regular Comic Books
|
Use Case ID: |
UC-10 |
|
Use Case Name: |
Regular Comic Books |
|
Actor: |
Customer |
|
Description: |
Page designated to provides what comics the store gets on a regular basis. |
|
Level: |
Medium |
|
Trigger: |
When user clicks on Daily Comics which is on the drop-down list of others (on Nav Bar). |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Daily Comics” Comment by Sheldon Linker: These things are published weekly, daily, or quarterly.
|
|
Postconditions: |
A list of Daily Comics will appear for the user. |
|
Screenshot |
|
Sell Second-Hand & Non-Comics Comment by Sheldon Linker: How is this different from §3.1.7?
|
Use Case ID: |
UC-11 |
|
Use Case Name: |
Sell Second-Hand & Non-Comics |
|
Actor: |
Customer |
|
Description: |
Provides a page where people can submit descriptions and pictures of items, they'd like to sell to the SwenCo comic book. Notify employee via eMail, IM, or Discord |
|
Level: |
High |
|
Trigger: |
When user clicks on Sell Second-Hand Products which is on the drop-down list of others (on Nav Bar). |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Sell Second-Hand Products”
|
|
Postconditions: |
A form will appear to get the information of the seller and the product. |
|
Screenshot |
|
Employment
|
Use Case ID: |
UC-12 |
|
Use Case Name: |
Employment |
|
Actor: |
Customer |
|
Description: |
User can find employment opportunity through a search engine. |
|
Level: |
Low |
|
Trigger: |
When user clicks on Employment Opportunity which is on the drop-down list of others (on Nav Bar). |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Employment Opportunity” Comment by Sheldon Linker: You can pop a whole list without the dialg, since there will be approximately 1 job at any time. How does the job data get into the system?
|
|
Postconditions: |
A search box will appear for users to select any job title. |
|
Screenshot |
|
Order Online
|
Use Case ID: |
UC-13 |
|
Use Case Name: |
Order Online |
|
Actor: |
Customer |
|
Description: |
User can order books online which will be sent via mail. |
|
Level: |
High |
|
Trigger: |
When user click “Buy” on any Product. |
|
Normal Flow: |
1. User opens the application 2. User open the Comic or any Merchandise page 3. User clicks “Buy” button on any product Comment by Sheldon Linker: Ok the thing is now in the cart. How does the cart get sold and delivered? |
|
Postconditions: |
Product will be added to the buyer’s cart. From the cart User can click on “Confirm Order” to order the products. |
|
Screenshot |
|
Check Order
|
Use Case ID: |
UC-14 |
|
Use Case Name: |
Check Order |
|
Actor: |
Customer |
|
Description: |
Allows user to check the order status |
|
Level: |
Medium |
|
Trigger: |
When user clicks on Check Order Status which is on the drop-down list of others (on Nav Bar). |
|
Normal Flow: |
1. User will open the Web Application 2. User will Hover mouse on “Others” on Navigation Bar 3. A small list will appear. 4. User will click “Check Order Status”
|
|
Postconditions: |
A search box will appear for user to search the product with its Order Id. |
|
Screenshot |
|
Inventory tracking System.
|
Use Case ID: |
UC-15 |
|
Use Case Name: |
Inventory Tracking System |
|
Actor: |
Client |
|
Description: |
To manage the overall inventory. |
|
Level: |
High |
|
Trigger: |
Client will open its Application and then Clicks on “Inventory Tracking System” |
|
Normal Flow: |
1. User will open Application 2. User will click “Inventory Tracking System” |
|
Postconditions: |
A page will appear that will tell the overall performance |
|
Screenshot |
|
Supplementary Requirements
Performance:
· The system will be interactive and will have very few and short delays ranging approx. 2-3 seconds
Usability:
· A normal user can learn to use the Application in 3-5 minutes max.
Supportability:
· Supported on Browsers such as Mozilla, Chrome, Opera and Safari.
Modifiability:
· Effort required to modify this software shall be low as it will only require1-2 weeks on average to make any kind of modification in the software
Security:
· Transmission of data, storage of information and transaction shall be secure without any changes in information.
|
Confidential |
SwenCo 2020 |
Page 21 |
