ELEC5620: Model Based Software Engineering (2013 - Semester 2)
|Unit:||ELEC5620: Model Based Software Engineering (6 CP)|
|Faculty/School:||School of Electrical and Information Engineering|
|Session options:||Semester 2|
|Versions for this Unit:|
|Brief Handbook Description:||Model-Based Software Engineering focuses on modern software engineering methods, technologies, and processes used in professional development projects. It covers both the pragmatic engineering elements and the underlying theory of the model-based approach to the analysis, design, implementation, and maintenance of complex software-intensive systems.
Students will participate in a group project, which will entail developing and/or evolving a software system, following a full development cycle from requirements specification through to implementation and testing using up-to-date industrial development tools and processes. At the end of the course they will provide a presentation and demonstration of their project work to the class. There is no formal teaching of a programming language in this unit, although students will be expected to demonstrate through their project work their general software engineering and architectural skills as well as their mastery of model-based methods and technologies.
Students successfully completing this unit will have a strong practical and theoretical understanding of the modern software development cycle as applied in industrial settings. In particular, they will be familiar with the latest model-based software engineering approaches necessary for successfully dealing with today’s highly complex and challenging software systems.
The pedagogic grounds for this course and its focus on model-based approaches are to arm new software engineers with skills and perspectives that extend beyond the level of basic programming. Such skills are essential to success in software development nowadays, and are in great demand but very low supply. The dearth of such expertise is one of the key reasons behind the alarmingly high failure rate of industrial software projects (currently estimated at being greater than 40%). Therefore, this unit complements SQE and strengthens a key area in the program.
|Assumed Knowledge:||A programming language, basic maths.|
|T&L Activities:||Tutorial: tutorial
Project Work - in class: project
Project Work - own time: Students will work in groups to design, build and test a model-based software system.
Independent Study: Self study and independent learning is a key to success in this UoS and is essential for the project.
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
|Attribute Development Method||Attribute Developed|
|Different design criteria for MBSE systems are presented and analysed. Students are required to design their own MBSE system in the project work.||Design (Level 4)|
|Gain an understanding of MBSE technology. Various MBSE systems widely used in real applications are introduced and analysed.||Engineering/IT Specialisation (Level 4)|
|Master the fundamentals of software engineering modelling and analysis||Maths/Science Methods and Tools (Level 4)|
|Intensive research will be included in the project work and the assignment. Students need to collect comprehensive information from various sources in order to perform well.||Information Seeking (Level 4)|
|Project reports are one of the main assessment elements for the project work. Students need to write concisely, accurately and convincingly. Each team is also required to give a presentation about their project at the end of the semester.||Communication (Level 4)|
|The project work requires students to form groups and manage their progress through the entire project, including conceiving, design, building, testing and demonstrating the project.||Project Management and Teamwork (Level 4)|
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.Design (Level 4)
Project: Three project reports plus demo
Quiz: Two quizze
Assignment: Two assignments.
Final Exam: final exam.
|Faculty Policies & Procedures:||Academic Honesty in Coursework. All students must submit a cover sheet for all assessment work that declares that the work is original and not plagiarised from the work of others.
Coursework assessment and examination policy. The faculty policy is to use standards based assessment for units where grades are returned and criteria based assessment for Pass/Fail only units. Norm referenced assessment will only be used in exceptional circumstances and its use will need to be justified to the Undergraduate Studies Committee. Special consideration for illness or misadventure may be considered when an assessment component is severely affected. This policy gives the details of the information that is required to be submitted along with the appropriate procedures and forms.
Special Arrangements for Examination and Assessment. In exceptional circumstances alternate arrangements for exams or assessment can be made. However concessions for outside work arrangements, holidays and travel, sporting and entertainment events will not normally be given.
Student Appeals against Academic Decisions. Students have the right to appeal any academic decision made by a school or the faculty. The appeal must follow the appropriate procedure so that a fair hearing is obtained.
Note that policies regarding assessment submission, penalties and assessment feedback depend upon the individual unit of study. Details of these policies, where applicable, will be found above with other assessment details in this unit outline.
All university policies can be found at http://sydney.edu.au/policy
Various request forms for the Faculty of Engineering and IT can be found at http://sydney.edu.au/engineering/forms/
Note: Students are expected to have a personal copy of all books listed.
|Note on Resources:||IBM Rational Rose Software Development Environment|
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
|Week 1||The role and nature of model-based methods in SE.|
|Week 2||The theory of modeling language design.|
|Week 3||In-depth knowledge of the UML 2 modeling language.|
|Week 4||Approaches to model transformations.|
|Week 5||Approaches to automated code generation.|
|Week 6||Model analyses methods.|
|Week 7||Basics of MBSE tooling.|
|Week 8||Key elements of MBSE methodologies.|
|Week 9||Industrial application of MBSE (experience and issues).|
|Week 10||System and multi-model development.|
|Week 11||Architectural design using MBSE.|
|Week 12||Relevant research areas and directions.|
|Week 13||MBSE process models (e.g., agile modeling).|
|Exam Period||Assessment Due: Final Exam|
The following is a list of courses which have added this Unit to their structure.
This unit contributes to the achievement of the following course goals:
|Design (Level 4)||Yes||27.25%|
|Engineering/IT Specialisation (Level 4)||Yes||17.33%|
|Maths/Science Methods and Tools (Level 4)||Yes||36.67%|
|Information Seeking (Level 4)||Yes||6.25%|
|Communication (Level 4)||Yes||6.25%|
|Professional Conduct (Level 4)||No||0%|
|Project Management and Teamwork (Level 4)||Yes||6.25%|
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.