index brief

CSE1 - CSE2

**Practice Identifying Business Problems**

Participants will practice identifying business improvement opportunities by studying the procedures and identifying their goals and purposes to design systems that will efficiently achieve their goals. Participants will also study modules, architecture, components, and their interfaces and data for a system based on the program's thematic and industry requirements.

**Architecting The Data**

Participants will practice structuring data so that it can be used effectively using general SQL language, with the understanding of data types, relationships, functions, and operations.

**Programming and Coding**

Participants will learn how to think about instructions for performing tasks and to transform those instructions into a written language that a computer can understand such as Python or C++.

when we talk about system outline base requirements are the first step

most of the treatment goes to Human-manager skills and needs

most of the requirements can be obtained by seeking the needs

of most important users and entities to the least

then try to describe them.

note -> starting with only the core functionality

comparing old systems or following up with the old current system day by day at least for a week. (system process)

planning an outcome a prototype

to show and discuss with the client (making a communication common island )

to get more data (form, pages, reports).

CSE1-CSE6

capturing requirements focusing on variability(use case engineer `plus` customer)

performing the analysis(user case designer)

designing the component system(subsystem engineer)

implementing the component system(subsystem engineer)

testing the component system(tester)

final packaging of the component system(components system librarian)