Www.monash.edu.au IMS5401 Web-based Systems Development Topic 3: Development for the web 3(f) Implications of issues in web site design.

Slides:



Advertisements
Similar presentations
kareRCIserIsviFIsaRsþGnuvtþKMerag
Advertisements

Integrating the NASP Practice Model Into Presentations: Resource Slides Referencing the NASP Practice Model in professional development presentations helps.
Internal Audit Capability Model (IA-CM) for the Public Sector
4th VRE Programme meeting July 2006, Manchester User engagement: five key challenges and strategies for addressing them Chris Ramsden and Kerstin.
Principles of Information Technology
IMS5401 Web-based Systems Development Topic 3: Development for the web 3(d) User Interaction.
IMS5401 Web-based Systems Development Topic 3: Development for the web 3(g) Development in practice: organizational behaviour.
IMS5401 Web-based Systems Development Topic 3: Development for the web 3(c) Information Architecture.
IMS5401 Web-based Systems Development Topic 3: Development for the web 3(b) Content design and layout.
Chapter Extension 16 Agile Development.
Systems Development Environment
Chapter 1 The Systems Development Environment
1 The Database Application Development Process The Database Application Development Process.
CIS 100a TEKnology – High Tech Exploration Introduction to High Tech.
IMS5401 Web-based Systems Development Topic 3: Development for the web (a) Overview of web development issues.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
1.1 Introduction: concepts and overview of systems development IMS Information Systems Development Practices.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Software Architecture in Practice
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Introduction to Systems Analysis and Design
About Waterloo website Project report June Outline Overview of process Project deliverables Lessons learned.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
The Many Contexts of Software Architecture
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Chapter 1 The Systems Development Environment
WORKING EFFECTIVELY IN AN INFORMATION TECHNOLOGY ENVIRONMENT
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Dr Lisa Wise 9/08/2002 The Evolution and Devolution of the Webmaster Role Dr Lisa Wise.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Chapter 23 Project Development Team © 2013 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Introduction to Systems Analysis and Design
Approaches to Systems Development
SYSTEM ANALYSIS.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
The Systems Development Environment Systems Analysis and Design II.
Software Development Life Cycle (SDLC)
Unit 8: Implementation, Part II Seminar Wednesday pm ET.
Building an E-commerce Web Site
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Presented for discussion with Implementation SIG Heather Grain.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Information Systems Development
MBI 630: Systems Analysis and Design
What is Design?.
Information Technology (IT)
Introduction To System Analysis and Design PART 2
CIS 210 Systems Analysis and Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Student Collaboration
Chapter 1 The Systems Development Environment
Presentation transcript:

IMS5401 Web-based Systems Development Topic 3: Development for the web 3(f) Implications of issues in web site design

2 Agenda 1.The context for development 2.Responsibilities of the developer 3.Web development teams and processes

The context for development Development as an abstract topic can only be addressed in the broadest of terms (hence the vagueness of some of what we have discussed as design guidelines/rules) ALL development aims to achieve certain objectives – whatever works best IS best, no matter what design rules/guidelines may say Therefore we may commodify design principles, but we cannot commodify design

4 The context for development (1) Web Application (purposes) Design features User(s)

5 The context for development (2) Design Process Design standards Technology constraints Design aesthetics Functional requirements Design Outcomes

Responsibilities of the developer To know what is important (and why) for the site being developed To be able to identify and call upon the appropriate design skills as required To identify the compromises needed and direct the design accordingly To liaise with technical staff responsible for implementation

7 What matters (and how much)? What is the relative importance of: Information content design? Page structure and layout? Architecture and navigation? Content maintenance and management? How do these needs reinforce or conflict with one another? What compromises are needed and how should they be implemented in the design?

8 Who should do it (and why)? To what standards (ie quality) must each aspect of site design be developed? What are the key skills required in getting the design to the appropriate quality? What specialists need to be employed to provide these skills? Graphic designers Photographers Content developers Information architects etc

9 Where do IS/IT professionals fit in (and how)? What sorts of skills can IS/IT professionals provide in the development process? How relevant are they to the needs of the site? How do they establish their credentials for providing relevant specialist skills? What do they need to do to learn (or improve) their skills to suit different types of sites?

10 An analogy with the past Computer systems development before IS professionals The evolving role of the IS professional Systems analyst? Business analyst? Technical analyst? Application specialist? Are we about to see this pattern repeated (or is it all just a continuation of the same pattern)?

Web site development teams and processes ‘Traditional’ IS development team Business analysts Systems analysts Programmers Specialists (database, application software,testing, etc) Web development team? …?? Note: Lack of certainty over roles Diversity of specialist backgrounds Lack of established norms for collaboration

12 Development processes ‘Traditional’ IS processes Waterfall SDLC Prototyping/RAD/JAD/iterative/etc Structured methodologies Web development processes …?? Note: Lack of clearly-defined processes Diversity of process models Lack of established norms/structures for development process

13 Developing development teams and processes Prevalence of ad hoc approaches Problems and increasing need for professionalism The development of norms for practice The current state-of-play. Refer: Taylor et al Barry & Lang Lee et al

14 The future Commodification of applications Identification and commodification of ‘best practice’ processes and techniques Evolution of specialised skills Commodification of technologies; impact on skill requirements Organizational recognition of needs Development of specialised development processes