(Individual Project) Website to explain Algorithms and Data Structure concepts and code walkthroughs in C#.
- Anticipated Completion Date: October 31, 2020
- Concept Description
- Wire-Frames (DRAFT)
- Initial ERD Diagram
- User Stories
- Use Cases
- Use Case Diagram
- Requirements
- Requirements Table
- Test Case Table
- Intitial Prototype
- Database Diagram
- Test Readiness Review
- After researching throughout the internet, I found a lack of information on Algorithms and Data Structures solved in C#.
- For a person that chooses to learn C# as their first programming language, it would be more difficult to understand Algorithms and Data Structures in another language.
- I have decided to create a website that will explain concepts and walkthrough code utilizing the C# programming language.
- There will be two videos and multiple challenges for each chapter.
- Each chapter will focus on a key concept.
- At the bottom of every chapter, there will be an embeded code editor with challenges and test cases so users can practice the chapter's key concept.
THESE ARE INITIAL DRAFTS
Initial database diagram draft
1. As a MSSA Student, I need to learn Algorithms and Data Structures in C#. So that I can do well in the Whiteboarding portion of the Technical Interview
2. As a School teaching C#, I need a resource for my students for whiteboard practice. So that more students are competent and confidant during whiteboarding challenges.
3. As a Company utilizing C#, I need a way to screen candidates. So that I can spend less time screening and more time interviewing the right candidates.
4. As an administrator, I need a simple way to add more and change content. So that information can be updated or added as technologies change or better ideas are available.
Scenario #1: <Student/ Employee> accesses website content.
Given: < Student/ Employee > is a subscriber.
When: < Student/ Employee > Logs in.
Then: Content is viewable to the < Student/ Employee > based on where they left off.
Scenario #2: <Student/ Employee> wants to check content before subscribing.
Given: <Student/ Employee> is not a subscriber.
And: <Student/ Employee> wants to learn Algorithms and Data Structures in C#.
When: <Student/ Employee> enters website.
Then: A preview of the course is available to the <Student/ Employee>.
Scenario #3: <Student/ Employee> wants to send their progress to a <School/ Company>.
Given: <Student/ Employee> is subscriber.
And: <Student/ Employee> has completed at least one subject.
When: <Student/ Employee> requests a progress report be sent to their <School/ Company>.
Then: <School/ Company> will receive an email with the completed code challenges, student’s submitted code and percent of course complete.
Scenario #4: <School/ Company> wants to check content before recommendation.
Given: < School/ Company > is not a subscriber.
And: < School/ Company > wants to recommend website to students.
When: < School/ Company > enters website.
Then: A preview of the course is available to the < School/ Company >.
Scenario #5: Instructor wants to add content.
Given: Instructor has admin username and password.
When: Instructor logs in.
Then: Instructor will be taken to an “Add Content” page where they can add videos, code challenges and test cases.
Scenario #6: <Student/ Employee> is stuck on a coding challenge and needs help.
Given: <Student/ Employee> is a subscriber.
And: <Student/ Employee> wants help with a coding challenge or concept.
When: <Student/ Employee> explains their issue in the message board.
Then: Instructor and other <Student/Employee>s are able to comment to explain.
Scenario #7: < Student/ Employee > find a bug in the website or incorrect test case.
Given: < Student/ Employee > found a bug.
When: <Student/ Employee> selects the bug icon.
Then: A form will pop up to describe the bug and will be emailed to instructor when submitted.
Scenario #8: < Student/ Employee > Finds the content useful.
Given: < Student/ Employee > wants to register.
When: <Student/ Employee> selects the register link.
Then: The <Student/ Employee> will be directed to the registration page.
- 1.0 Create User: System shall allow users to be created
- 1.1 User Form: System shall allow users to input their personal information
- 1.2 Password Encryption: System shall encrypt password that has been input
- 1.3 Form Validations: System shall check to see if input data is correct type and length
- 2.0 Authenticate User: System shall ensure the user is created
- 3.0 Login User: System shall login users with email and password
- 3.1 Check Subscription: System shall check to see if user is subscriber or past subscriber
- 4.0 Upload Content: System shall allow Admin to upload videos and code challenges
- 5.0 Check Solutions: System shall check user solution against test cases
- 5.1 Return result: System shall tell user how many test cases passed
- 6.0 Check expiration: System shall check expiration date
- 6.1 Charge User: System shall charge user for another month
- 6.2 Unsubscribe User: System shall disable subscription content
- 7.0 Preview Content: System shall allow unregistered User to preview the Website.
| Requirement ID | Requirement Description | Test Method |
|---|---|---|
| 1.0 | Create User: System shall allow users to be created | Demonstration |
| 1.1 | User Form: System shall allow users to input their personal information | Demonstration |
| 1.2 | Password Encryption: System shall encrypt password that has been input | Inspection |
| 1.3 | Form Validations: System shall check to see if input data is correct type and length | Inspection |
| 2.0 | Authenticate User: System shall ensure the user is created | Demonstration |
| 3.0 | Login User: System shall login users with email and password | Demonstration |
| 3.1 | Check Subscription: System shall check to see if user is subscriber or past subscriber | Demonstration |
| 4.0 | Upload Content: System shall allow Admin to upload videos and code challenges | Demonstration |
| 5.0 | Check Solutions: System shall check user solution against test cases | Inspection |
| 5.1 | Return result: System shall tell user how many test cases passed | Inspection |
| 6.0 | Check expiration: System shall check expiration date | Inspection |
| 6.1 | Charge User: System shall charge user for another month | Inspection |
| 6.2 | Unsubscribe User: System shall disable subscription content | Inspection |
| 7.0 | Preview Content: System shall allow unregistered User to preview the Website. | Inspection |
| Test ID | Req ID | Test Procedure | Current Status | Time Stamp |
|---|---|---|---|---|
| TC001 | 1.0 | Check if a user is created once you submit the create user form | Passed | Sep 23, 2020 |
| TC002 | 1.1 | Form should allow user to input their information | Passed | Sep 23, 2020 |
| TC003 | 1.2 | Check the database to make sure passwords are encrypted when creating a user and logging in | Failed | Sep 23, 2020 |
| TC004 | 1.3 | Check to see if validations occur if user inputs incorrect information | Passed | Nov 02, 2020 |
| TC005 | 2.0 | Check the email against the database to ensure unique email | Passed | Nov 02, 2020 |
| TC006 | 3.0 | Log in with a previously created account | Not Tested | |
| TC007 | 3.1 | Check to see if the logged in user has an active subscription | Not Tested | |
| TC008 | 4.0 | Upload a video to see if it is displayed on the webiste | Passed | Sep 30, 2020 |
| TC009 | 5.0 | Try correct and incorrect answers against the test cases | Not Tested | |
| TC010 | 5.1 | Once an answer is submitted, the amount of correct test cases are displayed to the user | Not Tested | |
| TC011 | 6.0 | Check an active account and an inactive account to check for expiration | Not Tested | |
| TC012 | 6.1 | When the account is expired and the user is on subscription, recharge the user | Not Tested | |
| TC013 | 6.2 | When the account is expired and the user is not on subscription, deactivate the user | Not Tested | |
| TC014 | 7.0 | Check to see if the preview page works and is available to all users | Passed | Oct 14, 2020 |
All of the requirements are currently covered by test cases. Although all of the test cases have not been tested because the project is not complete.
67% of the tested test cases are passing.
29% of the test cases out of the total amount of test cases are passing.
43% of the test casses have been tested.
The validation should be accurate to how the user is expected to use the website. The tests were created to be as realistic as possible to how the requirement will be satisfied. The requirements were created based on how a user will see and use the website. New tests will be created based on unique circumstances that might occur once the project is completed.