Roger Heller Q/P Management Group, Inc. 10 Bow Street Stoneham, MA 02180 Tel: (781) 438-2692

1. Using Joint Application Design and Function Points to Better Manager and Control Software Development Projects Roger Heller Q/P Management Group, Inc. 10 Bow Street Stoneham, MA 02180 Tel: (781) 438-2692 FAX: (781) 438-5549 http://www.qpmg.com

2. Using Joint Application Design and Function Points to Better Manager and Control Software Development Projects The methodologies reflected in the enclosed material, including the benchmark comparisons, are confidential and proprietary information of Q/P Management Group, Inc. and can not be reproduced without the expressed written permission of Q/P Management Group, Inc.

3. Why do Function Points and Joint Application Design Techniques Work So Well Together? Objectives of Function Point Analysis • Measures software by quantifying the functionality provided to the user • Based primarily on the logical design • Measures the functionality the user requests and receives Objectives of Joint Application Design Sessions • Bring users and systems developers together in a productive creative workshop environment to obtain quality requirements and specifications • Establish joint ownership of the project and the deliverables Together they provide a mechanism to define, size, estimate and manage scope of development projects.

4. Functional Requirements Analysis Process Joint Application Design Function Point Analysis Functional Requirements Project Size Establish Project Estimates • Project • Effort • Schedule • Staffing • Cost

5. How Do FPA and JAD Help Define Requirements Functional Requirements Analysis Process Joint Application Design • Utilizes a facilitated structured workshops to identify requirements • Requires planning and preparation • Involves both users and IS personnel • Provides an agreed upon understanding of requirements Function Point Analysis • Documents functionality from the user and technical perspective • Unit of Measure to size and estimate the effort • Vehicle to help manage change of scope • Helps identify gaps in the requirements

6. The Functional Requirements Analysis (FRA) Process Planning and Preparation The Players Conducting the Workshop

7. Planning the Workshop • Purpose is to identify and document the business needs • Knowledgeable business users are interviewed • Systems staff with business knowledge participate • Interview results will provide the framework to structure the workshop • Identify the scope of the workshop • Determine the number of workshop sessions • Identify the specific participants

8. Planning the Session The Type of Project Determines the focus of the Interviews • Enhancement Project • An overview of the current system is provided • Current application interfaces are identified • User documentation or existing systems documents are reviewed • New Development Project • A high level overview of the business needs is provided • Interface requirements are identified • High-level functional requirements are reviewed

9. Planning Session Results Planning Session Project Purpose High Level Requirements Project Purpose Impacted Systems

10. Example of Deliverables from the Planning Session High Level Requirements • Implement a Time Accounting System for I/S Project Purpose • The I/S department is considering outsourcing but needs to understand current productivity levels to determine if it is needed and if so what improvements can they expect from the outsourcer Impacted Existing Systems • Software Measurement tool needs hours from Time Accounting • Finance needs hours for payroll • HR needs staffing levels

11. The Players Participants must be knowledgeable of the business and systems issues that the workshop will address • Sponsors • Individuals that have knowledge of the strategic business issues, organizational goals, and constraints • Sanctions the project and provides direction as needed • Business Users or Their Representatives • Participants with extensive knowledge of the current business functions • Participants who understand the future business requirements and required strategies • Must have authority to make decisions related to the functional aspects and deployment of the project

12. The Players • System Experts • Individuals that have extensive knowledge of existing systems • Technology experience as it relates to the business requirements of the organization is required • System Specialists • Participants that provide expertise on a specific topic • These individuals attend the sessions when required for their specific topics

13. The Players • Workshop Leader • Individual that has excellent facilitator skills and will facilitate the workshop sessions • The facilitator also has a high level of expertise in the JAD and Function Point Analysis Methodologies • Workshop Analyst • The analyst has effective facilitation skills • The analyst is highly experienced in JAD and Function Point Analysis Methodologies • This participant is required to have a strong application development background

14. The Players The Workshop Facilitator Leads an Interactive Session TCAST Workshop objectives are to develop comprehensive requirements and establish a partnership that will lead to joint ownership of the project

15. Conducting the Workshop A series of workshop sessions are conducted based on the scope of the effort and the number of subject areas identified during the planning phase • Kickoff Session • Subject Area Session(s) • Wrap-up Session

16. Conducting the workshop The Kickoff Session • The initial session is attended by all participants • The facilitator provides an overview of the workshop process • Describes the sequence of events • Discusses the roles and responsibility of the participants • Identifies any materials and documents that should be brought to each of the sessions • The sponsor provides an overview of the business requirements • Shows support for the project • Commits the required resources to the workshop effort

17. Workshop Schedule Issues & Constraints List Assumptions List Action Items List Kickoff Session Results Kickoff Session

18. Examples of Kick-off Session Deliverables Workshop Schedule • The user representative, user liaison, lead analyst and FRA team • The sessions will be held Tuesday and Thursday from 9:00 – 12:00 for the next 2 weeks • Meeting location – To Be Determined Assumptions • The solution will be completed by the end of the 4th quarter • The solution will conform to the existing technologies Issues/Constraints • The project must be completed using existing headcount • The business needs are not fully understood Action Items • Lori finalize the location of the workshops and notify the team • Sherry to update project plan to reflect Workshop Schedule

19. Conducting the Workshop Subject Area Session • Subject Matter Expert provides an overview of the session topic • The impact of the required enhancements or new development based on the business needs is identified • The facilitator leads the participants through the collection of the functional requirements based on the specified business needs • As the requirements are identified they are related to each of the five FPA function types • High level processing logic is captured • The Workshop Analyst captures the functional requirements • These requirements are input into the function point model as data or transaction functions

20. Overview of the Time Accounting System I/S Staffs Software Measurement • Report Metrics • Hours by Activity • Productivity by project • Departmental productivity • Report time by • Project • Activity • Department • Non-productive • Report time weekly Data to Finance Data to HR

21. Subject Area Session(s) Assumptions, Issues & Constraints RequirementsDetails Function Point Count Action Items List Subject Area Session Results

22. Conducting the Workshop Workshop Wrap-up Session • A final review is conducted with all participants • Consensus is reached on the solution • The sponsors provide direction on the next steps required for project initiation

23. Workshop Session(s) Assumptions, Issues & Constraints Fully Documented Requirements Detail Function Point Count Action Items List The Workshop Results

24. Examples of Deliverables from Workshop Requirements Function Point Count • Requirement # TAS-203029138 • All I/S staff must be able to input time data • Input • Project/Activity & Time data by employee • Process • The logic of the TAS system will allow the user to add/change and delete time data • The logic will validate project codes against a project file maintained by HR • Output • N/a

25. Workshop Session(s) Terms & Definitions Project Attribute Analysis Internal Impacts External Impacts The Workshop Results

26. Examples of Deliverables from Workshop Project Attribute/Risk Analysis • Internal Impacts • All system staffs will need to carefully track their time and activities • Management needs to manage staff concerns related to potential outsourcing • External Impacts • Potential COTS vendor is behind schedule with their products • Terms/Definitions • FTP = Full Time Person • TAS = Time Accounting System • COTS = Commercial off the Shelf

27. The Final Step – Project Estimation Once the project has been clearly defined and sized, the effort required to develop the system can be determined • The project estimate is completed • Historical benchmark data is a primary component of the estimate • The estimate is based on the project size produced from the Function Point Count • Project attribute information provided by the project team is also input into the estimating model

28. Project Estimating Process Staffing Requirements Effort Estimate Schedule Cost Estimates The Project Estimating Results

29. Example of Project Estimate Report

30. Benefits of Functional Requirements Analysis • Defines the future system from the business user’s perspective • A team of business managers and system developers drive the process • Facilitated sessions ensure that requirements identified are comprehensive and agreed upon by the participants • A function point count is completed that establishes the size of the project • The estimate is based on the FPA size and the project attribute information provided by the project team • The initial project effort, staffing and schedule estimates are developed as a natural by-product of the requirements definition process • The results of combining the Joint Application Design and Function Point Analysis methodologies produces a blueprint for the future business processes and system

31. Functional Requirements Analysis “ It is not what you know but when you know it that counts”