SlideShare a Scribd company logo
1 of 36
By
FIVE POINT SOLUTIONS
TOOLS ARE US
(HIRE TRACKING
SYSTEM)
Team Leader
Peter Kropp
Standards Managers
Jaya Swami
Evan Panopoulos
Testing Manager
Fraser Hannell
Admin Manager
Joe Smith
Primary roles:
 Interview Summary Report
 Project plan
 Work breakdown structure
 Allocate Programming Tasks
 Edited and finalised SRS
 Coding for Main Form and Hire Form
 Assistance with Testing Procedures/Test Plan
 Progress Report
 Slide Presentation
 The system request - The Problem !!
 The planning and methods used to solve this
problem
 ……… and The Solution !!
 Design of the GUI Application
 Demonstration of the System
 The Online Help facility
 Conclusion and questions
The Interview
On the 26th July 2010, the project team (Five Point
Solutions) interviewed the client ‘Tools Are Us’, as a
means to gather information as to what is required with
the upgraded system.
Interview Summary Report
- The Interview
- System Request
- The Report
Five Point Solutions was asked to build a system that
would:
 Track the availability and scheduling of equipment (tools,
machinery, vehicles, etc) that customers have hired
 Allow the adding, editing and deleting of customers and
equipment available for hire
 Access to an online help facility
 To be able to generate reports
 Planning
 Analysis
 Design
 Implementation
 Support/Closing
The System Methodology Report outlines how the System
Development Life Cycle (SDLC), a systematic and orderly
approach, will be used for the implementation of the new
system. It comprises of the following phases:
Hire Tracking System
PROJECT PLAN
(Five Point Solutions)
Author : Peter Kropp
The project plan will describe, in detail, how Five Point
Solutions will meet the requirements of the new Hire
Tracking System, as proposed by Tools Are Us.
The basis of this project plan is to fully document the
development of the system, phase by phase, that will be based
on the standards of the System Development Life Cycle
(SDLC).
GANTT CHART – PROJECT OUTLINE
(Work Breakdown Structure)
Jaya Swami
(Standards Manager)
Primary roles:
 Prioritising System Requirements
 Creation of Events List
 Development of Modeled Events
 Coding for Login Form and Reserve Form (and
assistance with other forms)
 Assistance with Testing Procedures
 Disaster Recovery Plan
The Hire Tracking System will:
 allow the user to track the hiring of equipment items to
customers
 allow the user to reserve equipment items for the customer, if
unavailable at a particular time.
 allow a user with admin rights (only) to Add, Edit and Delete
customer details, equipment item details and category details.
1. Customer registers details
2. Customer enquires to availability of equipment item.
3. If unavailable, equipment item is reserved.
4. If available, equipment item is hired.
5. Equipment item is returned.
6. Customer pays a fee, if an item is returned late
4. If available, equipment item is hired
[Tools Are Us]
Disaster Recovery
Plan
by
[Jaya Swami]
19/10/2010
The Disaster Recovery Plan (DRP) is a plan that was
developed and its intended purpose is to be used in the
event of a disaster (e.g. Fire) at Tool Are Us.
Evan Panopoulos
(Standards Manager)
Primary roles:
 Context Flow Diagram (CFD)
 Data Flow Diagram (DFD)
 Coding for Categories Form
 Online Help Facility
Fraser Hannell
(Testing Manager)
Primary roles:
 Entity Relationship Diagram (ERD)
 Database development
 Data Dictionary/Data Elements
 Coding for Equipment Form
 Technical Manual
 Testing Plan/Testing Procedures
The Entity Relationship (ER) Diagram is represented as follows.
Example: Customer’s Table -
FieldField TypeType Form AttributeForm Attribute
CustomerID Numeric (7 Numeric) Text Box
Staff Boolean(Yes/No) Check Box
LastName Text(40 Alphabetical) Text Box
FirstName Text(40 Alphabetical) Text Box
Address Text (40 Alphanumeric) Text Box
Suburb Text(40 Alphabetical) Text Box
State Text(3 Alphabetical) Text Box
PostCode Text(4 Numeric) Text Box
HomeNumber Text(8 Numeric) Text Box
MobileNumber Text(10 Numeric) Text Box
Email Text(40 Alphanumeric) Text Box
Example – Customer Form:
A document created which describes the
technical aspects of the system.
Consists of:
 Testing Plan
 Testing Data
 Test Reports
Test data for Customer Form:
Joe Smith
(Admin Manager)
Primary roles:
 System Methodology Report
 SRS (with contributions from team members)
 Assistance with Data Dictionary/Data Elements
 Design of GUI Application
 Coding of Customer Form
 System Reports (using Crystal Reports)
 User Manual
 Assistance with Slide Presentation
The Software Requirement Specification (SRS)
document outlines the requirements for the
implementation of a Hire Tracking System for
‘Tools Are Us’.
Documents to the User how to navigate through
the new/upgraded system.
Main Menu Navigation
of
Hire Tracking System
Five Point Solutions Slide Presentation

More Related Content

What's hot

Chapter no 4 inception phase
Chapter no 4 inception phaseChapter no 4 inception phase
Chapter no 4 inception phasenaveed428
 
V model (software engineering)
V model (software engineering)V model (software engineering)
V model (software engineering)MuhammadTalha436
 
Using formal methods in Industrial Software Development
Using formal methods in Industrial Software DevelopmentUsing formal methods in Industrial Software Development
Using formal methods in Industrial Software DevelopmentRobert van Lieshout
 
9-Software Verification and Validation (Object Oriented Software Engineering ...
9-Software Verification and Validation (Object Oriented Software Engineering ...9-Software Verification and Validation (Object Oriented Software Engineering ...
9-Software Verification and Validation (Object Oriented Software Engineering ...Hafiz Ammar Siddiqui
 
Toolbox of techniques for Architecture Reviews
Toolbox of techniques for Architecture ReviewsToolbox of techniques for Architecture Reviews
Toolbox of techniques for Architecture ReviewsJason Baragry
 
Mi0033 software engineering...
Mi0033  software engineering...Mi0033  software engineering...
Mi0033 software engineering...smumbahelp
 
Introduction to formal methods
Introduction to formal methodsIntroduction to formal methods
Introduction to formal methodsInzemamul Haque
 
Dynamic Testing
Dynamic TestingDynamic Testing
Dynamic TestingJimi Patel
 
Assessment 2 descriptor
Assessment 2  descriptorAssessment 2  descriptor
Assessment 2 descriptorPraneel Chand
 
White box testing
White box testingWhite box testing
White box testingAbdul Basit
 
Decision Support Analyss for Software Effort Estimation by Analogy
Decision Support Analyss for Software Effort Estimation by AnalogyDecision Support Analyss for Software Effort Estimation by Analogy
Decision Support Analyss for Software Effort Estimation by AnalogyTim Menzies
 
System development life_cycle
System development life_cycleSystem development life_cycle
System development life_cycleSwapnil Walde
 
Test-Driven Development Introduction
Test-Driven Development IntroductionTest-Driven Development Introduction
Test-Driven Development IntroductionSamsung Electronics
 
Defect Life Cycle
Defect Life CycleDefect Life Cycle
Defect Life CycleANKUR-BA
 

What's hot (18)

Chapter no 4 inception phase
Chapter no 4 inception phaseChapter no 4 inception phase
Chapter no 4 inception phase
 
V model (software engineering)
V model (software engineering)V model (software engineering)
V model (software engineering)
 
Using formal methods in Industrial Software Development
Using formal methods in Industrial Software DevelopmentUsing formal methods in Industrial Software Development
Using formal methods in Industrial Software Development
 
9-Software Verification and Validation (Object Oriented Software Engineering ...
9-Software Verification and Validation (Object Oriented Software Engineering ...9-Software Verification and Validation (Object Oriented Software Engineering ...
9-Software Verification and Validation (Object Oriented Software Engineering ...
 
Toolbox of techniques for Architecture Reviews
Toolbox of techniques for Architecture ReviewsToolbox of techniques for Architecture Reviews
Toolbox of techniques for Architecture Reviews
 
Mi0033 software engineering...
Mi0033  software engineering...Mi0033  software engineering...
Mi0033 software engineering...
 
Introduction to formal methods
Introduction to formal methodsIntroduction to formal methods
Introduction to formal methods
 
Black box and white box testing
Black box and white box testingBlack box and white box testing
Black box and white box testing
 
Dynamic Testing
Dynamic TestingDynamic Testing
Dynamic Testing
 
Assessment 2 descriptor
Assessment 2  descriptorAssessment 2  descriptor
Assessment 2 descriptor
 
Black box testing
Black box testingBlack box testing
Black box testing
 
White box testing
White box testingWhite box testing
White box testing
 
Decision Support Analyss for Software Effort Estimation by Analogy
Decision Support Analyss for Software Effort Estimation by AnalogyDecision Support Analyss for Software Effort Estimation by Analogy
Decision Support Analyss for Software Effort Estimation by Analogy
 
SEKE 11 presentation
SEKE 11 presentationSEKE 11 presentation
SEKE 11 presentation
 
System development life_cycle
System development life_cycleSystem development life_cycle
System development life_cycle
 
Testcase
TestcaseTestcase
Testcase
 
Test-Driven Development Introduction
Test-Driven Development IntroductionTest-Driven Development Introduction
Test-Driven Development Introduction
 
Defect Life Cycle
Defect Life CycleDefect Life Cycle
Defect Life Cycle
 

Similar to Five Point Solutions Slide Presentation

Systems Analysis And Design 2
Systems Analysis And Design 2Systems Analysis And Design 2
Systems Analysis And Design 2MISY
 
Workshop on requirements and modeling at HAE 2015
Workshop on requirements and modeling at HAE 2015Workshop on requirements and modeling at HAE 2015
Workshop on requirements and modeling at HAE 2015Olivier Béghain
 
Complex System Engineering
Complex System EngineeringComplex System Engineering
Complex System EngineeringEmmanuel Fuchs
 
Software development life cycle
Software development life cycle Software development life cycle
Software development life cycle shefali mishra
 
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 days
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 daysPROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 days
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 daysGoLeanSixSigma.com
 
IFSM 461 Inspiring Innovation/tutorialrank.com
 IFSM 461 Inspiring Innovation/tutorialrank.com IFSM 461 Inspiring Innovation/tutorialrank.com
IFSM 461 Inspiring Innovation/tutorialrank.comjonhson137
 
IFSM 461 Effective Communication - tutorialrank.com
IFSM 461  Effective Communication - tutorialrank.comIFSM 461  Effective Communication - tutorialrank.com
IFSM 461 Effective Communication - tutorialrank.comBartholomew43
 
As Applied ICT term 3 Ex 10
As Applied ICT term 3 Ex 10As Applied ICT term 3 Ex 10
As Applied ICT term 3 Ex 10Jordan_0009
 
Onlinemovieticketbooking 120215060739-phpapp02
Onlinemovieticketbooking 120215060739-phpapp02Onlinemovieticketbooking 120215060739-phpapp02
Onlinemovieticketbooking 120215060739-phpapp02ISHA AHUJA
 
Ifsm 461 Education Specialist -snaptutorial.com
Ifsm 461 Education Specialist -snaptutorial.comIfsm 461 Education Specialist -snaptutorial.com
Ifsm 461 Education Specialist -snaptutorial.comDavisMurphyC58
 
IFSM 461 Education Organization - snaptutorial.com
IFSM 461  Education Organization - snaptutorial.comIFSM 461  Education Organization - snaptutorial.com
IFSM 461 Education Organization - snaptutorial.comdonaldzs207
 
IFSM 461 Enhance teaching - snaptutorial.com
IFSM 461  Enhance teaching - snaptutorial.comIFSM 461  Enhance teaching - snaptutorial.com
IFSM 461 Enhance teaching - snaptutorial.comDavisMurphyA52
 

Similar to Five Point Solutions Slide Presentation (20)

James hall ch 14
James hall ch 14James hall ch 14
James hall ch 14
 
Systems Analysis And Design 2
Systems Analysis And Design 2Systems Analysis And Design 2
Systems Analysis And Design 2
 
Workshop on requirements and modeling at HAE 2015
Workshop on requirements and modeling at HAE 2015Workshop on requirements and modeling at HAE 2015
Workshop on requirements and modeling at HAE 2015
 
Complex System Engineering
Complex System EngineeringComplex System Engineering
Complex System Engineering
 
Showcase 2
Showcase 2Showcase 2
Showcase 2
 
SE chapters 6-7
SE chapters 6-7SE chapters 6-7
SE chapters 6-7
 
Slides chapters 6-7
Slides chapters 6-7Slides chapters 6-7
Slides chapters 6-7
 
Software development life cycle
Software development life cycle Software development life cycle
Software development life cycle
 
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 days
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 daysPROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 days
PROJECT STORYBOARD: Reducing Software Bug Fix Lead Time From 25 to 15 days
 
IFSM 461 Inspiring Innovation/tutorialrank.com
 IFSM 461 Inspiring Innovation/tutorialrank.com IFSM 461 Inspiring Innovation/tutorialrank.com
IFSM 461 Inspiring Innovation/tutorialrank.com
 
VTU - MIS Module 4 - SDLC
VTU - MIS Module 4 - SDLCVTU - MIS Module 4 - SDLC
VTU - MIS Module 4 - SDLC
 
BIS Ch 4.ppt
BIS Ch 4.pptBIS Ch 4.ppt
BIS Ch 4.ppt
 
IFSM 461 Effective Communication - tutorialrank.com
IFSM 461  Effective Communication - tutorialrank.comIFSM 461  Effective Communication - tutorialrank.com
IFSM 461 Effective Communication - tutorialrank.com
 
As Applied ICT term 3 Ex 10
As Applied ICT term 3 Ex 10As Applied ICT term 3 Ex 10
As Applied ICT term 3 Ex 10
 
Onlinemovieticketbooking 120215060739-phpapp02
Onlinemovieticketbooking 120215060739-phpapp02Onlinemovieticketbooking 120215060739-phpapp02
Onlinemovieticketbooking 120215060739-phpapp02
 
Day5 R3 Basis Security
Day5 R3 Basis   SecurityDay5 R3 Basis   Security
Day5 R3 Basis Security
 
Ifsm 461 Education Specialist -snaptutorial.com
Ifsm 461 Education Specialist -snaptutorial.comIfsm 461 Education Specialist -snaptutorial.com
Ifsm 461 Education Specialist -snaptutorial.com
 
Chapter04
Chapter04Chapter04
Chapter04
 
IFSM 461 Education Organization - snaptutorial.com
IFSM 461  Education Organization - snaptutorial.comIFSM 461  Education Organization - snaptutorial.com
IFSM 461 Education Organization - snaptutorial.com
 
IFSM 461 Enhance teaching - snaptutorial.com
IFSM 461  Enhance teaching - snaptutorial.comIFSM 461  Enhance teaching - snaptutorial.com
IFSM 461 Enhance teaching - snaptutorial.com
 

Five Point Solutions Slide Presentation

  • 1. By FIVE POINT SOLUTIONS TOOLS ARE US (HIRE TRACKING SYSTEM)
  • 2. Team Leader Peter Kropp Standards Managers Jaya Swami Evan Panopoulos Testing Manager Fraser Hannell Admin Manager Joe Smith
  • 3.
  • 4. Primary roles:  Interview Summary Report  Project plan  Work breakdown structure  Allocate Programming Tasks  Edited and finalised SRS  Coding for Main Form and Hire Form  Assistance with Testing Procedures/Test Plan  Progress Report  Slide Presentation
  • 5.  The system request - The Problem !!  The planning and methods used to solve this problem  ……… and The Solution !!  Design of the GUI Application  Demonstration of the System  The Online Help facility  Conclusion and questions
  • 6. The Interview On the 26th July 2010, the project team (Five Point Solutions) interviewed the client ‘Tools Are Us’, as a means to gather information as to what is required with the upgraded system. Interview Summary Report - The Interview - System Request - The Report
  • 7. Five Point Solutions was asked to build a system that would:  Track the availability and scheduling of equipment (tools, machinery, vehicles, etc) that customers have hired  Allow the adding, editing and deleting of customers and equipment available for hire  Access to an online help facility  To be able to generate reports
  • 8.  Planning  Analysis  Design  Implementation  Support/Closing The System Methodology Report outlines how the System Development Life Cycle (SDLC), a systematic and orderly approach, will be used for the implementation of the new system. It comprises of the following phases:
  • 9. Hire Tracking System PROJECT PLAN (Five Point Solutions) Author : Peter Kropp The project plan will describe, in detail, how Five Point Solutions will meet the requirements of the new Hire Tracking System, as proposed by Tools Are Us. The basis of this project plan is to fully document the development of the system, phase by phase, that will be based on the standards of the System Development Life Cycle (SDLC).
  • 10. GANTT CHART – PROJECT OUTLINE (Work Breakdown Structure)
  • 12. Primary roles:  Prioritising System Requirements  Creation of Events List  Development of Modeled Events  Coding for Login Form and Reserve Form (and assistance with other forms)  Assistance with Testing Procedures  Disaster Recovery Plan
  • 13. The Hire Tracking System will:  allow the user to track the hiring of equipment items to customers  allow the user to reserve equipment items for the customer, if unavailable at a particular time.  allow a user with admin rights (only) to Add, Edit and Delete customer details, equipment item details and category details.
  • 14. 1. Customer registers details 2. Customer enquires to availability of equipment item. 3. If unavailable, equipment item is reserved. 4. If available, equipment item is hired. 5. Equipment item is returned. 6. Customer pays a fee, if an item is returned late
  • 15. 4. If available, equipment item is hired
  • 16. [Tools Are Us] Disaster Recovery Plan by [Jaya Swami] 19/10/2010 The Disaster Recovery Plan (DRP) is a plan that was developed and its intended purpose is to be used in the event of a disaster (e.g. Fire) at Tool Are Us.
  • 18. Primary roles:  Context Flow Diagram (CFD)  Data Flow Diagram (DFD)  Coding for Categories Form  Online Help Facility
  • 19.
  • 20.
  • 22. Primary roles:  Entity Relationship Diagram (ERD)  Database development  Data Dictionary/Data Elements  Coding for Equipment Form  Technical Manual  Testing Plan/Testing Procedures
  • 23. The Entity Relationship (ER) Diagram is represented as follows.
  • 24. Example: Customer’s Table - FieldField TypeType Form AttributeForm Attribute CustomerID Numeric (7 Numeric) Text Box Staff Boolean(Yes/No) Check Box LastName Text(40 Alphabetical) Text Box FirstName Text(40 Alphabetical) Text Box Address Text (40 Alphanumeric) Text Box Suburb Text(40 Alphabetical) Text Box State Text(3 Alphabetical) Text Box PostCode Text(4 Numeric) Text Box HomeNumber Text(8 Numeric) Text Box MobileNumber Text(10 Numeric) Text Box Email Text(40 Alphanumeric) Text Box
  • 26.
  • 27. A document created which describes the technical aspects of the system.
  • 28. Consists of:  Testing Plan  Testing Data  Test Reports
  • 29. Test data for Customer Form:
  • 31. Primary roles:  System Methodology Report  SRS (with contributions from team members)  Assistance with Data Dictionary/Data Elements  Design of GUI Application  Coding of Customer Form  System Reports (using Crystal Reports)  User Manual  Assistance with Slide Presentation
  • 32. The Software Requirement Specification (SRS) document outlines the requirements for the implementation of a Hire Tracking System for ‘Tools Are Us’.
  • 33. Documents to the User how to navigate through the new/upgraded system.