Final Report TK

Distraction Blocker
FINAL REPORT
Pankaj Karki Taimur Khan Fernando Kong Cintia Guerrero Castanon Nosipho Hlabangana
MIS 4330 SYSTEMS ANALYSIS & DESIGN | DR. DAWN OWENS | NOVEMBER 31, 2013 THE UNIVERSITY OF TEXAS AT DALLAS
Table of Contents
Page Number(s):
Executive Summary ............................................................................. 3 System Proposal .................................................................................. 4 Background & Justification ............................................................... 4 Problem Statement .......................................................................... 5 Objectives ........................................................................................ 5 Project Scope ................................................................................... 6 Functionality .................................................................................... 7 Expected Value ................................................................................ 8 Constraints ...................................................................................... 8 Project Plan (WBS) .............................................................................. 9 Requirements .................................................................................... 11 Functional Requirements ............................................................... 11 Non Functional Requirements ..................................................... 13 Structural Models .............................................................................. 15 Class Diagram ................................................................................ 15 Context Diagram ............................................................................ 16
MIS 4330 SYSTEMS ANALYSIS & DESIGN | DR. DAWN OWENS | November 31, 2013 THE UNIVERSITY OF TEXAS AT DALLAS
Behavioral Models ............................................................................. 17 Use Case Diagram .......................................................................... 17 Use Case Description ..................................................................... 18 Dynamic Models ................................................................................ 23 Sequence Diagram ......................................................................... 23 Design Documents ............................................................................. 25 User Interface Design .................................................................... 25 Control Specifications .................................................................... 30 Software Design Specifications....................................................... 32 Testing ............................................................................................... 35 Test Cases ..................................................................................... 35 Project Managament Documents ...................................................... 39 Term Meeting Minutes ................................................................. 39
Executive Summary
The purpose of this system plan is to define the need and functionality of Distraction Blocker. Schools and Universities have integrated the majority of their academics and learning processes around technology. Both high school and college students must have access to a computer and the internet for the majority of their academics. Even classes that are not completely online rely heavily on internet usage. Distraction Blocker is an application targeted towards students to aide in studying efficiently and effectively. This application will be designed to block access to all the applications and web pages which are irrelevant to the students current task. We are designing Distraction Blocker, an application focused primarily on helping students achieve a higher rate of success with their academic studies. The objective of this application is to improve the productivity of students by blocking distracting applications like social media sites, games, video players and web pages on their computer, tablet, or mobile device. The major functions and features of this application are to help students focus more on their school work and decrease the risk of distraction. This application will also reduce the risk of computer viruses by blocking irrelevant and unrelated web surfing. Distraction Blocker is currently an application that does not exist and we are hoping for it to be available in the near future.
We are designing an application focused primarily to help students achieve a higher rate of academic success. This will be done by blocking irrelevant websites, unwanted social media interferences, and other distractions students may face while using the internet for school related work.
By initiating this application a student will be restricted to focusing on information relevant to their current task. All other peripheral noise and distractions will be blocked by Distraction Blocker
Project Proposal
Background and Justification
Project Background:
Students are frequently distracted while working on academia. Distractions come from many sources. Social media presents major distractions. Unrelated web browsing generally leads to additional distraction. Third party apps such as video games can deter student efficiency. A risk of viruses and malware presents itself with unrelated wed surfing.
Project Justification:
Higher rates of efficiency can be achieved if students are able to eliminate distractions. Limiting involvement of third party apps can aide in higher rates of student efficiency. Blocking video games and social media can reduce the risk of distraction. Attempt to improve the productivity of students. Will aide in limiting unnecessary social media involvement and interferences.
Problem Statement
The following are problem statements aimed to be resolved through system implementation: Currently, too many distractions exist which negatively affect student productivity. Student productivity and efficiency is greatly deterred by many technological distractions and disruptions. High risk of distraction while using the computer for education. High risk of social media interference and unwanted involvement. Room for improved student efficiency while studying and working on academia. Numerous technological distractions deterring efficient student activities. Student efficiency is not optimized.
Objectives
The following are objectives which the system aims to complete: Increase student efficiency rate. Increase student productivity. Limit social media interference and distractions. Restrict unrelated web surfing. Limit viruses, malware, and other harmful files. Aide in efficient studying. Provide a tool which limits are restricts student distractions. Improve study time Reduce overall distractions. Create a method to reduce and remove distracting material.
Project Scope
The following statements define the project scope: The project will target students and researchers as its primary users. The system will aim to limit social media distractions. The system will aim to limit frivolous web browsing. The system will not restrict all web browsing completely. The project will aim to raise the efficiency of study time. The application will initially be implemented on desktop computers. The system will attempt to limit malware and threats from computer viruses. The system will operate within time parameters set by the user. The system will not be designed for business use. The application will serve as a tool available to students.
The project and application itself are both primarily targeted to students and researchers. Although the application may serve functionality in the business world, it is not currently within the projects scope. This is due to the numerous variables that arise in consistently changing business environments. It is also within the scope of the project to restrict web browsing, but not limit it entirely. A student will be able to access the internet for reference and research, but limitations will be placed on the sites a user will be able to visit. It is within the broad scope of the project to reach other platforms such as tablets and mobile devices, but our initial focus will be personal computers. At a later stage, once feasible, we will then attempt to broaden our project scope to cover more platforms and user devices. The primary scope of the project is to provide a tool to students which enables them to achieve higher academic success.
Functionality
The main functionality features of this application are: Block access to all distracting applications such as social media sites, games and video players. Block annoying popup and notification bubbles. Restrict the internet usage on information relevant to task at hand only. Set parameters of when to block distractions. (time/date parameters). Reduce the risk of computer viruses by blocking irrelevant and unrelated web surfing.
The main focus of Distraction blocker is to block programs and websites specified by a user. The user can also decide exactly how long and when the blocking occurs. The blocking part of the application will allow a user to control which programs or websites they are allowed to use at a specific time. The student will be able to block distracting applications such as video games, Facebook, Twitter or any other time wasting distraction. This would restrict usage to certain programs such as MS Word or others used for the task at hand. The implementation of such an application will help student to focus on what is important and prevents any distractions while they work on their school work. The application will also focus on the user being able to set a predefined parameter of when the program operates. This will define when the program runs and what it specifically blocks.
Expected Value
Expected value and benefits of project implementation: Aide students in achieving a higher rate of academic success. Eliminate distractions. Improve study time. Increase productivity rates. Lower total study time due to higher efficiency while studying without distractions. Promote constructive thinking. Block distracting applications. Restrict social media annoyance. Reduce risk of computer viruses and malware. Limit internet usage to task at hand only.
This application can be purchased with a relatively low price but great returns over time. By using this application, the student will be able to spend more time and focus on their educational work rather than wasting time and getting distracted by social media. The student would waste a great amount of time getting distracted by the social media, but using distraction blocker, the student will be able to save time on the long run and also learn how to manage their schedule and not be distracted so easily.
Constraints
Constraints that limit the project: Time limitation of less than 2 months to complete entire project. No additional resources or manpower will be allocated. Limitations in application programming resources. Human resources have other external responsibilities. Limitation in financial funding for development and implementation.
Project Schedule
Work Breakdown Schedule: Task Name
1.0 Planning
1.1 System Request 1.2 Feasibility Analysis 1.3 System Approval 1.3 Project Functionality and Scope 1.4 Project ScheduleWork Flow 1.5 Project Proposal 1.1 1.2 1.3 1.3 1.3,1.4 4 7 1 7 9 4 9/8/2013 9/12/2013 9/19/2013 9/20/2013 9/27/2013 10/6/2013 9/12/2013 9/19/2013 9/20/2013 9/27/2013 10/6/2013 10/10/2013
Predecessor
Effort
( in days)
Estimated Start Date
Estimated End Date
Assigned Resource(s)
Taimur, Pankaj Farnando, Nosipho Dr. Owens Nosipho, Taimur, Farnando, Zain Pankaj, Cinthia Taimur, Farnando Cinthia, Nosipho, Zain, Pankaj Pankaj, Farnando, Taimur, Nosipho Nosipho, Farnando, Taimur, Pankaj Nosipho, Farnando, Taimur, Pankaj
2.0 Analysis
2.1 Analysis Strategy 2.2 Requirements 2.3 Process Model 2.3.1 Use Case Descriptions 2.3.2 Use Case Diagrams 2.4 Object Behavior Model 2.4.1 Sequence Diagrams 2.5 System Proposal 2.2, 2.3 2.1- 2.4 5 2 10/24/2013 10/29/2013 10/29/2013 10/31/2013 2.2 2.2 6 4 10/17/2013 10/23/2013 10/23/2013 10/27/2013 1.5 1.5 1 5 10/11/2013 10/12/2013 10/12/2013 10/17/2013
Cinthia, Zain, Farnando, Taimur Nosipho, Zain
3.0 Design 3.1 Design Strategy 3.2 Design Architecture 3.3 UI Design 3.4 Develop Database 3.5 Program Design 3.6 System Specification 4.0 Implementation
2.5 2.5, 3.1 2.5, 3.1 3.2 3.2, 3.3, 3.4 3.1- 3.5
3 4 7 4 7 3
10/31/2013
Farnando, Cinthia, Nosipho Zain, Cinthia, Farnando, 11/3/2013 11/7/2013 Nosihpo Taimur, Pankaj, Nosipho, 11/3/2013 11/10/2013 Zain, Farnando, Cinthia Cinthia, Farnando, Zain, 11/7/2013 11/11/2013 Taimur Taimur, Pankaj, Nosipho, 11/11/2013 11/18/2013 Zain, Farnando, Cinthia 11/18/2013 11/21/2013 Pankaj, Taimur, Zain
11/3/2013
4.1 System Construction 4.2 UI Implementation 4.3 Test Cases 4.4 System Installation 4.5 Application Implementation 5.0 Post- Testing and QA Tasks
5.1 Testing 5.1.1 Performance Testing 5.1.2 Functional Testing 5.1.3 Usability Testing 5.1.4 Security Testing 5.1.5 Destructive Testing 5.2 QA Tasks 5.2.1 Support and Maintenance Plan
3.0 3.3 4.1, 4.2 4.3 4.4
7 6 3 2 2
11/21/2013 11/28/2013 11/26/2013 12/3/2013 12/6/2013 12/8/2013 12/3/2013 12/6/2013 12/8/2013
Taimur, Pankaj, Nosipho, Zain, Farnando, Cinthia Taimur, Pankaj, Nosipho, Zain, Farnando, Cinthia Taimur, Pankaj, Nosipho, Cinthia Farnando, Cinthia
12/10/2013 Zain, Nosipho
4.5 4.5 4.5 4.5 4.5
2 2 2 2 2
12/10/2013 12/10/2013 12/10/2013 12/10/2013 12/10/2013
12/12/2013 12/12/2013 12/12/2013 12/12/2013 12/12/2013
Nosipho, Zain Farnando, Cinthia Zain, Farnando Taimur, Cinthia Pankaj, Farnando
4.5
12/10/2013
12/12/2013
Taimur, Pankaj, Nosipho
10
Requirements
Functional Requirements: Requirement Name:
1) Block Preset Applications
Description:
The system must block applications that the user specified during the registration process.
2) Register User Account
The system must create, register, and store user accounts and profiles.
3) Set Distraction Timer
The system must be able to set a timer for the duration of distraction blocking.
4) Disable Distraction Timer
The system must provide a method to disable a previously set timer.
5) Log In
The application must provide users with the ability to log in to access their profile and settings.
6) Puzzle to Disable Timer
The application must present a puzzle or riddle when the disable timer option is selected.
7) Lock User Account
The system must block the user after 4 unsuccessful login attempts.
11
8) Retrieve Password
The system must be able to retrieve password verifying and accessing user's information with the provided email address.
9) Reset/Update Password
The system must be able to update or reset user's password if requested. The new password needs to be saved into the Login information of the user. The system must allow users to select and update the list of blocked applications and/or websites if needed.
10) Select/Update List of Blocked Applications and/or Websites 11) Update User Information
The system must allow the user to update any information related to their profile like name, address, phone number and email address.
12) Report of Locked Users
The system must allow the administrator to view the list of all the locked user accounts.
13) Unlock Locked Users
The system must allow the administrator to unlock locked user accounts.
12
Non - Functional Requirements: Requirement Name: Description:

The Distraction Blocker application must look attractive. It must be easy on the eyes. The themes and colors must flow together and represent the product efficiently. The application must be user friendly. Users should be able to navigate easily throughout the application. The interface must be a selling point of the application. The application must be reliable and must work at all times. There should be minimal margins of error in blocking applications using the Distraction Blocker. The Distraction Blocker application must have consistency in the theme, performance, fonts, presentation, and overall functionality of the application. The application must provide user information security along with functional security. A users information, preferences, or account may not be accessible by another user.
1) Look Attractive
2) User Friendly
3) Reliable
4) Consistent
5) Security
6) Maintainable
The application must be easy for the administrators to maintain. Maintainability involves user records and storage systems. The application must also be easy to design. Modifiable pertains to the ability to restructure the application as a whole.
7) Modifiable
13
8) Response Time
The Distraction Blocker interface must have a fast and quick response time.
9) Stability
The platform of the application and all of its relevant systems must be stable and well structured. There must be a failure management system in place in order to support application malfunctions.
10)
Failure Management
14
Structural Models
Class Diagram:
15
Context Diagram:
16
Behavioral Models
Use Case Diagram:
17
Use Case Descriptions:

Use Case 1: Register
Use Case Name: Register Primary Actor: User Stakeholders and Interests: User/Customer Register to use product. Brief Description: This use case describes how customers are able to register and create an account on the Distraction Blocker App. ID: 1 Importance Level: High Use Case Type: Essential, Internal
Trigger: User interest in product. Subflows: Optional, NONE Normal Flow of Events: 1) User clicks register. 2) User fills out the registration form. 3) User creates username. 4) User creates password. 5) User re-enters password 6) User enters email address. 7) User selects programs from list to block. 8) User saves preferences. 9) User registration complete. Alternate/Exceptional Flows: 3a) Username taken. 1. Please choose another username. 4a) If passwords dont match. 1. Please re-enter password. 5a) Invalid email address. 1. Please re-enter email address.
18
Use Case 2: Log In

Use Case Name: Log-In Primary Actor: User ID: 2 Importance Level: High
Use Case Type: Essential, Internal
Stakeholders and Interests: User/Customer Log-In to activate Distraction Blocker. Brief Description: This use case describes how customers are able to log in after registering and create an account on the Distraction Blocker App.
Trigger: Account registration complete. Application access desired.
Subflows: Optional, NONE Normal Flow of Events: 1) User clicks login. 2) User enters username. 3) User enters password. 4) User clicks submit. 5) User logs in successfully. Alternate/Exceptional Flows: 4a) Failed login. 1. Please re-enter password or username. 2. The account is locked after 4 unsuccessful login attempts. 2a. Administrator is informed about the locked account.
19
Use Case 3: Set Distraction Timer

Use Case Name: Set Distraction Timer Primary Actor: User Stakeholders and Interests: User/Customer Set / Activate timer. Brief Description: This use case describes how customers are able to set up and activate a timer after logging in and create an account on the Distraction Blocker App. ID: 3 Importance Level: High
Trigger: Application utility required. Desire to use App. Subflows: Optional, NONE Normal Flow of Events: 1) User clicks timer icon. 2) User selects hours field. 3) User selects minutes field. 4) User clicks set timer. 5) Timer activation is successfully. Alternate/Exceptional Flows: 2a) Invalid figure. 1. Please re-enter an hour from 1-12 am/pm. 3a) Invalid figure. 1. Please re-enter minutes from 0-60 min. 5a) Unable to set timer. 1. Please double check hours and minutes format.
20
Use Case 4: Deactivate Distraction Timer
Use Case Name: Deactivate Distraction Timer Primary Actor: User Stakeholders and Interests: User/Customer Remove / Deactivate timer.
ID: 4
Importance Level: High
Brief Description: This use case describes how customers are able to deactivate an activate timer on the Distraction Blocker App.
Trigger: Halt in application utility required. Desire to stop usage App. Subflows: Optional, NONE Normal Flow of Events: 1) User clicks timer icon. 2) User clicks stop timer. 3) User completes math/puzzle problem. 4) Timer deactivation is successfully. Alternate/Exceptional Flows: 3a) Incorrect answer. 1. System recycles new question. 1a. System allows maximum of 10 attempts, if unsuccessful the deactivation of timer is rejected.
21
Use Case 5: Maintain System
Use Case Name: Maintain System Primary Actor: System Administrator Stakeholders and Interests: System Administrator Maintain system operation
ID: 5
Importance Level: High
Brief Description: This use case describes how System Administrators are able to access their role to maintain the Distraction Blocker App.
Trigger: Desire to maintain application Subflows: Optional, NONE Normal Flow of Events: 1) Admin enters username 2) Admin enters password 3) Admin selects submit 4) Successful Administration Login 5) Admin can view files, table, accounts, etc. Alternate/Exceptional Flows: 4a) Failed login. 1. Please re-enter password or username.
22
Dynamic Models
Sequence Diagrams:
Registration Process:
23
Log In Process:
24
Design Documents
User Interface Design
The following images depict a systematical flow of Distraction Blockers graphical user interface design:
25
26
27
28
29
Controls Specification
The following section will determine controls beneficial to the functionality and operations of Distraction Blocker: Control Mechanisms to Implement: User Interface Control: The input field for email address must have a @ sign for login. Interface control: The email address control mechanism will be utilized at login screens and when users are registering for service from Distraction Blocker. This control mechanism will search and detect for a @ sign as user input within he login and registration field of email. If there is no @ sign t he system must employ its control mechanism to display an invalid email address error. This user interface control mechanism will allow for detection of incomplete, or errors within the email input text boxes.
Business Rule Control: A user must select a valid user name and a password to uniquely identify their account. This username/email address can only be associated with one account. This business control mechanism will employ a control method that ensures a user has a valid user name and password associated specifically to their account. If a user does not have a registered user name and an associated password, they must first complete the registration process in order to bypass this business rule control. The role and functionality of this business rule control is to ensure that all users of Distraction Blocker have registered prior to using the application. This will allow for the limitation of product use by registered customers of Distraction Blocker.
30
Flow Logic Control: Invalid username or password. This flow logic control will provide us the ability to ensure that invalid username and password entries are managed appropriately. If a user of the distraction blocker mistakenly enters an incorrect username or password, this flow logic control will redirect the users to a Login Error screen. Within this secondary screen, a user may retry entry of their user name and password until successful access to Distraction Blocker is attained. An additional variable of this control is to limit users to three input submissions prior to temporarily locking the account. This flow logic control will allow users the ability to reenter their user name and password in case of accidental errors during the entry process.
31
Software Design Specification

The following section will present three software design scenarios and their functionalities in detail:
Method Name: addInformation
Class Name: User
Description of Responsibilities:Updates the users profile with additional information. Arguments Received: anInformation userID Return Value: informationResult Message and Example: addInformation (userID, anInformation):Boolean informationResult = addInformation (2,userProfile) Algorithm Specificiation: If information is not null then Add the information to the Users Profile Insert the information into the database Return true Else Return False Data Type: Information Object Integer Data Type: Boolean
32
Method Name: addTimer
Class Name: User
Description of Responsibilities: Set/activate timer for the duration of distraction blocking Arguments Received: aTimer UserID Data Type: Application Timer Integer
Return Value: timerActivated
Data Type: Boolean
Message and Example: addTimer(userID,aTimer) timerResult=( Hours:Mins, 1:15)
Algorithm and Specification: If timer is not null then
Add timer to User Profile
Insert the timer into the database
Return true
Else Return False
33
Method Name: addBlock
Class Name: User
Description of Responsibilities: Implement an addition of a new app being blocked to an existing user. Arguments Received: aBlock userID Return Value: appBlocked Message and Example: addBlock (userID, aBlock) blockResult = addblock (2407068,Facebook) Algorithm Specificiation: If block is not null then Add the block to Potential Block List Insert Block into the database Return true Else Return False Data Type: Application Block Integer Data Type: Boolean
34
Testing
Test Cases
The following section will present three test case scenarios and their functionalities in detail.
Purpose: To ensure that there are no errors when blocking an application. Prereq: User must e xist and must be logged in. Test Data: userID= {Valid userID, invalid userID, empty} blockedapplicationID = { valid blockedapplicationID, invalid blockedapplicationID, empty} Steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. Visit application list Choose applications from list Confirm application list Click agree Choose time period blocked Confirm time Click submit button See Blocked list Verify that all chosen applications are blocked. Expected Output Expected to open application list Expected to add applications Expected to confirm application list Expected to agree to application list Expected to return to home page Expected time period to come up Expected to confirm time Expected to submit time Expected to return to home page Expected to block applications listed Expected that applications blocked appears Remarks Unable to block application
Test Input Enter Application List Click wanted applications to be blocked Click confirm application list Click agree Click disagree Click time period Click confirm time Click submit time Click cancel time Click blocked list Click chosen applications blocked Test Results: Date 11/15/2013
Pass/Fail Fail
35
11/15/2013 11/15/2013
Fail Pass
Unsuccessful agree selection All parameters are correct
Purpose: To check if the activation of timer is functional and done in accepted format and parameters.
Prerequisites: User must be registered. Timer must be set.
Test Data: userID= {Valid userID, invalid userID, empty} timerapplicationID = { valid timerapplicationID, invalid timerapplicationID, empty}
Steps: Steps to Carry Out Test Procedure 1. 2. 3. 4. 5. 6. 7. 8. Visit Application Click on TImer Select Hours Field Select Minutes Field Choose time period blocked Confirm timer Click submit button to set timer Timer activation is successful Test Input Enter Application List Click on Timer Set hours outside permitted parameters Set minutes outside permitted parameters Click submit to set timer with permitted parameters Click cancel after confirming timer Expected Output Expected to open application list Expected to open timer application Expected not to activate timer and prompt the user to try again Expected not to activate timer and prompt the user to try again Expected to activate timer without errors and show activation message Expected to return to home page
36
Test Results:
Date 11/13/2013 11/15/2013 11/19/2013 Fail Pass Fail
Pass/Fail
Remarks Hours outside parameter All entries within parameter Minutes entry outside of parameter
Purpose: Testing if the user can login into the system without any errors. Prerequisites: User has already made an account and has all the user information in the database Test Data: userID = {Valid userID, invalid userID, valid email, invalid email, empty} password = {valid, invalid, empty}
Steps: Steps to carry out the test. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Enter the application Enter the wrong userID Enter the wrong password Click LogIn without UserID Click LogIn without a password Click login with the correct information See the loading screen See the information and the agreement to use the application Click the agree button Click the disagree button See the personal profile Verify that welcome message is associated to the correct username Expected Output Expected to open the application Expected not to enter the application and tell the user to try again. Expected not to enter the application and prompt the user to try again.
Test Input STEP 1. Enter the application. STEP 2. Click login with wrong userID. STEP 3. Click login with wrong password.
37
STEP 4. Click login without userID.
Expected not to enter the application and prompt the user to enter missing information. Expected not to enter the application and prompt the user to enter the missing information. Expected to enter the application without errors. Expected to show a loading screen without errors. Expected to show the information and agreement page with the correct information. Expected to direct to the personal profile and view the welcome message. Expected to return to the login screen.
STEP 5. Click login without a password.
STEP 6. Click login with the correct information. STEP 7. See the loading screen.
STEP 8. See the information and the agreement to use the application. STEP 9. Click agree for the agreement page. STEP 10. Click disagree for the agreement page. STEP 11. See the personal profile.
Expected to show the personal profile with the correct username. Expected to show a welcome message with the correct username.
Step 12. Verify that welcome message is associated to the correct username.
Test Results: 11/01/13
Date Pass
Pass/Fail
11/07/13
Pass
11/14/13
Fail
11/18/13
Pass
Remarks The adblock application is updated as soon as an user login. The adblock application is updated as soon as a new user registers. Power outage, the adblock database could not be updated. The adblock database is updated every hour.
38
Project Management Details
Team Meeting Minutes:

Meeting Number
1
Meeting Date
Tuesday, September 24th
Time Start
6:00 PM
Time End
7:35 PM
Members Present
Pankaj, Taimur, Farnando, Zain, Cinthia, Nosipho
Objectives Discussed
- Basic project ideas. - Background and functionality. - Developed mission statement. - Discussed memo assignment - Discussed project scope. - Defined expected value.
Other Notes
- Assigned memo assignment responsibilities.
Friday, September 27th
4:00 PM
7:00 PM
Pankaj, Taimur, Farnando, Zain, Cinthia, Nosipho
- Assigned project schedule development roles.
Tuesday, October 1st Tuesday, October 8th
6:00 PM 7:00 PM
9:00 PM 9:00 PM
Pankaj, Taimur, Farnando, Cinthia, Nosipho Pankaj, Taimur, Farnando, Cinthia, Nosipho
- Developed project schedule. - Discussed systems proposal assignment - Comprised proposal information -Created system proposal document - Revised project scope - Structured project work schedule
- Assigned system proposal assignment responsibilities. - Finalized system proposal assignment document.
39
Meeting Number
5
Meeting Date
Tuesday, October 15th
Time Start
1:00 PM
Time End
2:30 PM
Members Present
Pankaj, Taimur, Fernando, Cintia, Nosipho
- Basic presentation discussion. - Discussion of Milestone 3 - Division of roles and assignment for project preparation. - Division of roles and assignment for milestone 3 - Discussed findings for milestone 3 - Discussed findings for project presentation. - Complied research and findings for milestone 3. - Compiled work for milestone 3 - Complied work for presentation. - Discussed further goals and things still left to do. - Complied milestone 3 work and information. -Created presentation. - Complied milestone 3 work and information. - Finalized milestone 3 assignment.
Other Notes
- Assigned milestone 3 assignment responsibilities. - Assigned project presentation responsibilities.
Thursday, October 17th
9:00 PM
10:00 PM
- Assigned project schedule. - Continued to work on milestone 3 responsibilities. - Assigned further milestone 3 assignment responsibilities.
Saturday, October 19th
12:00 PM
3:00 PM
Tuesday, October 22th
2:00 PM
4:00 PM
Pankaj, Taimur, Farnando, Cintia, Nosipho
Monday, October 28th
12:00 PM
2:00 PM
- Finalized presentation assignment. - Assigned further milestone 3 responsibilities. - Finalized milestone 3 assignment.
40
Meeting Number
10
Meeting Date
Tuesday, November12th
Time Start
12:00 PM
Time End
2:30 PM
Members Present
- Basic milestone 4 discussions - Division of roles and responsibilities for Milestone 4 - Initiation of Milestone 4
Other Notes
- Began work collectively on Milestone 4 - Delegated responsibilities.
11
Friday, November,15th
1:00 PM
3:00 PM
- Compiled works to date. - Addressed areas of concern and uncertainty - Peer reviews works and milestone efforts -Assigned final roles and determined finishing responsibilities - Compiled work for milestone 4 - Formatted milestone 4 document. - Discussed areas of concern and uncertainties. - Finalized Milestone 4
- Continued to work on milestone 4 responsibilities. - Determined milestone completion deadline
12
Tuesday, November 19th
2:00 PM
3:30 PM
- Completed Milestone 4
41

Final Report TK

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Final Report TK

Încărcat de

Drepturi de autor:

Formate disponibile

Distraction Blocker

Estimated Start Date

Estimated End Date

Cinthia, Zain, Farnando, Taimur Nosipho, Zain

3.0 3.3 4.1, 4.2 4.3 4.4

11/21/2013 11/28/2013 11/26/2013 12/3/2013 12/6/2013 12/8/2013 12/3/2013 12/6/2013 12/8/2013

12/10/2013 Zain, Nosipho

4.5 4.5 4.5 4.5 4.5

12/10/2013 12/10/2013 12/10/2013 12/10/2013 12/10/2013

12/12/2013 12/12/2013 12/12/2013 12/12/2013 12/12/2013

Taimur, Pankaj, Nosipho

2) Register User Account

3) Set Distraction Timer

4) Disable Distraction Timer

The system must provide a method to disable a previously set timer.

6) Puzzle to Disable Timer

7) Lock User Account

12) Report of Locked Users

13) Unlock Locked Users

Non - Functional Requirements: Requirement Name: Description:

Use Case Descriptions:

Use Case 2: Log In

Use Case Type: Essential, Internal

Trigger: Account registration complete. Application access desired.

Use Case 3: Set Distraction Timer

Use Case Type: Essential, Internal

Use Case 4: Deactivate Distraction Timer

Importance Level: High

Use Case Type: Essential, Internal

Use Case 5: Maintain System

Importance Level: High

Use Case Type: Essential, Internal

Software Design Specification

Method Name: addInformation

Class Name: User

Method Name: addTimer

Class Name: User

Return Value: timerActivated

Data Type: Boolean

Message and Example: addTimer(userID,aTimer) timerResult=( Hours:Mins, 1:15)

Algorithm and Specification: If timer is not null then

Add timer to User Profile

Insert the timer into the database

Else Return False

Method Name: addBlock

Class Name: User

Unsuccessful agree selection All parameters are correct

Prerequisites: User must be registered. Timer must be set.

Date 11/13/2013 11/15/2013 11/19/2013 Fail Pass Fail

STEP 4. Click login without userID.

STEP 5. Click login without a password.

Test Results: 11/01/13

Project Management Details

Team Meeting Minutes:

Friday, September 27th

Pankaj, Taimur, Farnando, Zain, Cinthia, Nosipho

- Assigned project schedule development roles.

Tuesday, October 1st Tuesday, October 8th

Thursday, October 17th

Pankaj, Taimur, Fernando, Cintia, Nosipho

Saturday, October 19th

Pankaj, Taimur, Fernando, Cintia, Nosipho

Tuesday, October 22th