1 / 16

Draft plans for course

Draft plans for course. General notes. Would be good to identify core messages for each topic How do you go through the experience of going through a complete development cycle with all its complexities Write a short case that can be a foundation for example in multiple lectures

jonah-mack
Download Presentation

Draft plans for course

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Draft plans for course

  2. General notes • Would be good to identify core messages for each topic • How do you go through the experience of going through a complete development cycle with all its complexities • Write a short case that can be a foundation for example in multiple lectures • For each topic – examples/anecdotes/successes/failures • Could be more than one aspect • E.g. software development • How have things changed over time • E.g., brand manager, procurement • Bring in new technologies • Company persona (like personas used in interface design) • Role playing • End-user • CIO –technology • CEO – management • Sales, • Engineering/Manufacturing - building • Discuss what happens with changes in company – go one level deeper • E.g. move from direct sales to hybrid channel sales model • What process would you go through to design the system? • Software development lifecycle as structuring element for sessions • Needfinding - Idea that software can solve a problem • Opportunity • Observation, interview, etc. • Understand • Practices / business process • Linkages to existing technologies, organizations,… • Design • Product definition [Point of view] • Interaction structure /interface • Technologies • Build • Software construction models (e.g., open source, agile programming, …) • Project organization and management • Deploy/Test • Support • Distribution • Help • Localization • Maintenance • Enhance • Testing • Feedback modes • Re-design

  3. Introduction [Hasso with others] • The problem domain • Exercise / role play • Emergency Management – status and cases • The technology opportunity • New ways of organizing information systems • The need for innovation / design thinking • Course details and logistics • Teaching team introductions

  4. Enterprise Applications • History and current state • Hasso’s story • Decentralization of IT organization • Composite Applications – going forward • Design analysis exercise • Embedded systems [physical platforms] • Brainstorm on uses of new tech (e.g., mobile) • Explore 2 or 3 different processes, companies • Horizontal vs. vertical

  5. Business processes • How you get and codify the information • Basic structure • Theoretical structure / workflow • Speech Acts (Winograd, Flores) -> • Both formal and informal processes • Lucy Suchman (why people work around formal processes) • How can enterprise software support this • Different representations / process maps • Differentiating factors • Industry-specific • Law/country • Company-specific • Modeling tools • Solution maps • Solution management/product development • Holistic understanding • Historical enterprise software support for this • Fragmented support within business units • Where this can go • More cross organizational and cross company processes

  6. Basic information systems (DB, GIS,Asset management…) Moving up the stack – DB, Warehouse, Analytics System, solutions (e.g., CRM) • Introduce the technology stack • Technology trends (e.g., diskless DB, intelligent routers) • Highlight the ones that might be relevant to the project • Invite Project Sponsor(s) to discuss their IT environment (case study) • Make connections to other organizations that might provide information or support

  7. Architectures [story of SAP] • Mainframe • Client-server • Web Services • Hardware/software stack and how it is evolving

  8. Software development • Software engineering, open source,.. • Real world complexities • Distribution and support models • Software leadership at different maturity stages • Processes • Specs, testing • Ad hoc vs. what is necessary in an enterprise setting • Design, vs redesign

  9. New interface technologies • Rich Web interfaces • Mobile interfaces • Programming models and tools • Info aggregation

  10. Business models

  11. Practical Design Platform

  12. Domain topics • Disaster management • Response • Logistics [supply chain] • Designing for chaos / failure • Uses of existing collaboration tools • Organization structure [players, roles, turf issues,…]

  13. Design Process Topics • Reducing scope for effective design • Developing a POV • Requirements Gathering / Needfinding • Prototyping methods • Artifacts as communication of design intent • HCI methods (levels of prototyping, user observation, etc.) • Innovation methods • Change methods (dealing with structure and culture) • Team process, project management • Storytelling / presentation • Communicating with users/clients • Visioning • Storyboarding, scenarios, etc. • Interim presentations and feedback • To class • To reviewers • Entrepreneurship – making things happen • Final presentations

  14. Potential Guests • Steve Jobs – • the role of design in product success • Shai Agassi – • software leadership in a global context • Bruce Nussbaum • IDEO person (Brown, Kelley,…) • Google (Mayer,…)

  15. Dates • W 4/4 - Intro • M 4/9 – Enterprise Applications • W 4/11 – Disaster Management • M 4/16 – Business processes • W 4/18 – Information systems / (e.g. deep dive into areas relevant to project) • M 4/23 – Scenarios/Focus • W 4/25 - Architectures • M 4/30 – Software development [CHI] • W 5/2 - Interface Technologies [CHI] • M 5/7 – Design proposals • W 5/9 – Project-related (To be scheduled) • M 5/14 – Project-related (To be scheduled) • W 5/16 – Project-related (To be scheduled) • M 5 21 – Project-related (To be scheduled) • W 5/23 – Project-related (To be scheduled) • M 5/28 – MEMORIAL DAY • W 5/30 - Rehearsals • M 6/4 – Presentations • W 6/6 – Recap, debrief, evaluation – Business models,

  16. Our tasks • Design scenario/role play for introduction • Find someone to give initial problem domain presentation

More Related