When you start a new design/dev project, what is the very first thing you do?

1- gather the requerments
2- analyze them
3- set up a progect plan identify the required resources-4
5- allocate resources there are a lot of steps to do here are just a sample

It depends on the Software development models(SDM) you want to use: Each SDM has different steps.
The waterfall model e.g.
shows a process, where developers are to follow these phases in order: 1.Requirements specification (Requirements analysis) 2.Software design 3.Implementation and Integration 4.Testing (or Validation) 5.Deployment (or Installation) 6.Maintenance Each model you choose has its own software development life-cycle (SDLC).

1.
Collect information as much as i can about business requirements and what this project for: i may not given the full information about it yet, or business requirements are in process, so i try to build main lines of the project and understand where this project going and what will be accomplish.
2.
Build a sketch for the project: its not a design its just a sketch to draw main lines i need to build the project.
3.
I see what my part will be on this project: Am i responsible for the design level, or development level, or both? This will tell where i should start.

Very good question.
The first thing I believe is the "Start up" phase.
Before doing anything you need to put in place 2 important things: 1.
Setting up the Project organization: this means identify stakeholder and conduct a quick stakeholders analysis.
Identify sponsors and their motives, assign a project manager....etc.
2.
Preliminary Business Case: initial expected cost, time line, what's the purpose of the project and what are benefits and dis-benefits.
Why is that? some project shouldn't even start.
If you've a preliminary business case where you can weight expected benefits against dis-benefits, cost and time line, you might not even want to take that project.
As for stakeholders,usually it's people who make a project success or fail.
If you don't know who are your stakeholders, how they are affected and affecting the project, you're putting your project in a big risk.
It's very important to identify your sponsor and you need to make sure he is committed to provide resources and support.
In case he is not available you need to know who does he delegate to take this role on his behalf.

1.
determine the entities i have in business logic and the relations between entities 2.
put a db design and code design 3.
implement db 4.
implement code as follow -three layers : 1.
implement db layer 2.
implement business logic layer 3.
implement UI layer

For me I'd look at an existing system if there is any and understand how it works, the gather the requirements and do some analysis then start the design and after that the implementation..

1.
ENVISIONING:- The very first thing to do in a development or a design project in ICT is the ones own vision of a new or existing plan/project by keeping in mind the risk of devlop/design a new or to update an existing.
Meets the business needs of the organization.
2.
Provides a clear plan to achieve a goal on time, within budget, with all features and functions initially specified: PLANNING Developing/ Designing Stabilizing Deploying

The very first thing to do is to know what project is all about, what type of service is needed from the team, when is the target date or deadline of completion of the project, and they must provide all the details to avoid panicking, much better if they will provide necessary details from 2 weeks before the project will starts (or before the deadline), and I believe it will be a success project for both sides.

It depends on the role that I stand on: - If I'm in business manner, I'll look on the value of this project to the company and if it will succeed or not, ...
- If I'm in development manner, I'll look on requirement, check if it enough or not, check the resources and submit a full plan for that project.

75% UNDERSTANDING THE PROBLEM, SEE IF THERE IS SOMETHING OUT THERE EXIST THEN START A DESIGN CONFIDENTLY!

in one word...
Feasibility Study , requirements..
after that everything go on..