EMS704: Simulation and Model-Based Systems Engineering

Coursework 2: Systems Modelling Languages

1 Outline

Coursework 2 weighting:                                20% of total grade

Coursework 2 release date:                           Tuesday, 11th  March

Coursework 2 submission due date:              Tuesday, 15th  April 23:59

Coursework 2 submission format:                  Individual report (read the briefing at QM+)

Case study approval:                                  Monday  24th   March;  you  will  be allocated a  random case study afterwards.

EMS704 incorporates two courseworks. Coursework 2 is the place where you apply all the systems engineering concepts, methods, and tools (OPM, DSM, UML, and SysML) that you learn over the last five weeks of this module (taught by Dr Jun Chen) into a single case study 一 which you pick from a pre-defined list or suggest a new one. The objective is to learn how to think about business challenges from the view of a Systems Engineer:

•    What are the problems that industry is currently facing?

•    How systems engineering methods and tools can help different stages of product lifecycle?

•     How to use data generated by models and how to identify gaps in data / documentation?

•     How to integrate the models that are developed by different teams into an integrated ‘system modeI,?

•     How to use systems modelling languages to improve the communication between multidisciplinary teams?

The coursework will also assess your ability to dealing with complex engineering problems, and to write a concise professional report and to communicate your results to audience as if you are working in industry. Coursework 2 is a series of six tasks which will be collated into one technical report and submitted before the submission due date. Students will be given the opportunity to discuss the assignments during normal tutorial sessions (running almost every week). To get the final score of the coursework 2 (20% of total), students need to complete all tasks. Note that this is an individual assignment. You should not discuss the assignment with other students or work together with other students  in  its  completion.  This  document  introduces  the  outline  of Coursework  2,  providing important dates for the assignment, submission instructions, and the marking criteria.

2    Coursework briefing

Your Coursework 2 project report should be structured as follows:

Title page and an Executive Summary

Summarise the work you have done and outcomes and make recommendations from the view of Systems Modeller.

Section 1: Introduction to the Case

Give a lay summary about your case supported by an illustration / image – assuming audience have no knowledge of the field.

Section 2: Logical decomposition model

For the system you selected, develop a system decomposition using a Block Definition Diagram (BDD). The system decomposition should be at least three levels of hierarchy, including level zero, with at least  10 components per level and shown as a tree structure. Specify hierarchy levels, interconnections between components, and model organization.

Moving on from the BDD, describe system block interactions (for at least five blocks) using an Internal Block Diagram (IBD). Use an IBD to convey additional information that you can’t convey on a BDD: the connections among part properties and reference properties; the types of matter, energy, or data that flow across the connections; and the services that are provided and required across the connections.

Describe each of the IBD and BDD diagrams in a text (no longer than 150-200 words each).

Section 3: Systems requirements model

Make a list of at least 10 requirements in a table and for each requirement, determine the following information:

•    A formal expression (following the standard language … shall be able to … )

•    The verification method (e.g., inspection, simulation, observation)

•    Associated risk, in form. of low, medium, or high

•    Whether they are functional, performance, or non-functional (e.g., environmental, safety). At least three requirements in each category are required to be identified.

Use the requirement table to develop a Systems Requirements Diagram (REQ). Use the REQ to convey specification of requirements and relationships among model elements. Describe the REQ diagram in a text (no longer than 150-200 words).

Section 4: Systems architecture model

Part 1: Identify 3-5 primary functions of the system you selected. Then, identify at least three secondary functions for each of the primary functions. Remember, the function is what the system does; the activities, operations, and transformations that the system produces. It's why we build the system, and composed of process + operand (e.g., charging + voltage).

Part 2: Use the information about system decomposition in Section 2 and identify a minimum of 10 forms (objects) for the system you selected. Remember, the form is what the system is which enables the functions.

Part 3: Combine the functional architecture (obtained in part 1) and logical architecture (obtained in part 2) together and develop a N x N Design Structure Matrix (DSM) model with at least 15 elements (including both functions and forms) and connections between them. Clearly label each row and column (e.g., A, B..) – consistent with component names and use the DSM Excel Macro tool (see QM+ week 2 material) to partition the DSM model. Describe the DSM model in a text (no longer than 150-200 words).

Section 5: System behaviour model

For the system you selected, describe its most typical behaviour using at least three diagrams from the list: Use Case diagram, Activity diagram, Sequence diagram, or State Machine diagram. Each diagram should contain all the important information about the system, a well representative of the complexity of the case. See the Weeks 3 and 4 lecture / tutorial notes for information about each of diagrams and examples.

Use this diagram to convey specification of sequences of actions, life cycle of a block, message- based behaviour. Describe each diagram in a text (no longer than 150-200 words).

Section 6: Systems parametric model

Describe system parameters using a Parametric Diagram (PAR). Use a PAR to convey constraints, equations and inequalities and system related parameters. Describe the PAR diagram in a text (no longer than 150-200 words) and mention how it would support integration of engineering analysis and design models.

Section 7: Total system model

Combine all four aspects of system model (requirement, structure, behaviour, and parametric) into one piece and discuss how this total system model uncovers the interactions within and across the system. You can use an example of change in a requirement to demonstrate how this change affects other requirements (in the same diagram) or functions and blocks in other diagrams; and what would be your suggested strategy to mitigate negative impact of such changes in your system.

Section 8. Conclusions and recommendation

Summarise what you have done in your case study, what was the outcomes - few bullet points about influential elements of the system, what would be the potential impact of your work in the area of your case, and make recommendations.

Bibliography

Include references to any works used in the report. This section does not contribute to the page limit (50 pages) for the report.

Appendix

Provide your (Matlab, Python) codes listings as an appendix to the report. The listings do not count towards the page count for the report.

SysML Software

Visual Paradigm cloud version (link) is the primary diagramming tool for this assignment, however students are free to choose another SysML modeIIing tooI if that’s a preferred option - as long as they can capture all the required information requested in this assignment.

3    Suggested topics for case study

•   Infrastructure systems (e.g., Hyperloop system, HS2 project)

•   Automotive systems (e.g., electric cars, Formula 1 cars, hybrid cars)

•   Space systems (Columbia space shuttle, Europa Clipper Mission, James Webb Telescope)

•   Robotic systems (e.g., an articulated robot)

•   Healthcare systems (e.g., medical equipment, pharmaceutical systems)

•   Smart cities (e.g., transportation systems, IoT)

4 Assessment

To get the final score of this case project, you need to submit your project report as a single PDF file to QMPlus before the deadline. Coursework 2 will be marked out of 100. Note that to get the final score of the case project, your project needs to contain all the required sections outlined above (in Section 2 of this document). The marking rubric below provide guidance on how final technical report will  be  assessed.  Section   1  will  be  assessed  via  its  clarity,  completeness,  consistency  and coherency. Note that this is indicative only and the actual mark awarded will be a holistic judgment of the overall quality of submitted work.

Section 2. Logical decomposition model        max 10 points

Section 3. Systems requirements model        max 10 points

Section 4. Systems architecture model          max 15 points

Section 5. Systems behaviour model             max 20 points

Section 6. Systems parametric model            max 10 points

Section 7. Total System model                       max 10 points

Clarity, Completeness & visual effectiveness                        max 10 points

Consistency and coherency                           max 5 points

Analytical thinking / reasoning                       max 10 points

Total                                                           max 100 points

5    Penalties for late submission

Late submissions will incur the usual penalties of a 5% reduction in the mark for every working day (or part thereof) that the coursework is late and a mark of zero for submission more than 5 working days late. For more information see the University ‘Late Submission Penalties’ section.

6 Feedback

Detailed marksheet will be provided within 15 working days after submission of the report, in line with the School’s procedure. The marking criteria (in Section 4 above) provide a guide to what areas the feedback will be provided on. Note that marks may be subject to change as a result of unfair means.

7 Unfair means

Your Technical Report will be checked through QM+ Turnitin after submission. The use of unfair means, e.g., plagiarism and collusion, is strictly forbidden. This is an individual assignment. You should not discuss the assignment with other students or work together with other students in its completion. The assignment must be wholly your own work.   References must be provided to any other work that is used as part of the assignment.  Any suspicion of the use of unfair means will be investigated and may lead to penalties. For more information, see the University Student Handbook 2023-24: Plagiarism and  referencing. If you  are  at  all  unsure  about what this  means and the implications for your work, then you should consult the Module Leader.

8    Extenuating circumstances

If you have any medical or special circumstances that you believe may affect your performance on the assignment then you should  raise these with the  Module  Leader  via email at the earliest opportunity before oral presentation. Before completing an extenuating circumstances form, make sure you read the university guidelines, available from here. Please note the decision of the module leader will be final in all requests for extensions.

9 Help

This  assignment  briefing  should  provide  all  the  information  that  is  required  to  complete  this assignment. Remember that you need to decide on what the most appropriate approach and also how exactly to structure your work. This is part of what you are being assessed on and will assess your knowledge and understanding of the lecture notes and research skills. However, if you need further clarifications on the assignment then please talk to Dr Jun Chen (j[email protected]) after one of the lectures and tutorial sessions, or email the tutors to book an appointment.