Uploaded on


  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. School of Business Informatics and Software Engineering MSc Software Engineering PROGRAMME DOCUMENT VERSION 1.0 MSE v1.0 April 2006 University of Technology, Mauritius La Tour Koenig, Pointe aux Sables, Mauritius Tel: (230) 234 7624 Fax: (230) 234 1747 Email: sobise@utm.intnet.mu website: www.utm.ac.mu
  • 2. MSc SOFTWARE ENGINEERING v1.0 MSc SOFTWARE ENGINEERING 1 Programme Information The MSc in Software Engineering is primarily intended for graduates of computing subjects who want an in-depth focused in the software engineering discipline. This programme is a basis for further study, research and acquiring skills and knowledge in areas like design patterns, intelligent agent technologies and other specialist fields. The course comprises of a six months industrial project where the student will apply acquired knowledge and skills to solve real-life problem. This course also helps the students to be conversant with all the software challenges that exist and shows them the right path to delivering code to the highest levels of quality, reliability and maintainability at the lowest cost. 2 Programme Aims The MSc Software Engineering programme prepares students to act project leaders. Furthermore, the students will be ready to join any public or private institution whether national or international where software development and maintenance are the main key activities. This programme is also an important step towards research. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 2 of 19
  • 3. MSc SOFTWARE ENGINEERING v1.0 PART I Regulations 1. Entry Requirements The Regulations of the University of Technology, Mauritius require an applicant for this Masters degree to: (a) (i) Be a recognised graduate and who has attained a standard at least equivalent to that of a Lower Second Honours Degree in a subject related to that of the proposed programme of study accepted by the Academic Council; (ii) Have passed an examination including a professional qualification in such a subject at a standard equivalent to Level 3 or equivalent to an Honours Degree; (iii) Have been deemed qualified for admission as candidate by the Academic Council on the recommendation of the School Board; (iv) Be a candidate for Postgraduate Diploma, is permitted by the Academic Council to transfer to candidate for a Master’s Degree in the same subject (b) Applicants should have a computing background with programming and system design as strengths. Admission decisions will be made by the School of Business Informatics and Software Engineering on a case by case basis. The primary criteria for acceptance of an applicant are: his or her anticipated successful completion of the programme. The assessment of an applicant’s likelihood of success can be carried out in a variety of ways e.g. entrance examination, interviews, etc. At the time of application, the student is expected to demonstrate his or her background in the field. 2. Programme Duration Full-Time: 1 year Part-Time: 2 years 3. Semester 15 weeks (excluding exam period) 4. Academic Tutoring Weekly 1 hour session between a maximum of two students and one lecturer. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 3 of 19
  • 4. MSc SOFTWARE ENGINEERING v1.0 5. Project on an industrial placement The students will undergo a six months project in the industry. This project will be jointly supervised by an internal academic staff and an external representative from the industry local or overseas through UTM linkages. 6. Academic Resources Selected modules will be delivered by foreign experts and professionals from the local industry. 7. Student Progress and Assessment For the award of the Masters Degree, all modules taken must be passed overall with passes in the examinations, coursework and other forms of assessment. All modules will be assessed as follows: Written examinations carrying 60 % of total marks and continuous assessment carrying 40 % of total marks. Continuous assessment can be based on seminars and/or assignments or class tests. 8. Grading Grade Marks x[%] A X ≥ 70 A 65 ≤ x < 70 B 60 ≤ x < 65 B 55 ≤ x < 60 C 50 ≤ x < 55 C 45 ≤ x < 50 D 40 ≤ x < 45 F X < 40 A–D Pass F Fail _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 4 of 19
  • 5. MSc SOFTWARE ENGINEERING v1.0 9. DEGREE AWARD CLASSIFICATION Overall weighted mark y (%) Classification > 70 MSc with Distinction 40 < y < 70 MSc Minimum Credits Required for Award of: Master’s Degree: 39 Postgraduate Diploma: 24 Postgraduate Certificate: 15 Breakdown as follows: (i) MSc Software Engineering Core modules: 12 credits +Electives: 12 credits +Industrial Project: 15 credits Candidates who obtain a mark of 70% and above will be awarded an MSc with Distinction. (ii) Postgraduate Diploma Software Engineering Core modules: 12 credits + Electives: 12 credits (iii) Postgraduate Certificate Software Engineering Core modules: 9 credits + Electives: 6 credits _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 5 of 19
  • 6. MSc SOFTWARE ENGINEERING v1.0 PART II 1. PROGRAMME STRUCTURE MSc SOFTWARE ENGINEERING – Full Time Version 1.0 (Programme Director: J. Narsoo) Semester 1 Semester 2 Code Module L+P Code Module L+P OSS5101 Unix Programming 2+2 SEM5201 Software Quality 3+0 Assurance SDT5101 Design Patterns 2+2 + 2 electives SCG5120 Distributed Computing 2+2 PRJ5204 Industrial Project + 2 electives MSc Software Engineering – Part Time Version 1.0 (Programme Director: J. Narsoo) Semester 1 Semester 2 Code Module L+P Code Module L+P OSS501 Unix 2+2 SEM5201 Software Quality 3+0 Programming Assurance SDT5101 Design 2+2 + 1 elective Patterns SCG5120 Distributed 2+2 Computing Semester 3 Semester 4 Code Module L+P Code Module L+P + 2 electives + 1 elective Industrial Project Note: • Registered students are required to submit a list of the electives they wish to take well before the programme starts. • The University reserves the right not to offer a given elective if the critical number of students is not attained and/or for reasons of resource constraints. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 6 of 19
  • 7. MSc SOFTWARE ENGINEERING v1.0 2. LIST OF MODULES CORE MODULES Code Module Hrs/Wk Credits OSS5101 Unix Programming 2L+2P 3 DST5101 Design Patterns 2L+2P 3 SCG5120 Distributed Computing 2L+2P 3 SEM5201 Software Quality Assurance 3L+0P 3 ELECTIVE MODULES BLOCK A Code Module Hrs/Wk Credits SEM5101 Software Project Management 3L+0P 3 SEM5102 Software Metrics 3L+0P 3 DBT5101 System Integration 2L+2P 3 HCA5105 Embedded Systems 2L+2P 3 ISM5101 Information Technology Economics 3L+0P 3 MCT5101 Mobile and Pervasive Computing 2L+2P 3 WAT5101 Service Oriented Architecture 2L+2P 3 Note : Sofware Project Management and Software Metrics are compulsory electives for those students not having covered these modules in their undergraduate programme. BLOCK B Code Module Hrs/Wk Credits PRG5106 Agent Technology 2L+2P 3 SDT5203 Agile Programming Techniques 2L+2P 3 ISM5102 Entrepreneurship 3L+0P 3 OUT5101 IT Sourcing 3L+0P 3 ISM5103 Strategic Information System 3L+0P 3 ISM5104 Global IT Management 3L+0P 3 The above list is not a final elective list, other related electives can be considered. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 7 of 19
  • 8. MSc SOFTWARE ENGINEERING v1.0 3. MODULE SPECIFICATIONS CORE MODULES Module Module Title Aims/ Learning Outcomes Module Outline Code OSS5101 Unix Aims • A Tour of UNIX and Linux. Versions of Programming UNIX. The aims of this module are • File I/O: File I/O, File Descriptors and Open to give a hands-on contact File Descriptions, Symbols for File on: Permission Bits, open and creat System • Using standard UNIX Calls, umask System Call, unlink System system call API's Call, Creating Temporary Files, Disk • Concurrent Special Files and File Systems, Hard and programming with Symbolic Links, Pathnames, Accessing and processes and threads Displaying File Metadata, Directories, • Network programming, Changing an I-Node including the client- • Terminal I/O: Reading from a Terminal, server paradigm Sessions and Process Groups • Writing shell scripts and (Jobs),Setting Terminal Attributes, portable application Terminal-Identification System Calls programs • Processes and Threads: exec System Calls, Implementing a Shell, fork System Learning Outcomes Call, exit System Calls and Process On successful completion of Termination, User and Group Ids, Setting this module, students User and Group Ids, Process Ids, chroot should be able to: System Call, Priority • Configure and manage • Interprocess Communication: Pipes, dup, a UNIX system Unidirectional Pipes and Bidirectional • Program under the Pipes, FIFOs, or Named Pipes, Simple UNIX environment Messaging Interface (SMI), System V IPC • Acquire programming (Interprocess Communication), System V experience in the Message Queues, Semaphores, File following: concurrent Locking programming with • Networking and Sockets: Socket Basics, processes and threads, Socket Addresses, Socket Options, Simple network programming Socket Interface (SSI), Socket and shell scripting. Implementation of SMI, Connectionless Sockets • Signals and Timers: Signal Basics, Deprecated Signal System Calls, Realtime Signals Extension (RTS). Global Jumps, Clocks and Timers. • Shell programming _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 8 of 19
  • 9. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code DST5101 Design Aims Patterns • Review of software development processes The module aims to look • Object Oriented modelling Using UML into software development • Introduction to Design Patterns processes including an • Examples of design patterns:Singleton, object-oriented approach Façade, Factory, Adapter, Bridge, which can be used to deal Composite, Decorator, Flyweight, Proxy, with issues which arise in Builder, Prototype, Interpreter, Template, real-world software. The Chain of responsibility, Command, Iterator, main overall themes are Mediator, Memento, Observer, State, reusability and coping with Strategy, Visitor change. The aim of this module is also to develop the ability to apply and justify the use of patterns in software engineering. Learning Outcomes On successful completion of this module, students should be able to: • Analyse the importance of patterns in software development. • Represent Patterns using UML • Design and develop software using existing patterns. SCG5120 Distributed Aims • Introduction to Distributed Systems Computing • Setting up your Development Environment The aims of this module is • Developing Distributed Applications to examine the forces • Kernels, Process, and Threads shaping the evolution of • Interprocess communication (IPC) distributed architectures and • Client-Server Architecture to develop a conceptual • Concurrency Control model for understanding • Distributed Objects and Object-based and evaluating distributed Systems systems and its constituent components • Web Services • Distributed Security Learning Outcomes • Distributed File Systems On successful completion of • Distributed Databases this module, students • Transaction Management should be able to: • Set up a development environment • Design and implement software and web services in a distributed environment _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 9 of 19
  • 10. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code SEM5201 Software Aims • Quality : Differentiating between Quality Quality Assurance, Quality Control and Testing, Assurance The module approaches the importance of quality, the cost of quality, issue of quality assurance in two views of quality, Quality attributes, the software development Quality audits process at an advanced • Quality and the Organisation : Management level. This includes a commitment to quality, Organisational rigorous account of the structure, Placement within the strategies for software organization, Quality coordination, Setting testing and quality control. quality standards The module is focussed • Software Quality Assurance and CMMI: around the notion of Process and product quality assurance, software process quality assurance goals, Processes for improvement. each goal • Risk identification and management Learning Outcomes • Software Quality Management and ISO • On successful 9001: Management responsibility, Internal completion of this quality audits, Control quality records, module, students Document and data control, Training, should be able to: Corrective and Preventive actions • Understand how quality • Quality Tools: Tools for ideas and issues affect each information, numbers, presentation aspect of the software • Software Quality Assurance Plan (SQAP): development life-cycle Relationship of SQAP to SQA program, • Know appropriate SQAP components, Purpose, Reference strategies for software documents, Standards, practices, and testing and validation conventions, Reviews and audits, Problem and how to implement reporting,Tools, techniques, and them methodologies, Code control, Media • Implement a software control, Supplier control, Records collection, quality assurance plan maintenance, and retention • Relate quality to the • Implementation of SQAP: Management current standards for acceptance, Acceptance by development process improvement. personnel, Planning for SQAP implementation, Resources, Scheduling, Risk Assessment, Training, Distribution of SQAP, Execution of SQAP _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 10 of 19
  • 11. MSc SOFTWARE ENGINEERING v1.0 ELECTIVES MODULES Module Module Title Aims/ Learning Module Outline Code Outcomes SEM5101 Software Aims • Project planning and management, Project This module aims to Project Management Plan (IEEE Std Management prepare the students to 1058.1) make good use of project • Product development life cycles, management principles in Software life cycles, Development life software development cyles projects. • Software maintenance, Life cycles incorporating software reuse, How to Learning Outcomes pick the appropriate life cycle? On successful completion • Software development processes, of this module, students Process concepts, Process maturity should be able to: (CMM), Process Interaction (IEEE Std • Set up a project team, 1074), Supporting or interfacing plan and schedule processes tasks and monitor • Marketing, Activity planning and project scheduling • Understand the nature • Cost and resource estimating, of software and be able Resource management to deal with the • Determining project status, Contracting different issues related and outsourcing to software • Organisational strategies, Managing maintenance teams, Environmental and social • Know the standards factors used in project management. • Be able to devise an appropriate structure for an IT department for different contexts • Understand the issues related to outsourcing of the IT function OUT5101 IT Sourcing Aims  IT Services This module aims at  IT Alignment to business sensitising students on the  Outsourcing - Economic point of view need for a proper IT  Outsourcing - Resource-based view sourcing strategy for an  Risk Management efficient use of funds and  Contract Management an effective contribution of  Insourcing / Back sourcing IT to overall business  Transformational Outsourcing performance.  Offshore software development  Business Process Outsourcing Learning Outcomes  International Trends Students are expected to understand the processes involved in sourcing of IT and to deal with the resulting issues for optimal use of IT by the organization. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 11 of 19
  • 12. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code SEM5102 Software Aims • Goal-based framework for software Metrics This module aims at measurement: Software measure describing software metrics classification, Goal-based paradigms: and its measurement Goal-Question-Metrics (GQM) and theory, models of software Goal-Question-Indicator-Metrics engineering measurement, (GQIM), Applications of GQM and software products metrics, GQIM software process metrics • Empirical investigation: Software and measuring engineering investigation, Investigation management. principles, Investigation techniques, Formal experiments: Planning, Formal Learning Outcomes experiments: Principles, Formal On successful completion of experiments: Types, Formal this module, students experiments: Selection, Guidelines for should be able to: empirical research • Understand • Measuring internal product attributes: Measurement size: Software size, Software Size: theory Length (code, specification, design), • Be familiar with Software Size: Reuse, Software Size: Software product Functionality (function point, feature and process point, object point, use-case point), measurements Software Size: Complexity • Understand • Measuring internal product attributes: Measurement structure: Software structural management measurement, Control-flow structure, Cyclomatic complexity, Data flow and data structure attributes, Architectural measurement, • Measuring software reliability: Reliability concepts and definitions, Software reliability models and metrics, Fundamentals of software reliability engineering (SRE), Reliability management models • Software test metrics: Test concepts, definitions and techniques, Estimating number of test case, Allocating test times, Decisions based on testing, Test coverage measurement, Software testability measurement, Remaining defects measurement • Object-oriented metrics: Object- Oriented measurement concepts, Basic metrics for OO systems, OO analysis and design metrics, Metrics for productivity measurement, Metrics for OO software quality _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 12 of 19
  • 13. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Learning Outcomes/ Aims Module Outline Code PRG5106 Agent On successful completion of • Introduction to agent and agent-based Technology this module, students should system be able to have: • Difference between agents and existing • An understanding of the software paradigms (such as objects variety of applications of and expert systems)? intelligent agents, and the • Types of application for which an agent- strengths and limitations of based solution is appropriate the current methods. • Major applications of agent technology, • An understanding of some benefits of agent technology of the technology and • Main obstacles and pitfalls in the way of algorithms that are used to the agent system developer construct intelligent agents. • Practical experience of building intelligent agents. Aims This module aims at preparing the student to build intelligent agents, that is, intelligent software programs that can act by themselves in some part of the human world. The kinds of tasks that an agent could be useful for and also the underlying designs, techniques, and algorithms for implementing such agents, will also be considered. MCT5101 Mobile and On successful completion of • Wireless Transmission Pervasive this module, students should • Telecommunication Networks Computing be able to: • J2ME • Show their understanding • .NET for mobile devices of Mobile and Pervasive • Bluetooth computing • WIFI • Know the different • Wireless Security technologies used in the • Pervasive Computing national and international • Advances in Mobile and Pervasive markets Computing • Design and build application for mobile devices Aims The aim of this module is to provide a general understanding of the Mobile and Pervasive computing field, get the student to think about the mobile computing field in a national and international context as well as giving the students hands on experience in mobile computing technologies currently used in Industry. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 13 of 19
  • 14. MSc SOFTWARE ENGINEERING v1.0 _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 14 of 19
  • 15. Module Module Title Aims/ Learning Outcomes Module Outline Code WAT5101 Service Aims • Service-Oriented Architecture in the Oriented This module aims is to MSc SOFTWARE ENGINEERING v1.0 enterprise: response to change and Architecture examine the service transformation, The evolution of the service oriented architecture and idea, Managing upside and downside risk the different types of • SOA and Business Process Management: services that can be Service-oriented government and business, implemented. Line-of-business services and service domains, Service-level abstractions, Learning Outcomes Reusable business vs. technical services On successful completion of • Fundamentals of service-oriented this module, students architecture: Architecture focus, the should be able to: concepts of the service contract, Enabling • Understand the infrastructure concepts of service • The Enterprise Architecture perspectives, oriented architecture The Zachman Framework and SOA, • Design and implement Process and use-case views, Data and webservices and other information views, Logical view, Contract service oriented view, Implementation view applications • Service-oriented prerequisites: Security, Service management, Process and composition, Metadata management • Key components for implementing SOA: SOA Meta model – Understanding the role of the service contract, Policy-based services, Service-oriented processes, Atomic services and composite services • Building a service and managing the business side: Granularity, Context/domain dependency, How to identify services (processes), How to differentiate services • Enabling Technologies and Standards: What are the current platform vendors offering, How are emerging startups filling the gap? The standards state-of-the-art • Developing the SOA Roadmap: What are the right starting points? Prioritizing service development and infrastructure expenditures, Making the right organizational changes, Governance and using SOA to increase visibility ISM5103 Strategic Aims • Connectivity: Strategic, Physical, Information This module aims at Organisational System developing the managerial • Contingency Plan and Business Impact skills for the formulation of Analysis strategic IS/IT plan. • Strategic IS/IT Frameworks • From Strategy to Architecture to Learning Outcomes Infrastructure • On successful • Organising and Controlling IS Processes – completion of this Outsourcing Strategies module, students • Knowledge Management should be able to: • IS/Business Strategies Alignment • Analyse case studies • Identify business strategies • Apply strategic framework to formulate IS Module Module Title Aims/ Learning Outcomes Module Outline Code DBT5101 System Aims • Sources: Data Warehouses, Temporal, Integration This module enables Scientific, The Web students to have knowledge • Sources and Storage: Distributed _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 and skills of handling very Databases, Data Warehouses, The of 19 Page 15 large volumes of data in a Web. variety of database • Manipulation: Data Mining, Online applications. Analytical Processing (OLAP), Visualisation for Exploration.
  • 16. MSc SOFTWARE ENGINEERING v1.0 _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 16 of 19
  • 17. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code ISM5102 Entrepreneurship Aims • The small business decision, This module provides an Developing and defining the overview of developing, business concept, Identify planning, financing and Business opportunities launching new businesses in • Methods of starting a business, software development. Forms of business organisation, Consideration is given of the Financing, Start up strategy, opportunities and issues specific Mission Statements to software development in • Product life cycle, Stages of small business ventures during business growth pre-startup, launch and initial • Development of a business growth stages. plan, Case studies, Risk Management: Finance and Learning Outcomes Controls, Business Tax • Upon the successful • Measuring success, Future completion of this module, Trends and Issues students should be able to: • Grasp and assess new business ideas. • Understand the business structures, stages of growth and profit • Develop a business plan for a new business. • Identify key launch process and timeline points and identify market niches. SDT5203 Agile Aims • Test Driven Development: Test Programming This module aims at providing Driven Development Rules, The Techniques the students with skills and TDD Development Cycle, TDD as a knowledge required to build and Design Technique, TDD as deliver high quality software in a Documentation, TDD Benefits, Unit rapid and regular way. Testing Patterns / Anti Patterns, Unit Testing Legacy code, Learning Outcomes Managing Suites of Unit Tests, On successful completion of this Refactoring Unit Test Code, Unit module, students should be able Testing Legacy Code, TDD of GUI to: applications, TDD multi-threaded • Understand the concepts applications, Dealing with legacy and techniques applications • Design and implement • Refactoring: Unit Testing Support, software using agile Introducing the Refactoring programming technique. catalogueRefactoring Legacy Code, Idioms, Refactorings and Design Patterns, Metrics • Automated Acceptance Testing: Automating acceptance testing as executable requirements, Creating an automated acceptance testing environment • Placing it in Context: eXtreme Programming, XP Values, Principles and Practices, TDD and Refactoring within the context of eXtreme Programming. _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 17 of 19
  • 18. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code ISM5101 Information Aims • Economic charateristics of Digital Technology The module aims at Products and Services: Distinctive Economics assisting the students to economic and organisational understand the application characteristics of Digital Products and of economic analysis to the Services, What is information product?, market of information What is virtual product? What is technology infrastructure. different about services? What are different digital product types and Learning Outcomes categories? On successful completion of • Cost Structure of Virtual/Information/IT this module, students Products and Services: What should we should be able to: know about costs from Microeconomics • Identify, quantify and what are the specifics of the cost and evaluate the structure of IT Products? Costs of costs and benefits production, Fixed costs, Variable costs, of existing and Costs of distribution - transaction costs, proposed IT Costs of consumption - Search costs, systems. Switching costs. • Critically assess • Market Structures, Competition and methods for Regulatory Policy in the IT: From cost evaluating the structure and consumer demand to return on market structure, Consumer demand investments in IT. and differentiated quality, Cost structure • Employ appropriate and differentiated quality, Imperfect economic competition in virtual product markets, qualitative and Monopolistic competition and zero quantitative marginal costs measures of the • Pricing of Digital Products and impact of IT in Services. Product Choices and various business Discriminatory Prices: Monopolistic context. pricing, Price discrimination, Bundling, Versioning • Management, Business strategies, Advertising, Feasibility and Efficiency of IT projects: Intersection with the marketing discipline (advertising), Intersection with the accounting discipline (managerial and capital accounting), Business planning, feasibility and efficiency analysis based on economic characteristics of IT products, market structures and prevailing pricing mechanisms. • Electronic Monetary Instruments and Electronic Payment Systems: Monetary Economics Perspective • Economic Aspects of Copyright Protection: Information products are easy to reproduce – easy to copy illegally! Banning/regulating vs proper marketing and managing _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 18 of 19
  • 19. MSc SOFTWARE ENGINEERING v1.0 Module Module Title Aims/ Learning Outcomes Module Outline Code HCA5105 Embedded Aims • Microprocessor/Microcontroller Systems This module aims at Architecture preparing the students to • Hardware/Software Co-design learn the applicability of • Hardware/Software Partitioning embedded systems in the • Device Drivers real world and understand • Real-Time Operating Systems all the design and • Scheduling Algorithms implementation issues • Control Theory involved when contructing • Interfacing an embedded system. Learning Outcomes On successful completion of this module, students should be able to: • Understand the architecture and application of embedded system. • Design and implement embedded systems • Design and implement device drivers and interfaces • Understand the concepts of a real-time operating system ISM5104 Global IT Aims  Global information technology Management This module aims at environment sensitising and providing  Framework for building national students with knowledge on information structure global IT management.  International business opportunities on the information superhighway Learning Outcomes  Problem of data quality in a developing Students are expected to economy understand the processes  How can information technology enable involved in global IT developing countries to integrate into management and design the global economy? and implement a proper  Information technology planning and framework. architectures for networked global organizations  Information systems resource structure and management in multinational organizations  Issues in Global Outsourcing  Global software outsourcing  Global management support systems  Strategic application of information technology in global business Developing and implementing global information systems _________________________________________________________________________________________________________________________ MSE v1.0/April 2006 Page 19 of 19