Feasibility Budget Sample by tru12399

VIEWS: 13 PAGES: 48

Feasibility Budget Sample document sample

More Info
									      New Global System Development
                    for
            Pavlo Orphan Care


                by
               Team 2
Jane Dow: Project Manager
Mark Vincent: Business Analyst
Mary King: Systems Analyst
Robert Star: Change Management Analyst

                                      1
                     Introduction
 What does Pavlo Orphan Care do?
  400,000 under care
  Relies on generosity and caring of others
 Current Business Operations
 Shortcomings
 Case for Business Process Re-engineering
 Case for new System-Global Orphan Care



                                               2
               Phased approach


I.     Planning phase
II.    Analysis phase
III.   Design phase
IV.    Implementation phase



                                 3
           I. PLANNING PHASE


   System Request
   Problem Statement
   Business Case
   Scope
   Feasibility



                               4
                      System Request

• Sponsor
     Needs
       • List needs
     Functions requested
       • List requirements
• Benefits
     Tangible
       • Give examples
     Intangible
       • Give examples
                                       5
                  Problem Statement


   Describe the business problems the
    new system plans to solve:
    1.   Lack of Information Management
    2.   Donors require financials and statistics
    3.   Child progress tracking needed
    4.   Application and approval process slow
    5.   Benefactors not properly matched to
         children                                   6
            Business case scenario

   Describe the business benefits the
    new system plans to deliver:
    1. Fully functional information
       management infrastructure
    2. Donors will receive regular quarterly
       reports on Pavlo financials
    3. Quarterly reports on the progress of
       the children will be available
    4. Application procedure will be replaced
       with online application processing
    5. Facilitate child-benefactor assignments
                                                 7
                 Project Scope

   Scope
    • Requirements
    • Budget         Requirements
                     (Skills/Budget)
                                               Resources


    • Time
                                       SCOPE




                                        Time




                                                           8
           Scope--Requirements

Requirements
    Web-based online application and
     admissions processing.
    Web forms for use in collecting data

     regarding the monitoring of child progress.
    Web forms for use in collecting data

     regarding renewal criteria and progress.
    Comprehensive reporting accessible via the

     World Wide Web.
                                                   9
             Scope--Resources

• Resources
    Budget: Indicate the budget for the project

    Skills: The project team members have

     good knowledge of the business process and
     technology.
      Indicate the experience of team members




                                                 10
                              Scope--Time


 Time
  • Duration of Project:
         Indicate the total duration for the project
  • Start date:
         Indicate project start date
  •   End date:
         Indicate project end date




                                                        11
            Feasibility Assessment

Feasibility considerations
  • Technical feasibility
  • Organizational feasibility
  • Economic feasibility




                                     12
               Feasibility--Technical

Technical (Risk = high/medium/low)
   Project size
   Extent of required features
   Maturity of technology used in the project
      Hardware
      Software
   Project team experience
   User group experience




                                                 13
            Feasibility--Organizational

Organizational (Risk = high/medium/low)
   Project champion
      Describe influence in the organization
      Describe involvement in project
   Management
      Describe support from management
      Describe the ratio of project budget to
       organization income
      Assess overall feasibility of support from
       management
   Users
      Describe user excitement about the project
      Describe user willingness to change from the
       current system                                 14
              Feasibility--Economical

Economical (Risk = high/medium/low)
 Tangible benefits
   List the tangible benefits of your proposed system
   Explain tangible benefits in quantitative terms
 Intangible benefits
   List the intangible benefits of your proposed system
   Explain intangible benefits in qualitative terms
 Return on Investment
   Show your ROI table


                                                           15
                  II. ANALYSIS PHASE


   Requirements Gathering
   Process flow
   Functional Modeling
      Use-case diagram
       Use-case description
   Behavioral Modeling
      Sequence diagram
       State chart diagram
   Structural Modeling
      CRC cards
       Class diagram
       Object diagram
                                       16
                 Analysis Strategy

   Analysis strategy choices
    • Business Process Automation (BPA)
    • Business Process Improvement (BPI)
    • Business Process Re-engineering (BPR)
   Analysis strategy selection
    • Identify the strategy used
    • Provide the rationale for the selected
      strategy
                                               17
               Requirements Gathering

   Requirement gathering technique choices
    •   Interviews
    •   Document analysis
    •   Observations
    •   Benchmarking
    •   Joint Application Development
   Requirement gathering technique selection
    • Identify the selected technique
    • Provide rationale for the selected technique
                                                     18
           Joint Application Session
                 (JAD)

   JAD session approach
    • Describe the JAD approach used
   JAD session outcomes
    • Describe the information you collected




                                               19
Translating Requirements to
        process flow
                                          Start



                                   Submit Application




                                   Process Application




                                                            No
                                   Approve Application?



                                                                  CC

                                       Yes




                                                                       No
                                Is the application for a child?


                                                                                                                                      Match with Sponsor
                                                                             Enter Benefactor Statistics
                                                  Yes                                                                                 Requirements
                      B

                                                                                                                                                                                      Yes
                                Match with Guardian Statistics

                                                                                                                                             Successful        No          Continue
                                                                            Match Benefactor Statistics
    Yes                                                                                                                                      Match?                        Match?
                                                                            with Applications on Hold

                                                                                                                                          Yes                                             No

                          No
   Continue Match?                   Successful Match?                                                                                     Assign Sponsor            Application on Hold

                                                                                                           No
                                                                                                                                      D
                                       Yes                                          Successful Match?           Application on Hold
        No
                                                                                                                                                                                  C
                                                                                                                                          Send Notifications
                                                                                                                                          to Benefactors
   Application on Hold             Assign Guardian                                  Yes
                                                                                                                         C


                                                                                      Assign Child                                                                   No
                                                                                                                                             Benefactors
                 C                                                                                                                           Accept?

                                Match with Tutor Statistics
                                                                                                                                           Yes
                                                                                          D
                                                                                                                                                                          Delete Match
                                                                                                                                           Confirm
                                                                                                                                             Confirm
        Yes
                                                                                                                                           Benefactors
                                                                                                                                            Benefactors



                           No                                                                                                              Monitor Child                              B
   Continue Match?                     Successful Match?                                                                                   Progress



                                                                                                                                             Send Reports to
   No                                  Yes                                                                                                   Benefactors



                                   Assign Tutor                                                                                              Evaluate for
 Application on Hold
                                                                                                                                             Renewal



                                                                                                                                                                No
                                                                                                                                                 Renew
             C
                                                                                                                                                 Application?
                                 Match with Mentor Statistics

                                                                                                                                             Yes
   Yes                                                                                                                                                                        B

                                                                                                                                           Process Renewal



                          No
Continue Match?                                                                                                                            Send Reports to
                                       Successful Match?                                                                                   Stakeholders


                                        Yes
             No
                                                                                                                                             Notify Applicant

                                          Assign Mentor
                                                                                                                                                                                  C
Application on Hold
                                                                                                                                                   End                                         20
        C
                Transition Process Flow to
                   Use-case Diagram

   Process Flow
    • Create high level abstraction from process flow
   Create boundaries for use-case diagram
    • Identify use cases
          Use case 1
          Use case 2
          Add more
    • Identify Actors
          Actor 1
          Actor 2
                                                    21
          Add more
                  Developing
               Use-Case Diagram
                       GLOBA L ORPHA N CA RE SYSTEM


                                  Submit A pplication




                                 Process A pplication




                                 A ssign benefactors

                       «include»                           «include»
  A pplicant               Send                               Match
                        notifications          «extend»     benefactor

                                        Drop Benefactor
                                                                         Staff


                                  Monitor progress

Child   Benefactor                  «extend»            «extend»

                         Reward child                  Appreciate
                                                       benefactor



                                  Evaluate for renewal
                     «include»

                           Review reports



                                        Send reports to
                                          stakeholders
                                                                                 22
                       Transition use-case
                          diagram to a
                      Use-Case Description
   Select one use case
   Format for use case description
    • Header information
          Use case name, primary actor, level, etc.
    • Trigger
    • Relationship
    • Normal flow
          Primary actor initiates
          System validates input
          System processes request
          System sends results
    • Sub flow
                                                       23
    • Exceptional flow
          Use-Case Description

Use Case Name: Assign Benefactors          ID: 3              Importance Level: High
Primary actor: Staff                            Use case type: Detail, essential
Stakeholders and Interests:
Staff: wants to match and assign benefactor to child
Benefactor: would accept, reject or quit the program after a notification is sent by staff to
serve a child
Brief Description: This use case describes how can a staff member can assign a
benefactor to the application for a child
Trigger: The system processes the child application and forwards it to the staff member

Type: External
Relationships:
       Association: Benefactor
       Include: Send Notification, Match Benefactor
       Extend: Drop benefactor
       Generalization: guardian, sponsor, mentor, tutor
Normal flow of events:
   1. The System forwards the processed application to the Staff member
   2. The Staff verifies benefactor’s details for accuracy from the benefactor’s list
   3. The Staff executes Match Benefactor use-case
   4. The Staff assigns a benefactor to a child and executes Send Notification use-case
   5. The Staff checks with the benefactor whether he/she accepts, rejects the child or
       quits supporting the program
       If benefactor accepts the child, the S-1: Accept child sub-flow is performed
       If benefactor rejects the child, the S-2: Reject child sub-flow is performed
       If benefactor quits from the program, S-3: Quit program sub-flow is performed
   6. The Staff provides the result of the transaction to the benefactor, child and the
       managerial staff
                                                                                                24
                 Transition use-case
                   description to a
                 Sequence Diagram

   Sequence diagram is associated with one
    use-case
   Draw objects and actors
   Represent messages based on time
    sequence
   Match first message with first line from
    normal flow
   Show subsequent messages using UML
    syntax                                     25
                        Sequence diagram

/ aStaff : Actor1         / aBenefactor : Actor2   / Benefactor.list   / aAssign



                1 : \VerifiesBenefactor\

                2 : \Match Benefactor\

         3 : \Send Notification\




                4 : \Aceept Child\

                        5 : \Create match\


               6 : \Offer services\




                                                                                   26
                          Transition use-case
                             description to
                              CRC Cards
   CRC cards: Class Responsibility and Collaboration
    Cards
   CRC cards are associated with one use-case
   Use subject-verb relationship to identify classes
    and messages
   Represent each class on one CRC card
   CRC card information
    •   Identify   class
    •   Identify   associated responsibilities and collaborations
    •   Identify   attributes
    •   Identify   relationships                                    27
                         CRC cards
Front:

   Class Name: Child             ID: 1             Type: Concrete, Domain

   Description: an individual who wants           Associated Use case:1
   Get admission to the program offered by GOCS

          Responsibilities                            Collaborators

   Apply for admission to program                      Benefactors
   Apply for renewal                                   Staff
   Receive services offered by benefactors
   Select a benefactor




Back:

   Attributes:
   Child ID
   First name
   Last name
   Date of birth
   Address
   Height
   Weight
   Education
   Name of current guardian
   Flag(Y/N)?

   Relationships:
    Generalization (a-kind-of): Applicant                                   28
            Transition CRC cards to a
                 Class Diagram

   Represent each CRC card with a
    class
   Show the attributes
   Show the responsibilities as methods
   Show the collaborations as messages
   Create relationships for
    generalization and aggregation
   Represent multiplicity relationships29
                           Class diagram
                          Updates-->


                                                          Applicant
                                               -   Applicant ID
                                               -   Fname
                                               -   Lname
     Processeschildappl
                                               -   Address
- Applicant ID                                 -   city
- Date of application                          -   State
                                               -   zip
+ Check for required fields ( )
                                               + Send application ( )
                                               + Receive notification ( )




                                                                                       Child
                    Benefactor
                                                                        -   Child ID
             -   BenefactorID               Provide services-->
                                                                        -   DOB
             -   Type
                                                                        -   Program
             -   Donation
                                                                        -   Height
             -   Education                                                              ...
             + Accept a child ( )                                       + Select benefactor ( )
             + Send reports ( )             <--Verifies                 + Apply for admission ( )
             + Send application ( )
             + Offer services ( )

                                      ^ Sends
                                      | Notification                                                         Progressreport
                                                                   Verfies details-->
                                                                                                        -   Child ID
                                                                                                        -   Benefactor ID
                                                                             Updates-->                 -   Grade
                                                                                                        -   Comments
                                           Staff                                                        + Monitor progress ( )
                         -       Staffno
              <--Matches -       fname
                         -       lname                                                                                Assigned
                         -       DOB
                                                                                                               -   Child ID
          <--Reveices    -       Address
                                                                   Assigns-->                                  -   Benefactor ID
                                + Match Benefactor ( )                                                         -   Service offered
                                + Drop Benefactor ( )                                                          -   Date from
                                                                                          Login                -   Date to
                                + verifies benefactor ( )
                                                                  Logs in --->*                                -   Staff ID
                                + send notification ( )                           - LoginID
                                                                                  - Password                   + Create match ( )
                                                                                  + Logs in staff ( )




                                                                                                                                     30
             Transition class diagrams
                to Object Diagram

   Object as instance of a class
   Object Diagrams show instances of
    the class diagram
    • Give examples for the attributes




                                         31
                               Object diagram
       Processedapplication:AP0005
      - Applicant ID : String = AP0005
      - Date : Date = 12-Nov-2002
      + Check required fields ( )



                                Staff:Mary Brown                            Assigned:assign020

                          -   Staff ID : String = S001            - Child ID : String = CH0010
                          -   Fname : String = Mary    Assigns--> - Benefactor ID : String = B0004
                          -   Lname : String = Brown              - Service : String = Sponsor
                          -   DOB : Date = 25-Jun-1958            - Date from : Date = 05-Jan-2003
            <--Receives
                          + Match benefactor ( )                     + Create match ( )
                          + Drop benefactor ( )
             <--Logs in   + verifies benefactor ( )
                                                               Updates-->
                          + send notifications ( )
        *

      Login:sbrown                          Verifies                           Progressreport:ch0010
                                             |
- LoginID : string = sbrown                  v                          -   Child ID : String = CH0010
- Password : string = qw...                                             -   Benefactor ID : String = B0003
                                       Benefactor:Joe Smith             -   Grade : String = B
                                                                        -   Comments : String = Good learner
                                  -   Benefactor ID : B0004
                                  -   Type : Sponsor
                                  -   Donation : $3000
                                  -   Education : Associate degree
                                                                      Verifies-->
                                  + Accept Child ( )
                                  + Send reports ( )
                                  + Send application ( )
                                  + Offer services ( )

                                                                                                               32
                   Creating a
              State Chart Diagram

   State chart diagram is associated
    with the entire system
   Identify an object that goes through
    many state changes
   Identify the states
   Represent the states using UML
    syntax
                                           33
                                               State chart diagram


Start
     Submit Application   Processed   Accept   Matched       Match Found   Assigned            Benefactors Notified




                                                         Match Not Found   Not Assigned   On Hold




                                                                                                                      34
             III. DESIGN PHASE

 Technical Architecture
 Method Specification
 Test Plans




                                 35
           Technical Architecture

 Selected locations
 Describe your LAN
 Describe your WAN




                                    36
Technical Architecture




                         37
             Method Specification

   Method name
   Method context
   Input argument
   Messages sent and arguments passed
   Arguments returned
   Algorithm specification


                                         38
                       Test Plan

   Unit Test
   Integration Test
   System Test
   Acceptance Test




                                   39
           IV. IMPLEMENTATION
                 PHASE

   User interface design
   Navigation design
   Prototype




                                40
User interface design –
      Screen layout




                          41
User interface design –
   Forms and Reports




                          42
               User interface design –
                     Error Message

    Date of birth error (12/31/2005)

     Date of birth is entered incorrectly
     Please re-enter the date of birth




Error message showing date of
birth error


                                            43
Navigation design




                    44
                    Prototype
   Click on the link below to access the
    demo
    http://localhost/index.htm




                                            45
                Conclusion


   Discuss your conclusion




                              46
                           References
   Foxx, Pim. (2003, January 13). Don't leave OS choice to
    developers. ComputerWorld [on-line]. Retrieved July 10,
    2004 from the World Wide Web:
    http://www.computerworld.com/softwaretopics/os/linux/st
    ory/0,10801,77407,00.html?from=story_picks
   Kapur, Gopal. (1999, May 3). Why IT project management
    is so hard to grasp. ComputerWorld [on-line]. Retrieved
    July 10, 2004 from the World Wide Web:
    http://www.computerworld.com/managementtopics/manag
    ement/project/story/0,10801,35529,00.html
   Walton, Bill. (2004, February 20). Iterative vs. waterfall
    software development: Why don't companies get it?.
    ComputerWorld [on-line]. Retrieved July 10, 2004 from the
    World Wide Web:
    http://www.computerworld.com/developmenttopics/develo
    pment/story/0,10801,90325,00.html


                                                             47
Questions ??????




                   48

								
To top