Developing a Rich Picture for an Information Sharing System

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/F271Spring 2003

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.

MBA students

GSM staffFaculty

GSM IS Dev. Staff

Catalyst-Web server

Email

GSM course contentForum &

Chat/IRCCentralize 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

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.

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

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

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)

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.

<Background-Institution-Icon><Background-Institution-Identifier>

<Background-Sponsor-Icon><Background-Sponsor-Identifier>

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

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

Reuse Notes: <tags> indicate the type of object specific to your project that should be included

<Background-Institution-Icon><Background-Institution-Identifier>

<Background-Sponsor-Icon><Background-Sponsor-Identifier>

<Community-Publisher-Icon><Community-Publisher-Identifier>

<Community-Author-Icon><Community-Author-Identifier>

<Community-EndUser-Icon><Community-EndUser-Identifier>

<Community-Developer-Icon><Community-Developer-Identifier>

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.

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!

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

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 staffFaculty

GSM IS Dev. Staff

Centralize IS support and content mgmt.







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

Dean’s Office

Example displaying people and technical system communities, system components, and major relations among technical system components

MBA students

GSM staffFaculty

GSM IS Dev. Staff

Do Email

Access other Web content

Do Forum or Chat/IRC





Manage Catalyst content

Develop& Test Catalyst




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

Dean’s Office

Example displaying people and technical system communities, system components, and major relations among technical system components

MBA students

GSM staffFaculty

GSM IS Dev. Staff

Do Email

Access other Web content

Do Forum or Chat/IRC





Manage Catalyst content

Develop& Test Catalyst




Create/edit & upload content

Edit/upload contentDownload

content

Upload msgs or bio content

Download content

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)

R ich P ic tu re s O b je ct H ie ra rchy

A u th o rsP u b lish e rsE n d -U se rsD e ve lo p e rs

P e o p le C om m un it ies

V e nd o rsA p p lica tio n S e rv ice P ro v id e rs (A S P s)

C lie n ts (U se r/E n d -U se r)G a te w a y/W e b S e rve rs

N e tw o rk F ile S e rverD a ta B a se (D B M S ) S e rver

B a ck -E n d S e rve rs

D e ve lo pm e nt a nd T es tin g P la tfo rmO th e r U se r A p p lica tio ns

S ys tem C om p on e n ts

T e ch n ica l S ys te m C o m m u n ity

P a rtic ipa tin g C o m m u n it ies

R e la tio n s (a c tiv it ie s)W o rkflo w (p a ths o f a c tiv ity a nd co n te n t f lo w )C o nten t In pu t/O u tp u tP e o p le C o m m u n ity R o les

P ro ce sses

F u n ctio n a l R e qu ire m e n ts

S p o nso rsIn s titu t io ns

B a ckg ro u nd C om m un ities

C o m m un ity C on ce rns

N o n -F u n ctio n a l R e qu ire m e n ts

R ich P ic tu re

Rich Picture Taxonomic Object Hierarchy

Documents

Developing a Rich Picture for an Information Sharing System