Common Mistakes in Core FCP

1. Common Mistakes in Core FCP OCD, Prototype & SSRD -NupulKukreja

2. Operational Concept Description • Initiatives in Benefits Chain: • They ARE NOT interactions with the system • They provide information as to what needs to be done to realize that benefit • Using the system, obtain reports, generate reports, update data ARE NOT INITIATIVES • Simple test: If you can put a ‘+’ sign at the end of the initiative’s arrow and if it “adds to the benefit” it’s an initiative, else you need to reconsider

3. OCD – Cont’d • Benefits: • Must be in sync with those on Winbook. No need to do double effort in ‘thinking’ them. Augment/sync the list with benefits logged in Winbook • Assumptions: • They’re business assumptions AND NOT technical assumptions. Ex: internet is available, people will use the system, will be periodically update etc., • Valid: Usability is a key factor in attracting more users OR The research people indeed want data about various localities to be accessed easily

4. OCD – Cont’d • Business Workflow • PLEASE use UML 2.x Activity Diagram notation (ONLY)!! • Element Relationship Diagram • NOT a workflow diagram • More like “high level architecture” • Think of “components” that are involved (elements) and “connectors” how/what they communicate amongst themselves (relationships) • Authentication is usually “inside” the system’s boundary • Administrator, User, Parent, Teacher ARE NOT Components! • Please involve System Architect so that the architecture/design is in sync with the vision!

5. Prototype Report • UI Prototype != Layout of page • Please add “realistic” information to the ‘panes’ to make it ‘look and feel real’. • It’s a visualization of the “to-be” system not a set of geometric drawings – feel free to add realistic dummy data to make it ‘come to life’ Menu Profile (info) List of Win Conditions, Issues & Options Categorizing menu

6. Prototype Report – Cont’d • Navigation Flow • NOT a workflow • It show’s how the ‘pages/screens’ are linked i.e., from which page can you navigate to which page(s). (Think of it as ‘hyperlinks’) • Do not add ‘roles’ like admin, user, teacher, student unless those are separate pages! • It may look like a tree but it’s okay if it looks like a graph too! (showing the interlink/navigability)

7. Prototype Report – Cont’d • Prototypes must be ‘linked’ to the OCD – prototype those UIs which directly link to capability goals • It’s probably the umpteenth time: LOGIN/LOGOUT IS NOT A CORE CRITICAL CAPABILITY (unless it’s for your project • Use Capability/LOS goals as a guide to know which UI to prototype • Should add value to user/client. Please prototype with this in mind – The ‘consumer’ of the prototype must OK it before it goes into the report (usually the client in most cases )

8. SSRD • Requirements are those which are suggested/mandated/required by the client AND NOT by the development team • Ex.: Usage of Eclipse/Visual Studio or Java/C# as the development language are NOT requirements if they have been put forth by the developers (it’s a way of realizing/implementing the requirements, but NOT a requirement!) • The Priorities (MoSCoW) should directly stem from the WinWin Prioritization • The ‘requirement’ at the bottom of the list is doubtfully a must have, but the one at the top, probably is