Software Engineering: A Hands-On Approach

Lee, Roger Y.

doi:10.2991/978-94-6239-006-5

Cited by 5 publications

(4 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…as it pertains to the environment, health, safety and public welfare, 2) become familiar with the engineering design process which includes learning to meet the desired needs/requirements within realistic constraints of product development with a focus on environmental, social, ethical and safety regulations, to name a few, 3) learn to articulate engineering problems and translate them into a structured design to reflect the product requirements, 4) master applying formal iterative formal decision making methods to assist in choosing between alternative conceptual designs, 5) acquire basic 2D and 3D sketching skills using engineering CAD tools, 6) experience developing virtual and physical prototypes based on an engineering design using various engineering tools, and 7) learn to work collaboratively in teams and communicate effectively using oral, written, and graphical forms. Chapters (1-4) [10] Chapters (1,(4)(5)(6)(7)(8)(9)(10)13) [11]. These seven learning outcomes are hereby referred to as CLO's (Course Learning Outcomes).…”

Section: B Educational Objectives and Expected Outcomesmentioning

confidence: 99%

“…The second part contains two to three small problems for the students to solve allowing them to brainstorm and assess their understanding of the new topic. The hands-on learning that takes place in the laboratory further bridges the gap between the theoretical focus in the lectures and the real world experiences shared by the guest speakers [13].…”

Section: A Typical Weekmentioning

confidence: 99%

See 1 more Smart Citation

First Year Engineering Design: Course Design, Projects, Challenges, and Outcomes

Hashim¹,

Tatarniuk²,

Harasymchuk³

2022

Preprint

View full text Add to dashboard Cite

This paper outlines the essential components of developing an introductory course in Engineering Design for the first year, first semester students at Thompson Rivers University (TRU). The course design accounts for the teaching context, stakeholder interests, and Canadian Engineering Accreditation Board (CEAB) criteria. The proposed course design scaffolds engineering design projects of three different levels. Through the described course, students become familiar with the engineering design process including translation of the design idea into virtual and physical prototypes. The course design is built around the concepts of engineering sustainability, ethics, and professionalism helping students understand the linkage between engineering design and social and human factors. The course is lecture and laboratory based with a focus on experiential hands-on learning where the Course Learning Outcomes (CLOs) are achieved by means of PowerPoint slides, presentations, lecture and laboratory notes, class discussions and activities, teamwork, lecture and lab video recordings, hand sketching, and virtual prototyping via Computer-Aided Design (CAD) software (Solidworks). Student performance was evaluated through quizzes, reports, homework assignments, laboratory assignments, projects, midterms and final exams. To ensure effective communication between students, anonymous team member peer review and evaluation were incorporated. Continual improvement of the course design was achieved by modifying the course structure based on student feedback.

show abstract

Section: B Educational Objectives and Expected Outcomesmentioning

confidence: 99%

Section: A Typical Weekmentioning

confidence: 99%

First Year Engineering Design: Course Design, Projects, Challenges, and Outcomes

Hashim¹,

Tatarniuk²,

Harasymchuk³

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…In case a system configuration is not schedulable, based on counter-examples generated by Uppaal, we apply a re-engineering by relocating timed actions between tasks and rerun the analysis in the goal to identify whether a potential configuration leading the system to be schedulable can be derived. To maintain the separation of concerns, functional-architectural constraints [23] and architectural cohesiveness [24], we only consider the relocation of actions belonging to the tasks of the same application, i.e. located at the same core.…”

Section: Conceptual Design 31mentioning

confidence: 99%

Compositional Schedulability Analysis of Multicore Modular Avionic Architectures

Boudjadar¹

2018

JCP

View full text Add to dashboard Cite

This paper presents a compositional schedulability analysis of multicore modular avionic systems (IMA). It provides a fine grained description of the software architecture and behavior to reduce the over-approximation, and a holistic analysis to check schedulability while considering computation requirements and shared memory interference. The system is structured in terms of subsystems, encapsulating ARINC653 partitions, each of which runs on a processing core. The schedulability analysis is performed for each subsystem individually while accounting for the memory interference that would result if the core under analysis runs effectively alongside with the rest of cores. Thereafter, we introduce an architecting technique to relocate functions between tasks located at the same partition in case of non schedulability, to derive potential schedulable system configurations delivering the same functionality. Schedulability is formally analyzed using Uppaal model checker. Our evaluation results show that our compositional analysis technique consumes up to 95% less than regular analysis, in terms of analysis time and memory space. 1202 perfect memory access i.e., the memory is immediately available whenever an access request occurs (hits) [6]- [9]. Such an estimation of the WCET at task level is most likely under-approximating. We believe that estimating the execution time at a lower level of the granularity (e.g. function level) results in less underapproximation of the execution time. Thus, the more granular the behavior representation is, the more optimistic the WCET will be. The under-approximation difference between task and function levels could be non comparable and would increase drastically with fine grained description levels.The interference resulting from shared memories and communication means (buses, networks) is a determinant factor in the schedulability of component-based real-time system. The interference time is in fact related to the number of concurrent components and the bandwidth of shared resources. Accordingly, accurate schedulability techniques require a holistic analysis where both computation and memory interference/ communication have to be considered together [10], [5].A surge of progress has been achieved in the area of schedulability analysis of multicore systems through an intensive use of model-based settings and formal methods. However, due to the systems size in avionics, given by the integration of huge number of concurrent applications, the use of formal methods can end up in state space explosion. Different techniques have been considered to bypass the state space explosion and provide upper bound guarantees on the schedulability, we cite abstraction-based [11], compositional analysis [12] and incremental analysis [13]. In this paper, we introduce a model-based framework for fine grained modeling and formal schedulability analysis of multicore avionic (IMA-driven) systems with shared memories. The system is structured in terms of subsystems, encapsulating ARINC653 partitions, each ...

show abstract

“…There have been attempts to integrate specific HCI methods [10] A review of SE 'textbooks' reveals that any research in the area of HCI-SE integration has not permeated sufficiently in these books, and a clear-cut gap exists especially in the 'requirements' chapters [24] [25] [26]. However, considerable amount of scholarly research in SE discusses various methods to integrate HCI practices in SE.…”

Section: Gaps In Hci and Sementioning

confidence: 99%

An Autoethnographic Study of HCI Effort Estimation in Outsourced Software Development

Dighe

Joshi

2014

Human-Centered Software Engineering

View full text Add to dashboard Cite

A fair amount of literature has been published concerning the gaps between HCI and software engineering. However, most of it tends to look at the effects of these gaps rather than their causes. We argue that the use of autoethnographic methods would help us in identifying the root causes of these gaps and can bring us closer to finding potential solutions. In this paper, we focus on issues associated with effort estimation for HCI activities in three projects in three typical engagement models for outsourced software development projects in a mainstream IT company in India, namely Fixed Price model, Mixed model, and Time & Material model. We found that the HCI practitioner needs to negotiate her position with several members of the team, both within the vendor and client organisations. At times, a foot-in-the-door project turns out to be a footin-the-mouth project. At other times, it leads to inefficiencies and imbalance of work load. The autoethnographic approach led to reflexive thinking by the HCI practitioner, helping her to develop a deeper understanding of all aspects of a problem, and bringing her closer to potential solutions in some cases. The paper also brings to light several aspects of autoethnography as a method, which can influence effort estimation of HCI activities for future projects.

show abstract

Software Engineering: A Hands-On Approach

Cited by 5 publications

References 24 publications

First Year Engineering Design: Course Design, Projects, Challenges, and Outcomes

First Year Engineering Design: Course Design, Projects, Challenges, and Outcomes

Compositional Schedulability Analysis of Multicore Modular Avionic Architectures

An Autoethnographic Study of HCI Effort Estimation in Outsourced Software Development

Contact Info

Product

Resources

About