Theater Script Online Database by krl73146

VIEWS: 19 PAGES: 39

									1
                         Introduction

• USC CSCI577b, Fall 2008 – Spring 2009

• 20+ Weeks of Development
• 8 People and the client

• Based on a number of years of software development
  experience
• Following the ICM, the leading technology in the field of
  Software Engineering


                                                              2
                         Outline

    Name                  Section                Time

Nory Nishimura   Overall System Introduction   10 Minutes

Jae young Bang         Data Reporting          10 Minutes

   Ka ho Au        System Demonstration        15 Minutes

Young Chan Noh        Supporting Plan          5 Minutes

  Gary Lam             Transition Plan         10 Minutes




                                                            3
Nory Nishimura – IIV&V, QFP, Quality Lead, and Tester

OVERALL SYSTEM INTRODUCTION



                                                        4
In the beginning…




                    5
Then there was an idea…




                          6
And 8 months later…




                      7
                         Outline

    Name                  Section                Time

Nory Nishimura   Overall System Introduction   10 Minutes

Jae young Bang        Data Reporting           10 Minutes

   Ka ho Au        System Demonstration        15 Minutes

Young Chan Noh        Supporting Plan          5 Minutes

  Gary Lam             Transition Plan         10 Minutes




                                                            8
Jae young Bang – Project Manager, Non-tech Lead, and Developer

DATA REPORTING



                                                                 9
                  Current Status of the Project

• Approximately 3500 of SLOC
• Total 4 risks at this moment
     – 2 of them have very low impact and probability


•   18 Artifacts that describe the system
•   Version 10.0 – numbers of the milestones
•   Have been written and modified thoroughly and carefully
•   Available at:
    http://greenbay.usc.edu/csci577/spring2009/projects/team16/



                                                                  10
ROI Analysis on Time

                       11
ROI Analysis on Money

                        12
              Comparison to The Legacy System

• There is no legacy system
• The new system is always going to be more cost-effective
  ( I’m sorry, Kinko’s)




                                                             13
                        Risk Management

• The least number of risks among all the teams
• Put every one of the team members to mitigate risks
   – e.g. Search Functionality

• Current critical risks on the system:
   – Unreliable Internet Connectivity: only for testing purpose
   – Malicious Visitor: 2 types of form validations are implemented




                                                                      14
                         Outline

    Name                  Section                Time

Nory Nishimura   Overall System Introduction   10 Minutes

Jae young Bang         Data Reporting          10 Minutes

   Ka ho Au        System Demonstration        15 Minutes

Young Chan Noh        Supporting Plan          5 Minutes

  Gary Lam             Transition Plan         10 Minutes




                                                            15
Ka ho Au – Prototyper and Developer

SYSTEM DEMONSTRATION



                                      16
          Main Features of This Demonstration

• Overall System Revisit – Core Capabilities

• Search in Script

• Update Script

• Archive/Restore/Reset




                                                17
                      Search in Script

• Search results are shown with page numbers

• The pages containing the target words are extracted to a PDF
  file, and available for download.




                                                                 18
                          Update Script

• Download a script

• Make changes on it

• All script access to the users still hold




                                              19
                  Archive/Restore/Reset

• Download the archive file

• Restore the system with the archived file

• Reset the system with one click




                                              20
                         Outline

    Name                  Section                Time

Nory Nishimura   Overall System Introduction   10 Minutes

Jae young Bang         Data Reporting          10 Minutes

   Ka ho Au        System Demonstration        15 Minutes

Young Chan Noh        Supporting Plan          5 Minutes

   Gary Lam            Transition Plan         10 Minutes




                                                            21
Young Chan Noh – System Architect and Developer

SUPPORTING PLAN



                                                  22
                            Support Strategy
Support Lifetime – Team 16 may provide the technical support by next year
          (at least 12 months)
Possibility of the Support –
1.Most members are familiar with system platform (could modify the code)
2.Some of the team members will be pursuing the masters degree by next year
3.The client, Julie, also is working on the campus
    => All issues, questions, and any related problems could be discussed
         by the in-person meeting.

Support Plan –
1.The new requirements of the system will remain stable
2.The system will be customized and modified for the final release
3.During the next two semesters, some of the team members will provide technical
    support and fix critical errors



                                                                                   23
                         Support Responsibilities
    Stakeholder                   Supporting roles               #      Supporting Skills

Software              - Application Modification                One    Intermediate
Maintenance           - System Installation/Deployment          or     Software Engineer
                      - Application Error Diagnostics           More
                      - Database Optimization
                      - Operating System Update




System Administrator - Operating System(Windows) Update         One    General PC user
                     - System Re-installation using backup CD          who has the
                     - Data archiving                                  administrator role
                     - Website Maintenance                             in the system




                                                                                            24
                         Outline

    Name                  Section                Time

Nory Nishimura   Overall System Introduction   10 Minutes

Jae young Bang         Data Reporting          10 Minutes

   Ka ho Au        System Demonstration        15 Minutes

Young Chan Noh        Supporting Plan          5 Minutes

  Gary Lam             Transition Plan         10 Minutes




                                                            25
Gary Lam – Requirements Engineer, Technical Lead, and Tester

TRANSITION PLAN



                                                               26
                  Hardware Requirements
• Server
   – PC
   – 1GHZ Processor
   – 512MB Ram
   – Network Card
• Client
   – Computer with network card




                                          27
                  Software Requirements
• Server
   – Apache Tomcat v6.0
   – Windows XP Home w/ SP3
   – MySQL v5.0
   – Java SDK v1.6




                                          28
                     Software Requirements
• Client
   – Web Browsers
        • Microsoft Internet Explorer v7
        • Mozilla Firefox v3
        • Safari v3.1
   – Adobe Reader v8.1




                                             29
                             Site Preparation
• We can support the initial installation if:
    – A place is given,
    – A computer (server) is given, and
    – The installation happens before the project period ends.




                                                                 30
                          Staff Preparation
• Maintenance staff can be train herself/himself by watching the video
  tutorials and the user manuals provided in text format or can be trained
  by Development Team




                                                                             31
                         Operational Testing
• Operational Testing was originally planned in early this semester
• It was not viable at the time




                                                                      32
             Stakeholder Roles and Responsibilities
                Stakeholder                Roles and Responsibilities
Testers                         -Ensure system passes all Acceptance Test
                                Cases.
                                -Test system onsite to ensure proper
                                functionality after installation of system.
Builders and Coders             -Ensure that all core capabilities of the system
                                are implemented and transitioned to client site
                                -Provide training for client to get familiar with
                                the system

Development Team                -Ensure hardware, its peripheral devices, and
                                other supplies are available and functioning
                                prior to transition.
                                -Develop user manual to assist with installation
                                and software use.


                                                                                    33
              Stakeholder Roles and Responsibilities
               Stakeholder                 Roles and Responsibilities
End Users                        -Provide system, peripheral devices, and other
                                 supplies to the Development Team (client
                                 only).
                                 - Perform informal testing at client site to
                                 ensure the product being launched is
                                 satisfactory.
Maintainers                      -Review documentations of system and clarify
                                 and have any doubts clarified.
                                 -Ensure core capabilities have been delivered
                                 -Receive training from Development Team or
                                 training materials to familiarize oneself with
                                 the development process, installation process,
                                 and the system itself.




                                                                                  34
                      Transition Schedule

      Date             Role       Responsibility         Location
03/11/09     Coder             Setup Early State   Client Site
                               System on site
03/13/09     Testers           On site Dry Run     Client Site
03/23/09     Client            Core Capability     Client Site
                               Drive-through
04/01/09     Coders            Prepare CD for      Coder Site
                               installation
04/15/09     Coders            Deploy system       Client Site
04/17/09     Team              Produce Manual      Team Site
04/21/09     Client            Training Sessions   Client Site
05/01/09     Team              Final Delivery      Client Site


                                                                    35
                        Training Resources
• Camtasia Studio
   – Video recording of on-screen display
   – Supports narration
   – Can be watched over and over again
• User Manual
   – Step by step instructions
   – Learn at your own pace
   – Outlines all features of the system




                                             36
                     Measure of Success
          Task                  Subtask       Completed
Create New Account   Click on Join Button        
                     Enter First Name
                     Enter Last Name             
                     Enter Organization
                     Enter Phone                 
                     Enter E-Mail                
                     Enter Username              
                     Enter Password
                     Confirm Password
                     Click on Submit Button




                                                          37
                        Product Elements
• Bundled installation file
• Source Code
• Training Material
   – Training Video
   – User Manual
• Documents
   – Operational Concept Description, System and Software Requirements
      Description… etc;




                                                                         38
Thank all of you very much
       Any Question?




                             39

								
To top