Tag Archives: SRS Template

8 Ways to Fine Tune your PHP Programming

August 18, 2010   Shubhamoy   5 Comments
PHP
Today I am going tell you some methods which will help those learning PHP & also those who are planning to start learning PHP. For those who are planning to learn PHP, I just want to say that every programming language has the same logic only the grammar (coding style or structure) changes.

1. Always follow the standard method of coding e.g. writing a single if statement without the curly braces {} works but always use them since this will result in easy updating in future.

2. Use comments to result in better understanding of the code. And also saves a lot for another programmer.

3. In case of any doubt, always refer to the online PHP Manual since it has a unique feature of adding the user comments which may provide better understanding of the issue. And also saves a lot of time since it minimizes the risk of any possible bug in the final program.

4. Use an IDE for PHP development just to enhance your programming skills and will also save a lot of time. Like NuSphere PhpED IDE(http://www.nusphere.com/). Even you can try Wamp Server or XAMPP for running your PHP scripts at your end.

5. Try to reduce the HTTP Request of files. It will in turn reduce the server load & increase the processing speed.

6. Always write a detailed list of things you expect your program to do. In technical terms, a Software Requirement Specification (SRS). So that you clearly know what you are going to do? Read this post for Writing SRS.

7. Use PHP Cheat Sheet or Reference Sheet while coding just to minimize the risk of errors. PHP Cheat Sheet is a collection of all the syntaxes, structures, etc.

8. Always give credit if you borrow some idea or code from someone else. Since the most important thing is that we should not be only a programmer but a good programmer & for that we must show respect towards the community of programmers. This result in worldwide acceptance & support for your work.

Let us hope these points will help you in honing your skills in PHP.

Note: Few points are also applicable to other programming languages

Update: Beginning PHP5, Apache, and MySQL Web Development can be used as a desk reference for a ready reference.

Shubhamoy

An engineer by chance and a blogger by choice. Love to share my knowledge with the masses. My main focus is always on open source technologies and latest gadgets. This blog provides me the platform to cherish my passion.

Website - More Posts

Read More

Software Requirements Specification (SRS) Template

June 24, 2009   Shubhamoy   1 Comment

What is SRS?

Software Requirements Specification(SRS) is basically an organization’s understanding (in writing) of a customer or potential client’s system requirements and dependencies at a particular point of time (usually) prior to any actual design or development work. It’s a two-way insurance policy that assures that both the client and the organization understand each other’s requirements from every perspective at a given point of time.

Benefits of a Good SRS

  • Establish the basis for agreement between the customers and the suppliers on what the software product is to do.
  • Reduce the development effort.
  • Provide a basis for estimating costs and schedules.
  • Provide a baseline for validation and verification.
  • Serve as a basis for enhancement.

What should the SRS address to?

  1. Functionality: What is the software supposed to do?
  2. External Interfaces: How does the software interact with people, the system’s hardware, other hardware, and other software?
  3. Performance: What is the speed, availability, response time, recovery time of various software functions, etc.?
  4. Attributes: What are the portability, correctness, maintainability, security, etc. considerations?
  5. Design constraints imposed on an implementation. Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environment(s) etc.?

What are the characteristics of a good SRS?

A SRS should be:

a) Correct
b) Unambiguous
c) Complete
d) Consistent
e) Ranked for importance and/or stability
f) Verifiable
g) Modifiable
h) Traceable

Difference between System Specification and Software Specification:

Very often we find that companies don’t understand the difference between System Specification and Software Specification. Important issues are not defined up front and Mechanical, Electronic and Software designers do not really know what their requirements are.

The following is a high level list of requirements that should be addressed in a System Specification:

  • Define the functions of the system
  • Define the Hardware/Software Functional Partitioning
  • Define the Performance Specification
  • Define the Hardware/Software Performance Partitioning
  • Define Safety Requirements
  • Define the User Interface (A good user’s manual is often an overlooked part of the System specification. Many of our customers haven’t even considered that this is the right time to write the user’s manual)
  • Provide Installation Drawings/Instructions
  • Provide Interface Control Drawings (ICD’s, External I/O)

Here is the SRS Template by Karl Weigers

Download SRS Template (Source – www.processimpact.com)

Update:

Shubhamoy

An engineer by chance and a blogger by choice. Love to share my knowledge with the masses. My main focus is always on open source technologies and latest gadgets. This blog provides me the platform to cherish my passion.

Website - More Posts

Read More