1. Developing a Rich Picture for an Information Sharing System Walt Scacchi, Ph.D. Systems Analysis and Design for ECommerce, EBusiness, and other Enterprise Systems M 271/F271 Spring 2003

2. What we are trying to develop A Rich Picture that captures functional and non-functional enterprise system requirements Communities of People and Technical Systems have requirements Requirements include community concerns, participant roles, system components, relations/activities, and overall processes A baseline example follows.

3. MBA students GSM staff Faculty GSM IS Dev. Staff Catalyst-Web server Email GSM course content Forum & Chat/IRC Centralize IS support and content mgmt. Communicate, discuss, & learn Communicate & support faculty & students Communicate, discuss, teach, & research Manage DB content Dev.& Test Create/edit & upload content Download content Catalyst.gsm.uci.edu: a for information sharing Upload msgs or bio content Edit/upload content Download content corporate portal Provide high- quality course content Help faculty, students, staff with h/w, s/w & network Fund, delegate, & promote Dean’s Office

4. Making Reusable Rich Pictures Domain models should be reusable Rich Pictures are a kind of (visual requirements) domain model Applications sub-domains use (domain- specific) sub-classes of an application domain like “Information Sharing Systems” Reusable models use generic objects classes that can be specialized via sub-classing into domain-specific object classes.

5. Developing a Rich Picture Start by developing Rich Picture(s) off-line using paper, post-its, colored pens, etc. Identify participating communities –Identify “background” sponsor or institution communities Bounded region for institution community created using PowerPoint shapes ( other choices also in Powerpoint Picture ClipArt shapes) –Identify “foreground” people and technical communities

6. Communities: Background Sponsors: Enable other enterprise communities –Example sub-class: an Enterprise Sponsor for a Corporate Portal The Dean’s Office at UCI GSM Institutions: Encapsulate/constrain other enterprise communities –Example sub-class: an Institution that situates an Enterprise Corporate Portal The UCI Graduate School of Management

7. Dean’s Office Example Background Communities displaying Sponsor (Dean’s Office -- ClipArt Icon) that is situated within the Institution (UCI GSM -- Reused GSM Icon.gif object plus WordArt text)

8. Reuse Notes: Example Background Communities displaying one Sponsor that is situated within one Institution. Two or more Institutions would each be represented as separate enclosed and colored regions. Two or more Sponsors would each be represented either encapsulated within their affiliated Institution, or with their own separate colored regions.

9. Communities: Foreground Authors (of Content) –Example sub-class:GSM Faculty Publishers (of Content created by Authors) –Example sub-class: GSM Administrative Staff End-users (of Content created by Authors) –Example sub-class: MBA Students Developers (of Content Representations) –Example sub-class: GSM IS Development Staff Mosaic of adjacent regions from PowerPoint ClipArt shapes

10. Dean’s Office Example displaying Sponsor (Dean’s Office) that is situated with the Institution (UCI GSM), and also Authors (Faculty), Publishers (Admin. Staff), End-Users (MBA Students), and Developers (IS Staff). People Icons are.gif objects found on theWeb or in PowerPoint ClipArt People. GSM staff Faculty GSM IS Dev. StaffMBA students

11. Reuse Notes: indicate the type of object specific to your project that should be included

12. Community Concerns For each community of people participants, indicate their primary concerns –Concerns may be goals, objectives, constraints, opportunities, constraints, business strategies, competitive strategies, or other non-functional requirements. –If participant communities have many concerns consider adding another Rich Picture or Text Slides (like this slide) to provide adequate space to capture these requirements.

13. Community Concerns The following classes of (reusable) concerns have been identified: –Sharing, Collaboration, Learning, Providing, Career Development, Competition, Legal Restrictions, Wealth Creation, Organizational, Fund-delegate-promote, Support/Help, Free Speech, Libel If your concern is not listed here let us know!

14. Reuse Example: displaying juxtaposed people communities and their virtual concerns indicated

15. Dean’s Office Example displaying juxtaposed people communities and their primary concerns indicated using PowerPoint AutoShape Callouts (“thought b”) with Text Box overlays. MBA students GSM staff Faculty GSM IS Dev. Staff Centralize IS support and content mgmt. Communicate, discuss, & learn Communicate & support faculty & students Communicate, discuss, teach, & research Provide high- quality course content Help faculty, students, staff with h/w, s/w & network Fund, delegate, & promote

16. Technical System Community Add software, hardware, network system components Add/identify any System Vendors or Application Service Providers that constrain your enterprise systems’ development, use, or evolution

17. Dean’s Office Example displaying people and technical system communities, system components, and major relations among technical system components MBA students GSM staff Faculty GSM IS Dev. Staff Do Email Access other Web content Do Forum or Chat/IRC Centralize IS support and content mgmt. Communicate, discuss, & learn Communicate & support faculty & students Communicate, discuss, teach, & research Manage Catalyst content Develop& Test Catalyst Provide high- quality course content Help faculty, students, staff with h/w, s/w & network Fund, delegate, & promote

18. Relations Add relations (activities/verbs) between community roles and system components –Try to incorporate names of objects being associated via each relation Example sub-class: (Faculty) Create course content (into Catalyst) –Basic types of relations include: Create, Publish, Search, Upload/Download, Interact, and Transact

19. Dean’s Office Example displaying people and technical system communities, system components, and major relations among technical system components MBA students GSM staff Faculty GSM IS Dev. Staff Do Email Access other Web content Do Forum or Chat/IRC Centralize IS support and content mgmt. Communicate, discuss, & learn Communicate & support faculty & students Communicate, discuss, teach, & research Manage Catalyst content Develop& Test Catalyst Provide high- quality course content Help faculty, students, staff with h/w, s/w & network Fund, delegate, & promote Create/edit & upload content Edit/upload content Download content Upload msgs or bio content Download content

20. Processes Processes are “flow” paths from people in one community through relations into another community Processes are generally domain-specific –Example sub-class: (Faculty) create, edit, and/or upload content (into Catalyst)

21. Rich Picture Taxonomic Object Hierarchy