ez4bk / smarter-university-system-17 Goto Github PK

Activity of Epic #45
Assign story points to each user story. You will have 100 points in total to distribute to each user story. Just like you have 100 dollars to buy user stories. You can have multiple user stories with the same story points. Assign story points in terms of their importance, feasibility, and complexity.

Activity of Epic #45
Assign story points to each user story. You will have 100 points in total to distribute to each user story. Just like you have 100 dollars to buy user stories. You can have multiple user stories with the same story points. Assign story points in terms of their importance, feasibility, and complexity.

Epic of MVP #4
Development on the software has started and the first two sprints have been completed. Your team has been developing features at a very fast pace and is worried that the quality of the software may be suffering. You are put in charge of a specific part of the for review. Your task is to review the source code and find instances where the software would crash under specific circumstances.
You are to write unit tests to cause such an application failure. Your focus in the quizzes module. After the developers fix these issues, your test cases can be used to verify that the issues have indeed been resolved.
Your task is to write 3 unit tests such that each unit test causes the quizzes part of the application to crash. You can find already existing test cases in the test directory of the repository. See the discussions_test.py for a complete test case. The quizzes_test.py has already been created. It has the first test function named test_expose_failure_01() already created. You need to implement that function and add two more functions.
Your test cases should cause the source code related to the quizzes capabilities to crash. That means the program will exit prematurely. Each of your test cases must make the program crash. No two test cases can cause a crash in the same line of code. In other words, the crash induced for every one of your test cases must be at a different line in the program.
In the comment of your test case, you must specify the file and the line number where the program is crashing.
You must specify at least one assertion on the expected output if the program did not crash.
Push the updated test cases to your forked repository and create a Pull Request. You must commit the test cases by the due date of the project.

Activity of Epic #41
Compose all deliverables and make the final submission.

Activity of Epic #45
Assign story points to each user story. You will have 100 points in total to distribute to each user story. Just like you have 100 dollars to buy user stories. You can have multiple user stories with the same story points. Assign story points in terms of their importance, feasibility, and complexity.

Activity of Epic #40
In the Google Doc, go to the "main" sheet in the bottom bar, complete test cases for "text" and "flag", and compile all test cases from other sheets.

text: The text of the post must have at least one character but may not exceed 100 characters.
flag: Attaches an icon to the post that provides a quick indicator about the role of the post. Possible values are: “INFO”, “IMPORTANT”, ”DUE_SOON”.

text is required.
flag is optional, so make sure you put null values as one of the entries as well.

Activity of Epic #44 #45
Redo of Activity #15 #21 #26
SOW is on page 13 of the PDF: https://github.com/ez4bk/smarter-university-system-17/blob/main/ProjectAssignment.pdf

Activity of Epic #45
Assign story points to each user story. You will have 100 points in total to distribute to each user story. Just like you have 100 dollars to buy user stories. You can have multiple user stories with the same story points. Assign story points in terms of their importance, feasibility, and complexity.

Develop design based on requirement analysis. Draw diagrams if needed. Discuss with frontend to coordinate.

Activity of Epic #44
Everyone in the group should contribute around 5 user stories to the project.

Activity of #45
Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree.
Using the graph tool provided https://dreampuf.github.io/GraphvizOnline/
Name your graph as "digraph varun_gole {".

Activity of Epic #44 #45
Redo of Activity #14 #20 #25
SOW is on page 13 of the PDF: https://github.com/ez4bk/smarter-university-system-17/blob/main/ProjectAssignment.pdf

Epic of MVP #3
In an effort to better understand what requirements the customer has raised in the SOW, you decide to rephrase them into user stories. User stories have the advantage that they are smaller, separate and, therefore, more manageable requirements. As a first step, identify epics that you want to organize the requirements by. Then, re-formulate the requirements stated in the SOW as user stories. The user stories must follow the exact format discussed in class. Each of the user stories must be assigned to an epic. Also, each user story must be assigned a unique identifier (e.g., numbers 1...n). Document the user story in the provided spreadsheet template and submit it as part of deliverable E.

Activity of Epic #6
Only activities go to the scrum board, no MVPs or Epics. Move from TODO to In Progress and Done if needed.

Create issues in GitHub. Create and maintain the scrum board.

Activity of Epic #40
In the Google Doc, go to the "location" sheet in the bottom bar, and complete test cases for "lat" and "lon".

lat: The latitude of the location this post was sent from. This is set when the user posts from a mobile device and location is enabled. The value must be inside the range -90.0 to +90.0 (North is positive) inclusive.
lon: The longitude of the location this post was sent from. The valid ranges for longitude are -180.0 to +180.0 (East is positive) inclusive.

These two parameters are optional, so make sure you put null values as one of the entries as well.

Do not put anything in the main sheet!

Activity of #45
Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree.
Using the graph tool provided https://dreampuf.github.io/GraphvizOnline/
Name your graph as "digraph chandan_salil {".

Activity of Epic #44
Everyone in the group should contribute around 5 user stories to the project.

Activity of Epic #45
Calculate story points and generate a group-level priority binary tree.

Activity of #45
Verify all the requirement binary trees created by contributors in this project

Activity of Epic #45
Assign story points to each user story. You will have 100 points in total to distribute to each user story. Just like you have 100 dollars to buy user stories. You can have multiple user stories with the same story points. Assign story points in terms of their importance, feasibility, and complexity.

Activity of Epic #41
Your task is to write 3 unit tests such that each unit test causes the quizzes part of the application to crash. You can find already existing test cases in the test directory of the repository. See the discussions_test.py for a complete test case. The quizzes_test.py has already been created. It has the first test function named test_expose_failure_01() already created. You need to implement that function and add two more functions.
Your test cases should cause the source code related to the quizzes capabilities to crash. That means the program will exit prematurely. Each of your test cases must make the program crash. No two test cases can cause a crash in the same line of code. In other words, the crash induced for every one of your test cases must be at a different line in the program.
In the comment of your test case, you must specify the file and the line number where the program is crashing.
You must specify at least one assertion on the expected output if the program did not crash.

Activity of Epic #44
Everyone in the group should contribute around 5 user stories to the project.

Activity of Epic #44 #45
Redo of Activity #12 #18 #23
SOW is on page 13 of the PDF: https://github.com/ez4bk/smarter-university-system-17/blob/main/ProjectAssignment.pdf

Activity of Epic #45
Take the spreadsheet with the user stories from Task 3 and add columns to capture the requirements rank for each of the team members as well as the total overall requirements rank. Submit the document in xlsx (Excel) format. The file must be named Team_x_UserStories.xlsx where x is to be replaced with the number of your team. Each requirement is represented as a row in the spreadsheet. The first column contains the requirements ID, the second column contains the name of the epic, and the third column contains the user story. A template for this spreadsheet is provided in the files for the assignment.

Epic of MVP #2
Create a scrum board using GitHub Project. Show the progress of activities on the board.

Activity of Epic #40
In the Google Doc, go to the "time" sheet in the bottom bar, and complete test cases for "post_time" and "due_time".

post_time: The date and time when the post should be made visible. This allows for delaying the posting to a specific time. The date and time must be specified in the ISO 8601 format with offset (https://en.wikipedia.org/wiki/ISO_8601)
due_time: The date and time when the post is due. This can be used to alert viewers of an action that needs to be taken and by what time that action is due. The date and time must be specified in the ISO 8601 format with offset (https://en.wikipedia.org/wiki/ISO_8601)

These two parameters are optional, so make sure you put null values as one of the entries as well.

Do not put anything in the main sheet!

Activity of Epic #44
Everyone in the group should contribute around 5 user stories to the project.

Epic of MVP #4
A crucial part of the quality assurance procedures is the testing of the system boundaries. More specifically, the Application Programming Interface (API) through which the user interface and other systems interact with the backend must be robust even when it receives requests that violate the API specification. Your task is to create test inputs for an API endpoint.
The endpoint exposes a new capability of the SUS that has come out of feedback from sprint reviews in which stakeholders expressed the desire to be able to show an activity stream in the sidebar of the SUS user interface. Lecturers and students alike can post to that activity stream as a means to provide status updates or to prompt others to complete tasks.
The primary component of an activity post is the message text, which is specified in the POST body. However, several additional parameters are specified in the URL to that endpoint as shown in this example:
POST /activity?flag=IMPORTANT&directed=TRUE&recipients=cdarwin body: I’d like to discuss the project

Remember, a test case means you call the API endpoint and you specify values for each of the parameters that are listed above. Example:
POST /activity?flag=IMPORTANT&directed=TRUE&recipients=cdarwin body: I’d like to discuss the project
Hence, for a single test case, you must choose what value to provide for each of the input parameters. Of course, some parameters may not have a value at all for some test cases. In the example URL above, only some of the parameters have been specified. In that situation, you leave the value for that parameter empty.

A spreadsheet where each row represents a test case and each column the value of the respective parameter. The submitted spreadsheet should be named activities_team_.xlsx
Where is the number of our team.

Create user stories. Prioritize user stories.

Develop design based on requirement analysis. Draw diagrams if needed. Discuss with backend to coordinate.

Activity of #45
Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree.
Using the graph tool provided https://dreampuf.github.io/GraphvizOnline/
Name your graph as "digraph yuchen_wei {".

Activity of Epic #5
Review all issues created and examine the quality of them.

Activity of Epic #40
In the Google Doc, go to the "direct" sheet in the bottom bar, and complete test cases for "directed" and "recipients".

directed: If set to TRUE, the post is directed towards other users. If this is set TRUE, the set of users must be specified in the recipients parameter.
recipients: Comma separated list of user ids where each user ID is a string. This value should not be set if the “directed” parameter is FALSE. The user names must be existing user names (see appendix)

These two parameters are optional, so make sure you put null values as one of the entries as well.

Do not put anything in the main sheet!

Appendix
When creating API test inputs, the endpoint expects usernames of users that exist in the system. Valid usernames are
the following:

• cdarwin
• tedison
• einstein

Any other username is considered an invalid username.

Activity of Epic #44
Examine all user stories created. Eliminate unnecessary ones and optimize the best outcome.

Activity of #45
Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree.
Using the graph tool provided https://dreampuf.github.io/GraphvizOnline/
Name your graph as "digraph kaustubh_bhatt {".

Activity of Epic #44 #45
Redo of Activity #16 #22 #27
SOW is on page 13 of the PDF: https://github.com/ez4bk/smarter-university-system-17/blob/main/ProjectAssignment.pdf

Activity of Epic #5
Create issues regarding activities that will be performed during the project. Plan some issues for later Epics.

Epic of MVP #2
Create labels. Create Issues. Assign activities.

Activity of Epic #44 #45
Redo of Activity #13 #19 #24
SOW is on page 13 of the PDF: https://github.com/ez4bk/smarter-university-system-17/blob/main/ProjectAssignment.pdf

Create API test inputs. Write unit tests.

Activity of #45
Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree.
Using the graph tool provided https://dreampuf.github.io/GraphvizOnline/
Name your graph as "digraph dhruven_patel {".

Activity of Epic #5
Create MVP, Epic, and Activity labels

Epic of MVP #3
Now that you have derived the user stories, you need to establish a priority order amongst them. The customer is currently unavailable but you have decided on a prioritization strategy and would like to do a practice run with the software engineers on your team. Apply the binary tree method discussed in class. All members of your team should apply the technique independently and you should combine the priorities of team members into an overall priority for each requirement. More specifically, every team member should take the list of requirements. Using the binary tree algorithm, consider each of the requirements. Starting with the first requirement as the root node, take any subsequent requirement and decide if it is more or less important than the requirements already in the tree. Follow the procedure discussed in class to create a binary tree (one for each team member).
Initially, you can create the binary tree in any format you choose. However, you have to submit your diagram in Graphviz format. See the section Creating binary trees in GraphViz format below for a description of how to generate such a graph. The trees should be submitted in one document named Team_x_Bigraph.txt where “x” is to be replaced with the number of your team. Label the graph with the name of the team member. For instance, for JohnDoe,thefirstlineofthegraphshouldbe“digraph john_doe {“.

After you constructed the bigraph, you determine the order of requirements for each of the team members by reading their respective bigraphs and noting the index of each requirement. The requirement with index 1 is the most important requirement. This will tell you the requirement priorities for each team member. Now, aggregate the priority ranks that each team member gave each requirement into a total priority. That priority ranking reflects the order of requirements in order of importance. The development team can now take this input and take the top few requirements to be implemented.
Take the spreadsheet with the user stories from Task 3 and add columns to capture the requirements rank for each of the team members as well as the total overall requirements rank. Submit the document in xlsx (Excel) format. The file must be named Team_x_UserStories.xlsx where x is to be replaced with the number of your team. Each requirement is represented as a row in the spreadsheet. The first column contains the requirements ID, the second column contains the name of the epic, and the third column contains the user story. A template for this spreadsheet is provided in the files for the assignment.

Activity #45

Activity of Epic #6
Create a scrum board using GitHub Project.

Activity of Epic #44
Everyone in the group should contribute around 5 user stories to the project.