> For the complete documentation index, see [llms.txt](https://samir-omer.gitbook.io/build-a-basic-computer-system-one-block-at-a-time/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://samir-omer.gitbook.io/build-a-basic-computer-system-one-block-at-a-time/the-book-index-a.k.a-the-road-map.md).

# \*\*The Book index\*\*  a.k.a the road map

CSE1

1\. must meet the needs

2\. immediately served

3\. future needs

4\. read-off and considerable experience

5\. collecting inputs 

6\. think layers and think of the users 

CSE2

using the rapid application development

-> system boundary 

-> describe the role of each analysis object and how it will interact with the system

-> goal is to look for the variability in the system 

-> structuring the needs 

-> line of events 

-think of each functionality, limited dependencies, and task and group them all into a subsystem or service

-> quality of analysis to meet (match) the needs of the system

-> enable the brainstorming sessions with the client if needed

-> thinking about things in a sequence (advice numbering)

CSE3

-> creating an abstract or a framework

-> supply the client's expectations 

-> divide cases to the objects (functions to locations-users) 

-> objects to processes 

-> implement and unit test each step (class)

->the process of design might differ from an engineering approach

CSE4

here using a code example 

implementing in PHP

implementing in java

-> packaging the implementation 

CSE5

-> unit testing

-> unit case testing

-> system testing

-> test configurations 

-> test corner-cases, unlikely, boundary-case 

-> test the system/service as if you are using it

CSE6

-> create a road map or a tutorial 

-> prerequisites 

-> guidelines 

-> expressing the system in terms of workers