8. HOW DOESTHE SUCCESSFUL
SYSTEM DEVELOPMENT FUNCTION?
The Essence of Software
Engineering:
The SEMAT Kernel
A thinking framework in the
form of an actionable kernel
http://www.omg.org/news/meetings/tc/berlin-13/special-events/essence-pdfs/S4-Elvesaeter.pdf
9. UX AS AN OPPORTUNITY,
AS A SOLUTION,
AS A CASE, PROJECT, PROCESS, CULTURE.
Stakeholders Level: Customers and
Needs in a very broad sense.
Solution Level: Requirements and
Deliverables
Endeavour Level:Who is working,
How they work and What they do.
Using system. Customer.
Enabling system. Endeavour.
System of interest. Solution.
10. STAKEHOLDERS ARE ANYONE WHO
HAS A CONCERN ABOUTTHE SYSTEM
Stakeholders are forming system views and
picking up a system of interest from
the Holon of Systems of systems.
14. • Goals are accomplished either by completing
some action (tasks) or
• Stand as a passive requirement for system aspect
• Sometimes they can be addressed but not
accomplished (soft goals)
• Some goals can conflict, contribute to a high-level
goal or be subject to a new pain
17. FORTHE ENGINEERING PROJECTS,
MOST IMPORTANTVIEWS ARE
• functional view
how it works
• modular view
what it contains
• placement view
where it is placed
18. FUNCTIONALVIEW CONCISELY
SHOWSTHE WORKFLOW
• Simplified BPMN notation
• Each block is a task
• Similar to Use Case
description
• In a concise way where
one can visually see
outcomes and flows
20. THE CENTRAL QUESTION
WHAT DOES USER NEED TO
COMPLETE THE PARTICULAR TASK?
ANOTHERTASK,A PARTICULAR INTERFACE
ELEMENT OR SPECIFIC CONTENT?
21. MODULES OR
CONTENT STRATEGY
• Modules view describes what content element do we have.
• Content structure, content types, hierarchy, usages, aggregations.
• What interface elements do we need?
• What are content specifications, size, visibility, type?
• UI structure from primitives (atomic design) to complex widgets.
• Boundary content cases (Too many, too long/short, absent, error).
25. PLACEMENTS
• Now we can pack the
content required to
accomplish specific
functional chunks to
wireframes, mockups or
code.
• Depending on device,
UI pattern fit, functional
requirement or navigation.