Sample presentation
-
Upload
timothy212 -
Category
Documents
-
view
1.290 -
download
0
description
Transcript of Sample presentation
11
New Global System Development New Global System Development for for
Pavlo Orphan CarePavlo Orphan Care
byby
Team 2Team 2Jane Dow: Project ManagerJane Dow: Project ManagerMark Vincent: Business AnalystMark Vincent: Business AnalystMary King: Systems AnalystMary King: Systems AnalystRobert Star: Change Management AnalystRobert Star: Change Management Analyst
22
IntroductionIntroduction
What does Pavlo Orphan Care do?What does Pavlo Orphan Care do?400,000 under care400,000 under careRelies on generosity and caring of othersRelies on generosity and caring of others
Current Business OperationsCurrent Business Operations ShortcomingsShortcomings Case for Business Process Re-engineeringCase for Business Process Re-engineering Case for new System-Global Orphan CareCase for new System-Global Orphan Care
33
Phased approachPhased approach
I.I. Planning phasePlanning phase
II.II. Analysis phaseAnalysis phase
III.III. Design phaseDesign phase
IV.IV. Implementation phaseImplementation phase
44
I. PLANNING PHASEI. PLANNING PHASE
System RequestSystem Request Problem StatementProblem Statement Business CaseBusiness Case ScopeScope FeasibilityFeasibility
55
System RequestSystem Request
• Sponsor Sponsor NeedsNeeds
• List needsList needs Functions requestedFunctions requested
• List requirementsList requirements
• BenefitsBenefits TangibleTangible
• Give examplesGive examples IntangibleIntangible
• Give examplesGive examples
66
Problem StatementProblem Statement
Describe the business problems the Describe the business problems the new system plans to solve:new system plans to solve:
1.1. Lack of Information ManagementLack of Information Management
2.2. Donors require financials and statisticsDonors require financials and statistics
3.3. Child progress tracking neededChild progress tracking needed
4.4. Application and approval process slowApplication and approval process slow
5.5. Benefactors not properly matched to Benefactors not properly matched to childrenchildren
77
Business case scenarioBusiness case scenario
Describe the business benefits the Describe the business benefits the new system plans to deliver: new system plans to deliver:
1.1. Fully functional information Fully functional information management infrastructuremanagement infrastructure
2.2. Donors will receive regular quarterly Donors will receive regular quarterly reports on Pavlo financialsreports on Pavlo financials
3.3. Quarterly reports on the progress of Quarterly reports on the progress of the children will be available the children will be available
4.4. Application procedure will be replaced Application procedure will be replaced with online application processingwith online application processing
5.5. Facilitate child-benefactor assignments Facilitate child-benefactor assignments
88
Project ScopeProject Scope
ScopeScope• RequirementsRequirements• BudgetBudget• TimeTime
Requirements Resources (Skills/Budget)
SCOPE
Time
99
Scope--RequirementsScope--Requirements
RequirementsRequirements Web-based online application and Web-based online application and
admissions processing.admissions processing. Web forms for use in collecting data Web forms for use in collecting data
regarding the monitoring of child progress.regarding the monitoring of child progress. Web forms for use in collecting data Web forms for use in collecting data
regarding renewal criteria and progress.regarding renewal criteria and progress. Comprehensive reporting accessible via the Comprehensive reporting accessible via the
World Wide Web.World Wide Web.
1010
Scope--ResourcesScope--Resources
• ResourcesResources Budget: Indicate the budget for the projectBudget: Indicate the budget for the project Skills: The project team members have good Skills: The project team members have good
knowledge of the business process and knowledge of the business process and technology.technology.
Indicate the experience of team membersIndicate the experience of team members
1111
Scope--TimeScope--Time
TimeTime• Duration of Project:Duration of Project:
Indicate the total duration for the project Indicate the total duration for the project
• Start date: Start date: Indicate project start dateIndicate project start date
• End date:End date: Indicate project end dateIndicate project end date
1212
Feasibility AssessmentFeasibility Assessment
Feasibility considerationsFeasibility considerations• Technical feasibilityTechnical feasibility• Organizational feasibilityOrganizational feasibility• Economic feasibilityEconomic feasibility
1313
Feasibility--TechnicalFeasibility--Technical
Technical (Risk = high/medium/low)Technical (Risk = high/medium/low) Project sizeProject size Extent of required featuresExtent of required features Maturity of technology used in the projectMaturity of technology used in the project
HardwareHardware SoftwareSoftware
Project team experienceProject team experience User group experienceUser group experience
1414
Feasibility--OrganizationalFeasibility--Organizational
Organizational (Risk = high/medium/low) Organizational (Risk = high/medium/low) Project championProject champion
Describe influence in the organizationDescribe influence in the organization Describe involvement in projectDescribe involvement in project
ManagementManagement Describe support from managementDescribe support from management Describe the ratio of project budget to Describe the ratio of project budget to
organization incomeorganization income Assess overall feasibility of support from Assess overall feasibility of support from
managementmanagement UsersUsers
Describe user excitement about the projectDescribe user excitement about the project Describe user willingness to change from the Describe user willingness to change from the
current systemcurrent system
1515
Feasibility--EconomicalFeasibility--Economical
Economical (Risk = high/medium/low)Economical (Risk = high/medium/low) Tangible benefitsTangible benefits
List the tangible benefits of your proposed systemList the tangible benefits of your proposed system Explain tangible benefits in quantitative termsExplain tangible benefits in quantitative terms
Intangible benefitsIntangible benefits List the intangible benefits of your proposed systemList the intangible benefits of your proposed system Explain intangible benefits in qualitative termsExplain intangible benefits in qualitative terms
Return on InvestmentReturn on Investment Show your ROI tableShow your ROI table
1616
II. ANALYSIS PHASEII. ANALYSIS PHASE
Requirements GatheringRequirements Gathering Process flowProcess flow Functional ModelingFunctional Modeling
Use-case diagramUse-case diagram Use-case descriptionUse-case description
Behavioral ModelingBehavioral Modeling Sequence diagramSequence diagram State chart diagramState chart diagram
Structural ModelingStructural Modeling CRC cardsCRC cards Class diagramClass diagram Object diagramObject diagram
1717
Analysis StrategyAnalysis Strategy
Analysis strategy choicesAnalysis strategy choices• Business Process Automation (BPA)Business Process Automation (BPA)• Business Process Improvement (BPI)Business Process Improvement (BPI)• Business Process Re-engineering (BPR)Business Process Re-engineering (BPR)
Analysis strategy selectionAnalysis strategy selection• Identify the strategy usedIdentify the strategy used• Provide the rationale for the selected Provide the rationale for the selected
strategystrategy
1818
Requirements GatheringRequirements Gathering
Requirement gathering technique choicesRequirement gathering technique choices• InterviewsInterviews• Document analysisDocument analysis• ObservationsObservations• BenchmarkingBenchmarking• Joint Application DevelopmentJoint Application Development
Requirement gathering technique Requirement gathering technique selectionselection• Identify the selected techniqueIdentify the selected technique• Provide rationale for the selected technique Provide rationale for the selected technique
1919
Joint Application Joint Application SessionSession(JAD)(JAD)
JAD session approachJAD session approach• Describe the JAD approach usedDescribe the JAD approach used
JAD session outcomesJAD session outcomes• Describe the information you collected Describe the information you collected
2020
Translating Requirements to Translating Requirements to process flowprocess flow
No
CC
Yes
Start
Submit ApplicationSubmit Application
Process ApplicationProcess Application
Approve Application?Approve Application?
Is the application for a child?Is the application for a child?
Match with Guardian StatisticsMatch with Guardian Statistics
Successful Match?
Yes
Assign Guardian
Yes
Match with Tutor StatisticsMatch with Tutor Statistics
Successful Match?
Assign Tutor
Yes
Match with Mentor StatisticsMatch with Mentor Statistics
Successful Match?
Assign Mentor
Yes
No
Continue Match?
Yes
Application on Hold
No
C
Continue Match?
Yes
No
No
Application on Hold
C
Continue Match?No
Yes
Application on Hold
No
C
Enter Benefactor StatisticsEnter Benefactor Statistics
Match Benefactor Statistics with Applications on HoldMatch Benefactor Statistics with Applications on Hold
Successful Match? Application on Hold
Assign Child
No
No
YesC
D
C
End
C
B
B
Match with Sponsor Requirements
Successful Match?
Assign Sponsor
Send Notifications to Benefactors
Monitor Child Progress
Send Reports to Benefactors
Evaluate for Renewal
Renew Application?
Process Renewal
Send Reports to Stakeholders
Continue Match?
Application on Hold
Yes
No
Yes No
No
Notify Applicant
D
Yes
Benefactors Accept?
Confirm Benefactors
Confirm Benefactors
Yes
No
Delete Match
B
2121
Transition Process Flow to Transition Process Flow to Use-case DiagramUse-case Diagram
Process FlowProcess Flow• Create high level abstraction from process flowCreate high level abstraction from process flow
Create boundaries for use-case diagramCreate boundaries for use-case diagram• Identify use casesIdentify use cases
Use case 1Use case 1 Use case 2Use case 2 Add moreAdd more
• Identify ActorsIdentify Actors Actor 1Actor 1 Actor 2Actor 2 Add moreAdd more
2222
Developing Developing Use-Case DiagramUse-Case Diagram
Submit Application
Process Application
Assign benefactors
Monitor progress
Evaluate for renewal
Send notifications
Send reports to stakeholders
Applicant
Staff
BenefactorChild
GLOBAL ORPHAN CARE SYSTEM
«include»
Match benefactor
«include»
Reward child
«extend»
Appreciate benefactor
«extend»
Drop Benefactor
«extend»
Review reports
«include»
2323
Transition use-case Transition use-case diagram to a diagram to a
Use-Case DescriptionUse-Case Description
Select one use caseSelect one use case Format for use case descriptionFormat for use case description
• Header informationHeader information Use case name, primary actor, level, etc.Use case name, primary actor, level, etc.
• TriggerTrigger• RelationshipRelationship• Normal flowNormal flow
Primary actor initiatesPrimary actor initiates System validates inputSystem validates input System processes requestSystem processes request System sends resultsSystem sends results
• Sub flowSub flow• Exceptional flow Exceptional flow
24
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
2525
Transition use-case Transition use-case description to a description to a
Sequence DiagramSequence Diagram
Sequence diagram is associated with one Sequence diagram is associated with one use-caseuse-case
Draw objects and actorsDraw objects and actors Represent messages based on time Represent messages based on time
sequencesequence Match first message with first line from Match first message with first line from
normal flownormal flow Show subsequent messages using UML Show subsequent messages using UML
syntax syntax
26
Sequence diagram
/ aStaff : Actor1 / aAssign/ Benefactor.list/ aBenefactor : Actor2
1 : \VerifiesBenefactor\
2 : \Match Benefactor\
3 : \Send Notification\
4 : \Aceept Child\
5 : \Create match\
6 : \Offer services\
2727
Transition use-case Transition use-case description to description to
CRC CardsCRC Cards
CRC cards: Class Responsibility and Collaboration CRC cards: Class Responsibility and Collaboration Cards Cards
CRC cards are associated with one use-caseCRC cards are associated with one use-case Use subject-verb relationship to identify classes Use subject-verb relationship to identify classes
and messages and messages Represent each class on one CRC cardRepresent each class on one CRC card CRC card informationCRC card information
• Identify classIdentify class• Identify associated responsibilities and collaborationsIdentify associated responsibilities and collaborations• Identify attributesIdentify attributes• Identify relationshipsIdentify relationships
2828
CRC cardsCRC cards
Front: Back:
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
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
2929
Transition CRC cards to a Transition CRC cards to a Class DiagramClass Diagram
Represent each CRC card with a Represent each CRC card with a classclass
Show the attributes Show the attributes Show the responsibilities as methodsShow the responsibilities as methods Show the collaborations as messagesShow the collaborations as messages Create relationships for Create relationships for
generalization and aggregation generalization and aggregation Represent multiplicity relationships Represent multiplicity relationships
30
Class diagram
Applicant
- Applicant ID- Fname- Lname- Address- city- State- zip
+ Send application ( )+ Receive notification ( )
Child
- Child ID- DOB- Program- Height
...
+ Select benefactor ( )+ Apply for admission ( )
Benefactor
- BenefactorID- Type- Donation- Education
+ Accept a child ( )+ Send reports ( )+ Send application ( )+ Offer services ( )
Staff
- Staffno- fname- lname- DOB- Address
+ Match Benefactor ( )+ Drop Benefactor ( )+ verifies benefactor ( )+ send notification ( )
Assigned
- Child ID- Benefactor ID- Service offered- Date from- Date to- Staff ID
+ Create match ( )
Processeschildappl
- Applicant ID- Date of application
+ Check for required fields ( )
Login
- LoginID- Password
+ Logs in staff ( )
*
<--ReveicesAssigns-->
<--Matches
Sends | Notification
Verfies details-->
Provide services-->
<--Verifies
Updates-->
Progressreport
- Child ID- Benefactor ID- Grade- Comments
+ Monitor progress ( )
Updates-->
Logs in --->
3131
Transition class diagrams Transition class diagrams to Object Diagramto Object Diagram
Object as instance of a classObject as instance of a class Object Diagrams show instances of Object Diagrams show instances of
the class diagramthe class diagram• Give examples for the attributesGive examples for the attributes
32
Object diagram
Benefactor:Joe Smith
- Benefactor ID : B0004- Type : Sponsor- Donation : $3000- Education : Associate degree
+ Accept Child ( )+ Send reports ( )+ Send application ( )+ Offer services ( )
Staff:Mary Brown
- Staff ID : String = S001- Fname : String = Mary- Lname : String = Brown- DOB : Date = 25-Jun-1958
+ Match benefactor ( )+ Drop benefactor ( )+ verifies benefactor ( )+ send notifications ( )
Assigned:assign020
- Child ID : String = CH0010- Benefactor ID : String = B0004- Service : String = Sponsor- Date from : Date = 05-Jan-2003
+ Create match ( )
Processedapplication:AP0005
- Applicant ID : String = AP0005- Date : Date = 12-Nov-2002
+ Check required fields ( )
Assigns-->
Verifies
|v
<--Receives
Login:sbrown
- LoginID : string = sbrown- Password : string = qw...
*
<--Logs in
Progressreport:ch0010
- Child ID : String = CH0010- Benefactor ID : String = B0003- Grade : String = B- Comments : String = Good learner
Updates-->
Verifies-->
3333
Creating a Creating a State Chart DiagramState Chart Diagram
State chart diagram is associated State chart diagram is associated with the entire system with the entire system
Identify an object that goes through Identify an object that goes through many state changesmany state changes
Identify the statesIdentify the states Represent the states using UML Represent the states using UML
syntax syntax
34
State chart diagram
Processed Matched Assigned
Not Assigned On Hold
Start
Submit Application Accept Match Found
Match Not Found
Benefactors Notified
3535
III. DESIGN PHASEIII. DESIGN PHASE
Technical ArchitectureTechnical Architecture Method SpecificationMethod Specification Test PlansTest Plans
3636
Technical ArchitectureTechnical Architecture
Selected locationsSelected locations Describe your LANDescribe your LAN Describe your WANDescribe your WAN
37
Technical Architecture
Atlanta, GA U.S.A.
St. Petersburg, Russia
Bombay, India
Addis Ababa, EtiopiaSan Diego, CA U.S.A.
Fib
er B
ackb
one
655
mb
s
PBX
Satellite Rx
Satellite Rx
Satellite Tx
Satellite Rx
CAT3 and CAT 5 Cabling for Voice & Data
CAT3 and CAT 5 Cabling for Voice & Data
CAT3 and CAT 5 Cabling for Voice & Data
CAT3 and CAT 5 Cabling for Voice & Data
CAT3 and CAT 5 Cabling for Voice & Data
100BaseT
100BaseT
100BaseT
100BaseT
100BaseT
100BaseT WiFi
`
Laptop
Desktop Computer
Printer
Cisco Ethernet Switch
ATM Switch
ATM Switch
Radio Link
Public Internet/VPN to all Networks
Public Internet/VPN to all Networks
Public Internet/VPN to all Networks
Public Internet/VPN to all Networks
Public Internet/VPN to all Networks
Cisco Router
Cisco Router
Cisco Router
Cisco Router
Cisco Router
Satellite Rx
3838
Method SpecificationMethod Specification
Method nameMethod name Method contextMethod context Input argumentInput argument Messages sent and arguments passedMessages sent and arguments passed Arguments returnedArguments returned Algorithm specificationAlgorithm specification
3939
Test PlanTest Plan
Unit TestUnit Test Integration TestIntegration Test System TestSystem Test Acceptance TestAcceptance Test
4040
IV. IMPLEMENTATION IV. IMPLEMENTATION PHASE PHASE
User interface designUser interface design Navigation designNavigation design PrototypePrototype
4141
User interface design – User interface design – Screen layoutScreen layout
4242
User interface design – User interface design – Forms and ReportsForms and Reports
4343
User interface design – User interface design – Error MessageError Message
Error message showing date of birth Error message showing date of birth errorerror
Date of birth is entered incorrectly Please re-enter the date of birth
Date of birth error (12/31/2005)
4444
Navigation designNavigation design
GOCS HOME PAGE
DONATE NOW ENROLL A CHILD HELP A CHILD LOGIN TO GOCS CONTACT US
ENTER/MODIFYCHILD
ENTER/MODIFYBENEFACTOR
APPLICATIONFORM
SUCCESSSTORIES
DONATION FORMAPPLICATION
FORM
MATCHBENEFACTOR REVIEW CHILD REPORTS
LIST OFCHILDREN
LIST OFBENEFACTORS
LIST OFMATCHES
4545
PrototypePrototype
Click on the link below to access the Click on the link below to access the demodemo
http://localhost/index.htmhttp://localhost/index.htm
4646
ConclusionConclusion
Discuss your conclusionDiscuss your conclusion
4747
ReferencesReferences
Foxx, Pim. (2003, January 13). Don't leave OS choice to Foxx, Pim. (2003, January 13). Don't leave OS choice to developers. developers. ComputerWorld ComputerWorld [on-line].[on-line]. Retrieved July 10, Retrieved July 10, 2004 from the World Wide Web: 2004 from the World Wide Web: http://www.computerworld.com/softwaretopics/os/linux/storhttp://www.computerworld.com/softwaretopics/os/linux/story/0,10801,77407,00.html?from=story_picksy/0,10801,77407,00.html?from=story_picks
Kapur, Gopal. (1999, May 3). Why IT project management is Kapur, Gopal. (1999, May 3). Why IT project management is so hard to grasp. so hard to grasp. ComputerWorldComputerWorld [on-line]. Retrieved July [on-line]. Retrieved July 10, 2004 from the World Wide Web: 10, 2004 from the World Wide Web: http://www.computerworld.com/managementtopics/managhttp://www.computerworld.com/managementtopics/management/project/story/0,10801,35529,00.htmlement/project/story/0,10801,35529,00.html
Walton, Bill. (2004, February 20). Iterative vs. waterfall Walton, Bill. (2004, February 20). Iterative vs. waterfall software development: Why don't companies get it?. software development: Why don't companies get it?. ComputerWorld ComputerWorld [on-line]. Retrieved July 10, 2004 from the [on-line]. Retrieved July 10, 2004 from the World Wide Web: World Wide Web: http://www.computerworld.com/developmenttopics/develophttp://www.computerworld.com/developmenttopics/development/story/0,10801,90325,00.htmlment/story/0,10801,90325,00.html
4848
Questions ??????Questions ??????