Aqua Utopia|海の底で記憶を紡ぐ
Cosmic Funnies
Sweet Seals For You, Always

Janaina Medeiros
let's talk about Bridgerton tea, my ask is open

No title available
Fai_Ryy
he wasn't even looking at me and he found me
Today's Document
d e v o n
Jules of Nature

tannertan36

Discoholic 🪩

PR's Tumblrdome
🩵 avery cochrane 🩵
sheepfilms
wallacepolsom

⁂
Game of Thrones Daily
almost home
seen from United States

seen from United States

seen from United States
seen from United States

seen from Italy

seen from Malaysia
seen from South Africa

seen from Canada
seen from United States

seen from United States

seen from United States

seen from United States
seen from United States
seen from United States

seen from United States
seen from United States
seen from United States

seen from Türkiye
seen from Canada
seen from United States
@corvuschamber-blog
Project Processes
The Project Processes are used to establish and evolve project plans, to execute the project plans, to assess actual achievement and progress against the plans and to control execution of the project through to fulfillment.
Individual Project Processes may be invoked at any time in the life cycle and at any level in a hierarchy of projects, as required by project plans or unforeseen events. The Project Processes are applied with a level of rigour and formality that depends on the risk and complexity of the project.
ISO/IEC 15288:2008, p. 24
Modeling, Simulation, and Prototyping
Models represent the essential characteristics of the system under development, the environment in which the system operates, and/or interactions with enabling systems and interfacing systems.
Types of Models and Simulations
Systems Engineering models and simulations typically reflect four paradigms:
Functional analysis with specialty, environmental, and interface engineering models attached
Modern Structured Analysis/Process for System Architecture and Requirements Engineering
Systems Modeling Language (SysML™)
Context‐sensitive systems, also called complex, adaptive systems, which modify their internal gradients, architecture, and content depending on interactions with their environment.
Models may be made up of one or several of the following types:
Physical (e.g., Wind Tunnel model, Mockups, Acoustic model, structural test model, engineering model, prototypes)
Graphical (e.g., N2 charts, Behavior diagrams, Program Evaluation Review Technique [PERT] charts, Logic Trees, blueprints)
Mathematical (deterministic; e.g., Eigen value calculations, Dynamic motion, Cost)
Statistical (e.g., Monte Carlo, Process modeling, sequence estimation)
Implementation Process
The purpose of the Implementation Process is to realize a specified system element.
This process transforms specified behavior, interfaces and implementation constraints into fabrication actions that create a system element according to the practices of the selected implementation technology. The system element is constructed or adapted by processing the materials and/or information appropriate to the selected implementation technology and by employing appropriate technical specialties or disciplines. This process results in a system element that satisfies specified design requirements through verification and stakeholder requirements through validation.
ISO/IEC 15288:2008, p. 42
Causal Loop diagram Example : Gold Mining Investment in Peru - using VUE
Causal Loop Diagrams Software
-Open Source
-Intuitive Interface
Vensim :
-Link: http://vensim.com/
Stella / iThink :
-Link: http://www.iseesystems.com/Softwares/Business/ithinkSoftware.aspx
Alternatives
Visual Understanding Environment (VUE) :
-Link : http://vue.tufts.edu/
Microsoft Visio:
-link: http://office.microsoft.com/en-us/visio/
Causal Loop Diagrams
System behavior in system dynamics is modeled by using feedback (causal) loops, stocks and flows (levels and rates), and the non-linearities created by interactions among system components.
In this view of the world, behavior over time (the dynamics of the system) can be explained by the interaction of positive and negative feedback loops.
The models are constructed from three basic building blocks: positive feedback or reinforcing loops, negative feedback or balancing loops, and delays. Positive loops (called reinforcing loops) are self-reinforcing while Negative loops (called balancing loops) tend to counteract change. Delays introduce potential instability into the system.
Peter M. Senge (1990), The Fifth Discipline: The Art and Practice of the Learning Organization, Doubleday Currency, New York.
Architectural Design Process
The purpose of the Architectural Design Process is to synthesize a solution that satisfies system requirements.
This process encapsulates and defines areas of solution expressed as a set of separate problems of manageable, conceptual and, ultimately, realizable proportions. It identifies and explores one or more implementation strategies at a level of detail consistent with the system’s technical and commercial requirements and risks. From this, an architectural design solution is defined in terms of the requirements for the set of system elements from which the system is configured. The specified design requirements resulting from this process are the basis for verifying the realized system and for devising an assembly and verification strategy.
ISO/IEC 15288:2008, p. 40
Sources of Requirements
Requirements analysis, like the set of SE processes, is an iterative activity in which new requirements are identified and constantly refined as the concept develops and additional details become known. These are analyzed, and deficiencies and cost drivers are identified and reviewed with the customer to establish a requirements baseline for the project.
INCOSE Systems Engineering Handbook v. 3.2.2
Definicion de Valor
"El Valor es una medida de la importancia percibida (por ejemplo, beneficio dividido entre coste) de un producto o servicio especifico por parte de un cliente, y potencialmente otros stakeholders y varía en función de :
La eficacia de un producto para satisfacer la necesidad del cliente
La importancia relativa de la necesidad a ser satisfecha
La disponibilidad del producto en relación a cuando este es requerido
El coste de adquisición para los clientes. "
McManus, Hugh L., “Product Development Value Stream Mapping Manual,” LAI Release Beta, MIT, April 2004
System Requirements : Iterative and Recursive
Iteration : When the application of the same process or set of processes is repeated on the same level of the system, the application is referred as iterative.
Recursion: When the same set of processes or the same set of process activities are applied to successive levels of system elements within the system structure, the application form is referred to as recursive.
ISO/IEC CD 29148, Requirements Engineering
Waste in Product Development
The Lean Advancement Initiative (LAI) classifies waste into seven categories:
Over-Processing
Waiting
Unnecessary Movement
Over-Production
Transportation
Inventory
Defects
McManus, Hugh L, “Product Development Transition to Lean (PDTTL) Roadmap,” LAI Release Beta, MIT, March 2005
Waste:
"The work element that adds no value to the product or service in the eyes of the customer. Waste only adds cost and time."
Womack, James P., and Daniel T, Jones, Lean Thinking, New York: Simon & Schuster, 1996
Definition of Value
"Value is a measure of worth (e.g., benefit divided by cost) of a specific product or service by a customer, and potentially other stakeholders and is a function of:
The product's usefulness in satisfying a customer need
The relative importance of the need being satisfied
The availability of the product relative to when it is needed
The cost of ownership to the customer. "
McManus, Hugh L., “Product Development Value Stream Mapping Manual,” LAI Release Beta, MIT, April 2004