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

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

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. UCI GSM
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. <Background-Institution-Icon> <Background-Sponsor-Icon>
<Background-Institution-Identifier>
<Background-Sponsor-Identifier>
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. UCI GSM Faculty GSM staff MBA students GSM IS Dev. Staff 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.

11. <Background-Institution-Icon> <Background-Sponsor-Icon>
<Background-Institution-Identifier>
<Background-Sponsor-Identifier>
<Community-Author-Icon>
<Community-Publisher-Icon>
<Community-Author-Identifier>
<Community-Publisher-Identifier>
<Community-EndUser-Icon>
<Community-Developer-Icon>
<Community-EndUser-Identifier>
<Community-Developer-Identifier>
Reuse Notes: <tags> 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. Provide high-quality course content
Fund, delegate, & promote
Provide high-quality course content
Communicate, discuss, teach, & research
UCI GSM
Dean’s Office
Communicate & support faculty & students
Faculty
GSM staff
Centralize IS support and content mgmt.
Communicate, discuss, & learn
Help faculty, students, staff with h/w, s/w & network
MBA students
GSM IS Dev. Staff
Example displaying juxtaposed people communities and their primary concerns indicated using PowerPoint AutoShape Callouts (“thought b”) with Text Box overlays.

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

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

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

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