Has a well -defined methodology and a series of steps for
all stages in a typical software development project
lifecycle. This methodology has been documented and is
adhered to for all projects managed by NKB. For effective
management ,the complete project lifecycle is divided into
various phases. The software life cycle encompasses all
activities required to define, develop ,test, deliver,
operate and maintain the software project. Each phase has
well defined inputs ,processes and deliverables. |
| The
various phases in the software project life cycle are : |
 |
Work flow analysis |
|
|
Requirements |
|
|
Design |
|
|
Development |
|
|
Testing |
|
|
Installation and check out |
|
|
Warranty |
|
|
Maintenance |
|
|
| All these phases are discussed one by one in the
following sections |
WORK FLOW ANALYSIS |
| NKB constitutes a core group for work flow analysis.
This group comprises of users ,subjects matter experts,
developers involved in development and maintenance of
existing computer systems supporting existing Business
Processes, Customers, Project Manager and NKB's Consultants.
This group describes and defines the Business Processes and
requirements of the systems to be developed. NKB Team
facilitates all core group meetings and workshops . |
| This process is completed in three stages described
below: |
|
"AS-IS " Process Model |
|
|
"AS-IS" Analysis |
|
|
"TO-BE" Process Model |
|
|
| All these stages follow each other sequentially, as
discussed below. |
| "AS-IS"
PROCESS MODEL |
Workflow analysis begins with describing the Business
Processes as they exist. The group helps in documenting the
"AS-IS" Business Process layout. All the external
and internal "Entities" of the system are
identified. The group also identifies each transaction among
all the entities.
This process involves extensive user's interviews for
collecting information on the "AS-IS" Business
Processes .
NKB team then documents the "AS-IS" Business
Model using one of the process modeling tool. This document
is then presented to the core group for review and
acceptance. This document apart from describing the Business
Processes also contains |
|
Graphical description of the Business
Process model |
|
|
Entities and their interaction description and
layout |
|
|
Entities and their functional description |
|
|
| "AS-IS"
Analysis |
In this step the core group identifies the constraints
in the existing business processes and also suggests ways of
removing these constraints. NKB team facilitates the focus
group in identifying other opportunities to make business
processes more effective and efficient.
These constraints and opportunities are documented and are
used by the core group in the next step to define the "TO-BE"
Business Process Model. |
"TO-BE"
PROCESSES MODEL |
| The third step is to define the "TO-BE"
Business Process Model. While deriving the "TO-BE"
model, the constraints and opportunities identified during
the "AS-IS" analysis stage are considered and
applied. Both the workshop approach and the individual
interviews are used during this step. |
| ENTRY
POINT |
| Receipt of Purchase Order from Customers. |
Tasks |
|
Constitute Core Group |
|
|
Describe "AS-IS " Business Processes |
|
|
Prepare "AS-IS" Business Process Document |
|
|
Conduct "AS-IS" Business Process Analysis |
|
|
Prepare "AS-IS" Analysis Document |
|
|
Dfine "TO-BE" Business Processes |
|
|
Prepare "TO-BE" Business Process Document |
|
|
Conduct and facilitate Focus Group Workshops |
|
|
Conduct Individual Interviews |
|
|
| DELIVERABLES |
|
"AS-IS " Business Process
Document |
|
|
"AS-IS" Analysis Document |
|
|
"TO-BE" Business Process Description
Document |
|
|
| CHECK
POINTS: |
| Review and acceptance of Business Process model by
Focus Group and Project Manager. |
| Exit
Point |
| Acceptance of Business Process Model by Focus Group |
| REQUIREMENTS
PHASE |
This phase is undertaken by conducting user interviews and
studying the specifications provided by the user. The
proposed system is documented in the System Requirements
Specifications (SRS) DOCUMENT and includes description of
system requirements.
This document forms the basis for scope functionality of
proposed system. This is the reference document for all
subsequent phases including the Acceptance Test Phase. |
| Entry
Point |
| Receipt of Purchase Order from the customer or
acceptance of the "TO-BE" BUSINESS PROCESS model . |
| Tasks |
| |
Examine
the user requirements |
|
| |
Determine
context for study |
|
| |
Conduct
User Interviews |
|
| |
Examine
the documents/specifications provided by the user |
|
| |
Prepare/Modify
Data Flow Diagrams(DFD) |
|
| |
Define
Controls |
|
| |
Define
Interfaces with other Systems |
|
| |
Identify
Proposed System Requirements |
|
| |
Define
Naming Conventions |
|
| |
User
Interface Requirements |
|
| |
Output
and Input Requirements |
|
| |
Processing
Logic |
|
| |
Performance
Requirements |
|
| |
Security
and Backup Requirements |
|
| |
Interface
Requirements |
|
| |
Reliability/availability
Requirements |
|
| |
nstallation/operational
Requirements |
|
| |
Portability
Requirements |
|
| |
Standard
Compliance |
|
| |
Prepare
Data Flow Diagrams(DFD),Context Diagrams and Event List |
|
| |
Setup
Data Dictionary |
|
| |
Define
Input/ Output Screens/Formats |
|
| |
Prepare
Acceptance Plan(ATP) |
|
| |
Define
Acceptance Criteria |
|
| |
Outline
Acceptance Strategy |
|
| |
Define
Acceptance Test Resource Requirements |
|
| |
Functional
and Performance Test |
|
| |
Walk
through with Customer and Project Technical Review Team
(PTRT). |
|
|
| PTRT is an Internal Technical Evaluation Team of NKB
which takes an independent look at the deliverables
generated by the project team. |
|
|
| DELIVERABLES
|
|
SRS document |
|
|
ATP document |
|
|
| Check
Points |
|
Software Requirement Review(SRR) with
Project Technical Review Team |
|
|
Walk through /review of SRS and ATP with customer
and obtain approval |
|
|
| Exit
Point |
| Approval of SRS and ATP by customer. |
| DESIGN
PHASE |
After the SRS has been approved ,NKB TEAM starts work
on the design and produces external and internal
specifications also the test plan for integration and System
Tests are produced at the end of this phase ,the Program
design is complete and program specifications are ready .
|
Entry Point |
Approval of SRS and ATA by the customer
|
| Tasks |
| |
Define
Naming Conventions and Standard Compliance |
|
| |
Develop
System Architecture Specifications |
|
| |
Define
Modules and Components |
|
| |
Define
Boundaries and Interfaces |
|
| |
Detailed
Data Flow Diagrams |
|
| |
State
Transition Diagram |
|
| |
Data
Structure Design |
|
| |
Structure
Charts |
|
| |
Develop
External Interface specifications |
|
| |
Human
Computer Interface Design |
|
| |
Develop
Detailed Design Specifications |
|
| |
Identifications
of Modules , Components and Units |
|
| |
Physical
Design of Data Structure |
|
| |
Design
Inter-Program flow |
|
| |
Data
Dictionary |
|
| |
Detailed
Algorithm for Processing |
|
| |
Adaptations
for Identified Reusable Code |
|
| |
Initialization
Procedures |
|
| |
Exceptions
handling |
|
| |
Design
System and Integration Test |
|
| |
Design
test cases and procedures for integration and system
testing |
|
| |
Design
test data or receive test data from customer |
|
| |
Prepare
Draft User Manual |
|
| |
Prepare
Software Design Document |
|
| |
Walk
through of SDD with PTRT |
|
|
| DELIVERABLES |
| |
SDD
document |
|
| |
Test
document |
` |
|
| Check
Points: |
| |
Design
Review by PTRT |
|
| |
Review
and Approval of user interface by the customer |
|
| |
Review
of the test plans by the PTRT |
|
|
| Exit
Point |
Acceptance of SDD and Test Document by NKB Quality
Assurance Group
|
DEVELOPMENT PHASE |
This phase of Software Development involves translation of
design specifications into source code ,debugging
,documentation and unit testing.
|
| Entry
Point |
| Approval of SDD and test documents by PTRT. |
Tasks
|
|
Write Programs using SDD |
|
|
Unit Test Programs |
|
|
Integration |
|
|
Develop System Test and Acceptance Test Programs |
|
|
| DELIVERABLES |
|
Tested and Documented Programs |
|
|
System and Acceptance Test Programs |
|
|
Integration Test Reports |
|
|
| Check
Points |
| Sample source code review by QAG(Quality Assurance
Group) |
| Exit
Point: |
| Completion of integration testing of software as per
test plan. |
| TESTING
PHASE |
During this phase, the QAG tests the system by the running
and acceptance tests. The Customer may also conduct Factory
Acceptance test at this stage.
|
Entry
Point
|
| Completion of successful integration testing by
development team. |
Tasks:
|
|
QAG to perform Acceptance test |
|
|
Customer to conduct FAT |
|
|
Produce test Summary Reports |
|
|
| DELIVERABLES |
|
System installation procedure for next
phase |
|
|
Test summary |
|
|
| Check
Point |
| Review of test results and system acceptance by QAG. |
| Exit
Point |
| Approval or Acceptance by QAG. |
INSTALLATION
AND CHECK-OUT
|
During this phase the customer installs the system for
acceptance testing. As a part of acceptance test, the
customer uses real data. NKB team assists the customer
during this phase. User training is also conducted during
this phase. |
| Entry
Point |
| Completion of customer acceptance by the QAG. |
| Tasks |
|
Prepare for Acceptance Test |
|
|
Install Software |
|
|
Initialize Data Structures |
|
|
Assist Customer to conduct Acceptance Test |
|
|
Evaluate test Results |
|
|
Get approval on Acceptance test |
|
|
Revise and finalize all Documentation |
|
|
Register all deliverables for configuration
management |
|
|
Replicate the software at other customer
locations |
|
|
User training |
|
|
| DELIVERABLES |
|
Accepted system by the customer |
|
|
Acceptance Test Results |
|
|
| Check
Points |
| Physical Audit by configuration Management |
| Exit
Point |
| Acceptance of system by customer and physical audit
certificate. |
| WARRANTY
PHASE |
| During this phase NKB provides support to ensure proper
running of the developed software. NKB fixes all defects
detected during this period. |
| Entry
Point |
| On Completion of Acceptance test by consumer. |
| Tasks |
|
Hand over bug notification form to
customer |
|
|
Analyse and fix bug notified |
|
|
Log enhancement requests separately |
|
|
System tuning |
|
|
| DELIVERABLES |
| Support services |
| Check
Point |
| None |
| Exit
Point |
| End of warranty phase. |
| MAINTAINANCE
PHASE |
| During this phase, on site or remote customer support
is provided if so desired by the customer. Modifications are
made in order to enhance adopt and correct errors in
software developed by NKB. |
| Entry
Point |
| Signing of Maintenance Contract. |
| Tasks |
|
Maintain Software |
|
|
Release major version of software |
|
|
| DELIVERABLES |
|
Software releases |
|
|
Associated documentation |
|
|
New Source Code |
|
|
| Check
Point |
| As negotiated in the Maintenance Contract. |
Exit
Point
|
| As negotiated in the Maintenance Contract. |
| Quality
Assurance |
Right from the time the proposal is being prepared till
the project windup and archiving, our quality processes help
us in giving Quality product to the customer. A contract
review at the start of the project helps us to foresee the
risks or special concerns and plan preventive actions in
advance. This is followed by preparation of a Development
and Quality Plan that is a detailed plan that dictates the
way the project is to be managed. Every factor that will
have a bearing on the way the project progresses like Roles,
Responsibilities, Configuration Management, Exigency
management, Problem Escalation and Review Mechanism, is
clearly spelt out in the plan.
During the project execution, client has a single point of
contact. Our structured reporting ensures the client is
continually updated of the project progress. This project is
reviewed at various well-defined milestones against the
project plan. All changes to the specifications are
controlled through a strict change control mechanism.
Our Customer Feedback system and Software metrics system
enables us to continually improve further and achieve
enhanced customer satisfaction.
|
Project
Management |
|
Single Point of Contact |
|
|
Well defined milestones |
|
|
Well defined deliverables |
|
|
Configuration Control |
|
|
Structured Testing |
|
|
Structured Reporting |
|
|
Exigency Management |
|
|
Documentation |
|
|
Project Feedback |
|
|
Project Archiving |
|
|
NKB
Software Solutions (P) Ltd.