Th64-CSE360-Phase-3

.pdf

School

Arizona State University *

*We aren’t endorsed by this school

Course

360

Subject

Computer Science

Date

Feb 20, 2024

Type

pdf

Pages

Uploaded by MinisterExplorationMouse17

CSE 360 Project Report Number 3 Team Th64 Team Member Names: 1. William Adams 2. Jaden Thomas 3. Quan Nguyen 4. David Williams 5. Evan Gittens

Team Project Phase 3 Table of Contents 1. Executive Summary ............................................................................................................................... 1 2. Customer Problem ................................................................................................................................ 2 3. Concept of Operations .......................................................................................................................... 3 4. Received Requirements ...................................................................................................................... 10 5. Derived Requirements ........................................................................................................................ 12 6. High-Level System Architecture .......................................................................................................... 13 7. Requirements Analysis ........................................................................................................................ 16 8. Conclusion .......................................................................................................................................... 23 9. Appendix A: Credit Sheet .................................................................................................................... 25 10. Appendix B: Current Team Norms ................................................................................................. 26 1

Team Project Phase 3 Executive Summary 1. Executive Summary Since its inception in 2005, EffortLogger has been an indispensable cog in streamlining our customers' project tracking and management process. However, as our client’s organization burgeons and adapts to dynamic currents, a flood of new challenges have emerged, it’s incredibly clear that these challenges require our attention to ensure EffortLogger not only retains functionality, but also adapts to the clients rapidly changing environment. The upcoming challenge navigates the careful balance between insatiable appetite for increasing productivity and accuracy against the imperative of safeguarding the covert sanctuary of employee privacy. Our client aspires to improve their planning accuracy by collecting more data, all while preserving the confidentiality surrounding their workforce. Simultaneously, the ominous specter of data security casts a long shadow. The competitive arena sees rivals arming themselves with sophisticated hacking strategies with the goal of infiltrating and stealing sensitive data. The clarion call is for EffortLogger to bolster its data security bastions, creating robust barriers between threat actors and our clients precious data. Moreover, as our client faces exponential growth the indispensable need for a more robust EffortLogger grows as well. With the establishment of a Quality Assurance Engineering entity and the expansion of agile teams, EffortLogger must evolve. The envisioned enhancements include: agile framework integration for expedited poker planning sessions that include real-time data sharing amongst crew members. Additionally, the tool will include measures to enhance security by anonymizing individual effort and defect reports, this sets the tone for a secure yet productive environment. EffortLogger V2.0 is not merely an upgrade but also a strategic move towards adjusting with more modern project management tools and paradigms. This will ensure our client remains operational, running efficiently and safely in a sea of competitors. 1

Team Project Phase 3 Customer Problem 2. Customer Problem 2.1 Customer Problem 1: Employee Privacy and Data Security 2.1.1 Need to Find Automated Way to Identify Opportunities for Improvement Without Violating Employee Privacy ● The firm has recently been pressured for workers to provide more detail about their productivity rates, defect rates, and other data. ● This would enable the firm to reduce the size of the contingencies that must be added to deal with “surprises.” ● The online drop box used for submitting efforts and defects contain user information which concerns users. ● The firm used a third-party tool for anonymizing user information in the metadata. This provides a lack of adequate measures to protect and prevent potential risks. ● Transparency in pay raises and promotions is valued importantly in the firm. Since the system is transitioned to a data-driven system, it could negatively impact the transparency 2.2 Customer Problem 2: Confidential Information Security 2.2.1 Competitors Rumored to Employ an Array of Hacking Methods to Gain Access to Confidential Planning and Operational Data ● The entire leadership team is equally concerned about hackers gaining access to the firm’s confidential information. ● Access to this information would give unfair insights into the firm’s capabilities, competencies, and other sensitive information 2.3 Customer Problem 3: Enterprise-Scale Support for Agile and Quality ● The system solutions the customer produces have increased in size by a factor of 20 since the first EffortLogger tool was produced and delivered. Costs have gone up by a larger factor leading to the creation of a Quality Assurance Engineering organization with interesting cross-functional links to the firm’s Human Resources and Customers Services organizations. ● Need for a generic system product to address what the firm see’s as the potential for significant demand to support enterprise-scaled agile teams. 2

Team Project Phase 3 Concept of Operations 3. Concept of Operations 4. Key Operational Scenarios 4.1. Overview of the Operational Scenarios 4.1.1. The user wants to track their effort on a deliverable. ● The system will generate a spreadsheet of the user’s effort log based on the information provided. When the user is entering the project they are working on, the user will also be able to specify the stakeholder they’re working with. 4.1.2. The user is in a “planning poker” session with their colleagues ● The system will show the user relevant user stories from their backlog, sorted by their average weight based on prior user input. The user can then change weights on-the-fly to re-order the importance of these user stories. 4.1.3. The user wants to share their “planning poker” card ● Once the “share” button is clicked, the system will generate a stylized “card” that will be sent to their team’s applications as well. 4.2. Proposed Solution Summary ● Our proposed solution is to keep EffortLogger relatively similar to how it has worked in the past but add extra features such as support for enterprise scale operations, the ability to include identifying information about individuals in an entirely new user interface overhaul, improved user story based estimations, and an all new planning poker tool. We choose this specific approach due to the problems and needs given to us by the documents that were provided to us by our customers and stakeholders. 4.3. Major Processes and Functions ● Attributes Start/Stop an activity and then log it as an entry Process Name Create an Effort Log entry Purpose This process is relatively the same as it is in the original EffortLogger but now includes the ability to include identifying information about the user logging the activity and the option to include more enterprise scale information in the activity. Description The user can press the Start Activity 3

Team Project Phase 3 Concept of Operations button to start the current activity. After the activity is finished and the user has entered all relevant information to log, then the user can press the Stop Activity button to stop and log that activity. Priority High Frequency Duration of the process will continue until the user stops the current activity that they are logging. ● Attributes Edit attributes of an activity Process Name Edit an Effort Log entry Purpose This process is largely identical to the original Effort Log entry editing process but it must now include support for entering/editing more enterprise scale information about the activity. Description The user can select a Project and an Effort Log entry from said project to modify. Alternatively, they can clear all entries from a project. All attributes of the entry log should be able to be modified and then edited. The entry itself should be able to be split into two entries or deleted. Beyond this, the user should be able to return to the effort log console. Priority High Frequency This process may not occur during every use of the Effort Logger, however, it is essential for a user to be able to correct any initial errors in their log. ● Attributes Create a defect log Process Name Create a defect log 4

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help