0% found this document useful (0 votes)
1 views11 pages

Gash

Uploaded by

hafizyt2014
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1 views11 pages

Gash

Uploaded by

hafizyt2014
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Article Summary


Group Name ID
1. Soreti Tarekegn
2. Abdulhafiz Mohamed
3. Fuad Getachew
4. Dano Dula 1303234
Introduction


Tittle: Software Engineering Education: Towards
Ethical,
Reliable,andBeautifulSoftware
Overview: This study explores an innovative
approach to teaching software engineering at the
graduate level.
Purpose: The course aims to create software that
is not only functional but ethical, reliable, and
aesthetically pleasing.
Student Impact: Positive feedback on the course's
emphasis on real-world applications and ethics.
Six Key Dimensions


1. Restate Software Engineering Goals: Shift
focus to ethical, reliable, and beautiful software.
2. Software as a Service (SaaS): Emphasize
modern software development using
microservices.
3. Architectural Principles: Use proven design
principles and modular structures.
4. Sound Design Principles: Employ effective
modeling and design strategies.
Ethical, Reliable, and Beautiful
Software

 Ethical: Software must respect user privacy,
avoid unwanted monitoring, and use resources
responsibly.
 Reliable: Handles failures safely, adapts to
user environments, and provides consistent
performance.
 Beautiful: Easy to use, aesthetically pleasing,
and designed for diverse users. Beauty
includes both UI and underlying code.
Software as a Service (SaaS)


Software as a Service (SaaS)
 What is SaaS?: A modern model delivering
software via the web or apps.
 Core Elements:
 Micro-services: Modular components that
enhance adaptability.
 Prototyping: Use prototypes to validate designs
quickly.
 Reuse & Extensibility: Focus on creating
reusable and easily adaptable software
components.
Software Architecture and D-
design:

Proven Architectural Principles
Key Elements:
 Componentization: Break software into
modular components.
 Architecture Views: Use multiple
perspectives (logical, physical) for better
understanding.
 Design Focus: Prioritize ease of
maintenance, reliability, and cohesion.
Design Principles & 6S Checklist


 Modeling Properties:
 Completeness: Include all required elements.
 Consistency: Ensure no contradictions in design.
 Correctness: Meet specifications accurately.
 6S Checklist:
 Site: Proper placement of components.
 SOLID & SOFA: Follow object-oriented best practices.
 Style: Maintain code style and clarity.
 Sign-off: Peer review to ensure quality.
Rapid Multi-Modal Prototyping


Prototyping Levels:
 Low-Fidelity: Simple paper sketches or
wireframes.
 High-Fidelity: Detailed digital designs with
user feedback.
 Code-Based: Functional prototypes for real
testing.
Goal: Speed up the design process and refine
based on user input.
Incremental, Iterative, Real-world
Project


Objective: Solve a practical problem with
real-world implications.
Project Criteria:
 Address a real-world issue.
 Use SaaS architecture.
 Include diverse databases and
programming languages.
Example Project: National Vaccine Registry
developed during COVID-19.
Lessons Learned


 Holistic Approach: Emphasizing ethics,
reliability, and aesthetics in software.
 Hands-On Learning: Incremental
problem-solving enhances real-world skills.
 User Trust: Building reliable systems
fosters confidence and user loyalty.
Conclusion


The course has been well-received, with students
appreciating the focus on ethical, reliable, and beautiful
software, as well as clean and efficient architectures.
The integration of IEEE SWEBOK and modern practices
has been particularly valuable.
Future plans include expanding project diversity,
enhancing software reuse, focusing on software-
intensive products, and integrating AI, diverse user
needs, and sustainability.
Additional data will be collected to further refine the
course.

You might also like