New Global System Development for Pavlo Orphan Care

1
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

2
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

3
Phased approach

• Planning phase
• Analysis phase
• Design phase
• Implementation phase

4
I. PLANNING PHASE

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

5
System Request

• Sponsor
• Needs
• List needs
• Functions requested
• List requirements
• Benefits
• Tangible
• Give examples
• Intangible
• Give examples

6
Problem Statement

• Describe the business problems the new system
  plans to solve
• Lack of Information Management
• Donors require financials and statistics
• Child progress tracking needed
• Application and approval process slow
• Benefactors not properly matched to children

7
Business case scenario

• Describe the business benefits the new system
  plans to deliver
• Fully functional information management
  infrastructure
• Donors will receive regular quarterly reports on
  Pavlo financials
• Quarterly reports on the progress of the children
  will be available
• Application procedure will be replaced with
  online application processing
• Facilitate child-benefactor assignments

8
Project Scope

• Scope
• Requirements
• Budget
• Time

SCOPE
Requirements Resources
(Skills/Budget)
Time
9
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.

10
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

11
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

12
Feasibility Assessment

• Feasibility considerations
• Technical feasibility
• Organizational feasibility
• Economic feasibility

13
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

14
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

15
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

16
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

17
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

18
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

19
Joint Application Session(JAD)

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

20
Translating Requirements to process flow
21
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
• Add more

22
Developing Use-Case Diagram
23
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
• Exceptional flow

24
Use-Case Description
25
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

26
Sequence diagram
27
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

28
CRC cards
29
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 relationships

30
Class diagram
31
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

32
Object diagram
33
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

34
State chart diagram
35
III. DESIGN PHASE

• Technical Architecture
• Method Specification
• Test Plans

36
Technical Architecture

• Selected locations
• Describe your LAN
• Describe your WAN

37
Technical Architecture
38
Method Specification

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

39
Test Plan

• Unit Test
• Integration Test
• System Test
• Acceptance Test

40
IV. IMPLEMENTATION PHASE

• User interface design
• Navigation design
• Prototype

41
User interface design Screen layout
42
User interface design Forms and Reports
43
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

 
44
Navigation design
45
Prototype

• Click on the link below to access the demo
• http//localhost/index.htm

46
Conclusion

• Discuss your conclusion

47
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/lin
  ux/story/0,10801,77407,00.html?fromstory_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/managementt
  opics/management/project/story/0,10801,35529,00.ht
  ml
• 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/dev
  elopment/story/0,10801,90325,00.html

48
Questions ??????