Inception
-
mean.io Web Development. -
PHP 5 using XAMPP (include Apache server and MySQL).
The development tools may change. It depends on the organization's demands. After writing the SRS file, we will know better and be sure about the tools we will use.
- Using the system without any knowledge with programming languages.
- Easy to use UI.
- Support CMS (Control Managemnet System)
- Cooperation between the team members.
- Coordinating expectation with the organization members.
- Learning about the organization vision and activities.
- Writing SRS (Software Requirements Specifications).
- System Design.
- Divide the project to small sub-projects (as modules).
- Determine a schedule for the project tasks.
- Subscription a team leader.
| Risk | Result | Suggested Solution |
|---|---|---|
| Changing Requirements Customer | Extension of time preparing a project. | Dealing in this case is to try to set up cooperation and coordination with customer expectations. |
| Team Substitution | Central personality can leave The project pose to a significant risk. | Not to gather all information at one member. |
| Wrong estimation of system size | Confusion of team and postpone date of completion of the project. | Setting up a SRS document and the start of practice after understanding system requirements in-depth. |
| Lack of punctuality | Postpone date of completion of the project. | Prioritizing the customer requirements. Assigning one team member to be team leader. |
| Unfamiliarity of the team with Development Tools | Postpone date of completion of the project, team Substitution | Distribution of tasks when all team members know to do their task and aware of the development tools he will use. |
- Git for version controlling.
- Brackets or WebMatrix or Eclipse PHP for editing code.
- Azure for distribution of the web app.
GoDaddy.
git/github.
- Programming practices and programming style conventions
- Comment conventions - comment everything which may be unclear.
- Indent style conventions - indentation is mandatory for easily reading the code.
- Line length conventions - limit of 80 chars per line.
- Naming conventions - use clear and understandable names.
- Programming principles
- Re-use code - don't repeat yourself
- KISS - Keep it Short and Simple / Keep it Simple, Silly.
- Worse is better - the idea is that quality does not necessarily increase with functionality. There is a point where less functionality ("worse") is a preferable option ("better") in terms of practicality and usability.
- Programming rules of thumb
- If it ain't broke, don't fix it.
- You aren't gonna need it - always implement things when you actually need them, never when you just foresee that you need them.
