1 / 7

Effective DFD and Use Case Alignment Strategy | PPM Feedback Reports

Understand how DFD designs and Use Cases align, ensuring consistency in software design. Tips on teamwork, terminology, and project context. Learn to handle requirements changes with MSProject.

marjorie-lazos
Download Presentation

Effective DFD and Use Case Alignment Strategy | PPM Feedback Reports

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tutorial Week 7 PPM feedback PSR and Project Review Report

  2. PPM Feedback • DFD designs are data based, Use cases are process based. When you expand a DFD level 0 process to enact the processes required for the Use Cases, you WILL NOT have a separate DFD diagram for each use case. The functionality of each Use Case overlap or are related in terms of how they deal with the data (eg both update the Risk DataBase). Hence they are part of the same DFD level 1 (possibley expanded for more detail to level 2).

  3. PPM Feedback cont • Design should be consistent.If you work in co-operative pairs, splitting the work, this tends to show in the design. Terms used in data flows in the DFD, should be the same used in Data Table, etc • Context and Level 0 Diagram should be generic to whole project.Base it on the E-R Digram data entities as your data stores. Then you decide which process deals with risk at level 0 and expand that. • Risk is an expansion of the process that maintains the Project Data base.See E-R Diagram

  4. PPM feedback cont. • The Use Cases specify specific steps, these should be in the Interface design. Do not re-order the steps or skip steps • The requirements of the project included pseudo code for bottom level functionality in the DFD. See ProjectProcessDesign.doc template • QA included issues relating to keeping track of user input. This should appear in your interface or data table, eg link risk data to the participantID who entered it.

  5. PPM Feedback - final • Your MSProject work deals with designs and designers. The Software you are designing deals with Cheese projects. Your design should not refer to designers or Cheese makers. These are specific projects, and SIP wants a generic project managements software that can handle the Farm Cheese project, and other similar collaborative projects. Design and Cheese become Work Products, designers and cheese makers are Participants. Use general terms.

  6. Change Management • On the web there is a requirements change. Enter a plan in MSProject to change your design to include this, but do not include in your design (you do not have the use case yet). • When you submit your Project Status Reports, tell us how this changed your plan, what time it took to re-plan, etc • Also when you submit a PSR make sure you send us a report form MSPRoject showing the relevant data, ie your Actual Work times and Planned Times, in separate columns.

  7. Summary of Task • To make a new subcategory of tasks (ie a bold line that summaries a collection of tasks) look at the MSProject help menu Contents under Build a plan Define phases and create a task list Create phases and subphases in a project

More Related