CPET 545 SOA and Enterprise Applications. SOA Final Project Project Scope Management

Transcription

1 CPET 545 SOA and Enterprise Applications Examples of Tasks and Subtasks o SOA Project Plan (checklist) Statement of work Resources Schedule Risk plan SOA Final Project Project Scope Management o SOA Rollout Plan SOA Server platform installation and configuration SOA Governance SOA Software Configuration SOA Software Quality Assurance Analysis Design Implementation Testing Rollout and integration with existing systems SOA Documentation User documentation and packaging User training SOA Rollout Plan & Review o SOA Software Requirements Development tools and techniques Standards Requirements Elicitation (interviews, observations, discussion & summary, use cases, expert judgment) SOA Software Requirements & Review o SOS Risk Plan Identifying risks brainstorm: delay, out of business, etc Risk analysis Risk treatment Monitoring and controlling risks Risk mitigation SOA Risk Plan & Review o SOA System Analysis SOA Reference Architecture Requirement Specifications

2 Introduction o Purpose o Scope o System overview o References Definitions Use Cases Functional requirements o Name o Summary o Rationale o Requirements o References Non-functional requirements o Summary o Rationale o Requirements o References Examples of non-functional requirements Availability Efficiency Flexibility Portability Integrity Performance Reliability Reusability Robustness Scalability Usability Interface specifications Functional specifications Service specifications Technical/performance specifications Process specification Database integration specification Legacy system integration specification SOA Analysis Report & Reviews o SOA System Design Development of Services Service contracts Schema WSDL etc

3 Business process modeling Schema WSDL Legacy APIs BPEL SOA System Design Report & Review o SOA Software Implementation Development of Service and Unit Testing Business process composition/orchestration System integration SOA System Demo SOA Implementation Report & Review o SOA Software System Test (Verification and Validation) Test plans (IEEE 829) Purpose Features to be tested Features not to be tested Approach (how the test will be performed) Suspension criteria and resumption criteria Environmental Needs Schedule Acceptance criteria Roles and responsibilities Test cases Name Requirement Preconditions Steps Expected results Integration test Plans Specifications Test cases Process test Plans Specifications Test cases System test Plans Specifications Test cases System Test Report & Review

4 o SOA Software System Acceptance Test Acceptance criteria from a test plan Test environment Acceptance test specifications Acceptance test cases Defect tracking and triage Performance testing Acceptance Test Report & Review o SOA Software Delivery o SOA Software Maintenance Internal training support and sales Post acceptance support Technical support Control and Tracking o Project Planning: Estimate budges Schedules, and Defect rates o Project Management: Track and control costs Schedule, and Quality o Process improvement: Provide baseline date Trace root cause of problems and defects Identify changes from baseline data, and Measure trends Software Metrics, Measures, and Measurement o Productivity models and measures o Quality models and measures o Reliability models and measures o Performance models and evaluation o Cost and schedule estimation o Data collection o Structure and complexity metrics Core Metrics Examples and Standards o NASA s DA3 MOD Core Metrics o Software Engineering Laboratory Core Metrics o United States Army Core Metrics o Department of Defense Core Metrics

5 o USAF Software Metrics Policy o IEEE Standard : Standard for Software Project Management Plans o IEEE Standard : Standard for Software Productivity Metrics o IEEE Standard : Standard for Software Quality Assurance Plans o IEEE Standard : Standard for Software Verification and Validation o IEEE Standard : Standard for Software Maintenance o IEEE Standard : Standard Classification for Software Anomalies Department of Defense Core Metrics (DoD) o Size Line of codes (LOC) Progress Reuse Rework o Effort Staff-hours expended Cost Rework Resource allocations o Schedule Calendar dates Schedule o Quality Counts of problems and/or defects Readiness for delivery Improvement trends Rework USAF Software Metrics Policy, 1994, o Size o Efforts (staff labor) o Schedule o Software Quality o Rework SOA Metrics see references o Cost ROI To build new service Average cost to run a service Governance cost o Elapse time to build a new service (agility metric) o Service utilization o etc

6 Other Tasks Easily Forgotten o Familiarization o Business justification o Selection or design of project processes o Getting documents agreed with customers or users o Design and agreement of user interface o Hardware selection, purchase, installation, and support o System software and development tools selection, purchase, installation, and support o Setting up and understanding bought-in packages or reused modules o Feasibility study and/or proof of concept exercise o Fallback and recovery schedules o Security related issues o Walk-through, progress, quality reviews o The project office technical management, secretarial support, team leaders, team coordination, system management, quality assurance o Project management o Management of subcontractors o Technical documentation o etc PMBOK Guide 2004 [2] 5 Project Scope Management 5.1 Scope Planning Scope Planning: Inputs.1 Enterprise Environmental Factors.2 Organizational Process Assets.3 Project Charter.4 Preliminary Project Scope Statement.5 Project Management Plan Scope Planning: Tool and Techniques.1 Expert Judgment.2 Templates, Forms, Standards Scope Planning: Outputs.1 Project Scope Management Plan 5.2 Scope Definition Scope Definition: Inputs.1 Organizational Process Assets.2 Project Charter.3 Preliminary Project Scope Statement.4 Project Scope Management Plan.5 Approved Change Requests Scope Definition: Tool and Techniques.1 Product Analysis.2 Alternative Identification

7 .3 Expert Judgment.4 Stakeholder Analysis Scope Definition: Outputs.1 Project Scope Statement Project objectives Product scope description Project requirements Project boundaries Project deliverables Product acceptance criteria Project constraints Project assumptions Initial project organization Initial defined risks Schedule milestones Fund limitation Cost estimate Project configuration management requirements Project specifications Approved requirements.2 Requested Changes.3 Project Scope Management Plan (Updates) 5.3 Create WBS Create WBS: Inputs.1 Organizational Process Assets.2 Project Scope Statement.3 Project Scope Management Plan.4 Approved Change Requests Create WBS: Tools and Techniques.1 Work Breakdown Structure Templates.2 Decomposition Create WBS: Outputs.1 Project Scope Statement (Updates).2 Work Breakdown Structure Organizational Breakdown Structure (OBS) Bill of Materials (BOM) Risk Breakdown Structure (RBS) Resource Breakdown Structure (RBS).3 WBS Dictionary.4 Scope Baseline.5 Project Scope Management Plan (Updates) 5.4 Scope Verification Scope Verification: Inputs

8 .1 Project Scope Statement.2 WBS Dictionary.3 Project Scope Management Plan.4 Deliverables Scope Verification: Tools and Techniques.1 Inspection Scope Verification: Outputs.1 Accepted Deliverables.2 Requested Changes.3 Recommended Corrective Actions 5.5 Scope Control Scope Control: Inputs.1 Project Scope Statement.2 Work Breakdown Structure.3 WBS Dictionary.4 Project Scope Management Plan.5 Performance Reports.6 Approved Change Requests.7 Work Performance Information Scope Control: Tools and Techniques.1 Change Control System.2 Variance Analysis.3 Replanning.4 Configuration Management System Scope Control: Outputs.1 Project Scope Statement (Updates).2 Work Breakdown Structure (Updates).3 WBS Dictionary (Updates).4 Scope Baseline (Updates).5 Requested Changes.6 Recommended Corrective Action.7 Organizational Process Assets (Updates).8 Organizational Plan (Updates) References [1 ] Paul Coombs, IT Project Estimation: A Practical Guide to the Costing of Software, 2003, Cambridge University Press, ISBN x [2 ] A Guide to the Project Management Body of Knowledge, (PMBOK Guide), 3 rd, by Project Management Institute, ANSI/PMI [3 ] Pricing Strategies, from Wikipedia, the free Encyclopedia, [4 ] Harold Kerzner, Project Management: A System Approach to Planning, Scheduling, and Controlling, 2006, Wiley, ISBN [5 ] Kathy Schwalbe, Information Technology Project Management, 4 th Edition, Thomson, ISBN

9 [6 ] Risk Analysis & Risk Management, [7 ] Mantel, Meredith, Shafer, and Sutton, Project Management in Practice, 3 rd edition, Wiley, 2007, ISBN [8 ] Software Engineering Institute, [9 ] Software Measurement for DoD Systems: Recommendations for Initial Core Measures: [10 ] Army Software Metrics Office (ASMO), [11 ] Integrated SOA Governance, [12 ] Managing the QoS of E-Government: Metrics for Large Scale SOA, by Mauricio Monsalve, 2007 XXVI International Conference of the Chilean Computer Science Society. [13 ] Understanding Features in SOA: Some Experiences from Distributed Systems, N. Wilde, S. Simmons, M. Pressel, and J. Vandeville, Proceedings of 2 nd International Workshop on Systems Development in SOA Environments, Leipzig, Germany, May 11, [14 ] Chapter 9.7 SOA Metrics of Executing SOA: A Practical Guide for the Service-Oriented Architecture, by N. Bieberstein, R. G. Laird, K. Jones, and T. Mitra, May 2008, from IBM Press, ISBN [15 ] What Metrics Can you Use for SOA, by Loraine Lawson, Dec. 5, 2007, [16 ] The 19 th Open Grid Forum OGF19, Jan. 29-Feb. 2, 2007, NC, USA, [17 ] OGF Workshop: SOA Metrics What do Users Need to Know? [18 ] SOA Metrics, Optimization/Serve-Business-Goals/SOA-Metrics.html [19 ] Preliminary SOA Indicators/Metrics: A Staring point for Technical Discussion/Elaboration, V 1.055, Nov. 5, 2006, by John Salasin, NIST, [20 ] Questionnaire/Survey on SOA Metrics, [21 ] SOA Metrics for Continuous Improvement, by Saul Caganoff, Jan. 7, 2008,