​

This standard identifies the competences you need to construct a software design as part of the product definition activity, in accordance with approved procedures. You will be given a detailed brief or a request for change/modification order, and you will be required to access these requirements and to extract all necessary information in order to carry out the software design activity. You will need to select the appropriate software design tool to use, based on the type and complexity of the software functions to be developed. Peer review feedback will also need to be evaluated and undertaken, and any lessons learned from the activity will need to be shared within the business.  You will be expected to use current British, European, international and company standards to produce a software design, which must include the identity of the appropriate design elements, date of software modification and other relevant information.

Your responsibilities will require you to comply with organisational policy and procedures for working in the software development team. You will be required to report any problems with the computer hardware, software or procedures that you cannot personally resolve, or that are outside your permitted authority, to the relevant people. You will be expected to work to verbal/written instructions and draft specifications, with a minimum of supervision, taking personal responsibility for your own actions and for the quality and accuracy of the work that you carry out.

Your underpinning knowledge will provide a good understanding of your work, and will provide an informed approach to applying software design procedures. You will understand the computer system and software used, and its application, and will know about the various tools and techniques used to produce the software design, in adequate depth to provide a sound basis for carrying out the activities to the required specification.

You will understand the safety precautions required when working in the software development team. You will be required to demonstrate safe working practices throughout, and will understand the responsibility you owe to yourself and others in the workplace.

---

​

1. work safely at all times, complying with health and safety legislation, regulations, directives and other relevant guidelines
2. plan the software design modelling activities before you start them
3. use appropriate sources to obtain the required information for the software design model to be created
4. access and use the correct design modelling software
5. use appropriate techniques to create software design models
6. use codes and other references that follow the required conventions
7. produce the finished software design models, with sufficient detail to allow implementation
8. make sure that design models are checked and approved by the appropriate person
9. undertake and evaluate peer review feedback, and identify what lessons can be learned from the feedback
10. provide technical feedback on the engineering software design activity undertaken including lessons learnt and those lessons which can be shared within the business
11. save and store the software design models as the appropriate file type and in the correct location
12. deal promptly and effectively with problems within your control, and seek help and guidance from the relevant people if you have problems that you cannot resolve

---

​

1. the specific safety precautions to be taken when working with software development environment hardware (to include such items as safety guidance relating to the use of visual display unit (VDU) equipment and work station environment such as lighting, seating, positioning of equipment; repetitive strain injury (RSI); the dangers of trailing leads and cables; how to spot faulty or dangerous electrical leads, plugs and connections)
2. the importance of good housekeeping arrangements (such as cleaning down work surfaces; putting media, manuals and unwanted items of equipment into safe storage; leaving the work area in a safe and tidy condition)
3. the importance of applying the appropriate behaviours in the workplace and the implications for both the individual and the business if these are not adhered to
4. the relevant sources and methods for obtaining any required technical information relevant to the model being produced (such as drawing briefs, specification sheets, request for changes or modifications to models; technical publications; calculations; software requirements)
5. identification of the correct version of software tool, and the various design techniques that are supported by the tool
6. how to access the specific software design model to be used
7. the basic principles of software design and how to apply them to the work being undertaken
8. types of representation that may be produced by the modelling software (such as static structure, sequence diagrams)
9. the national, international and organisational standards and conventions that are used for the models/drawings
10. the application and use of design modelling tools for either functional or object orientated methods
11. how to access, recognise and use a wide range of standard components and symbol libraries from the modelling tools
12. how to evaluate and undertake any peer review feedback and how any lessons learned from the engineering software design activity can be shared within the business
13. the importance of undertaking and recording the rationale behind the design decision and the short term and long term consequences
14. the need for document control (such as ensuring that completed models are approved, labelled and stored on a suitable storage device)
15. why it is necessary to be able to recall previous issues of modified models
16. when to act on your own initiative and when to seek help and advice from others

---

---

​

1. Prepare for the software design activities, by carrying out all of the following:

   1. check that the working environment is in a safe and appropriate condition and that all working equipment is in a safe, tested and usable condition (such as cables undamaged, correctly connected, safely routed)
   2. open the appropriate design modelling software
   3. set up the software design modelling environment and select a suitable template/folder
   4. identify relevant software design requirements to be implemented
   5. identify the required standards and all relevant sources (such as software requirements and existing design)

2. Use four of the following to obtain the necessary data to produce the required design model:

   1. new model brief/request                                 
   2. specifications (such as software acceptance tests)
   3. change order/modification request                
   4. regulations
   5. technical publications                                  
   6. previous models/designs
   7. calculations                                                   
   8. software requirements
   9. standards reference documents (such as Universal Modelling Language (UML))
   10. notes from meetings/discussions
   11. other specific available data

3. Take into account seven of the following, as appropriate to the design model being produced:

   1. function                         
   2. cost                             
   3. operating environment
   4. quality                       
   5. lifetime of the product    
   6. interfaces
   7. testing method               
   8. accuracy                        
   9. safety
   10. resources (such as memory, performance and bandwidth)     
   11. design structure          
   12. ease of modification of design

4. Carry out all of the following before producing the software design model:

   1. ensure that the data and information you have is complete and accurate
   2. analyse the data and information to identify the model requirements
   3. recognise and deal with problems (such as technical issues and lack of information, or incorrect information)

5. Use one of the following modelling methodologies to produce the software design:

   1. object orientated design (such as UML)
   2. functional design (such as Modular Approach to Software Construction Operation and Test (MASCOT)

6. Create/modify the software design elements using five of the following:

   1. objects                                  
   2. classes                      
   3. types
   4. functions                              
   5. procedures              
   6. data
   7. change requests             
   8. sequence diagrams

7. Check the software design model for all of the following:

   1. completeness                      
   2. coherence                
   3. accuracy
   4. coupling and cohesion          
   5. traceability

8. Save and store the software design model in appropriate locations, to include carrying out all of the following:

   1. check that the design model is correctly titled, referenced and annotated
   2. ensure that the software design model has been checked and that it complies to company procedures
   3. save the design model to an appropriate location (such as storage device, configuration database)
   4. register and store the design models in the appropriate company information system (where appropriate)
   5. record and store any changes to the design models in the appropriate company information system
   6. ensure that a separate backup copy is created and placed in safe storage

9. Produce software design models which comply with one of the following:

   1. company standards and procedures
   2. customer standards and requirements
   3. statutory regulations and codes of practice
   4. software standards
   5. BS, ISO or BSEN standards and procedures
   6. other international standards

---

---

---

​Additional Information

You will be able to apply the appropriate behaviours required in the workplace to meet the job profile and overall company objectives, such as:

• strong work ethic
• positive attitude
• team player
• dependability
• responsibility
• honesty
• integrity
• motivation
• commitment

---

---

---

---

---

1

---

31 Mar 2020

---

Current

---

Original

---

Semta

---

SEMEM450

---

Corporate Managers and Senior Officials, Engineering, Engineering and Manufacturing Technologies, Functional Managers

---

1121

---

engineering; leading; design structure; operating environment; interfaces; safety; specifications

---