Full document describing all aspects of the curriculum, release 2 (pdf)

More documents

Recommendations

Info

E-BUSINESS (SE-O-08)AIMS:Current approaches to systems design and development such as the rational unified process, SSADM,Multiview or web-based approaches take a very centralised approach. There is a central database modeldefined early on, and an emphasis on centrally designed business processes. The emphasis is on fulfillingthe processing demand of the business, not meeting the task-oriented needs of the client or user. Many e-commerce systems are targeted at external users. Hence there is a need for new approaches to systemdevelopment which take a client oriented view, are much more bottom-up than top-down and seek to elicitclient-views throughout the design process.This module explores the issues around such a transition from business focussed design to clientfocused design. The issues are developed through a study of usability engineering as a client-leddevelopment process. Usability engineering is gaining acceptance as a design approach which focuses onthe customer needs and the customer view in preference to the business process demand. It is seen as amore fruitful approach to the design of ecommerce systems which are customer facing.Students explore the frameworks for alternative design approaches and critically evaluate the fit ofusability engineering to the demands of design of e-commerce systems.The module further emphasises the importance of a research-based approach to systems designand explores current research in systems design, usability engineering and related cognitive sciences.LEARNING OUTCOMES:Upon successful completion of this module, the student will be able to:• critically appraise current approaches to systems design in comparison to the requirements of e-commerce and distributed system design;• apply the techniques of usability engineering, within the process framework of ISO13407 to thedevelopment of an e-commerce application;• critically evaluate approaches to measuring usability performance objectives and identify appropriateapproaches for given situations;• apply a range of supporting techniques derived from current literature to enhance the process of elicitingusability requirements;• identify and describe technical and research trend which may influence approaches to client-led design.SYLLABUS CONTENT:• Characteristics of e-business systems and consequences for design: requirement for bottom-upapproach, focus on screens and tasks.• Critical analysis of top-down approaches to system design and development: properties of top-downapproaches such as Rational Unified Process (RUP).• Issues in distributed design.• Characteristics of an alternative design approach.• Alternative approaches which do not rely on top-down analysis and a pre-defined data structure:exploration of other techniques for eliciting usability requirements and understanding tasks; jointapplication design; focus groups.• Service-oriented human-computer interaction (HCI): applying service concepts to systems design.• Approaches to evaluating web usability: survey of the literature.• Nature of culture: effect of culture on usability.• Use of scenarios in usability engineering: construction of scenarios in e-business.• Continued evaluation of implemented e-business applications: approaches to getting feedback.• System integration and usability engineering: systems integration across e-commerce systems.• Future issues concerning web-based applications.• Dealing with change: autonomic systems and service-oriented computing; principles of self-evolvingsystems; screen evolution and tailorability.• Comparing usability engineering and the RUP.• Alternative emergent environments: complexity; synchronicity and (e.g.) StarLogo.• Aspects of security in e-business applications.PREREQUISITES: NoneRECOMMENDED ASSESMENT: Coursework and unseen paperhttp://perun.im.ns.ac.yu/msc-se/ 30
BUSINESS PROCESS RE-ENGINEERING (SE-O-09)AIMS:To provide a greater understanding of effective solutions to change problems that need tocombine technological, organisational and people-orientated strategies by adopting a processbasedapproach to change management. To introduce the contingencies that affect managementand the most effective measures for dealing with them. To introduce strategic IS/IT planning andhow it must relate to business strategy. To demonstrate the use and validity of organisationaldevelopment models through current real-life case studies.LEARNING OUTCOMES:Upon successful completion of this module, the student will be able to:• understand the methods used to changing processes and the impact it has on companyculture, people and the integration with other information systems;• develop a strategic plan of IS/IT to support a business strategy aimed at providing anorganisation with competitive advantage;• manage information as a resource and have an understanding of systems developmentlifecycle;• implement, evaluate and analyse strategic business change processes;• understand the benefits the learning organisations strategy can bring to knowledge basedorganisations.SYLLABUS CONTENT:• Changing business processes: the importance of technology as a driver for organisationalchange.• Change and the manager: change and the human resource: the cultural web and the past:the cultural attributes of change.• The importance of communication and the resistance to change: building the culture forsuccessful strategy implementation; the influence IT will have on the internal appearance oforganisations in the future.• Business intelligence and the future of e-business.• The concept of the learning organisation and its influence on systems development:examples of organisations that have been through minor change programs and the lessonsthat have been learnt.PREREQUISITES: Business modellingRECOMMENDED ASSESMENT: Coursework and unseen paperhttp://perun.im.ns.ac.yu/msc-se/ 31
Page 1 and 2: Joint MSc curriculum in software en
Page 3 and 4: 2. Goals of the Joint MSc curriculu
Page 5 and 6: 4. Module listList of induction lay
Page 7 and 8: 6. Quality assurance and controlQua
Page 9 and 10: • current practitioners with adeq
Page 11 and 12: 7. Module Templateshttp://perun.im.
Page 13 and 14: PRINCIPLES OF PROGRAMMING, CODING A
Page 15 and 16: SYSTEM MODELLING AND DESIGN (SE-IN-
Page 17 and 18: REQUIREMENTS ENGINEERING (SE-C-02)A
Page 19 and 20: SOFTWARE TESTING (SE-C-04)AIMS:With
Page 21 and 22: INFORMATION SYSTEM DEVELOPMENT PROC
Page 23 and 24: SOFTWARE EVOLUTION (SE-O-01)AIMS:Wi
Page 25 and 26: FORMAL METHODS ENGINEERING (SE-O-03
Page 27 and 28: PRIVACY, ETHICS AND SOCIAL RESPONSI
Page 29: BUSINESS MODELLING (SE-O-07)AIMS:Th
Page 33 and 34: SOFTWARE ENGINEERING FOR DATABASE S
Page 35 and 36: PROJECTAIMS:This module is intended
Page 37 and 38: Moduleaka “course” or (in some
Page 39 and 40: The list of abbreviationsABASB2BB2C

Full document describing all aspects of the curriculum, release 2 (pdf)

Create successful ePaper yourself

Delete template?

Save as template?