Pieter Van Gorp's List: TU/e Design Course OML

• The Business Analyst's Handbook [Paperback
• The Business Analyst's Handbook

  • seems very valuable, since it describes concrete meetings and deliverables for the BACH1 students...

• UML For The IT Business Analyst

• Use Case Driven Object Modeling with UMLTheory and Practice

• Conducting Validation Tests

• Assessing the Project Plan
   
   

  The intent of this checklist is to assess the completeness of the Software Project Plan (SEPA 5/e, Part Two). The more questions that elicit a negative response, the higher the risk that the Plan is incomplete.

   
   
  • Is the statement of scope accurate and consistent with the needs of the customer? 
  • Is the statement of scope bounded? 
  • Are the software functions noted consistent with the scope? 
  • Is software performance and behavior addressed within the statement of scope? 
  • Are constraints that will affect the product or the project noted and described? 
  • Are estimates developed reasonably (see Checklist: Cost Estimates and Schedule) 
  • Have all required resources including hardware, software, tools, people, and others been fully described? 
  • Have all project risks been fully described: (see Checklist: Airlie Project Quicklook and Checklist: Risk Analysis) 
  • Has a risk table been developed? (see Checklist: Risk Analysis) 
  • Has a Risk Mitigation, Monitoring, and Management Plan been developed? (see Checklist: Risk Analysis) 
  • Is the project schedule developed reasonably (see Checklist: Cost Estimates and Schedule) 
  • Is the project team staffed and organized appropriately (see Checklist: Building an Effective Software Engineering Team) 
  • Has an SQA Plan been developed for this project? (see Checklist: Assessing the SQA Process) 
  • Has an SCM Plan been developed for this project? (see Checklist: Assessing the SCM Process)

•   Adaptable Process Model
• SYSTEM SPECIFICATION

• System Specification
• Software Project Plan
• SCM Plan
• Software Requirements Specification
• Test Specification

3 more annotations...

• The APM Process
• concept development
• new application development
• application enhancement
• Web application development

3 more annotations...

• System Specification
• SQA Plan
• SCM Plan
• Software Requirements Specification
• NASA Software Engineering Documents

3 more annotations...

•  

  FP   CALCULATOR

• Function Point Calculators (several)

• Chapter   26: Software Cost Estimation. This chapter introduces   the problem of software cost estimation, including some discussion   of software productivity. It includes a brief description   of the COCOMO II cost model.

• Vision and Scope Document Template
• Requirements Prioritization Spreadsheet

• Software  Project Management 5/e
  By: Bob Hughes &  Mike Cotterell
  ISBN:     9780077122799
    May 2009

• MS Project can create a PERT chart from a Gantt chart
• The critical path (shown in red) is a series of tasks that must be completed on schedule for a project to finish on schedule. Each task on the critical path is a critical task. Most tasks in a typical project have some slack and can therefore be delayed a little without affecting the project finish date. Those tasks that cannot be delayed without affecting the project finish date are the critical tasks. As you modify tasks to resolve overallocations or other problems in your schedule, be aware of the critical tasks and that changes to them will affect your project finish date.