Developing a Rich Picture for an Information Sharing

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/F 271 Spring 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.

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

Making Reusable Rich Pictures • Domain models should be reusable • Rich Pictures are a kind of (visual requirements) domain model • Applications sub-domains use (domainspecific) 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 Power. Point shapes (other choices also in Powerpoint Picture Clip. Art 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 -- Clip. Art Icon) that is situated within the Institution (UCI GSM -- Reused GSM Icon. gif object plus Word. Art text)

<Background-Institution-Icon> <Background-Institution-Identifier> <Background-Sponsor-Icon> <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.

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 Power. Point Clip. Art shapes

Dean’s Office GSM staff MBA students Faculty GSM IS Dev. Staff 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 the. Web or in Power. Point Clip. Art People.

<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-End. User-Icon> <Community-End. User-Identifier> <Community-Developer-Icon> <Community-Developer-Identifier> Reuse Notes: <tags> indicate the type of object specific to your project that should be included

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

Fund, delegate, & promote Communicate & support faculty & students Provide highquality course content Dean’s Office GSM staff Faculty Communicate, discuss, teach, & research 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 Power. Point Auto. Shape Callouts (“thought b”) with Text Box overlays.

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

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

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

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

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)

Rich Picture Taxonomic Object Hierarchy