1. Passing from design to implementation
Jarosław Kuchta
Embedded Systems Software Engineering
Passing from design to implementation
GUT - INTEL 2015/16
Embedded Systems Software Engineering

2. Embedded Systems Software Engineering
Issues
Technology choose
OO programming language vs script language
Automatic code generation
Method implementation
Property access methods
Mapping abstract components to concrete classes
Framework usage
Code documentation
Reverse engineering, back-synchronization
GUT - INTEL 2015/16
Embedded Systems Software Engineering

3. Embedded Systems Software Engineering
Technology choose
Target execution environment
Programming language
Programming environment
User interface technology
Database technology
GUT - INTEL 2015/16
Embedded Systems Software Engineering

4. Embedded Systems Software Engineering
Choose criteria
Environment availability (price, licenses)
Knowledge of language and tools
Need to fit to just existing solutions
Need to fit to specific user requirements
GUT - INTEL 2015/16
Embedded Systems Software Engineering

5. Object-oriented programming languages
Language categories
Object-oriented programming languages
Script languages
data abstraction
encapsulation
modularity
polymorphism
inheritance
weak typing (unknown class properties and functions)
flexible fitting to external (third-party made) components
portability (wide usage)
slower execution (interpretation or just-in-time compilation)
GUT - INTEL 2015/16
Embedded Systems Software Engineering

6. Automatic code generation
Skeleton code
GUT - INTEL 2015/16
Embedded Systems Software Engineering

7. Method implementation
Parameter list completion
Overloaded methods vs. default parameter values
Virtual vs. abstract methods
Optimization (final, sealed, const)
GUT - INTEL 2015/16
Embedded Systems Software Engineering

8. Property access methods
public int getValue() { return _value; } public void setValue(int x) { _value = x; } private int _value;
public int Value { get { return _value; } set { _value = x; } } private int _value;
GUT - INTEL 2015/16
Embedded Systems Software Engineering

9. Mapping abstract design components to concrete implementation classes
Stereotype
ASP class
JSP class
form
Page
button
Button
ImageButton
label
Label
text box
TextBox
TextField
check box
CheckBox
needs adaptor to a specific framework
GUT - INTEL 2015/16
Embedded Systems Software Engineering

10. Embedded Systems Software Engineering
Framework usage
Assumption: implementation acceleration
Constraint: a framework should be well known
Threats:
A framework can not be fitted to the project needs
Developers don’t know exactly how to use a framework:
Weak documentation
Unknown internal framework mechanisms
Incomprehensible source code
Lack of source code & obscured binary code
Sealed classes – no chance for modification
Project is late!
GUT - INTEL 2015/16
Embedded Systems Software Engineering

11. Embedded Systems Software Engineering
Code documentation
Self-documentation – meaningful names
Special documentation comments (documentation generation)
Code structure overview description:
files and folders hierarchy
component list
class reference
GUT - INTEL 2015/16
Embedded Systems Software Engineering

12. Reverse engineering & back synchronization
Code-based approach
Model-based approach
GUT - INTEL 2015/16
Embedded Systems Software Engineering

13. Embedded Systems Software Engineering
Bibliography
Roger S. Pressman: Software Engineering. A Practitioner's Approach (book, PDF)
Coad, Yourdon: Object-Oriented Programming (book)
GUT - INTEL 2015/16
Embedded Systems Software Engineering