City of LA Personnel Department Mobile Application

42
City of LA Personnel Department Mobile Application Team 02 1

description

City of LA Personnel Department Mobile Application. Team 02. 1. Requirements & OCD. 2. System Purpose. Mobile application that provides • Critical information to applicants interested in employment opportunities with City of LA • Allow users to subscribe to a specific job - PowerPoint PPT Presentation

Transcript of City of LA Personnel Department Mobile Application

City of LA Personnel DepartmentMobile Application

Team 02

1

Requirements & OCD

2

System Purpose

Mobile application that provides

• Critical information to applicants interested in employment

opportunities with City of LA

• Allow users to subscribe to a specific job

• The system will send notification via email and/or text message for

reminding when that position open 3

New Requirement

4

Updated Boundary System Diagram

5

Updated Element Relationship Diagram

6

Test Plan and Cases

7

Test Strategy

• Unit testing

• Integration testing

• System testing* (waiting for information from clients)

• Core Capabilities Drive-through

• Requirement Traceability

• Acceptance testing

8

Test Cases

TC-01 Intuitiveness of UI

TC-02 Search existing jobs

TC-03 View open jobs

TC-04 View job descriptions

TC-05 Subscribe for notification

TC-06 Create/update user profile details

TC-07 Receive notification for open jobs

TC-08 Process Neogov RSS feed

TC-09 View LAPD jobs9

Requirement Traceability Matrix

10

Test Resources

Personnel: All members participate, with tester leading the process and IV&V verifying and validating results

Computing resource: Computers, Android devices, iOS devices, server, internet

Other: RSS feed and email/text message service

11

Test Schedule

12

Architecture

13

Use Case diagram

14

Hardware Component diagram

15

Software Component diagram

16

Deployment Diagram

17

Sequence diagram - Subscription

18

Sequence Diagram: User Profile

19

Sequence Diagram: Notification

20

Class Diagram

21

Interface Class diagram

22

Artifacts and Information diagram

23

COTS Selection

Phonegap

To create an app for Android and iOS.

Uses HTML, CSS and Javascript to create an hybrid application (web based and native application).

Prototyped for Android and iOS.

24

Prototype

25

Home ScreenOld Updated

26

SubscriptionOld Updated

27

Open JobOld Updated

28

Life Cycle Plan

29

Roles and ResponsibilitiesShreya Kamani - Project Manager Anushree Shridhar - ImplementerPattra Thongprasert - Implementer / TrainerAbhishek Trigunayat - Implementer Travis Jones - TesterWilliam Everton - IIV and V

30

Plan for 577b

31

32

33

Feasibility

34

Risk Assessment

35

Definition of Done

· Complete code implementation

· Pass every criteria in all test cases

· Documentation of code and configuration must be complete for future client reference

· Client must be trained for product transition and maintenance

· Application adheres to quality guidelines set by both the Android and Apple marketplace

· All final deliverables and complete manuals deliver to clients

36

Quality Focal Point

37

Traceability MatrixCapability Goals Requirements Use Cases Test Cases

OC-1 List jobs WC_2374WC_2378WC_2380WC_2382

UC-02 View open jobsUC-03 Search all jobsUC-04 View job descriptions

TC-02 Search existing jobsTC-03 View open jobsTC-04 View job descriptions

OC-2 Send notifications WC_2370WC_2377

UC-06 Notifications for job openingsUC-07 Process Neogov RSS feed

TC-07 Receive notification for open jobs

TC-08 Process Neogov RSS feed

OC-3 Subscription to jobs WC_2373WC_2383

UC-01 Create/update user profileUC-05: Subscribe for notifications

TC-06 Create/update user profile details

TC-05 Subscribe for notifications

OC-4 View LAPD jobs WC_3055 UC-08 View police department jobs TC-09 View LAPD jobs

38

CONFIRMED IN_PROGRESS RESOLVED

FCR ARB 4 3 11

DCR ARB 3 9 42

Currently 2 0 60

Tasks Resolved

Average Days Open Average Hours Std Dev Hours

EstimatedSeptember 6 8.7 4.9 ±2.6

October 23 7.4 5.3 ±5.0

November 13 7.5 3.2 ±2.1December

January 10 16.3 4.2 ±1.1

February 8 73* 6.4 ±0.8

Metrics

39

January February March April May0%

20%

40%

60%

80%

100%

Ideal Burndown

Feb 11: Rebaselined DCR ARB

Mar 26: Core Capability Drive-Thru

Apr 10: In-stallation

Burndown

40

Team Strong and Weak Points

+Team Cohesion

Our team has worked together now for nearly 6 months now. We are leveraging on each others strengths and learning to assist when teammates need help.

+Experience

Our team now has more experience with the project. We have a better understanding of the problems at hand and how solve them.

-Scheduled Break

The scheduled break between CSCI 577A and 577B has caused an interruption of progress. Our momentum in our tasks have since improved, but this did affect our productivity momentarily.

-Communication

Every team can stand improvement for better communication. Since the entire team is not collocated in Los Angeles, it is even more important that we have clear discussions regarding tasks and intent.

41

Questions?

42