Research, Analysis, Architecture

I'm able to identify and understand project needs and quickly respond to changing requirements. My experience of working in Agile development practices has taught me how to work close to business people throughout the project, resolve queries in an efficient methodical manner and deliver working software in shorter timescales. I have knowledge in creating UML diagrams, flowcharts and user stories, and address at early stages non functional requirements like scalability, performance, testability and maintainability for the system.

I always try to design the architecture of a new system before I start any coding on it. I see architecture as the foundation with the core elements on which the rest must be built.

Firstly, I define the logical architectural layers. This depends on the complexity and nature of the application but usually if I see a large amount of data with multiple users and complex business logic I think of the application as having three layers.
1. Application or presentation layer.
2. Business logic or domain layer.
3. Data layer.

Next step is to address all the important functionalities on UML diagrams. My aim is to keep them short by highlighting only important issues and avoiding spending too much time. I draw only important classes showing their necessary attributes and operations. According to my experience, thinking of all the details when designing the system is usually worthless as only while coding you can discover that some aspects of the design are wrong.

Back-end development

For the server-side web development I use PHP. I have decent experience in object oriented programming in PHP and unless the project is very small I am using Zend Framework. ZF is my favourite framework because it provides lots of components that are extendable and a robust MVC physical structure (pattern).

My model's implementation is based on the concept to contain all the business logic and application data. It consists of domain objects and data mappers. Data Mappers are responsible for handling the transition of data from database to domain objects and vice-versa. There is a data mapper class for each domain object. Data mappers hide the database from the domain layer achieving the separation of business and storage logic. All exchanges between controllers and database are made by the data mappers.

MySQL is my choice of database in my applications and as interface for accessing it I use PDO. I focus on query optimisation and use transactions when is needed.

Finally, I have experience using SVN as version control system and my coding style is based on PSR coding standards.

User Interface Design, Front-end development

Wireframes is what I use for the development of static, low-fidelity interface designs. I find wireframes an easy and quick way to convert user stories (functional requirements) into a user friendly interface design. The flexibility and simplicity of wireframes allow me to focus on usability, information architecture and consistency, terms that play significant role on designing interfaces with great user experience.

Then comes the front-end development where I convert the interface design to an actual interactive interface. My favourite tools are: HTML5, CSS3, JavaScript(jQuery), AJAX. As front-end framework I use Bootstrap that helps me develop user friendly and modern interfaces, with clear and fun animations and interactions. And all that without having to focus on the development of UI components and layout structure. Instead, all I have to focus on is visual design enhancements, interactive design and consistency.