THE FAB FIVE FIRM T E A M A S S I G N 3/7/2013 MILESTONE TWO ISDS 3100: SPRING 2013 AMEN AHMED ALI BURMESTER NELSON JOINTER DANIELLE KRUMM CHANCE WAHL

Transcription

1 THE FAB FIVE FIRM T E A M A S S I G N 3/7/2013 MILESTONE TWO ISDS 3100: SPRING 2013 AMEN AHMED ALI BURMESTER NELSON JOINTER DANIELLE KRUMM CHANCE WAHL

2 TABLE OF CONTENTS Actor Glossary Use-Case Glossary Use-Case Diagram Use-Case Narratives....5 Map Detailed Activities Appendix Gantt Chart Page 1

3 ACTOR GLOSSARY Term Synonym Description Owner Team leader Controller of the program. Responsible for creating and assigning tasks and posting content for. Team Group member Individuals that acts on the created and assigned task that s given by the owner. Page 2

4 USE-CASE GLOSSARY Use-Case Name Use-Case Description Participating Actors and Roles View Group Projects Post Content This use case describes how the owner and members will be able to view the project that they are working on in that specific group. This use case describes the event of the owner and/or team members posting content such as documents or diagrams. Owner Team Owner Creating and Assigning Tasks This use case describes the event of the owner creating and assigning task amongst the team members. Owner Page 3

5 USE-CASE DIAGRAM Page 4

6 USE-CASE NARRATIVES Team Assign Author (s): _Danielle Krumm Date: 3/12/2013 USE CASE NAME: PRIMARY BUSINESS ACTOR: OTHER PARTICIPATING ACTORS: View Group Projects Owner Team DESCRIPTION: This use case describes how the owner and members will be able to view the project that they are working on in that specific group. PRE-CONDITION: The individual creating the group project must be the owner. TRIGGER: This use case is initiated when the owner adds members to the group. TYPICAL COURSE Actor Action System Response OF EVENTS: Step 1: Step 2: The owner provides his username The system responds by verifying that all and password. required information has been provided. ALTERNATE COURSES: CONCLUSION: POST-CONDITION: Step 3: The owner creates the project and adds team members to the group by pressing the plus sign next to the project name. Step 5: The owner types the username of the team member and presses the plus sign to add the member to the project. Step 4: The system responds by opening a small box where the owner can type the name of the member and press add. Step 6: For each member added to the group, the system verifies that they can view information uploaded by the owner. Alt-Step 7: The owner or club member can go back to other projects they are a part of. Alt-Step 8: The owner or club member can log out of the project. Alt-Step 9: The owner or team member can press the home button to go back to the project home screen. This use case concludes when all members of the group are able to view and make changes to the project. The group was made and members were added. BUSINESS RULES IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS The owner is the only person allowed to create a group. The owner is the only member allowed to add other members to a particular group project. GUI to be provided for Team Assign members via a smartphone App. ASSUMPTIONS: OPEN ISSUES: CORRESPONDING FORMS AND REPORTS: 1. Need to determine which member will complete each task of the project. Task Form Page 5

7 Team Assign Author (s): _Amen Ahmed Date: 3/12/13_ USE CASE NAME: PRIMARY BUSINESS ACTOR: OTHER PARTICIPATING ACTORS: DESCRIPTION: Post Content Owner Team s, Database (internal server) This use case describes the event of the owner and/or team members posting content such as documents or diagrams. PRE-CONDITION: The team leader and all other members must be registered users of Team Assign. TRIGGER: This use case is initiated content (files) are added to a project. TYPICAL COURSE Actor Action System Response ALTERNATE COURSES: CONCLUSION: POST-CONDITION: BUSINESS RULES IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS ASSUMPTIONS: OPEN ISSUES: CORRESPONDING FORMS AND REPORTS: Step1: From the Documents page, a user can press the + button to add a file to the project. Step3: The user inputs the name of the file, the related task(s) from a drop down list, and the file itself. Step4: The user presses Save to complete the file add. Step6: The document/file added is now viewable and downloadable by all team members. Step2: The system will return a Document Add page that allows for user input. Step 5: The system stores the file and file information in an internal database and returns a verification message to the user. Step7: The system makes documents/files readily available on demand. Go home Go back Sign Out This use case concludes when a user adding a document/file receives a verification message that the document/file was successfully added to the project. The document/file has been added to the project. Duplicate document/file names will not be accepted within a project. N/A GUI to be provided for Team Assign members via a smartphone App. s will be notified of new documents/files added with a New status on documents/files that a member has not viewed. N/A File Sharing form Page 6

8 Team Assign Author (s): Amen Ahmed Date: 3/12/13_ USE CASE NAME: PRIMARY BUSINESS ACTOR: OTHER PARTICIPATING ACTORS: DESCRIPTION: Creating and Assigning Tasks Owner Database (internal server) This use case describes the event of the owner creating and assigning task amongst the team members. PRE-CONDITION: The team leader and all other members must be registered users of Team Assign. TRIGGER: This use case is initiated when tasks are added to a new project. TYPICAL COURSE Actor Action System Response ALTERNATE COURSES: CONCLUSION: POST-CONDITION: BUSINESS RULES IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS ASSUMPTIONS: OPEN ISSUES: CORRESPONDING FORMS AND REPORTS: Step1: From a project s task page, the owner of a project will press the +Add Task button. Step3: The owner will then fill in required information such as task name, due date, responsible party, task description. Step4: Press the Add Task button to save and add the task to the projects list of tasks. Step6: Team members can now view created tasks and will appear as a priority for the responsible party. Step2: The system will initiate the New Task page. Step 5: The system will accept all input and make connection to the internal server where, among other things, projects and tasks are stored and return a verification message. Step7: The system will retrieve stored information on demand. Go home Go back Sign Out This use case concludes when the project leader (owner) receives a verification message that the created task was successfully added to the project. The task has been created and assigned. Duplicate tasks will not be accepted within a project. N/A GUI to be provided for Team Assign members via a smartphone App. s will be notified of new task with a New status on tasks that a member has not viewed. N/A Tasks form Page 7

9 MAP VIEW GROUP PROJECTS CREATING AND ASSIGNING TASK Page 8

10 POST CONTENT [Swipe right to cross off task as completed] Page 9

11 DETAILED ACTIVITIES MILESTONE 2: Team Name Amen Ahmed Ali Burmester Danielle Krumm Nelson Jointer Chance Wahl Role Leader Milestone Activity Actor Glossary Use Case Glossary Use Case Diagram Use Case Narratives Detailed Activities Functional Requirements Service Request Scope Statement Statement of Work Gantt Chart System Description Results of Research Team Danielle, Ali Nelson, Chance Chance, Nelson Amen, Ali, Chance, Danielle, Nelson Danielle, Ali Danielle, Ali Amen Amen, Ali, Danielle, Chance, Nelson Amen Amen Chance, Nelson Amen, Ali, Chance, Danielle, Nelson MILESTONE 3: Team Name Amen Ahmed Ali Burmester Danielle Krumm Nelson Jointer Chance Wahl Role Leader Page 10

12 APPENDIX Functional Requirements SEARCH AND BROWSE: 1.1 The system will allow users to view multiple group projects and view corresponding tasks for each project. 1.2 The system will allow users to view completed task and due dates. 1.3 The system will allow users to view uploaded documents. SELECTION: 2.1 The system will allow registered users to join group projects. 2.2 The system will allow users select a task to view more details. 2.3 The system will allow users to select members to be assigned to particular tasks. 2.4 The system will allow users to log out of their account. ENTER INFORMATION: 3.1 The system will allow users to register and access an individual account. 3.2 The system will allow users to create a new task or new group project. 3.3 The system will allow users to mark tasks as completed. 3.4 The system will allow users to upload documents. Non-Functional Requirements OPERATIONAL: 1.1 The system can run on handheld devices. 1.2 The system can save all group members work for other group members to see. 1.3 The system should be able to work on any Web browser. 1.4 The system will function properly on the ios system. PERFORMANCE: 2.1 The application will be available 24 hours a day, 365 days a year. 2.2 The interaction between the user and the system should not exceed 2 seconds. SECURITY: 3.1 Group names and/or user IDs will be kept private and secure. 3.2 The users login information will be kept private and secure. Page 11

13 GANTT CHART Page 12