ec-06aV1

ec-06aV1 - University of Southern California Center for...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
University of Southern California Center for Systems and Software Engineering Simplifiers & Complicators and IICM-Sw Barry Boehm & A Winsor Brown CS 577a September 4, 2009
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
University of Southern California Center for Systems and Software Engineering The WinWin Approach The win-win approach is a set of principles, practices, and tools, that enable a set of interdependent stakeholders to work out a mutually satisfactory (win-win) set of shared commitments . 09/08/08 ©USC-CSSE 2
Background image of page 2
University of Southern California Center for Systems and Software Engineering Formulating Reasonable Win Conditions Can Be Hard: Two Cultures 09/08/08 ©USC-CSSE 3 Customers Developers - No idea of the relative cost and difficulty of satisfying win conditions. - Likely to insist on infeasible win conditions as statements of need. - Likely to refrain from suggesting win conditions which they think are difficult to implement, but may be easy. - Golden rule: Do unto others as you would have others do unto you. -Don’t understand customer’s workflow - Build a system friendly to the programmers.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
University of Southern California Center for Systems and Software Engineering 09/08/08 ©USC-CSSE 4 Conflicts in Win Conditions and Expectations Hard things for software people “If you can do queries with all those ands, ors, synonyms, data ranges, etc., it should be easy to do natural language queries.” “If you can scan the document and digitize the text, it should be easy to digitize the figures too.” Hard things for librarians “It was nice that you could add this access feature, but it overly (centralizes, decentralizes) control of our intellectual property rights.” “It was nice that you could extend the system to serve the medical people, but they haven’t agreed to live with our usage guidelines.”
Background image of page 4
University of Southern California Center for Systems and Software Engineering Simplifiers & Complicators: A Method for Dealing With Two-Cultures Problem Identify appropriate domain and System Boundary Diagram for project Helps set context and acts as communication tool between clients and developers? Generate/refine high-level architecture ("Element Relationship Diagram" AKA Component & Connector diagram; more later ) for project Acts as “context diagram” Map initial requirements (win conditions) to WinWin Taxonomy These will be used later as a requirements outline (SSRD §2, 3 and 4) Top-n risk identification This will be managed for your actual project using DART (later lecture) Identify simplifiers and complicators For both developers and clients First general then specific Note: These activities may be concurrent and iterative. 09/08/08 ©USC-CSSE 5
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
University of Southern California Center for Systems and Software Engineering 09/08/08 ©USC-CSSE 6 S&C Subdomain (General) Type of Application System Boundary Diagram Multimedia Archive * Assets * … Archive Use standard query languages Use standard or COTS search engine Uniform media format Developer Simplifiers Developer Complicators
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 29

ec-06aV1 - University of Southern California Center for...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online