Team10
Life REEODatabaseSystem Cycle Objective
Architecture Review Board Session Wednesday, October 24th 2007
10/24/2007
1
Introduction to Team 10
Kalyani Soniminde Operational Concept Descriptor Vishal Patel Project Manager and Prototyper Nirav Chheda- System Requirement Analyst Parag Shah- System Architect Swara Desai- Life Cycle Planner Samit Vyas- Feasibility Analyst
10/24/2007
Mark Dexter IV & V
2
Introduction to REEO
REEO is a nonprofit organization. Committed to empowering Community College students with the opportunity to transfer to a Four-Year University, to earn a college degree and Committed to obtain a professional position upon graduation by providing financial, educational and professional resources. Relies upon individuals, foundations, and corporations to provide financial contributions, as well as, donations of time, products and services. 100% of donations goes directly to REEO 's scholarship fund. Represented by : Scott Stimpfel Chairman of the Board, Director of Corporate Development
10/24/2007 3
Independent Verification and Validation
- Mark Dexter
10/24/2007
4
I V & V Analysis
Teams Strong Points Operational View - Team cohesion developed quickly. Effective in
understanding client needs and how to effectively use class supplied tools to achieve goal. Technical View Good understanding of database concepts, web site design, and programming logic required to effectively integrate COTS product.
Teams Weak Points Operational View Coordination of effective meeting schedule. With client
on the East Coast they have had to resolve many scheduling conflicts to remain effective and on track. Technical View Content Management System (CMS) recommended by client not well known by development team. Have been diligently working on overcoming this hurdle and understanding COTS product Joomla.
10/24/2007 5
I V & V Analysis
Technical Concerns
SSRD Requirements need to be clarified. Need to be refined and reworded. SSAD Use Case descriptions are inconsistent. Need to be refined for consistency. UML documentation Design model is incomplete and needs to be finished.
Operational Risks
Learning curve of Joomla could effect integration testing Handover of documentation to CSCI-577b team.
Sources of Observation
Package 10/24/2007 Evaluation, Win-Win negotiation, and Client Meeting Notes, and 6 discussions with Project Manager.
Operational Concept Description
- Kalyani Soniminde
10/24/2007
7
System Capability Description
A web-based content management system which will provide academic support and employment opportunities to the students and allow the corporate partners to browse through the student resume database to find potential candidates and post job openings. Unlike the current manual process of academic support and employment application, the proposed system will provide secured access granting privileges to users to automate the application process
10/24/2007 8
Expected Benefits
Provide large amount of information and services in an organized and user friendly manner from a single system Create online profiles the data will be stored automatically into the database. Hence automating the system and fastening the process. Provide fast and efficient searching based on keywords increasing the opportunities Provide social networking and chat room features which will increase the interactions among the college students Authenticate the user and accordingly grant user specific privileges securing the personal data. Simple web-based interface for creating and publishing the information Assist in better scheduling of the various events with community colleges partners Assist in their fund raising efforts
10/24/2007 9
Benefits Chain
REEO Staff, Students & Corporate partners Developer & IV&V Corporate partners, Students Students, Corporate partners
Develop a web based system
Develop new event scheduling & registration process
Develop new job posting & application process
Develop new networking process
Automated paperless system, Convenient UI Fast & efficient program
Scheduling Multiple events
Ample job opportunities available online
Increased interaction among students & exposure to corporate world
Online profile generation process
Improved event scheduling and registration process
availableonline
All Information
Central hub of communication and Data
Continuing event activities & increased no. of sponsors
Increased Productivity, Participants growth and raised fund
Provide secure interface, grant privileges
Efficient searching
Fast & easy notification Provides analyzing the data & generate statistical information
Develop new Search process Develop new authentication and validation process
System Admin REEO staff
Develop new email notification process
Student, Corporate partners, REEO staff
Provide Data Analysis process
REEO staff, students, corporate partners
10/24/2007
10
System Boundary Diagram
Student/ AlumniOf REEO Community College Partners
Internet
Executive Board
OnlineProfileSetup ActivityTracking EventScheduling
REEO Database
Volunteers (Sponsor)
EventNotification SocialNetworking/Chatroom ReportGenerator CustomizedSearching Authenticationandvalidation FileHandling JSP Web Interface
Academic Board
Corporate Partners
10/24/2007
System Admin
Apache
11
Capability Goals
OC-1: Central Hub of communication OC-2: User Login and Authentication OC-3: Online profile generation OC-4: Customized Searching OC-5: Event scheduling and registration OC-6: Job Posting and Scheduling OC-7: Email Notification and Reminders OC-8: Report Generation
10/24/2007
12
Element Relationship
10/24/2007
13
Comparison Of Systems
Current System
Diffused activities and data Manual overhead filling and maintaining student, corporate partners and community college information. Incompatible schedules between program and school schedule.
Proposed System
Centralized hub of information and activities Automated Process online profile setup. Organized data and less effort. Centralized online registration of events. Improved efficiency and time management. Improved communication Data Analysis and Report generation enabling better statistics , thus effective fund raising strategies.
14
Lack of communication Manually monitoring and tracking activities and inaccurate statistics and data analysis.
10/24/2007
Organizational Transformation
Proper dissemination of work among the REEO staff members as roles for each task will be assigned to the staff members. The reminder emails can be scheduled before hand and thus does not require the presence of the staff member. 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.
10/24/2007 15
Operational Transformation
An automated system which will replace all the manual operational procedures and workflow in the organization.
Need not interact with individual student or corporate partner or the community college partner. Need not publicize about the upcoming events
10/24/2007
16
Prototype Design
- Vishal Patel
10/24/2007
17
Prototype Design Agenda
REEO Prototype Design Goals Prototype Web Usability Checklist & Approach Win-Win Negotiation REEO Existing Website
Main Page Contact Us page
REEO New Website Design
Main Page Contact Us page Functionality page
Comparison of old and new website design
Main page Contact us page
Plan for rest of the semester
10/24/2007 18
REEO Prototype Design Goals
Users:
REEO Students REEO Staff Corporate Partners Displays only static information
REEO mission & governance REEO programs REEO contacts REEO Media Center REEO news Secured Web based data entry Job application system Searching system Social networking/ Chat rooms REEO news update
Existing Website:
No functionality available which can be beneficial to its users:
GOALS of the new REEO web-site design:
Display dynamic content GUI should be intuitive, user friendly & visually appealing Provide all functionality which will be beneficial to its users Should acts a common communication hub for all information & operations beneficial to its users 19
10/24/2007
Prototype Design: Web Design Usability Checklist Checklist (Reference: CSCI 588 Web Usability Handout)
Architecture & Navigation Layout & Design Content Forms & Interaction Graphics Color Typography Error Tolerance Platform & Implementation
Approach
JOOMLA CMS Templates used WYSIWYG
10/24/2007 20
Win-Win Negotiations - TWiki
Win-Win Negotiation Client Meeting Session 2
System Interface Win Conditions
User Interface Win Conditions
Easy navigation User Readability and Understandability Consistency in website
10/24/2007
21
REEO Existing Website Home Page
10/24/2007
22
REEO Existing Website Contact Us Page
10/24/2007
23
REEO New Website Design Main Page
10/24/2007
24
REEO New Website Design Contact Us Page
10/24/2007
25
REEO New Website Design Function Page
10/24/2007
26
Comparison of REEO Existing Website and New Website Design Main Page
10/24/2007
27
Comparison of REEO Existing Website and New Website Design Contact Us Page
10/24/2007
28
Plan for rest of the semester
Develop new prototypes according to clients requirement Review feedback from client & team members Refine existing prototypes incrementally based on feedback Improve the prototype graphically using existing or templates developing new templates
10/24/2007 29
Systems and Software Requirements Definition (SSRD)
- Nirav Chheda
10/24/2007
30
Requirements
Budget and Schedule Requirements Development Requirements Capability Requirements System Interface Requirements Level of Service Requirements Evolutionary Requirements
10/24/2007 31
Budget and Schedule Requirements
Schedule
Project Schedule = 12 weeks
Budget
Budget Allocated = Negligible
10/24/2007 32
Development Requirements
Modeling Tool IBM RSM Web Development Tools COTS CMS Joomla will be used Project Management MS Project, MS Excel Development Language PHP, MySQL Web Server Apache 1.3.x or above Test Server Open Source WAMP Server Transition Requirements Support Environment
33
10/24/2007
Capability Requirements
High Priority Requirements Central hub of information User authentication service Dynamic Calendar Event Registration Online Chat Profile Generation Job Application and Posting Report Generation Image Gallery Login Behavior Low Priority Requirements Document Upload Email Notification Reminder Email Customized Searching Website Behavior
10/24/2007
34
Joomla Plug-ins
Chat BlastChat Resume Upload Mjaz Tools Uploader for DOCman Events Calendar Thyme Image Gallery Photo Gallery with Slideshow/ FlickUr Pic Pro Search Joomla Search Registration Form Security Registration
10/24/2007
35
System Interface Requirements
Consistency Readability Display of Sponsors Easy Navigation Linkage Requirement Network Interface
10/24/2007 36
Level of Service Requirements
Maximum Availability System Integrity COTS Product Verification Easy Usability Response Time Flexible UI design Reusability Protection of personal information
37
10/24/2007
Evolutionary Requirements
Capability Requirement
Extension for media streaming
10/24/2007
38
System and Software Architecture Description (SSAD)
-Parag Shah
10/24/2007
39
The BIG question!
Why have an Architecture Design for a COTS project?
COTS Architecture Tried to map the COTS features as Use-cases
10/24/2007
40
Operational Stakeholders and the System
10/24/2007
41
Hardware Deployment Structure
10/24/2007
42
Web Server Software Structure
10/24/2007
43
Modes of Operation
System Administrators
For managing content
Front End Interface
Each actor has a different screen
10/24/2007
44
Life Cycle Plan
- Swara Desai
10/24/2007
45
LCP Purpose
Presents the overall strategy Identifies the roles and responsibilities of all the stakeholders Plans all the tasks and milestones to be met at the end of each phase Presents an analysis of cost, complexity and size of each module Controls and monitors the projects progress
10/24/2007
46
Overall Strategy
Overall approach COTS Based Win win Spiral Model
Incremental process Schedule of 24 weeks
10/24/2007
47
Deliverables
Deliverable
Early OCD
Delivery Date
09/24/2007
Delivery Medium
Softcopy
Prototype
10/05/2007
Softcopy
LCO Core
10/10/07
Softcopy
LCO Draft
10/17/07
Softcopy
LCO Package
10/29/07
Softcopy
LCA Draft
11/28/07
Softcopy
LCA Package
12/10/07
Softcopy
10/24/2007
48
Project monitor and control mechanism
MS project plan Weekly Client Meeting Report Weekly Progress Report Regular team meeting Weekly Effort Report DART (Risk management)
49
10/24/2007
Team member Vishal Patel
Role
Responsibilities
Inception Elaboration Same as inception Project Management. Prototype OCD. Shaper Same as inception
Construction Code, Testing, Review
Transition Document user manual/Maintena nce support/testing Document user manual/Maintena nce support/testing Document user manual/Maintena nce support/testing Maintenance support/testing Development support/ modify as per changes/ ROI analysis Maintenance support/testing/ Modify as per 50 changes
Project Manger, Prototyper
Kalyani Soniminde
Operational Concepts Engineer
Review/ Integration
Nirav Chheda
Requirement Analyst
SSRD
Same as inception
Testing/ Review
Parag Shah
System Architect
SSAD, UML
Same as inception COTS assessment, FRD Same as inception
Implementation/ integration Implementation/ integration/ ROI analysis Apply LCPs to development stage. Plan for transition
Samit Vyas
Feasibility Analyst
FRD, SID
Swara Desai
Life Cycle Planner
LCP, learning facilitator
10/24/2007
577b Team Essentials
In-depth knowledge of the project, requirements, and COTS chosen Moderate familiarity with CMS and COTS Good command over PHP, MySQL Moderate to good development ability Maintenance: negligible, but considerate if COTS product has a new version
10/24/2007 51
Cocomo tool: Resource Estimation
10/24/2007
52
Planned Resources Allocation
Estimated effort: 9.9 person months (pessimistic estimate) 120 hours per month 6 developers
10/24/2007
53
Feasibility Rationale Description
- Samit Vyas
10/24/2007
54
Feasibility Rationale Description
Outline
Business Case Analysis
Cost Analysis Benefits Analysis Return on Investment (ROI) Analysis
Process Feasibility Risk Analysis Traceability Matrix
10/24/2007 55
Costs Analysis
Business Case Analysis
Software Cost : Negligible Hardware Cost : Negligible COTS Product cost : Negligible Personnel time is the only cost to the client.
10/24/2007
56
Personnel cost for development phase
A 1 2 3 4 5
Business case analysis
Hours 36 Hours 4 Hours 18 Hours 6 Hours 14 Hours 78 Hours
Inception and Elaboration Time Invested (CS577a) Meeting with Full team & Individual members (3 hours per week x 12 weeks) Win-Win negotiation meetings (2 x 2hours) Email time (1.5 hrs per week x 12 weeks) Architecture Review boards Document Preparation Total (Inception and Elaboration Time Invested (CS577a))
...