System
Team E-Mentoring #16
02/15/2008
Agenda
Introduction Test/ Peer Review Plan OCD & Prototype & SSRD System Architecture Life Cycle Plan Feasibility Rationale Quality Management Iteration Plan Things Done Right!
Introduction
Project name: E-Mentoring Client: Los Angeles Urban League
Development Team
Chen Zhao
Project Management, Feasibility Rationale, Life Cycle Planning
Bruno Samuel
Quality Management
Chen Wei Ma
System Development
Tan Liu
Requirements Management, Operational Concept
Philip Wong
Architecture Design, System Development
Carlos Rosario
Independent Verification & Validation
Testing Plan and Cases
Carlos Rosario
Contents
1
Test Cases
3 2
Testing Goals
3
Acceptance Testing
Test Cases
Test Cases are thoroughly described so the tester will not miss anything
Testing will ensure
Information provided in deliverable will be correct No sensitive information will be passed through the wrong parties All functionality described in win win negotiations works as described in artifacts The system will be consistent across multiple browsers
Testing will conclude
Testing will continue throughout the semester as new iterations of the system arise Every unit will continually need to be tested Testing will be done by the QMP, IV&V and Project Manager Testing will be done concurrently with the client for acceptance testing
Peer Review Plan
Carlos Rosario
Contents
1
Immediate Review
3 2
Artifacts to Review
3
Peer Review Roles
Immediate Review
RLCA 577B Transition Place in Life Cycle
Artifacts to Review
OCD SSAD UML SSRD LCP FRD QMP Transition Plan Test Plan and Cases Iteration Plan
Peer Review Roles
All team members will be expected to participate in peer review The author must keep reviewers informed on artifact status The team leader must ensure artifact distribution The specific reviewer (QMP, IV &V, Team Leader, Client, etc.) must review the artifact Reviewers must complete review logs Reviewer must ensure delivery of review to author Author must complete suggested changes
OPERATIONAL CONCEPT REQUIREMENTS PROTOTYPE
Tan Liu Chen Wei Ma
Changes in OCD
Filled in the TBDs for Success Critical Stakeholders (Administrator & Maintainer). Changed key stakeholders for 577b Changed the System Boundary Diagram. Changed the Element Relations Added the References & Changed the Background color of the Figures
Project Vision
Mentoring Aid Mentee Apprising Reduce Dropout Rate Galvanize Relationship between Students, Teachers & Parents
Changes in Current System & Deficiency
Changes in Current System
Eliminates the need of Physical Presence. The Communication can be made through Discussion Board or Personal Messages which are automatically saved. Web Based E-mentoring System which requires Internet to connect to the system.
Deficiency
Mentee might get a delay in response.
Proposed New System
Eliminates the need of Physical Presence Mentee & Mentor can interact Privately and Publicly Notification of Messages and Schedule Updates
System Benefits Chain
System Boundary
Desired Capabilities and Goals
Capability Goals
Communication via Personal Message & Discussion Board Email Notification Services Scheduler (To-do list & Sharing Calendar Events) Security Levels Usable
Level of Service Goals
System Response Time 10 Seconds Reusability 50% of the Code Reliability 99.99% of Operational Time Concurrent Use 50 Users
Contents of SSRD
Project Requirements Capability Requirements System Interface Requirements Level of Service Requirements Evolutionary Requirements
Project Requirements
24 weeks schedule Zero Budget Delivery on CD Open to Modification (S) Well documented (S) Commented Code (S) DART Tool Weekly Effort Reports
UML ASP.NET (S) Dell PowerEdge (S) MS SQL Server 2005 (S) Windows Server 2003 Backup Server (S)
Capability Requirements
Priority
CR8- Personal Message CR9- Tools Links CR10- User Calendar CR11- To-Do List CR12- Error Page CR13-Delete Confirmation CR14-Email Notification
M (Must Have) M (Must Have) S (Should Have) S (Should Have) S (Should Have) S (Should Have) M (Must Have)
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, Oct 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Math Midterm Review, due 12 days ago On Going Tasks: Science Homework 4, due in 1 hours Literature Homework 3, due in 3 hours Literature Homework 4, due in 10 days Math Homework 4, due in 15 days Science Presentation, due in 26 days Science Homework 4, due in 1 month
Comming Tasks: Notes Literature Final Review, begin in 1 month Select a task to view or edit the note Literature Homework 4, begin in 3 hours Math Final Review, begin in 3 days Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Text
Task View Subject Literature Literature Literature Literature Science Science Science Science Math Math Math
Time Line Task Homework 3 Homework 4 Homework 5 Final Review Homework 4 Presentation Midterm Review Final Review Homework 2 Midterm Review Final Review Begin Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Add
Remove
Due Date 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008 12:00pm Dec. 15th, 2008
Tasks of Today:
Friday, February 15th, 2008
User: Peter Kirschner
Logout
Over Due: Literature Homework 3, due 5 hours ago Science Homework 4, due 3 hours ago On Going Tasks: Science Homework 4, due in 3 hours Science Homework 4, due in 3 hours Science Homework 4, due in 3 hours Science Homework 4, due in 3 hours Science Homework 4, due in 3 hours Science Homework 4, due in 3 hours
Comming Tasks: Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours Science Homework 4, begin in 3 hours
Notes
Select a task to view or edit the note
Text
Task View Literature Physics History Math Science CSCI577 Science Science Science Science Science
Time Line Feb March
Add
Remove
April
Homework 1 Homework 4 Homework 4 Midterm Review Midterm Review Presentation Midterm Review Midterm Review Midterm Review Midterm Review Midterm Review
Capability Requirements
Priority
CR1- Account Creation CR3- User Authentication CR5- User Authorization CR6- User Profile CR7- Discussion Board
M (Must Have) M (Must Have) M (Must Have) M (Must Have) M (Must Have)
Discussion board prototype: COTS
Capability Requirements
Priority
CR8- Personal Message CR9- Tools Links CR10- User Calendar CR11- To-Do List CR12- Error Page CR13-Delete Confirmation CR14-Email Notification
M (Must Have) M (Must Have) S (Should Have) S (Should Have) S (Should Have) S (Should Have) M (Must Have)
User Calendar prototype: COTS
Capability Requirements
Priority
CR8- Personal Message CR9- Tools Links CR10- User Calendar CR11- To-Do List CR12- Error Page CR13-Delete Confirmation CR14-Email Notification
M (Must Have) M (Must Have) S (Should Have) S (Should Have) S (Should Have) S (Should Have) M (Must Have)
Tool Links Prototype
Capability Requirements
Priority
CR8- Personal Message CR9- Tools Links CR10- User Calendar CR11- To-Do List CR12- Error Page CR13-Delete Confirmation CR14-Email Notification
M (Must Have) M (Must Have) S (Should Have) S (Should Have) S (Should Have) S (Should Have) M (Must Have)
Delete Confirmation Prototype
System Interface Requirements
IR-1: Color Theme (S) SR-1 Future Compatibility (S)
Level of Service Requirements
Priority
LOS-1 System Reliability LOS-2 Concurrent Use LOS-3 Response Time LOS-4 Expandability LOS-5 Reusability
S (Should Have) S (Should Have) S (Should Have) S (Should Have) S (Should Have)
Evolutionary Requirements
ER-1 User Authentication Security Support (W)
Prototype Conclusion
Almost the same as what client need The most significant change from LCO is applying COTS No change on visitor/guest webpage
System and Software Architecture
Philip Wong
Outline
System Structure Diagram Deployment Diagram System Information Model COTS Selections Remaining COTS Decisions Remaining Issues
System Structure Diagram
ROI
6 5.519114688 5 4.496183206 4
3
2.737024221
2 1 0 First year -1 -2 -1 Second year Third year Fourth year
ROI = Cum(B-C)/C
Deployment Diagram
System Information Model
COTS Selections
COTS Product
COTS Type Scheduling Tool (Calendar) VCalendar Discussion Board
Website Status http://www.vcalendar .org/site/ SELECTED http://www.codeproje ct.com/aspnet/Jump JumpyForum yForum.asp SELECTED
Remaining COTS Decisions
COTS Product DotNetOpen Mail SharpOpen Mail
COTS Type Email Email
Website Status http://dotnetopenmail UNSELECT .sourceforge.net http://anmar.eu.org/p ED rojects/sharpwebmai UNSELECT l ED
Remaining Issues
COTS Selection for Personal Messages and Email Notification. Integration of remaining COTS selection with existing system.
LIFE CYCLE PLAN
Chen Zhao
Status
Issues Solved:
Only three members of our team will continue to 577b, so the new team members have to take some time to get familiar with this project. One more continuing member +Two new members joined the team!
Responsibilities
Team Member / Role Chen Zhao Project Manager & Feasibility Analyst Primary / Secondary Responsibility Inception Primary: Analyze project business case. Control project progress. Conduct risk management. Primary author of FRD and Quality Management. Secondary: Review and refinement for OCD. Primary: (IV & V ) i.e., verification and validation Secondary: Help out in project plans and progress reports. Elaboration Primary: Analyze project business case. Control project progress. Conduct risk management. Primary author of FRD and Quality Management. Secondary: Maintenance and Enhancements to the OCD Primary: (IV & V ) i.e., verification and validation Secondary: Help out in project plans and progress reports. Construction Primary: Monitor and Control construction progress. Risk management. Feasibility Rationale. Secondary: Life cycle planning. Primary author of FRD, LCP and SID. Primary: (IV & V ) i.e., individual verification and validation. Primary author of TPC, PRP. Secondary: Testing. Transition Primary: Transition progress monitor and control. Secondary: Supervise testing, installation and deployment
Carlos Rosario (IV&V) Verifications and Validation.
Primary: (IV & V ) i.e., verification and validation Secondary: Testing.
Responsibilities (cont.)
Team Member / Role Bruno Samuel (during construction and transition phase) Quality Focal Point N/A N/A Primary / Secondary Responsibility Inception Elaboration Construction Primary: Make the Quality Management Plan and the Iteration Plan. Primary author of QMP, IP. Secondary: Quality Assurance and Testing Transition Primary: Communicate with Customers to review transition progress. Secondary: Exit criteria reviews.
Responsibilities (cont.)
Team Member / Role Chen Wei Ma (during construction and transition phase) Developer Primary / Secondary Responsibility Inception Elaboration Construction Primary: Development of system components. Detail design of the system. Secondary: Quality assurance. Integration and Testing of the system. Transition Primary: Installation and deployment. Secondary: Transition testing.
N/A
N/A
Responsibilities (cont.)
Team Member / Role Philip Wong System Architect & Developer Primary / Secondary Responsibility Inception Primary: Design architecture for the proposed system. Provide alternative solutions. Primary author of SSAD. Secondary: UML modeling. Elaboration Primary: Further analysis of the system architecture. Complete all details of the system architecture as well as propose architecture for the team to commit to. Primary author of SSAD. Secondary: UML modeling. Construction Refine Primary: system architecture. Primary author of SSAD. Development of system components. Programming assistant Secondary: Documentation of API and produce test and iteration plans. Transition Primary: Programming assistant Supervise installation and deployment Secondary: Transition testing.
Responsibilities (cont.)
Team Member / Role Tan Liu Requirement Analyst Primary / Secondary Responsibility Inception Primary: Understand Customer requirement. Analyze requirements and report in SSRD. Secondary: Review and refine supportive information documents (SID) Elaboration Primary: Continue to review and refine project and system requirements. Primary author of SSRD. Secondary: Review and refine supportive information documents (SID) Construction Primary: Requirements management and document maintenance. Primary author of SSRD. Refine OCD. Secondary: Component development. Transition Primary: Exit criteria reviews. Secondary: Communicate with Customers to review transition progress.
Project Schedule
Construction Phase Schedule
Construction Phase Schedule
RLCA Package and Construction Planning
Construction Phase Schedule
Construction Phase Schedule
Development
Construction Phase Schedule
Transition Phase Schedule
Project Deliverables
CSCI 577b
Project Deliverables(Cont.)
CSCI 577b
Approaches
Monitoring and Control Team website Weekly Progress Report Weekly MS project plan Weekly Effort Report DART Risk Management Team meetings Client meetings Google group for the project
Methods, tools and Facilities
Tool
LeanMBASE Guidelines version 1.9 LeanMBASE Templates Easy Win-win tool COCOMO II MS Project 2003 DART IBM Rational Software Architect iCard FileZilla Firefox Visual studio SQL Server Windows Server 2003 Dreamwaver IE Microsoft office Adobe Acrobat
Source
USC CSSE USC CSSE USC CSSE USC CSSE USC USC CSSE IBM Website USC CSSE USC USC CSSE Microsoft Microsoft Microsoft Macromedia Microsoft Microsoft Adobe
Usage
Reference material for documents Template for the documents Win-win negotiate with clients and collect the requirements Schedule and estimate for the cost of the project Life Cycle Plan for the project Add, Edit and vote for risks and manage risks. UML modeling Record the weekly effort for every one in the team Upload and down files to the greenbay server View and download files from project website Develop the prototype Database server for the project Platform on which to build the project Develop the website for the project View and download files from project website Documentation for the project Documentation for the project
COCOMO Estimation (LCA before)
COCOMO Estimation (RLCA updated)
Updated Cost Driver Personnel Continuity
Very Low Very High
Language and tool Experience
Low Very High
FEASIBILITY RATIONALE
Chen Zhao
Business Case Analysis
Cost Analysis Benefit Analysis ROI (Return on Investment)
Cost Analysis
Software and Hardware Costs Personnel Costs
Software and Hardware Costs
Type Hardware cost for Dell Power Edge desktop as Web server Software cost for Dreamweaver Cost Free Rationale Client side has already obtained the desktop before. Trail version of Dreamweaver only used for initial prototype with no dynamic function. Obtained by client Obtained from client Obtained from client Open source software will be used for development, which is free. Open source software will be used for development, which is free.
Free
Software cost for MS Windows Server 2003 Software cost for MS Visual Studio 2005 Software cost for MS SQL Server 2005 Software cost for source code to integrate discussion board component in the system Software cost for source code to integrate calendar component in the system
Free Free Free Free
Free
Personnel Costs
Activity Time spent
Inception & Elaboration Phase (CS577a, 12 weeks)
Time spent by client (include meeting, email, and other communication time) = 3hrs/week x 12weeks Time spent on WikiWinWin tutorial = 1.5hr Time spent on WikiWinWin negotiation = 1.5hr/session x 2sessions 3 Client representative (include meeting preparation and document review) = 3hrs/week x 12weeks Time spent on LCO ARB (Architecture Review Board) 36 hours 1.5 hour 3 hours 36 hours 9 hours
Construction & Transition Phase (CS577b, 12 weeks)
Time spent by client (include meeting, email, and other communication time) = 3hrs/week x 12weeks Maintainer (include meeting preparation and code review) = 10hrs/week x 12weeks Time spent on LCA ARB (Architecture Review Board) Deployment of system in transition phase + training 36 hours 120 hours 9 hours 30 hours
Total (Development) Maintenance (per year)
277.5 hours 156 hours
Benefit Analysis
Current work
10 high school faculty spend 5hour/week communicating with students to decrease the school dropping rate (36 school weeks) 200 high school students spend 3 hours/week getting instructions of both academic and normal life (36 school weeks) 200 parents spend 1hour/week monitoring the study status of their children (36 school weeks) Time spent on LCO ARB (Architecture Review Board) 1800 hours/year
21600 hours/week
7200 hour/year
9 hours
Time Saved
Reduce 10% of school faculty work load (1800 x 0.1) Reduce 5% of students time of getting instructions (21600 x 0.05) Reduce 5% of parents time of monitoring their children (7200 x 0.05) 180 hours/year 1080 hours/year 360 hours/year
Total time saved by the new system
1620 hours/year
ROI Analysis
Effort Expended Effort Saved Cum. Net Cost ( C ) Cum. Net Benefit ( B ) ROI = Cum(B-C)/C
First year Second year Third year Fourth year 277.5 156 156 156 0 1620 1620 1620 277.5 433.5 589.5 745.5 0 1620 3240 4860 -1 2.737024221 4.4961832 5.51911469
Breakeven Point Summary
ROI
6 5.519114688 5 4.496183206 4
3
2.737024221
2 1 0 First year -1 -2 -1 Second year Third year Fourth year
ROI = Cum(B-C)/C
COTS Analysis
MS SQL Server 2005
Database
MS Windows Server 2003
HTTP Server
Graphical User Interface
IE Firefox
COTS
Discussion Board Jumpy Forum Calendar VCanlendar
Risk Assessment
Complex features and intense schedule Potential COTS Incompatibility Unfamiliarity with the LeanMBASE Special target users (9-grade students) Communication Gap (Two culture problem) People Shortfall X
Quality Management Plan
Bruno Samuel
Contents
1
Goals
3 2
Strategy
3
Configuration Management
Goals
1. Usefulness: We define Usefulness of E-Mentoring application as the degree of appreciable value of replicating or simplifying existing complex or tedious business workflows or combination of processes in achieving the desired goal in a substantial degree of accuracy. This speaks not only to the ability to capture proper business process flows but also the accuracy of translate them into technical feature-set solutions that deliver stakeholder groups goals. Quality can be seen here as a conformance to requirements. This will be backbone in gauging the worthiness of investment of resource, time, effort, and dollars in seeing this project successful. 2. Usability: We define Usability of E-Mentoring application as the degree of easiness experienced by the users in interacting, interfacing and working with the application. The Usability reflects the conformance to the Voice-ofthe-Customer. The Usability may consist of a mix of tangible product specifications as well as quality-of-service.
Quality Areas
Business Process Technology Implementation and Migration Documentation
Defect Prevention Strategies
Viewing software development within the context of the larger systems-level definition, design, and development. Global perspective Recognizing both the potential value of opportunity and the potential impact of adverse effects.
Thinking toward tomorrow, identifying uncertainties, anticipating potential outcomes. Forward-looking view Managing project resources and activities while anticipating uncertainties.
Encouraging free-flowing information at and between all project levels. Open communication Enabling formal, informal, and impromptu communication. Using processes that value the individual voice (bringing unique knowledge and insight to identifying and managing risk).
Making risk management an integral and vital part of project management. Integrated management Adapting risk management methods and tools to a project's infrastructure and culture.
Sustaining constant vigilance. Continuous process Identifying and managing risks routinely through all phases of the project's life cycle.
Mutual product vision based on common purpose, shared ownership, and collective communication. Shared product vision Focusing on results.
Working cooperatively to achieve common goal. Teamwork Pooling talents, skills, and knowledge.
Defect Prevention / Peer Review Chart
No Deliverable Primary Owner Secondary Owner Peer Review /Team Review Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/No Yes/Yes Yes/Yes Yes/Yes Yes/No Yes/No Frequency of Check
1 2 3 4 5 6 7 8 9 10 11 12 13 14
OCD FRD SSRD SSAD RSM LCP SID QMP Code UML Iteration Plan Project Plan Test Plan IV&V
Tan Liu Chen Zhao Tan Liu Philip Wong Philip Wong Chen Zhao Chen Zhao Bruno Samuel Chen Wei Ma Philip Wong Bruno Samuel Chen Zhao Carlos Rosario Carlos Rosario
Chen Zhao Tan Liu Philip Wong Chen Wei Ma Chen Wei Ma Philip Wong Chen Wei Ma Carlos Rosario Philip Wong Tan Liu Carlos Rosario Bruno Samuel Bruno Samuel Bruno Samuel
Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review Bi-weekly review
Defect Detection Strategies
Step 1: Risk/Defects Assessment (identifying what the risks/defects are and what to focus on) - making a list of all of the potential dangers that will affect the project - assessing the probability of occurrence and potential loss of each item listed - ranking the items (from most to least dangerous) Step 2: Risk/Defect Control (taking action) - coming up with techniques and strategies to mitigate the highest ordered risks - implementing the strategies to resolve the high order risks factors - monitoring the effectiveness of the strategies and the changing levels of risk throughout the project
Product Quality Focus Areas
Hardware/Software Preparation & Infrastructure Test Mentee Tests Mentor Tests Administrator Test
Defect Taxonomy
Risk/Defect Control Framework
Defect/Risk Ranking Very Low Low Automated Analysis Simple Complier syntax checking Basic compiler capabilities for static module-level code analysis, syntax, type-checking and traceability checking. Some compilers extensions for static module and inter-module level code analysis, syntax, type-checking. Basic requirements and design consistency, traceability checking Intermediate-level module and inter-module code syntax and semantic checking. No peer review Ad-hoc informal walk-through. Minimal preparation, no follow-up The author of the artifact reviews the document following the guidelines Well-defined sequence of preparation, review, and minimal follow-up. Informal review roles and procedures Another team member checks the artifact together with the author him/herself to ensure the correctness of the format and content. Formal review roles with all participants welltrained and procedures applied to all products using basic checklist, follow up. Peer Reviews No Testing Simple ad-hoc testing and debugging. Basic text based debugger. Basic unit test, integration test, system test process. Basic test data management, problem tracking support. Test criteria based on checklists. Execution Testing and Tools
Nominal
Well-defined test sequence tailored to Los Angeles Urban League (acceptance /alpha/beta/flight/etc) tests. Basic test coverage tools, test support system. Basic test process manageme...