Filetype PDF | Posted on 30 Jan 2023 | 2 years ago
Authentication
digital resources
148x Filetype PDF File size 0.24 MB Source: www.conference.rtu.lv
Prototyping process in education and science
Nadezhda Kunicina Anatolijs Zabasta
Institute of Electrical Engineering and Electronics, Institute of Electrical Engineering and Electronics,
FEEE, Riga Technical University FEEE, Riga Technical University
Riga, Latvia Riga, Latvia
Nadezda.Kunicina@rtu.lv Anatolijs.Zabasta@rtu.lv
Antons Patlins Ivana Bilic
Institute of Electrical Engineering and Electronics, Faculty of Economics,
FEEE, Riga Technical University University of Split,
Riga, Latvia Split, Croatia
Antons.Patlins@rtu.lv ibilic@efst.hr
Janis Peksa
Institute of Information Technology
Faculty of Computer Science and Information Technology,
Riga Technical University
Riga, Latvia
Janis.Peksa@rtu.lv
Abstract— Current article shows the prototyping process, learning, research, and scientific writing, is given [15] as well
types of prototyping models, best practices of prototyping, as sustainability and motivation in the education process
limitations of prototypes, advantages, and disadvantages of shown in [14], [16].
prototyping, as well as differences between software and Student Engagement in Cross-Domain Innovation
hardware prototyping. Prototyping infrastructures are also Development and the Impact of IT on Learning Outcomes and
shown here. In this case, three examples from Riga Technical Career Development as well as improvement and development
University are offered. This publication demonstrates the of study programs, methods, and approaches shown in
authors’ opinions only, and it cannot be regarded as the
European Union’s official position. The paper is developed in a [17],[18],[19],[20],[21],[22],[23]. Information Tools for
frame of the project “ERASMUS+ Capacity-building in the Field Education of Electrical Engineers offers in [24]. Practical
of Higher Education 2019 Call for Proposals. Development of Knowledge Improvement in Electrical Engineering Education
practically-oriented student-centered education in the field of is shown in [25],[26],[27].
modeling of Cyber-Physical Systems, CybPhys. 609557-EPP-1- The current article aims to show the prototyping process,
2019-1-LV-EPPKA2-CBHE-JP – ERASMUS+ CBHE. The prototyping models, best prototyping practices, limitations of
article is also devised for students of applied physic and electrical prototypes, advantages, disadvantages of prototyping, and
engineering specialties. The article can be useful for students and differences between software and hardware prototyping.
professionals focusing on innovation management issues.
Prototyping infrastructures are also shown here. In this case,
Keywords—education, electrical engineering, prototyping, three examples from Riga Technical University are offered in
innovations, market, entrepreneurship, innovation management. the last section of the article.
I. INTRODUCTION II. PROTOTYPING PROCESS
The article “Prototyping process in education and science” The prototyping method includes the following phases [1]:
provides technical background for students of applied physic 1. Identifying specific criteria – a prototyping model starts
and electrical engineering specialties. The article is addressed with an overview of the requirements. Throughout this
for all levels of students and developers of prototypes of step, the device specifications are described in detail.
electromechanical devices, automotive control schemes, During the process, system users are interviewed to learn
motion control solutions, and a high level of automated from the client what their expectations are.
infrastructure management technologies.
Riga Technical University offers different studies in the 2. Design the prototype – step two is either a conceptual
field of sustainable education. Research the phenomenon of design or a rapid design. A simple design of the system is
motivation, towards science, through effective teaching, generated at this level. It is not a complete build, though,
and giving the user a quick understanding of the program. cohesive product. This approach is useful in reducing the time
The quick design helps in developing the prototype. for feedback between the user and the application
3. Build a prototype – an actual prototype is designed in this development team.
process based on the fast design information. It is a tiny -Enormous prototype
working model of the system required. The enormous prototyping approach is used mainly for
4. User evaluation – the proposed system is presented to the web creation. It is composed of three phases in sequence.
client for an initial assessment at this point. It helps the 1. The basic prototype is present in HTML format, with all
work model find its power and weakness. Comments and the current websites.
suggestions are collected from the client and forwarded to
the developer. 2. Use a service layer for a prototype can simulate the data
5. Refining prototype – If the user is not pleased with the flow.
current prototype, modify it according to its feedback and 3. The systems are incorporated in the final version and
suggestions. This process will not be finished until all the integrated.
user-specified requirements are met. Once the user is
satisfied with the prototype developed, a final system is B. Best practices of prototyping
developed based on the end prototype approved. Here are some things can look at during the prototyping
6. Test product, implement a product, and maintain the process [3]:
product – if the final system, based on the final prototype, Once the requirements are unknown, should be using
is produced, it is thoroughly tested and deployed for prototyping
production. The system is maintained routine to minimize
downtime and to prevent large-scale failures. Planned and regulated prototyping is critical
A. Types of prototyping models Daily meetings are essential for holding the project on
Four types of models for prototyping are [2]: schedule and preventing unnecessary delays
1. Fast prototypes for throw-away, The consumers and the designers should be aware of the
challenges and drawbacks of prototyping
2. Prototype evolutionary, The decision-maker needs to accept a concept early and
3. Incremental prototype, then encourage the team to progress to the next level.
4. Enormous prototype. In the software prototyping process, if there is a need to
-Fast prototypes for throw-away implement new concepts, should never be afraid to
change earlier decisions
Its preliminary requirement is based. It has designed For each version should select the appropriate step-size
quickly to demonstrate how visually the requirement would
look. Feedback from the customer helps push modifications to Implement critical features early on, so it can still have a
the requirement. The prototype is produced again before the worthwhile program if decision-maker runs out of time
requirement is based. A created prototype will be discarded in Advantages of the prototyping [4]:
this process and will not be part of the eventually accepted
prototype. This approach is useful to test solutions and get The users participate actively in development.
immediate feedback on consumer needs. Furthermore, errors may be found in the initial stage of
-Prototype evolutionary the process of software creation.
Here the created prototype is incrementally improved It is possible to recognize missing functionality, which
based on input from the customer until it is eventually reduces the risk of failure as prototyping is also
accepted. It helps save both time and effort. Prototype considered a disease prevention activity.
evolutionary can often be challenging to create a prototype Helps members of the team to communicate effectively.
from scratch for any process contact. This model is useful for
a project that uses a not well-known emerging technology. It is Consumer satisfaction occurs, and at a very early stage,
also used for a complex project, where it is crucial to test the consumer can feel the product.
every feature once. Evolutionary is useful because, in the There is hardly any chance that the software will be
initial stage, the condition is either not stable or not well rejected.
understood.
-Incremental prototype Quicker customer feedback lets decision-makers get
Throughout incremental prototyping, the final product is better approaches to app creation.
decimated into various small prototypes and individually Enables the customer to evaluate if the software code
created. The different designs are finally combined into one matches the specified software.
It helps the decision-maker find out which features are should be anticipated that actual sample costs would be
missing in the system. considerably higher than the overall manufacturing costs.
It also identifies complex functions or difficult ones. Prototypes are often used for concept revision for cost control
purposes by optimization and refining. Prototype testing can
Flexible design and fosters innovation. be used to reduce the probability of a concept not working as
It is a model that is clear cut, so it is easy to understand. expected, but prototypes usually can not eradicate all
probability. A prototype’s capacity to meet the expected final
No need for specialist experts to construct the model. output of the product is pragmatically and technically
constrained, and specific considerations and technical
The prototype acts as a basis to derive a specification for judgment are always needed before going ahead with a
the device. production design. Making the complete design is also costly
The concept helps provide a deeper understanding of the and can be time-consuming, particularly when replicated
needs of the consumer. many times — making the complete design, finds out the
challenges and how to fix them, and builds another complete
Prototypes may be altered or even discarded. design. Alternatively, fast prototyping or rapid application
development techniques are used for the initial prototypes,
Often a prototype serves as the basis for operating which implement a part of the complete design, but not all of
requirements. it. It helps designers and suppliers quickly and cost-effectively
Prototypes will provide early training for software check the product components most likely to have issues, fix
system consumers of the future. specific issues, and then construct the entire design.
Scaffolding and the telescope’s law express this counter-
Furthermore, the disadvantages [4]: intuitive idea — that the best way to construct something is to
Prototyping is a delayed process and takes time. create something else. Pros and cons summarized in the table
below [5]:
The cost of creating a prototype is a complete waste
because it eventually throws away the prototype. TABLE I. ADVANTAGES AND DISADVANTAGES OF THE PROTOTYPES
Prototyping can spur excessive requests for change. Pros Cons
Often, consumers may not take part in a more extended Users may test the program That iteration expands on the original.
period in the iteration process. There may be far too during development and The final answer will only be
many differences in software specifications when the provide positive feedback. incrementally more remarkable than the
A version of the throw-away original.
customer tests the prototype each time. can be developed in days. Formal end-of-phase evaluations can not
Lousy documentation, as the requirements of the With approaches evolving, take effect. Thus, the system’s
customers, change. consumers are becoming complexity is challenging to handle, and
Software developers are finding it very difficult to handle increasingly optimistic about the project never seems to end.
all the improvements requested by the clients. After the method and the Documentation of the device is
seeing a way earlier prototype model, the customers may outcomes. sometimes missing or insufficient since
believe that the actual product will be delivered to him Prototyping helps to spot the main emphasis is prototype creation.
shortly. When they are not satisfied with the initial defects and omissions early Device backup and recovery concerns,
prototype, the client could lose interest in the final on. functionality, and reliability may be
product. ignored in a rush to build a prototype.
Developers who want to create prototypes quickly can The cons and pros’ design methodology may differ and
end up designing solutions for under-standard may not always fully coincide with the above table. However,
production. these are some of the essential cons and pros that should be
C. Limitations of prototypes considered.
Engineers and prototyping specialists seek to recognize D. Software vs. Hardware prototyping
concept flaws to reproduce the functionality of their expected Software prototyping is the practice of developing
product consistently. It is necessary to note that prototypes prototypes of software programs, i.e., creating incomplete
must reflect a deviation from the final production design by iterations of the software program. It is also an operation that
their very nature. Regardless of variations in materials, can occur in software development and is similar to
procedures, and adherence to the specification, a prototype prototyping as understood from other fields, such as computer
may struggle to work acceptably while the output specification science or manufacturing [6].
would have been successful. A confusing notion is that Hardware prototyping is the practice of developing
prototypes may work acceptably, whereas manufacturing prototypes of physical hardware, i.e., creating incomplete
design can be faulty as prototyping materials and processes iterations of the hardware product. Very similar to software
can sometimes outperform their output equivalents. Besides, prototyping; however, the outcome is different; one can
owing to inefficiencies in components and procedures, it
physically touch it another to touch the software prototype functional aspects of the system (transaction speeds,
need to have the device like a computer or smart device. amount of data storage, response time).
Hardware prototyping is very similar to general prototyping 4. Capability/technique prototypes – used for design
principles; it is not discussed in more detail. However, approach or idea creation, presentation, and evaluation.
software prototyping into dimensions Horizontal and Vertical
prototyping [7]. -Operational prototyping
-Horizontal prototype Alan Davis proposed operational prototyping suggested
A common word used for a software user interface is the the functional prototyping to combine throw-away and
horizontal version. It provides a broad view of a whole system evolutionary prototyping with traditional systems. It provides
or subsystem, concentrating more on user interaction than sensibly the best of both the worlds of quick-and-dirty and
low-level system features, such as access to databases. conventional-development. Designers only create well-
Horizontal prototypes contribute to: understood features in constructing the evolutionary baseline
when playing poorly understood features using throw-away
Confirmation of device scope and user interface prototyping [10].
specifications. Those measures follow the following methodology:
Demo version of the program to get buy-in from the Using traditional creation techniques, and an
client. Create preliminary estimates of time, cost, and evolutionary prototype is built and transformed into a
effort for the development. model, defining and enforcing only the specifications
-Vertical prototype which are well understood.
A vertical prototype is a complete enhancement of a single Baseline copies are sent along with a professional
subsystem or feature. It is useful to get detailed specifications prototyper to several client sites.
for a given purpose, with the following advantages: The prototyper watches the user on the device at each
Server finishing architecture. location.
Obtain data volume and device interface specifications The prototyper logs it whenever the user experiences a
details for network sizing and performance engineering. problem or thinks about a new function or necessity. It
Clarify specific demands by digging down to the frees the user from documenting the question and allows
essential features of the device. him to continue to function.
The prototyper constructs a throw-away prototype on top
E. Software development method [8] of the baseline device after the user’s session is finished.
-Dynamic systems development method The consumer now makes use of and tests the new
The Dynamic Systems Development Method (DSDM) program. If the new modifications are not successful,
offers a structure for delivering business solutions that rely they are removed by the prototyper.
heavily on prototyping as a critical methodology and is When the user likes the changes, the prototyper writes
certified by ISO 9001. It builds upon commonly known requests for feature-enhancement and forwards them to
concept concepts. The concept may be a diagram, a business the development team.
process, or even a device put into production according to The engineering team then creates a new evolutionary
DSDM. DSDM prototypes aim to be gradual, evolving from prototype using traditional approaches, with the
simple forms to more complete ones. Often, DSDM modification requests in hand from all locations.
prototypes can be throw-away or evolutionary. Evolutionary
prototypes can evolve horizontally (width than depth) or -Evolutionary systems development
vertically (each section is constructed in detail with further
iterations detailing subsequent sections). In the end, Development of Evolutionary Systems is a class of
evolutionary designs will develop into final systems [9]. methodologies which try to implement evolutionary
The four prototype categories which DSDM recommends prototyping formally. John Crinnion mentions one particular
are: form, called Systemscraft, in his book Evolutionary Systems
Creation. Systemscraft was developed as a ‘prototype’
1. Business prototypes – problem formulation used to approach to be modified and adjusted to suit the specific
plan and demonstrate are automated. setting it was applied in. The principle of Systemscraft, not
2. Usability prototypes describe, improve, and show unlike evolutionary prototyping, is to construct and expand
usability, accessibility, look, and user interface design. upon a functional system from the initial requirements in a
series of revisions. Systemscraft puts great emphasis on the
3. Performance and capacity prototypes – used to identify, conventional analysis that is used in system creation [11].
demonstrate and forecast how systems can operate There are also other methods available that are not covered.
under peak loads and demonstrate and test other non-
no reviews yet
Please Login to review.
