Presentation is loading. Please wait.

Presentation is loading. Please wait.

MyUMich Service Architecture Janus Project Brown Bag 1 June 2000.

Similar presentations


Presentation on theme: "MyUMich Service Architecture Janus Project Brown Bag 1 June 2000."— Presentation transcript:

1 myUMich Service Architecture Janus Project Brown Bag 1 June 2000

2 26 May 2000 myUMich Service Architecture 2 Overview Introductions Institutional messages & business goals – Linda Place User requirements study – Judy Dean Portal benchmark study – John Cady Service/information architecture – John Cady & BJ Streu

3 26 May 2000 myUMich Service Architecture 3 Institutional Messages Suspension of Belief “Publicness” Faculty Autonomy Transparent Administration Making Our History Visible

4 26 May 2000 myUMich Service Architecture 4 Principle of Suspension of Belief Creation of an environment that – Enables and supports intellectual and artistic creativity and exploration of alternative world views – Encourages risking identity loss and discourages rigid perspectives – Encourages exploration of complexity – Fosters compromise and accommodation across divergent viewpoints

5 26 May 2000 myUMich Service Architecture 5 Principle of “Publicness” Local community minded Commitment to eliminating socio-economic barriers to education Enabling an education that interacts with as many aspects of American life as possible

6 26 May 2000 myUMich Service Architecture 6 Principle of Faculty Autonomy Decentralization of decision making with respect to teaching and research Enable taking of personal responsibility Encourage personal engagement with work

7 26 May 2000 myUMich Service Architecture 7 Principle of Transparent Admin Keep bureaucracy invisible to faculty and students Enable creativity and exploration to happen without being obviously present Do not focus on production of goods and services but on enabling of academic processes

8 26 May 2000 myUMich Service Architecture 8 Principle of Visible History Take community member accomplishments seriously by keeping them visible

9 26 May 2000 myUMich Service Architecture 9 Business Goals Improved recruitment and retention Brand enhancement (national recognition) Development of lifelong relationships

10 26 May 2000 myUMich Service Architecture 10 First Target Audience Undergraduate students Potential students

11 26 May 2000 myUMich Service Architecture 11 User Requirements Overview Role and task modeling Student interactions and user testing “Best practices” research and benchmarking

12 26 May 2000 myUMich Service Architecture 12 Portal Benchmark Study Goal: see how to best handle portal structure Studied: – Top 10 Internet portals (as ranked by Traffick.com) – Two school-specific portals with guest views – Looked at college student portals; none worth study Focus: organization, navigation, and labeling

13 26 May 2000 myUMich Service Architecture 13 Positive Findings Found some strong examples to emulate Solid confirmation of the utility of the “containers” approach as the primary model of organization

14 26 May 2000 myUMich Service Architecture 14

15 26 May 2000 myUMich Service Architecture 15 Positive Findings, part 2 Also, great insights into customization options: – Add/remove modules – Customize within a module – Move content within columns – Etc. And into creating the customization process: – Strategies for easily moving content up or down in a column – How to give user feedback about changes

16 26 May 2000 myUMich Service Architecture 16 Pitfalls However, we also discovered some pitfalls Some sites supplemented container navigation with lists of menu items, navigation bars, etc. This caused a variety of problems: Pitfall #1:menu sprawl

17 26 May 2000 myUMich Service Architecture 17

18 26 May 2000 myUMich Service Architecture 18

19 26 May 2000 myUMich Service Architecture 19 Pitfalls #2: multiple navigation bars

20 26 May 2000 myUMich Service Architecture 20

21 26 May 2000 myUMich Service Architecture 21 Pitfalls (continued) #3: several levels of menus

22 26 May 2000 myUMich Service Architecture 22

23 26 May 2000 myUMich Service Architecture 23 Pitfalls #4: partial inclusion of options

24 26 May 2000 myUMich Service Architecture 24

25 26 May 2000 myUMich Service Architecture 25 Pitfalls #5: Duplication or near-duplication of links

26 26 May 2000 myUMich Service Architecture 26

27 26 May 2000 myUMich Service Architecture 27 Benchmark Summary Some good ideas Some lessons A state-of-the-art architecture is within our reach

28 26 May 2000 myUMich Service Architecture 28 Proposed Organizational Structure In a static Web site: design architecture + content simultaneously In interactive, fluid portal environment: design shell first, then architectures of services

29 26 May 2000 myUMich Service Architecture 29 Design Considerations Satisfy those fans of one all-in-one page and those who prefer several simpler pages Avoid the menu pitfalls we found in other portals Build a system that can accommodate services we haven't even thought of yet Keep things simple and efficient for the user How to:

30 26 May 2000 myUMich Service Architecture 30 An Answer Aha! Yahoo! Not a graphically pleasing site, but a very functional one Yahoo! architecture – Begin with single all-in-one page – Can add pages, choose content, and name them

31 26 May 2000 myUMich Service Architecture 31

32 26 May 2000 myUMich Service Architecture 32 Advantages of Yahoo! Approach Gives user control over the way s/he defines “simple” Relieves us of need to categorize menu items Relieves us of potential menu item politics User presented with only as much complexity as needed

33 26 May 2000 myUMich Service Architecture 33 Using the Yahoo! Method This model gives us the greatest flexibility and modularity of all the systems we’ve seen It has been tested and is proving popular – Yahoo! is by far the portal leader (see handouts) Our architecture will be more sophisticated and flexible than either MyUW or MyUCLA (and the latter has been in use since 1997)

34 26 May 2000 myUMich Service Architecture 34 Other Structural Notes Keep navigation to a minimum and prominent Build an intuitive and easy customization process Educate users re: customization benefits/ease Take care in designing default page; most users not expected to customize, at least at first

35 The Architecture

36 26 May 2000 myUMich Service Architecture 36

37 26 May 2000 myUMich Service Architecture 37

38 26 May 2000 myUMich Service Architecture 38

39 26 May 2000 myUMich Service Architecture 39

40 26 May 2000 myUMich Service Architecture 40

41 26 May 2000 myUMich Service Architecture 41

42 26 May 2000 myUMich Service Architecture 42

43 26 May 2000 myUMich Service Architecture 43

44 26 May 2000 myUMich Service Architecture 44

45 26 May 2000 myUMich Service Architecture 45

46 26 May 2000 myUMich Service Architecture 46

47 Contributing to Student Input Contact Linda Place lmp@umich.edu 615-5820


Download ppt "MyUMich Service Architecture Janus Project Brown Bag 1 June 2000."

Similar presentations


Ads by Google