# \*\*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&#x20;

6\. think layers and think of the users&#x20;

CSE2

using the rapid application development

-> system boundary&#x20;

-> 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&#x20;

-> structuring the needs&#x20;

-> line of events&#x20;

-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&#x20;

-> divide cases to the objects (functions to locations-users)&#x20;

-> objects to processes&#x20;

-> implement and unit test each step (class)

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

CSE4

here using a code example&#x20;

implementing in PHP

implementing in java

-> packaging the implementation&#x20;

CSE5

-> unit testing

-> unit case testing

-> system testing

-> test configurations&#x20;

-> test corner-cases, unlikely, boundary-case&#x20;

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

CSE6

-> create a road map or a tutorial&#x20;

-> prerequisites&#x20;

-> guidelines&#x20;

-> expressing the system in terms of workers
