 DEVELOPMENT METHODOLOGY

RENAISSANCE Software will follow a Standard Software Development Model, coupled

with both scheduled and unscheduled interim builds to support of early interfaces
tests and establish empirical performance numbers.

The lifecycle model can be used as it is or tailored for any software development
project. RENAISSANCE Software may also follow Iterative software Development
Model for the project which includes conscious modifications to several stages,
including modification to the number and types of expected documents. The software
development methodology to be utilized will decided once the project enters into the
requirements specification phase.

The software will be maintained in an environment identical to the development

environment. Software and system-level change requests will control changes to the
software, and regression testing will be performed when changes are made.

The standard implementation software development methodology of RENAISSANCE

Software consists of the following tasks:

 SYSTEM ANALYSIS & DESIGN

The analysis and design approach used for the Employee Management System will
be structured analysis and Design.

The following sections detail the analysis and design processes selected for the
Employee Management System project.

 REQUIREMENTS ANALYSIS

Requirements analysis on the Project System will consist of the following process but
not limited to:

1. Identify system-level requirements and interface control requirements applicable

to software.

Private & Confidential

2. Identify the external interfaces to the software and illustrate in a context diagram
using the analysis tool.
3. Define the external interface data elements in a data dictionary.
4. Define the top-level software components based on the functionality.
5. Define a rationale and verification strategy for each requirement as it is written.
The rationale will include traceability to upper level requirements where applicable.

Software requirements will be documented in a Software Requirements Specification

(SRS). The requirements analysis phase will be considered complete
When the following criteria have been met:

1. Each requirement has a documented rationale and/or upper-level source

requirement and a verification Strategy.
2. The Team project Manager /Team Lead, have reviewed the requirements.

The entire requirements analysis phase will be considered complete when the SRS
has been baseline and signed off.

 DESIGN

Design of the System will consist of the following process but not limited to:

1. Construct structure charts, flowcharts, and/or state transition diagrams, as

appropriate.
2. Include narratives, timing diagrams, memory maps, block diagrams, and other
illustrations as appropriate to complete the design of the System.

The software design will be documented in a Software Design Specification (SDS).

The design phase will be considered complete when the following criteria have been
met:

1. Traceability for the design elements been documented in the requirements

traceability matrix.
2. The Software Project Manager/Team Lead, have reviewed the design.
3. The design has been reviewed by peer review, if applicable, and any required
changes incorporated.

Private & Confidential

  SOFTWARE DEVELOPMENT, TEST, AND INTEGRATION.

The project will include development of new code (or modify reused code) if needed,
unit test, integrate, and document software While reused code will not be expected
to conform to a single coding standard, changed source code must be supplemented
with sufficient new comments and standard code headers to meet commenting
provisions of the coding standard and to promote understandability.

 SYSTEM QUALIFICATION TEST AND DELIVERY

The project will conduct Qualification Testing according to Qualification Test Plans
and Procedures, and document results in a Test Report. After successful Software
Usability Review (SUR), the software will be ready for installation.

 SUPPORT INSTALLATION AND USE.

The Project team will provide support to software installation, acceptance testing,
and user operation.

DEVELOPMENT METHOLODOLOGY

1. Software
Requirements
2. Software
Design
3. Software Unit
Development, Test,
Integration
4. System
Qualification
Test and
Code Delivery 5. Support of
Installation & Use

Project Planning and Oversight

Software Configuration Management

Software Quality Assurance

Private & Confidential

  PROJECT ORGANIZATION

Prolific project management principles shall be followed throughout the project life
cycle. Software development activities shall be planned in advance and monitored
carefully throughout the life cycle. RENAISSANCE Software will imply the following
project management methodology for the Project.

 PROJECT RESOURCE PLAN

The RENAISSANCE Software’s project team will include of junior and senior level
software engineers for software specification, development, and testing;
management and quality assurance representatives for oversight.

 PROJECT MEETINGS AND REVIEWS

Meetings and reviews will be held to track progress, make changes to the software
development plan, identify risks, and track project metrics after every one week.
Project Managers, Team leads along with the other team members will review the
project progress after every one week/two weeks.

 PROBLEM ESCALATION

Problem situations (if any) are to be resolved in an orderly and timely manner. The
severity of the problem will dictate the persons responsible for resolving and the
time period allowed for sufficient resolution. If no decision is made about the conflict
in the amount of time stated, the project manager will proceed forward, but will
notify the System Owner and Technical Monitor to cater the impact of risk.

 PROJECT TRACKING

In accordance with procedures, the following tracking data will be internally collected
and analyzed for software activities. Project tracking consists of the accumulation of
tracking information and the reporting of the tracking data in project reviews.
Tracking data will be collected to monitor the performance and progress of the
project during weekly/monthly software project meetings. This data will be
documented and presented at weekly management review meetings. This data
includes:

 Risks that may affect cost and schedule

 Hours spent on each task

Private & Confidential

  Budget spent on each task
 Estimated hours until completion on each task
 Estimated cost at completion of each task
 Cost variance
 Milestones achieved

In addition to in-progress tracking, several metrics will be documented for newly

completed tasks and reviewed at weekly/monthly management review meetings.
When baseline items are completed, the size of the item will be recorded .When
milestones are met, the actual date when the milestone is met will be recorded.
When a task is completed, the following data will be recorded for the task:

 Actual hours to complete the task

 Actual cost to complete the task
 Schedule variance (difference between actual and planned days to complete),
and
 Cost variance (difference between actual and planned cost to complete).

 QUALITY ASSURANCE AND TESTING

The intent of QA is to objectively verify adherence of project activities to the

software development process surveillance.

QA shall be performed module and task wise. Errors/Bugs if any will be discussed in
the management review meeting and problem escalation will be documented so that
it’s properly resolved and corrective action plan is implemented. These reviews will
validate readiness to proceed to the next development phase.

The Project will apply a quality assurance process to provide adequate assurance
that the software projects and processes in the project life cycle conform to their
specified requirements and adhere to their established plans.

The Quality Assurance Team will prepare and execute a project SQA Plan containing
quality standards, methodologies, procedures, tools, resources, schedules, and
responsibilities for ensuring quality checks at every phase of the development.

 PLATFORM/TOOLS:

Tools that will be used for the project include, but are not restricted to:

Private & Confidential

Tools Purpose
MS Project Project Management
MS Visio Software Designing
Erwin Database Designing
MS Word Documentation

Tools (Development) Purpose

PHP Software Development
MY SQL Database

 PROJECT SIZE ESTIMATES

Any project will be determined by analyzing the project requirements that are known
to date. This included the current project objectives and information gathered during
the pre sales analysis phase of this project and documenting the requirements,
concept of operations, integration and interfacing requirements and the cross-
reference matrix. Should there be a change in requirements, the size estimates and
their respective impact on cost will be revised and reconsolidated with the mutual
consent of both the parties

 TIME ESTIMATES

Renaissance Technologies will work 6 days a week and 24 days in a month. Our
System Analyst will determine the total time for the proposed project after studying
the project.

 TRAINING

Project training will be provided by formal courses/facilitated video/ informal “chalk

talks,” or on-the-job training. We would recommend that the training shall be
conducted at a centralized location. The training days will be decided mutually and
will be informed to the concerned. However RENAISSANCE Software recommends
conducting three days of training for the project. However the days can be increased
with the mutual understanding terms & conditions contract.

Private & Confidential

  PROJECT DELIVERABLES

 Project Documentation
 Project Code

 ASSUMPTIONS

a) The deliverables mentioned in the proposal will be based on an initial study only.
On the completion of the Requirement Definition Report, the above
implementation duration and user deliverables will be re-evaluated, and changes,
if any, will be incorporated.

b) The proposal will cover all requirements as realistically as possible. However, in

case of new or specific requirements, which would be discovered after the initial
system study, Price estimates and time estimates will be revised accordingly.

c) Client will be responsible for coordination of facilities and availability of all other
resources required to support the project.

d) Our consultants will work on a 7 hours/6 days a week schedule.

Private & Confidential

  PRICE ESTIMATES

Price Quotation will be sent after studying the relevant project.

 TERMS AND CONDITIONS

 In principle, all payments are to be made in Pakistan Rupees, payable to

RENAISSANCE Software (Pvt).Ltd:
o 25% Advance on signing of the contract.
o 25% on signing of SRS
o 25% on installation of final prototype
o 25% Completion and after training

 The proposal will be valid for 30 days after which time we may still choose to
abide by it but will not be bound to do so.

Private & Confidential