jose/LogSource
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

image
Some checks are pending
Deploy Arise to html branch / Deploy Arise (push) Waiting to run
Details

Browse source
This commit is contained in:
Jose Falanga 2025-10-13 18:41:21 -03:00
parent 4f3266cb9f
commit 7d4b47382a
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
arise-source/rehosted/vertical-vs-horizontal/index.md
View file

@ -24,7 +24,7 @@ Now, you and I well know in the real world there are often constraints and exter
My diagram-fu is weakened when working on my laptop’s track-pad, but the diagram below still serves to illustrate a few key points. My diagram-fu is weakened when working on my laptop’s track-pad, but the diagram below still serves to illustrate a few key points.
![[./graph.jpg]] ![[graph.jpg]]
First, components of the game (Single Player, Tutorial, etc) differ in the amount of work and are so represented by different width blocks. As each HL is complete quality goes up. The VS sits on top of the HL and therefore is elevated in quality by it. In this diagram two vertical slices are created for two different portions of the game; single player and multiplayer. You can see that the slices themselves are of different widths. This represents the amount of the component the VS is meant to demonstrate. For example the single player VS may only be showing off one portion of one campaign mission, whereas the multiplayer VS might be demonstrating nearly fully functional gameplay on a variety of maps. Also note that each slice was started during a different HL iteration. Had the VS for single player began on the 3rd HL iteration it would have achieved a higher quality level. First, components of the game (Single Player, Tutorial, etc) differ in the amount of work and are so represented by different width blocks. As each HL is complete quality goes up. The VS sits on top of the HL and therefore is elevated in quality by it. In this diagram two vertical slices are created for two different portions of the game; single player and multiplayer. You can see that the slices themselves are of different widths. This represents the amount of the component the VS is meant to demonstrate. For example the single player VS may only be showing off one portion of one campaign mission, whereas the multiplayer VS might be demonstrating nearly fully functional gameplay on a variety of maps. Also note that each slice was started during a different HL iteration. Had the VS for single player began on the 3rd HL iteration it would have achieved a higher quality level.