Operational Concept Description
Upcoming SlideShare
Loading in...5
×
 

Operational Concept Description

on

  • 1,138 views

 

Statistics

Views

Total Views
1,138
Views on SlideShare
1,138
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Operational Concept Description Operational Concept Description Presentation Transcript

  • Team 6 Fall 2003 – LCA ARB Presentation
    • Online Help/Tutorials for LAPK Software
      • 25 th Nov 2003
  • Operational Concept Description (OCD)
    • current version : v2.2
    • Siddharth Thakkar
      • team 6 – csci577a Fall 2003
      • author : FRD
      • team role: System Architect
  • Progress from LCO to LCA Stage
    • Minor changes caused by:
      • LCO ARB Comments
      • Corrections after LCO Package Grading
      • Corrections after Agile Review done before LCA ARB
        • Reference: Agile Internal Review Document for LCA ARB Version of OCD
      • Corrections and Finalization for LCA version
  • 2.1.2 Results Chain
    • Changes
      • Included More Initiatives based on LCO Package Review
      • Corresponding intermediate results and final outcomes matching the Organization Goals were identified
  • Updated Results Chain
  • 2.3 System Boundary and Environment
    • Changes
      • Removal of csci577a Team 6 as an Actor from the diagram
    • New Diagram =>
  • 3.2 Organization Goals
    • Changes
      • Corrected the Measurable for each Organization Goal after Client’s approval for each numeric values
    • New Contents
      • Project should lead to
        • approximately more than 10% increased sales/distribution and positive end-user feedback for the LAPK Software (measured per Year)
        • more than 10% increase in end-user productivity and positive feedback regarding ease of use of the new help system. (measured per Month of use of software)
        • More than 15% reduction in support-overhead (in form of technical-service/support calls and emails because of the new help methods. (measure Annually)
  • 3.3.1 Current Organization Structure
    • Changes
      • Removal of LAPK Help Manager Actor
    • New Diagram
  • 3.3.3 Current System Processes
    • Changes
      • Elimination of LAPK Help Developer (577a Team) since that was an representation-error
      • LAPK Software Developers themselves responsible for maintaining the current software-help artifact
    • New Diagram =>
  • 4.2 Project Goals and Constraints
    • Changes
      • Many previous PGs where actually capabilities and not top-level project goals
      • Moving a few old incorrect PGs to Project Constraints subtopics.
    • New Goals
      • PG-1 Structuring of Help Information
      • PG-2 Long term solution for an easy software help content-management system
    • New Constraints
      • PC-1 Limited Schedule
      • PC-2 Limited Dollar Budget
  • 4.4 L.O.S. Goals
    • Changes
      • Elimination of previously incorrect L.O.S. Goals
    • New Contents
      • This system being very simple, no rigid Level of Service goals have been recommended by the Clients (LAPK Personnel) or identified by the Team 6 members.
        • Reference: TA’s review on the LCO OCD
  • 4.5.1 Proposed Organization Structure
    • Changes
      • Simplified and corrected previous UML Diagram
      • Identification of LAPK-Help Administrator as an new Business Worker role
    • New Diagram
  • 4.5.3 Proposed System Processes
    • Changes
      • Addition of Activity Diagrams for Each Processes idenfied
    • New Contents
      • Diagrams as shown in next few slides
      • Please refer to the OCD Document to see all the detailed Activity Diagrams
  • 4.5.3 Proposed System Processes (continued)
    • Activity Diagram – Use Discussion Forums
  • 4.5.3 Proposed System Processes (continued)
    • Activity Diagram – Search Help Manual
  • 4.5.3 Proposed System Processes (continued)
    • Activity Diagram – View Tutorial Videos
  • 4.5.3 Proposed System Processes (continued)
    • Activity Diagram – Browse the Help System
  • 4.6.1 Operational Stakeholders
    • Changes
      • Identification and Addition of Operational Stakeholders based on MBASE Guidelines v2.4
    • New Contents
      • LAPK–Software User
      • LAPK–Help Administrator
    Intermediate Technical expertise – able to refer to technical documents and utilize them to understand and update the Help system. Also able to use technical hardware and software tools and programs to administer the Help system. Expected Expertise Assumption High frequency – The frequency of updates depend on the frequency with which new modifications are suggested or identified, or when a new LAPK Software feature is released. Frequency of usage Assumption Update Help Data Major Activities Performed Highly varying expertise level – includes naïve users to highly expert users like researchers in the field of Pharmacokinetics Expected Expertise Assumption High frequency (multiple times per day) Frequency of usage Assumption Browse the Help system, Search the Help information, View Help Multimedia, Send Emails, Use Discussion Forums Major Activities Performed
  • Team 6 – Online Help and Tutorials for LAPK
            • THE END!
            • Open Discussion
            • THANK YOU ALL!
  • Prototype
    • current version : v2.2
    • karan s. chhina
      • team 6 – csci577a Fall 2003
      • author-of : OCD Sec 5, Prototype
      • team role: System Developer, Webmaster
  • Prototype Presentation Outline
    • Contents
      • Introduction
      • Details
      • Screenshots
      • Next Prototype
      • Conclusion
    • References:
      • SSRD v2.2
      • SSAD v2.2
      • Client Meetings - http://www-scf.usc.edu/~csci577/www/team6a/clntmeet.html
  • Prototype – Introduction
    • Modules:
      • Online Help
      • Navigation Tree Generator
      • Webpage Template
      • Online Search
      • Bundled Help
    • Purpose of this prototype
      • To show a functional Online Help module
      • Search in the Online Help
      • To propose the possible interface for the multimedia help
  • Prototype – Details (1)
    • Online Help Module
      • Functional prototype created
      • COTS tool used – Macromedia Dreamweaver
    • Navigation Tree generator
      • Generates the navigation tree
      • Links are provided to the corresponding HTML files
    • Webpage Template
      • COTS tool used – Macromedia Dreamweaver
      • Created a template to generate the HTML help pages.
      • Predefined fields for the maintainer to put in the relevant information
  • Prototype – Details (2)
    • Online search Module
      • Search module provided for the Online Help module
      • Implemented using “Google SiteSearch”
      • Search results displayed in bottom frame
    • Offline Help Module
      • COTS Product used – HTML Help Workshop
      • Functional prototype
  • Prototype – Details (3)
    • Functional Prototype – Bundled Help
      • Contents file generated
        • Hierarchical Navigation bar created for the contents
        • The help divided into headings
        • Each heading has sub-headings
      • Sample pages created from the template provided for the Online help module
      • Index file generated
        • Contains keywords used in the help files
        • Keywords linked to the respective pages
  • Prototype - Screenshots
    • Online Help – main screen
  • Prototype - Screenshots
    • Online Help – Search Function
    Online Search window showing the search result
  • Prototype - Screenshots Multimedia Help window showing the video being played in a different window 
  • Prototype - Screenshots Macromedia Dreamweaver template (.dwt file) Used to generate the help files
  • Next Prototype Logical diagram
  • Conclusion
    • Client meeting to get feedback on the prototype
    • Question?
  • System and Software Requirements Definition (SSRD)
    • current version : v2.2
    • Vikas Bansal
      • team 6 – csci577a Fall 2003
  • Changes in SSRD since the first ARB
    • Major Requirements
      • Project Requirements
      • Capability Requirements
      • System Interface Requirements
    • References:
      • SSRD v2.2
      • Team 6 WinWin Negotiation Report
  • Changes in Project Requirements
    • Budget and Schedule
      • Previous: Zero Dollar Budget
        • New: One time licensing for Macromemedia Dreamweaver.
      • Previous: Schedule is of 12 weeks
        • New: Schedule is of 24 weeks
    • Development Requirements
      • Tools requirement
        • New: Use of UML/Rose, MS Project for System Architecture design and LCP development
      • Computer Communication requirement
        • From 3 second online search to no requirement
  • Changes in Capability Requirements
    • System Requirements
      • Corrections as per Nominal and off-Nominal Requirements
    • Nominal -
          • Navigable Help Data
          • Using Index and doing Search through keywords and main topics
          • Use of Multi Language Support
          • Hyperlinks from Bundled help to launch Browsers
          • Linking of Audio/Video from CD
          • The online and the bundled versions of help should comply with each other.
          • Providing Index and facilitating Search through keywords and main topics.
          • Content-management system
          • Language supported by Apache Web Server
          • Printing of obtained Help
          • Web Conferencing
          • Broadcasting
          • F1 Key support
    • Off-Nominal
          • Discussion forum
          • Email facility for bug reporting for fixing dead URL’s, providing technical support to users.
  • Changes in System Interface Requirements
    • Communication Interface Requirement
          • Client-server model for multimedia help as previously identified as Email support
  • Level of Sevice Requirements
    • Level of Service has been removed from the requirement by the client
  • Thank You
    • Questions ?
  • SYSTEM & SOFTWARE ARCHITECTURE DESCRIPTION (SSAD)
    • current version : v2.2
    • Ashwin Sangtani
      • team 6 – csci577a Fall 2003
      • author : SSAD
      • team role: System Architect
  • SYSTEM ANALYSIS - Structure
  • Business Artifact Model
  • Behavior – Processes Use-Case Diagram
  • Process-Capability Process Capability Use Case
  • Process 1 – Browse through help system Activity Diagram for Browse Thru
  • Process-2 View Tutorials/ Videos Activity Diagram for Video/Tutorial
  • Process-3 Email Support Activity Diagram for Email Support
  • Process-4 Discussion Forum Activity for Discussion Forum
  • Process 5 – Update Help Content Update Help Content Activity Diagram
  • Process-6 Searching Searching Activity Diagram
  • ARCHITECTURE DESIGN - Topology System Topology
  • Hardware Classifier Model Hardware Classifier Model
  • Software Classifier Model Software Classifier Model
  • Deployment Model Deployment Model
  • H/W Component Classifier 1 - Server Interface - Webserver
  • Component Classifier 2–PC/Workstation Interface – PC/Workstation
  • S/W Component Classifier 1- Web Page Template Interface – Webpage Template
  • Component Classifier 2 – Navigation Tree Generator Interface – Navigation Tree Generator
  • Component Classifier – 3 Online Search Component Interface – Online Search
  • Component Classifier – 4 Bundled Help Interface - Bundled Help
  • Component Classifier – 6 User Feedback Interface - User Feedback
  • Analysis Classes Analysis Classes
  • Behavior – Process Realization Behavior – Process Realization
  • PR1 – Browse through help data Sequence Diagram - Browse
  • PR2 – Update Content Sequence Diagram – Update Content
  • PR3 – Discussion Forums Sequence Diagram – Discussion Forum
  • PR4 –Search Help Manual Sequence Diagram - Search
  • PR5 –Send Email Sequence Diagram – Send Email
  • PR6 – View Tutorial/Videos Sequence Diagram – View Tutorial/Video
  • Topology System Topology
  • Hardware Classifier Model Hardware Classifier Model
  • Software Classifier Model Software Classifier Model
  • Team 6 – Online Help and Tutorials for LAPK
            • THE END!
  • LIFE CYCLE PLAN DESCRIPTION (LCP)
    • current version : v2.2
    • nicunj sanghani
      • team 6 – csci577a Fall 2003
      • author-of : LCP
      • team role: System Anaylst
  • ASSUMPTIONS
    • Stable Requirements
    • Limited budget depending on grants available but client willing to pay max. $500 for 1 time license
    • Entering of content into the help systems will be done at LAPK after the development, integration and installation of the system and would not require effort from developers
    • The client will provide feedback and propose changes if any for the developed system in a timely fashion
    • The team members will be persistent in their efforts and will work at least 20 hours per week towards the development of the project .
    • Our team will not be responsible for the maintenance of the system
  • MILESTONES & PRODUCTS
    • For the inception and elaboration phases of the LAPK project the process model we are using is Win-Win Spiral model that helps us analyze the requirements, resolve risks, and identify the objectives for every spiral of the spiral model and plan the milestones to be met at every stage .
    • Another thing that made us select the win-win spiral model is that it is recommended by the csci577 educational staff and apart from that it works very well with the MBASE guidelines.
    • An IKIWISI approach is adopted to get the feedback from the clients by delivering them the prototype of actual system . All assumptions and hidden requirements were clarified through the use of prototype.
  • MILESTONES & PRODUCTS
    • For the 577b class we have 12 weeks and stable set of requirements which wont change over we will be using the incremental model which will be risk driven.
    • In the first increment all the high priority requirements will be implemented while the low priority requirements will be implemented in the second iteration.
  • MILESTONES & PRODUCTS
            • ENGINEERING STAGE
            • INCEPTION PHASE
            • Team Formation (09/05/03)
            • Project assignment (09/10/03)
            • First Team Meeting (09/14/03)
            • First Client Meeting (09/22/03)
            • First draft of the OCD and review (09/23/03)
            • Submission of the Early OCD and corresponding QR (09/24/03)
            • Second Easy Win-Win Negotiation -2 (09/26/03) .
            • Review of the Prototype (10/01/03)
            • Win-Win Report Submission (10/03/03)
            • . QR of the OCD (10/08/03)
            • LCO drafts put up on the website (10/12/03 .
            • QR of the Rose Model and SSRD (10/13/03)
            • LCO ARB (10/20/03) .
            • Completion of LCP (10/23/03)
            • Completion of SSRD (10/23/03)
            • Completion of SSAD (10/27/03)
            • Completion of Prototype (10/23/03)
            • Completion of FRD (10/23/03) .
            • Submission of the Quality Report of the SSAD(10/27/2003 .
            • LCO Packages submission (10/31/03)
  • MILESTONES & PRODUCTS
            • ENGINEERING STAGE
            • ELABORATION PHASE CYCLE 1
            • Team Meeting(11/01/03)
            • Team meeting with clients (11/06/03)
            • Completion of OCD DRAFT(11/07/03)
            • Team Meeting(11/07/03)
            • Completion of LCP LCA draft version(11/08/03)
            • Completion of SSRD LCA draft version (11/09/03)
            • Completion of SSAD LCA draft version (11/11/03)
            • Completion of Prototype LCA draft version (11/12/03)
            • Completion of FRD LCA draft version (11/14/03)
            • Team Meeting(11/14/03)
            • LCA Drafts put up on the website (11/15/03)
            • Team meeting with clients(11/16/03)
            • Team Meeting(11/18/03)
  • MILESTONES & PRODUCTS
            • ENGINEERING STAGE
            • ELABORATION PHASE CYCLE 1
            • Submission of the Quality Report of the SSAD,SSRD and OCD(11/25/2003)
            • LCA ARB presentation(11/25/03)
            • Team Meeting(11/26/03 )
            • Completion of OCD (11/26/03
            • Completion of LCP (11/27/03)
            • Completion of SSRD (11/28/03)
            • Completion of SSAD (11/30/03)
            • Completion of Prototype (12/1/03)
            • Completion of FRD (12/01/03)
            • Internal Informal Review(12/02/03)
            • Submission of the LCA packages (12/03/03)
            • Evaluation by the clients (12/12/03)
  • MILESTONES & PRODUCTS
            • ENGINEERING STAGE
            • ELABORATION PHASE CYCLE 2
            • New Team Formation (01/27/04)
            • Meeting with the clients (2/4/04)
            • Team meeting (02/08/04)
            • Team meeting (02/12/04)
            • Team meeting (02/16/04)
            • Started making the IOC Working Set#0 consisting of Peer Review Plan, Test Plan, Quality Management Plan and Iteration plan for the next iteration (02/17/04-2/20/04)
            • Architecture Re-baseline Review (02/20/04)
            • Team meeting (02/21/04)
            • Completion of OCD ((02/22/04)
            • Completion of LCP ((02/23/04)
  • MILESTONES & PRODUCTS
            • ENGINEERING STAGE
            • ELABORATION PHASE CYCLE 2
    • Completion of SSRD (02/23/04)
    • Completion of SSAD (02/24/04)
    • Completion of FRD (02/24/04)
    • Internal Informal Review (2/25/04)
    • Submission of the RLCA packages and IOC Working Set#0 (02/26/04)
  • PRODUCTION STAGE
    • CONSTRUCTION PHASE ITERATION#1
    • Team meeting (02/27/04)
    • Implementation of webpage template component(02/27/04-03/02/04)
    • Testing of the webpage template component(03/01/04)
    • Team meeting (03/02/04)
    • Team meeting with the client (03/03/04)
    • Implementation of Navigation tree generator component (03/05/04-03/07/04)
    • Team meeting (03/06/04)
    • Testing of the system developed until this stage (03/08/04)
    • Team meeting (03/09/04)
    • Team meeting with the client (03/10/04)
    • Implementation of Bundled Help component (03/11/04-03/14/04)
    • Team meeting (03/13/04)
    • Testing of the system developed until this stage (03/15/04)
  • PRODUCTION STAGE
    • CONSTRUCTION PHASE ITERATION#1
    • Team meeting with the client (03/16/04)
    • Team meeting (03/17/04)
    • Implementation of Online Search component(03/17/04-03/20/04)
    • Testing of the system developed until this stage (03/21/04)
    • Team meeting (03/21/04)
    • Team meeting with the client (03/22/04)
    • Implementation of User Feedback component (03/23/04-03/24/04)
    • Testing of the system developed until this stage (03/25/04)
    • Team meeting (03/26/04)
    • Team meeting with the client (03/28/04)
    • Core capability Drivethrough(03/30/04)
    • Review of the system and incorporation of all the changes suggested by client (3/29/04)
    • Documentation of Peer Review Report, Test Report, Iteration Assessment Report, Change Summaries for updates to the RLCA Packages and CCD Report.(03/30/04 )
    • Submission of IOC working set#1 and Core Capability Drivethrough(CCD) Report(3/31/04):
  • PRODUCTION STAGE
    • CONSTRUCTION PHASE ITERATION#2
    • Team meeting (03/31/04)
    • Beginning of implementation of low priority requirements (04/01/04)
    • Implementation of “presentation of various help using multimedia” feature(04/01/04-04/05/04)
    • Team meeting (04/04/04)
    • Testing of the system developed until this stage (04/06/04):
    • Team meeting with the client (04/08/04):
    • Team begins to develop the transition plan (04/09/14).
    • Team meeting (04/10/04
    • TRR drafts on the web (04/14/04)
    • User manual ,training materials ,regression test package and package tools and procedures, installation scripts preparation(04/15/04).
    • Transition Readiness Review (04/17/04)
    • Submission of IOC working set#2 transition plan and support plan.(04/19/04)
  • TRANSITION PHASE
    • Training of the clients and the LAPK Help administrators(04/20/04/-04/26/04)
    • Transitioning of the system into LAPK( 04/26/04/-04/30/04)
    • Release readiness review(05/02/04)
            • SUPPORT STAGE
            • Subsequent releases of the system (05/02/04-05/07/04
  • PROJECT DELIVERABLES
    • Inception Phase
    • Operational Concept Definition – Early Sections
    • Win-Win report
    • First Prototype
    • Individual Effort report
    • Progress report
    • Agenda and Minutes of Meeting
    • Weekly Model Clash Report
    • LCO package containing OCD,SSAD,SSRD,LCP,PROTOTYPE,FRD,
    • ROSE DIAGRAMS
    • Status report
  • PROJECT DELIVERABLES
    • Elaboration phase cycle 1
    • Individual Effort report
    • Progress report
    • Agenda and Minutes of Meeting
    • Weekly Model Clash Report
    • LCA package containing OCD,SSAD,SSRD,LCP,PROTOTYPE,FRD,
    • ROSE DIAGRAMS
    • Status report
    • Peer Review Plan
    • Quality Management Plan
    • Test Plan
    • Iteration Plan
  • PROJECT DELIVERABLES
    • Elaboration phase cycle 2
    • Individual Effort report
    • Progress report
    • Agenda and Minutes of Meeting
    • Weekly Model Clash Report
    • RLCA package containing OCD,SSAD,SSRD,LCP,PROTOTYPE,FRD,
    • ROSE DIAGRAMS
    • Status report
    • Peer Review Plan
    • Quality Management Plan
    • Test Plan
    • Iteration Plan
  • PROJECT DELIVERABLES
    • Production Stage Construction Phase Iteration1
    • Individual Effort report
    • Progress report
    • Agenda and Minutes of Meeting
    • Weekly Model Clash Report
    • RLCA package containing OCD,SSAD,SSRD,LCP,PROTOTYPE,FRD,
    • ROSE DIAGRAMS
    • Status report
    • Peer Review Plan
    • Quality Management Plan
    • Test Plan
    • Iteration Plan
    • Peer review report
    • Change Summaries for updates to RLCA packages.
  • PROJECT DELIVERABLES
    • Production Stage Construction Phase Iteration1
    • Test Report
    • Core Capability Drive through report
    • Iteration Assessment Report
  • PROJECT DELIVERABLES
    • Production Stage Construction Phase Iteration2
    • Individual Effort report
    • Progress report
    • Agenda and Minutes of Meeting
    • Weekly Model Clash Report
    • RLCA package containing OCD,SSAD,SSRD,LCP,PROTOTYPE,FRD,
    • ROSE DIAGRAMS
    • Status report
    • Peer Review Plan
    • Quality Management Plan
    • Test Plan
    • Iteration Plan
    • Peer review report
    • Test Report
    • Iteration Assessment Report
  • PROJECT DELIVERABLES
    • Transition Phase
    • Transition Plan
    • System and Software Support Plan
    • Installation Scripts
    • Software User’s Manual
    • Source code
  • PROJECT DELIVERABLES
    • Support Stage
    • Release Description Report
    • Source code
    • Software User’s Manual
    • Installation Scripts
  • Responsibilities
    • LAPK Help Developers –
    • 1. Analyze, design, and implement the Online Help satisfying the customer and user requirements.
    • 2. Deploy the product to customers.
    • 3. Provide training and technical support to administrator or user during the transition stage.
    • 4. Provide win-win conditions and negotiate win conditions with other stakeholders.
  • Responsibilities
    • CLIENTS
    • 1. Provide the Online Help requirement, background, LAPK organization goals, market perspectives, etc.
    • 2. Providing project team with the analysis of current system and requirements specifications for the new help system
    • 3. Provide support to the developers during the project life cycle including feedback on the prototype, operational description definition, and other artifacts.
    • 4. Monitor the project progress 5. Provide the environment for system deployment and running.
    • 6. Provide win-win conditions and negotiate win conditions with other stakeholders.
    • 7.Providing the existing help references, manuals and suggestions about high level goals to be achieved by the new system
  • Responsibilities
    • LAPK software users
    • Provide support to the development of the system such as giving feedback on the prototype, user manual, and other artifacts promptly.
  • Responsibilities
    • LAPK Help Administrator
    • 1. Review and provide feedback on the system-related artifacts such as Prototype SSRD, OCD, SSAD, etc.
    • 2. Master the necessary skills to support the system.
    • 3. Understand the framework of the Online Help.
    • 4. Perform and support system test.
    • 5. Provide win-win conditions and negotiate win conditions with other stakeholders.
  • Reviews
    • Agile Internal Review(AIR) Early OCD OCD ,SSAD SSRD,Rose Model.
    • Architecture review board(ARB)-LCO
    • Architecture review board(ARB)-LCA
    • Architecture review board(ARB)-RLCA
    • Transition Readiness Review (TRR )
    • Release Readiness Review (RRR)
    • Internal Informal review
  • Risk Monitoring and Control
    • Limited Schedule: Which may possibly affect the quality of system
    • Half the team is probably not going to take 577b so the new members will have to be trained during the construction phase
    • The client is not ready to spend much(at the max. 500 US$) for a 1 time license but implementing certain features may need expensive COTS tools
    • Unfamiliarity of the team with medical terms leading to spelling errors and hence more time needed in rectification of errors
    • Friction between team members will hamper team performance as it causes loss of morale
  • Tools And Facilities used.
    • Engineering stage
    • Easy Win-Win Online-Requirements negotiation
    • Internet Explorer-To access information from worldwide web
    • Rational Rose-To draw UML diagrams for SSAD
    • USC COCOMO II-Cost Estimation Tool
    • Microsoft Project 2000-Project Tracking and Planning by drawing Gantt charts and PERT charts
    • Microsoft PowerPoint 2000 ARB presentations
    • Microsoft Word 2000 Word processing for LCO, LCA package elements except Prototypes and COCOMO II results
    • Adobe Acrobat 5.0documentation in PDF
  • Tools And Facilities used
    • Production stage
    • Internet Explorer-To access information from worldwide web
    • Rational Rose-To draw UML diagrams for SSAD
    • USC COCOMO II-Cost Estimation Tool
    • Microsoft Project 2000-Project Tracking and Planning by drawing Gantt charts and PERT charts
    • Microsoft PowerPoint 2000 ARB presentations
    • Microsoft Word 2000-Documentation
    • Adobe Acrobat 5.0documentation in PDF
  • Configuration Change management Refer Word document for the Flow Chart
  • COCOMO ESTIMATE
  • BUDGETS
    • During both engineering phase and production phase every team member is putting 15 hrs of effort each week and the project development period is of 24 weeks. Plus there are 6 members in the team so the total effort comes out to be 24*15*6=2160 person-hours. The organization has to pay the system administrator and assuming that he is paid $12 per hour and he works 10 hrs a month then the LAPK organization has to pay him 120*12=$1,440.
    • Initially 100 man hours will be needed for organizing the data to make it suitable to fit in the java script tree. There will be also some extra initial work for which a help maintainer needs to be paid. So this payment will come out to be 40*12=$480. Also LAPK needs Dream weaver for this system. That will cost another 400us $
    • As the maintainer has solid technical background, not much time will be elapsed in training him so we assume at the maximum 5 man hours plus 15 man hours will be required for the documentation of the manual. The team will make necessary changes depending upon the feedback so assume 10 man hours for that.
  • LCP - Conclusion
    • Questions?
  • FEASIBILITY RATIONALE DESCRIPTION (FRD)
    • current version : v2.2
    • Jiby John Kattakayam
      • team 6 – csci577a Fall 2003
      • author : FRD
      • team role: Team Manager
  • FRD Presentation Outline
    • CONTENTS
      • Business Case Analysis
      • System Requirements Prioritization
      • Process Match to System Priorities
      • Risk Assessment
      • Analysis Results
    • References:
      • OCD v2.2
      • SSRD v2.2
      • SSAD v2.2
      • LCP v2.2
  • Project Life Cycle Costs
  • continued……. Cost & Benefit Comparison
  • Return on Investment – Time & Money
    • We estimate each user saves 120 hours a year using this system.
    • An estimated 240 hours a year is saved by each LAPK researcher from traveling and giving training.
    • ROI = BENEFITS – COSTS / COSTS
    • ROI(TIME) = 17280 – 2498 / 2498 = 5.92
    • ROI(MONEY) = 34000 – 4985 / 4985 = 5.82
    • The gains from the project outweigh the costs by almost 6 times in both Time and Money Saved.
  • Requirements Prioritization Very High(9-10), High(7-8), Medium(5-6), Low(3-4)
  • System Priorities & Process Match
    • Win-Win Spiral Model is followed into the CTS phase also.
    • Iteration Plans, Test Plans, Quality Management Plans have been drawn up for the next 3 phases and personnel allocated too.
    • Iteration 1 – Very High & High Priorities implemented. Indexed, Searchable Navigable Help System.
    • Iteration 2 – Medium Priorities Implemented. Discussion forum, web-conferencing, email support implemented here.
    • Iteration 3 – Low Priorities. Palm OS Porting, Contextual Help implemented here.
  • TOP SIX RISK ITEMS
      • Adding of New Requirements in Construction
      • Purchase of COTS tools overruns the budget
      • Unfamiliarity with pharmacokinetic terms
      • Training time for construction phase
      • Team Cohesion
      • Uncertainty in Bundling Help
  • RISK MEASUREMENT
  • Analysis Results
    • Solution is Feasible as specified architecture supports all project requirements and supports LAPK organizational goals.
    • Positive Features
      • All project goals and requirements identified.
      • Return of Investment Calculations yield very positive results.
      • Schedule has been followed as planned.
      • Comprehensive Risk Analysis performed
    • Concerns
      • Three team members undecided on continuing.
      • Overdependence on COTS tools.
      • Time to add features which have been right now characterized as low priority.
  • Team 6 – Online Help and Tutorials for LAPK
            • THE END!
            • THANK YOU ALL!