Thai CDC Software tool

1
Thai CDC Software tool

• Team 3
• Life Cycle Objectives
• -Architecture Review Board
• -10/26/2007

2
Introduction to Thai CDC

• Thai CDC is a nonprofit organization.
• Committed to Empowering and improving working
  conditions for low-income Thais and other
  exploited workers.
• Committed to Promoting the rights of Thai
  Americans as well as advocating for more humane
  labor and immigration policies.
• Committed to Providing and ensuring access to
  culturally sensitive human and social services.
• Represented by
• Pheel Wang

3
Continued

• Clients
• -Thai Community Development Center
• Users
• -Thai CDC System Administrator HR
• -Thai CDC Project Manager
• -Thai CDC Staff
• Maintainers
• -Thai CDC Maintainers
• Developers
• -577A Team 3

4
- Kevin Locklin
IIVV
5
LCO Defect Identification Review

• Documents Reviewed
• FRD, SSRD, SSAD, SID, RSM, OCD and LCP
• Types of Review
• All documents were reviewed using the Agile
  Artifact Review method
• OCD incorporated feedback from the TA
• Client meeting notes were used to tailor these
  documents
• Sources of Observation
• Client meetings
• WikiWinWin negotiation
• Package evaluation (AAR)

6
LCO Defect Identification (1 of 3)

• Missing
• References for ROI data
• Win condition reference numbers
• Assessment of system down time
• Storage capacity and bandwidth
• Wrong
• Section heading numbering system
• Formatting issues
• Extra
• Features
• Unnecessary Risks
• UML Layout

7
LCO Defect Identification (2 of 3)

• Low
• Section numbers
• Formatting
• Medium
• TOC, TOF and TOT
• Spelling
• Links within documents
• High
• Person-Months inconsistent between LCP and FRD
• Wrong win condition references
• Modes of Operation

8
LCO Defect Identification (3 of 3)

• Low
• Typos
• Links within documents
• Medium
• Modes of operation
• Win condition numbers
• High
• Server requirements such as storage capacity and
  bandwidth
• Justification of ROI numbers used

9
Thai CDC - Strong Points

• Operational view
• The SSAD does a good job of covering all the
  desired functions of the CDC software tool for
  website development and content management.
• The team appears to have a thorough understanding
  of how the end-system will work and the functions
  it needs to perform the way the client desires.
• The Element Relation Diagram in the OCD appears
  to be well thought out and thorough.
• Technical view
• The UML model of the system captures the
  functionality of the tool and provides clear
  relationships of each module.
• Using Drupal as the base for this tool eliminates
  any cost while providing the platform necessary
  to accomplish all the goals of Thai CDC.
• COCOMO was used to estimate a realistic value for
  the amount of effort needed

10
Thai CDC - Weak Points

• Operational view
• Documentation and user guides
• Might not be enough time to capture the detail
  necessary
• Secure donation/payment
• Pay Pal will be used, but no team members have
  used it before. Need more details on how to
  incorporate it to the site.
• Does it cost anything? Need more details.
• Technical view
• Server requirements are not clearly addressed.
• Bandwidth? Storage?
• System availability not clearly defined.
• Down time for maintenance?

11
Concerns

• None of the developers have used Drupal before
• Start tinkering with it now
• Start development early if possible
• Requirements not quite firm
• Continue to update the WinWin negotiation
• Keep client involved
• Set a deadline after which requirements are not
  allowed to change
• Performance not addressed
• Find similar sites and gather statistics
• SWAG if necessary

12
Risks

• None of the developers have used Drupal before
• Start tinkering with it now
• Start development early if possible
• Server requirements
• Survey the current site to get user statistics
• Estimate number/size of downloads
• Have a plan to expand once storage and/or
  bandwidth reach a limit
• Team member retention for spring
• Have team members put a status report together
  before the fall semester ends stating what they
  have done and what needs to be done next
• Keep contact with those who leaveget a
  commitment!

13
Operational Concept Description

• -Bharat Bagai

14
System Capability Description

• A web based software tool which will allow the
  Thai CDC users to easily publish, manage and
  organize a wide variety of content.
• Unlike the current website proposed software tool
  will allow the Thai CDC Staff to create a website
  which will provide the user with a lot of
  features including a virtual market, news feeds
  and the ability to make donations.

15
Expected Benefits

• Provide the Thai CDC staff with the ability
  create different modules in the website and make
  changes easily.
• Simple web-based interface for creating and
  publishing the information.
• Authenticate the user and accordingly grant user
  specific privileges securing the personal data.
• Assist in their fund raising efforts.
• Assist in better scheduling of the various events
  at Thai CDC.

16
System Boundary Diagram

17
Benefits Chain

• Assumptions
• - volunteer availability
• - ample storage for the archive
• Knowledge of RSS feeds
• - Customers of Thai CDC willing to donate or
  purchase merchandise

Update XML for RSS feeds And Update Events
Calendar
Use the Thai CDC website to upload and download
content, read news, make donations and volunteer
for events.
Ensure storage capabilities and system
availability
Organize, manage and Publish various content
Donations, secure payment
Up to date Website with more features
RSS news feed and calendar
Ease ability to Create and Edit the Content on
the Website
Faster, more frequent updates increase community
involvement
Develop new online system to archive information,
provide access to the Thai CDC online store.
Thai CDC provides services to the Thai community
18
Capability Goals

• OC-1 Web Based Application
• OC-2 Virtual Market
• OC-3 News Feed
• OC-4 Volunteer Recruitment
• OC-5 Uploading/ Downloading Multimedia
  Content
• OC-6 Event Calendar
• OC-7 Make Donation
• OC-8 User Security

19
Comparison Of Systems
20
Organizational Transformation

• Proper dissemination of work among the Thai CDC
  staff members as roles for each task will be
  assigned to the staff members.
• This system will provide a lot of flexibility to
  the members of the organization as any member can
  organize event as per their wish and need not
  consult the web designer for these purposes.

21
Prototype Design

• -Srikanth Chakkilam

22
Prototype Design Objectives

• Thai CDC Prototype Design Goals
• Prototype Design Approach
• Technical Issues
• Tool Capabilities
• Thai CDC Current Website
• Conclusions and Future Plans.

23
Thai CDC Prototype Design Goals

• Users
• Thai CDC System Administrator
• Thai CDC Staff
• Thai CDC System Maintainer
• Current System
• No current system to manage the website
• Just a static webpage with no capabilities
  that benefit its users.
• New System
• A tool which helps manage THAI CDC to manage
  their content for the website.
• Tool capabilities include top eight
  requirements that have been negotiated and
  converged.
• Objectives of the Tool
• Manage and upload Content with EASE
• EASE User friendly GUI and easy to
  navigate.

24
Continued.

• Provide capabilities and functionalities
  that are beneficial as well as advantageous to
  the user .

25
Prototype Design Approach

• Design
• Intended to mitigate risk
• Design based on Wiki Win Win Negotiation
• Snapshots using Macromedia Dreamweaver and
  templates of DRUPAL
• Implementation
• COTS Approach Adopted
• COTS used DRUPAL Framework

26
Technical Issues?

• Server Issues
• Existing servers capability

27
Tool Capabilities

• CR-1 Multimedia Module
• CR-2 Event Calendar
• CR-3 Volunteer Recruitment
• CR-4 Virtual Market
• CR-5 Donation Module
• CR-6 News Archive
• CR-7 User Access Permissions

28
Thai CDC Current Website
29
Login Page
30
Main Page
31
Multimedia Module
32
Continued.
33
Virtual Market Module
34
Continued.
35
Volunteer Recruitment Module
36
Continued..
37
Conclusions and Future Plans.

• Showed the initial prototype to the client.
• Reviewed the prototype as per the feedback from
  the client, end users and development team
• If any specifications are added, discuss and
  negotiate what is within scope.
• Improve and Enhance the Prototype as per the
  feedback.

38
Requirements

• -Pavan Burgula

39
Requirements

• Project Requirements
• Capability Requirements
• System Interface Requirements
• Level of Service Requirements
• Evolutionary Requirements

40
Project Requirements

• Development Requirements
• Tools WikiWinWin Tool, MSProject, DART, RSM,
  COCOMOII
• Web Development Drupal CMS
• Languages PHP to integrate Drupal modules, SQL
• Server Apache 1.3x
• Database MySQL

41
Project Requirements

• Budget- 0.0 development cost for the client
• Schedule- 24 weeks
• 12 weeks for life cycle architecture
• 12 weeks for development and implementation

42
Project Requirements

• Support Environment Requirements
• Provide the Thai CDC staff with user manual
  (e-copy) with complete instructions

43
Capability Requirements

• Multimedia
• Event Calendar
• Volunteer Requirement System
• Virtual Market
• Donation
• RSS Newsfeed
• User Security
• User Input in Thai

44
System Interface Requirements

• Simple User Interface- Tool should have an easy
  to use GUI.
• User Feedback- Feedback from the users of the
  tool to judge its simplicity.

45
Level of Service Requirements

• Easy Usability
• It should be useable and it is based on user
  feedback. The rating is from 1 to 5.
• Desired 100 rating of 5
• Accepted 90 rating of 5
• Availability
• The tool should be available for all the hours of
  the day.

46
Evolutionary Requirements

• Viewing Website in Thai
• The tool should include the capability for the
  user to view the website in Thai.

47
System Architecture

• -Vishal Chawathe

48
Purpose

• Provides a general Structure for Thai CDC
  software tool.
• Shows which actors interact with the system.
• What services the system is going to provide.
• What artifacts and information does the system
  inspect, manipulate or produce.
• What are the various modes of operation.
• Shows major components in system and the
  dependencies among them.

49
Overview

• Actors Description of users of the system.
• System Structure Static Structure Diagram.
• Artifacts and Information System Information
  Model.
• Behavior
• -Processes
• -Modes of Operation

50
Static Structure Diagram
51
Overview of Actors

• System Administrator
• He is responsible for creating, approving
  website content made by Thai CDC staff,
  publishing website.
• Thai CDC Staff
• Responsible for creating website content for
  Thai CDC.
• Maintainer
• Responsible for maintaining the Thai CDC
  software tool and Website.

52
System Information Model
53
Processes

• System Administrator
• Process 1,2 Admin login/logout.
• Process 3,4Add/ Delete page/story.
• Process 5,6,7 Add/Edit/Delete Multimedia
  content.
• Process 8,9,10 Add/Edit/Delete Virtual Market
  content.
• Process 11,12,13 Add/Edit/Delete Donation
  content.
• Process 14,15,16 Add/Edit/Delete Calendar event
  content.
• Process 17,18,19 Add/Edit/Delete RSS News Feed.
• Process 20,21,22 Add/Edit/Delete Event Calendar
  content.
• Process 23 Publish the Website finally.
• Maintainer
• Maintains the system.
• Process 6,9,15,18,20

54
Processes

• Thai CDC Staff
• All above process except publishing the Website
  i.e. process 23.

55
Use case Diagram
56

• Modes of Operation
• The system does not require change of modes in
  operation hence system operates only in a single
  mode which is the execution mode with the
  standard configuration.

57
Life Cycle Plan

• -Nipun Bhandari

58
What does Life Cycle Plan present

• Demonstrates overall strategy in order to
  maximize productivity of stakeholders and
  resources
• Identifies roles and responsibilities of all the
  stakeholders
• Plans and reviews all tasks milestones to be
  completed at the end of each phase
• Monitors and controls the progress of project
  during various stages
• Allows to estimate analyze schedule and size of
  each project module

59
Life Cycle Stages

• Engineering Stage (CSCI 577a)
• Inception Phase
• Elaboration Phase
• Production Stage (CSCI 577b)
• Construction Phase
• Transition Phase

60
Overall Strategy

• Overall Approach
• COTS Based
• Process Model Implemented
• WinWin Spiral Model
• 24 weeks schedule
• Risk Management

61
Deliverables

• Engineering Stage

62
Deliverables

• Production Stage

63
Approach

• Monitoring and Control
• Weekly Microsoft Project Plan
• Weekly Client Meeting Report
• Weekly Progress Report
• Weekly Effort Report
• Regular team meeting
• DART Tool (Risk Management)
• Yahoo Group for Team3 Thai CDC project

64
Approach (contd.)

• Methods, Tools and Facilities
• Engineering Stage

65
Approach (contd.)

• Methods, Tools and Facilities (contd.)
• Production Stage

66
Responsibilities
67
MS Project So Far
68
MS Project Plan Later in 577a
69
MS Project Plan 577b (Expected)
70
A look at 577b Team Essentials

• Good knowledge of CMS Tool and project
  requirements.
• Good development ability and knowledge of PHP,
  MySQL database
• Approximately 5 Hours per month of maintenance
  required for updating the website

71
COCOMO Cost Effort Estimation
72
COCOMO Cost Effort Estimation

• Person-Months
• 10.8
• Months 1.54

73
Feasiblity Rationale Description

• -Lakshmi Kodali

74
Feasibility Rationale Description

• Outline
• Business Case Analysis
• Cost Analysis
• Benefits Analysis
• Return on Investment (ROI) Analysis
• Process Feasibility
• Risk Analysis
• Traceability Matrix

75
Business Case Analysis

• Costs Analysis
• Software Cost 0.00
• Hardware Cost 0.00
• COTS Product cost 0.00
• Personnel cost is only time client spends on
  this project

76
Personnel cost
77
Maintenance Costs (Annually)
This cost includes updation and Maintenance cost
of Content Management Tool and database by Thai
CDC.
Note All values based on assumptions with
present knowledge.
78
Benefit Analysis

• Quality of website upgrade.
• Multimedia News and level of service
  enhancement.
• Better publicity of events.
• Larger market for Thai CDC products.
• Easy access to Donors.
• Volunteer tracking system
• East Hollywood Publicity indirect Benefits
• Saving of Ads in News Paper about job openings
• And many other benefits.

79
Benefit Analysis

• Hours saved
• Hours saved because of the easy maintenances of
  the
• website is 40 Hrs per Month.
• ( i.e. is the no. of more hours Thai CDC
• had to invest in maintaining the system if it
  didnt have the
• content managements system we are giving to
  them).
• Total Annually is 4012 480Hrs
• Note All values based on assumptions with
  present knowledge.

80
ROI Analysis
Note All values based on assumptions with
present knowledge.
81
ROI Analysis
82
Process Feasibility
83
Process Feasibility
84
Risk Analysis

• Risk 1 Personnel Shortfall
• Risk 2 Less time for construction
• Risk 3 COTS Integration
• Risk 4 Inflexibility in schedule
• Risk 5 Lack of Web Domain Expertise

85
Traceability Matrix
86
Defects Identification

• Early OCD, Prototype, LCO Draft
• Peer Reviews, TA Feedback, Agile Artifact Reviews

87
COTS Analysis

• This project involves the use of COTS packages.
• Connector manages component (including COTS)
  communication

88
COTS Analysis (Cont.)

• COTS packages used in this project
• Drupal Version 5.2.
• Database server MySQL 5,
• Apache web server (version 2.36)
• Connectors used in this project
• MYSQL Connector/PHP

89
Glossary

• The Thai Community Development Center was
  founded in April 1994 on
• the idea that all peoples have a basic right to a
  decent standard of living and
• quality of life. Website http//thaicdc.org/
• Editor Thai CDC staff. The person has the
  rights to create/Edit/Delete the
• website using the Thai CDC software tool.
• This is the same as Creator.
• User Thai CDC staff. The staff has the right
  to use the software tool to
• create and edit the website.
• Drupal (Content Management System)
• Drupal is an open source content management
  system which is used to
• organize content on the website. Website
  http//drupal.org/
• SID Supporting Information Document as
  defined in LeanMBASE
• OCD Operational Concept Design

90
References

• LeanMBASE Guidelines version 1.9
• http//greenbay.usc.edu/csci577/fall2007/site/guid
  elines/LeanMBASE_Guidelines_V1.9.pdf
• LeanMBASE Version 1.9 Templates for FRD
  http//greenbay.usc.edu/csci577/fall2007/site/guid
  elines/LeanMBASE_v1.9_templates_for_FRD.doc
• Win-Win Negotiation Report, Team 3
  http//greenbay.usc.edu/csci577/fall2007/projects/
  team3/LCO/WikiWinWin_Report_F07_T03.doc
• Minutes of the Client I http//greenbay.usc.edu/
  csci577/fall2007/projects/team3/CMN/client_meeting
  1.doc
• Minutes of the Client II
• http//greenbay.usc.edu/csci577/fall2007/projects/
  team3/CMN/client_meeting2.doc

91
Continued..

• Minutes of the Client III
• http//greenbay.usc.edu/csci577/fall2007/projects/
  team3/CMN/client_meeting1.doc
• Wikipedia Website
• http//www.wikipedia.org/
• Operational Concept Description (OCD) for LCO
  version 1.0, Team 3 http//greenbay.usc.edu/csci57
  7/fall2007/projects/team3/LCO/OCD_LCO_F07a_T03.pdf
  
• System and Software Architecture Description
  (SSRD) for LCO version 1.0, Team 3
• http//greenbay.usc.edu/csci577/fall2007/projects/
  team3/LCO/SSRD_LCO_F07a_T03_v1.0.doc

92

• Thank You.