Slide 1

Thrdplace Social Networking Team MembersRole Gaurav DoonProject Manager YiXiang LiuOperational Concept Engineer Tao HuRequirement Engineer Feng WenPrototyper Ronghui ZhangSoftware Architect Xin LiuFeasiblity Analyst Kan QiLife Cycle Planer 1

Slide 2

Remote Team Member 2

Slide 3

Strong Points We are good at sharing our vision. We agree on a decision only after consulting everyone in the team and when everyone is satisfied with it. Familiarity with technologies like MySql and HTML 5 which are used in the project will make things easier. 3

Slide 4

Weak Points Due to clash of schedules, sometimes it becomes difficult to organize a team meeting. Some technologies like PHP, thrdplace database are not known to the team members, but they will be implemented in the project. 4

Slide 5

Concerns and solutions Sometimes it is difficult to have long meetings due to clashing schedule of team members. Possible solution is to have short meetings after the class. No prior knowledge about technologies like PHP, thrdplace database. Proposed solution is to learn about these technologies from the client. Some team members will not continue into 577b or the development phase of the project, so there will be some different team members. Proposed solution is try to use frameworks and libraries that are well known. 5

Slide 6

Operational Concept Description 6

Slide 7

System Purpose 7 The new system will add recommendation System search Engine user Homepage to the ThrdPlace mainly in order to increase users satisfaction and use of ThrdPlace user inflow and revenue of ThrdPlace

Slide 8

8 Shared Version The recommendation system will recommend users some projects and other users they may like automatically The search engine will enable the users to search projects or users according to influence, success and similarity. The homepage will provide a new project and friends manage for users.

Slide 9

9 Benefits Chain 9

Slide 10

10 System boundary and environment

Slide 11

11 Capability Goals Priority Level OC-1 Search previews for users: The system is capable of enabling users to search other profiles of other users as well as their projects with a map interface. > OC-2 Search users with similar projects: The system is capable of users to search other users and clients who have similar projects > OC-3 Search users and projects: The system is capable of users to search users and projects by capitals like funds, supplies and volunteers. > OC-4 Search the most successful users and projects: The system is capable of users to search the most successful users and projects with the criteria of funds and volunteers. >

Slide 12

12 Capability Goals Priority Level OC-5 Search most influence users and projects: The system is capable of users to search most influence users and projects with the criteria of likes and success rate of projects. > OC-6 Search clients and projects in local community: The system is capable of users to search users and projects in the users community including the active ones and closed one with a map interface. > OC-7 User homepage: The website is capable of providing a user homepage for every user to manage their profile, projects and friends. > OC-8 Recommendation System: The website will automatically recommend some projects and users the typical user may like on the homepage and search page. >

Slide 13

13 Level of Service Goals Referred WinWin Agreements The user home page should be available for users. LOS-1 The search engineer should be associated with a map interface and the project search results can be seen with a map interface. LOS-2 The recommendation system must provide trustful and accurate information for the user. LOS-3

Slide 14

Prototype

Slide 15

Two highest risk items 1. Two types of search view 2. User interface mismatch The ability to search for the similar users or project is very important to our client. The client mentioned the basic functionalities but not user interface. It is important to give client better understanding of what the final product will look like.

Slide 16

User homepage Profile basic information Announcement Recent Activities Recommendation Section Recommendation from ThirdPlace

Slide 17

Project Page The list of Projects The information about Project

Slide 18

The list of Friends The link to Projects list of a friend Friend Page

Slide 19

Search Section Result Section Filter Section Seach Page(List)

Slide 20

The list of Friends The link to Projects list of a friend Seach Page(Map)

Slide 21

Requirements 21

Slide 22

Agreed Win-conditions (WC_2441)As a user, I can search for the most successful or influential clients and campaigns.(MMF search, Ranking system) (WC_2442)As a user, I can search for clients and campaigns who are active in my community (active or closed projects or both).(MMF search, Ranking system) (WC_2447)As a user, I can search other users and clients and campaigns similar to me. (MMF search) (WC_2445) As a user, I can search for clients and campaigns by the capital (funds, supplies and volunteers) that I am looking for. (MMF search, Ranking system) (WC_2800) As a user, I will have a recommendation section on my profile page displaying users and projects similar to mine.(MMF Ranking system) (WC_2444) As a user, I can search for the most successful client and campaigns.(MMF search, Profile) (WC_2449) System shall be deployed on Thrdplace servers.(MMF Deployment) (WC_2450) Maximum budget is 10,000 dollars.(MMF Budget) (WC_2451) Maximum downtime for the system is 3 days in a month.(MMF constraints, Levels of service) 22

Slide 23

System Architecture 23

Slide 24

System Context Diagram Show our systems external interfaces. Define interactions with our system. 24

Slide 25

System Context Diagram 25

Slide 26

Use Case Diagram Define Interface, Entity and Control objects and their classes. Clarify activities & message exchange between objects & users 26

Slide 27

Use Case Diagram 27

Slide 28

Use Case Diagram 28 Profile part

Slide 29

Use Case Diagram 29 Friends part

Slide 30

Use Case Diagram 30 Projects part

Slide 31

Use Case Diagram 31 Search part

Slide 32

Life Cycle Plan 32

Slide 33

Topics Status of The LCPSkills and ResponsibilitesApproachResources Milestoens and Products 33

Slide 34

Current Status of the LCP By specifying monitoring and controlling methods, as well as facilities and tools which will be used in this project, decision on which approach will be adopted to help implementation of the project will be made in this version. Besides, resources necessary for the projects success will also be identified. This document will be a part of Foundation Commitment Package. 34

Slide 35

Milestones and Products Criteria Valu e 30% of NDI/NCS features Single NDI/NCS Unique business process Need control over upgrade Rapid deployment Critical on compatibility Internet connection independence Need high performance Need high security Asynchronous Communication Access data anywhere CriteriaValue Critical mass schedule constraints Lack of personnel capability Little to no upfront costs Low total cost of ownership Not-so-powerful local machines 35

Slide 36

Milestones and Products PhaseschedulemilestonesDeliverables Exploration Phase 09/11/13 09/27/13 Valuation Commitment Review Valuation Commitment Package Valuation phase 09/28/13 10/21/13 Foundations Commitment Review Foundations Commitment Package Foundations phase 10/2213 12/09/13 Development Commitment Review Development Commitment Package Development phase - Construction Iteration 1/11/14 4/16/14 Transition Readiness Review, Draft Transition Readiness Review Package, Integrated system Transition Readiness Review Package, Draft Transition Readiness Review Package Development phase - Transition Iteration 4/17/14 5/07/12 Operational Commitment Review Package, Transition manual Transition manual Operational Commitment Review Package, Transition manual 36

Slide 37

skills Team membe rs RoleCurrent Skills skills required Responsibilities Gaurav Doon PM C/C++, Java, HTML, JAVASCRIPT, Mysql cocomo II, Microsoft Project, Bugzilla, Winbook - Manage Project - Distribute workload, give specific task to each team member Evidence Tao Hu RE,Shaper, IIV&V HTML/CSS, PHP, JavaScript, jQuery, SQL, Apache, JSP, Java Trello, Mind42, Winbook VV: - Review the project artifacts - Manage Project Quality Shaper: - Assess WinWin negotiation context RE: - Assess user requirements - Search and collect data to develop the system - Negotiate with the client to meet win-win condition Kan Qi Life Cycle Planner Java, C/C++, PHP, JavaScript, Mysql, JSP, Android, HTML/CSS, SVN COCOMOII, Bugzilla, COTIPMO COTIPMO Microsoft Project - Plan Project Plan - Identify team members responsibilities 37

Slide 38

skills Team membe rs RoleSkillsRequired skills Responsibi lities Yixiang Liu Operation al Concept Engineer Java, C/C++, PHP, HTML/CSS ER diagram or EER diagram, Winbook, Bugzilla - Analyze the current system - Set specific goals, visions, and user scenarios Xin Liu Feasibility Analyst Java/C++ ROI calculation,COC OMOII, Bugzilla - Assess Project Risk - Plan Risk Mitigation technique Feng Wen Prototyper Java, C, Android, Win32, HTML/CSS ER diagram or EER diagram, Bugzilla, COTIPOMO, UML, - Prioritize system capabilitie s - Design prototype - Co-work with Software Architectur e Ronghui Zhang Software Architect C/C++, C#, Java,HTML/CSS, Mcirosoft SQL Server UML, VPUML,Bugzilll a - Analyze and develop current system with the technologi es - Work with Prototyper todesign, and model the new systems 38

Slide 39

Approach Monitoring and Control Bi-Weely project plan and report weekly team meetings Mothly effort report Closed Loop Feedback Control Bugzilla Wechat Reviews peer reviews IIV&V teaching staff 39

Slide 40

40

Slide 41

Estimated CSCI577a Effort : 7 team members at 10 hrs./week for 12 weeks Estimated CSCI577b Effort : 5team members at 10 hrs./week for 12 weeks Module NameSLOCREVL Profile management150010% Search Engine200015% Intelligent Recommendation5005% 41

Slide 42

PRECNOMINAL FLEXHIGH RESLNOMINAL TEAMHIGH PmatNOMINAL RELY NOMINA L DATA NOMINA L DOCU NOMINA L CPLXLOW RUSELOW TIMEHIGH STOR NOMINA L PVOLLOW ACAPHIGH PCAPHIGH PCON NOMINA L APEX NOMINA L LTEX NOMINA L PLEXLOW TOOLLOW SITEVH SCEDNOM 42

Slide 43

According to COINCOMO II, one team member effort = 0.83 COINCOMO II person months. The most likely effort from the COCOMO estimation above is 8.93, so the total team members need for this project = 8.93/0.83 = 10.76 Since we have 7 developers in total on our team, the estimated workload for this project would exceed our capacity to handle and thus may introduce risks of project failure. Thus, we may need to negotiate high-priority requirements to cut less valuable works and reduce the risk of project incompleteness. 43

Slide 44

Feasibility Evidence Description 44

Slide 45

Feasibility Evidence Description---Thrdplace Purpose of FED Process Feasibility Risk Assessment NDI/NCS Feasibility 45

Slide 46

Purpose of FED FED evaluate the degree of feasibility of the project based on making risk assessment. Then the key stakeholders can determine whether to proceed into the next level of commitment. 46

Slide 47

Process Feasibility 47

Slide 48

Process Feasibility 48

Slide 49

Process Feasibility 49

Slide 50

Risk Assessment 50

Slide 51

Risk Assessment 51

Slide 52

NDI/NCS Feasibility Analysis NDI: Mysql, apache NCS: esri 52

Slide 53

NDI/NCS Feasibility Analysis 53

Slide 54

NDI/NCS Feasibility Analysis 54

Slide 55

NDI/NCS Feasibility Analysis Evaluation Results Screen Matrix for NCS Attributes 55

Slide 56

NDI/NCS Feasibility Analysis the attributes of it satisfy 82.5% of NCS attributes and the features of it satisfy 94.75% of NCS features. Evaluation Results Screen Matrix for NCS features 56

Slide 57

Quality Focal Point 57

Slide 58

Traceability Matrix OCDWin-Win AgreementSSADTest Case OC-1 Search previews for users WC_2448UCN/A OC-2 Search users with similar projects WC_2447UCN/A OC-3 Search users and projects WC_2445UCN/A OC-4 Search the most successful users and projects WC_2444UCN/A OC-5 Search most influence users and projects WC_2441UCN/A OC-6 Search clients and projects in local community WC_2442UCN/A OC-7 User homepage WC_2801UCN/A OC-8 Recommendation System WC_2800UCN/A 58

Slide 59

Quality Management Strategy StrategyPriorityDescription Win-WinHigh The win-win methodology (Win-Win Session, Win-Book, etc.) will be used to ensure that all stakeholders' win conditions are met with the final implementation. Incremental Commitment Model Standard High By using the Incremental Commitment Model templates and guidelines, the artifacts produced should have the correct format and substance. PrototypingHigh Include explicitly all requirements and risks in the prototype and improve prototype in iterative cycle to make sure the clients user interface expectations are understood and incorporated. Programming StyleHigh Use the same programming style as the original code of ThrdPlace website to increase readability and compatibility. Version ControlHigh Use Dropbox to share updated repository between team members to prevent communication defect. Defect Prevention Strategy 59

Slide 60

Quality Management Strategy StrategyPriorityDescription Compliance checking models, assertions, standards. High ThrdPlace websites codes mainly consists of HTML/CSS, PHP, JavaScript. The W3C Markup Validation Service is used to validate HTML/CSS; FireBug is used to debug and auto check syntax and semantic errors of JavaScript/ PHP. Traceability checkingHigh Traceability matrix is used to check the relationship between all artifacts. Views, interface, behavior, pre/post conditions High Requirement, design view consistency checking during prototyping. Defect Detection Strategy Automated Analysis 60

Slide 61

Quality Management Strategy StrategyPriorityDescription Peer reviewHigh Mid-semester Peer Evaluation and End-semester Peer Evaluation will be conducted using iCard System. Architecture Review BoardHigh FCR_ARB and DCR_ARB will be conducted to evaluate project progress and decide whether to move forward to next phase in ICSM. Defect Detection Strategy People Review 61

Slide 62

Quality Management Strategy StrategyPriorityDescription Code Coverage TestingHigh A program with high code coverage has been more thoroughly tested and has a lower chance of containing software bugs than a program with low code coverage. Cobertura is used to test code coverage. Functionality TestingHigh Test all the functions of website and user interaction with the website. Firefox add-on Selenium is used. Performance TestingHigh Include web load testing and web stress testing. Firefox add-on Page Speed is used to test and provide suggestions. Compatibility TestingHigh Test web compatibility across different browsers, operating system and devices (laptop, tablet, mobile). Security TestingHigh Include URL access control testing, Cookie encryption testing and database security testing. Defect Detection Strategy Execution Testing 62

Slide 63

Quality Management Strategy Strategy Priorit y Description Defect Tracking System (Bugzilla ) Very High Bugzilla allows developers in a group to keep track of project activities such as outstanding bugs and development tasks in their product effectively. Project Mange and IIV&V are responsible for assigning a defect in Bugzilla. The defect assignee will be notified by email and have to resolve the defect before deadline. IIV&V will monitor the defect and then verify or reopen a defect according to requirements. (Below is the lifecycle of a defect in Bugzilla) Defect Removal Tracking 63

Slide 64

Thank You!! 64