Syllabus – Weekly schedule. Project Deliverable 1 Required elements –Product statement –One use case –Redesign justification Format-specific additional.

Slides:



Advertisements
Similar presentations
Teaming Up. Teams A group of people working together to accomplish a task.
Advertisements

Formative assessment of the Engineering Design process
SAMPLE THE MANAGER’S COMMUNICATION HANDBOOK A Practical Guide to Build Understanding, Support, and Acceptance WELCOME!
Teamwork. Can be in person or virtually. Organizing a Team Project Appoint a group manager Define a clear and definite goal Identify the type of document.
Internet Management Consultants and Solution Providers Outstanding CMS Projects Lessons from the Front Line.
Writing for CIEG 461 Prof. Stephen A. Bernhardt Dept of English Kirkpatrick Chair University of Delaware September 23, 2002.
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
Term Project Teams of ~3 students Pick a system (discuss choice with me)  Want simple functionality, security issues, whole system (e. g., client and.
Term Project Pick a system (discuss choice with me)  Want simple functionality, security issues, whole system (e. g., client and server side) Submit a.
Oct. 2, 2003CS WPI1 CS 509 Design of Software Systems Lecture #5 Thursday, Oct. 2, 2003.
Syllabus – Weekly schedule. Project Sharing – Exercise 3 Team level discussion Teams share results of contextual inquiry Note: Jennifer & Anita circulate,
socio-organizational issues and stakeholder requirements
Planning for a Web site Project ITS Web Services - Wendy Dascoli November 1, 2007.
Requirements Analysis
Deployment General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification ImplementationDeployment Evaluation.
Instant Design Challenge
Instant Design Challenge
Instant Design Challenge Using the Design Process and Engineering Notebook.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Commonwealth of Massachusetts Statewide Strategic IT Consolidation (ITC) Initiative ANF IT Consolidation Website Publishing / IA Working Group Kickoff.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
NIH ACSI Meeting Oct. 4, Evaluation of NIH ACSI Website Project: Highlights of the Final Report Jennifer Crafts, Ph.D. Westat.
Chapter 10 Information Systems Analysis and Design
Project 3 Cookie Cutters Kevin Huynh Sean Tsusaki Jordaniel Wolk.
Design Step 2: Research the Problem. Knowledge Base Does a similar product already exist? Are there regulatory and standards issues? –intellectual property.
Welcome TC518: User-centered Design Section A (Day): Tues/Thurs, 1:30-3:20 Instructor: Dr. Jennifer Turns, Assistant Professor Phone:
Applied Software Project Management
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Expert System Job Offer Evaluation Software May Abstract The project’s focus is to decide what criteria should be used to determine which job offer.
Information Architecture & Design Week 3 Schedule -Syllabus Updates -Group Project Deliverables -IA Methodologies -Research Topic Presentations.
Request For Qualifications (RFQ) Missouri Local Programs How to Complete the RFQ & Get it Advertised.
PRJ566 Project Planning & Management Software Architecture.
Project Sharing  Team discussions (15 minutes) –Share results of your work on the Project Scope Proposal –Discuss your choice of methods and results –Prepare.
Administrivia  Final Exam –Due Date – Thursday, March 17 –Q & A  Deliverable 2 –Q & A.
Mid-Term Evaluation  Course and Instructor evaluation  Jennie Dorman.
Z556 Systems Analysis & Design Session 10 ILS Z556 1.
1  [company] Inc. [year] Girl Scouts of the USA Secure Site Project Kickoff [date]
TEAMING UP. TEAM A group of people working together to accomplish a task.
1 Overview of Class #2 Today’s goals Comments on syllabus and assignments Mathematics education in the U.S. and becoming a teacher of mathematics Introduction.
Final Year Project 1 (FYP 1) CHAPTER 1 : INTRODUCTION
Interacting with consumer Software Engineering. So far… What is Software Engineering? Different software process models waterfall, incremental, spiral.
User Interfaces 4 BTECH: IT WIKI PAGE:
Problem-Solving Meeting Foundations
Getting Ready for Smarter Balanced Jan Martin Assessment Director, SD DOE Feb. 7, 2014.
Jigsaw Activity. * The room has 3 sections: * Elementary * Middle * High * Please move to the section for your grade level and take your electronic device(s)
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
SLIDE 1 Title of the project Member 1 ( Reg. No) Member 2 ( Reg. No) Member 3 ( Reg. No) Place : Duration : Half sem/ Full sem Guide Internal/External.
The Software Engineering Process Discussion Slides.
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
Engineering Design Building the Team. Elements of Cohesive Teams Trust Willingness to engage in conflict Commitment Accountability Attention to results.
Stage 1 Integrated learning Coffee Shop. LEARNING REQUIREMENTS The learning requirements summarise the knowledge, skills, and understanding that students.
Information Technology Project Management – Fourth Edition By Jack T. Marchewka Northern Illinois University Power Point Slides by Gerald DeHondt Grand.
Response to an Emergency Training for 211 Staff in Ontario Updated September
Project Planning: Scope and the Work Breakdown Structure
Requirements Determination
“It was years after we had taken usability to guide us that it was said by some other companies that they could not afford to employ a usability specialist.
Information Technology Project Management – Fourth Edition
Administrivia Final Exam Deliverable 3 Feedback on Heuristic Eval
Technical Communication: Foundations
Required Course Project
Required Course Project
Instant Design Challenge
Instant Design Challenge
Formative assessment of the Engineering Design process
Final Exam - Questions A critical look at the design experience (300 words): Imagine you had a chance to start the design project over, knowing what you.
Instant Design Challenge
A Fundamental Challenge
Purpose Statement Template
SDLC (Software Development Life Cycle) Role Play
Presentation transcript:

Syllabus – Weekly schedule

Project Deliverable 1 Required elements –Product statement –One use case –Redesign justification Format-specific additional requirements –Document: 4 page max, submit document –Presentation: 5 minute max, submit slides/handouts Grading criteria: All deliverables should –Embody professional-level communication –Fulfill core requirements (see above) –Exemplify user-centric language –Address additional demands of the communication event

Project Sharing – Exercise 4 Team level discussion Teams share results of user and task analyses Note: Jennifer & Anita circulate, distribute exercises, and answer questions Class-level discussion Debriefing, Teams share one insight that think may benefit other teams

Discussion of Readings Focus How do designers use knowledge of users, tasks, and contexts to understand observed usability problems? How does one set priorities for a UCD redesign? How does one constrain redesign? How do designers communicate the requirements that guide their redesign, and serve as the basis of an agreement about scope? How do designers manage the scope of a project? What are the challenges associated with managing scope (e.g., scope creep)? Process Divide into two rooms Position Paper discussants –Sedgwick, Main room –Tassielli, Main room –Stutzman, Secondary room –Jafarzadeh, Secondary room Everyone else: First digit of social security number… –0 through 4, Secondary room –5 through 9, Main room

Proposing rqmts, Setting scope Goal of proposing…

Your Job… Group 1 – Reverse engineer a product statement –Based on the information communicated in the main page, create a product statement that could have guided the design of the Labor and Industries website. Group 2 – Reverse engineer a use case –Based on the information communicated in the main page, develop a use case capturing the interaction that is offered when someone enters this online organization…(what does the page suggest that users want to know or do and how does the system respond).

Proposing rqmts, Setting scope …

Looking across solutions –What differences exist? What do differences mean? Looking across solutions and experience –What is required in order to create the product statement? Use cases? –What difficulties did you experience (or do you anticipate) in constructing the product statement? Use case?