Archive for the ‘Software Development Life Cycle’ Category

Business Requirements Vs System Requirements

March 12, 2011 3 comments
S No Business Requirements System Requirements


Business requirements are criteria in order for the software to be successful in meeting the user needs. Generally they focus on the “what” not the “how”. System requirements address the “how” associated with the business requirements (the “what”).


Business requirements concern the business. Software requirements concern the software solution to the “problem” stated in the business requirements.


Business requirements defined as benefits of the business desires. Software requirements define what the solution must do (or be) to assure the business requirements.


Business Requirements are goals and targets the business wants to achieve.

Examples:  No: 1 jobs consultancy company

System Requirements are technical goals

 Example: Implement web based job portal.


Implementation of QMS (Part 1)

October 2, 2009 Leave a comment

Define Quality Policy and Quality Objectives

Based upon the vision and mission statement of the organization, the top management will freeze the policy and objectives that need to be managed or maintain to meet its business goal. To be honest if prepared this with value, can measure the performance of the quality management system to great extent, but mostly in order to meet the requirements of the ISO 9001:2008, organizations establish this as a part, without any value or meaning. However it’s depends upon the individual or the organization who defines the same, since ISO 9001:2008 is the generic management system rather specific.

Constraints need to be considered while on working with policy and objective is what need to be done or what need to be managed to meet the business goals. For an example if we are going to define the policy for a startup company (of embedded systems of any particular products). Let us consider its vision statement is “Be leader in the network and embedded arena” and the mission statement will be “Deliver products on time with high quality”.

By combining both the vision and mission statement, came to the conclusion that the company want to maintain it’s delivery with high quality and on time for long run. So putting up this all in a line can say its policy as “Provide solutions & services or Products and services (supplier) that met the expectations of the customer (customer) in terms of Cost, Time and Quality”.

As defined the policy above, need to look into objectives to carry forward this policy. Quality Objectives is the measurable items at the end of the day to know where we are. From the above statement (policy), it’s clear that the measurable objects or items will be schedule, effort and quality (quality may be in terms of Defect Removal Efficiency, Customer satisfaction feedback & on time delivery).

Process for Bug Life Cycle

June 13, 2008 4 comments

Defect Management

June 11, 2008 Leave a comment

Process for Software Testing

June 5, 2008 1 comment

Process for Software Testing

Process for Software Development

May 23, 2008 Leave a comment

Process for Software Development




To provide general guidelines to carryout coding phase


Process Requirement:


1. Coding:


Entry Criteria:

Ø      Approved Technical Design Documents

Ø      Approved Project Plan

Ø      Coding Standards



Ø      Development process begins with the implementation of the Technical Design by the developer assigned.

Ø      Developers design and create source code following SDLC coding standards / guidelines provided by the Development Team Leader

Ø      Completed Code shall be compiled and the errors/ bugs shall be fixed.


Exit Criteria:

Ø      Compiled error free Code


2. Code Review and Unit Testing


Entry Criteria:

Ø      Compiled Error Free Code



Ø      Developer Team Leader Conducts walkthrough on code at formal or informal agenda based upon the review process.

Ø      Verifies with the checklist and RTM against the working product/code.

Ø      Unit Testing will be done and if any issues are identified then it as to get closed before release to the system or integration test


Records Retention:

Ø      Code Review

Ø      Unit testing issue report


Exit Criteria:

Ø      Updated baseline code (SCM Plan)


Process of Software / System Design (Part 2)

Process of Software / System Design



  1. To describe design goals set.
  2. To define system architecture and detailed design of the system.

Process Requirement:


1. System Architecture:


Entry Criteria: Approved SRS



Ø     On approval of SRS from internally and externally the team which is involved with design activity start to prepare HLD (High Level Design).

Ø     The same as to be review and approved by Project Head / manager

Ø     Refer:


Record Retention: HLD


Exit Criteria: Approved HLD


2. Detailed Design Document:


Entry Criteria: Approved HLD



Ø     On approval of High Level Design, the team involve in the low level design start to prepare (LLD)

Ø     LLD involves web page design and Usability (Navigation)

Ø     The same as to be review and approved by Project Head / manager


Record Retention: LLD


Exit Criteria: Approved LLD


3. Validation


Entry Criteria: HLD & LLD



Ø     Conducting informal reviews and walkthroughs or inspections of the detailed software and data base designs.

Ø     The Critical Design Review (CDR) that completes the software detailed design phase.


Record Retention: HLD & LLD


Exit Criteria: Approved HLD & LLD