CS 577A Team 1 DCR ARB. PicShare

Size: px

Start display at page:

Download "CS 577A Team 1 DCR ARB. PicShare"

Sheila Hunter
5 years ago
Views:

1 CS 577A Team 1 DCR ARB PicShare

2 Team and Project Review (DEN)

3 Project Evaluation Positives Resilient Agile detailed design promotes thoroughness before any code is written Development time should be reduced since most interactions and functionality have been nearly explicitly mapped Manage complexity better Learned another MVC Framework (Spring) and back-end COTS solution (Heroku/Parse) Negatives Worthwhile for larger, longer term projects (defense-industry scale projects F-35), but maybe less so for apps where first to market may be more critical (mobile app market) Large amount of time wasted on process conventions, which could be spent on functionality Conflicting guidance Building a prototype seems counter-intuitive to the long-term design process. Could instead work towards the setup or planning for next semester Grading depends on short-term prototype demonstration - 577a class requirements vs process Better designed, less refined prototype at this point versus architected agile

4 Team Evaluation Positives People contribute and do their part Once a direction is decided, team commits Teammates reliable Communication worked, but there might be room for improvement Team lead takes the initiative when necessary Negatives Not enough people speaking up, direction decided by two team members, sometimes one Team direction changes by single member after team makes decision Undermines team consensus and commitment, produces uncertainty Ex. Veto Parse -> Choose/Reject Spring/Heroku -> Choose Parse

5 Process Improvement Trailblazing system works better System Integrator takes the lead and establishes a format first Everyone doing something their own way and then submitting for revision is inefficient Do it first, then send out guidelines This reduces the overall amount of rework for everyone

6 Program Model Assumptions: People desire to share photos People are interested in what is happening around them People are dissatisfied with existing means of sharing photos Stakeholders Initiatives Developers Client Maintainers App Users Design and develop system Marketing Maintenance Documentation, training and knowledge transfer Using the app to share photos Value Propositions Cost To increase efficiency of photo sharing To allow users to share photos through private and public events as well as their current location To improve user experience in photo sharing To promote sharing of photos Benefits Development costs Maintenance costs Server costs COTS costs Revenue Increase number of users Beneficiaries App Users (Techsavvy people aged 18-45)

7 Domain Model

8 Use Case Diagram

9 Class Diagram

10 Technical Architecture ios (Swift) Parse MongoDB (NoSQL) Cloud Code (JS)

11 User Account Creation

12 Create Account

13 Log into Account

14 Log out of Account

15 Navigation Class Diagram

16 Navigate between Screens

17 Upload photo to location

18 Take a Photo

19 View Photos on devices

20 Upload to Location after Taking Photo

21 Parse Cloud Code Why Cloud Code? Although most of our logic runs on the front-end and Parse is taking good care of the back-end for us, sometimes we still need to implement some logic that runs on the back-end. That is why we need the Cloud Code.

22 Class Diagram Entity & Code

23 Auto-expiration

24 Use Case Text & Sequence Diagrams

25 View joined diagram

26 Search Event

27 Risk Rank Risk Description Cause Mitigation Method 1 Unknown system We have not defined how well the system should work We plan to discuss the technical and load constraints such as how many users it should support or the non-functional requirements among expected load to our servers and database. our teams and then negotiate with the client P(L) 1-10 S(L) RE 4 16

28 Risk Rank Risk Description Cause 2 The scope of the Even after negotiating with the client to create a core project is large for set of MVP requirements, the project is still sizable for the time frame. our time frame. Also new requirements were discovered as we performed robustness analysis and FCR ARB presentation adding to the scope. Mitigation Method We plan to consistently negotiate with the client for any new requirements to reduce the scope. We also plan to begin prototyping in order to buy information about our system to get a better estimate of development tasks. P(L) 1-10 S(L) RE 5 15

29 Risk Rank Risk Description Cause 3 The project may Since the team is inexperienced in mobile app not be completed development, so there will be an initial high learning on schedule due curve. to lack of mobile app development experience. Mitigation Method We plan to mitigate this risk by modifying our team structure and process to match the strengths of our team. Likewise we plan to start learning more about our development platform and begin prototyping. P(L) 1-10 S(L) RE 7 14

30 Risk Rank Risk Description Cause 4 System may not Due to a lack of end-user involvement during the function system development, the system may be difficult to according to user use or not what the user has expected. expectations Mitigation Method We plan to have the client test our system as we develop prototypes in order to buy information about what our end-user may expect from our application. P(L) 1-10 S(L) RE 6 12

31 Risk Rank Risk Description Cause 5 Potential COTS We may decide to use some COTS as part of our conflicts and system to help expedite our development. However, integration issues since we have not started development, we don't know if they will integrate well with our system. Mitigation Method We plan to mitigate this risk through buying more information through prototyping the components that will use these COTS. P(L) 1-10 S(L) RE 3 9

32 Project Management Risk Rank Risk Description 1 Staff Turnover Cause Our den student team members may not take 577b in the next semester and other students may join our team. Mitigation Method We plan to make our development style consistent. It will be much easier for us to transfer current task to new team members. Also we will record every details of our project. Good documentation makes it easier for new team members to understand what we have completed. P(L) S(L) 1-10 RE 2 20

33 Project Management Risk Rank Risk Description 2 Requirement Change Cause Mitigation Method As a part of agile development, our client have changed We have worked much to change our some requirements and may change more in the future. model due to requirement change. We have divided work into different parts. In the future, the team member who is responsible for the corresponding changed requirements will focus on the rework, which is quite familiar to them. P(L) 1-10 S(L) RE 3 18

34 Project Management Risk Rank Risk Description 3 Management Change Cause We may have different integrators for different parts in the future process of project. Also staff turnover makes team management different. Mitigation Method We plan to make everyone's responsibility more clear and our teamwork more efficient to reduce the amount of the work of integrator. P(L) 1-10 S(L) RE 2 10

35 Technical Debt - Paid # Description Enabler Interest Mitigation plan Lack of collaboration through using Resilient Agile 1 results in additional errors, inconsistencies, and redundancies 1. Follow Resilient Agile process. 2. Each member work on all tasks in parallel Be familiar with RA process quickly and figure out a viable next step plan. System integrator will provide guidelines for team work as a prevention method in reducing errors. Also system integrator will Paid. integrate the work on a consistent basis to 10h * 8p = 80h prevent large merge conflicts. Also appoint an additional backup system integrator to help with the workload. 2 Lack of product understanding due to 2 minimal and inconsistent communication with client 1. Different schedule of each team member and client. 2. Lack of direct negotiation. Push process forward first, accumulate risks and solve them. Formulate weekly summary of questions for client, and communicate with him regularly Paid. through . Attempt to schedule a weekly 4h * 4p = 16h meeting around client's busy schedule. 2 Get a complete 1. Following the RA process in Lack of system prototype of and specific Begin prototyping major risk and areas of the, the major work of team is 3 major risk areas may reveal requirement and concern to unveil any potential problems or to figure out accurate undiscovered flaws in design. high-matched integration issues. requirement. product design. current state No. of weeks active Not paid. 5h * 8p = 80h 2

36 Technical Debt - Unpaid # Description Focus only on critical MVP features of 4 the app may cause additional rework to add additional features Decision to use Parse over a custom 5 backend solution, will increase costs as the number of users increases. Enabler 1. There are many features which cannot be completed at once. 2. Help team to better understand requirements concretely and quickly. 1. Team members have different experience in backend development.. 2. Parse is easy to learn and could help us avoid a lot of technical detail. Interest Completed a cycle for RA to create a robust design. Mitigation plan current state Appoint an architect to architect our system at a high level to allow the system to be scalable. Compile list of additional features Not paid. and have team members keep these features 10h * 8p = 80h in mind as they are developing the MVP features. Get a prototype up Develop ios app with capability to replace and running Parse with a custom backend solution. quickly. Not paid. Depend on technical and non-technical requirement, which have not been determined. No. of weeks active 4 1

37 Technical Debt - Unpaid # Description Enabler Interest Mitigation plan Current State No. of weeks active 6 Lack of UX and UI design, the UI is 1. Lack of experienced UX and UI designed to meet requirement simply. designer in team. Get a prototype up Refer to some similar applications for UI and and running Not paid. UX designed principles. Reach out to client to quickly. 8h * 8p = 64h. hire a Graphic Designer. 1 7 Lack of well-considered, solid infrastructure. Team did not spend time on considering the best solution for the requirements, but rather for the team. Get a prototype up and running After completing the MVP, team will quickly. negotiate with client and decide to use Parse Team can focus in development or explore other solutions. more on frontend programming There is not enough time to plan and discuss. 2. Parse is really easy to use and reduces a lot of complex work. Not paid. Depend on technical and non-technical requirement, which have not been determined.

38 Traceability (1 of 3) # Requirement The system shall allow a user to upload a 1 photo to an event. Use Case # Use Case Description 1,24 The system shall allow a user to reserve a hashtag for a private event, allowing the user to specify a password to upload and 2 view photos of the event. 4, 5,6,7,8 The system shall allow users to view photos uploaded from nearby locations in 3 a grid layout. Class Diagram Test Case Upload photo to my event, Search for event & upload photo Upload photo to my event Photo management TC-03 Create private event, Reserve Hashtag, Set a password, View Set a password, reserve a photos of event, View event with hashtag, view photos of password event/private with password Event Management TC-01 9 Search by location The system shall allow users to search for 4 events by hashtag. Sequence Diagram 10 Search for event Search Location Search Location Search Event Search Event TC-09 The system shall delete expired events 5 and any photos associated with them. 17,18 Delete expired events, Delete photos of expired events Auto expiration Admin The system shall provide functionality for users to delete their own photos and for 6 administrators to delete photos. 11,19 Delete uploaded photos, Admin delete photos Admin delete photo, Delete photos in event if owner Admin, Event Management Take a photo Photo management The system shall allow a user to take a 7 photo with the camera on the device. 13 Take photo TC-02

39 Traceability (2 of 3) # Requirement The system shall prevent users from uploading photos to private events 8 without the password. The system shall provide an interface for users to create a new account or login to 9 an existing one. The system shall allow a user to create a 10 public event. Use Case # Use Case Description Sequence Diagram 28,29 Join event, view joined event view joined event, search for Event event Management 14,16 Create account, Log in to Create account, Login to account account 3 Create public event Class Diagram Account Create public event Event Management TC-01 Event Management TC-04 The system shall allow an owner to delete 11 photos in their event. 12 Delete photos in private event Delete Photos in Event if Owner The system shall delete expired photos 12 uploaded to a location. 20 Delete expired location photos Auto expiration Admin Download photos to device Event Management 3 Create a public event Create public event Event Management 2 Take photo for location Upload to location after taking photo Photo management The system shall allow users to download 13 photos to their device. The system shall prevent events from having the same hashtag as any other 14 non-expired event. The system shall only allow users to take photos when uploading to their current 15 location. 21 Download photo to device Test Case TC-05

40 Traceability (3 of 3) # Requirement Use Case # Use Case Description Sequence Diagram Class Diagram View photos on device Photo management Search Location Search Location 3,4 Create a public event, Create a private event Create public event Event Management 7,8 View photos of event/private with password View photos of Event event/private with password Management The system shall allow users to view photos 16 on their device to upload. 26 View photos on device The system shall allow users to filter nearby photos by a predefined radius (My Home, My 17 Block, My City). The system shall allow hashtag names only contain alphanumeric and dashes and 18 underscore characters. The system shall display the remaining time on an event as days if greater than 1 day or 19 hours:minutes if less than 1 day. 9 Search by location Test Case The system shall allow administrators to filter the list of all events by hashtag name and 20 users by username. 22,23 Admin search for photo by Search for photos by user, user, Admin search for Search for photos by event photo by event Admin The system shall allow users to create an 21 account profile and logout of their account. Create profile, Log in to account Account TC-08 Navigation TC-09 The system shall allow users to navigate 22 between screens with a tab bar. 15,25 Create profile, Log in to account 27 Navigate between screens Navigate between screens

41 Test Case Examples

42 Test Case Examples - TC-01 TC-01 Create Event, software item level, erroneous test The test for Create Event will be completed when: The system creates a public or private event. The system displays the newly created event on the event screen. The system displays the appropriate error response for mistakes. This test case has 5 subtest cases: TC Check create public event with valid hashtag name. TC Check create private event with valid hashtag name and password. TC Check create public event with invalid hashtag name. TC Check create private event with invalid password. TC Check create private event with no network connection.

43 Test Case Examples - TC-01

44 Test Case Examples - TC-02 TC-02 Search by Location, software item level, erroneous test The test for Search by Location will be completed when: For a functioning location sensor, the location sensor should return location data and for a non-functioning sensor, the system should notify the user that the sensor is non-functional. A successful test must query a test region and return all photos within the test region. A successful empty test must return the null result when no photos are within the region and display to the user the null result notification. Omitted photos in the first test or superfluous photos in the second test are considered failures for each test, respectively. For each sub-case, lack of user notification is also considered a failure. A successful test should connect when the database is available, display a connection failure message when the database is unavailable, or display a database software failure message when a non-connection issue arises. This test case has 3 subtest cases: TC Functional Sensor Test TC Non-Functional Sensor Test TC Populated Location Query Test

45 Test Case Examples - TC-02

46 Test Case Examples - TC-03 TC-03 Upload a Photo, system item level, erroneous test The test for Upload a Photo will be completed when: A photo is tagged with location data and descriptive text The photo and tag data (location & descriptive text) are submitted to the photo database The uploaded photo can be viewed by browsing photos around the current user location This test case has 3 subtest cases: TC Upload a photo with valid tag data and server connectivity. TC Upload a photo with invalid tag data. TC Upload a photo with no server connectivity.

47 Test Case Examples - TC-03

48 Test Case Examples - TC-04 TC-04 Delete uploaded photos, software item level, erroneous test The test for Delete uploaded photos will be completed when: System display Delete successfully after delete the photo correctly System display Failed to connect to Internet if user device cannot get access to Internet System display Failed to delete, try again later if user device can get access to server but failed to delete the photo by any reason This test case has 3 subtest cases: TC Check deleting a photo when every part of the system works well TC Check deleting a photo without Internet access TC Check deleting a photo when server is out of work

49 Test Case Examples - TC-04

50 Test Case Examples - TC-05 TC-05 Download photos for events, software item level, erroneous test The test for Download photos for events will be completed when: System display Download successfully after download the photo correctly System display Internet Interruption if user device cannot get access to Internet System display Failed to download the photo, try again after cleaning storage if user device storage is full This test case has 3 subtest cases: TC Check downloading a photo when every part of the system works well TC Check downloading a photo with Internet interruption TC Check downloading a photo when local device is out of storage

51 Test Case Examples - TC-05

52 Test Case Examples - TC-06 TC-06 Navigation Functionality Test, software item level, erroneous test The test for Navigation Functionality Test will be completed when: System successfully displays the navigation bar on screen when it should be. System successfully receives user input on navigation bar. Navigation bar invokes corresponding screen correctly based on user input. This test case has 3 subtest cases: TC Check navigation bar display TC Check navigation bar input receipt TC Check navigation invoke functionality

53 Test Case Examples - TC-06

54 Test Case Examples - TC-07 TC-07 Search for photo by user, software item level, erroneous test The test for Search for photo by user will be completed when: The user returns correctly. The system displays user on the monitor correctly. The system shows appropriate an error message according to the mistake. This test case has 3 subtest cases: TC Check search for photo by a user with legal name TC Check search for photo by a user automatically TC Check search for photo by a user without Internet access

55 Test Case Examples - TC-07

56 Test Case Examples - TC-08 TC-08 Create Account, software item level, erroneous test The test for Create Account will be completed when: The system creates a public or private event. The system displays the newly created event on the event screen. The system displays the appropriate error response for mistakes. This test case has 3 subtest cases: TC Check creating an account with correct information TC Check creating an account with missing required field TC Check creating an account with address or username that is already in use

57 Test Case Examples - TC-08

58 Test Case Examples - TC-09 TC-09 Search for event, software item level, erroneous test The test for Search for event will be completed when: The system stops searching process and returns error messages if a user types in an illegal search term. The system properly returns error messages when the server is down. The system retrieves search result within one second. This test case has 3 subtest cases: TC Check input search term legality TC Check server error status TC Test search response speed

59 Test Case Examples - TC-09

60 Backup Sequence Diagram Slides

61 Create Profile

62 Create a Private Event

63 Set a Password

64 Create a Public Event

65 View Photos of Event/View Photos of Private Event with Password

66 Reserve a Hashtag

67 Delete Photos in Event if Owner

68 Download Photos to Device

69 Search Photos by Location - Primary Course of Action

70 Search Photos by Location - Alternate Course of Action

71 Admin login

72 Search for photo by event

73 Search for photo by user

74 Admin delete photo

75 Upload Photo to my event

76 Open My Event for Upload

77 Search event for upload

78 Upload to Event

Prototype Report (PRO) Version 2.1. Prototype Report. PicShare. Team 02. Team Members

Prototype Report (PRO) Version 2.1. Prototype Report. PicShare. Team 02. Team Members Prototype Report PicShare Team 02 Team Members Sultan Alsarra Adil cem Albayrak Julapat Julnual Charles Reitz Mohammad Almunea Aref Shafaeibejestan Andrea Brown Travis Weaver 12/7/2015 Version History