1 / 22

Common mistakes in Core FC Package

Common mistakes in Core FC Package. October 15, 2010. Outline. OCD PRO SSAD LCP FED. Operational Concept Description. Benefit Chain Diagram How each stakeholder create benefit , especially in operation phase ? Should correspond to your organization goals and core capabilities

nate
Download Presentation

Common mistakes in Core FC Package

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. Common mistakes in Core FC Package October 15, 2010

  2. Outline • OCD • PRO • SSAD • LCP • FED

  3. Operational Concept Description • Benefit Chain Diagram • How each stakeholder create benefit, especially in operation phase ? • Should correspond to your organization goals and core capabilities • Element Relationship Diagram • What are the elements that you develop(put them in dashed box) ? • What are the elements that you have to coordinate/ interoperate (put them outside the dashed box)? • Business Workflow • Sequence of worksthat stakeholdershave to perform • Will reflect on how your new system improve the current workflow • Do not care about how your system works (not a technical flow)

  4. A not so good Benefit Chain Diagram Overemphasized • Common Mistakes • Focus too much on what you develop • Missing critical stakeholder • Missing core initiatives • Missing contributions • Wrong notations • Initiative and outcome don’t match Underemphasized

  5. A Good example of Benefit Chain Diagram

  6. Database Management System Requests for access Visitor Activates Creates and manages show AUTHENTICATION Stage Manager Task Tracker Project Operations Tracked using Username/ Password Manages designer tasks Tasks Controls Editor/Designer Scheduling Data Budget Data User View schedule and tasks Uses Uses Show Roster Database Creates Show, Budget manages user account Creates report using budget data Administrator Reporting A not so good example of Element Relationship Diagram • Common Mistakes • Unorganized drawing • Mixing between the module you develop and module you link to • missing elements that you link with

  7. A good example of Element Relationship Diagram

  8. System User A not so good example Visit website homepage Already a member? • Common Mistakes • Focus on technical flow • Too detail on system’s behavior instead of “business” transaction no Sign-up yes Log-in Access training videos and material, Provide feedback, securely download material, Access the discussion board, Online shopping, Access coupons

  9. A good example of Business Workflow Diagram

  10. Prototype • Critical issues and concerns are not stated • State the specifics of each • Be specific to what prototypes are to address • Only UI is not sufficient • If UI is the only concern, then OK • Otherwise, discuss about how you meet the capabilities or level of service

  11. SSAD • Generally good in translating the OOA&D concepts into analysis • Some misunderstanding in conceptual separations of different diagrams/models

  12. System Context Diagram • Incorrect hierarchy of actor classes • Should match exactly with the use-case model • Look for common functionalities • Incorrect system scope • What you are developing • External systems • Not an actor • Show as another system/component

  13. Artifacts and Information • Many components are not artifacts • Association = sharing of information • Persistent data that are stored/used by system for execution • Think in terms of database design. • The information architecture of the system

  14. Use-Case • Hierarchy of users • Look for common use-cases • Missing related capability requirements/win conditions • Incorrect pre-/post- conditions • Course of actions not shown in sequence • Missing actors described in the system context

  15. Pre-/Post- Conditions Bad precondition: “User wants to access the website” “User needs to provide valid information” Good precondition: “User is Administrator. Database is initialized” Bad postcondition: “Information was changed” Good postcondition: “User information is saved to the database.” “If username and password are verified, user is granted access; otherwise, user is denied access.”

  16. Course of Actions Good Bad

  17. Use-Case Bad Good

  18. FED • 4.2.1 NDI/NCS Candidates • For each functionality you are looking for in NDI/NCS, you should evaluate more than 1 product • 4.2.2 NDI/NCS Evaluation Criteria • Trace back with OCD for Capability Goals and LOS Goals

  19. 4.2.1 NDI/NCS Candidates • Think about what are available in the market • List the possible candidates (more than one) • Prove by using 4.2.2 criteria and show results in 4.2.3 results which your choice is the best

  20. For example: you are looking for one or more NDI/NCS that has the following functionalities • content management system • an online calendar tool Example:

  21. 4.2.2 NDI/NCS Evaluation Criteria • One table for the attributes • Check ICM EPG for common attribute • Check your OCD for LOS goals • Example: Concurrency, 24/7 availability, interoperability • At least one table for the features • Check your OCD for capability goals • Elaborate Capability Goals into features or sub features • Could separate into many tables for different Capability, e.g. one table for CMS, one table for online calendar tool • You will later use table of attributes and table of features as a scoring guide in 4.2.3

  22. Example of table of features Features for the Content Management system Features for the Content Management system

More Related