PPT W8
PPT W8
Week – 8
Digital Business System Development
LEARNING OUTCOMES
• Demonstrate the practical elements of e-business with selected
platforms and technologies, in a customized business model.
OUTLINE
• Analytics for digital technology projects.
• Process modeling.
• Data modeling.
• Design for digital technology projects.
• Design thinking.
• Roadmap.
• Focus on security design for digital businesses.
• Change management.
Analytics for digital technology projects
Requirement Analysis
• Digital technology projects, like other information system projects,
require an analysis stage before starting their implementation.
• What the user needs (user requirements) must be explored in depth
first so that what is built will be exactly as expected.
Requirement Analysis
• Information is an agent of coordination and control in organizations
and businesses, therefore the flow of information must be treated
appropriately for optimal results.
• Analysis carried out in digital technology projects must be user-
centric.
Process Modelling
Process Modeling Stages
Data Modelling
Traditional Data Modeling
• Identify the entities involved.
• Identify the attributes of each entity.
• Identify the relationships between entities and their characteristics.
• Using ERD
Modern Data Modeling
• Denormalization
• Aggregation
• Dimensionality reduction
Design for digital technology projects
Microservices Architecture
• Microservices architecture by Martin Fowler (2014) is defined as a
special way of designing a software application as a set of services
that can be implemented independently.
• In this microservices architecture, the software is divided into small
service features that can be uninstalled like lego.
Microservices Architecture
• Modularization of services.
• Organized according to business capabilities.
• Focus on products, not projects.
• Smart endpoints, dumb pipes.
• Decentralized governance.
• Decentralized data management.
• Infrastructure automation.
• Not error-proof.
• Evolutive design.
Design thinking
Design Thinking
Roadmap
The Important of Roadmap
• Features develop along with business dynamics, new services
continue to appear, services that are no longer profitable have to be
closed or modified.
• The architecture is also constantly evolving.
• Because the development and changes of these features require
effort, time and cost, it is necessary to be clear to all parties about the
future map of system development.
The Important of Roadmap
• Set goals
• Gather input
• Create a theme
• Prioritize themes
• Visualize and share
• Revisions and updates
2. Jelassi, Tawfik. Martinez-Lopez, Francisco J. (2020). Strategies for e-Business: Concepts and Cases on Value Creation and Digital
Business Transformation. 4. Springer. ISBN: 978-3-030-48949-6.
3. Katsov, I. (2012, October 16). NoSQL Data Modeling Techniques. Highly Scalable Blog.
https://highlyscalable.wordpress.com/2012/03/01/nosql-data-modeling-techniques/.
5. Gibbons, S. (2018, January 14). Empathy Mapping: The First Step in Design Thinking. Nielsen Norman Group.
https://www.nngroup.com/articles/empathy-mapping/.
7. World Leaders in Research-Based User Experience. The 6 Steps to Roadmapping. Nielsen Norman Group.
https://www.nngroup.com/articles/roadmapping-steps/?lm=design-thinking-learners-journey&pt=article.