DCR ARB Presentation. CS577a Fall 2015 Team 2

Transcription

1 DCR ARB Presentation CS577a Fall 2015 Team 2 -Sultan Alsarra -Aref Shafaeibejestan -Adil Cem Albayrak -Mohammad Almunea -Charles Reitz -Julapat Julnual -Andrea Brown -Travis Weaver

2 Outline 2 :: Remote Team Members :: Operational Concept Description :: Win Win Agreements/Requirements :: Architecture :: Prototype :: Life Cycle Plan :: Feasibility Evidence :: QFP

3 3 Remote Team Members

4 Team s Strengths 4 Operational View Technical View Quality product/project is shared goal Some team members have experience in ios development 5 members have identical class schedules, so meeting is easier At least one team member is an experienced web developer 8 team members is more than typical Several members taking 571 (Web Technologies)

5 Team s Weaknesses 5 Operational View Technical View Solutions Team formed out of desire to work with others who will take 577b, rather than skills or cohesion Only a member or two have experience with backend server/db mgmt, config, security, etc. Skill range is incidentally broad Only a couple members (out of 8) with experience in app development One member is taking 585 and others have taken at least a DB course in their undergraduate studies. Back-end work should be less than front-end Experienced app developers can spend more time teaching the rest

6 Technical Concerns & Solutions 6 :: Minimal experience developing front to back solution. Mitigation Combine team member front- and back-end experiences to work together to design communication between application and server. :: Data Upload/Download size Mitigation Found Objective-C and PHP methods to compress.jpg images

7 7 Testing Strategy and Test Cases

8 Testing Strategy :: Approach Test the most critical requirements in win-win conditions Mitigate the risks :: Strategies Unit test : interface, classes Integration test : subsystems Functional test : use case scenarios

9 Test Cases for Event Management TC-01 Create Events TC-02 Search Events TC-03 Delete private event TC Create public event TC Create private event

10 Test Cases for Picture Management TC-04 Post pictures TC-05 Sort pictures TC Take a picture and post it in an event TC Sort pictures by date TC Take a picture and post it in nearby location TC Sort pictures by popularity TC Choose a picture from gallery and post it in an event TC Sort pictures by distance TC-06 Browse pictures TC-07 Delete pictures TC-08 Report pictures TC Browse pictures in public event TC-09 Save picture to device TC-10 Like/unlike picture TC Browse pictures in private events TC Browse pictures in nearby location

11 Test Cases for Profile Management TC-11 Register TC-12 Login TC Register with TC Login with TC Register with Facebook TC Login with Facebook TC-13 Logout

12 Test Cases for Admin Management TC-14 Browse users TC-15 Suspend a user TC-16 Update an event TC-17 Restore reported picture TC-18 Change app settings TC-19 Generate statistics report TC-20 Search pictures TC-21 Delete events

13 Example Test Case - 1 (Sunny Day) Test Case Number TC Check uploading picture to nearby with correct information Test Item Uploading picture is tested with all data expected. Test Priority M (Must Have) Pre-conditions A picture is taken by the user in the app Post-conditions The picture and metadata are uploaded successfully, and success is indicated to the user 1. Take Picture 2. Click Post to Nearby Picture is posted to nearby successfully message is shown Input Specifications Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability Pass Criteria: This test will pass when all of the following conditions are met. The picture is uploaded correctly The picture is written to nearby in the database The user is shown success Fail Criteria: Other than pass criteria The user device has a camera The user device is connected to the internet The user device has accessible GPS data N/A WC_3580: As a user, I can take many pictures to introduce my geo-location, so the tourists using the app will search the location and see what s there.

14 Example Test Case - 2 (Rainy Day) Test Case Number TC Check saving picture without enough space on device Test Item Saving picture is tested without enough space on device Test Priority M (Must have) Pre-conditions The user is viewing a picture Post-conditions Input Specifications 1. The picture is not saved to the user s device 2. Appropriate error message is shown on the screen The user clicks the download button on the screen Expected Output Specifications Not enough space on device message is shown Pass/Fail Criteria Pass Criteria: The test is passed when meet all the following conditions are met Appropriate error message is shown The picture is not saved to device Fail Criteria: Other than pass criteria Assumptions and Constraints The user has not enough space to save the picture on the device The device has Internet connections N/A Dependencies Traceability WC_3623: As a user, I can save one or many pictures from an event/hashtag to my phone so that I can keep the photos after the event/hashtag expires

15 Example Test Case - 3 (Rainy Day) Test Case Number TC Check login by using without internet connection or system is down Test Item Test Priority Login using is tested with ( /password) and no internet connection or system is down M (Must have) Pre-conditions The system displays the form for the /password pair Post-conditions The system gives error message for a connection failure Input Specifications 1. Enter the and password 2. Click Log in Connection failure message is shown Clear up the password field Pass Criteria: The test is passed when meet all the following conditions are met. The alert message is shown correctly. Clear the password field and no changes to the field. Fail Criteria: When the pass criteria is not met. Both fields /password are filled The device is not connected to the internet or the system is down N/A Expected Output Specifications Pass/Fail Criteria Assumptions and Constraints Dependencies Traceability WC_3584: As a user, I can login to the application using my registered username or my Facebook account, so I can use the application with my own profile.

16 16 Operational Concept Description

17 System Purpose 17 The primary purpose: Make sharing picture easier! Introduce new methods: Location Based Event Based

18 Program Model 18 Assumptions: People are willing to share their pictures. People have smartphones with camera and Internet connection. Stakeholders (Who is accountable for the initiatives) Maintainers Administrators Developers Users Owner Cost (cost factors) Development Cost Maintenance Cost Advertising COTS (server,..) Initiatives (What to do to realize benefits) Design & Develop the new system Marketing campaign Proper Training and knowledge transfer Maintain the System Survey and User Testing Value Propositions (Benefits i.e Why) Increase efficiency of sharing pictures. Improve user experience by allowing users to create/post different types of events (public, private, location). Easier picture sharing options. Beneficiaries (Who derives value) Users Owner Benefits Increase number of users on the app. Increase number of events.

19 Benefit Chain Diagram 19

20 20 System Boundary & Environment

21 Core Capabilities 21 Capability Goals Priority Level OC-1 Use Hashtag: User can post pictures with a hashtag that indicates a public event Must Have OC-2 Login with Facebook: User can login using Facebook. Must Have OC-3 Use Location: User can post pictures to the nearby location Must Have OC-4 Search Events: User can search events by their name (hashtag). Must Have OC-5 Browse Event s Pictures: User can browse pictures associated with an event and sort them by like or date. Must Have OC-6 Administrator: Admin can control and supervise user s content. Must Have OC-7 Delete Picture: Users can delete pictures that they posted. Users can also delete pictures of their private events. Should Have OC-8 Create/Delete Private Event: User can create/delete a private event that only people with password has access to it. Should Have OC-9 Like/unlike Picture: Users are able to like/unlike a picture Could Have OC-10 Report Picture: Users are able to report inappropriate pictures. Could Have OC-11 Choose Add Picture Type: When user create a private event they can choose if users can upload pictures, or only post pictures captured live. Could Have OC-12 Take Picture or Choose from Gallery: Users can decide whether to take a photo or choose it from gallery when adding a picture. Could Have OC-13 Save Picture to Device: User can save the picture to his/her own device. Could Have

22 Goals and Constraints 22 Organizational Goals: OG-1: Simplify sharing pictures from smart phones OG-2: Share location based pictures OG-3: Share public and private hashtags with friends and families OG-4: Increase efficiency of sharing pictures OG-5: Improve user experience by allowing users to create/post different types of events (public, private, location) Constraints: CO-1: ios as an Operating Systems: The new system should work on ios CO-2: Facebook Login: The user should be able to use the application using his Facebook credentials CO-3: Zero Monetary Cost: The Chosen NDI/NCS must be free CO-4: Linux as an Operating System: the available back-end server is linux CO-5: Free Database System

23 23 Win Win Agreements Win Win Agreements

24 Win Win Agreements Event Management Status Win Condition Description SAME WC_3579 As a user, I can use a hashtag for a picture taken in a special event such as a basketball game, so the people miss the event will see what they missed. SAME WC_3585 As a user, I can reserve my event's hashtag for a limited time (one week), so I and event attendees can use the hashtag to post pictures of the event. SAME WC_3603 As a user, I can shut down my own event, so that I can remove my event and all pictures in the event before reserved time is up. SAME WC_3621 As a user, I can set up a private event that only invited people can see and access via password, so that I can ensure only the people I want to participate may participate. SAME WC_3627 As a user, I can save the hashtags to save time searching for them later and see my history of hashtags. NEW WC_3763 As a user, I can create a public/private event without posting a picture in it, so that I can reserve the hashtag before the event starts.

25 Win Win Agreements Picture Management Status Win Condition Description SAME WC_3580 As a user, I can take many pictures to introduce my geo-location, so the tourists using the app will search the location and see what s there. SAME WC_3591 As a user, I can delete pictures that I took, so they are no longer accessible. SAME WC_3599 As a user, I can report any inappropriate picture, so that it will be removed from the event. SAME WC_3600 As a user, I can moderate the pictures in an event that I created, so that pictures that I don't like will be removed from the event. SAME WC_3619 As a user, I can take a photo from the PicShare app or choose a picture from my gallery, so that I can take a picture from another app.

26 Win Win Agreements Picture Management (2) Status Win Condition Description SAME WC_3623 As a user, I can save one or many pictures from an event/hashtag to my phone so that I can keep the photos after the event/hashtag expires. SAME WC_3634 As a user, I can choose if users can upload pictures, or only post pictures captured live, which would give me more control over content in my private events. UPDATED WC_3637 As a user, I can sort pictures in events by date or popularity, and I can sort pictures in location by distance, date or popularity, so that I can have more control over picture viewing. SAME WC_3751 As a user, I can like a picture.

27 Win Win Agreements Picture Management (3) Status Win Condition Description NEW WC_3760 As a user, I can post only captured live pictures to nearby location, so that all the pictures will be from that area. NEW WC_3761 As a user, I can choose the radius for browsing pictures in nearby locations, so that I can view the ones closest to me. NEW WC_3762 As a user, I can write a caption for the pictures before posting them, so that my pictures will be more descriptive.

28 Win Win Agreements Profile Management Status Win Condition Description SAME WC_3583 As a user, I can create my login with specific username and password or Facebook account, so I can use them to login to the application. SAME WC_3584 As a user, I can login to the application using my registered username or my Facebook account, so I can use the application with my own profile.

29 Win Win Agreements Admin Management Status Win Condition Description NEW WC_3764 As an admin, I can login into my administrative page with my password and username, so that I can perform admin features. NEW WC_3765 As an admin, I can browse users of the app and view pictures that they posted, so that I can manage users and their contents. NEW WC_3766 As an admin, I can suspend a user, so that I can have more control over users. NEW WC_3767 As an admin, I can list pictures by all, location, event or report count, so that I will have more control over pictures. NEW WC_3768 As an admin, I can delete pictures from the system, so that I will have more control over pictures. NEW WC_3769 As an admin, I can create an event hashtag, so that I can reserve it.

30 Win Win Agreements Admin Management (2) Status Win Condition Description NEW WC_3770 As an admin, I can update an event, so that I can change the event's name or expiration date. NEW WC_3771 As an admin, I can delete events with all their pictures, so that I can have more control over events. NEW WC_3772 As an admin, I can change the system settings such as report count threshold and picture lifetime, so that I can have more control over the system configurations. NEW WC_3773 As an admin, I can generate reports regarding events, users and pictures, so that I can have more information about the system. NEW WC_3774 As an admin, I can restore pictures that has been marked inappropriate, so that I have better control over the pictures.

31 31 Architecture Architecture

32 Top Level Physical Architecture 32

33 Top Level logical Architecture 33

34 Use Case Diagram 34

35 Use Case List 35 # Use Case Name # Use Case Name UC-1 Login UC-13 Save Picture to Device UC-2 Logout UC-14 Browse Event s Pictures UC-3 Register UC-15 Sort Pictures UC-4 Create Private Event UC-16 View Nearby Pictures UC-5 Delete Event UC-17 Create Public Event UC-6 Search Events UC-18 Browse Users UC-7 Add Picture UC-19 Suspend User UC-8 Delete Picture UC-20 Update Event UC-9 View Specific Picture UC-21 Search Pictures UC-10 Like Picture UC-22 Restore Reported Pictures UC-11 Unlike Picture UC-23 Change App Settings UC-12 Report Picture UC-24 Generate Statistics Report

36 Hardware Component Diagram 36

37 Software Component Diagram 37

38 Artifact and Information Diagram 38

39 Class Diagram 39

40 Sequence Diagram - Report Picture 40

41 Sequence Diagram - Register with Facebook 41

42 Sequence Diagram - Create Events 42

43 Entity Relationship Diagram 43

44 44 Prototype

45 Prototype 45 :: Server side event management :: User Interface (mockup) :: User Interface (ios) :: User Interface (admin)

46 Prototype : Server side event management 46 Why? :: Limited experience in building an end-to-end system: back-end server to front-end application Mitigation :: Algorithms :: Hostgator Implementation

47 Prototype : Server side event management 47 Get Nearby List Get Nearby Image

48 Prototype : Server side event management 48 Post to Event

49 Prototype : Server side event management 49 Live Demo

50 Prototype : User Interface (mockup) 50 Progress :: Update the prototype regarding to Prototype Progress Presentation s comment :: Update the prototype regarding to Owner s comment

51 Prototype : User Interface (mockup) 51 Explore - Event Screen :: Change + to Create Event :: Add pre-populated # before event input :: Add Input private event s password popup

52 Prototype : User Interface (mockup) 52 Explore - Nearby (Filter & Sort) :: Change some wordings

53 Prototype : User Interface (ios) 53 Progress :: Create explore screen with back-end integration :: Create photo screen with back-end integration

54 Prototype : User Interface (ios) 54

55 Prototype : User Interface (ios) 55

56 Prototype : User Interface (ios) 56

57 Prototype : User Interface (ios) 57 Live Demo

58 Prototype : User Interface (admin) 58 Reason for Prototype: It s a new feature requested by the owner, and he considers it very important, which makes it a high priority item that needs prototyping. Features requested: :: User Management :: Event Management :: Picture Management :: Configurations :: Statistical Reports

59 Prototype : User Interface (admin) 59 Progress :: Reviewed by Owner :: Changed some features based on Owner s feedback :: Uploaded on hostgator

60 Prototype : User Interface (admin) 60 Live Demo

61 61 Life Cycle Plan

62 Life Cycle Plan 62 Purpose: Managing the project team while they work on each phase of the project s life cycle. Development Strategy: Architected Agile. Duration: Two Semesters (24 weeks) Team: Consists of 8 team members. Assumptions: All team members will be registered in 577B; No new team members.

63 Life Cycle Plan 63 Let s Meet The Team: Member Strengths Rigo THE MAN!! Aref Architecture, UML Modeling, Backend Development Adil Requirements Engineering, UML Modeling, Backend Development Mohammad Operational Concept Engineering, Database, Backend Development Jul App Development Charles App Development Travis Quality Focal Point, IIV&V Andrea Feasibility Analyst, IIV&V Sultan Management, Life Cycle Planner, QA

64 Life Cycle Plan 64 Re-Baselined Foundations Phase: Duration: From 1/15/16 to 2/19/16 Activities: Re-baseline Project Status Prepare for Development Phase Plan for Testing Milestones: Re-Baselined Development Commitment Review Re-Baselined Development Commitment Package

65 Life Cycle Plan 65 Development Phase: Duration: From 1/26/16 to 5/2/16 Activities: Construction Iteration 1 (Core Capabilities) Construction Iteration 2 (Full Capabilities) System Transition Milestones: Core Capability Drivethrough Transition Readiness Review Operation Commitment Review Operation Commitment Package

66 66 Project Plan - Re-Baselined Foundations Phase

67 Project Plan - Development Phase 67

68 Life Cycle Plan 68 Artifact deliverable in Re-Baselined Foundations Phase : Artifact Due date Format Medium Every Monday website Jira Progress Report Biweekly.xls Soft copy Project Plan Biweekly.mpp Soft copy Re-Baselined Development Commitment Review Presentation Fri 2/12/2016.ppt,.pdf Soft copy Re-Baselined Development Commitment Package Fri 2/19/2016.pdf Soft copy Jira

69 Life Cycle Plan 69 Artifact deliverable in Development Phase: Artifact Due date Format Medium Every Monday website Jira Progress Report Biweekly.xls Soft copy Project Plan Biweekly.mpp Soft copy Core Capability Drivethrough Presentation Fri 3/25/2016.ppt,.pdf Soft copy Transition Readiness Review Presentation Fri 4/8/2016.ppt,.pdf Soft copy Installation and Transition Mon 4/18/2016.ipa,.pdf Software, Softcopy Operation Commitment Review Presentation Mon 4/25/2016.ppt,pdf Softcopy Operation Commitment Package Mon 5/2/2016.pdf Softcopy Jira

70 Life Cycle Plan 70 Project Scale Factors: Scale Driver Value Rationale Precedentedness (PREC) Low Most of the team is not familiar with mobile app development. Only two of the eight members have developed mobile apps before. Development Flexibility (FLEX) High Owner is flexible and open to input and suggestions from team members and wishes general conformity with his requirements. Risk Resolutions (RESL) High Risk Elimination is feasible for project and most can be mitigated by buying information and prototyping such as the Facebook API. Team Cohesion (TEAM) Very High Team chemistry is very good with seamless interactions and communications between members. Members also are highly cooperative and have a good understanding of the project. Process Maturity (PMAT) NOM Team has an okay understanding of CMM Maturity but has no expertise.

71 Life Cycle Plan 71 PicShare App Modules Used for Estimation: No Module Description SLOC (estimation) REVL (estimation) 1 Picture Module The system will provide the user the ability to share pics to locations or event. Also allows to add picture to hashtag and write a caption for it. This has most features of the system which explains the large number of SLOC 2,468 10% 2 Browse Module This module provides the user the ability to browse pictures in events or locations and sort them. Has some location and distance algorithms but less features than picture module 1,943 10% 3 Profile Module The system that allow users to register with their and password and login %

72 Life Cycle Plan 72 COINCOMO Estimate for ios App:

73 Life Cycle Plan 73 Estimation: Number of SLOC: 5041 Effort needed (Pessimistic): person-month Each Member Works: 18hrs/week for 12 weeks of development Total Time Spent by Members: A: 18 hrs/wk 8 members 4 weeks = 576 hrs/month B: 18 hrs/wk x 8 members x 12 weeks = 1728 total hours Number of time Needed: A: (11.18 person-month 152 hrs/person-month) 576 = 2.9 months B: person-month x 152 hrs/person-month = 1699 total hours Is it possible: Yes, for one application, since it will take us 2.9 months or 12 weeks to finish (1728 hrs> 1699 hrs) and that s in the worst case scenario.

74 Iteration Plan 74 The Plan: The construction iteration of the Development phase will be divided into two cycles: 1. Construction Iteration 1 (Core Capability): The core capabilities of the system are developed and tested. Purpose is to make sure the most important core features of the app are ready for the Core Capability Drivethrough 2. Construction Iteration 2 (Full Capability): Any problems with core functionality will be addressed. Full capability are developed and tested

75 75 Construction Iteration 1 (Core Capabilities) To Be Developed Developer Tester Charles, Aref Andrea Jul, Mohammad Andrea Charles, Jul, Mohammad Andrea OC-4 Search Events: User can search events by their name (hashtag). Charles, Jul, Adil Travis OC-5 Browse Event s Pictures: User can browse pictures associated with an event and sort them by like or date. Charles, Jul, Aref Travis OC-6 Administrator: Admin can control and supervise user s content. Charles, Jul, Adil Sultan OC-7 Delete Picture: Users can delete pictures that they posted. Users can also delete pictures of their private events. Charles,Jul, Mohammad Sultan OC-8 Create/Delete Private Event: User can create/delete a private event that only people with password has access to it. Charles,Jul Travis OC-12 Take Picture or Choose from Gallery: Users can decide whether to take a photo or choose it from gallery when adding a picture. Aref, Adil Sultan OC-1 Use Hashtag: User can post pictures with a hashtag that indicates a public event OC-2 Login with Facebook:User can login using facebook OC-3 Use Location: User can post pictures to the nearby location

76 76 Construction Iteration 2 (Full Capabilities) To Be Developed OC-9 Like/unlike Picture: Users are able to like/unlike a picture OC-10 Report Picture: Users are able to report inappropriate pictures. OC-11 Choose Add Picture Type: When user create a private event they can choose if users can upload pictures, or only post pictures captured live. OC-13 Save picture to Device: User can save the picture to his/her own device. Developer Tester Charles,Jul,Aref Andrea Charles,Jul,Mohammad Travis Charles,Jul,Adil Sultan Charles,Jul,Mohammad Sultan

77 77 Feasibility Evidence

78 78 Major Risks

79 Major Risks 79 Risk Exposure Risk Description Risk Mitigation Potential Magnitude Probability Loss Risk Exposure Inaccurate understanding of software requirements Meet owner with specific questions. Prototype, 6 verify win conditions with owner, and create OCD 8 48 Requirements Changes Design to cost, incremental development Server Side Management Technology Ambiguity +4 Self-learning, knowledge transfers, prototyping, and incremental development Unrealistic Schedule and Budget +5 Feasibility analysis, project planning, design to cost, and incremental development Development Commitment Review new Improve presentation skills and dry run presentations Personnel Shortfalls -3 Lack of experience in developing mobile apps

80 Major Risks (cont.) 80 Risk Exposure Risk Description Risk Mitigation Potential Magnitude Probability Loss Risk Exposure Gold Plating -3 Prototyping, designing to cost, incremental development Lack of Involvement by SuccessCritical-Stakeholders -3 Proper communication and dialog with owner, incremental development, weekly updates System Design Interface and HCI issues -3 Prototyping, incremental development, regular feedback from owner Human-System Integration Shortfalls -2 Prototyping, incremental development, surveys, interviews Architecture/Reuse/NonDevelopment Item conflict -1 Prototyping, incremental development, research of API and its SDK

81 81 Business Case Analysis

82 Personnel Costs 82 Activities Time Spent (Hours) Valuation and Foundation Phases: Time Invested (CS577a, 12 weeks) Owner: 2 Win win sessions 3 Owner: Meeting via , phone call, and other means [1hr/wk * 12wks * 1 person] 12 Architecture Review Boards [1.5 * 2 times * 1 person] 3 Re-Baseline, Development and Operation Phases: Time Invested (CS577b, 12 weeks) Owner: Meeting via , phone calls, and other means [1hr/wk * 12wks * 1 person] ARBs, Transition Readiness, and Core Capability Drive-through session [1.5hrs * 4 times * 1 person] Deployment of system in operation phase and training Installation and deployment [3hrs * 2 times * 1 person] Training and support [2 hrs * 2 times * 1 person] Maintenance Period (52 weeks) Maintainer: 4 hours * 52 weeks per year 208 Total Worth ($15/hour) 250 $3750

83 Hardware and Software Cost 83 Type Cost Rationale Hardware cost (HostGator) $160/month owner-chosen hosting for development on a Linux server. Development cost $99/year Apple Developer Account Ownership cost $99/year

84 Benefit Analysis (in hours) 84 Current activities and resources used % Reduce Time Saved (Hours/Year) Sharing pictures User: Uploading pictures (15 pictures * 2 mins = 30 mins) * 52 weeks 98% 25.4 User: Sending pictures (3 mins * 10 people = 30 mins) * 52 weeks 97% 25.1 User: Searching for pictures by event (15 mins * 12 events = 180 mins) * 52 weeks 99% User: Viewing pictures by location (50 posts * 3 mins = 150 mins) * 52 weeks 98% Receiving pictures Total Worth ($15/hour) $5006.7

85 Benefit Analysis (in dollars) 85 Year No. of Users Benefit (No. of users * $0.05 * 12) ,000 $ ,000 $3, ,000 $6,000 Assumptions: $0.05 per event created Each user creates at least one event per month

86 ROI Analysis 86 Assume 10% per year increase in cost Year Cost Benefit (Effort Saved) Cumulative Cost Cumulative Benefit ROI

87 ROI Analysis Graph 87

88 NDI/NCS Components NDI/NCS COTS DESCRIPTION FEATURES / WHY? COST USAGE TYPE MySql DBMS High Performance High Availability Comprehensive Application Development Management Ease Free Open Source Apache Web Server Authentication/Authorization Configuration Large File support SQL Database Support Free Open Source HostGator VPS Hosting $160/Month Black Box Flexibility in software installations / apache configurations Unlimited potential for IP's and SSL's Unlimited simultaneous processes Widespread documentation $99/Year Black Box ios SDK Software Development Kit

89 89 Quality Focal Point

90 Traceability Matrix 90 OCD Requirement Use Case Test Cases WC_3579 UC-7 WC_3763 WC_3583 WC_3584 UC-17 UC-3 UC-1 TC-04 TC-01 TC-02 OC-3: Use Location WC_3580 UC-7 OC-4: Search Events OC-5: Browse Event s Pictures WC_3627 UC-6 WC_3637 UC-14 WC_3764 UC-1 WC_3765 WC_3766 WC_3767 WC_3768 WC_3769 WC_3770 WC_3771 WC_3772 WC_3773 WC_3774 UC-18 UC-19 UC-21 UC-8 UC-17 UC-20 UC-5 UC-23 UC-24 UC-22 OC-1: Use Hashtag OC-2: Login with Facebook OC-6: Administrator TC-12 TC-04 TC-05 TC-02 TC-05 TC-06 TC-14 TC-15 TC-16 TC-17 TC-18 TC-19 TC-20 TC-21

91 Traceability Matrix 91 OCD Requirement Use Case Test Case WC_3591 UC-8 TC-07 WC_3585 UC-12 WC_3603 UC-5 WC_3621 UC-4 WC_3763 UC-4 OC-9: Like/Unlike Picture WC_3751 UC-13 OC-10: Report Picture WC_3599 OC-7: Delete Picture OC-8: Create/Delete Private Event UC-10 UC-11 TC-01 TC-03 TC-10 TC-08 OC-11: Choose Add Picture Type WC_3634 UC-7 TC-04 OC-12: Take Picture or Choose From Gallery WC_3619 UC-4 TC-04 OC-13: Save Picture to Device WC_3623 UC-13 TC-09

92 Defects 92 Current defects: Avoidable Defects Unavoidable Defects Concerns Ambiguity regarding connectors for computer we were using for prototype presentation Can't determine how snapchat and Instagram compressions operations, because they hide sensitive info and nothing found so far Some features of Github may require payment: creating organizations with private repositories Some members were busy with registering for classes for spring semester, so we couldn't meet as much as we needed (As of Week 9 Project Status Report)

93 Technical Debt - Resolved 93 Technical Debt Item Resolution Admin Features Additional Requirements Got clear feedback from owner on what he exactly wants for the admin features. Updated our use case diagrams with these new admin features, added 8 use cases. Updated all our OCD diagrams, business workflows and architecture diagrams, to reflect this new admin feature. Update FCR Slides With Correct Diagrams Did a Full Review of Previous FCR ARB Slides and Updated Diagram With Correct Diagram from FC Package, Before Starting DCR ARB Slides. Each Member Had to Review Their Part And Update it. Cut Back on Prototype Reviews We had to fix logic and syntax mistakes in our algorithms diagrams we missed because we didn t review them correctly. We also fixed some mistakes in our GUI prototype such as spelling and syntax mistakes, and added comments to our server side prototype code. Incomplete Prototype Previously unclear requirements clarified at or after FCR ARB, additional features added to prototype.

94 Technical Debt - Active 94 Technical Debt Item Planned Mitigation New GUI Design - Prototype Rework Get clear information from owner about the new features. Do incremental development, test and feedback. owner/team requirements flexibility Server Prototype Weakness - User defined filenames Plan to work with more experienced team members to decide on file naming convention. Algorithm to be developed, implemented, and tested in prototype. ios Inexperience Less experienced team members to work together with more experienced team members. Less experienced team members to seek tutorials on ios development.

95 JIRA - Cumulative Issues Report 95 - Resolved Issues - Open Issues

96 Q & A Do you have any question? Let s ask us.